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] Standardize host naming convention #440

Open
grafuls opened this issue Jun 28, 2023 · 3 comments
Open

[RFE] Standardize host naming convention #440

grafuls opened this issue Jun 28, 2023 · 3 comments

Comments

@grafuls
Copy link
Contributor

grafuls commented Jun 28, 2023

Is your feature request related to a problem? Please describe.
In Quads core functionalities, the code heavily relies on the hosts naming convention that we utilize where the template is <rack>-h<u-location>-[<blade>-]<model>-<domain>. This is only mentioned on the docs once and it's not heavily enforced for Quads usage and could be error prone.

Describe the solution you'd like
Include additional optional arguments for --define-host cmd for --rack, --model, --uloc and --blade and have --hostname be optional if none of the other are passed, then have quads pick the domain from the config file and construct the hostname.
Additionally if we require enough metadata at host definition we can have Quads leverage the foreman.py library to automatically do the foreman host definition.

Describe alternatives you've considered
Make the --define-host input optionally (when no args passed) interactive. Display a prompt for each argument with a default value.

$ quads --define-host
Rack<f21>: f22
U-Location<01>:
Blade<000> :
Model<R640>: R650
Default Cloud<cloud01>: 
Type<Baremetal>:
...
@sadsfae
Copy link
Member

sadsfae commented Jun 28, 2023

Great suggestion +1

@sadsfae
Copy link
Member

sadsfae commented Jun 28, 2023

Can we have some logic that if none of those new params are defined then it just defaults to the old behavior? (which can also be accomplished via CNAME anyway in DNS so people have never needed to rename their servers). This way people wouldn't have to make DNS records if they didn't want to greenfield or rename their systems too if they didn't want to use those params.

@grafuls grafuls changed the title [RFE] Standarize hostnames naming convention [RFE] Standardize host naming convention Jun 28, 2023
@sadsfae
Copy link
Member

sadsfae commented Sep 13, 2023

I think this will be addressed in: #448

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

No branches or pull requests

2 participants