multi-l3 NetworkManager needs to assign nodes via network_id assignment instead of cluster network name

Bug #1272145 reported by Andrew Woodward
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Ryan Moe

Bug Description

NetworkManager needs to assign nodes via network_id assignment instead of cluster network name. This prevent's multiple networks from being able to be used.

Tags: multi-l3
Changed in fuel:
milestone: none → 4.1
Andrew Woodward (xarses)
summary: - NetworkManager needs to assign nodes via network_id assignment instead
- of cluster network name
+ multi-l3 NetworkManager needs to assign nodes via network_id assignment
+ instead of cluster network name
Changed in fuel:
milestone: 4.1 → 5.0
Ryan Moe (rmoe)
Changed in fuel:
milestone: 5.0 → 5.1
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :
Changed in fuel:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.