January 2018 - Users - oVirt List Archives

Need input please.
by carl langlois 07 Jan '18

07 Jan '18

Hi again all, I really need your input on recovering my failed upgrade to 4.2. I do not now what manipulation i did to end up in this situation. First i have to host and a hosted_engine running on those Hosts. The engine is seem to be running fine. If i ssh to any hosts i can manage the hosted engine with hosted_engine command. The hosted engine can also migrate from one to the others if i put one host in local maintenance. In the web UI i can see evevrything but i am not able to do any action on the current data center, hosts, domain.. The main problem is that all host are stuck in not operational mode.. I do not know where to look for The only thing that i can see that is not working is this event [image: Inline image 1] I do i debug this SSLEngine problem... log? what to look in the log? Anything would help. here is some question : i would like to remove one host and adding it again but i am not able to remove from the UI. Is there a way to force the remove somewhere ? Thanks Carl

5 10

Can't create 2nd network for VMs in DMZ zone
by Andrei V 07 Jan '18

07 Jan '18

Hi ! I'm having difficulty to utilize 2nd NIC on HP Proliant server in order to connect guest VM to DMZ (engine, node and all other guest VMs are on internal zone). I tried to use PCI passthrough, downed ifcfg-enp3s4f1 on node host, created vNic profile "PCI NIC Passthrough", network named "Node10-NIC2", then Virtual Machines -> Network Interfaces -> nic 2 of type PCI Passthrough and profile above. Unfortunately, guest OS (SuSE Leap 42.3) still don't recognize this NIC. This 2nd NIC is visible on Compute -> Hosts -> Network Interfaces. I can assign it network named "Node10-NIC2". However, right now I'm working from the remote, if node net setup get screwed, it will be a big problem. In the archive I found that this 2nd NIC must be up with no IP and default route. Is this correct definition of ifcfg-enp3s4f1? NetworkManager is disabled on node. TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=no NM_CONTROLLED=no NAME=enp3s4f1 UUID=09f96366-e4a9-4e6e-a090-7267ed102d36 DEVICE=enp3s4f1 ONBOOT=yes Thanks in advance Andrei V

1 0

Local storage and multiple hosts in cluster
by Waqar Khan 07 Jan '18

07 Jan '18

Hi, I have 1 engine manager and 2 nodes. The 2 nodes are using local storage (this is for testing out ovirt and learning about it). I cannot however add 2 hosts to the same cluster in the same data centre without shared storage. Is there a workaround for this? Regards

2 1

ovirt 4.2 and hosted-engine storage migration
by gabriel_skupien＠o2.pl 06 Jan '18

06 Jan '18

Does it exist any supported procedure to migrate the hosted-engine from one NFS storage to another NFS storage? I would appreciate any clue regarding this matter.

1 0

Upgrade to 4.2
by carl langlois 06 Jan '18

06 Jan '18

Hi all, I have upgrade to 4.2 and have some problem getting everithing up and running again. The upgrade was made from latest 4.1. For now the engine dashboard can be access but all hosts, data center are all the status to "Not responsive" ... for now the only thing i found is ERROR ssl handshake: SSLError, address: from a systemctl status vdsmd Any help would be appreciated Carl

2 2

Re: [ovirt-users] Unable to add VM Portal successfully
by Jakub Niedermertl 06 Jan '18

06 Jan '18

Hi Pym, to deploy VM Portal (ovirt-web-ui) next to the engine one needs to compile it from sources to rpm package [1], and install it next to ovirt-engine package. Container deployment is not used by default. Technically ovirt-web-ui is another war application served by engine's Wildfly. See symlink /usr/share/ovirt-engine/ovirt-web-ui.war and configuration file /etc/ovirt-engine/engine.conf.d/50-ovirt-web-ui.conf of package ovirt-web-ui [2] for details. Best regards Jakub [1]: https://github.com/oVirt/ovirt-web-ui#build [2]: http://resources.ovirt.org/pub/ovirt-4.2/rpm/el7/noarch/ On Thu, Jan 4, 2018 at 10:58 AM, Pym <pym0914(a)163.com> wrote: > Hi: > > I recently built the ovirt-engine service in source code compilation, > which is now accessible through the web interface. However, there is no VM > Portal feature on the main page. After clicking, "404 - failed to find the > page". > > Next I found the source code for web- UI functionality at github, and I > wanted to install it through source compilation. I tried to follow the > above process, but the following problems occurred: > > " > [root@ovirttest ovirt-web-ui]# docker run --rm -it --network host > --add-host ovirttest.erc.com:10.100.211.113 -e ENGINE_URL= > https://ovirttest.erc.com/ovirt-engine -p 3000:3000 > mareklibra/ovirt-web-ui:latest > yarn start v0.24.4 > $ node scripts/start.js > Please authenticate against oVirt running at https://ovirttest.erc.com/o > virt-engine > oVirt user (admin@internal): admin > oVirt password: ****** > oVirt domain (internal-authz): ovirttest.erc.com > Failed obtaining oVirt auth token: Error: connect ECONNREFUSED > 10.100.211.113:443 > Done in 27.64s. > " > > How to make sure the container can reach the engine on this ip:port. > > Or there are other ways to solve this problem, which has been bothering me > for days. > > Thank you very much. > > > >

2 1

Ovirt update 4.2 crash
by Thomas Fecke 05 Jan '18

05 Jan '18

