<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Cambria",serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">We do support Neutron for vCenter, but – as I mentioned a few months ago – we do not yet have a fully vetted way to deploy the multi-hypervisor use case with both KVM/QEMU and vCenter. This depends on our ability to select multiple networking options and align them to the correct hypervisors.</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">Per a conversation with Andrian Noga and his team yesterday, they are finishing work on the component registry [1] which will enable the multi-hypervisor, multi-network use case. This work is being completed now.</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">My recommendation remains that we should avoid deprecating nova-network until we have at least tested the basic multi-hypervisor use case with the new functionality. Can we remove nova-network after FF as a High priority bug?</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">[1] <a href="https://review.openstack.org/#/c/229306/">https://review.openstack.org/#/c/229306/</a></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Mike Scherbakov [mailto:<a href="mailto:mscherbakov@mirantis.com">mscherbakov@mirantis.com</a>]</span></p><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Sent:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Tuesday, December 01, 2015 1:37 AM<br><b>To:</b> OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><b>Subject:</b> Re: [openstack-dev] [Fuel] Remove nova-network as a deployment option in Fuel?</span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">Aleksey, can you clarify it? Why it can't be deployed? According to what I see at our fakeUI install [1], wizard allows to choose nova-network only in case if you choose vcenter.</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Do we support Neutron for vCenter already? If so - we could safely remove nova-network altogether.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">[1] <a href="http://demo.fuel-infra.org:8000/">http://demo.fuel-infra.org:8000/</a></p></div></div><p class="MsoNormal"> </p><div><div><p class="MsoNormal">On Mon, Nov 30, 2015 at 4:27 AM Aleksey Kasatkin <<a href="mailto:akasatkin@mirantis.com">akasatkin@mirantis.com</a>> wrote:</p></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><div><p class="MsoNormal">This remains unclear.</p></div><p class="MsoNormal" style="margin-bottom:12.0pt">Now, for 8.0, the Environment with Nova-Network can be created but cannot be deployed (and its creation is tested in UI integration tests).<br>AFAIC, we should either remove the ability of creation of environments with Nova-Network in 8.0 or return it back into working state.</p></div><div><p class="MsoNormal"><br clear="all"></p><div><div><div><p class="MsoNormal" style="margin-bottom:12.0pt">Aleksey Kasatkin </p></div></div></div></div><div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Fri, Oct 23, 2015 at 3:42 PM, Sheena Gregson <<a href="mailto:sgregson@mirantis.com" target="_blank">sgregson@mirantis.com</a>> wrote:</p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">As a reminder: there are no individual networking options that can be used with both vCenter and KVM/QEMU hypervisors once we deprecate nova-network.</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">The code for vCenter as a stand-alone deployment may be there, but the code for the component registry (<a href="https://blueprints.launchpad.net/fuel/+spec/component-registry" target="_blank">https://blueprints.launchpad.net/fuel/+spec/component-registry</a>) is still not complete. The component registry is required for a multi-HV environment, because it provides compatibility information for Networking and HVs. In theory, landing this feature will enable us to configure DVS + vCenter and Neutron with GRE/VxLAN + KVM/QEMU in the same environment.</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">While Andriy Popyvich has made considerable progress on this story, I personally feel very strongly against deprecating nova-network until we have confirmed that we can support <i>all current use cases</i> with the available code base.</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">Are we willing to lose the multi-HV functionality if something prevents the component registry work from landing in its entirety before the next release?</span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Sergii Golovatiuk [mailto:<a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@mirantis.com</a>] <br><b>Sent:</b> Friday, October 23, 2015 6:30 AM<br><b>To:</b> OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br><b>Subject:</b> Re: [openstack-dev] [Fuel] Remove nova-network as a deployment option in Fuel?</span></p><div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p><div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hi,</p></div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> </p></div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">As far as I know neutron code for VCenter is ready. Guys are still testing it. Keep patience... There will be announce soon.</p></div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br clear="all"></p><div><div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--<br>Best regards,<br>Sergii Golovatiuk,<br>Skype #golserge<br>IRC #holser</p></div></div></div></div></div></div></div></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><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></p></blockquote></div><p class="MsoNormal"> </p></div><p class="MsoNormal">__________________________________________________________________________<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></p></blockquote></div><div><p class="MsoNormal">-- </p></div><div><p class="MsoNormal">Mike Scherbakov<br>#mihgen</p></div></div></body></html>