-
Notifications
You must be signed in to change notification settings - Fork 23
Add Cephadm version conditon for Rocky multi-node #824
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
Conversation
@@ -2,6 +2,12 @@ | |||
############################################################################### | |||
# Cephadm deployment configuration. | |||
|
|||
# Ceph release name. | |||
cephadm_ceph_release: "{{ 'quincy' if (ansible_facts['distribution_release'] == 'jammy') or (ansible_facts['distribution_release'] == '9') else 'pacific' }}" |
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.
Should it go in the main etc/kayobe/cephadm.yml
file?
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 say the reasoning on not having a surprise upgrade at a client site still stands: #480
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.
Sure, not saying we should change the default to quincy, but if pacific doesn't work on RL9 then we could conditionally enable it as we are here?
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 moved these conditions to etc/kayobe/cephadm.yml
@@ -0,0 +1 @@ | |||
dnf_custom_repos: "{{ stackhpc_dnf_repos }}" |
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.
dnf_custom_repos: "{{ stackhpc_dnf_repos }}" | |
--- | |
dnf_custom_repos: "{{ stackhpc_dnf_repos }}" | |
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.
Or perhaps copy etc/kayobe/inventory/group_vars/overcloud/stackhpc-dnf-repos
to etc/kayobe/environments/ci-multinode/inventory/group_vars/all/stackhpc-dnf-repos
This would also include infra-vms but I don't think that's a bad thing
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 not sure that we want this on the seed-hypervisor, as this would be less representative of a customer deployment.
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.
For a typical deployment there is a chicken and egg situation here because pulp runs on the seed. I agree that multinodes should reflect the standard config.
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.
What are we going to do here then? Why was this config necessary?
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.
This config was necessary to ensure RL 9.3 packages to be installed on seed when performing kayobe seed host configure
Closing this PR as this change is included on PR #828 |
Add condition of checking Rocky Linux release number on conditional variables
cephadm_ceph_release
andcephadm_image_tag
The upstream Cephadm Pacific repository is no more available and this change prevents targeting the repository when building Rocky Linux 9 multi-node environment.
The change was made at
etc/kayobe/environments/ci-multinode/cephadm.yml
to override only when environment is set to be ci-multinode