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

Integrate 3.1.5 Discovery image kernel options #44

Closed
lzap opened this issue Oct 4, 2019 · 5 comments · Fixed by #2464
Closed

Integrate 3.1.5 Discovery image kernel options #44

lzap opened this issue Oct 4, 2019 · 5 comments · Fixed by #2464

Comments

@lzap
Copy link
Member

lzap commented Oct 4, 2019

Into provisioning guide from https://theforeman.org/plugins/foreman_discovery/15.0/index.html

@melcorr
Copy link
Member

melcorr commented Oct 8, 2019

This will require work before it can be integrated with the docs here.

If we're going to accept them into the improved doc set, they'll need a more robust definition that covers the "who, what, where, how and why" of each option.

It is missing context for a new user: where do you set this option? Can one or more of these options be set at the one time? If so, are there any known successful combinations for certain use cases?

Ideally we would write a procedure where we show users how to set up the Discovery image kernel, so that the user who references this list has also the steps they need to change it.

@lzap
Copy link
Member Author

lzap commented Oct 9, 2019

It definitely needs a rework, thus the issue created.

@melcorr
Copy link
Member

melcorr commented Oct 11, 2019

Foreman discovery image currently recognizes the following list of configuration options:

Where are these configuration options set?

@maximiliankolb
Copy link
Contributor

I've added the missing parameters: #2464

@ekohl ekohl linked a pull request Sep 25, 2023 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants