[feature]expose root-disk-source for maas provider
Bug #1930020 reported by
Bayani Carbone
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Juju 2.8.10 along with MAAS 2.9.2
I've setup a lxd based KVM host on MAAS and I have 2 storage pools available on the KVM host: lvm and ceph.
The lvm pool is the default pool in MAAS.
When adding machines through Juju, it's not possible to set a constraint to specify which storage pool to use, thus all VMs get created using the lvm pool.
The 'root-disk-source' constraint is available for the lxd provider but not the maas provider.
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| milestone: | none → 2.9-next |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| Changed in juju: | |
| milestone: | 2.9-next → none |
To post a comment you must log in.
This would be a useful option to have.
juju currently doesn't set "boot_disk" when invoking the allocate machine api.
The only thing currently supported is that when you do
$ juju add-machine --constraint=
juju will set the "storage" parameter on the allocate machines API to something like
"storage": "root:1024"
where "root" has a special meaning to maas.
We'd need to figure out the interaction between "root" and "boot_disk" etc in order to know how to wire things up properly.