--_004_5e5ceee923ea447880f660f699109f85DR1XEXCH02Besetcorp_ Content-Type: multipart/alternative; boundary="_000_5e5ceee923ea447880f660f699109f85DR1XEXCH02Besetcorp_" --_000_5e5ceee923ea447880f660f699109f85DR1XEXCH02Besetcorp_ Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Hey Guys, I wanna update ovirt 4.1 to 4.2. I followed the update guide but in the "yum update" I get following error m= essage: --> Konflikt wird verarbeitet: ovirt-engine-setup-plugin-ovirt-engine-4.2.0= .2-1.el7.centos.noarch kollidiert mit ovirt-engine < 4.1.7 --> Abh=E4ngigkeitsaufl=F6sung beendet Fehler: ovirt-engine-setup-plugin-ovirt-engine conflicts with ovirt-engine-= 4.1.5.2-1.el7.centos.noarch Sie k=F6nnen versuchen, mit --skip-broken das Problem zu umgehen. Sie k=F6nnten Folgendes versuchen: rpm -Va --nofiles -nodigest How to upgrade to 4.2? Thank you Guys Mit freundlichen Gr=FC=DFen / Best regards, Thomas Fecke Pre Sales Specialist +49 3641 3114 205 [ESET] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -= - - - - - - - - - - ESET Deutschland GmbH Spitzweidenweg 32 07743 Jena Deutschland www.eset.de<http://www.eset.de/> Amtsgericht Jena: HRB 508673 - Gesch=E4ftsf=FChrer: Miroslav Miku=B9 --_000_5e5ceee923ea447880f660f699109f85DR1XEXCH02Besetcorp_ Content-Type: text/html; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 2"> <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> Hey Guys,<o:p></o:p> <o:p> </o:p> I wanna update ovirt 4.1 to 4.2. <o:p></o:p> <o:p> </o:p> I followed the update guide but in the “yum up= date” I get following error message:<o:p></o:p> <o:p> </o:p> <o:p> </o:p> --> Konflikt wird verarbeitet: = ovirt-engine-setup-plugin-ovirt-engine-4.2.0.2-1.el7.centos.noarch kollidie= rt mit ovirt-engine < 4.1.7<o:p></o:p> --> Abh=E4ngigkeitsaufl=F6sung = beendet<o:p></o:p> Fehler: ovirt-engine-setup-plugin-= ovirt-engine conflicts with ovirt-engine-4.1.5.2-1.el7.centos.noarch<o:p></= o:p> Sie k=F6nnen versuchen, mit --skip= -broken das Problem zu umgehen.<o:p></o:p> Sie k=F6nnten Folgendes versuchen:= rpm -Va --nofiles –nodigest<o:p></o:p> <o:p> </o:p> How to upgrade to 4.2? Thank you Guys<o:p></o:p> <o:p> </o:p> Mit freundlichen Gr=FC=DFen / Best regards,<o:p></o:p><= /span> Thomas Fecke<o:p></o:p> Pre Sales Specialist<o:p></o:p> +49 3641 3114 205 <o:p></o:p> <img width=3D"262" height=3D"37"= style=3D"width:2.7291in;height:.3854in" id=3D"Grafik_x0020_1" src=3D"cid:i= mage001.png(a)01D3865F.017A8C60" alt=3D"ESET"><o:p></o:p> <o:p> </o:p> - - - - - - - - - - - - - - - - - - -= - - - - - - - - - - - - - - - - - - - - - - - - - - - - -<o:p></o:p></s= pan> ESET Deutschland GmbH<o:p></o:p> Spitzweidenweg 32<o:p></o:p></= p> 07743 Jena Deutschland<o:p></o:p>= <o:p> </o:p> <a href=3D"http://www.= eset.de/">www.eset= .de</a> <o:p></o:p>= <o:p> </o:p> Amtsge= richt Jena: HRB 508673 – Gesch=E4ftsf=FChrer: Miroslav Miku=B9= <o:p></o:p> <o:p> </o:p> </div> </body> </html> --_000_5e5ceee923ea447880f660f699109f85DR1XEXCH02Besetcorp_-- --_004_5e5ceee923ea447880f660f699109f85DR1XEXCH02Besetcorp_ Content-Type: image/png; name="image001.png" Content-Description: image001.png Content-Disposition: inline; filename="image001.png"; size=7177; creation-date="Fri, 05 Jan 2018 18:54:34 GMT"; modification-date="Fri, 05 Jan 2018 18:54:34 GMT" Content-ID: <image001.png(a)01D3865F.017A8C60> Content-Transfer-Encoding: base64 iVBORw0KGgoAAAANSUhEUgAAAQYAAAAlCAYAAAHXfXeGAAAAAXNSR0IArs4c6QAAAARnQU1BAACx jwv8YQUAAAAJcEhZcwAADsQAAA7EAZUrDhsAABueSURBVHhe7V0HfJVFth8sWV196+66blHf7rqu Rtn3Vl11XSyASA8QWgIklPRKCQRCSJCQRgmhJiS5/aZRBQEVaRIFRRDQALoISLHhirKKigKW8/7n fPPd3JuiqEGTfff/u+c3M2fOlG/u1G/mzKe+FWJGXa9tzQ9qBKfPnSOVmduQLgjCI4t0uqQGDSUV HiH202fOinmGMxM6VOzsp0N54LTbZ7KZlZV1kcPhuAbkttls5cyzW63zQTNdLtcfEbzN/Pnzf8J8 E3a7fZrFYrlbqa59YjmBv8Qnk+rYhVTn7tQ3Ow+ZOMNsgerey2Pq8M2PhEXLJBEffPUVqaSUhvSf i/Rs/ei+aLRSZuRdp0M1LyRBXRlNnPr0U1Ih4aSCB9LxDz6gF4+9TmrgEFIRsfJ3oKJJxfMGKtm1 2soVMkdbmX8XmyUVFb92Op15Vqv1drfTObMc4IopQpyo6vAQ3ZY0SjKwducuUu3aC++xbdvpwFtv Ue2RI0al7NX3AtWJ1ExJvD5+nEo5p4xU9ixS0+Z9M81Y8PU0E1RQkqxjbiVISv3Dc4ePyj+w6cAh UjHos2JG0rsffSy8ayc+TCoavNiR9BXcp8+eJTVyPH0C0wTLr/vnq9plQI1MJTUuoxV1K736btR5 l7o/+9E1VLhyNc1asUp4Hcank3qoG6muPUk98KB05iooWPyGFBTSYE0ctvaIUaDShpiCB/gUxOLF i29mEw24RhgacG9AY31ZO9ltqSgv38OjETqDvszDCPN7m9V6WAQAjE4vs7/b7b7OZrGMZB43fuYh C20qKiquYB7i2oGwfSH/ErthhsF9C9sboO24NHmA84EUxCD0Yn36Y2gNI9U3xBh6mcduJrYbbs/D tR5MzglUk7K/AtH3oowcwlg0Xsfqh4pKbmWFMWvhYZU3p/HRoT41NkLUpyIHqeFJf9GxtwJk5u60 7NytW/43Q6VNaXyaVZ+yZrSikQLDn4mLeJjD8PhfKRPF/SXPrjEcMu/69CnCU3Gj6bLRE8TOeOpV DLPJ47TLgIodZQyZrQb9B0vGbTXPkOoXKnaeux49cYLU0EhqnztdeDxfYKiQMDFTqxeT6hIkdhkl zLA9giWcLMowdOlUlMNqTcHQdxmGxSgMWV2cNtsg5mOOOwfudPCT2F1ZWWks0uz2BzH8XQ8zb1FV lYV5WNQVs+mw2UrtWMxB1sruSsyNnVZrMGTbYaF3P8z/ETmHo4hNBnhz2HTZ7QnCABB/sGHDfIAR X1yKeUGQzBeYXj/xnvB5fsCLP54DiLtLDzHnr37MM2dQPXoLMdSDWCyac4YuQ2XcZmDs3iNmWdmD 8tA2m73+3IFRWlp6E5tul2ub02K5t6ys7G8uh2Mq85wOx6tsmnA7HGNramouYTvmE7NQoDmIczIe bgncj4qQF5DmIswpLsGq9xqX03lKs4H7O0rmT50+LQuHuY+uJtUtiN798EO6ou9AUu070dN799Wt ePGQJp6q3SMmF4xZODy5kgXIN6yM8S+11dYWgGFRkvnzheqnJ0mo/tw0VB/MEOsmSXV2plaF6CT9 iN8MWWs0tuprQGOe1bG3ImTmLGt0FvhtKT37uI6xFWPu3J9j8pSjCorXqplFO1oEzViwGsv1EMlf dNJc0KMqPl46UD8uBPj9CCZ69zuq6JNz53Qn0DxQk6eRypnVPJSLUTl7plvn2o9mx8P5dF3ODP3X NS9Onz1HakwaqfGZBo2GPQFjCPMwCVeJY0mNm1Tnj8m8+NenRJApw5Q6aYfOvR/NhujESBUeqf86 A+e++IJUGBYCscnUBvSPaWiREXHiVqHDtBTRjZOyPDKR7kohNTRaZP8yJU9k5GXliBhSw6LpK6zM TOw8eoyOvPe+dhFNXLEKK7ZEWrbrRc2pA4f6nPM0HPHEJhmUjErkRzNjwKCNqqexUDKRaLWTGjDY IJ4im9R/kLxn3LRnr8j9JjrekOmP6XQQFk+9+8tL11uSx9AxvRiT95S9wNcrzqbwxZdfkuqJhRvH hzRqjx3TPhhmumOxZubHpFBM44fWLda8gYXUPm0VlLvdsgjjhZaYWMixiUXdI2wy4Ldk2bJlAVjf RINfqtksk4qVq2fzFmG3IP4X2e6229sLU8NeUjJMWz2LR5vFki4MDSz0hM8vim2lpT1NO1bJBWxn IKysfrE4jBE55AHp7uVVdnFx8ZUwy0QQgOwGNhFvKJvI2yY2GQhX7LBYOmNB+jvN4pX1MGtJyQOI +yb4/4a3TjkNw7drUKl6oJMudgMLVq+RhaW6z1hwmli4ag2VPb6W3nzP+KOP/utdsXtvt65+fofx 5l4vVqUydOws27MmCpY/Ysg82BWL2FXkXL+RHOs2GKtyThcr+drDR7Q0KgPyIXxv4hV/hw6yqq4P PHC1w25/AeYd7MZDd0GBtDNfaaAAPcscyO3CKvsZ7WQ/T0EzbGVlQ1GZauWtv802QrM5jVG86kcF ulizVHVV1e7y8vIX2I54VmjTZ0mFP034jMqKil2cT7ajEqYgjRfsZWV3IW55XQtzAP9RiCNWu5fw Kxq2I8/bEfZ5tjOqKyt3oSLIc8DcDf/N4gEgzIoK5IsrO7tRsdaJRwP0HvhnbtGvvPGGLnoDmVWL 5M/iVy+ePwDuYXPmaQmiN1ARVEct0wV/Lr9p4D+5cw/aq1u2VIZuvaTH+NnAIfQleoD6OHPuc7rI 3MrhHgi9zIG3j2tfVAbeGvLuoZgGDPEPExcEI2IP87zhuUOHdfE3H2TOEBZhzDmai6ISSIXHt6DX Vf9pCEF3N2nqGTURk0Ke0adm0JWZOXRFM5CaMBn08PenyXmk0h6u0Dn24/89ohLHo2eQLQc/LjQK i7qpGQseAW1r9G3gD07FG1RB0RyVhxnxnepSFZNcoaKTFujc+nFBkD97sOy58957VgGpaXMb7tt/ F6q/r/9daXYpqVnFH6rIyD/pHPtxQTB1+gSVjz8/I48e2X9AT/2aB7eWoII19lr5u1A2KikfUfTj AiEr6xKVi4JOM85qNDcC5y5s/MDLdyZMSDNyT+rc+9GsSM208T7BydOn9d/XvAiciR7Hs5+QIYeA 1CisVniPgvcl2O6959DYvgST9/4FHyr04wJgZOoXbfCn1Ef72UVyoksORTPBHlO5WPsamLFhM6l4 Lxmm+DE0c+NmLYHKkDPDOPGFP3T2U89ori9uyso3lrMI2xTu5ErF8QhBdlTqQP0EfjQbksdSr6JS XeQGbs+dbmxKRcTRrVNy6IZ0rPGjE0nFJFH+2vUi8ymrGw2LFl6HWfNkk+rGjCzjpdCgYZ43jYGT s2Vj6a78meJmfHTmDG33et3MkI2xCFEuahS3ZU+r26Riik5uoEHix/dFZBwVPL5WF7kBOfQeHkGp 1Us0h6jtRHTP4F2FP4Lx9P5XSQ0ZLptX3jj3+Rf0IYYcc4cykDUNwkbQkud3iJshr7mDB9LvklM0 h+jqhFHGkUlWGRpctzOa6KoweIhDjlPWUa1+gvpoU1lZaQfk2KPDZpONIrij2GTYbLZINq1W6w0V FRXWMrf7RkXUxl5WFsR8u8UymE0GZBPtVut87VTV1dWeZa3dZpvLxy4tFsuliGu4024v502hZcXF V4LvdFgsHbQoh/uV2+l0QcbJMhxvuctVvnTp0svZn491Io9ytBN+cWwifBqbVVVVc9kEP5PNSoSv KC+3IZ7/ZbfD4RjLJsNlsdzCz+SePVt0v3jvxOVyuZHHeIS/lfc2kNfri4uLf+uwWnsh7G0SUBAa TlVbtuqiN+DZJeRDfuZeAO9Myq7lQJE5dfpTY6eS5Xr0MXYsQZejgiSUWESGETgK84J+obRb6+g0 hbvSMCfQO5IBg8I1lyjFWe7h16MD+gl8kFVTcwlv9mgnb9psRiEvMzeOGCiUlWyiUJawCf81bIL/ Knhy5taE0+F4U1tZdeVSrlRcqOxGnLIDyQDPszGE+vH7kJCQAKTtc2R19uzZl/MfwXb4PSdMAJVK NqtMQOYJNiEju6+o0PtKS0vbIg1RmzE3mpAXJ5vgS3gUVxvYpUKZG2SQ8Zlsc5yQeYPtnBfUTKlQ BoIHUGWN71hununtMTXXcz7YpFkrHtVSJOGuHIg/hjenHupOqkNnVIh+Enbe6sdEJpAVSnv2oT1H 6ypDSO40OUtsniceUjCbrglDL6PPEQfoCsdIsWFpqvm+FNxkZXDZ7RHc+tiNh9+Nhx9kLStbKwIA CkHOCoOfq01peQybxSI8b/CfwSbkKlDIrF27jd34U15HL9SH7Yhzg6kjBd7v8CcUQ245u02Ady1I 3p4iX1s9OlUWi8+zoLU+i/huNysbx4O0doNEDwp8m5h2+0Q24W9WpjYIl8IW8GQYhfkOm+CfYBNx D0GlvortDREUTPMfXa2L3oC6t73sUiYVlWgO0bpdu8nyxJNU+tgT4v70zFnZwj5+8qS4Tch2NcJ2 Tjf0JwOjMYdAZVny9BZxM9Td98pO52W9+sn2NdONETGe3dEArbDGSCmzevg+1DXI0yq9wVu+vDVs tjYU+mI2UfB72WSggGaxicJMcLtcTzudTtnaZsAvTFsF8K9FZTArj+yL4M+QbW6kIT0MA4VdiPhe gExP7oJLSkr+BF44Cv8aLcJ/xDXw/zPb+Q/l7WtbcbG40QPthL9UMsgs1Kact0A8MkzhWeSsAv+h FW7300hPhj5UYKvL4XgBaf4CvPEYCp5B2N7ih/TwfDvxDC52w//BZVlZspXdEGjJofm+R96uG4ox mQ+5P9SNJthdNNHhNsZ5/Am/CjXUJfgQPR+gZ5nB02fSM3v30ZM7dxtyCDt/1RqRC4yJF/edo+rm BydOnaJFm2tE593EZdza9eH6ANhNpJTZPHxfCpIu/tsChdNdW/1ogD4Dvgpo5BTS5awM0LlHXUvk 8wqYS3z06adaAuP8WCzxeHjg8wqiNQGZTt3oH+CbCEzExJDnHJhXODc+pbm+KFy5Ct0+hhc9PwkY UDcpneDGBNKct/jQwHD9BH40G0LDlvPM/rNmPhFtIjAFFcbUJGHNEp508uqA7TwRZDcmsT4aJ6as UCN+4VhZxMVdqp/Aj2ZDVNR/8TuFn+klY3MjkN9ReB9MaQ6KjD+rc+9HsyMxxcGvidskjKGXj7+j /8bmwa050xtRtfoexK+0k7Ku1Dn344IgdXK+eniacbfGqAmNnlj6tsQnpS5K8zqp9H2INb4zckkl pv9C59iPC47MqclqUvZh2QxqTIfwh6evVGbuWpWR9zedQz9aHPisvZ8Magq8no9OmgFarWKS16iY xCJMfH+lff3woxUiq+C3qqAoX26zmWsltcChyU7inmtpOTTP9uMSl4lZPvPhLix5G1SkCotuVuFR fdAxWNAxOFR0Mt+y0cYoYD/8aE3ImzURnQFXbpLrrabMIJU1k24qdVHC2k20cFctPXboCK07coye PHz0R6V1h4/RqgOv0fUL0Bj5hGQ+8tuSqKDIOLE5bV6JLl0//GhlyJreGY3rS2lgmXnUJjOfpm/Z Rp83ohjZksBXTQcuwKxhEtbBU6a3TJo6k9T0eaQeniYXl/nhR+tAWnY37gxU+lQ5sTxyte8RuJYM 6RgKMTLzW1PWEf064jeY3tSYzIUk7iAmTpXDKH740bLB+jNj0var8ZPlJPz41cYhpm/CvuPv0KKd L9GMjTWUv2EzTdu4mfJgzt68hdbsfYWOnvy3lvx6vPvxx/TkK/tp3tNbJTzHYxK75z3zrFxN/t4n n+gQvuDrogLzC0kljSOVMlFTunGSPiGFbs6fRZGLl9N8xFO9u5ZW7HkZtI+W1+6lsue2U8bj66h9 URldZKpwcFiOYwxo1ASKXvwIFW/ddt40f8tzdF3WNCN9T340ceeVknZajU2Xg01++NFyETf6IdFv ik6im6bk0Sf6AyyNYR0acACrywyPRScyCg0P9tiRpCITSEXEk4pKJBUPPsvwnaFhkXT39EL6dyN6 WkU1W0iFRxlhOB4OMyLOuBrMJPEbY/ixfWiUhPMGXwMSyOo39WTtzz2vJc4f/3znX3T1WHQMnHeO JzqZHnmxVvueH/hi6dvzCuryU5+4w0kYnaVL3w8/Wigi4jIUa66EDqWxi5bq6t0Q2w4dpjbD0ViZ +IM44RF07Zjx9OzB19CZnJFr2j5AB7DwqRq6iGX4nj+WGzyMbpuSgwZT967ilbePU0AMGs4wdAxa pl1ewwsoX3v3BN2cliGaNVePHEtXxyXTHYjr488+0xK6Y+BjVKxdw3GFhFPGIyu1bx32Y4bTduJk ujQiji6OiqerkP6CRg5jPnvwkHRA8px4hpsnZtK9yNs9U/PogWkFdPBf72rJOsxbv4nuzMyidrnT 6Z6cafRT5FPuJ+T81Cf2GxH7lC59P/xooRg0bJmoqQUPpPJnfDWqvJG1fIVxclm+MQPqG0IjXeW0 8/ARH9rx2mt0yzhMy82r1kOG0MWDh9LW/XVfKtr52mG6CJ2BHIhlmdBwChgynCJKLGTfXEOrd+6i lTt20gZM+fcce52OoIM4+/nnOrQv+Ba5wLETjCvd+dDsgMG0Xt9P6Y35T66noPyZ1LdwrlDvGYUU WWqjDz7xnc2whtjNfHi3L+Izn5UJeQ0IH0G1yE99pJRXGppk3vJNEZd16NCDTd1d2RhYNc5mtR6r cLutLpdrtN1qjTWv72PYbbYjSxYvJrvdHshum822GTLG18c0ILMUfM/dkKxBBd6bLqfT4rLbY10O h83pcLzt0Gp2Vqt1MvzlEnTWuUD6n4HXid3eQDoJ8DuKfMUibJrFYvm99hIgbOrSJUsIpkd5iWEv K2uP+D9z2u3jKt3uMfAfmsXLWgD25/Csj/Gzwj6a9UCYX8lfmLBaT5a7XPn84QSk+z7y9AD7eaOy svJnDpst0e10ZiP8GaRRyF+0gP2X+LvaII495W734grEj/DDzU8KIu89UAYnkW4ZKAVlkguefKyJ dVJQvp7rGxFuFPL/lnl3JvzGbdywgZCuqF3CHYL0PuC8sLusrOxGuA+73W48mjsOeStGvk6Adx/7 M2A/iHCeO0QZcLeD3HGUbRH/T5xvpPu6G/GxP5cZwq1Cvvcjv2nl5eWpyLO85Ib9ai4v8wNVsFez zg38L7VbLH3wDNHgPQFiBeh62+jBA9eL6mTXIKp8unFNeUY8Gq2oT6ADEWKdXFatZB6rTHhTF606 wcTuTt1pw0u+U/IC/pBFp25GePNSWf7IFZNW1/SoRnCHxGqfHTrTTQkjRW/HhHQMSZj2sz+HCR5A r771tvb9bmifMQV5D6p7VibkIQCdTu3RugtrTaQ4XL5l83XEZR088MC36RjkPlCbbVdlRcX+6qqq 7agIHi1ABv7sbfiTI2Du44aCP9ppKyt7WHsLEB6/OsUvyHI8PkpjfBEteDu1kytlH1S4z8Dbh8b5 a832AauNIlwx8vYOGoV1Ln+MQAPhH3LY7acQfhA3IpiTtBcrg90D9/uQsbB+MEyPPjSe4dGqysqj leXlnMdFnAbzIXMtnu0QN3i3y7WQnxf+Tb6vYXn4vwzT5x445HMz4j5UXVm5nRs889BYfspxQ9bn sl8T4GcjTx8gPs7TdjTQI0jfoxqLsJMRF9quPQn8x/EM3fDMB80vxIG3yakbqAlunIiLFfykUcL+ AsLJBb8M/oIM4ngJcXbVLAHSyoCcoVTHHR7+S/EA0KH9HPH0Njs7VM828F+P/J7icCJ0XujRe6Wo r3bsTFUYrZvCRKeb+DJh81M7qkMnmrPS+Kzf98XJjz6mHa8eoOVbnyXnhk3kxhS/fNNmKsCS4JaY BDQ6dC5muu07UdjMQh1SdwyxkOlkKP2xNqf5RRxvDJ01h9Sd98hnOj3EX8n5299J3XG3F8HN6QWh 0zPTZEK8Ab37eT5L6I0Ui81QMPSWb4q4rHv0Pqg6hJz3IX9WIUYDO+S02Ubgj/8jjxZckbU3V7r9 qChyZQkq0lMrV6wguEXt1gQaQykqjOeTRLCHQfYTVLoBpaWlfyx3OgehE/gI4fR3mQygMtVAZox2 NoCjtLRtdXX13yHzB+RxHeJcyny4A2H/t23hQkNPvajoWrhPoUO4n90um60j3J5PMHoDeXgWo2QO Pyvi/hOeVdSDOQ0862F0FL+Uywys1lNoXE1uAeuLnY+A/qpZ0ski3G7+dBPHzyP5Wt2IEP94dDgf oaMLQz7bwrwbactJVZTfQrMxMmCPRdpHPDMGq5U//SS3d6Ox9kNHSUjnmNkxQL4b4j+NNCNgvwFx B6O83ke8cikEA+H3wD+N04Z5C88UIcszlw/xDN05HPjRKLePzUseioqKrob7KOJag3C34Zm5s3mn sLDQc8IW4fohLydq9Izs/NC1Z46M2Pd1pDS7U1f1hli/a7fcAC4jI18Q3b4z3RwRg0b9kZYwwO7/ DsMy4e/3GY2Fb/4GbX6prrG+eOg1uhpT86swuv+8fyj9DA0uMDKOPqw3rWfs4JtAzJkFp3tfBwqb Pkv76o4hKk5mE+J/bwfKdFdo3zocevs43TQ8Svylg2vX3iceb7SNS0Te0XFwfCZh5hPQM9jnVnMT KaVWxIvn9JZvivi6/K5BW3Xp/yBAxZBpN1c2zfLBel15vytCQkIuNm8aMWE2mPpoiv99wA1IW1sF 1qxZ4+nUvw3MTuaHQY++vWT6/lA3um1kCp39GqXbBWseJ3U/RlleIvC1/ky8VOBGKaMwTHabfqwu /48HKLWRDiecR/B2DxgNxZRnFX7uAMzRle3cKXDH1RMj+P0d6cbo+IZLibgkPcojDpZDHprS8v4m jLbYjQ7QO19MeJYAdGSNzhj4mxx8F4W3fFPE3//r2Sdfl74ffrRQdO/+E9U/9Kh8i7FbLypcbdy4 83XY+/rrlI9pfn9M6W9PnUhtR48DpYr517ETKCh/Bk2uXOT5SE1T4N0My/qNNKRwHt05Pp3ajhqr 4zHiajsmlR6ckk1JZVZase15OvdFw1OY0jHwVVFB/Yz1OxNr9/P7hl796N70TMpaupxWbN9Bzx84 SK+8+aYQP8PmfS9T9ZatlF61iO7gF6b8zoTfA3B4My6T+obQpaFhtHL7C544TBq+oNgIWz9MfeKX rf0HnUP88h0UP/xo2QiLCONL//iTI/x2f966jbrZtXycPnPWuFCQO7a6iwC9SH9zmbczhzRCnksE tVyTpP0bjcPL/+tIPpMyYoYudT/8aAXgbxiOHEcqfqTswV+bkkZP7H1ZN7+WCznHwNfOjogluca2 pdLo8TCTfHYT/PCjdWDs2MvV6AnLRWeCj+/ysd6YUXTF+Ezq76iUI8Q733iTDpx4r8VQ7dvv0A3Z M4wj0fzV3JZEfLyaLxhJSX9ejR79G13KfvjRijEp+z6VmfO4mpTzuWhcZqHx8bc+uNOor4z0YxPn qeFtPz8scdmwJiWXFX9ULyN3m8rMNj7k74cfrQpK/R8DdfRFMWcPiAAAAABJRU5ErkJggg== --_004_5e5ceee923ea447880f660f699109f85DR1XEXCH02Besetcorp_--

