Open Stack

Hi Jon,

We're about to expand our OpenStack Cloud to a second datacenter.
>

Congratulations! :)


> Anyone one have opinions they'd like to share as to what I would and
> should be worrying about or how to structure this?


What services will be shared between the two locations? Keystone with db
replication is usually quite easy and Glance with some type of file sync is
also easy.

Also think about network connectivity. Will the new location have a local
gateway to the internet? Or will all traffic come back to the original
location in order to get out? That's outside of OpenStack and more of a
general network/sysadmin thing, but it will determine how you handle
OpenStack outages when a network outage happens.


> Should I be thinking cells or regions (or maybe both)?  Any obvious or not
> so
> obvious pitfalls I should try to avoid?
>

I have never used Cells, but that's mostly due to being able to accomplish
everything with Regions. Check out some of my posts over the last year on
the regular OpenStack list about Regions.

Also think about how you'll handle Quotas. Do you want each user to have a
separate quota for each side? Or share a quota? I'm not aware of a
"supported" way by OpenStack or a side project that does the latter. We've
been doing this ourselves for several years using out of bound scripts.


> Current scale is about 75 hypervisors.  Running juno on Ubuntu 14.04
> using Ceph for volume storage, ephemeral block devices, and image
> storage (as well as object store).  Bulk data storage for most (but by
> no means all) of our workloads is at the current location (not that
> that matters I suppose).
>
> Second location is about 150km away and we'll have 10G (at least)
> between sites.


For one of our clouds, the two regions are 300km apart on a 10G connection.
We're seeing approximately 3.7ms ping times.

Some short notes:

* Galera replication works well -- we don't see any noticeable lag.

* We replicate Glance images by a simple rsync script.

* We have one site designated as "master" and that's where the main DNS
name points. Each site has a separate DNS name so you could access each one
using a specific URL (cloud.example.com, site1.cloud.example.com,
site2.cloud.example.com). By accessing any of them, once logged into the
dashboard you can access the opposite through Horizon.

Hope that helps... let me know if you have any questions on any of the
above.

Joe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150504/8f8192d6/attachment.html>