RFE: Network Isolation Should Allow Non-Standard Networks on Nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Wishlist
|
Dan Sneddon |
Bug Description
Currently TripleO network isolation assumes that certain networks will be on certain roles. These networks can be individually enabled/disabled, but it isn't possible to arbitrarily assign networks to roles. The Ceph OSD nodes, for instance, only have ports configured on the Control Plane, Storage, Storage Management, and Management networks. If one wanted to place a port from the Internal API network on the Ceph node, it would require customizing the Ceph Heat templates.
We should not be so prescriptive about which networks are on which nodes. If we just add all networks to all nodes, they will ordinarily be noop'd, and can be enabled for custom environments.
This work will mainly need to take place in the role templates for the overcloud nodes, so compute.yaml, ceph-storage.yaml, etc. and the Puppet equivalent role files. Since these networks would only be enabled in a custom environment, no changes to the existing NIC config templates are needed.
summary: |
- Network Isolation Should Allow Non-Standard Networks on Nodes + RFE: Network Isolation Should Allow Non-Standard Networks on Nodes |
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in tripleo: | |
milestone: | none → newton-1 |
Changed in tripleo: | |
status: | Fix Committed → Fix Released |
This doesn't appear to have been started, and it has no assignee, so I'm bumping to n2