Verifying the Configured Changes

Ensure that the backend details are available in /etc/cinder/cinder.conf in the cinder-volume container [overcloud-controller-0 ~]$ sudo podman exec -it openstack-cinder-volume-podman-0 tail -22/etc/cinder/cinder.conf.

[datacore_iscsi1]

datacore_api_timeout=300

datacore_disk_failed_delay=300

datacore_disk_pools=cinder-pool

datacore_disk_type=single

san_ip=datacore.domain.com

san_login=your_san_login

san_password=your_san_password

volume_backend_name=datacore_iscsi1

volume_driver=cinder.volume.drivers.datacore.iscsi.ISCSIVolumeDriver

backend_host=hostgroup

[datacore_fc1]

datacore_api_timeout=300

datacore_disk_failed_delay=300

datacore_disk_pools=cinder-pool

datacore_disk_type=single

san_ip=datacore.domain.com

san_login=your_san_login

san_password=your_san_password

volume_backend_name=datacore_fc1

volume_driver=cinder.volume.drivers.datacore.fc.FibreChannelVolumeDriver

backend_host=hostgroup

Ensure that the services are working using the openstack volume service list command:

(overcloud) [director~]$ openstack volume service list .