-
Notifications
You must be signed in to change notification settings - Fork 1.5k
WIP Vsphere upi test #1495
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
Closed
Closed
WIP Vsphere upi test #1495
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -19,37 +19,24 @@ sshKey: YOUR_SSH_KEY | |
| 3. Fill out a terraform.tfvars file with the ignition configs generated. | ||
| There is an example terraform.tfvars file in this directory named terraform.tfvars.example. The example file is set up for use with the dev cluster running at vcsa.vmware.devcluster.openshift.com. At a minimum, you need to set values for `cluster_id`, `cluster_domain`, `vsphere_user`, `vsphere_password`, `bootstrap_ignition_url`, `control_plane_ignition`, and `compute_ignition`. | ||
| The bootstrap ignition config must be placed in a location that will be accessible by the bootstrap machine. For example, you could store the bootstrap ignition config in a gist. | ||
| Initially, the `bootstrap_complete` variable must be false, the `bootstrap_ip` variable must be an empty string, and the `control_plane_ips variable must be an empty list. | ||
|
|
||
| 4. Run `terraform init`. | ||
|
|
||
| 5. Run `terraform apply -auto-approve`. | ||
| 5. Ensure that you have you AWS profile set and a region specified. The installation will use create AWS route53 resources for routing to the OpenShift cluster. | ||
|
|
||
| 6. Find the IP address of the bootstrap machine. | ||
| If you provided an extra user, you can use that user to log into the bootstrap machine via the vSphere web console. | ||
| Alternatively, you could iterate through the IP addresses in the 139.178.89.192/26 block looking for one that has the expected hostname, which is bootstrap-0.{cluster_domain}. For example, `ssh -i ~/.ssh/libra.pem -o StrictHostNameChecking=no -q [email protected] hostname` | ||
| 6. Run `terraform apply -auto-approve -var 'step=1'`. | ||
| This will create the bootstrap VM. | ||
|
|
||
| 7. Update the terraform.tfvars file with the IP address of the bootstrap machine. | ||
| 7. Run `terraform apply -auto-approve -var 'step=2'`. | ||
| This will create the control-plane and compute VMs. | ||
|
|
||
| 8. Run `terraform apply -auto-approve`. | ||
| From this point forward, route53 resources will be managed by terraform. You will need to have your AWS profile set and a region specified. | ||
| 8. Run `openshift-install upi bootstrap-complete`. Wait for the bootstrapping to complete. | ||
|
|
||
| 9. Find the IP addresses of the control plane machines. See step 6 for examples of how to do this. The expected hostnames are control-plane-{0,1,2}.{cluster_domain}. The control plane machines will change their IP addresses once. You need the final IP addresses. If you happen to use the first set of IP addresses, you can later update the IP addresses in the terraform.tfvars file and re-run terraform. | ||
| 9. Run `terraform apply -auto-approve -var 'step=3'`. | ||
| This will destroy the bootstrap VM. | ||
|
|
||
| 10. Update the terraform.tfvars file with the IP addresses of the control plane machines. | ||
| 10. Run `openshift-install upi finish`. Wait for the cluster install to finish. | ||
|
|
||
| 11. Run `terraform apply -auto-approve`. | ||
| 11. Enjoy your new OpenShift cluster. | ||
|
|
||
| 12. Run `openshift-install user-provided-infrastructure`. Wait for the bootstrapping to complete. | ||
| You *may* need to log into each of the control plane machines. It would seem that, for some reason, the etcd-member pod does not start until the machine is logged into. | ||
|
|
||
| 13. Update the terraform.tfvars file to set the `bootstrap_complete` variable to "true". | ||
|
|
||
| 14. Run `terraform apply -auto-approve`. | ||
|
|
||
| 15. Run `openshift-install user-provided-infrastructure finish`. Wait for the cluster install to finish. | ||
| Currently, the cluster install does not finish. There is an outstanding issue with the openshift-console operator not installing successfully. The cluster should still be usable save for the console, however. | ||
|
|
||
| 16. Enjoy your new OpenShift cluster. | ||
|
|
||
| 17. Run `terraform destroy -auto-approve`. | ||
| 12. Run `terraform destroy -auto-approve -var 'step=3'`. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| output "ip_addresses" { | ||
| value = ["${vsphere_virtual_machine.vm.*.default_ip_address}"] | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -51,3 +51,7 @@ variable "datacenter_id" { | |
| variable "template" { | ||
| type = "string" | ||
| } | ||
|
|
||
| variable "cluster_id" { | ||
| type = "string" | ||
| } | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Can you provide a reason why we are dropping jq ?
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.
CI can't install epel-release and has an issue with internal repos, so upi-installer build fails with it.
@stevekuznetsov is looking at it afaik
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.
@smarterclayton where do the
devel-4.0rpm repos come from?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.
Builds for this started to see them unreachable