Merge lp://staging/~freyes/maas-deployer/virtual-nodes into lp://staging/maas-deployer
Proposed by
Felipe Reyes
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 69 | ||||
Proposed branch: | lp://staging/~freyes/maas-deployer/virtual-nodes | ||||
Merge into: | lp://staging/maas-deployer | ||||
Diff against target: |
263 lines (+195/-13) 2 files modified
examples/virtual-nodes.yaml (+166/-0) maas_deployer/vmaas/engine.py (+29/-13) |
||||
To merge this branch: | bzr merge lp://staging/~freyes/maas-deployer/virtual-nodes | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Nobuto Murata | Needs Fixing | ||
Billy Olsen | Approve | ||
Review via email: mp+289115@code.staging.launchpad.net |
Description of the change
Maintainers,
I would like to add the option to create virtual machines (virtual-nodes) and get them registered into the freshly installed maas.
This MP includes a exmple yaml file to understand how this is intended to be used.
Rationale
---------
maas-deployer already has all the plumbing needed to create (through virsh) and register VMs/bare-metal (into MAAS), but some scenarios (specially labs and bug reproducers) require to create extra VMs for the workload that it's intended to be deployed with juju (typically OpenStack), so I pretend to use this for that, as a tool to build disposable labs easily.
Best,
To post a comment you must log in.
In general, I'm +1 on this. I feel that the virtual-nodes set is something that may be confusing rather than just nodes, however I do understand why its there (so there's a distinction of nodes to create and nodes which are expected to be present). I really waffled back and forth about whether to use virtual-nodes or to use a tag inside of a node, but ultimately it doesn't matter that much so I'll approve as is.