Summary: Liberty OVS agent restarts are better, but still need work.
See: https://bugs.launchpad.net/neutron/+bug/1514056
As many of you know, Liberty has a fix for OVS agent restarts such
that it doesn’t dump all flows when starting, resulting in a loss of
traffic. Unfortunately, Liberty
Thanks Neil, very helpful.
From: neil.jer...@metaswitch.com
Subject: Re: [Openstack-operators] Anyone using Project Calico for tenant
networking?
Hi Ned,
Sorry for the delay in following up here.
On 06/02/16 14:40, Ned Rhudy (BLOOMBERG/ 731 LEX) wrote:
> Thanks. Having read the
Clayton,
This is really good information.
I’m wondering how we can help support you and get the necessary dev support to
get this resolved sooner than later. I totally agree with you that this should
be backported to at least Liberty.
Please let me know how I and other can help!
—Joe
On Wed, Feb 10, 2016 at 5:06 AM, Neil Jerram wrote:
> In terms of how floating IPs are represented in the Neutron data model:
> currently they require a relationship between an external Network, a
> Router and a tenant Network. The floating IP pool is defined as a
>
Hi all,
Unfortunately today's meeting of the Telco Working Group [1] is canceled, my
apologies for the late notice!
Thanks,
Steve
[1] https://wiki.openstack.org/wiki/TelcoWorkingGroup
___
OpenStack-operators mailing list
Hi Ned,
Sorry for the delay in following up here.
On 06/02/16 14:40, Ned Rhudy (BLOOMBERG/ 731 LEX) wrote:
> Thanks. Having read the documentation, I have one question about the
> network design. Basically, our use case specifies that instances be able
> to have a stable IP across terminations;
On Thu, Feb 4, 2016 at 5:41 AM, Tomas Vondra wrote:
> Hi Carl,
> sorry for the late reply, but these links of yours expanded to about 12 tabs
> in my browser, most with serveral pages of text. "Given lots of thought" may
> be an understatement.
>
> Both the specs sound very