Skip to content
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

WIP: IPI installation to Azure Stack #4799

Closed
wants to merge 11 commits into from
Closed

Conversation

staebler
Copy link
Contributor

@staebler staebler commented Mar 28, 2021

  • Add AzureStack as a valid value for the azure cloudName field.
  • Add the platform.azure.armEndpoint field for specifying the ARM endpoint when installing on Azure Stack.
  • Add validation specific to Azure Stack.
  • Add the github.com/terraform-providers/terraform-provider-azurestack module. This is replaced with a fork that bumps the azurerm provider used and fixes a bug the an invalid ConflictsWith in the availability set resource.
  • Add terraform for provisioning a cluster using the azurestack provider.

https://issues.redhat.com/browse/CORS-1665

This builds on #4729

/cc @jhixson74 @patrickdillon

@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 28, 2021
@openshift-ci-robot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from staebler after the PR has been reviewed.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

@patrickdillon patrickdillon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than /data/data/azure/main-stack.tf and the exclusion logic couldn't we just write the tf configs in /data/data/azurestack? At a quick glance it doesn't look like azurestack is reusing any of the azure modules; but perhaps there is a benefit or need?

@staebler
Copy link
Contributor Author

Rather than /data/data/azure/main-stack.tf and the exclusion logic couldn't we just write the tf configs in /data/data/azurestack? At a quick glance it doesn't look like azurestack is reusing any of the azure modules; but perhaps there is a benefit or need?

That is how I originally wrote it. But I had used different variables names (like azurestack_region). I didn't like having to duplicate all the go code for building out the variables. And I didn't like the prospect of keeping those in sync. Now that I am using the same terraform variable names for both, I think that you are correct that it would be better to put the azure stack in /data/data/azurestack. I could symlink the terraform variables file from /data/data/azure to /data/data/azurestack.

@staebler
Copy link
Contributor Author

b833f34...503ea32

  • Move terraform files for Azure Stack to data/data/azurestack.

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 5, 2021
@openshift-ci-robot
Copy link
Contributor

@staebler: 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/test-infra repository.

staebler and others added 9 commits June 17, 2021 15:03
Bump github.com/openshift/api to include new AzureStack
value for the AzureCloudEnvironment.
Add AzureStack as a valid value for the azure cloudName
field. Add the `platform.azure.armEndpoint` field for
specifying the ARM endpoint when installing on Azure Stack.
Add validation specific to Azure Stack.
Include the azurestack provider in the plugins that
terraform knows.
Add the github.com/terraform-providers/terraform-provider-azurestack
module. Replace it with a forked version that uses a new azurerm
provider and that fixes an invalid ConfictsWith declaraction in the
availability set resource.
Add the terraform files for provisioning a cluster in
Azure Stack.
When provisioning a cluster onto Azure Stack, use the terraform
in data/data/azurestack instead of data/data/azure.
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 18, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 18, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from staebler after the PR has been reviewed.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Use the azurestack_image resource to create an image to use
for the azurestack VMs.

This requires an existing blob with the OS image to be in the
environment. The OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE
environment variable must point to the existing blob.
@ausil
Copy link

ausil commented Jul 14, 2021

what exactly does arm mean in this case? I am guessing not the arm architecture?

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 14, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 14, 2021

@staebler: 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/test-infra repository.

@patrickdillon
Copy link
Contributor

what exactly does arm mean in this case? I am guessing not the arm architecture?

I believe it stands for azure resource manager

@ausil
Copy link

ausil commented Jul 14, 2021

what exactly does arm mean in this case? I am guessing not the arm architecture?

I believe it stands for azure resource manager

okay, thanks, I thought so, I only just learned it existed. This is likely to go cause confusion with the ARM architecture.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2021

@staebler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-verify-codegen b52401b link /test okd-verify-codegen
ci/prow/okd-images b52401b link /test okd-images
ci/prow/e2e-aws-workers-rhel8 b52401b link /test e2e-aws-workers-rhel8
ci/prow/okd-unit b52401b link true /test okd-unit
ci/prow/openstack-manifests b52401b link true /test openstack-manifests
ci/prow/e2e-aws-upgrade b52401b link true /test e2e-aws-upgrade
ci/prow/e2e-aws b52401b link true /test e2e-aws

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.

@staebler staebler closed this Dec 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants