You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an RFE to allow users to request a future major OS (e.g. RHEL8/RHEL9/etc) when they submit a future request. This would first be captured in our landing codebase as an optional question/checkbox and appear in JIRA.
The QUADS-related feature would be a cloud-level object attribute and corresponding optional argparse like --os VALUE which saves this at the cloud level prior to allocation when a new assignment is defined, ahead of scheduling and subsequent future allocation.
During M&R phase instead of honoring the default OS label in /opt/quads/conf/quads.yml this will use the cloud attribute for OS if defined.
quads --define-cloud cloud05 --os RHEL9
This attribute should be wiped clean when that cloud environment is redefined with --force similar to how --vlan or --nowipe or --qinq works.
It might also make sense to consider an additional argparse that lists the available operating system targets that queries Foreman via our Foreman library to get an actionable equivalent of hammer os list e.g. quads --os-list
The text was updated successfully, but these errors were encountered:
This is an RFE to allow users to request a future major OS (e.g. RHEL8/RHEL9/etc) when they submit a future request. This would first be captured in our landing codebase as an optional question/checkbox and appear in JIRA.
The QUADS-related feature would be a cloud-level object attribute and corresponding optional argparse like
--os VALUE
which saves this at the cloud level prior to allocation when a new assignment is defined, ahead of scheduling and subsequent future allocation.During M&R phase instead of honoring the default OS label in
/opt/quads/conf/quads.yml
this will use the cloud attribute for OS if defined.quads --define-cloud cloud05 --os RHEL9
This attribute should be wiped clean when that cloud environment is redefined with
--force
similar to how--vlan
or--nowipe
or--qinq
works.It might also make sense to consider an additional argparse that lists the available operating system targets that queries Foreman via our Foreman library to get an actionable equivalent of
hammer os list
e.g.quads --os-list
The text was updated successfully, but these errors were encountered: