- Users - oVirt List Archives

Gluster storage question
by Bartosiak-Jentys, Chris 11 Feb '17

11 Feb '17

Hello list, Just wanted to get your opinion on my ovirt home lab setup. While this is not a production setup I would like it to run relatively reliably so please tell me if the following storage configuration is likely to result in corruption or just bat s**t insane. I have a 3 node hosted engine setup, VM data store and engine data store are both replica 3 gluster volumes (one brick on each host). I do not want to run all 3 hosts 24/7 due to electricity costs, I only power up the larger hosts (2 Dell R710's) when I need additional resources for VM's. I read about using CTDB and floating/virtual IP's to allow the storage mount point to transition between available hosts but after some thought decided to go about this another, simpler, way: I created a common hostname for the storage mount points: gfs-data and gfs-engine On each host I edited /etc/hosts file to have these hostnames resolve to each hosts IP i.e. on host1 gfs-data & gfs-engine --> host1 IP on host2 gfs-data & gfs-engine --> host2 IP etc. In ovirt engine each storage domain is mounted as gfs-data:/data and gfs-engine:/engine My thinking is that this way no matter which host is up and acting as SPM it will be able to mount the storage as its only dependent on that host being up. I changed gluster options for server-quorum-ratio so that the volumes remain up even if quorum is not met, I know this is risky but its just a lab setup after all. So, any thoughts on the /etc/hosts method to ensure the storage mount point is always available? Is data corruption more or less inevitable with this setup? Am I insane ;) ? Thanks,

2 4

Trying oVirt 4.1
by Andy Michielsen 11 Feb '17

11 Feb '17

Hello all, I was trying to give the latest oVirt a go and install it on my KVM system before committing it on any hardware. The installation went fine. When logging on into the node https://<node>:9090 I wanted to install an hosted engine but I get this messages Failed to execute stage 'Environment setup': [Errno 2] No such file or directory: '/etc/iscsi/initiatorname.iscsi' Hosted Engine deployment failed But I must admit I have not set up iscsi nor do I want to. Maybe local, nfs or glusterfs. What is the way to do this properly ? Kind regards.

2 1

Optimizations for VoIP VM
by Jim Kusznir 11 Feb '17

11 Feb '17

Hello: I set up a FreeSwitch-based VoIP server as a host on my cluster, and am having audio problems. I'm not 100% sure if its virtualization related or network related yet. But I would like to optimize my VM for VoIP (or rather, tell Ovirt all the "right settings" to optimize that VM to VoIP). Does anyone have any specific suggestions? Are there known issues with VoIP on Ovirt-managed clusters? (I know well reputed companies that sell VoIP server virtual hosting and guarantee the performance, so I know VoIP Virtualization is possible, just need to know if its recommended with Ovirt, and if so what do I need to do to give it the best chance of success?) Thanks! --Jim

4 5

oVirt maintence "best practices"
by Jim Kusznir 11 Feb '17

11 Feb '17

hello: Now that I've had my ovirt cluster running for about a month and a half, I am realizing I don't necessarily know the best practices for keeping it up. I've been seeing the notices in the ovirt hosts screen showing that there are updates waiting for the hosts, and I'll put them in maintence mode one at a time and apply the updates. What about the engine itself? Is it recommended/safe to log into the engine and just run "yum update"? Is there other procedures I should be doing? My oVirt cluster is a 3 node cluster with gluster, running on each node. Thanks! --Jim

2 1

Re: [ovirt-users] Error attempting to upload an ISO image
by Yaniv Kaul 10 Feb '17

10 Feb '17

On Feb 10, 2017 9:07 PM, "Berger, Sandy" <SBERGER(a)qg.com> wrote: I originally installed a hosted engine on oVirt 4.0.x. Since then I’ve updated to 4.1. engine-upgrade-check shows no updates available: [root@waovccm1 ~]# engine-upgrade-check VERB: queue package ovirt-engine-setup for update VERB: Building transaction VERB: Empty transaction VERB: Transaction Summary: No upgrade However, “yum update” shows several updates available (see below) including python-ovirt-engine-sdk4 x86_64 4.1.0-1.el7.centos. The installed version of that RPM is currently 4.0.4-1.el7.centos.x86_64. Is it safe to run a yum update on the hosted engine? Why wouldn’t engine-upgrade-check show a necessary update like that? Should be OK to run. I'm not sure but I think the ISO uploader should depend on a newer pyhton-ovirt-sdk. Y. Thanks much for your assistance! [root@waovccm1 ~]# yum update Loaded plugins: fastestmirror, versionlock Loading mirror speeds from cached hostfile * base: repos.forethought.net * extras: centos.mbni.med.umich.edu * ovirt-4.1: mirrors.ibiblio.org * ovirt-4.1-epel: mirror.steadfast.net * updates: mirror.atlanticmetro.net Resolving Dependencies --> Running transaction check ---> Package NetworkManager.x86_64 1:1.4.0-13.el7_3 will be updated ---> Package NetworkManager.x86_64 1:1.4.0-14.el7_3 will be an update ---> Package NetworkManager-libnm.x86_64 1:1.4.0-13.el7_3 will be updated ---> Package NetworkManager-libnm.x86_64 1:1.4.0-14.el7_3 will be an update ---> Package NetworkManager-team.x86_64 1:1.4.0-13.el7_3 will be updated ---> Package NetworkManager-team.x86_64 1:1.4.0-14.el7_3 will be an update ---> Package NetworkManager-tui.x86_64 1:1.4.0-13.el7_3 will be updated ---> Package NetworkManager-tui.x86_64 1:1.4.0-14.el7_3 will be an update ---> Package NetworkManager-wifi.x86_64 1:1.4.0-13.el7_3 will be updated ---> Package NetworkManager-wifi.x86_64 1:1.4.0-14.el7_3 will be an update ---> Package antlr-tool.noarch 0:2.7.7-30.el7 will be updated ---> Package antlr-tool.noarch 0:2.7.7-35.el7 will be an update ---> Package bind-libs.x86_64 32:9.9.4-38.el7_3 will be updated ---> Package bind-libs.x86_64 32:9.9.4-38.el7_3.1 will be an update ---> Package bind-libs-lite.x86_64 32:9.9.4-38.el7_3 will be updated ---> Package bind-libs-lite.x86_64 32:9.9.4-38.el7_3.1 will be an update ---> Package bind-license.noarch 32:9.9.4-38.el7_3 will be updated ---> Package bind-license.noarch 32:9.9.4-38.el7_3.1 will be an update ---> Package bind-utils.x86_64 32:9.9.4-38.el7_3 will be updated ---> Package bind-utils.x86_64 32:9.9.4-38.el7_3.1 will be an update ---> Package device-mapper.x86_64 7:1.02.135-1.el7_3.1 will be updated ---> Package device-mapper.x86_64 7:1.02.135-1.el7_3.2 will be an update ---> Package device-mapper-libs.x86_64 7:1.02.135-1.el7_3.1 will be updated ---> Package device-mapper-libs.x86_64 7:1.02.135-1.el7_3.2 will be an update ---> Package firewalld.noarch 0:0.4.3.2-8.el7 will be updated ---> Package firewalld.noarch 0:0.4.3.2-8.1.el7_3 will be an update ---> Package firewalld-filesystem.noarch 0:0.4.3.2-8.el7 will be updated ---> Package firewalld-filesystem.noarch 0:0.4.3.2-8.1.el7_3 will be an update ---> Package java-1.8.0-openjdk.x86_64 1:1.8.0.111-2.b15.el7_3 will be updated ---> Package java-1.8.0-openjdk.x86_64 1:1.8.0.121-0.b13.el7_3 will be an update ---> Package java-1.8.0-openjdk-devel.x86_64 1:1.8.0.111-2.b15.el7_3 will be updated ---> Package java-1.8.0-openjdk-devel.x86_64 1:1.8.0.121-0.b13.el7_3 will be an update ---> Package java-1.8.0-openjdk-headless.x86_64 1:1.8.0.111-2.b15.el7_3 will be updated ---> Package java-1.8.0-openjdk-headless.x86_64 1:1.8.0.121-0.b13.el7_3 will be an update ---> Package kernel.x86_64 0:3.10.0-514.6.1.el7 will be installed ---> Package kernel-tools.x86_64 0:3.10.0-514.2.2.el7 will be updated ---> Package kernel-tools.x86_64 0:3.10.0-514.6.1.el7 will be an update ---> Package kernel-tools-libs.x86_64 0:3.10.0-514.2.2.el7 will be updated ---> Package kernel-tools-libs.x86_64 0:3.10.0-514.6.1.el7 will be an update ---> Package kpartx.x86_64 0:0.4.9-99.el7 will be updated ---> Package kpartx.x86_64 0:0.4.9-99.el7_3.1 will be an update ---> Package libnl3.x86_64 0:3.2.28-2.el7 will be updated ---> Package libnl3.x86_64 0:3.2.28-3.el7_3 will be an update ---> Package libnl3-cli.x86_64 0:3.2.28-2.el7 will be updated ---> Package libnl3-cli.x86_64 0:3.2.28-3.el7_3 will be an update ---> Package libpciaccess.x86_64 0:0.13.4-2.el7 will be updated ---> Package libpciaccess.x86_64 0:0.13.4-3.el7_3 will be an update ---> Package libsemanage.x86_64 0:2.5-4.el7 will be updated ---> Package libsemanage.x86_64 0:2.5-5.1.el7_3 will be an update ---> Package libsemanage-python.x86_64 0:2.5-4.el7 will be updated ---> Package libsemanage-python.x86_64 0:2.5-5.1.el7_3 will be an update ---> Package libtiff.x86_64 0:4.0.3-25.el7_2 will be updated ---> Package libtiff.x86_64 0:4.0.3-27.el7_3 will be an update ---> Package ntp.x86_64 0:4.2.6p5-25.el7.centos will be updated ---> Package ntp.x86_64 0:4.2.6p5-25.el7.centos.1 will be an update ---> Package ntpdate.x86_64 0:4.2.6p5-25.el7.centos will be updated ---> Package ntpdate.x86_64 0:4.2.6p5-25.el7.centos.1 will be an update ---> Package openssh.x86_64 0:6.6.1p1-31.el7 will be updated ---> Package openssh.x86_64 0:6.6.1p1-33.el7_3 will be an update ---> Package openssh-clients.x86_64 0:6.6.1p1-31.el7 will be updated ---> Package openssh-clients.x86_64 0:6.6.1p1-33.el7_3 will be an update ---> Package openssh-server.x86_64 0:6.6.1p1-31.el7 will be updated ---> Package openssh-server.x86_64 0:6.6.1p1-33.el7_3 will be an update ---> Package ovirt-guest-agent-common.noarch 0:1.0.12-4.el7 will be updated ---> Package ovirt-guest-agent-common.noarch 0:1.0.13-1.20161220085008.git165fff1.el7.centos will be an update ---> Package ovirt-imageio-common.noarch 0:0.4.0-1.el7 will be updated ---> Package ovirt-imageio-common.noarch 0:1.0.0-1.el7 will be an update ---> Package ovirt-imageio-proxy.noarch 0:0.4.0-0.201608310602.gita9b573b.el7.centos will be updated ---> Package ovirt-imageio-proxy.noarch 0:1.0.0-0.201701151456.git89ae3b4.el7.centos will be an update ---> Package ovirt-setup-lib.noarch 0:1.0.2-1.el7.centos will be updated ---> Package ovirt-setup-lib.noarch 0:1.1.0-1.el7.centos will be an update ---> Package policycoreutils.x86_64 0:2.5-9.el7 will be updated ---> Package policycoreutils.x86_64 0:2.5-11.el7_3 will be an update ---> Package policycoreutils-python.x86_64 0:2.5-9.el7 will be updated ---> Package policycoreutils-python.x86_64 0:2.5-11.el7_3 will be an update ---> Package python-firewall.noarch 0:0.4.3.2-8.el7 will be updated ---> Package python-firewall.noarch 0:0.4.3.2-8.1.el7_3 will be an update ---> Package python-ovirt-engine-sdk4.x86_64 0:4.0.4-1.el7.centos will be updated ---> Package python-ovirt-engine-sdk4.x86_64 0:4.1.0-1.el7.centos will be an update ---> Package python-perf.x86_64 0:3.10.0-514.2.2.el7 will be updated ---> Package python-perf.x86_64 0:3.10.0-514.6.1.el7 will be an update ---> Package python2-crypto.x86_64 0:2.6.1-10.el7 will be updated ---> Package python2-crypto.x86_64 0:2.6.1-13.el7 will be an update ---> Package python2-paramiko.noarch 0:1.16.1-1.el7 will be updated ---> Package python2-paramiko.noarch 0:1.16.1-2.el7 will be an update ---> Package selinux-policy.noarch 0:3.13.1-102.el7_3.7 will be updated ---> Package selinux-policy.noarch 0:3.13.1-102.el7_3.13 will be an update ---> Package selinux-policy-targeted.noarch 0:3.13.1-102.el7_3.7 will be updated ---> Package selinux-policy-targeted.noarch 0:3.13.1-102.el7_3.13 will be an update ---> Package unboundid-ldapsdk.noarch 0:3.0.0-1.el7 will be updated ---> Package unboundid-ldapsdk.noarch 0:3.2.0-1.el7 will be an update ---> Package xfsprogs.x86_64 0:4.5.0-8.el7 will be updated ---> Package xfsprogs.x86_64 0:4.5.0-9.el7_3 will be an update --> Finished Dependency Resolution Dependencies Resolved ============================================================ ==================== Package Arch Version Repository Size ============================================================ ==================== Installing: kernel x86_64 3.10.0-514.6.1.el7 updates 37 M Updating: NetworkManager x86_64 1:1.4.0-14.el7_3 updates 2.5 M NetworkManager-libnm x86_64 1:1.4.0-14.el7_3 updates 442 k NetworkManager-team x86_64 1:1.4.0-14.el7_3 updates 146 k NetworkManager-tui x86_64 1:1.4.0-14.el7_3 updates 222 k NetworkManager-wifi x86_64 1:1.4.0-14.el7_3 updates 175 k antlr-tool noarch 2.7.7-35.el7 centos-ovirt-common-candidate 357 k bind-libs x86_64 32:9.9.4-38.el7_3.1 updates 1.0 M bind-libs-lite x86_64 32:9.9.4-38.el7_3.1 updates 729 k bind-license noarch 32:9.9.4-38.el7_3.1 updates 83 k bind-utils x86_64 32:9.9.4-38.el7_3.1 updates 202 k device-mapper x86_64 7:1.02.135-1.el7_3.2 updates 269 k device-mapper-libs x86_64 7:1.02.135-1.el7_3.2 updates 333 k firewalld noarch 0.4.3.2-8.1.el7_3 updates 386 k firewalld-filesystem noarch 0.4.3.2-8.1.el7_3 updates 44 k java-1.8.0-openjdk x86_64 1:1.8.0.121-0.b13.el7_3 updates 232 k java-1.8.0-openjdk-devel x86_64 1:1.8.0.121-0.b13.el7_3 updates 9.7 M java-1.8.0-openjdk-headless x86_64 1:1.8.0.121-0.b13.el7_3 updates 31 M kernel-tools x86_64 3.10.0-514.6.1.el7 updates 4.0 M kernel-tools-libs x86_64 3.10.0-514.6.1.el7 updates 3.9 M kpartx x86_64 0.4.9-99.el7_3.1 updates 67 k libnl3 x86_64 3.2.28-3.el7_3 updates 278 k libnl3-cli x86_64 3.2.28-3.el7_3 updates 160 k libpciaccess x86_64 0.13.4-3.el7_3 updates 26 k libsemanage x86_64 2.5-5.1.el7_3 updates 144 k libsemanage-python x86_64 2.5-5.1.el7_3 updates 104 k libtiff x86_64 4.0.3-27.el7_3 updates 170 k ntp x86_64 4.2.6p5-25.el7.centos.1 updates 547 k ntpdate x86_64 4.2.6p5-25.el7.centos.1 updates 85 k openssh x86_64 6.6.1p1-33.el7_3 updates 438 k openssh-clients x86_64 6.6.1p1-33.el7_3 updates 642 k openssh-server x86_64 6.6.1p1-33.el7_3 updates 440 k ovirt-guest-agent-common noarch 1.0.13-1.20161220085008. git165fff1.el7.centos ovirt-4.1 67 k ovirt-imageio-common noarch 1.0.0-1.el7 centos-ovirt41-candidate 22 k ovirt-imageio-proxy noarch 1.0.0-0.201701151456.git89ae3b4.el7.centos ovirt-4.1 41 k ovirt-setup-lib noarch 1.1.0-1.el7.centos ovirt-4.1 19 k policycoreutils x86_64 2.5-11.el7_3 updates 841 k policycoreutils-python x86_64 2.5-11.el7_3 updates 445 k python-firewall noarch 0.4.3.2-8.1.el7_3 updates 301 k python-ovirt-engine-sdk4 x86_64 4.1.0-1.el7.centos ovirt-4.1 406 k python-perf x86_64 3.10.0-514.6.1.el7 updates 4.0 M python2-crypto x86_64 2.6.1-13.el7 ovirt-4.1-epel 476 k python2-paramiko noarch 1.16.1-2.el7 ovirt-4.1-epel 258 k selinux-policy noarch 3.13.1-102.el7_3.13 updates 414 k selinux-policy-targeted noarch 3.13.1-102.el7_3.13 updates 6.4 M unboundid-ldapsdk noarch 3.2.0-1.el7 centos-ovirt41-candidate 1.9 M xfsprogs x86_64 4.5.0-9.el7_3 updates 895 k Transaction Summary ============================================================ ==================== Install 1 Package Upgrade 46 Packages Total download size: 113 M Is this ok [y/d/N]: n Exiting on user command Your transaction was saved, rerun it with: yum load-transaction /tmp/yum_save_tx.2017-02-10.13-02.zcwZWT.yumtx *From:* Yaniv Kaul [mailto:ykaul@redhat.com] *Sent:* Friday, February 10, 2017 12:55 PM *To:* Berger, Sandy <SBERGER(a)qg.com> *Cc:* Ovirt Users <users(a)ovirt.org> *Subject:* Re: [ovirt-users] Error attempting to upload an ISO image On Feb 10, 2017 6:47 PM, "Berger, Sandy" <SBERGER(a)qg.com> wrote: After the 4.1 upgrade, I’m getting the following results attempting to upload an ISO image: [root@waovccm1 ~]# ovirt-iso-uploader --iso-domain=waISOLibrary upload slb.iso Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): ERROR: v4 is not a valid StorageFormat Can you ensure the 4.1 python SDK is installed? I think it is 4.1.24 and above that has it. Y. INFO: Use the -h option to see usage. I was able to manually copy the file to the correct directory on the NFS server but can’t get the utility to work properly. *Sandy Berger * *IT - EUX* Quad/Graphics *Performance* through *Innovation* Sussex, Wisconsin 414.566.2123 <(414)%20566-2123> phone 414.566.4010 <(414)%20566-4010>/2123 pager/PIN sandy.berger(a)qg.com www.QG.com <http://www.qg.com/> Follow Us: Facebook <http://www.qg.com/social1> | Twitter <http://www.qg.com/social2> | LinkedIn <http://www.qg.com/social3> | YouTube <http://www.qg.com/social4> _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

1 0

Error attempting to upload an ISO image
by Berger, Sandy 10 Feb '17

10 Feb '17

--_000_DM5PR05MB3161E920F37BD052F9CC85A4D5440DM5PR05MB3161namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable After the 4.1 upgrade, I'm getting the following results attempting to uplo= ad an ISO image: [root@waovccm1 ~]# ovirt-iso-uploader --iso-domain=3DwaISOLibrary upload sl= b.iso Please provide the REST API password for the admin@internal oVirt Engine us= er (CTRL+D to abort): ERROR: v4 is not a valid StorageFormat INFO: Use the -h option to see usage. I was able to manually copy the file to the correct directory on the NFS se= rver but can't get the utility to work properly. Sandy Berger IT - EUX Quad/Graphics Performance through Innovation Sussex, Wisconsin 414.566.2123 phone 414.566.4010/2123 pager/PIN sandy.berger(a)qg.com<mailto:sandy.berger@qg.com> www.QG.com<http://www.qg.com/> Follow Us: Facebook<http://www.qg.com/social1> | Twitter<http://www.qg.com/= social2> | LinkedIn<http://www.qg.com/social3> | YouTube<http://www.qg.com/= social4> --_000_DM5PR05MB3161E920F37BD052F9CC85A4D5440DM5PR05MB3161namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <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"> After the 4.1 upgrade, I’m getting the followi= ng results attempting to upload an ISO image:<o:p></o:p> <o:p> </o:p> = [root@waovccm1 ~]# ovirt-iso-uploader --iso-domain=3DwaISOLibrary upload sl= b.iso<o:p></o:p> = Please provide the REST API password for the admin@internal oVirt Engine us= er (CTRL+D to abort):<o:p></o:p> = ERROR: v4 is not a valid StorageFormat<o:p></o:p> = INFO: Use the -h option to see usage.<o:p></o:p> <o:p> </o:p> I was able to manually copy the file to the correct = directory on the NFS server but can’t get the utility to work properl= y.<o:p></o:p> <o:p> </o:p> Sandy Berger <o:p></o:p> IT - EUX<o:p= ></o:p>  <o:p></o:p> Quad/Graphics<o:p><= /o:p> Performance&nb= sp;through Innovation<o:= p></o:p>  <o:p></o:p></= span> Sussex, Wisconsin<o= :p></o:p> 414.566.2123 phone<= o:p></o:p> 414.566.4010/2123 pager/PIN<span= style=3D"font-size:10.5pt;font-family:"Arial",sans-serif;color:#= 444444"><o:p></o:p>  <= /span><o:p></o:p> <a href=3D"mailto:sandy.berger@qg.com"><s= pan style=3D"color:blue">sandy.berger(a)qg.com</a><o:p></o:p> <a href=3D"http://www.qg.com/">www.QG.com</a><o:p></o:p></span= > <o:p> </o:p> </div> Follow Us: <a href=3D"http://www.qg.com/social1">Facebook</a> | <a href=3D"= http://www.qg.com/social2"> Twitter</a> | <a href=3D"http://www.qg.com/social3">LinkedIn</a> | <a href= =3D"http://www.qg.com/social4"> YouTube</a> </body> </html> --_000_DM5PR05MB3161E920F37BD052F9CC85A4D5440DM5PR05MB3161namp_--

3 3

Re: [ovirt-users] Manually starting VMs via vdsClient (HE offline)
by Yaniv Kaul 10 Feb '17

10 Feb '17

On Feb 10, 2017 3:21 PM, "Nathanaël Blanchet" <blanchet(a)abes.fr> wrote: Le 09/02/2017 à 19:48, Yaniv Kaul a écrit : On Thu, Feb 9, 2017 at 6:00 PM, Doug Ingham <dougti(a)gmail.com> wrote: > > > On 9 February 2017 at 12:03, Dan Yasny <dyasny(a)gmail.com> wrote: > >> >> On Thu, Feb 9, 2017 at 9:55 AM, Doug Ingham <dougti(a)gmail.com> wrote: >> >>> Hi Dan, >>> >>> On 8 February 2017 at 18:26, Dan Yasny <dyasny(a)gmail.com> wrote: >>>> >>>> >>>> But seriously, above all, I'd recommend you backup the engine (it comes >>>> with a utility) often and well. I do it via cron every hour in production, >>>> keeping a rotation of hourly and daily backups, just in case. It doesn't >>>> take much space or resources, but it's more than just best practice - that >>>> database is the summary of the entire setup. >>>> >>>> >>> If you don't mind, may I ask what process you use for backing up your >>> engine? If you use HE, do you keep one server dedicated to just that VM? >>> I've not had that particular issue in the restore process yet, however I >>> read that it's recommended the HE host is free of virtual load before the >>> backup takes place. And as they need to be done frequently, I'm reading >>> that as a dedicated host... >>> >>> >> If you use a dedicated host, you might as well abandon self hosted. HE is >> nice for small setups with the HA built in for extra fun, but once you >> scale, it might not be able to cope and you'll need real hardware. You're >> running a heavy-ish java engine plus two databases after all. >> > I'd be interested to know what type of scale needs a real hardware for engine, rather 100 vms or 1000 vms? it may be about the hosts number? It depends on many factors. Just saw someone who is running the engine as a VM on a hefty hardware, and his setup had 50 hosts and 2500 VMs. I don't know all the details and specifically what I'd be interested to know is the underlying storage performance and how it's connected. In any case, as you scale up the system you will need more vCPUs and memory. Lastly, in 4.1 we've made various improvements to the engine and its database usage, so I expect somewhat improved performance and scale. Y. >> So as I said, all I do is add the engine-backup command to cron on the >> engine, and then my backup server comes in and pulls out the files via scp, >> also through cron. Nothing fancy really, but it lets me sleep at night >> > > This particular project has 10 new maxed out servers to back it, and I > don't see it outgrowing that for at least a year or so. It's hardly a full > DC. > I presume the DB will become the heaviest part of the load, and I'm > already planning a separate high I/O environment for dedicated HA DB hosts. > > See the top section of this page: > http://www.ovirt.org/documentation/self-hosted/chap-Backing_ > up_and_Restoring_an_EL-Based_Self-Hosted_Environment > > It seems that I'll always have to keep at least one host free to be able > to avoid restore problems. If not, and I were to keep hourly backups, then > migrating VMs off the host every hour would just be a pain. > I don't see the point in an hourly backup. Of what? The DB? The VM? What storage will it be based on? I suggest revising the strategy. > > > -- > Doug > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > _______________________________________________ Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14blanchet(a)abes.fr _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

1 0

libvirtError: Cannot get interface MTU
by Tyson Landon 10 Feb '17

10 Feb '17

I am new to Ovirt and have a test cluster running with 2 hosts. I have errors when live migrating that started after I installed a new NIC in one host. Live migrate was working fine before the changes. The vdsm log shows the errors below depending on if i am migrating from host1 or host2. Running ovs-vsctl list-br shows that the bridge exists. Ip a shows the interface is down. I do not know what a vdsm bridge is for or if the server just needs to restart a service to get things in order again. Have any of you seen this error before and were able to fix it? HOST 1 libvirtError: Cannot get interface MTU on 'vdsmbr_TK4cSEjh': No such device HOST 2 libvirtError: Cannot get interface MTU on 'vdsmbr_vqqOTlrR': No such device HOST 1 ovs-vsctl list-br vdsmbr_3fDBsCCF vdsmbr_TK4cSEjh vdsmbr_VWhs9soF HOST2 ovs-vsctl list-br vdsmbr_YBtJDFGg vdsmbr_qf3gXZdq vdsmbr_vqqOTlrR Thanks Tyson

2 4

Manually starting VMs via vdsClient (HE offline)
by Doug Ingham 10 Feb '17

10 Feb '17

Hi Guys, My Hosted-Engine has failed & it looks like the easiest solution will be to install a new one. Now before I try to re-add the old hosts (still running the guest VMs) & import the storage domain into the new engine, in case things don't go to plan, I want to make sure I'm able to bring up the guests on the hosts manually. The problem is vdsClient is giving me an "Unexpected exception", without much more info as to why it's failing. Any idea? [root@v0 ~]# vdsClient -s 0 list table | grep georep 9d1c3fef-498e-4c20-b124-01364d4d45a8 30455 georep-proxy Down [root@v0 ~]# vdsClient -s 0 continue 9d1c3fef-498e-4c20-b124-01364d4d45a8 Unexpected exception /var/log/vdsm/vdsm.log periodic/1063::WARNING::2017-02-08 17:57:52,532::periodic::276::virt.periodic.VmDispatcher::(__call__) could not run <class 'vdsm.virt.periodic.DriveWatermarkMonitor'> on ['65c9807c-7216-40b3-927c-5fd93bbd42ba', u'9d1c3fef-498e-4c20-b124-01364d4d45a8'] Cheers, -- Doug

4 12

Best way to shutdown and restart hypervisor?
by Gianluca Cecchi 10 Feb '17

10 Feb '17

Hello, what is considered the best way to shutdown and restart an hypervisor, supposing plain CentOS 7 host? For example to cover these scenarios: 1) update host from 4.0 to 4.1 2) planned maintenance to the cabinet where the server is located and take the opportunity to update also OS packages My supposed workflow: - put host into maintenance - yum update on host - shutdown os from inside host (because from power mgmt it is brutal power off / power on) --> should I get any warning from web admin gui in this case, even if the host was in maintenance mode? - power mgmt -> start from webadmin gui (or power on button/virtual button at host side?) Would be advisable to put inside power mgmt functionality some logic about os mgmt, so for example, if action is restart, first try to shutdown OS and only in case of failure power off/power on? Thanks in advance, Gianluca

4 6