Re: [ovirt-users] FQDN for vm creating with hosted-engine
FQDN convention should be following your organizational domain conventions, as long as FQDNS reachable via DNS, should work just fine. 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. 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. 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. Thanks in advance. Best regards, Nikolai Nikolai Sednev Senior Quality Engineer at Compute team Red Hat Israel 34 Jerusalem Road, Ra'anana, Israel 43501 Tel: +972 9 7692043 Mobile: +972 52 7342734 Email: nsed...@redhat.com IRC: nsednev - Original Message - From: Cong Yue cong_...@alliedtelesis.com To: nsed...@redhat.com, Yedidyah Bar David d...@redhat.com Cc: users@ovirt.org Sent: Wednesday, December 17, 2014 6:41:54 PM Subject: RE: FQDN for vm creating with hosted-engine --- 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. IP address should be reserved for the VM at DHCP. 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. --- 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? 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? What is the confusions if I use manual IP rather than DHCP for engine VM? Thanks, Cong -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of users-requ...@ovirt.org Sent: Wednesday, December 17, 2014 1:17 AM To: users@ovirt.org Subject: Users Digest, Vol 39, Issue 107 Send Users mailing list submissions to users@ovirt.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.ovirt.org/mailman/listinfo/users or, via email, send a message with subject or body 'help' to users-requ...@ovirt.org You can reach the person managing the list at users-ow...@ovirt.org When replying, please edit your Subject line so it is more specific than Re: Contents of Users digest... Today's Topics: 1. 1. FQDN for vm creating with hosted-engine (Yue, Cong) (Nikolai Sednev) -- Message: 1 Date: Wed, 17 Dec 2014 04:16:33 -0500 (EST) From: Nikolai Sednev nsed...@redhat.com To: users@ovirt.org Subject: [ovirt-users] 1. FQDN for vm creating with hosted-engine (Yue, Cong) Message-ID: 2080226028.11273252.1418807793775.javamail.zim...@redhat.com Content-Type: text/plain; charset=utf-8 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. IP address should be reserved for the VM at DHCP. 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. Thanks in advance. Best regards, Nikolai Nikolai Sednev Senior Quality Engineer at Compute team Red Hat Israel 34 Jerusalem Road, Ra'anana, Israel 43501 Tel: +972 9 7692043 Mobile: +972 52 7342734 Email: nsed...@redhat.com IRC: nsednev - Original Message - From: users-requ...@ovirt.org To: users@ovirt.org Sent: Wednesday, December 17, 2014 1:19:12 AM Subject: Users Digest, Vol 39, Issue 104 Send Users mailing list submissions to users@ovirt.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.ovirt.org/mailman/listinfo/users or, via email, send a message
Re: [ovirt-users] FQDN for vm creating with hosted-engine
--- 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. IP address should be reserved for the VM at DHCP. 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. --- 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? 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? What is the confusions if I use manual IP rather than DHCP for engine VM? Thanks, Cong -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of users-requ...@ovirt.org Sent: Wednesday, December 17, 2014 1:17 AM To: users@ovirt.org Subject: Users Digest, Vol 39, Issue 107 Send Users mailing list submissions to users@ovirt.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.ovirt.org/mailman/listinfo/users or, via email, send a message with subject or body 'help' to users-requ...@ovirt.org You can reach the person managing the list at users-ow...@ovirt.org When replying, please edit your Subject line so it is more specific than Re: Contents of Users digest... Today's Topics: 1. 1. FQDN for vm creating with hosted-engine (Yue,Cong) (Nikolai Sednev) -- Message: 1 Date: Wed, 17 Dec 2014 04:16:33 -0500 (EST) From: Nikolai Sednev nsed...@redhat.com To: users@ovirt.org Subject: [ovirt-users] 1. FQDN for vm creating with hosted-engine (Yue, Cong) Message-ID: 2080226028.11273252.1418807793775.javamail.zim...@redhat.com Content-Type: text/plain; charset=utf-8 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. IP address should be reserved for the VM at DHCP. 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. Thanks in advance. Best regards, Nikolai Nikolai Sednev Senior Quality Engineer at Compute team Red Hat Israel 34 Jerusalem Road, Ra'anana, Israel 43501 Tel: +972 9 7692043 Mobile: +972 52 7342734 Email: nsed...@redhat.com IRC: nsednev - Original Message - From: users-requ...@ovirt.org To: users@ovirt.org Sent: Wednesday, December 17, 2014 1:19:12 AM Subject: Users Digest, Vol 39, Issue 104 Send Users mailing list submissions to users@ovirt.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.ovirt.org/mailman/listinfo/users or, via email, send a message with subject or body 'help' to users-requ...@ovirt.org You can reach the person managing the list at users-ow...@ovirt.org When replying, please edit your Subject line so it is more specific than Re: Contents of Users digest... Today's Topics: 1. FQDN for vm creating with hosted-engine (Yue, Cong) 2. Server 2012 R2 + Intel Conroe Cluster (Nathan Llaneza) 3. alternate method of fencing (Brent Hartzell) 4. Re: Don't start vm (Roman Nikolayevich Drovalev) -- Message: 1 Date: Tue, 16 Dec 2014 14:44:44 -0800 From: Yue, Cong cong_...@alliedtelesis.com To: users@ovirt.org users@ovirt.org Subject: [ovirt-users] FQDN for vm creating with hosted-engine Message-ID: ed08b56256b38842a463a2a0804c5ac0326aca3...@svr-ca-exch1.atg.lc Content-Type: text/plain; charset=us-ascii Hi Now I am trying to confirm KVM's HA with ovirt, and doing the walk through as the following guide. http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/ 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. The following is my hosts file, my VM host and storage is 10.0.0.92. And I am trying to assign 10.0.0.95 to the hosted VM. --- [root@compute2-2 ~]# cat /etc/hosts 10.0.0.93 compute2-2 nfs2-2 10.0.0.95 ovrit-test 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 Also how I can remove the VM I installed, as for when I try to do hosted-engine --deploy, it shows --- [root@compute2-2 ~]# hosted-engine --deploy [ INFO ] Stage: Initializing Continuing will configure this host for serving as
Re: [ovirt-users] FQDN for vm creating with hosted-engine
- Original Message - From: Cong Yue cong_...@alliedtelesis.com To: users@ovirt.org Sent: Wednesday, December 17, 2014 12:44:44 AM Subject: [ovirt-users] FQDN for vm creating with hosted-engine Hi Now I am trying to confirm KVM's HA with ovirt, and doing the walk through as the following guide. http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/ 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. Do you refer to the following: Please provide the FQDN for the engine you would like to use. This needs to match the FQDN that you will use for the engine installation within the VM. Note: This will be the FQDN of the VM you are now going to create, it should not point to the base host or to any other existing machine. Engine FQDN: ? We recently changed this text to be so, due to [3]. If you still do not find it easy to understand, please suggest better wording. Thanks! The Engine FQDN is the name that is used by others to refer to the machine on which the engine runs. In this context it's the name of the VM. This does not have to be the hostname of that machine - the output of the command 'hostname' there. E.g. you might want to have a hostname 'purple.example.com' but connect to it as 'my-engine.example.com'. You'd probably add to the dns an A and a PTR record for 'purple', and a CNAME record for 'my-engine'. You should then input at this prompt, as well as the one during engine-setup inside this vm, 'my-engine.example.com'. See [1] [2] as examples for naming conventions. [1] https://tools.ietf.org/html/rfc1178 - an rfc from 1990, still mostly relevant today [2] http://mnx.io/blog/a-proper-server-naming-scheme/ - some random document found by searching for 'hostname conventions' [3] https://bugzilla.redhat.com/show_bug.cgi?id=1069945 : [TEXT] Add a note explaining better how FQDN will be used The following is my hosts file, my VM host and storage is 10.0.0.92. And I am trying to assign 10.0.0.95 to the hosted VM. --- [root@compute2-2 ~]# cat /etc/hosts 10.0.0.93 compute2-2 nfs2-2 10.0.0.95 ovrit-test 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 Seems like you intend to use ovirt-test for the engine, so enter that. Also how I can remove the VM I installed, as for when I try to do hosted-engine --deploy, it shows --- [root@compute2-2 ~]# hosted-engine --deploy [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor and create a VM where you have to install oVirt Engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]: Yes [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup Configuration files: [] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20141216144036-30j0wk.log 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 If you set it up with a previous 'hosted-engine --deploy', you can kill it with 'hosted-engine --vm-poweroff'. If you created it yourself, best use the same tool - e.g. if with virsh, use that to kill it. You can always use ps to find the qemu process of it and kill it with 'kill'. Best, -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