2 1

changing Master Storage Domain
by Giorgio Bersano 05 Jan '18

05 Jan '18

Hello, I've a question regarding Master Storage Domain. I did already search the net without results so I'm asking here. In our production setup (ovirt 4.1.7) we have five iSCSI Data Storage Domains and we unfortunately need to remove the one that is the Master SD. That's not difficult, I know the procedure as I did it in the past: - Move every disk belonging to the MSD to another SD - Put the MSD in maintenance - Detach it then Remove it Another SD is automatically selected as Master and everything should be OK (for the sake of simplicity i did not mention the other operations needed on the storage array and the hosts to phisically remove the LUN). The tricky part is I don't want a random choice, I want to choose which SD becomes the new Master. Is there any specific procedure to obtain this result? TIA, Giorgio.

2 2

[vdsm] status update: running containers alongside VMs
by Francesco Romani 05 Jan '18

05 Jan '18

Hi everyone, I'm happy to share some progress about the former "convirt"[1] project, which aims to let Vdsm containers alongside VMs, on bare metal. In the last couple of months I kept updating the patch series, which is approaching the readiness to be merged in Vdsm. Please read through this mail to see what the patchset can do now, how you could try it *now*, even before it is merged. Everyone is invited to share thoughts and ideas about how this effort could evolve. This will be a long mail; I will amend, enhance and polish the content and make a blog post (on https://mojaves.github.io) to make it easier to consume and to have some easy-to-find documentation. Later on the same content will appear also on the oVirt blog. Happy hacking! +++ # How to try how the experimental container support for Vdsm. Vdsm is gaining *experimental* support to run containers alongside VMs. Vdsm had since long time the ability to manage VMs which run containers, and recently gained support for [atomic guests](http://www.projectatomic.io/blog/2015/01/running-ovirt-guest-agent-as-privileged-container/). With the new support we are describing, you will be able to manage containers with the same, proven infrastructure that let you manage VMs. This feature is currently being developed and it is still not merged in the Vdsm codebase, so some extra work is needed if you want to try it out. We aiming to merge it in the oVirt 4.1.z cycle. ## What works, aka what to expect The basic features are expected to work: 1. Run any docker image on the public docker registry 2. Make the container accessible from the outside (aka not just from localhost) 3. Use file-based storage for persistent volumes ## What does not yet work, aka what NOT to expect Few things are planned and currently under active development: 1. Monitoring. Engine will not get any update from the container besides "VM" status (Up, Down...) One important drawback is that you will not be told the IP of the container from Engine, you will need to connect to the Vdsm host to discover it using standard docker tools. 2. Proper network integration. Some steps still need manual intervention 3. Stability and recovery - it's pre-alpha software after all! :) ## 1. Introduction and prerequisites Trying out container support affects only the host and the Vdsm. Besides add few custom properties (totally safe and supported since early 3.z), there are zero changes required to the DB and to Engine. Nevertheless, we recommend to dedicate one oVirt 4.y environment, or at least one 4.y host, to try out the container feature. To get started, first thing you need is to setup a vanilla oVirt 4.y installation. We will need to make changes to the Vdsm and to the Vdsm host, so hosted engine and/or oVirt node may add extra complexity, better to avoid them at the moment. The reminder of this tutorial assumes you are using two hosts, one for Vdsm (will be changed) and one for Engine (will require zero changes); furthermore, we assume the Vdsm host is running on CentOS 7.y. We require: - one test host for Vdsm. This host need to have one NIC dedicated to containers. We will use the [docker macvlan driver](https://raesene.github.io/blog/2016/07/23/Docker-MacVLAN/), so this NIC *must not be* part of one bridge. - docker >= 1.12 - oVirt >= 4.0.5 (Vdsm >= 4.18.15) - CentOS >= 7.2 Docker >= 1.12 is avaialable for download [here](https://docs.docker.com/engine/installation/linux/centos/) Caveats: 1. docker from official rpms conflicts con docker from CentOS, and has a different package name: docker-engine vs docker. Please note that the kubernetes package from CentOS, for example, require 'docker', not 'docker-engine'. 2. you may want to replace the default service file [with this one](https://github.com/mojaves/convirt/blob/master/patches/centos72/system… and to use this [sysconfig file](https://github.com/mojaves/convirt/blob/master/patches/centos72/syste…. Here I'm just adding the storage options docker requires, much like the CentOS docker is configured. Configuring docker like this can save you some troubleshooting, especially if you had docker from CentOS installed on the testing box. ## 2. Patch Vdsm to support containers You need to patch and rebuild Vdsm. Fetch [this patch](https://github.com/mojaves/convirt/blob/master/patches/vdsm/4.18.15.… and apply it against Vdsm 4.18.15.1. Vdsm 4.18.15.{1,2,...} are supported as well. Rebuild Vdsm and reinstall on your box. [centos 7.2 packages are here](https://github.com/mojaves/convirt/tree/master/rpms/centos72) Make sure you install the Vdsm command line client (vdsm-cli) Restart *both* Vdsm and Supervdsm, make sure Engine still works flawlessly with patched Vdsm. This ensure that no regression is introduced, and that your environment can run VMs just as before. Now we can proceed adding the container support. start docker: # systemctl start docker-engine (optional) # systemctl enable docker-engine Restart Vdsm again # systemctl restart vdsm Now we can check if Vdsm detects docker, so you can use it: still on the same Vdsm host, run $ vdsClient -s 0 getVdsCaps | grep containers containers = ['docker', 'fake'] This means this Vdsm can run containers using 'docker' and 'fake' runtimes. Ignore the 'fake' runtime; as the name suggests, is a test driver, kinda like /dev/null. Now we need to make sure the host network configuration is fine. ### 2.1. Configure the docker network for Vdsm PLEASE NOTE that the suggested network configuration assumes that * you have one network, `ovirtmgmt` (the default one) you use for everything * you have one Vdsm host with at least two NICs, one bound to the `ovirtmgmt` network, and one spare _This step is not yet automated by Vdsm_, so manual action is needed; Vdsm will take care of this automatically in the future. You can use [this helper script](https://github.com/mojaves/convirt/blob/master/patches/vdsm/cont-se…, which reuses the Vdsm libraries. Make sure you have patched Vdsm to support container before to use it. Let's review what the script needs: # ./cont-setup-net -h usage: cont-setup-net [-h] [--name [NAME]] [--bridge [BRIDGE]] [--interface [INTERFACE]] [--gateway [GATEWAY]] [--subnet [SUBNET]] [--mask [MASK]] optional arguments: -h, --help show this help message and exit --name [NAME] network name to use --bridge [BRIDGE] bridge to use --interface [INTERFACE] interface to use --gateway [GATEWAY] address of the gateway --subnet [SUBNET] subnet to use --mask [MASK] netmask to use So we need to feed --name, --interface, --gateway, --subnet and optionally --mask (default, /24, is often fine). For my case the default mask was indeed fine, so I used the script like this: # ./cont-setup-net --name ovirtmgmt --interface enp3s0 --gateway 192.168.1.1 --subnet 192.168.1.0 Thhis is the output I got: DEBUG:virt.containers.runtime:configuring runtime 'docker' DEBUG:virt.containers.command:* calling ['/bin/docker', 'network', 'inspect', 'ovirtmgmt'] Error: No such network: ovirtmgmt DEBUG:virt.containers.command:* called ['/bin/docker', 'network', 'inspect', 'ovirtmgmt'] DEBUG:virt.containers.runtime.Docker:config: cannot load 'ovirtmgmt', ignored DEBUG:virt.containers.command:* calling ['/bin/docker', 'network', 'create', '-d', 'macvlan', '--subnet=192.168.1.0/24', '--gateway=192.168.1.1', '--ip-range=192.168.1.0/24', '-o', 'parent=enp3s0', 'ovirtmgmt'] DEBUG:virt.containers.command:* called ['/bin/docker', 'network', 'create', '-d', 'macvlan', '--subnet=192.168.1.0/24', '--gateway=192.168.1.1', '--ip-range=192.168.1.0/24', '-o', 'parent=enp3s0', 'ovirtmgmt'] DEBUG:virt.containers.runtime:configuring runtime 'fake' You can clearly see what the script did, and why it needed the root privileges. Let's deoublecheck using the docker tools: # docker network ls NETWORK ID NAME DRIVER SCOPE 91535f3425a8 bridge bridge local d42f7e5561b5 host host local 621ab6dd49b1 none null local f4b88e4a67eb ovirtmgmt macvlan local # docker network inspect ovirtmgmt [ { "Name": "ovirtmgmt", "Id": "f4b88e4a67ebb7886ec74073333d613b1893272530cae4d407c95ab587c5fea1", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.1.0/24", "IPRange": "192.168.1.0/24", "Gateway": "192.168.1.1" } ] }, "Internal": false, "Containers": {}, "Options": { "parent": "enp3s0" }, "Labels": {} } ] Looks good! the host configuration is completed. Let's move to the Engine side. ## 3. Configure Engine As mentioned above, we need now to configure Engine. This boils down to: Add a few custom properties for VMs: In case you were already using custom properties, you need to amend the command line to not overwrite your existing ones. # engine-config -s UserDefinedVMProperties='volumeMap=^[a-zA-Z_-]+:[a-zA-Z_-]+$;containerImage=^[a-zA-Z]+(://|)[a-zA-Z]+$;containerType=^(docker|rkt)$' --cver=4.0 It is worth stressing that while the variables are container-specific, the VM custom properties are totally inuntrusive and old concept in oVirt, so this step is totally safe. Now restart Engine to let it use the new variables: # systemctl restart ovirt-engine The next step is actually configure one "container VM" and run it. ## 4. Create the container "VM" To finally run a container, you start creating a VM much like you always did, with few changes 1. most of the hardware-related configuration isn't relevant for container "VMs", besides cpu share and memory limits; this will be better documented in the future; unneeded configuration will just be ignored 2. You need to set some custom properties for your container "VM". Those are actually needed to enable the container flow, and they are documented in the next section. You *need* to set at least `containerType` and `containerImage`. ### 4.2. Custom variables for container support The container support needs some custom properties to be properly configured: 1. `containerImage` (*needed* to enable the container system). Just select the target image you want to run. You can use the standard syntax of the container runtimes. 2. `containerType` (*needed* to enable the container system). Selects the container runtime you want to use. All the available options are always showed. Please note that unavailable container options are not yet grayed out. If you *do not* have rkt support on your host, you still can select it, but it won't work. 3. `volumeMap` key:value like. You can map one "VM" disk (key) to one container volume (value), to have persistent storage. Only file-based storage is supported. Example configuration: `containerImage = redis` `containerType = docker` `volumeMap = vda:data` (this may not be needed, and the volume label is just for illustrative purposes) ### 4.2. A little bit of extra work: preload the images on the Vdsm host This step is not needed by the flow, and will be handled by oVirt in the future. The issue is how the container image are handled. They are stored by the container management system (rkt, docker) on each host, and they are not pre-downloaded. To shorten the duration of the first boot, you are advised to pre-download the image(s) you want to run. For example ## on the Vdsm host you want to use with containers # docker pull redis ## 5. Run the container "VM" You are now all set to run your "VM" using oVirt Engine, just like any existing VM. Some actions doesn't make sense for a container "VM", like live migration. Engine won't stop you to try to do those actions, but they will fail gracefully using the standard errors. ## 6. Next steps What to expect from this project in the future? For the integration with Vdsm, we want to fix the existing known issues, most notably: * add proper monitoring/reporting of the container health * ensure proper integration of the container image store with oVirt storage management * streamline the network configuration What is explicitely excluded yet is any Engine change. This is a Vdsm-only change at the moment, so fixing the following is currently unplanned: * First and foremost, Engine will not distinguish between real VMs and container VMs. Actions unavailable to container will not be hidden from UI. Same for monitoring and configuration data, which will be ignored. * Engine is NOT aware of the volumes one container can use. You must inspect and do the mapping manually. * Engine is NOT aware of the available container runtimes. You must select it carefully Proper integration with Engine may be added in the future once this feature exits from the experimental/provisional stage. Thanks for reading, make sure to share your thoughts on the oVirt mailing lists! +++ [1] we keep calling it that way _only_ internally, because it's a short name we are used to. After the merge/once we release it, we will use a different name, like "vdsm-containers" or something like it. -- Francesco Romani Red Hat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

3 2

Configuring Gluster
by carl langlois 05 Jan '18

05 Jan '18

Hi all, I am in the process of adding GlusterFS storage to our already ovirt setup. I am using 4.1.8 for now but plan to upgrade to 4.2 later. I need your suggestions on what is the best approach for replacing my NFS storage to a GlusterFS storage.. Thanks for all your inputs. Carl

2 1