Open Stack

Indeed a blueprint has been filed (on Launchpad, not neutron-specs) on this already[0], but there has been no work on this as far as I can tell. I think it would be worthwhile contribution. 

Amir

[0] https://blueprints.launchpad.net/neutron/+spec/neutron-agent-soft-restart
________________________________________
From: Paul Ward [wpward at linux.vnet.ibm.com]
Sent: Monday, June 30, 2014 2:11 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [neutron] ovs-neutron-agent wipes out all flows on     startup

The current design for ovs-neutron-agent is that it will wipe out all
flows configured on the system when it starts up, recreating them for
each neutron port it's aware of.  This has a not-so-desirable side
effects that there's a temporary hiccup in network connectivity for the
VMs on the host.

My questions to the list: Is there a reason it was designed this way
(other than "Everything on the system must be managed by OpenStack")?
Is there ongoing work to address this or would it be a worthwhile
contribution from our side?


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev