Unless you have a reason to use CentOS, I suggest you use oVirt node, it is much more optimized out of the box for oVirt On Thu, Sep 27, 2018 at 2:25 PM Stefano Danzi <s.danzi(a)hawai.it&gt; wrote: > Hello! > > I'm almost ready to start with a new oVirt deplyment. I will use CentOS > 7, self hosting engine and glusert storage. > I have 3 phisical host. Each host has four NIC. My first idea is: > > - configure bond betwheen NICs > - configure a VLAN interface for management network (and local lan) > - configure a VLAN interface for gluster network > - configure gluster for the hosted engine > - start "hosted-engine --deploy" process > > is this enough? do I need a phisical dedicated NIC for management network? > > Bye > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/DRCM7TIHMRP...

On Mon, Oct 8, 2018 at 10:28 AM Stefano Danzi <s.danzi(a)hawai.it <mailto:s.danzi@hawai.it>> wrote: I'm looking into oVirt node. The node management interface allow to configure network cards as bond or team. Is team interface supported by oVirt? Last time asked for other reasons on September, it seems not so soon. See Edward's message here: https://www.mail-archive.com/users@ovirt.org/msg50866.html HIH, Gianluca

Unless you have a reason to use CentOS, I suggest you use oVirt node, it is much more optimized out of the box for oVirt

You should be using shared external storage or glusterfs, if gluster you should have other drives in the server to porvision as gluster bricks during the hyoerconverged deployment On Mon, Oct 8, 2018, 8:07 AM Stefano Danzi, <s.danzi(a)hawai.it <mailto:s.danzi@hawai.it>> wrote: Hi! It's the frist time thai I use node. I installed node on my hosts and I leave auto partitioning. Hosts storage now is: [root@ovirtn01 ~]# lsblk NAME                                                          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT sda                                                             8:0    0 136,7G  0 disk ├─sda1                                                          8:1    0     1G  0 part  /boot └─sda2                                                          8:2    0 135,7G  0 part   ├─onn_ovirtn01-pool00_tmeta                                 253:0    0     1G  0 lvm   │ └─onn_ovirtn01-pool00-tpool                               253:2    0  94,8G  0 lvm   │   ├─onn_ovirtn01-ovirt--node--ng--4.2.6.2--0.20181003.0+1 253:3    0  67,8G  0 lvm   /   │   ├─onn_ovirtn01-pool00                                   253:6    0  94,8G  0 lvm   │   ├─onn_ovirtn01-var_log_audit                            253:7    0     2G  0 lvm   /var/log/audit   │   ├─onn_ovirtn01-var_log                                  253:8    0     8G  0 lvm   /var/log   │   ├─onn_ovirtn01-var                                      253:9    0    15G  0 lvm   /var   │   ├─onn_ovirtn01-tmp                                      253:10   0     1G  0 lvm   /tmp   │   ├─onn_ovirtn01-home                                     253:11   0     1G  0 lvm   /home   │   ├─onn_ovirtn01-root                                     253:12   0  67,8G  0 lvm   │   └─onn_ovirtn01-var_crash                                253:13   0    10G  0 lvm   /var/crash   ├─onn_ovirtn01-pool00_tdata                                 253:1    0  94,8G  0 lvm   │ └─onn_ovirtn01-pool00-tpool                               253:2    0  94,8G  0 lvm   │   ├─onn_ovirtn01-ovirt--node--ng--4.2.6.2--0.20181003.0+1 253:3    0  67,8G  0 lvm   /   │   ├─onn_ovirtn01-pool00                                   253:6    0  94,8G  0 lvm   │   ├─onn_ovirtn01-var_log_audit                            253:7    0     2G  0 lvm   /var/log/audit   │   ├─onn_ovirtn01-var_log                                  253:8    0     8G  0 lvm   /var/log   │   ├─onn_ovirtn01-var                                      253:9    0    15G  0 lvm   /var   │   ├─onn_ovirtn01-tmp                                      253:10   0     1G  0 lvm   /tmp   │   ├─onn_ovirtn01-home                                     253:11   0     1G  0 lvm   /home   │   ├─onn_ovirtn01-root                                     253:12   0  67,8G  0 lvm   │   └─onn_ovirtn01-var_crash                                253:13   0    10G  0 lvm   /var/crash   └─onn_ovirtn01-swap                                         253:4    0  13,7G  0 lvm   [SWAP] But I have no more space for hosted engine.... (Vm/Data space will be in another place). Now I could: - manually resize volumes - reinstall with custom partitioning and leave 60Gb for hosted engine volume. what's the better way? Il 27/09/2018 13:46, Hesham Ahmed ha scritto: > Unless you have a reason to use CentOS, I suggest you use oVirt node, > it is much more optimized out of the box for oVirt > > _______________________________________________ Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@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/PKVK6EWIHWK...