Hi Wodel, You simply need to create a cinder-volume.conf in your config override directory with the backend blocks you want, eg: $ cat cinder-volume.conf [DEFAULT] enabled_backends=nimble-az1,nimble-az2,ceph-nvme-az3 cross_az_attach = False [nimble-az1] san_ip = {{ nimble_az1_controller_vip }} san_login = {{ nimble_admin_user }} san_password = {{ nimble_admin_password }} volume_driver = cinder.volume.drivers.nimble.NimbleISCSIDriver volume_backend_name = nimble backend_availability_zone = {{ availability_zone_1 }} backend_host = {{ nimble_hostgroup }} report_discard_supported = True enable_unsupported_driver = True suppress_requests_ssl_warnings = True use_multipath_for_image_xfer = False [nimble-az2] san_ip = {{ nimble_az1_controller_vip }} san_login = {{ nimble_admin_user }} san_password = {{ nimble_admin_password }} volume_driver = cinder.volume.drivers.nimble.NimbleISCSIDriver volume_backend_name = nimble backend_availability_zone = {{ availability_zone_2 }} backend_host = {{ nimble_hostgroup }} report_discard_supported = True enable_unsupported_driver = True suppress_requests_ssl_warnings = True use_multipath_for_image_xfer = False [ceph-nvme-az3] volume_driver = cinder.volume.drivers.rbd.RBDDriver rbd_pool = {{ ceph_cinder_pool_name }} rbd_ceph_conf = /etc/ceph/ceph.conf rbd_flatten_volume_from_snapshot = false rbd_max_clone_depth = 5 rbd_store_chunk_size = 4 rados_connect_timeout = 5 rbd_user = {{ ceph_cinder_user }} rbd_secret_uuid = {{ cinder_rbd_secret_uuid }} report_discard_supported = True image_upload_use_cinder_backend = True volume_backend_name = high-performance backend_availability_zone = {{ availability_zone_3 }} backend_host = ceph-nvme Please note that the ceph setup in kolla-ansible is fairly rigid and assumes a single cinder pool and a single cinder ceph user. You are probably better off defining your own ceph blocks if you need to split across the separate pools. If you better want to understand the workflow for kolla deploying ceph here are the relevant sections: https://github.com/openstack/kolla-ansible/blob/8371d979b6c07ec64eb56b5948c9... https://github.com/openstack/kolla-ansible/blob/stable/yoga/ansible/roles/ci... Cheers, Danny ________________________________ From: wodel youchi <wodel.youchi@gmail.com> Sent: 05 May 2022 09:19 To: OpenStack Discuss <openstack-discuss@lists.openstack.org> Subject: [Kolla-ansible][xena] how to deploy multiple cinder backends? CAUTION: This email originates from outside THG ________________________________ Hi, I want to deploy multiple cinder backends, ceph SSD pool for high performance VMS, ceph SAS pool for normal VMS and NFS share for small VMS and for cinder backup. Could that be done while deploying or it has to be done after the initial deployment? Could you assist me with some examples, sometimes the documentation is not that obvious to understand. Regards. Danny Webb Principal OpenStack Engineer The Hut Group<http://www.thehutgroup.com/> Tel: Email: Danny.Webb@thehutgroup.com<mailto:Danny.Webb@thehutgroup.com> For the purposes of this email, the "company" means The Hut Group Limited, a company registered in England and Wales (company number 6539496) whose registered office is at Fifth Floor, Voyager House, Chicago Avenue, Manchester Airport, M90 3DQ and/or any of its respective subsidiaries. Confidentiality Notice This e-mail is confidential and intended for the use of the named recipient only. If you are not the intended recipient please notify us by telephone immediately on +44(0)1606 811888 or return it to us by e-mail. Please then delete it from your system and note that any use, dissemination, forwarding, printing or copying is strictly prohibited. Any views or opinions are solely those of the author and do not necessarily represent those of the company. Encryptions and Viruses Please note that this e-mail and any attachments have not been encrypted. They may therefore be liable to be compromised. Please also note that it is your responsibility to scan this e-mail and any attachments for viruses. We do not, to the extent permitted by law, accept any liability (whether in contract, negligence or otherwise) for any virus infection and/or external compromise of security and/or confidentiality in relation to transmissions sent by e-mail. Monitoring Activity and use of the company's systems is monitored to secure its effective use and operation and for other lawful business purposes. Communications using these systems will also be monitored and may be recorded to secure effective use and operation and for other lawful business purposes. hgvyjuv