<div dir="ltr">Hi Gary,<div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks for sending this out, comments inline.<br><br><div class="gmail_quote">On 29 June 2014 00:15, Gary Kotton <span dir="ltr"><<a href="mailto:gkotton@vmware.com" target="_blank">gkotton@vmware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
Hi,</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
At the moment there are a number of different BP’s that are proposed to enable different VMware network management solutions. The following specs are in review:</div>
<ol>
<li style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<span>VMware</span><span> NSX</span><span>-</span><span>vSphere plugin: <a href="https://review.openstack.org/102720" target="_blank">https://review.openstack.org/102720</a></span></li><li><span><font face="Calibri,sans-serif"><span>Neutron</span><span> mechanism driver
</span><span>for</span><span> </span><span>VMWare</span><span> vCenter DVS network creation</span>:</font></span><a href="https://review.openstack.org/#/c/101124" target="_blank">https://review.openstack.org/#/c/101124</a>/</li>
<li style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<span>VMware</span><span> dvSwitch</span><span>/</span><span>vSphere API support
</span><span>for</span><span> </span><span>Neutron</span><span> ML2: <a href="https://review.openstack.org/#/c/100810" target="_blank">https://review.openstack.org/#/c/100810</a>/</span></li></ol>
<div><span style="font-family:Calibri,sans-serif">In addition to this there is also talk about HP proposing some for of VMware network management.</span></div></div></blockquote><div><br></div><div>I believe this is blueprint [1]. This was proposed a while ago, but now it needs to go through the new BP review process.<br>
</div><div><br></div><div>[1] - <a href="https://blueprints.launchpad.net/neutron/+spec/ovsvapp-esxi-vxlan" target="_blank">https://blueprints.launchpad.net/neutron/+spec/ovsvapp-esxi-vxlan</a><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"><div><span style="font-family:Calibri,sans-serif"><br>
</span></div>
<div><font face="Calibri,sans-serif">Each of the above has specific use case and will enable existing vSphere users to adopt and make use of Neutron.</font></div>
<div><span style="font-family:Calibri,sans-serif"><br>
</span></div>
<div><font face="Calibri,sans-serif">Items #2 and #3 offer a use case where the user is able to leverage and manage VMware DVS networks. This support will have the following limitations:</font></div>
<ul>
<li><font face="Calibri,sans-serif">Only VLANs are supported (there is no VXLAN support)</font></li><li><font face="Calibri,sans-serif">No security groups</font></li><li><font face="Calibri,sans-serif">#3 – the spec indicates that it will make use of pyvmomi (</font><a href="https://github.com/vmware/pyvmomi" target="_blank">https://github.com/vmware/pyvmomi</a>). There are a number of disclaimers here:
<ul>
<li>This is currently blocked regarding the integration into the requirements project (<a href="https://review.openstack.org/#/c/69964" target="_blank">https://review.openstack.org/#/c/69964</a>/)</li><li>The idea was to have oslo.vmware leverage this in the future (<a href="https://github.com/openstack/oslo.vmware" target="_blank">https://github.com/openstack/oslo.vmware</a>)</li>
</ul>
</li></ul>
<div><font face="Calibri,sans-serif">Item #1 will offer support for all of the existing Neutron API’s and there functionality. This solution will require a additional component called NSX (</font><a href="https://www.vmware.com/support/pubs/nsx_pubs.html" style="font-family:arial,helvetica,sans-serif;font-size:13px" target="_blank">https://www.vmware.com/support/pubs/nsx_pubs.html</a>).</div>
<div><br></div></div></blockquote><div><br></div><div><div>It's great to see this breakdown, it's very useful in order to identify the potential gaps and overlaps amongst the various efforts around ESX and Neutron. This will also ensure a path towards a coherent code contribution.</div>
<div><br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>
</div>
<div>It would be great if we could all align our efforts and have some clear development items for the community. In order to do this I’d like suggest that we meet to sync and discuss all efforts. Please let me know if the following sounds ok for an initial
meeting to discuss how we can move forwards:</div>
<div> - Tuesday 15:00 UTC</div>
<div> - IRC channel #openstack-vmware</div></div></blockquote><div><br></div><div>I am available to join.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div><br>
</div>
<div>We can discuss the following:</div>
<ol>
<li>Different proposals</li><li>Combining efforts</li><li>Setting a formal time for meetings and follow ups</li></ol>
<div>Looking forwards to working on this stuff with the community and providing a gateway to using Neutron and further enabling the adaption of OpenStack.</div></div></blockquote><div><br></div><div><div>I think code contribution is only one aspect of this story; my other concern is that from a usability standpoint we would need to provide a clear framework for users to understand what these solutions can do for them and which one to choose.</div>
<div><br></div><div>Going forward I think it would be useful if we produced an overarching blueprint that outlines all the ESX options being proposed for OpenStack Networking (and the existing ones, like NSX - formerly known as NVP, or nova-network), their benefits and drawbacks, their technical dependencies, system requirements, API supported etc. so that a user can make an informed decision when looking at ESX deployments in OpenStack.</div>
</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div><br>
</div>
<div>Thanks</div><span class=""><font color="#888888">
<div>Gary</div>
</font></span></div>
<br></blockquote><div> </div><div>Cheers,</div><div>Armando</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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></div></div>