On 07/13/2015 04:09 AM, Kevin Benton wrote:
because you won't have to run Neutron agents on compute nodes anymore.
How will upgrades work for OVN?
We haven't written anything down yet, but here's what I expect.
Right now we're still changing the db schema however is needed without
messing
Thanks for the info. So the equivalent in neutron would be if we just
ensure backward compatible AMQP APIs, right?
On Mon, Jul 13, 2015 at 7:33 AM, Russell Bryant rbry...@redhat.com wrote:
On 07/13/2015 04:09 AM, Kevin Benton wrote:
because you won't have to run Neutron agents on compute nodes
On 07/13/2015 05:08 PM, Kevin Benton wrote:
Thanks for the info. So the equivalent in neutron would be if we just
ensure backward compatible AMQP APIs, right?
There's a few parts:
1) Backwards compatibility with changes to the oslo.messaging APIs using
API versioning (what you're referring to,
Some pedant comments inline.
Salvatore
On 13 July 2015 at 23:29, Russell Bryant rbry...@redhat.com wrote:
On 07/13/2015 05:08 PM, Kevin Benton wrote:
Thanks for the info. So the equivalent in neutron would be if we just
ensure backward compatible AMQP APIs, right?
There's a few parts:
because you won't have to run Neutron agents on compute nodes anymore.
How will upgrades work for OVN?
On Thu, Jul 9, 2015 at 2:30 PM, Russell Bryant rbry...@redhat.com wrote:
On 07/09/2015 10:11 AM, Ihar Hrachyshka wrote:
On 07/09/2015 09:01 AM, Artur Korzen wrote:
Hi all,
I've been
Thanks Ihar comments!
Is Neutron ready to be upgradable with minimal downtime of services
and no VM access downtime?
As the ovs bug you refer to above, no, at least not in reference
implementation. That's for data plane.
My understanding is that after the ovs neutron agent will be
On 07/09/2015 10:11 AM, Ihar Hrachyshka wrote:
On 07/09/2015 09:01 AM, Artur Korzen wrote:
Hi all,
I've been researching the Neutron project as a part of work on
Openstack rolling upgrades, my primary assignments included
testing if there is no VM access downtime when performing
upgrade.
