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.

Sign up for GitHub

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

Jump to bottom

IPI for vSphere: Support deployment to vSphere Resource Pool #3921

Closed
lamw opened this issue Jul 18, 2020 · 18 comments · Fixed by #5136
Closed

IPI for vSphere: Support deployment to vSphere Resource Pool #3921

lamw opened this issue Jul 18, 2020 · 18 comments · Fixed by #5136

Comments

@lamw
Copy link

lamw commented Jul 18, 2020

Version

$ openshift-install version

4.5.2
built from commit 6336a4b3d696dd898eed192e4188edbac99e8c27
release image quay.io/openshift-release-dev/ocp-release@sha256:8f923b7b8efdeac619eb0e7697106c1d17dd3d262c49d8742b38600417cf7d1d

Platform:

vSphere

Method:

IPI

What happened?

During the create install-config operation, it looks like the only option for where the OpenShift VMs are deployed to is at the root of the vSphere Cluster. For environments that leverage vSphere Resource Pools, it would be nice to be able to specify that, rather than having to move that after the fact. See screenshot below

openshift-on-vmware-cloud-on-aws-4new

What you expected to happen?

List both top level vSphere Cluster but also any Resource Pools that maybe available for selection.

Additional Details

I see that vSphere Terraform provider is being leveraged for the automation and Resource Pools is a supported option
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 28, 2020
@giannisalinetti
Copy link

giannisalinetti commented Nov 27, 2020 •
edited
Loading

This would be a great feature for IPI installations and I wonder why it is going stale. Please consider working on it, many customers that are adopting IPI on vsphere would love it!
I noticed the same limitation on v4.6.4.

@claudiotassini
Copy link

Confirmed same behaviour with openshift-install 4.6.4,

@claudiotassini
Copy link

/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 27, 2020
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 25, 2021
@styblope
Copy link

styblope commented Mar 3, 2021

same problem here. See my quick 4.7 patch to get things done.

@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 2, 2021
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci-robot
Copy link
Contributor

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

@jcpowermac
Copy link
Contributor

@styblope please submit a PR, cc me and I will review.

@jcpowermac
Copy link
Contributor

/remove-lifecycle stale

@jcpowermac
Copy link
Contributor

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label May 7, 2021
@jcpowermac
Copy link
Contributor

/reopen

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 7, 2021

@jcpowermac: Reopened this issue.

In response to this:

/reopen

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.

@openshift-ci openshift-ci bot reopened this May 7, 2021
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 5, 2021
@willhaines willhaines mentioned this issue Aug 5, 2021
Merged
1 task
@willhaines
Copy link
Contributor

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 5, 2021
@willhaines willhaines mentioned this issue Aug 12, 2021
Closed
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 4, 2021
@willhaines
Copy link
Contributor

/remove-lifecycle stale

Still trying to work through issues with e2e-vsphere test.

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

IPI for vSphere w/ existing resource pool UCBoulder/openshift-installer
8 participants
@lamw @openshift-bot @styblope @willhaines @jcpowermac @giannisalinetti @claudiotassini @openshift-ci-robot