<div dir="ltr">Hi Marius,<div><br></div><div>Attached is the controller node template.</div><div>I've also added below the ovs-vsct show results for both the compute and control node</div><div>For some reason there is also a bridge called "undef" in both the controller and the compute</div><div><br></div><div><div>[heat-admin@overcloud-controller-0 ~]$ sudo ovs-vsctl show</div><div>00ce4561-418d-4161-b907-3b2222930f35</div><div>    Manager "ptcp:6640:127.0.0.1"</div><div>    Bridge br-int</div><div>        Controller "tcp:<a href="http://127.0.0.1:6633">127.0.0.1:6633</a>"</div><div>        fail_mode: secure</div><div>        Port br-int</div><div>            Interface br-int</div><div>                type: internal</div><div>    Bridge undef</div><div>        Port undef</div><div>            Interface undef</div><div>                type: internal</div><div>    Bridge br-mng</div><div>        fail_mode: standalone</div><div>        Port "vlan204"</div><div>            tag: 204</div><div>            Interface "vlan204"</div><div>                type: internal</div><div>        Port "vlan202"</div><div>            tag: 202</div><div>            Interface "vlan202"</div><div>                type: internal</div><div>        Port br-mng</div><div>            Interface br-mng</div><div>                type: internal</div><div>        Port "vlan203"</div><div>            tag: 203</div><div>            Interface "vlan203"</div><div>                type: internal</div><div>        Port "eno2"</div><div>            Interface "eno2"</div><div>        Port "vlan201"</div><div>            tag: 201</div><div>            Interface "vlan201"</div><div>                type: internal</div><div>    Bridge br-up</div><div>        Port br-up</div><div>            Interface br-up</div><div>                type: internal</div><div>    Bridge br-ex</div><div>        fail_mode: standalone</div><div>        Port br-ex</div><div>            Interface br-ex</div><div>                type: internal</div><div>        Port "eno3"</div><div>            Interface "eno3"</div><div>    ovs_version: "2.5.0"</div><div>[heat-admin@overcloud-controller-0 ~]$</div></div><div><div><br></div><div><br></div><div>[heat-admin@overcloud-compute-0 ~]$ sudo ovs-vsctl show</div><div>2f6bccd5-9653-42df-a1db-8cb5c3b0293a</div><div>    Manager "ptcp:6640:127.0.0.1"</div><div>    Bridge br-down</div><div>        fail_mode: standalone</div><div>        Port br-down</div><div>            Interface br-down</div><div>                type: internal</div><div>        Port "em3"</div><div>            Interface "em3"</div><div>    Bridge br-up</div><div>        fail_mode: standalone</div><div>        Port br-up</div><div>            Interface br-up</div><div>                type: internal</div><div>        Port "em4"</div><div>            Interface "em4"</div><div>    Bridge br-ex</div><div>        fail_mode: standalone</div><div>        Port "vlan204"</div><div>            tag: 204</div><div>            Interface "vlan204"</div><div>                type: internal</div><div>        Port "vlan202"</div><div>            tag: 202</div><div>            Interface "vlan202"</div><div>                type: internal</div><div>        Port "vlan201"</div><div>            tag: 201</div><div>            Interface "vlan201"</div><div>                type: internal</div><div>        Port br-ex</div><div>            Interface br-ex</div><div>                type: internal</div><div>        Port "em2"</div><div>            Interface "em2"</div><div>    Bridge br-int</div><div>        Controller "tcp:<a href="http://127.0.0.1:6633">127.0.0.1:6633</a>"</div><div>        fail_mode: secure</div><div>        Port br-int</div><div>            Interface br-int</div><div>                type: internal</div><div>    Bridge undef</div><div>        Port undef</div><div>            Interface undef</div><div>                type: internal</div><div>    ovs_version: "2.5.0"</div><div>[heat-admin@overcloud-compute-0 ~]$</div></div><div><br></div><div><br></div><div><br></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Mar 31, 2017 at 1:01 PM Marius Cornea <<a href="mailto:marius@remote-lab.net">marius@remote-lab.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Samuel,<br class="gmail_msg">
<br class="gmail_msg">
Could you please share the nic template used for the controller node?<br class="gmail_msg">
The bridges should be created according to the nic template so I would<br class="gmail_msg">
like to see how it looks.<br class="gmail_msg">
<br class="gmail_msg">
Thanks!<br class="gmail_msg">
<br class="gmail_msg">
On Thu, Mar 30, 2017 at 4:59 PM, Samuel Monderer<br class="gmail_msg">
<<a href="mailto:smonderer@vasonanetworks.com" class="gmail_msg" target="_blank">smonderer@vasonanetworks.com</a>> wrote:<br class="gmail_msg">
> Hi,<br class="gmail_msg">
><br class="gmail_msg">
> I would like to test my VNF on an openstack environment deployed using<br class="gmail_msg">
> TripleO.<br class="gmail_msg">
> For that I need to setup flat provider networks that go only to the compute<br class="gmail_msg">
> node.<br class="gmail_msg">
> I tried deploying an overcoud with additional neutron bridge mappings as<br class="gmail_msg">
> following<br class="gmail_msg">
><br class="gmail_msg">
> Added NeutronBridgeMappings: "<br class="gmail_msg">
> datacentre:br-ex,physdown;br-down,physup:br-up" to network environment file<br class="gmail_msg">
> Added following resources to compute.yaml file<br class="gmail_msg">
><br class="gmail_msg">
>             -<br class="gmail_msg">
>               type: ovs_bridge<br class="gmail_msg">
>               name: br-down<br class="gmail_msg">
>               mtu: 9000<br class="gmail_msg">
>               members:<br class="gmail_msg">
>                 -<br class="gmail_msg">
>                   type: interface<br class="gmail_msg">
>                   name: ens4f0<br class="gmail_msg">
>                   # force the MAC address of the bridge to this interface<br class="gmail_msg">
>                   primary: true<br class="gmail_msg">
>             -<br class="gmail_msg">
>               type: ovs_bridge<br class="gmail_msg">
>               name: br-up<br class="gmail_msg">
>               mtu: 9000<br class="gmail_msg">
>               members:<br class="gmail_msg">
>                 -<br class="gmail_msg">
>                   type: interface<br class="gmail_msg">
>                   name: ens4f1<br class="gmail_msg">
>                   # force the MAC address of the bridge to this interface<br class="gmail_msg">
>                   primary: true<br class="gmail_msg">
><br class="gmail_msg">
> This will create the intended OVS bridges on the the compute node with the<br class="gmail_msg">
> interfaces connected.<br class="gmail_msg">
><br class="gmail_msg">
> The unwanted side effect it that ii also created the bridges on the<br class="gmail_msg">
> controller node without any interfaces connected to it<br class="gmail_msg">
><br class="gmail_msg">
> Is there a way to have the undercloud create the bridges only on the compute<br class="gmail_msg">
> nodes and not on the controller nodes???<br class="gmail_msg">
><br class="gmail_msg">
> Samuel<br class="gmail_msg">
><br class="gmail_msg">
> _______________________________________________<br class="gmail_msg">
> rdo-list mailing list<br class="gmail_msg">
> <a href="mailto:rdo-list@redhat.com" class="gmail_msg" target="_blank">rdo-list@redhat.com</a><br class="gmail_msg">
> <a href="https://www.redhat.com/mailman/listinfo/rdo-list" rel="noreferrer" class="gmail_msg" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br class="gmail_msg">
><br class="gmail_msg">
> To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com" class="gmail_msg" target="_blank">rdo-list-unsubscribe@redhat.com</a><br class="gmail_msg">
</blockquote></div></div>