-
Notifications
You must be signed in to change notification settings - Fork 103
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 support for multicontrollers #500
base: main
Are you sure you want to change the base?
Conversation
Need to test it on an actual environment, submitted PR for initial feedback |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: averdagu 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 |
Hi @averdagu. Thanks for your PR. I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/51e3a694b38549d3a79be806783047c0 ✔️ install-yamls-content-provider SUCCESS in 1h 40m 56s |
6618686
to
53a848b
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/571502dfda8e4f118332827435542d13 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 07m 39s |
c9b5011
to
237c548
Compare
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/8f698f9af9b54dcdbf4c1d6d04f050a1 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 36m 21s |
/ok-to-test |
I think this PR should include some documentation (in devsetup dir?) explaining how this should be used for multi node case. |
echo STORAGE_IP_START ${STORAGE_IP_START} | ||
echo STORAGE_IP_END ${STORAGE_IP_END} | ||
echo TENANT_IP_START ${TENANT_IP_START} | ||
echo TENANT_IP_END ${TENANT_IP_END} | ||
|
||
cat > ${DEPLOY_DIR}/ctlplane.yaml <<EOF_CAT | ||
apiVersion: k8s.cni.cncf.io/v1 |
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 wonder if this should/could make devsetup/scripts/bmaas/network-attachement-definition.sh more generic and re-use?
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 think there are different things.
In this case during the gen-netatt.sh the NetworkAttachmentDefinition resources are being created. This will determine the IPs that will have the pods that have an interface on any of those networks. So at the end this script will generate openshift resources.
The newtork-attachment-definition.sh is useful to modify the crc VM (but gen-netatt.sh will be used regardless if we use crc or dev-metal3 deployment)
237c548
to
e950ed8
Compare
In order to adopt an OSP Wallaby environment, CRC VM needs to be able to connect to all Wallaby networks. With this new target CRC will be able to do it.
Adopting a multicontroller OSP 17.1 wallaby deployment means modifying a lot of the hardcoded values in nncp stage. In order to make things easier the Interfaces, Networks and vlans are parameterized. As well as adding a new variables section called MCD (multi cluster deployment) with the correct values to adopt a multi controller wallaby environment.
Adopting a multicontroller OSP 17.1 wallaby deployment means modifying a lot of the hardcoded values in netattach stage. In order to make things easier the Interfaces, Networks and vlans are parameterized.
Adopting a multicontroller OSP 17.1 wallaby deployment means modifying a lot of the hardcoded values in netattach stage. In order to make things easier the Interfaces, Networks and vlans are parameterized.
e950ed8
to
107c317
Compare
@averdagu: 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/test-infra repository. I understand the commands that are listed here. |
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/5bd0cb7dcaa54087815b9bd622035034 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 31m 28s |
Adopting from an OSP 17.1 wallaby deployment formed by 3 controllers + 2 computes requires a
lot of manually changing hardcoded values on a few different files to adapt to the network schema of
wallaby deployment. With this pull request I intend to make it parameterizable