<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">I agree – I don’t think we can change the user’s ability to manage old releases. This work should be about preventing the selection of nova-network for new environments on 8.0 release and later – we should restrict this via all methods of interaction, including UI, CLI and API if possible.</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"> Oleg Gelbukh [mailto:<a href="mailto:ogelbukh@mirantis.com">ogelbukh@mirantis.com</a>] <br><b>Sent:</b> Tuesday, December 22, 2015 3:09 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] Removal of support for nova-network</span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">Sergii,</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Nailgun will still have data of clusters with old releases, should they be in the database backup. And it still has to be able to manage them.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">--</p></div><div><p class="MsoNormal">Best regards,</p></div><div><p class="MsoNormal">Oleg Gelbukh</p></div></div><div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Tue, Dec 22, 2015 at 11:58 AM, Sergii Golovatiuk <<a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@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><p class="MsoNormal">Hi,</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">There won't be upgrade to 8.0. User will be able to backup and load data to a new master node. nova-network has been deprecated for 2 releases so we can remove it. If we remove it we can remove tests from acceptance testing as well as from auto-tests so it should remove tech debt so will release our QA/CI resources to focus on other tests.</p></div><div><p class="MsoNormal"> </p></div></div><div><p class="MsoNormal"><br clear="all"></p><div><div><div><p class="MsoNormal">--<br>Best regards,<br>Sergii Golovatiuk,<br>Skype #golserge<br>IRC #holser</p></div></div></div><p class="MsoNormal"> </p><div><div><div><p class="MsoNormal">On Tue, Dec 22, 2015 at 12:28 AM, Evgeniy L <<a href="mailto:eli@mirantis.com" target="_blank">eli@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><p class="MsoNormal">Hi,</p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">We mustn't touch Nailgun's logic, otherwise after upgrade user won't be able</p></div><div><p class="MsoNormal">to manage her/his old nova Cluster. So lets just remove it from UI.</p></div><div><p class="MsoNormal">Also as far as I know we should provide a way to manage old clusters not</p></div><div><p class="MsoNormal">for a release, but for a couple of years.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Thanks,</p></div></div><div><div><div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Tue, Dec 22, 2015 at 10:40 AM, Igor Kalnitsky <<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@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"><p class="MsoNormal">I don't think it's a good idea to drop support of 7.0 nova-network<br>setup in 8.0. We should keep compatibility for at least one release.</p><div><div><p class="MsoNormal"><br>On Tue, Dec 22, 2015 at 9:15 AM, Aleksey Kasatkin<br><<a href="mailto:akasatkin@mirantis.com" target="_blank">akasatkin@mirantis.com</a>> wrote:<br>> Sergii,<br>><br>> We could remove it completely from nailgun if support for 7.0 and earlier is<br>> not required.<br>><br>><br>> Aleksey Kasatkin<br>><br>><br>> On Tue, Dec 22, 2015 at 3:27 AM, Sergii Golovatiuk<br>> <<a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@mirantis.com</a>> wrote:<br>>><br>>> Hi,<br>>><br>>> Finally we can deprecate nova-network ...<br>>> We should remove it from UI, nailgun logic and tests to have less<br>>> technical debt.<br>>><br>>> --<br>>> Best regards,<br>>> Sergii Golovatiuk,<br>>> Skype #golserge<br>>> IRC #holser<br>>><br>>> On Mon, Dec 21, 2015 at 5:01 PM, Sheena Gregson <<a href="mailto:sgregson@mirantis.com" target="_blank">sgregson@mirantis.com</a>><br>>> wrote:<br>>>><br>>>> Hey guys –<br>>>><br>>>><br>>>><br>>>> I know this has been a topic of a lot of discussion – Adrian informed me<br>>>> on Friday that QA has confirmed the multi-hypervisor use case has been<br>>>> tested successfully without nova-network, so we can finally deprecate it!<br>>>><br>>>><br>>>><br>>>> Users who want to deploy multiple hypervisors will need to use the Fuel<br>>>> DVS plugin (Neutron ML2 driver) to support their vCenter computes and the<br>>>> KVM/QEMU computes can use Neutron + GRE/VXLAN.<br>>>><br>>>><br>>>><br>>>> I’ve created a kind of “cover all the things” bug here:<br>>>> <a href="https://bugs.launchpad.net/fuel/+bug/1528407" target="_blank">https://bugs.launchpad.net/fuel/+bug/1528407</a>. Given the state of<br>>>> nova-network right now in Fuel, I have marked it as Critical.<br>>>><br>>>><br>>>><br>>>> Let’s start the conversation on here and make sure all the bases are<br>>>> covered – if additional bugs need to be logged or there’s administrative<br>>>> overhead, let me know and I’ll be happy to help out!<br>>>><br>>>><br>>>><br>>>> Sheena Gregson | Sr. Product Manager | Mirantis<br>>>><br>>>> p: <a href="tel:%2B1%20650%20646%203302" target="_blank">+1 650 646 3302</a> | e: <a href="mailto:sgregson@mirantis.com" target="_blank">sgregson@mirantis.com</a><br>>>><br>>>><br>>>><br>>>><br>>>><br>>>> __________________________________________________________________________<br>>>> OpenStack Development Mailing List (not for usage questions)<br>>>> Unsubscribe:<br>>>> <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>>><br>>><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>><br>><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><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></div></div></blockquote></div><p class="MsoNormal"> </p></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></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></div></body></html>