Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upAllow changing default storage pool #2415
Comments
marmarek
added
C: core
P: major
labels
Nov 4, 2016
marmarek
added this to the Release 4.0 milestone
Nov 4, 2016
marmarek
assigned
kalkin and
marmarek
Nov 4, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
andrewdavidwong
Nov 5, 2016
Member
@kalkin replied with
(posting as a comment since GitHub doesn't send notifications for reactions)
|
@kalkin replied with |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Done. |
marmarek
closed this
Jul 13, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedNov 4, 2016
In current implementation pool named "default" is special in the sense that
qvm-createwill use it if no other is specified. But it is just normal pool. Especially, it can't be easily renamed, it stays as "default" in VM storage settings etc.This means there is no easy way for changing default storage pool in the system (for new VMs).
Proposal: add global property
default_pool, then during VM creation patch volume_config with value pointed there. The same way asqvm-create -Pis handled.@kalkin if you have nothing against, I'll implement this.