<div dir="ltr">We should continue to support nova-network for 7.0 and prior environments, so it won't be removed completely.  We should prevent users from creating new environments on Mitaka/8.0 versions and later which use nova-network.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 18, 2016 at 9:18 AM, Igor Kalnitsky <span dir="ltr"><<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Roman, Sheena,<br>
<br>
You meant to remove nova-network completely? Or only for new<br>
environments? Should we support nova-network for old (let's say, 7.0)<br>
clusters?<br>
<br>
Thanks,<br>
Igor<br>
<div class="HOEnZb"><div class="h5"><br>
On Fri, Jan 15, 2016 at 10:03 PM, Sheena Gregson <<a href="mailto:sgregson@mirantis.com">sgregson@mirantis.com</a>> wrote:<br>
> Adrian – can someone from the PI team please confirm what testing was<br>
> performed?<br>
><br>
><br>
><br>
> From: Roman Alekseenkov [mailto:<a href="mailto:ralekseenkov@mirantis.com">ralekseenkov@mirantis.com</a>]<br>
> Sent: Friday, January 15, 2016 11:30 AM<br>
><br>
><br>
> To: OpenStack Development Mailing List (not for usage questions)<br>
> <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
> Subject: Re: [openstack-dev] [Fuel] nova-network removal<br>
><br>
><br>
><br>
> I agree with Sheena. Sounds like removing support for nova-network would be<br>
> the best option, even though it's late.<br>
><br>
><br>
><br>
> However, I'd like us to think about the impact on vCenter integration.<br>
> vCenter+nova-network was fully supported before. Since we are now<br>
> recommending DVS or NSX backends, I'd like the team to explicitly confirm<br>
> that those configurations have been tested.<br>
><br>
><br>
><br>
> Thanks,<br>
><br>
> Roman<br>
><br>
><br>
><br>
> On Fri, Jan 15, 2016 at 6:43 AM, Sheena Gregson <<a href="mailto:sgregson@mirantis.com">sgregson@mirantis.com</a>><br>
> wrote:<br>
><br>
> Although we are very close to HCF, I see no option but to continue removing<br>
> nova-network as I understand it is not currently functional or well-tested<br>
> for the Mitaka release.  We must either remove it or test it, and we want to<br>
> remove it anyway so that seems like the better path.<br>
><br>
><br>
><br>
> Mike, what do you think?<br>
><br>
><br>
><br>
> From: Roman Prykhodchenko [mailto:<a href="mailto:me@romcheg.me">me@romcheg.me</a>]<br>
> Sent: Friday, January 15, 2016 8:04 AM<br>
> To: OpenStack Development Mailing List (not for usage questions)<br>
> <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
> Subject: Re: [openstack-dev] [Fuel] nova-network removal<br>
><br>
><br>
><br>
> I’d like to add that nova-network support was removed from python-fuelclient<br>
> in 8.0.<br>
><br>
><br>
><br>
> 14 січ. 2016 р. о 17:54 Vitaly Kramskikh <<a href="mailto:vkramskikh@mirantis.com">vkramskikh@mirantis.com</a>><br>
> написав(ла):<br>
><br>
><br>
><br>
> Folks,<br>
><br>
> We have a request on review which prohibits creating new envs with<br>
> nova-network: <a href="https://review.openstack.org/#/c/261229/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/261229/</a> We're 3 weeks away<br>
> from HCF, and I think this is too late for such a change. What do you think?<br>
> Should we proceed and remove nova-network support in 8.0, which is<br>
> deprecated since 7.0?<br>
><br>
><br>
> --<br>
><br>
> Vitaly Kramskikh,<br>
> Fuel UI Tech Lead,<br>
> Mirantis, Inc.<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><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" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><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" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" 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" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>