Bug 1127405

Summary: RFE: Need an option to exclude network IP's when creating Nova networks
Product: Red Hat OpenStack Reporter: Mike Burns <mburns>
Component: openstack-novaAssignee: Russell Bryant <rbryant>
Status: CLOSED ERRATA QA Contact: Ofer Blaut <oblaut>
Severity: low Docs Contact:
Priority: medium    
Version: 5.0 (RHEL 7)CC: arkady_kanevsky, beagles, cdevine, jdonohue, John_walsh, kurt_hey, mburns, ndipanov, oblaut, ohochman, randy_perryman, rhos-integ, rhos-maint, sgordon, slong, sreichar, sseago, yeylon
Target Milestone: Upstream M3Keywords: FutureFeature, OtherQA
Target Release: 6.0 (Juno)   
Hardware: x86_64   
OS: Linux   
URL: https://blueprints.launchpad.net/nova/+spec/better-support-for-multiple-networks
Whiteboard: upstream_milestone_juno-3 upstream_definition_approved upstream_status_implemented
Fixed In Version: openstack-nova-2014.2.1-11.el7ost Doc Type: Enhancement
Doc Text:
When using nova-network with multiple networks, it is now possible to set the MTU, enable or disable DHCP, set the DHCP server, and indicate whether the network shares addresses with other networks. Previously, it was not possible to set these parameters on a per-network basis, making it more difficult to use nova-network with multiple networks. With this update, administrators now have more flexibility with settings when using multiple networks with nova-network.
Story Points: ---
Clone Of: 1119382 Environment:
Last Closed: 2015-02-09 14:58:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1119382    
Bug Blocks: 1093544, 1108193, 1119945, 1127404    

Comment 1 Stephen Gordon 2014-08-13 15:54:14 UTC
*** Bug 1098855 has been marked as a duplicate of this bug. ***

Comment 3 arkady kanevsky 2014-09-03 13:25:10 UTC
What is the plan for backporting to OSP5 and exposing it thru Installer UI?

Comment 8 errata-xmlrpc 2015-02-09 14:58:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-0152.html