[ovirt-devel] Where should the answer file for the improved HE flow be located?

Yedidyah Bar David didi at redhat.com
Mon Oct 12 05:29:31 UTC 2015


On Sun, Oct 11, 2015 at 10:36 PM, Fabian Deutsch <fdeutsch at redhat.com> wrote:
> Hey,
>
> lately we had the issue that the answer file for the engine in the HE
> flow changed (it required an additional answer).

"in the HE flow" specifically?

As discussed in private, this might best (?) be solved by adding an option
to engine-setup which will make it accept the default answer for each question
where a default is supplied.

>
> Currently the answerfile is maintained by node in the engine appliance.
>
> I wonder if it wouldn't make more sense to keep the answer file (which
> is solely used for the HE flow) could be maintained inside the
> hosted-engine-setup repository, and be packaged in a subpackage (i.e.
> hosted-engine-setup-answers[-3.6]).

IIUC the appliance is not specific to HE, right? Can be used independently.

>
> Another thought is that the HE-setup cloud-init is already referencing
> the engine answerfile, if it was matained in the same package, then it
> should also be easier to ensure that the assumed and real paths of the
> answerfile match.
>
> So, if the answerfile was in that subpackage of HE-setup, we could
> just install that specific package inside the appliance, and the rest
> is left to the HE-setup logic.

IMHO it would be best if we do not need to maintain this answerfile at all.
If the existence of such an option would have been enough, I'd vote for
adding it.

Otherwise, I'd like to understand what, if at all, in the currently-maintained
answerfile is HE-specific, and what is different from merely accepting the
defaults.

If we do agree eventually that such an answerfile needs to be maintained
manually, I agree with Tolik, who said in a private discussion that it should
be maintained inside the package of engine-setup. Perhaps we even need more
than one such file, depending on the answers to above :-)

Best,
-- 
Didi



More information about the Devel mailing list