Snap: helio-services (revision 2, pending manual review)
Source: https://github.com/canonical/helio (snaps/helio-services/snap/snapcraft.yaml)
What it is
helio-services contains all OpenStack 2026.1 control-plane services (Keystone, Glance, Nova, Neutron, Cinder, Placement, Horizon…), strictly confined, configured by Helio through snap set.
Why these four interfaces
Helio Clouds without Ceph store volumes, and optionally images, on storage appliances: NetApp, Pure, Dell PowerStore, Hitachi, HPE 3PAR, IBM FlashSystem. Cinder and Glance then attach appliance volumes to the host through os-brick, the standard OpenStack library, to copy images to or from volumes, migrate them, and back them up.
This needs:
iscsi-initiator: iSCSI logins through the host’s iscsid (iscsiadm).nvme-control: NVMe-oF connections (nvme connect,/dev/nvme-fabrics).dm-multipath: multipath devices through the host’s multipathd.block-devices: reading and writing the attached block devices.
Scope
Only the three apps that attach volumes plug them:
glance-apicinder-volumecinder-volume-external(a second Cinder volume service for appliances in a separate availability zone)
No other app has them. Helio connects them only on nodes whose deployment uses an appliance backend; Ceph-only clouds don’t need them.
The daemons (iscsid, multipathd) stay the host’s; the snap only ships the client tools os-brick calls. This is the same need the upstream cinder-volume snap and Sunbeam’s storage charms have.
Happy to answer questions or narrow anything further.