Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cinder: Support for multiple Volume Service AZs #30

Open
snschee opened this issue Mar 28, 2017 · 1 comment
Open

Cinder: Support for multiple Volume Service AZs #30

snschee opened this issue Mar 28, 2017 · 1 comment

Comments

@snschee
Copy link

snschee commented Mar 28, 2017

In our Prod environment we currently use two Cinder Volume AZs.
The first AZ was setup via SOC Crowbar.
For the second AZ we used the stacked configuration file future and replaced some cinder.conf parameters.

root@d2c-76-8a-ac-64-ff:~ # ps -aef | grep cinder-volume
root     21813 13446  0 10:02 pts/1    00:00:00 grep --color=auto cinder-volume
cinder   27631     1  0 Feb01 ?        10:57:02 /usr/bin/python /usr/bin/cinder-volume --config-file=/etc/cinder/cinder.conf --config-file=/etc/cinder/cinder-volume-lab42bAZ2.conf --logfile=/var/log/cinder/volume-lab42bAZ2.log
cinder   27649 27631  2 Feb01 ?        1-03:49:25 /usr/bin/python /usr/bin/cinder-volume --config-file=/etc/cinder/cinder.conf --config-file=/etc/cinder/cinder-volume-lab42bAZ2.conf --logfile=/var/log/cinder/volume-lab42bAZ2.log

root@d2c-76-8a-ac-64-ff:~ # cat /etc/cinder/cinder-volume-lab42bAZ2.conf
[DEFAULT]
storage_availability_zone = lab42bAZ2
default_availability_zone = nova
allow_availability_zone_fallback = false

enabled_backends=backend-netapp-lab42bAZ2-0

debug = true

[backend-netapp-lab42bAZ2-0]
volume_backend_name = lab42bvsos8
use_multipath_for_image_xfer = true
iscsi_write_cache = off
netapp_server_hostname = 10.20.90.64
netapp_server_port = 1080
netapp_pool_name_search_pattern =
netapp_transport_type = http
netapp_vserver = lab42bvsos8
netapp_storage_family = ontap_cluster
netapp_storage_protocol = nfs
nfs_shares_config=/etc/cinder/nfs_shares-backend-netapp-lab42bAZ2-0
volume_driver = cinder.volume.drivers.netapp.common.NetAppDriver
root@d2c-76-8a-ac-64-ff:~ #

But therefor we still use the non-clustered (active-passive) Cinder-Volume configuration where the Cinder-Volume services are pinned to a specific control node:

root@d2c-76-8a-ac-64-6e:~ # cinder-manage service list
Binary           Host                                 Zone             Status     State Updated At
cinder-scheduler d2c-76-8a-ac-65-ff                   nova             enabled    :-)   2017-03-28 10:04:38.919489
cinder-volume    d2c-76-8a-ac-64-ff@backend-netapp-lab42bAZ2-0 lab42bAZ2        enabled    :-)   2017-03-28 10:04:39.045227
cinder-scheduler d2c-76-8a-ac-64-ff                   nova             enabled    :-)   2017-03-28 10:04:42.590909
cinder-volume    d2c-76-8a-ac-64-ff@backend-netapp-0  nova             enabled    :-)   2017-03-28 10:04:43.464835
cinder-scheduler d2c-76-8a-ac-64-ff                   nova             enabled    :-)   2017-03-28 10:04:39.567708
root@d2c-76-8a-ac-64-ff:~ #

Can you please add support of multiple Cinder-Volume services in different Cinder-AZs in the same control cluster with active-passive failover support.

@matelakat
Copy link

cinder active-passive is not working with multi-az setup, that is the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants