Open Stack

On 05-08-20 05:03:29, Eric K. Miller wrote:
> In case this is the answer, I found that in nova.conf, under the
> [libvirt] stanza, images_type can be set to "lvm".  This looks like it
> may do the trick - using the compute node's LVM to provision and mount a
> logical volume, for either persistent or ephemeral storage defined in
> the flavor.
> 
> Can anyone validate that this is the right approach according to our
> needs?

I'm not sure if it is given your initial requirements.

Do you need full host block devices to be provided to the instance?

The LVM imagebackend will just provision LVs on top of the provided VG
so there's no direct mapping to a full host block device with this
approach.

That said there's no real alternative available at the moment.

> Also, I have read about the LVM device filters - which is important to
> avoid the host's LVM from seeing the guest's volumes, in case anyone
> else finds this message.
 
Yeah that's a common pitfall when using LVM based ephemeral disks that
contain additional LVM PVs/VGs/LVs etc. You need to ensure that the host
is configured to not scan these LVs in order for their PVs/VGs/LVs etc
to remain hidden from the host:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/logical_volume_manager_administration/lvm_filters  

-- 
Lee Yarwood                 A5D1 9385 88CB 7E5F BE64  6618 BCA6 6E33 F672 2D76
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200805/a53474da/attachment.sig>