<html><body><div style="font-family: georgia,serif; font-size: 12pt; color: #000000"><div>FQDN convention should be following your organizational domain conventions, as long as FQDNS reachable via DNS, should work just fine.</div><div>Normally from the beginning you don't have to edit manually /etc/hosts at all, once your HE-VM getting the same IP from reserved range of DHCP IP addresses and DNS has its FQDN in its records, since your hosts during hosted-engine-deployment will be given already known FQDN of the HE-VM instead of its IP, then hosts will get to HE-VM via DNS.</div><div><br></div><div>Using reserved IP address range advised, as during some time, if you're using IP addresses from dynamic pool, you'll eventually will loose connectivity to your HE-VM, as it's IP will be updated after lease time expires or renewed.</div><div><br></div><div>For repeated HE installations with same FQDN for the engine desired, to get always the same IP address for HE-VM, each time you're deploying it, you will have to write down it's MAC address, so when asked during deployment to provide MAC address for HE-VM, you'll just write manually the same MAC address (that very MAC address, that is already matched in reserved DHCP IP<->MAC pair), this will ensure that your HE-VM will receive then the same IP address from DHCP and will resolve to FQDN in DNS database records.</div><div><br></div><div><br></div><div><span name="x"></span><br>Thanks in advance.<br><div><br></div>Best regards,<br>Nikolai<br>____________________<br>Nikolai Sednev<br>Senior Quality Engineer at Compute team<br>Red Hat Israel<br>34 Jerusalem Road,<br>Ra'anana, Israel 43501<br><div><br></div>Tel: +972 9 7692043<br>Mobile: +972 52 7342734<br>Email: nsednev@redhat.com<br>IRC: nsednev<span name="x"></span><br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Cong Yue" <Cong_Yue@alliedtelesis.com><br><b>To: </b>nsednev@redhat.com, "Yedidyah Bar David" <didi@redhat.com><br><b>Cc: </b>users@ovirt.org<br><b>Sent: </b>Wednesday, December 17, 2014 6:41:54 PM<br><b>Subject: </b>RE: FQDN for vm creating with hosted-engine <br><div><br></div>---<br>FQDN or fully qualified domain name means that you have to reserve in your DNS a name corresponding to IP received by HE VM from DHCP.<br>IP address should be reserved for the VM at DHCP.<br><div><br></div>I advise not to use manual IP to FQDN at your host, as this will lead to many confusions, especially when you'll have more than a single host machine, but you always can configure at your /etc/hosts file the FQDN corresponding to IP address given to HE VM.<br>---<br>Thanks for the explanation. Now I understand what FQDN is for Ovirt. Is there any problem if I do not use the naming convention like aaa.bbb.ccc, but only aaa?<br>Also I am some confused for the above explanation. Here it said the IP for VM is better to be got from DHCP rather than manual IP. If so, do this mean I need to change all /etc/hosts file of all virt nodes to update the IP for the FQDN for engine VM?<br>What is the confusions if I use manual IP rather than DHCP for engine VM?<br><div><br></div>Thanks,<br>Cong<br><div><br></div><br>-----Original Message-----<br>From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of users-request@ovirt.org<br>Sent: Wednesday, December 17, 2014 1:17 AM<br>To: users@ovirt.org<br>Subject: Users Digest, Vol 39, Issue 107<br><div><br></div>Send Users mailing list submissions to<br> users@ovirt.org<br><div><br></div>To subscribe or unsubscribe via the World Wide Web, visit<br> http://lists.ovirt.org/mailman/listinfo/users<br>or, via email, send a message with subject or body 'help' to<br> users-request@ovirt.org<br><div><br></div>You can reach the person managing the list at<br> users-owner@ovirt.org<br><div><br></div>When replying, please edit your Subject line so it is more specific than "Re: Contents of Users digest..."<br><div><br></div><br>Today's Topics:<br><div><br></div> 1. 1. FQDN for vm creating with hosted-engine (Yue, Cong)<br> (Nikolai Sednev)<br><div><br></div><br>----------------------------------------------------------------------<br><div><br></div>Message: 1<br>Date: Wed, 17 Dec 2014 04:16:33 -0500 (EST)<br>From: Nikolai Sednev <nsednev@redhat.com><br>To: users@ovirt.org<br>Subject: [ovirt-users] 1. FQDN for vm creating with hosted-engine<br> (Yue, Cong)<br>Message-ID:<br> <2080226028.11273252.1418807793775.JavaMail.zimbra@redhat.com><br>Content-Type: text/plain; charset="utf-8"<br><div><br></div>FQDN or fully qualified domain name means that you have to reserve in your DNS a name corresponding to IP received by HE VM from DHCP.<br>IP address should be reserved for the VM at DHCP.<br><div><br></div>I advise not to use manual IP to FQDN at your host, as this will lead to many confusions, especially when you'll have more than a single host machine, but you always can configure at your /etc/hosts file the FQDN corresponding to IP address given to HE VM.<br><div><br></div><br><div><br></div><br><div><br></div>Thanks in advance.<br><div><br></div>Best regards,<br>Nikolai<br>____________________<br>Nikolai Sednev<br>Senior Quality Engineer at Compute team Red Hat Israel<br>34 Jerusalem Road,<br>Ra'anana, Israel 43501<br><div><br></div>Tel: +972 9 7692043<br>Mobile: +972 52 7342734<br>Email: nsednev@redhat.com<br>IRC: nsednev<br><div><br></div>----- Original Message -----<br><div><br></div>From: users-request@ovirt.org<br>To: users@ovirt.org<br>Sent: Wednesday, December 17, 2014 1:19:12 AM<br>Subject: Users Digest, Vol 39, Issue 104<br><div><br></div>Send Users mailing list submissions to<br>users@ovirt.org<br><div><br></div>To subscribe or unsubscribe via the World Wide Web, visit http://lists.ovirt.org/mailman/listinfo/users<br>or, via email, send a message with subject or body 'help' to users-request@ovirt.org<br><div><br></div>You can reach the person managing the list at users-owner@ovirt.org<br><div><br></div>When replying, please edit your Subject line so it is more specific than "Re: Contents of Users digest..."<br><div><br></div><br>Today's Topics:<br><div><br></div>1. FQDN for vm creating with hosted-engine (Yue, Cong)<br>2. Server 2012 R2 + Intel Conroe Cluster (Nathan Llaneza)<br>3. alternate method of fencing (Brent Hartzell)<br>4. Re: Don't start vm (Roman Nikolayevich Drovalev)<br><div><br></div><br>----------------------------------------------------------------------<br><div><br></div>Message: 1<br>Date: Tue, 16 Dec 2014 14:44:44 -0800<br>From: "Yue, Cong" <Cong_Yue@alliedtelesis.com><br>To: "users@ovirt.org" <users@ovirt.org><br>Subject: [ovirt-users] FQDN for vm creating with hosted-engine<br>Message-ID:<br><ED08B56256B38842A463A2A0804C5AC0326ACA3F65@svr-ca-exch1.atg.lc><br>Content-Type: text/plain; charset="us-ascii"<br><div><br></div>Hi<br><div><br></div><br><div><br></div>Now I am trying to confirm KVM's HA with ovirt, and doing the walk through as the following guide.<br><div><br></div>http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/<br><div><br></div><br><div><br></div>During the VM setting, FQDN is asked, what FQDN means about? Does it mean the hostname of VM host? In my case, it is compute2-2.<br><div><br></div>The following is my hosts file, my VM host and storage is 10.0.0.92.<br><div><br></div>And I am trying to assign 10.0.0.95 to the hosted VM.<br><div><br></div>---<br><div><br></div>[root@compute2-2 ~]# cat /etc/hosts<br><div><br></div>10.0.0.93 compute2-2 nfs2-2<br><div><br></div>10.0.0.95 ovrit-test<br><div><br></div>127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4<br><div><br></div>::1 localhost localhost.localdomain localhost6 localhost6.localdomain6<br><div><br></div>----<br><div><br></div>Also how I can remove the VM I installed, as for when I try to do hosted-engine --deploy, it shows<br><div><br></div><br><div><br></div>---<br><div><br></div>[root@compute2-2 ~]# hosted-engine --deploy [ INFO ] Stage: Initializing<br><div><br></div>Continuing will configure this host for serving as hypervisor and create a VM where you have to install oVirt Engine afterwards.<br><div><br></div>Are you sure you want to continue? (Yes, No)[Yes]: Yes [ INFO ] Generating a temporary VNC password.<br><div><br></div>[ INFO ] Stage: Environment setup<br><div><br></div>Configuration files: []<br><div><br></div>Log file:<br><div><br></div>/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20141216144036-30j0wk.log<br><div><br></div>Version: otopi-1.3.0 (otopi-1.3.0-1.el7) [ INFO ] Hardware supports virtualization [ INFO ] Bridge ovirtmgmt already created [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ ERROR ] The following VMs has been found: ac4c8d35-ca47-4394-afa8-1180c768128c<br><div><br></div>[ ERROR ] Failed to execute stage 'Environment setup': Cannot setup Hosted Engine with other VMs running [ INFO ] Stage: Clean up [ INFO ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'<br><div><br></div>[ INFO ] Answer file '/etc/ovirt-hosted-engine/answers.conf' has been updated [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination<br><div><br></div>--<br><div><br></div>Thanks,<br><div><br></div>Cong<br><div><br></div><br>________________________________<br>This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.ovirt.org/pipermail/users/attachments/20141216/34bdb2c2/attachment-0001.html><br><div><br></div>------------------------------<br><div><br></div>Message: 2<br>Date: Tue, 16 Dec 2014 18:16:03 -0500<br>From: Nathan Llaneza <ntllaneza573@gmail.com><br>To: users <users@ovirt.org><br>Subject: [ovirt-users] Server 2012 R2 + Intel Conroe Cluster<br>Message-ID:<br><CAMkYohUBA_QVeRHo+yKYm5XTe8JYBemUfTbK4gwzS1WYzpbdCw@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><div><br></div>Hey All,<br><div><br></div>I think I have found a bug in oVirt 3.4.4. We just bought a new server that<br>supports the Conroe CPU model, and I am trying to install Server 2012 R2<br>without luck. I keep getting error code 0x000000C4. The problem is while<br>Windows is still to load into its pre-installation environment it cashes<br>and then immediately resets. This is a continuous loop. I have found a way<br>to install Server 2012 R2. Move the cluster away from the Conroe Family (in<br>my case Penryn). Thanks for all you do.<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.ovirt.org/pipermail/users/attachments/20141216/48265917/attachment-0001.html><br><div><br></div>------------------------------<br><div><br></div>Message: 3<br>Date: Fri, 12 Dec 2014 11:14:40 -0500<br>From: Brent Hartzell <brent.hartzell@outlook.com><br>To: <users@ovirt.org><br>Subject: [ovirt-users] alternate method of fencing<br>Message-ID: <BLU406-EAS4159135A9D7BC80AB172E758D600@phx.gbl><br>Content-Type: text/plain; charset="us-ascii"<br><div><br></div>Is there a way to force oVirt to place a host into maintenance mode<br>automatically when a problem occurs? The problem we have is separate<br>networks for everything:<br><div><br></div><br><div><br></div>2 public nics which are bonded active/backup for internet access<br><div><br></div>4 bonded gigabit nics for our Gluster network<br><div><br></div>1 IPMI<br><div><br></div><br><div><br></div>The ipmi is on a completely different network, not attached to anything else<br>other than a VPN.<br><div><br></div><br><div><br></div>///<br><div><br></div><br><div><br></div>Our cluster servers shared Gluster & hypervisor on the same hosts, which<br>works great however, all are 1U servers so we don't have room for another<br>NIC to dedicate to just an ipmi network connection in addition to the ipmi<br>card itself. Even if the PSU on a host fails, then the ipmi power management<br>is useless anyhow and the VM's on that host will not be moved.<br><div><br></div><br><div><br></div>I've tested putting a host into maintenance mode with running VM's and it<br>will auto-migrate the VM's without issue. Is there a way to make oVirt just<br>force a host into maintenance mode if there's some sort of problem or some<br>other fencing mechanism that will allow the VM's to be migrated to another<br>host?<br><div><br></div><br><div><br></div><br><div><br></div>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.ovirt.org/pipermail/users/attachments/20141212/9db1e791/attachment.html><br><div><br></div>------------------------------<br><div><br></div>Message: 4<br>Date: Tue, 16 Dec 2014 13:44:22 +0300<br>From: Roman Nikolayevich Drovalev <drovalev@kaluga-gov.ru><br>To: Nir Soffer <nsoffer@redhat.com>, "users@ovirt.org"@kaluga-gov.ru<br>Subject: Re: [ovirt-users] Don't start vm<br>Message-ID:<br><OF0CF7416C.ABB8F3CC-ON43257DB0.003E3C0E-43257DB0.00406F2F@kaluga-gov.ru><br><div><br></div>Content-Type: text/plain; charset="us-ascii"<br><div><br></div>Hi,<br><div><br></div><br>> ><br>> > Hi,<br>> > answer below<br>> ><br>> > > > Nir Soffer <nsoffer@redhat.com><br>> > > ><br>> > > > > > Hi,<br>> > > > > ><br>> > > > > > I attach the file. Below log in the vdsm.log.62.xz<br>> > > > > ><br>> > > > > > The given nonexistent disk has probably appeared after<br>template<br>> > > > removal<br>> > > > > > from which it has been created.<br>> > > > > > BUT it was independent and before problems was not, after<br>template<br>> > > > > > removal!<br>> > > > > > The disk exists, but at it has changed ID!<br>> > > > ><br>> > > > > I don't understand this description.<br>> > > > ><br>> > > > > Can you describe to steps to reproduce this issue?<br>> > > > ><br>> > > > > Guessing from your description:<br>> > > > > 1. Create vm with x disks<br>> > > > > 2. Create template<br>> > > > > 3. Create vm from template<br>> > > > > 4. Remove template<br>> > > > > ?<br>> > > ><br>> > > > Yes.<br>> > > > 1. Create vm with x disks on the DS 3524 through FC (multipathd on<br>> > vdsm)<br>> > > > 2. Create template<br>> > > > 3. Create vm (independent) from template<br>> > > > 4. Start vm and job in the vm<br>> > > > 5. Remove template<br>> > > > 6. Stop vm<br>> > > > 7. Don`t start vm with error<br>> > ><br>> > > Do you mean - start vm fail with error about missing lv?<br>><br><div><br></div>Yes<br><div><br></div><br><div><br></div>><br>> > ><br>> > > > 8. seek it disk - #lsblk<br>> > ><br>> > > Can you share the output of lsblk both before and after you stop the<br>vm?<br><div><br></div>No, since vm does not start!<br><div><br></div><br>><br>> > ><br>> > > > 9. many command with block 253:20<br>> > ><br>> > > Not sure what do you mean by that<br>><br>> You did not explain what you mean<br><div><br></div>Hm, ?? vgchange ....<br><div><br></div>><br>> > > Note: do *not* activate all lvs using "vgchange -a y"<br>> > > Only vdsm should activate its volumes.<br>> ><br>> > OK! If vm don`t start, how to take data from vm?<br>><br>> Of course if you need to troubshoot the system, and the vm is not<br>> running, there is no problem to access the lv directly.<br>><br>> Even then, you should *not* activate all lvs in a vg using<br>><br>> vgchange -a y<br>><br>> But activate only the lv you want to access using<br>><br>> lvchange -a y<br><div><br></div>Thank you, did not know<br><div><br></div>><br>> ><br>> > ><br>> > > > 10. mount finded lvm in lvm volume and save data<br>> > ><br>> > > Mount? how mount is related to lvm?<br>> ><br>> > VM disk is lv on vdsm. I mounted lv, inside lvm on lv vdsm!<br>><br>> You mean you activate the lv on the host?<br><div><br></div>Yes, intro LVM vdsm<br><div><br></div><br>><br>> > > > 12. reboot all vdsm host<br>> > > > 13. dont't find ID it disk! ID it disk changed!<br>> > ><br>> > > Please share output of lvs both before and after the vm is stopped.<br>> ><br>> > Before<br>> > -/dev/9d53ecef-8bfc-470b-8867-836bfa7df137/<br>> fb8466c9-0867-4e73-8362-2c95eea89a83<br>> > After -<br>> > /dev/9d53ecef-8bfc-470b-8867-836bfa7df137/33b905e2-23df-49a9-<br>> b772-4ebda3b0cd22<br>><br>> This not the output of lvs, these are the symlinks to the active lvs.<br>><br>> Can you share the lvs output before and after the vm is stopped?<br><div><br></div><br>No, since the vm does not start!<br><div><br></div>><br>> ><br>> > Now the problem disk has again received old ID(lvdisplay), BUT I have<br>> > already removed it!<br>><br>> I'm not sure what you mean. Can you share the output of lvdisplay before<br>> and after the operation?<br>><br><div><br></div>Already is not present, I have removed this problem disk<br><div><br></div><br>> ><br>> > The Mysticism!<br>> ><br>> > At me 3 disks on 9 GB, 5 days ago I have removed them. Now I them see<br>till<br>> > now (lvdisplay on the vdsm host) Why?<br>><br>> Did you update lvm cache using "pvscan --cache"?<br><div><br></div>No. I should after each operation with disks, do in the console "pvscan -<br>cache"?<br><div><br></div><br>><br>> ><br>> > In general my problem has begun that on Windows 2008 Vm the empty seat<br>has<br>> > come to an end.<br>><br>> What do you mean by that?<br><div><br></div>This is first problem! Second problem - don't start the vm.<br><div><br></div>><br>> > I have expanded volume in web gui. When I began to expand<br>> > a disk in VM - error.<br>><br>> > lvdisplay on the vdsm host has shown the old size of<br>> > a disk!<br>><br>> Is the volume preallocated or thin provisioned?<br><div><br></div>All my disks - prelocated.<br><div><br></div>><br>> Preallocated volumes are extended when you modify the volume size in<br>> engine ui (as you described). Thin provisioned volumes are extended<br>> only when the available space is bellow a threshold, so the lv<br>> size will not change after you modify the volume size.<br>><br>> ><br>> > Sometimes normally all works!<br>><br>> Do you mean that now everything works?<br><div><br></div><br>The VM it has been removed, since for a week I could not start it!<br><div><br></div>Now all works on others VM. But there were 2 problems! My problem to<br>understand, that I have made not so or it is a problem oVirt.<br>I wish to use oVirt, but is not assured of it because of these problems!<br><div><br></div>><br>> ><br>> > How I understand, probably, "all ok" when you work with VM which are<br>on<br>> > SPM host??!<br>><br>> Lost you here.<br><div><br></div>It agree, a head around ))<br><div><br></div><br>Thanks<br><div><br></div>Roma<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.ovirt.org/pipermail/users/attachments/20141216/78dbbd5d/attachment.html><br><div><br></div>------------------------------<br><div><br></div>_______________________________________________<br>Users mailing list<br>Users@ovirt.org<br>http://lists.ovirt.org/mailman/listinfo/users<br><div><br></div><br>End of Users Digest, Vol 39, Issue 104<br>**************************************<br><div><br></div>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.ovirt.org/pipermail/users/attachments/20141217/527d76e5/attachment.html><br><div><br></div>------------------------------<br><div><br></div>_______________________________________________<br>Users mailing list<br>Users@ovirt.org<br>http://lists.ovirt.org/mailman/listinfo/users<br><div><br></div><br>End of Users Digest, Vol 39, Issue 107<br>**************************************<br><div><br></div>This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.<br></div><div><br></div></div></body></html>