[2.5, enhacement] MAAS should, by default, create virtual machines inside a KVM host /pod based on a prefix
Bug #1806756 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[2.5] MAAS should, by default, create virtual machines inside a KVM host /pod based on a prefix. This prefix could be the KVM host name, otherwise, it could be nice to allow the user to override the prefix.
For example, when juju creates containers inside a host, it does so in a stable naming convention, e.g:
juju-id-0
juju-id-1
juju-id-3
MAAS should do the same with KVM pods.
summary: |
- [2.5] MAAS should, by default, create virtual machines inside a KVM host - /pod based on a prefix + [2.5, enhacement] MAAS should, by default, create virtual machines + inside a KVM host /pod based on a prefix |
Changed in maas: | |
milestone: | none → next |
tags: | added: pods |
tags: |
added: pod removed: pods |
Changed in maas: | |
importance: | Undecided → High |
status: | New → Triaged |
importance: | High → Undecided |
Changed in maas: | |
milestone: | next → none |
To post a comment you must log in.
Nice idea! It might be a bit strange if we generate both names with petname; you'd end up with hosts like:
>>> import petname -'.join( [petname. generate( 2, '-'), petname.generate(2, '-')])) moral-moray ghoul-witty- tuna crow-sharp- gecko viper-cuddly- bream prompt- marmot sound-kid handy-ghoul light-zebra oryx-golden- heron prompt- mole
>>> for i in range(10):
... print('
...
wise-feline-
needed-
united-
viable-
ideal-lizard-
fleet-bunny-
chief-toad-
dear-corgi-
moving-
on-beetle-
We could use the the node_id or similar as the suffix, though that could eventually reach into the thousands if you bring up and tear down a lot of VMs. Or create a separate auto-increment per-pod. Or simply iterate until we find a good one... etc.
Names are hard.