[2.4] Add ability to specify the storage pool for Virsh Pod

[Stefan Fleischmann]

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_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"

$ dpkg -l | grep maas
ii maas 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS client and command-line interface
ii maas-common 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Region Controller for MAAS
ii python3-django-maas 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)

[Stefan Fleischmann (sfleischmann)]

I'll be happy to provide more info if needed.

[Blake Rouse (blake-rouse)]

MAAS will pick the pool that has the most available space and use that. At the moment this is not configurable.