[Openstack-operators] [all] QPID incompatible with python 3 and untested in gate -- what to do?

Hello! There's been some recent progress on python3 compatibility for core libraries that OpenStack depends on[1], and this is likely to open the flood gates for even more python3 problems to be found and fixed. Recently a proposal was made to make oslo.messaging start to run python3 tests[2],

[Openstack-operators] [Neutron] Floating IPs / Router Gateways

Hi folks, Looking for a bit of advice on how to accomplish something with Neutron. Our setup uses OVS+GRE with isolated tenant networks. Currently, we have one large network servicing our Floating IPs as well as our external router interfaces. What we're looking to do is actually have two

[Openstack-operators] Oslo.messaging ZeroMQ driver changes in Liberty

Hi, Does anyone use any version of ZeroMQ driver in production deployment? If you do, please leave your comments in [1], or reply to this letter. [1] https://review.openstack.org/#/c/171131/ Thanks, Oleksii Zamiatin ___ OpenStack-operators mailing

[Openstack-operators] [Large Deployments] UPDATE: Meeting this Thursday at 16:00 UTC #openstack-meeting

Hello again, folks! I went over all the schedules at: https://wiki.openstack.org/wiki/Meetings And for the Even months (Feb, April, June, etc). #openstack-meeting was open at 16:00 UTC. So, I've updated the above to include our meeting and added: https://wiki.openstack.org/wiki/Meetings/LDT

Re: [Openstack-operators] [Neutron] Floating IPs / Router Gateways

Probably not in the way you want. You can have two subnets on the external network. Then you would set the allocation pool to be nothing for the subnet that you want the router interfaces to be attached to to make sure floating IPs aren't allocated from it. Then whenever you attach a router

Re: [Openstack-operators] [Neutron] Floating IPs / Router Gateways

Jacob Godin jacobgo...@gmail.com wrote on 04/14/2015 05:12:48 PM: Absolutely. We're trying to reduce our public IPv4 usage, so having one per tenant network (not even including floating IPs) is a drain. I am having exactly the same issue. I am currently solving it with a different hack that

[Openstack-operators] [Neutron] Floating IPs / Router Gateways

- Original Message - Hi folks, Looking for a bit of advice on how to accomplish something with Neutron. Our setup uses OVS+GRE with isolated tenant networks. Currently, we have one large network servicing our Floating IPs as well as our external router interfaces. What we're

Re: [Openstack-operators] [Neutron] Floating IPs / Router Gateways

Absolutely. We're trying to reduce our public IPv4 usage, so having one per tenant network (not even including floating IPs) is a drain. Instead of having: instance - (gateway IP) virtual router NAT (public IP) - (public gateway) router We want to have: instance - (gateway IP) virtual router NAT

Re: [Openstack-operators] [Neutron] Floating IPs / Router Gateways

Thanks Kevin. That might work in some instances, however our tenants have the ability to create their own routers and allocate their gateway. I suppose we could hack some code in to restrict what networks are usable for routers vs floating IPs. On Tue, Apr 14, 2015 at 6:08 PM, Kevin Benton

Re: [Openstack-operators] [Neutron] Floating IPs / Router Gateways

Hey Mike, Would you send along your solution off-list? I'm curious, and I won't judge :) On Tue, Apr 14, 2015 at 6:22 PM, Mike Spreitzer mspre...@us.ibm.com wrote: Jacob Godin jacobgo...@gmail.com wrote on 04/14/2015 05:12:48 PM: Absolutely. We're trying to reduce our public IPv4 usage, so