multi-l3 NetworkManager needs to assign nodes via network_id assignment instead of cluster network name
Bug #1272145 reported by
Andrew Woodward
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.
Changed in fuel: | |
milestone: | none → 4.1 |
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 |
Changed in fuel: | |
milestone: | 5.0 → 5.1 |
To post a comment you must log in.
A feature, not a bug. Superceded by: /blueprints. launchpad. net/fuel/ +spec/multiple- cluster- networks
https:/