CP-48027: Corosync upgrade add cluster_stack_version datamodel change
#5567
Conversation
|
Something is wrong here? 5000+ files changed? You might want to split automated tests into a different commit so we can ignore them. |
There are autogenerated test files due to the interface change. I could do a separate commit, but that would mean some of the commits will fail the test though. But it looks like even that would not make the CI happy.... |
Vincent-lau
force-pushed
the
private/shul2/corosync3-basic
branch
from
ff5a99f
to
135a225
Compare
|
The review dog thing failing is really not good :/ I'll try to make time to reduce complexity in CI so it doesn't fail because of a valid change |
Vincent-lau
force-pushed
the
private/shul2/corosync3-basic
branch
2 times, most recently
from
67ff66f
to
f1c0c2b
Compare
|
Can the conflicts be solved first? |
Vincent-lau
force-pushed
the
private/shul2/corosync3-basic
branch
2 times, most recently
from
2ff971f
to
99d77a9
Compare
Vincent-lau
force-pushed
the
private/shul2/corosync3-basic
branch
from
99d77a9
to
cbbc21c
Compare
Vincent-lau
force-pushed
the
private/shul2/corosync3-basic
branch
from
d402f1c
to
d00c393
Compare
Add a new field `cluster_stack_version` to the cluster datamodel to track the version of corosync currently in use. This version will always be set to 3. Also add logic to switch corosync binary and associated library versions when a cluster is created, if needed. Signed-off-by: Vincent Liu <shuntian.liu2@cloud.com>
Signed-off-by: Vincent Liu <shuntian.liu2@cloud.com>
This is purely for testing purpose. Normal user is not allowed to create a corosync2 cluster. Signed-off-by: Vincent Liu <shuntian.liu2@cloud.com>
Signed-off-by: Vincent Liu <shuntian.liu2@cloud.com>
|
hold off merging as there are non-trivial changes after the review. I would like to do some xenrt testing before merging it. |
This is the core part of the corosync upgrade, mainly deal with the
cluster_stack_versiondatamodel field, and the switching logic for corosync binary and libraries.The multi-link support will be done in a separte PR.
Best reviewed by commit