Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFE] Allow Tenants to Choose Future OS Platform for Provisioning #474

Open
sadsfae opened this issue May 2, 2024 · 1 comment
Open

Comments

@sadsfae
Copy link
Member

sadsfae commented May 2, 2024

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

@grafuls
Copy link
Contributor

grafuls commented May 6, 2024

@sadsfae
Is this a duplicate of #318 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants