[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
6
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.

Tags: pod
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
Revision history for this message
Mike Pontillo (mpontillo) wrote :

Nice idea! It might be a bit strange if we generate both names with petname; you'd end up with hosts like:

>>> import petname
>>> for i in range(10):
... print('-'.join([petname.generate(2, '-'), petname.generate(2, '-')]))
...
wise-feline-moral-moray
needed-ghoul-witty-tuna
united-crow-sharp-gecko
viable-viper-cuddly-bream
ideal-lizard-prompt-marmot
fleet-bunny-sound-kid
chief-toad-handy-ghoul
dear-corgi-light-zebra
moving-oryx-golden-heron
on-beetle-prompt-mole

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.

Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Changed in maas:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.