[2.4] Add ability to specify the storage pool for Virsh Pod
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Wishlist
|
Newell Jensen |
Bug Description
I have three pools defined on the Virsh pod:
$ virsh pool-list --all --details
Name State Autostart Persistent Capacity Allocation Available
-------
default running yes yes 49,09 GiB 19,93 GiB 29,16 GiB
iso running yes yes 1,13 TiB 521,53 GiB 635,19 GiB
zfs running yes yes 1,13 TiB 520,44 GiB 636,28 GiB
Image files are created in the pool called "iso". How can this be configured? If there is no way to configure which storage pool is selected, I would expect that the pool called "default" is used.
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
$ dpkg -l | grep maas
ii maas 2.3.0-6434-
ii maas-cli 2.3.0-6434-
ii maas-common 2.3.0-6434-
ii maas-dhcp 2.3.0-6434-
ii maas-dns 2.3.0-6434-
ii maas-proxy 2.3.0-6434-
ii maas-rack-
ii maas-region-api 2.3.0-6434-
ii maas-region-
ii python3-django-maas 2.3.0-6434-
ii python3-maas-client 2.3.0-6434-
ii python3-
Related branches
- Blake Rouse (community): Approve
- MAAS Lander: Needs Fixing
-
Diff: 377 lines (+83/-12)7 files modifiedsrc/maasserver/api/tests/test_enlistment.py (+7/-0)
src/maasserver/api/tests/test_machine.py (+4/-0)
src/maasserver/forms/tests/test_pods.py (+9/-0)
src/maasserver/rpc/tests/test_nodes.py (+1/-0)
src/maasserver/websockets/handlers/tests/test_machine.py (+3/-0)
src/provisioningserver/drivers/pod/tests/test_virsh.py (+21/-1)
src/provisioningserver/drivers/pod/virsh.py (+38/-11)
Changed in maas: | |
status: | Triaged → In Progress |
assignee: | nobody → Newell Jensen (newell-jensen) |
Changed in maas: | |
milestone: | 2.4.x → 2.4.0beta2 |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
I'll be happy to provide more info if needed.