My customer wants subnets to have parameters the same way that hosts in Satellite 6 have parameters.
For example, in the Foreman GUI:
Hosts > All hosts > $host > YAML
Displays "classes" for Puppet as well as "parameters" and those parameters can be modified by using the GUI to navigate:
Hosts > All hosts > $host > Edit > Parameters > Host Parameters
He would like to be able to use the Satellite GUI similarly to navigate:
Infrastructure > Subnets > $subnet > Parameters
Though the "parameters tab is missing from subnets edit view" (from his perspective and thus this RFE).
His use-case is for the following to happen:
If a host's primary interface is assigned to a subnet, then the physical location information from that subnet is inherited by that host.
So he would use the new "subnet parameters" to store location information for that subnet and then any host would inherit that information.
Because he doesn't yet have this feature, his workaound is to store the location information in every host (which already supports parameters).
Is it possible for the host inheritance usecase described above to be addressed by what was proposed in the following upstream issue?
Connecting redmine issue http://projects.theforeman.org/issues/1464 from this bug
Per 6.3 planning, moving out non acked bugs to the backlog
Upstream bug assigned to ohadlevy
Upstream bug component is WebUI
This has been resolved upstream in http://projects.theforeman.org/issues/3582 which is in Foreman 1.12.
Moving to Post and aligning flags.
@ Satellite 6.3 All Snaps
This bug has been verified as a new Feature in Satellite 6.3
Following aspects of this Bug has been tested over the snaps from API, CLI and UI ends:
1. Subnet Parameter can be created, deleted, updated, read.
2. Subnet Parameters impacts on host
The numerous tests have been written to verify this bug and functionality.
These tests has been tested manually/automation over 6.3 snaps
Also some bugs were raised and they are tracked for tracker:
All the bugs in this trackers wrt this bug have been verified and fixed.
And hence changing the bug status to Verified.
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.