-----
So from this i can see that when using logical volumes the volume
names are defined by setting the virt-path to the volume group name
and the logical volume name will be sytstemName-disk0
If the calc_virt_path2 function was modified slightly, to first split
the location on / and using the first part as the volume group name,
and then if the second part is not null set the logical volume name to
the second part, else use the default name.
It would be possible to also explicitly specify the logical volume in
the virt-path using the form volumeGroup/logicalVolume
I would submit a patch to do it, but im not a python programmer.
Python's easy :)
Anyhow, if --virt-path is an LVM volume, the idea with systemName-diskN
nomenclature is that you can specify that a virtual machine gets
multiple disks
cobbler profile edit --name=foo --virt-size=5,6,7
In this example, it would get 3 disks -- 5GB, 6GB, and 7GB
The disks would be named as follows:
virtName-disk0
virtName-disk1
virtName-disk2
Essentially the thought is that allowing too much variance in naming
here is going to cause some confusion, and using the virt name and the
disk numbers ensure things don't stomp over each other.
If you want to specify a specific LVM partition, you can still
pre-create it and then specify it with it's full "/dev" path.
Make sense?
I believe there are a several people using the LVM/virt stuff as above
so I'm not sure I'd want to change it and possibly break them.
--Michael
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
