Using openstack in a different location - what options are there?

asked 2020-01-14 00:05:23 -0500

tony.pearce gravatar image

I have a working 3-node openstack environment with storage array:

  • 1 x virtual controller
  • 2 x physical hosts
  • And storage is backed by cinder / iscsi against a Nimble Storage array, which uses the nimble-cinder API.

I want to be able to use openstack if this environment is down, such as power or internet failure.

I have another physical location, with another Nimble Storage array and some empty physical hosts. Moving the controller to the other location is easy, because it's a VM and is taken care of by the host which it runs on. But there are some confusions on my side about the other components such as:

  • physical host
  • data storage volumes

Regarding data storage, all of the instances have volumes which reside on the nimble array and are accessed via iscsi from the controller and the hosts.

-> does openstack have any way of copying data from one datatype to another?

I can enable volume replication on the nimble side. However, the IQN and storage array IP addresses are different at the other site so I dont see how it would be useful.

I guess maybe I should be asking if there are any examples of running openstack across 2 sites with 2 separate storage arrays, and how it's achievable.

edit retag flag offensive close merge delete


How about:

  1. replicate the production volumes to 2nd location
  2. bring up the controller in the 2nd location
  3. update the cinder DB to point all the volumes to the new IQN and IP address

I dont want to edit db... is there a better option?

tony.pearce gravatar imagetony.pearce ( 2020-01-14 04:51:32 -0500 )edit

There is discussion on cheesecake but apart from a 2016 proposal i dont see it has been implemented into any openstack :(

tony.pearce gravatar imagetony.pearce ( 2020-01-15 20:12:52 -0500 )edit