-
Notifications
You must be signed in to change notification settings - Fork 40
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
Sync upstream patches down to openshift #110
Sync upstream patches down to openshift #110
Conversation
/lgtm |
/retest Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/hold |
192a6fb
to
070157d
Compare
Removing a forgotten mdns configuration parameter that might interfere if mdns is disabled.
[conductor]bootloader is expecting either a glance image ID or a URL, set it to the httpd server and copy the esp image in there on startup.
Currently, log files is disabled by metal3-io#46. This PR aims to remove this outdated infomation from README.md Signed-off-by: Kim Bao Long <longkb@vn.fujitsu.com>
The bootloader was copied to the html folder in runironic-conductor while some other scripts are used to start ironic. Moving the copy to runhttpd as the file is served by httpd.
It was missing the port, always going to port 80 when httpd listens on 6180 in BMO deployments
Users may have set some ironic options using env variables. Log them to that its more obvious that they have been set.
Without this configuration, the ipmitool timeout is 1 second. This is too short for vbmc. This commit uses the ipmitool retry feature and extends the timeout
Using the default entrypoint, which runs both the ironic-api and ironic-conductor processes in the same container, the container should exit immediately if either of those processes ends.
This reverts commit f95983f. This is no longer needed as we are about to being in the jinja changes from upstream.
This centralizes the cryptic configuration done in multiple files. In addition, it configures json_rpc to be authenticated when API and conductor are running in the same container and HTTP_BASIC_HTPASSWD is set. API and json_rpc would accept the same credentials. This is to prevent other processes in the same host to access the RPC interface over localhost.
When running both API and Conductor in the same container, we'll generate the username and password if not given by the user through the ironic-rpc auth config file.
This commit allows the user to start Ironic using TLS on all endpoints, by providing the following files : - /certs/ironic/tls.crt - /certs/ironic/tls.key - /certs/ca/ironic/tls.crt - /certs/ironic-inspector/tls.crt - /certs/ca/ironic-inspector/tls.crt If something is not provided,it will default to HTTP instead.
070157d
to
67de067
Compare
/unhold |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: derekhiggins, elfosardo The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Use generic python-chardet
This includes most of the upstream patches to the ironic image, with the exception of