-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add GitLab based Kayobe-Automation #1471
base: stackhpc/2024.1
Are you sure you want to change the base?
Conversation
This commit adds the required collections and roles for GitLab CI to the `etc/kayobe/ansible/requirements.yml` file. Note: this will need changing before merging but is required until the roles and collections been merged and released.
Includes steps for deploying GitLab runners, generating pipelines and deploying OpenBao for secret management.
e1e5994
to
9a301fb
Compare
8e675b7
to
ff8d471
Compare
Improve the docs based on feedback provided. [skip ci]
ff8d471
to
beaedd3
Compare
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.
I'm going through this deployment for a client at the moment and will add more comments as I go
1. Identify a suitable host for hosting the runners. | ||
Ideally an infra-vm would be deployed to allow for easily compartmentalising the runners from the rest of the environment. | ||
8 VCPUs and 16GB of RAM is recommended for the guest machine however this may need to be adjusted for larger deployments. | ||
Whether the host is in an infra-vm or not it will need access to the :code:`admin_network` or :code:`provision_oc_network`, :code:`public_network` and the :code:`pulp registry` on the seed. | ||
The steps will assume that an infra-vm will be used for the purpose of hosting the runners. |
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.
I'd personally be in favor of adding a default config to our base environment which has some standard settings for cpus, memory, disk, runner name etc. Maybe we could even pre-configure the network interfaces to some extent
GitLab Pipelines | ||
---------------- | ||
|
||
1. Edit :code:`${KAYOBE_CONFIG_PATH}/inventory/group_vars/gitlab-writer/writer.yml` in the base configuration making the appropriate changes to your deployments specific needs. See documentation for `stackhpc.kayobe_workflows.gitlab <https://github.com/stackhpc/ansible-collection-kayobe-workflows/tree/main/roles/gitlab>`__. |
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.
making the appropriate changes to your deployments specific needs
This is a bit vague. I think a lot of this can be given defaults here in SKC.
We should have a default writer.yml
with:
gitlab_output_directory: $KAYOBE_CONFIG_PATH/../../.gitlab/
gitlab_registry: "{{ pulp_url }}"
gitlab_openstack_release: "{{ openstack_release }}"
and then just tell people to set gitlab_kayobe_environments:
Co-authored-by: Tom Clark <[email protected]> Co-authored-by: Alex-Welsh <[email protected]>
43071a0
to
1ae7397
Compare
1ae7397
to
f3b4fde
Compare
d4d982a
to
4d76e84
Compare
Add support for GitLab based kayobe-automation complete with OpenBao for secret managment.