From df63282b329965b03a8956170aa0b5406a894e56 Mon Sep 17 00:00:00 2001 From: Michal Nasiadka Date: Wed, 11 Mar 2026 12:10:25 +0100 Subject: cinder: Change default destination for cinder-volume/backup containers Kolla-Ansible defaulted for long time to deploy cinder-volume/backup containers on storage group, which is good for Cinder LVM deployments. Problem is - majority of deployments does not use Cinder LVM backend - they use mainly Ceph (based on OpenStack User Survey) and probably some other proprietary vendors which are API driven. Let's change the default to reflect reality. If a user has cinder lvm enabled - we will deploy it as it was before If a user has both cinder lvm and something else enabled - we will deploy cinder-volume and cinder-backup in both places (cinder group and storage group) If a user doesn't have cinder lvm enabled - we deploy only in the cinder group Change-Id: Ia4a874de8f1b8eab8ff688eab4c6af013449c18c Signed-off-by: Michal Nasiadka --- doc/source/reference/storage/cinder-guide.rst | 47 ++++++++------------------- 1 file changed, 13 insertions(+), 34 deletions(-) (limited to 'doc') diff --git a/doc/source/reference/storage/cinder-guide.rst b/doc/source/reference/storage/cinder-guide.rst index 9f8a5bf2a..a850deb27 100644 --- a/doc/source/reference/storage/cinder-guide.rst +++ b/doc/source/reference/storage/cinder-guide.rst @@ -67,6 +67,14 @@ Enable the ``lvm`` backend in ``/etc/kolla/globals.yml``: enable_cinder_backend_lvm: "yes" +Edit the inventory file and add ``storage`` group as a child of +``cinder-volume`` group: + +.. code-block:: ini + + [cinder-volume:children] + storage + .. note:: There are currently issues using the LVM backend in a multi-controller setup, @@ -151,9 +159,11 @@ Cinder LVM2 backend with iSCSI As of Newton-1 milestone, Kolla supports LVM2 as cinder backend. It is accomplished by introducing two new containers ``tgtd`` and ``iscsid``. -``tgtd`` container serves as a bridge between cinder-volume process and a -server hosting Logical Volume Groups (LVG). ``iscsid`` container serves as -a bridge between nova-compute process and the server hosting LVG. +``tgtd`` container is the target part of iSCSI setup which needs to run +on the ``storage`` Ansible group for exposing volumes from LVM. +``iscsid`` container is the client part of iSCSI setup which needs to run +together with nova-compute for instance access to storage and on hosts +running ``cinder-volume`` and ``cinder-backup`` for volume operations. In order to use Cinder's LVM backend, a LVG named ``cinder-volumes`` should exist on the server and following parameter must be specified in @@ -163,37 +173,6 @@ exist on the server and following parameter must be specified in enable_cinder_backend_lvm: "yes" -For Ubuntu and LVM2/iSCSI -------------------------- - -``iscsd`` process uses configfs which is normally mounted at -``/sys/kernel/config`` to store discovered targets information, on centos/rhel -type of systems this special file system gets mounted automatically, which is -not the case on debian/ubuntu. Since ``iscsid`` container runs on every nova -compute node, the following steps must be completed on every Ubuntu server -targeted for nova compute role. - -* Add configfs module to ``/etc/modules`` -* Rebuild initramfs using: ``update-initramfs -u`` command -* Stop ``open-iscsi`` system service due to its conflicts - with iscsid container. - - Ubuntu 16.04 (systemd): - ``systemctl stop open-iscsi; systemctl stop iscsid`` - -* Make sure configfs gets mounted during a server boot up process. There are - multiple ways to accomplish it, one example: - - .. code-block:: console - - mount -t configfs /etc/rc.local /sys/kernel/config - - .. note:: - - There is currently an issue with the folder /sys/kernel/config as it is - either empty or does not exist in several operating systems, - see `_bug 1631072 `__ for more info - Cinder backend with external iSCSI storage ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- cgit v1.2.3