Hello,

I'm running my Ovirt-Node-NG based Hosts off ISCSI root. That is what
"vdsm-tool config-lvm-filter" suggests. Is this correct ?

[root@myhostname ~]# vdsm-tool config-lvm-filter
Analyzing host...
Found these mounted logical volumes on this host:

  logical volume:  /dev/mapper/onn_myhostname--iscsi-home
  mountpoint:      /home
  devices:         /dev/mapper/mpath-myhostname-disk1p2

  logical volume: 
/dev/mapper/onn_myhostname--iscsi-ovirt--node--ng--4.2.7.1--0.20181209.0+1
  mountpoint:      /
  devices:         /dev/mapper/mpath-myhostname-disk1p2

  logical volume:  /dev/mapper/onn_myhostname--iscsi-swap
  mountpoint:      [SWAP]
  devices:         /dev/mapper/mpath-myhostname-disk1p2

  logical volume:  /dev/mapper/onn_myhostname--iscsi-tmp
  mountpoint:      /tmp
  devices:         /dev/mapper/mpath-myhostname-disk1p2

  logical volume:  /dev/mapper/onn_myhostname--iscsi-var
  mountpoint:      /var
  devices:         /dev/mapper/mpath-myhostname-disk1p2

  logical volume:  /dev/mapper/onn_myhostname--iscsi-var_crash
  mountpoint:      /var/crash
  devices:         /dev/mapper/mpath-myhostname-disk1p2

  logical volume:  /dev/mapper/onn_myhostname--iscsi-var_log
  mountpoint:      /var/log
  devices:         /dev/mapper/mpath-myhostname-disk1p2

  logical volume:  /dev/mapper/onn_myhostname--iscsi-var_log_audit
  mountpoint:      /var/log/audit
  devices:         /dev/mapper/mpath-myhostname-disk1p2

This is the recommended LVM filter for this host:

  filter = [ "a|^/dev/mapper/mpath-myhostname-disk1p2$|", "r|.*|" ]

This filter allows LVM to access the local devices used by the
hypervisor, but not shared storage owned by Vdsm. If you add a new
device to the volume group, you will need to edit the filter manually.

Configure LVM filter? [yes,NO]


Am 05.01.2019 um 19:34 schrieb teh...@take3.ro:
> Hello Greg,
>
> this is what i was looking for.
>
> After running "vdsm-tool config-lvm-filter" on all hosts (and rebooting them) 
> all PVs, VGs and LVs from ISCSI domain were not visible anymore to local LVM 
> on the ovirt hosts.
>
> Additionally i made following tests:
> - Cloning + running a VM on the ISCSI domain
> - Detaching + (re-)attaching of the ISCSI domain
> - Detaching, removing + (re-)import of the ISCSI domain 
> - Creating new ISCSI domain (well, i needed to use "force operation" because 
> creating on same ISCSI target)
>
> All tests were successful.
>
> As you wished i filed a bug: <https://github.com/oVirt/ovirt-site/issues/1857>
> Thank you.
>
> Best regards,
> Robert
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VD6WCL343YGB2JVBWPZG54IMSQZ5VZ7M/
-- 


*Ralf Schenk*
fon +49 (0) 24 05 / 40 83 70
fax +49 (0) 24 05 / 40 83 759
mail *r...@databay.de* <mailto:r...@databay.de>
                
*Databay AG*
Jens-Otto-Krag-Straße 11
D-52146 Würselen
*www.databay.de* <http://www.databay.de>

Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202
Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm.
Philipp Hermanns
Aufsichtsratsvorsitzender: Wilhelm Dohmen

------------------------------------------------------------------------
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HX3LO46HW6GERQXDRCLRYUUN2NLURQTK/

Reply via email to