Status: New
Owner: ----
New issue 1146 by [email protected]: unable to mark storage as unavailable for
allocation
https://code.google.com/p/ganeti/issues/detail?id=1146
I'm using ganeti 2.15.
I found through the output of 'gnt-node list-storage -t lvm-vg' that a
number of LVM volume groups are considered Allocatable by ganeti. I don't
want them to be available for allocation because they are used for the
node's system itself, but I can't figure out how to mark them so they wont
be, for example:
Node Type Name Size Used Free
Allocatable
weaver lvm-vg ganetivg0 431.5G 71.2G 360.3G Y
weaver lvm-vg vg_weaver0 32.6G 17.7G 14.9G Y
the 'vg_weaver' volume group should not be allocatable. gnt-node
modify-storage has the option to mark these, but it only works for type
lvm-pv according to the man page (2.15): "Only LVM physical volumes can be
modified at the moment."
I looked at the output of 'gnt-node volumes' and thought maybe I could mark
the physical volume:
weaver /dev/mapper/md2_crypt vg_weaver0
root 10.2G -
weaver /dev/mapper/md2_crypt vg_weaver0
var 7.4G -
weaver /dev/mapper/md3_crypt ganetivg0
5553cd4e-a030-4f3d-aabe-46b28ba4b34b.disk0_meta 128M testvm
so I attempted this:
# gnt-node modify-storage --allocatable=no weaver-pn lvm-pv
/dev/mapper/md2_crypt
which seemed to take, but I dont see that it made any difference.
list-storage still shows them as allocatable, and 'gnt-node info weaver'
doesn't show that configuration anywhere.
--
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
