Support deploying multinodes on Leafcloud #45
Merged
+334
−243
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The StackHPC overcloud host image ships with small logical volumes that must be expanded after deployment.
- add-fqdn.yml: This functionality has been moved to the fix-networking.yml custom playbook in stackhpc-kayobe-config - fix-homedir-ownership.yml: This workaround should no longer be required due to fixes in the images. If the issues resurface it will be better to be made aware of it than hide it with a workaround. This playbook also had the job of waiting for the hosts to become reachable using wait_for_connection. This has been moved to grow-control-host.yml for the Ansible control host, and the fix-networking.yml custom playbook in stackhpc-kayobe-config.
These are no longer required since we only connect to the Ansible control host using Ansible in this repository.
This is less coupled to SMS lab.
This may be used for SSH access to the Ansible control host when no direct access to the multinode network is available.
This location is easier to find.
- Backup previous results to avoid mistaking them for new ones - Ignore docker logs check failure because it's racy - Check for failed-tests artifact and exit 1 if any tests fail
…l host This avoids problems such as "Too many authentication failures" when using SSH agent.
Previously the first deployment of a system with a Vault CA for internal TLS and os_capacity enabled would fail when deploying HAProxy. os_capacity deployment requires admin-openrc.sh to exist, but because of the use of -kt haproxy the post-deploy tasks that create it will be skipped. This change fixes the issue by skipping the os_capacity tag when deploying HAProxy.
seunghun1ee
previously approved these changes
Apr 11, 2024
Alex-Welsh
reviewed
Apr 11, 2024
Co-authored-by: Alex-Welsh <[email protected]>
Require users to name their clusters.
Alex-Welsh
approved these changes
Apr 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains various changes required to deploy a multinode cluster on Leafcloud. It also contains a number of other changes, fixes and reorgs.
Details are in individual commit messages.
This PR depends on stackhpc/stackhpc-kayobe-config#1021