Open Stack

We restricted this because allowing nova-network to be used as an underlay
for all possible combinations added QA time and effort to supporting a soon
to be deprecated option.



As nova-network is being deprecated upstream and will relatedly be
deprecated in Fuel – AFAIK, there is a goal to deprecate nova-network
entirely in Fuel 8.0 -  we should reduce the number of customers who are
even able to use this as the networking underlay to only reflect customers
who absolutely require it.



There is not sufficient value in supporting nova-network for other use
cases.



*From:* Mike Scherbakov [mailto:mscherbakov at mirantis.com]
*Sent:* Wednesday, July 29, 2015 12:47 PM
*To:* OpenStack Development Mailing List (not for usage questions) <
openstack-dev at lists.openstack.org>
*Subject:* [openstack-dev] [Fuel] Restrictions in Fuel API: nova-network



Folks,

why do we even want to introduce restrictions?



Please see

https://bugs.launchpad.net/fuel/+bug/1470488

about locking nova-network.



We already suffer from locked Settings tab in our API.



Instead, we just need to introduce a warning, that this option is
deprecated and it's on risk of a user to use it. We want Fuel to be
flexible, and not too prescriptive.



Thanks,

-- 

Mike Scherbakov
#mihgen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150729/1c6b0061/attachment.html>