Cinder-volume auto-connect iscsi/nvme system files

store-requests privileged-interfaces
1
  • name: cinder-volume
  • description: The Cinder Volume snap contains the Volume handler from the OpenStack cinder service. This service is responsible for spawning volumes from external backends, such as Ceph, PureStorage, Hitachi, Dell SC…
  • snapcraft: snap-cinder-volume/snap/snapcraft.yaml at main · canonical/snap-cinder-volume · GitHub
  • upstream: https://opendev.org/openstack/cinder/
  • upstream-relation: Cinder Volume snap is managed by the Canonical OpenStack team. We are a downstream distribution of the OpenStack project. This work is a part of the upstream Sunbeam work.
  • interfaces:
    • system-files - etc-iscsi:
      • request-type: auto-connection
      • reasoning: Required to access iSCSI configuration files (/etc/iscsi/initiatorname.iscsi, /etc/iscsi/iscsid.conf) and state directory (/var/lib/iscsi) for establishing iSCSI connections to storage backends like PureStorage, Hitachi, and Dell SC arrays. Many enterprise storage systems use iSCSI as the primary protocol for volume attachment.
    • system-files - nvme-identity:
      • request-type:auto-connection
      • reasoning: Needed to read NVMe host identification files (/etc/nvme/hostnqn, /etc/nvme/hostid) which are required for NVMe-over-Fabrics connections to modern storage arrays. Enterprise storage backends increasingly support NVMe protocols for high-performance volume access.
    • system-files - nvme-multipath:
      • request-type: auto-connection
      • reasoning: Required to read NVMe multipath configuration (/sys/module/nvme_core/parameters/multipath) to determine if NVMe multipathing is enabled on the system. This is essential for ensuring redundant paths to NVMe storage backends and proper failover behavior in enterprise storage environments.
2

This request has been added to the queue for review by the @reviewers team.

3

Hello @gboutry!

Given the snap’s functionality, all requested interfaces make sense to me. +1(#voteFor) from my side for auto-connecting the requested system-files to cinder-volume

4

Hello, I’m going to retract this query, as it actually not the right way to handle this use case.

These system-files interfaces are most likely to go away, instead being replaced by: interfaces: add iscsi-initiator, multipath-control interfaces by gboutry · Pull Request #15949 · canonical/snapd · GitHub

NVMeOF will have to be re-investigated.

5

Hey @gboutry, thanks for the update.

In that case I’m removing the request from the queue for now. Thanks!