[openstack-dev] [neutron] Expected cli behavior when ovs-agent is down

Assaf Muller amuller at redhat.com
Sun Aug 23 22:33:20 UTC 2015


On Sat, Aug 22, 2015 at 5:08 AM, shihanzhang <ayshihanzhang at 126.com> wrote:

> hi Vikas Choudhary, when ovs-agent service recover(ovs-agent process
> restart), the dhcp port will not re-binding successfully?
>
>
>
>
>
> At 2015-08-22 14:26:08, "Vikas Choudhary" <choudharyvikas16 at gmail.com>
> wrote:
>
> Hi Everybody,
>
> I want to discuss on https://bugs.launchpad.net/neutron/+bug/1348589.This
> is there for more than a year and no discussion i could find on this.
>
> *Scenario:*
> ovs-agent is down and then a network and subnet under this newly created
> network are created using cli. No error visible to user, but following
> irregularities are found.
>
> *Discrepancies:*
> 1. neutron port-show <dhcp-port> shows:
>      binding:vif_type      | binding_failed
> 2. Running "ovs-ofctl dump-flows br-tun", no of-flow got added
> 3. Running "ovs-vsctl show br-int", no tag for dhcp-port.
>
> neutron db will have all the attributes required to retry vif binding.My
> query is when should we trigger this rebinding.Two approaches i could think
> of are:
> 1> At neutron server restart, for all ports with vif_type as
>  "binding_failed" plugins/ml2/drivers/mech_agent.bind_port can be invoked
> as a sync up activity.
>
>
Or when you start the OVS agent again. Check out this patch:
https://review.openstack.org/#/c/162260/.


>
> 2> In neutron port update api,
> http://developer.openstack.org/api-ref-networking-v2-ext.html , could be
> enhanced to receive vif binding related options also and then
> eventually plugins/ml2/drivers/mech_agent.bind_port can be
> invoked.Corresponding changes will be made to 'port update cli' also.
>
> Please suggest.
>
>
>
> 夏日畅销榜大牌美妆只要1元
> <http://r.mail.163.com/r.jsp?url=http%3A%2F%2F1.163.com%2Fhd%2Foneact%2Fhdframe.do%3Fid%3D21%26from%3Dfooter_beauty&sign=817593681&_r_ignore_statId=7_13_79_48&_r_ignore_uid=nt@163.com>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150823/fb6df4b2/attachment.html>


More information about the OpenStack-dev mailing list