-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Re-organize hypervisor implementations #18977
Re-organize hypervisor implementations #18977
Conversation
d2c5134
to
9d89c9c
Compare
LGTM |
9d89c9c
to
e05c4fd
Compare
Ensures that for each hypervisor implementation, their `config.go` file deals with implementing the `VirtProvider` interface while the `machine.go` file is for implementing the `VM` interface. Moves the `Virtualization` type into a common file and created wrappers for the individual hypervisors. Allows for shared functions that are exactly the same while providing the flexibility to create hypervisor-specific implementations of the functions. [NO NEW TESTS NEEDED] Signed-off-by: Jake Correnti <[email protected]>
e05c4fd
to
5160342
Compare
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.
LGTM
I restarted a timed out test that looked to be a flake. I would like a @bbaude head nod on this.
@baude @ashley-cui PTAL |
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.
LGTM, great job!
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jakecorrenti, rhatdan 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 |
Ensures that for each hypervisor implementation, their
config.go
file deals with implementing theVirtProvider
interface while themachine.go
file is for implementing theVM
interface.Moves the
Virtualization
type into a common file and created wrappers for the individual hypervisors. Allows for shared functions that are exactly the same while providing the flexibility to create hypervisor-specific implementations of the functions.[NO NEW TESTS NEEDED]
Does this PR introduce a user-facing change?