[ovirt-users] FQDN for vm creating with hosted-engine

[Yedidyah Bar David]

----- Original Message -----
> From: "Cong Yue" <Cong_Yue at alliedtelesis.com>
> To: users at 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 at 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 at 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