Bug 1299297

Summary: We need to support any isolated network on any overcloud node
Product: Red Hat OpenStack Reporter: Dan Sneddon <dsneddon>
Component: openstack-tripleo-heat-templatesAssignee: Dan Sneddon <dsneddon>
Status: CLOSED CURRENTRELEASE QA Contact: Amit Ugol <augol>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: mburns, nlevinki, rhel-osp-director-maint
Target Milestone: gaKeywords: TestOnly
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-28 13:51:46 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:

Description Dan Sneddon 2016-01-18 02:04:22 UTC 
Description of problem:
We need a more flexible architecture for assigning which networks are in use on which nodes. This will provide better support for custom networks and OpenDaylight.

Version-Release number of selected component (if applicable):
OSP 8 Beta


Actual results:
Right now we are very prescriptive in which networks can go on which nodes.

Expected results:
Using the network-environment.yaml, you should be able to specify which networks are on which nodes.

Additional info:
Upstream has already merged patches to make this possible.
Comment 2 Mike Burns 2016-04-07 21:03:37 UTC 
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Comment 3 Dan Sneddon 2016-04-07 21:08:06 UTC 
(In reply to Mike Burns from comment #2)
> This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

That is not correct. This feature was merged into T-H-T with this change: https://review.openstack.org/249533

And the changes were merged down to OSP prior to the release of 8. This still requires QE validation, but the dev work is done and merged.