[Openstack-operators] best practice to manage multiple Data center using openstack

2016-01-28 Thread XueSong Ma
Hi: does anyone can tell me what are the best way or manage multiple DC using one openstack system? or the good reasons for it? We have sevel openstack env(multiple region), but its really difficult to manage them, python code, software update. etc. Thanks a lot! Jeff __

Re: [Openstack-operators] DVR and public IP consumption

2016-01-28 Thread Fox, Kevin M
Hi Tomas, The using external addresses per tenant router is a feature to a lot of sites, like ours. We want to know for sure, at minimum, which tenant was responsible for bad activity on the external network. Having the external address tied to a tenant router allows you to track bad activity b

Re: [Openstack-operators] DVR and public IP consumption

2016-01-28 Thread Fox, Kevin M
Ah. so it was done just to make it simple to reuse lots of existing code to get DVR working quickly and thus a current requirement, but there is nothing stopping further enhancements to be made to eliminate it in the future? What about a step in between what's there now, and eliminating it compl

Re: [Openstack-operators] Live migration neutron issues

2016-01-28 Thread Adam Dibiase
I have an update to my migration issue and thought I would share. It seems this happens on instances that are CentOS 5.x. It does not happen on instances that are CentOS 6.x. Does anyone know what neutron is sending to the guest to start the network post migration and why it would not work in CentO

[Openstack-operators] Announcing Debian Mitaka b2 packages with backports for Jessie and Trusty

2016-01-28 Thread Thomas Goirand
Hi everyone, I'm delighted to announce the release of Debian packages for Mitaka b2. Debian Experimental === I have uploaded it all to Debian Experimental. This is the only place where you may find official packages. It will stay this way until Debian Bikesheds (Bikesheds is what

Re: [Openstack-operators] DVR and public IP consumption

2016-01-28 Thread Tomas Vondra
Robert Starmer writes: > > > I think I've created a bit of confusion, because I forgot that DVR still does SNAT (generic non Floating IP tied NAT) on a central network node just like in the non-DVR model.  The extra address that is consumed is allocated to a FIP specific namespace when a DVR is