Status: New
Owner: ----
New issue 852 by [email protected]: gnt-instance adding disks with
prefered pv
http://code.google.com/p/ganeti/issues/detail?id=852
What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".
What distribution are you using?
root@node2 ~ # gnt-cluster --version
gnt-cluster (ganeti v2.10.4) 2.10.4
root@node2 ~ # gnt-cluster version
Software version: 2.10.4
Internode protocol: 2100000
Configuration format: 2100000
OS api version: 20
Export interface: 0
VCS version: (ganeti) version v2.10.4
root@node2 ~ # hspace --version
hspace (ganeti) version v2.10.4
compiled with ghc 7.4
running on linux x86_64
root@node2 ~ # cat /etc/debian_version
7.5
root@node2 ~ # dpkg -l ganeti
[...]2.10.4-1~bpo70+1[...]
What steps will reproduce the problem?
1. create multiple PVs
2. put them in one VG
3. create VMs || add disks to VMs
What is the expected output? What do you see instead?
< ganeti creates the LVs by default behaviour and spreads them over all PVs
create an option for --disk (e.g. --disk 0:add,size=32G,pv=/dev/md/raid
--disk 1:add,size=128G,pv=/dev/sda6)
Please provide any additional information below.
LVM can do this with "lvcreate -L 32G -n [uuid].disk0_data [vg] [pv]"
and if set with modify "pvmove -n [uuid].disk0_data [current-pv] [new-pv]"
This would be a great feature because if you have IO-Problems and want to
split the VMs on to different Disks and keep this dynamic a separation with
volume groups is not possible.
You would have to export and reimport the VM if you want to change it, on
this way you only have to set the option.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
