<div dir="ltr">Samuel,<br><br><div>VXLAN was moved to 7.0, as you noted it won't make 6.1. Mirantis has identified this as a high priority for 7.0 so it should get more attention this time. However any assistance in CR / Testing is always appreciated.</div><br><div class="gmail_quote"><div dir="ltr">On Thu, May 28, 2015 at 1:38 PM Samuel Bartel <<a href="mailto:samuel.bartel.pro@gmail.com">samuel.bartel.pro@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi Sean,<br><br></div>I understand and share you point of view. The best and cleaner solution would be to have the vxlan support out of the box. Unfortunatly it is not the case for 6.0 and I doubt this feature can be available before HCF for 6.1 (planned in the next upcoming days).<br></div><div> That's why in my initial message I asked if help is needed to ship this feature in 7.0<br></div><div><br></div>Having a vxlan plugin is a workaround, an ugly one, but the only workaround which make the job in 6.0 and 6.1.<br></div>My actual vxlan plugin modify ml2 neutron plugin configuration in order to switch segmentation type to vxlan and restart neutron services or neurton crm ressources. The only issue, I have for the moment is to recreate net04 network and corresponding subnet as you can't redefine an already defined resource in puppet.</div></div></blockquote><div><br></div><div>The plugin tasks run as separate puppet jobs so they are not bound by this restriction. Going forward with granular tasks, this will only be a problem within the specific task.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div>About the fact to choose GRE and having vxlan. it will be the same with contrail, nuage cinder netapp, nfs nova nfs glance plugins for example. In the create env form you choose a configuration. But you can choose in settings tab by activating a particular plugin to override initial network or storage configuration. In every case, It will be done on purpose. <br><br>--<br>
Regards,<br>
Samuel Bartel,<br>
IRC #samuelbartel<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-05-28 21:42 GMT+02:00 Sean M. Collins <span dir="ltr"><<a href="mailto:sean@coreitpro.com" target="_blank">sean@coreitpro.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div><div class="gmail_quote">On May 28, 2015 2:51:56 PM EDT, Andrey Danin <<a href="mailto:adanin@mirantis.com" target="_blank">adanin@mirantis.com</a>> wrote:<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div>Hi, Sean,<br><br></div>A plugin cannot modify Fuel UI but it actually can change a segmentation type after deployment. On UI it's still GRE but in fact it will be VxLAN. I know, it's ugly, but should work.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 28, 2015 at 7:47 PM, Sean M. Collins <span dir="ltr"><<a href="mailto:sean@coreitpro.com" target="_blank">sean@coreitpro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">VxLAN support cannot be made as a plugin because plugins cannot modify<br>
the initial networking wizard (based on conversations I've had in<br>
#fuel-dev) where the choices between Neutron VLAN, Neutron GRE, and<br>
nova-network are shown to the user.<br>
<br>
I am currently working on this blueprint and have a WIP patch for<br>
fuel-web. Please contact me if you want to help contribute to the work.<br>
<span><font color="#888888"><br>
--<br>
Sean M. Collins<br>
</font></span><div><div><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"></div></blockquote></div><br clear="all"></div></div>I don't think that's a good way to go about it, we'd be giving someone a surprise if they actually wanted to deploy GRE only to discover it deployed VXLAN.<span><font color="#888888"><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</font></span></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div>