-
Notifications
You must be signed in to change notification settings - Fork 34
StoragePool creation changes for new 2 Nodes + 1 Arbiter cluster #2154
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
base: master
Are you sure you want to change the base?
StoragePool creation changes for new 2 Nodes + 1 Arbiter cluster #2154
Conversation
7970644
to
259e6c7
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: aruniiird The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
259e6c7
to
cd0d893
Compare
...orage-system/create-storage-system-steps/capacity-and-nodes-step/capacity-and-nodes-step.tsx
Outdated
Show resolved
Hide resolved
...em/create-storage-system-steps/create-local-volume-set-step/create-local-volume-set-step.tsx
Show resolved
Hide resolved
cd0d893
to
72d3d9b
Compare
c1f916f
to
d6f2525
Compare
...orage-system/create-storage-system-steps/capacity-and-nodes-step/capacity-and-nodes-step.tsx
Outdated
Show resolved
Hide resolved
...orage-system/create-storage-system-steps/capacity-and-nodes-step/capacity-and-nodes-step.tsx
Outdated
Show resolved
Hide resolved
...-storage-system/create-storage-system-steps/capacity-and-nodes-step/selected-nodes-table.tsx
Outdated
Show resolved
Hide resolved
...-storage-system/create-storage-system-steps/capacity-and-nodes-step/selected-nodes-table.tsx
Outdated
Show resolved
Hide resolved
...em/create-storage-system-steps/create-local-volume-set-step/create-local-volume-set-step.tsx
Outdated
Show resolved
Hide resolved
...em/create-storage-system-steps/create-local-volume-set-step/create-local-volume-set-step.tsx
Outdated
Show resolved
Hide resolved
f6047e7
to
de9b29f
Compare
/hold |
b63901d
to
e21d994
Compare
One of the TWO issues I was facing is resolved now (the first issue, where ![]() |
@SanjalKatiyar , @bipuladh , please take a look at the Don't think this is relevant to this PR EDIT: above was a different error. now I could see that we have test failures related to |
e21d994
to
5bfd053
Compare
8f1af47
to
e98bbaf
Compare
When we detect a 2 Nodes + 1 Arbiter cluster, we should only show, '2-way Replication' in 'Data protection policy' list How is '2 Nodes + 1 Arbiter' cluster detected? There is an entry in 'Infrastructure' CR's `controlPlaneTopology` status, value should be `HighlyAvailableArbiter`. Added changes for 'StorageSystem' creation steps. Made changes to types as well. Signed-off-by: Arun Kumar Mohan <[email protected]>
Selected Nodes table footer sample (for a TNA cluster setup) Before Change (this included arbiter resources): '3 node selected (36 CPUs and 156.9 GiB on 0 zone)' After Change (now we exclude the arbiter resources): '2 nodes selected (32 CPUs and 125.6 GiB on 0 zone) + 1 arbiter detected' Change description: previously we had included the arbiter resources as well, but now we include only resources from nodes other than arbiter node. Signed-off-by: Arun Kumar Mohan <[email protected]>
e98bbaf
to
1673ffb
Compare
@aruniiird: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
When we detect a 2 Nodes + 1 Arbiter cluster, we should only show, '2-way Replication' in 'Data protection policy' list
How is '2 Nodes + 1 Arbiter' cluster detected?
There is an entry in 'Infrastructure' CR's
controlPlaneTopology
status, value should beHighlyAvailableArbiter
.