-
Notifications
You must be signed in to change notification settings - Fork 29
Add BMC feature to foreman-proxy #484
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -44,6 +44,17 @@ variables: | |
| type: AbsolutePath | ||
| parameter: --certificate-server-ca-certificate | ||
| persist: false | ||
| foreman_proxy_bmc_default_provider: | ||
| parameter: --bmc-default-provider | ||
| help: Default BMC provider. | ||
| choices: | ||
| - freeipmi | ||
| - ipmitool | ||
| - redfish | ||
|
Comment on lines
+47
to
+53
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. While the parameter is called "default provider", the overall behavior is a bit different. The smart proxy code takes the provider from the request, and falls back to the default if unset (honoring the "default" definition): But then Foreman comes (who is the only consumer of this API) and always sets the provider unless the selected provider in Foreman is "IPMI": Which basically makes the setting "used IPMI implementation" (as one can't pick one in Foreman), not "fallback provider". To add insult to injury, everyone disagrees what a provider is. Foreman defines IPMI, Redfish and SSH, but the Proxy knows about freeipmi, ipmitool, redfish, shell and ssh 🤯 I don't think we can (or even should) fix all of that mess here and now, but maybe calling this PS: I couldn't find any users of the "Shell" provider, which is basically giving power control over the machine running the smart proxy. First I thought that'd be used in Discovery, but there we have an own implementation. It was added in https://projects.theforeman.org/issues/2387 but the explanation is rather… slim
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
In this case of user selected IPMI in foreman UI, the smart proxy does not get any bmc_provider in request and falls back to
Yes and also with ssh provider, i am not sure if its supported as provider by foreman, our doc does not say that and even i can't see any ssh key deployed at https://github.com/theforeman/puppet-foreman_proxy/blob/master/manifests/init.pp#L401 path |
||
| foreman_proxy_bmc_redfish_verify_ssl: | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we expose the "foreman_proxy" part to the user? Or should this be
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i think it should be |
||
| parameter: --bmc-redfish-verify-ssl | ||
| help: Verify SSL certificates for Redfish BMC connections. | ||
| type: Boolean | ||
|
|
||
| constraints: | ||
| required_together: | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| --- | ||
| :enabled: {{ feature_enabled }} | ||
| :bmc_default_provider: {{ foreman_proxy_bmc_default_provider }} | ||
|
|
||
| {% if foreman_proxy_bmc_default_provider == 'redfish' %} | ||
| :redfish_verify_ssl: {{ foreman_proxy_bmc_redfish_verify_ssl }} | ||
| {% endif %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the bmc.yaml.example are more providers: