I think renaming the existent volume to a name that cinder/nova-volume recognize is enough.
On Thu, Oct 25, 2012 at 8:48 AM, Daniel Vázquez <daniel2d2...@gmail.com> wrote: > If we create a volume out of openstack context (it's is not created on > nova database) only on system level. Can we after add to openstack? > reformulate ask, Can we add to openstack an existen volumen (it's > living on nova-volumes group)? I'm not sure on nova-volume create > command or horizon ... that behavior it will be with existent lv label > or some other properties. > > 2012/10/24 Daniel Vázquez <daniel2d2...@gmail.com>: >> Yeah!! Jon, I'm agree with you about organization/separation LVM >> groups, this is for very very very special situation. >> Any case if I use nova pattern labeling via logical volumen creation >> or via renaming label, I hope can switch the content of this custom >> logical volument to use with openstack, an attach to a VM in future. >> >> >> >> 2012/10/24 Jonathan Proulx <j...@csail.mit.edu>: >>> On Wed, Oct 24, 2012 at 08:56:26PM +0200, Daniel Vázquez wrote: >>> :Hi here! >>> : >>> :Can we create and use news logical volumes for own/custom use(out of >>> :openstack) on nova-volumes openstack LVM group, and use it beside >>> :openstack operational? >>> :IMO it's LVM and no problem, but it has openstack collateral consequences? >>> >>> If you are talking about creating random logical volumes for >>> non-openstack use in the same volume group nova-volume or cinder is >>> using to create volumes (lv are in the same vg but don't otherwise >>> interact), yes you can do that without ocnfusing openstack or having >>> your volumes trampled. For example only having one volume group and >>> using that for operating system partitions as well as volume-<foo> >>> volumes for cinder >>> >>> I don't think it's a particularly good idea from an organizational >>> standpoint I'd rather have distinct vg's for each purpose so it is >>> clear which resources are operating system and which are data, but in >>> my environment (a private computing/research cloud with a small admin >>> group and 1k users in a few 10's of closely related tenents) it's >>> probably more an aesthetic than technical choice. The larger and more >>> diverse your situation the stronger I'd argue for keeping them in >>> seperate VGs. >>> >>> -Jon > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp -- guilherme \n \tab maluf _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp