On Mon, Mar 27, 2017 at 5:05 AM, Tatsuya <suginami(a)gmail.com> wrote:
Dear Didi
> Even if you never heard about hosted-engine in previous versions and 4.1
> was your first attempt? Any suggestions for improvement to make it
easier
> to find?
Sorry to late reply. I notice that I forget to add "users
<users(a)ovirt.org>"
as a destination.
The inquiry of the other day was about oVirt 4.0.
Yesterday I installed 4.1 for the first time.
I think that if I had been able to deploy self hosted engine not only when
reinstalling host
but also when adding new host, I could have noticed.
Hi Tatsuya,
you should see it also adding new hosts, it should look like this:
https://raw.githubusercontent.com/oVirt/ovirt-site/30c70a9076f94113469401...
That one is from 4.1.0
There is also an explicit icon to highlight which host is running the
engine VM and which ones are ready for it:
https://raw.githubusercontent.com/oVirt/ovirt-site/30c70a9076f94113469401...
Deploying from CLI is explicitly prevented and it's pointing you to the web
UI with this message:
'Setup of additional hosts using this software is not allowed anymore.
Please use the engine web interface to deploy any additional hosts.'
Do you think it's not that clear?
Anything we can improve?
Or it may be useful to pop up the deployment method of self hosted engine
when adding new host is completed.
Regards
Tatsuya
---------- Forwarded message ----------
From: Tatsuya <suginami(a)gmail.com>
Date: 2017-03-23 1:10 GMT+09:00
Subject: Re: [ovirt-users] How to deploy hosted-engine to the second and
later host machines
To: Yedidyah Bar David <didi(a)redhat.com>
Dear Didi
> e.g. that if the storage
> domain is not empty, a message will be emitted saying something like:
> "To add this host as an additional one to an existing hosted-engine HA
> cluster, please use the engine web administration ui or the API/SDK".
It seems to be a very appropriate explanation when reading after
understanding,
but it may be better to ready specific steps.For example, this is one
example among many:
"In particular, when creating a new host from the engine web
administration ui,
please select "Deploy" on the self hosted engine tab."
Also, "hosted-engine --deploy --config-append=answers.conf" was an error
from cli,
but "hosted-engine --deploy" wasn't an error, so I almost created a new
hosted-engine
using "hosted-engine --deploy" to the second and later host machines.
From the above, It wil be better to warn also when running "hosted-engine
--deploy".
Regards
Tatsuya
2017-03-21 15:29 GMT+09:00 Yedidyah Bar David <didi(a)redhat.com>:
> On Mon, Mar 20, 2017 at 5:44 PM, Tatsuya <suginami(a)gmail.com> wrote:
> > Dear lan and Didi
> >
> >> Found a working option to get second and subsequent hosts deployed with
> >> ovirt 4.1
> >>
> >> 1-Set second host into maintenance
> >> 2-highlight second host and choose "Installation -->
Reinstall", edit
> >> params in popup and click OK
> >> 3-Ignore warning that pops up and watch the vdsm.log or look for
> >> "Installing" status in webui
> >> 4-It should show you that the install is running, keep watching
> vdsm.log.
> >> 5-Click 'ok' on warning and wait patiently for install to finish.
> >>
> >> Second node comes up and is active.
> >
> >> No, sorry for not being clear. I referred to the engine web admin ui
> >> (and also API/SDK). Thanks, Ian, for your reply explaining this.
> >
> > I apologize for this late reply.I had been trying again from
> reinstalling
> > the host.
> >
> > Thanks to you, I was able to install HostedEngine in second and
> subsequent
> > hosts.
> > I think that I could not find this option by myself.
>
> Even if you never heard about hosted-engine in previous versions and 4.1
> was your first attempt? Any suggestions for improvement to make it easier
> to find?
>
> >
> > I'm grateful for your support.
>
> You might want to open one or more RFEs for some clarifications in the
> interface - both command line and cockpit - e.g. that if the storage
> domain is not empty, a message will be emitted saying something like:
> "To add this host as an additional one to an existing hosted-engine HA
> cluster, please use the engine web administration ui or the API/SDK".
>
> Best,
> --
> Didi
>