<div dir="ltr">>- If you configure multiple type drivers, the first one will always be used, subject to resource availability. E.g. with 'vlan,vxlan', you would only start using VXLAN if all 4094 VLANs were already in us.<div><br></div><div>Not quite. It will only use a type driver automatically if it's in 'tenant_network_types'. You can have all the type drivers you want configured in 'type_drivers' and they will only be available to admins who manually specify the type in a network creation request.</div><div><br></div><div>So if you wanted to allow the creation of new networks and set them to a specific type while leaving the old networks untouched, you would just remove 'flat' from the 'tenant_network_types' option.</div><div><br></div><div><br></div><div>>- One issue that I suspect to be lurking is: what if the L3 plugin/agent that you need for a port - e.g. to map a floating IP onto it - depends on the mechanism driver that is used to bind that port?</div><div><br></div><div>The reference L3 plugin doesn't have a problem with this because it's not the L3 agent's responsibility to do L2 wiring for its ports. It just creates the ports and lets the L2 agent (or other mech driver) deal with wiring the VIFs.</div><div><br></div><div><br></div><div>It's not clear in the original email, but if the original flat networks are not available to the new compute nodes, you will encounter issues if you try to boot a VM onto one of the flat networks and it gets scheduled to a new compute node. It will result in a binding failure (assuming the vendor ML2 driver was written correctly).</div><div><br></div><div>Currently, Nova scheduling doesn't account for networks that aren't available to every compute node in the datacenter. So if the intention is to have the flat network available to the old compute nodes, and then a different network available to the new compute nodes, it's not really going to work.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 1, 2016 at 5:35 AM, Neil Jerram <span dir="ltr"><<a href="mailto:neil@tigera.io" target="_blank">neil@tigera.io</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto" lang="en-GB" style="background-color:rgb(255,255,255);line-height:initial"> <div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)">In principle... In the fully general case I think there are issues lurking, so it would indeed be interesting to hear about real experience from people who have done this. </div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)"><br></div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)">FWIW here's what I think I understand about mixed ML2 configurations:</div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)"><br></div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)">- We're talking about 'type' drivers and 'mechanism' drivers. Type drivers are about how instance data is transported between compute hosts. Mechanism drivers are about what happens on each compute host to connect instance data into that ('type') system.</div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)"><br></div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)">- If you configure multiple type drivers, the first one will always be used, subject to resource availability. E.g. with 'vlan,vxlan', you would only start using VXLAN if all 4094 VLANs were already in us.</div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)"><br></div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)">- OTOH if you configure multiple mechanism drivers, they will be asked in turn if they want to handle connecting up (aka binding) each new Neutron port. So different mechanism drivers can in principle handle different kinds of port.</div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)"><br></div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)">- One issue that I suspect to be lurking is: what if the L3 plugin/agent that you need for a port - e.g. to map a floating IP onto it - depends on the mechanism driver that is used to bind that port?</div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)"><br></div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)">I hope those points are useful to start discussing this interesting topic further. </div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)"><br></div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)"> Neil </div><div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)"><br></div> <div style="width:100%;font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)"><br></div> <div style="font-size:initial;font-family:Calibri,'Slate Pro',sans-serif,sans-serif;color:rgb(31,73,125);text-align:initial;background-color:rgb(255,255,255)"></div> <table width="100%" style="background-color:white;border-spacing:0px"> <tbody><tr><td colspan="2" style="font-size:initial;text-align:initial;background-color:rgb(255,255,255)"> <div style="border-style:solid none none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3pt 0in 0in;font-family:Tahoma,'BB Alpha Sans','Slate Pro';font-size:10pt"> <div><b>From: </b>Remo Mattei</div><div><b>Sent: </b>Tuesday, 1 November 2016 06:09</div><div><b>To: </b>Chris</div><div><b>Cc: </b><a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a>; Soputhi Sea</div><div><b>Subject: </b>Re: [Openstack] Mixed ml2 drivers in single Openstack setup</div></div></td></tr></tbody></table><div><div class="h5"><div style="border-style:solid none none;border-top-color:rgb(186,188,209);border-top-width:1pt;font-size:initial;text-align:initial;background-color:rgb(255,255,255)"></div><br><div id="m_-7080103415799656410_originalContent"><div><div style="direction:inherit">You can with ml2 mix plugins. You will have to look at the options but it is designed for that. </div><br>Sent from my iPad</div><div><br>On Oct 31, 2016, at 9:08 PM, Chris <<a href="mailto:contact@progbau.de" target="_blank">contact@progbau.de</a>> wrote:<br><br></div><blockquote type="cite"><div><div class="m_-7080103415799656410WordSection1"><p class="MsoNormal">Hello,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">We currently use the flat ml2 driver in our Openstack setup (around 500 nodes). <u></u><u></u></p><p class="MsoNormal">We now want to change to a network vendor specific ml2 driver. So the legacy compute nodes will use the flat network and compute nodes added in the future will use the network based on the new ml2 vendor plugin.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Question is it possible to mix two network setups like described above? We don’t use regions could this be a possible solution?<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Any help and answer appreciated.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Cheers<u></u><u></u></p><p class="MsoNormal">Chris<u></u><u></u></p></div>
!DSPAM:1,<wbr>581818fd210478584850555!
</div></blockquote><blockquote type="cite"><div><span>______________________________<wbr>_________________</span><br><span>Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a></span><br><span>Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a></span><br><span>Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a></span><br><span></span><br><span></span><br><span>!DSPAM:1,<wbr>581818fd210478584850555!</span><br></div></blockquote><br></div></div></div></div>
<br>______________________________<wbr>_________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
<br></blockquote></div><br></div>