-
Notifications
You must be signed in to change notification settings - Fork 485
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 vSphere IPI #154
Add vSphere IPI #154
Conversation
- Does vsphere need any metadata changes: | ||
- `pkg/asset/cluster/vsphere` | ||
- `pkg/asset/cluster/vsphere/vsphere.go` | ||
- Do we need to create resource pools? |
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.
@sdodson @dav1x when you get a chance if you can take a look as well. |
- Custom placement of the VM template | ||
- Custom name of the VM template | ||
- `pkg/rhcos/vsphere.go` | ||
- Add machines and machinesets |
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.
Developing for the machine API is happening here
API
https://github.com/openshift/machine-api-operator/tree/master/pkg/apis/vsphereprovider
Controller
https://github.com/openshift/machine-api-operator/tree/master/pkg/controller/vsphere
We'll start by supporting only vCenter interactions (no raw esxi) and only supporting cloning templates on "creation". We'll extend this behaviour later on only if there's a product requirement.
We are assuming the existence of a secret with a user and password keys used to login against the vCenter https://github.com/openshift/machine-api-operator/blob/master/pkg/controller/vsphere/machine_scope.go#L57
@jcpowermac I know vSphere IPI support has already merged. Can you help make sure this enhancement is updated to reflect what has been done and then we'll merge it to reflect the current state of things? Thanks! |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
@jcpowermac bump on this, can we do a quick review to make sure there aren't significant deviations between this enhancement and what's actually been implemented and then merge it? |
/remove-lifecycle rotten |
@jcpowermac bump. :-) (also pinged on slack) |
This is generally up-to-date, there might have been minor changes from when this document was written til now. vSphere IPI continues to use kni aka baremetal networking services. The CI section is out of date, we only use VMC (VMware on AWS) now. That can be updated later
8ef14fa
to
e149501
Compare
@jcpowermac says this is close enough and that the CI section is the most out of date. We should just merge as is. /lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: russellb The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
No description provided.