<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Noel,<br>
<br>
The ML2 plugin uses the binding:host_id attribute of port to control
port binding. For compute ports, nova sets binding:host_id when
creating/updating the neutron port, and ML2's openvswitch mechanism
driver will look in agents_db to make sure the openvswitch L2 agent
is running on that host, and that it has a bridge mapping for any
needed physical network or has the appropriate tunnel type enabled.
The binding:host_id attribute also gets set on DHCP, L3, and other
agents' ports, and must match the host of the openvswitch-agent on
that node or ML2 will not be able to bind the port. I suspect your
configuration may be resulting in these not matching, and the DHCP
port's binding:vif_type attribute being 'binding_failed'.<br>
<br>
I'd suggest running "neutron port-show" as admin on the DHCP port to
see what the values of binding_vif_type and binding:host_id are, and
running "neutron agent-list" as admin to make sure there is an L2
agent on that node and maybe "neutron agent-show" as admin to get
that agents config details.<br>
<br>
-Bob<br>
<br>
<br>
<div class="moz-cite-prefix">On 10/20/14 1:28 PM, Noel Burton-Krahn
wrote:<br>
</div>
<blockquote
cite="mid:CAH6UTCF4hi3e6isyCPy=nK5gQ2k=KX=41-9aJ5SRqktWW-oPeg@mail.gmail.com"
type="cite">
<div dir="ltr">I'm running OpenStack Icehouse with Neutron
ML2/OVS. I've configured the ml2-ovs-plugin on all nodes with
host = the IP of the host itself. However, my dhcp-agent may
float from host to host for failover, so I configured it with
host="floating". That doesn't work. In this case, the
ml2-ovs-plugin creates a namespace and a tap interface for the
dhcp agent, but OVS doesn't route any traffic to the dhcp
agent. It *does* work if the dhcp agent's host is the same as
the ovs plugin's host, but if my dhcp agent migrates to another
host, it loses its configuration since it now has a different
host name.
<div><br>
</div>
<div>So my question is, what does host mean for the ML2 dhcp
agent and host can I get it to work if the dhcp agent's host
!= host for the ovs plugin?</div>
<div><br>
</div>
<div>Case 1: fails: running with dhcp agent's host = "floating",
ovs plugin's host = IP-of-server</div>
<div>dhcp agent is running in netns created by ovs-plugin</div>
<div>dhcp agent never receives network traffic</div>
<div><br>
</div>
<div>Case 2: ok: running with dhcp agent's host = ovs plugin's
host = IP-of-server</div>
<div>
<div>dhcp agent is running in netns created by ovs-plugin
(different tap name than case 1)</div>
</div>
<div>dhcp agent works</div>
<div><br>
</div>
<div>--</div>
<div>Noel</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> </div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>