+++ This bug was initially created as a clone of Bug #1122550 +++
Description of problem:
For OSP deployment Customers require ability to define infrastructure network(s) per node type on top of individual NICs, bonded network, or bridged networks.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from arkady kanevsky on 2014-07-23 09:35:11 EDT ---
See joint Dell/RedHat RA for examples of network requirements
The RHEL-OSP installer currently runs only on RHEL 6. Changes made on RHEL 6 will apply to RHEL-OSP deployments on both RHEL 6 and RHEL 7. Closing this bug as a duplicate since we only need to track it in 1 place.
*** This bug has been marked as a duplicate of bug 1122550 ***
This bug is specific to tracking the network assignment enhancements coming to Staypuft for A1 async release. The ability to do this on top of bonded network interfaces will be tracked in a subsequent delivery/cloned bug.
Using untagged VLAN interfaces should be transparent to Staypuft and should just be a validation effort
If you want to define a VLAN interface you don't change existing physical device but you create a new one that is VLAN and is attached to physical device. Easier is to assign the VLAN subnet to physical device in staypuft wizard (which creates the VLAN interface for you) and then go to host form and edit it (override VLAN tag on VLAN device)
Tested using subent with VLAN and attached it to interface
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.