Re: [ovirt-users] Testing self hosted engine in 3.6: hostname not resolved error
On Thu, Oct 22, 2015 at 5:08 PM, Simone Tiraboschi <stirabos(a)redhat.com>
wrote:
> engine is up and admin web portal accessible and host results up.
>
> I expected storage to be configured inside admin web portal but
> apparently I don't see anything already configured and also I don't see the
> sh engine VM listed... is it correct?
>
No, we have an open bug on that:
https://bugzilla.redhat.com/show_bug.cgi?id=1269768
You can try to manually import it in the mean time.
Ok, I'll try.
So when bug solved, if I have a problem with the engine and for example I'm
not able to connect to it through ssh and/or web admin console, what other
means would I have to connect to it console and check (eg if it is in
kernel panic for any reason)?
During setup I was proposed to connect via remote-viewer via a temporary
password; I imagine this way is not usable after install, correct?
But hosted-engine storage domain can just contain the engine VM so you
still need to add a regular storage domain for other VMs.
>
Ah, ok. I thought that the initial storage domain would have become the
first storage domain for general VMs purposes too...
So actually if on dedicated filesystem/device, it could be small in size,
say 5-10Gb if I use the appliance, correct?
BTW: what is the 2Gb file system on loop device?
>
It was used by hosted-engine-setup as a fake storage pool to bootstrap the
hosted-engine storage domain.
It shouldn't be there at the end.
Could you please attach hosted-engine-setup logs to let me check why it's
still there?
here it is:
https://drive.google.com/file/d/0BwoPbcrMv8mvRFFKSmR0REN3Qkk/view?usp=sha...
>
> I configured the storage domain part as NFS, pointing
> to ovc71.localdomain.local:/NFS_DOMAIN
> Reading page at
> http://www.ovirt.org/Features/Self_Hosted_Engine
>
> it is not clear to me what to do next if I want for example keep a single
> host with its sh engine as a replacement concept of what before was
> all-in-one... and start creating VMs....
>
You have to setup your first regular data domain for other VMs: you can
add another NFS one.
OK.
In case I want to setup a single host with self hosted engine, could I
configure on hypervisor
a) one NFS share for sh engine
b) one NFS share for ISO DOMAIN
c) a local filesystem to be used to create then a local POSIX complant FS
storage domain
and work this way as a replacement of all-in-one?
>
Put the host in global maintenance (otherwise the engine VM will be
restarted)
Shutdown the engine VM
Shutdown the host
>
>
Ok. And for starting all again, is this correct:
a) power on hypevisor
b) hosted-engine --set-maintenance --mode=none
other steps required?
Attachments:
- attachment.html (text/html — 6.8 KB)