[ovirt-users] list of answer file parameters?

[Jorick Astrego]

On 08/15/2014 02:21 PM, Yedidyah Bar David wrote:
> ----- Original Message -----
>> From: "Alon Bar-Lev" <alonbl at redhat.com>
>> To: "Jorick Astrego" <j.astrego at netbulae.eu>
>> Cc: users at ovirt.org
>> Sent: Friday, August 15, 2014 1:59:41 PM
>> Subject: Re: [ovirt-users] list of answer file parameters?
>>
>>
>>
>> ----- Original Message -----
>>> From: "Jorick Astrego" <j.astrego at netbulae.eu>
>>> To: users at ovirt.org
>>> Sent: Friday, August 15, 2014 1:27:23 PM
>>> Subject: [ovirt-users] list of answer file parameters?
>>>
>>> Hi,
>>>
>>> I'm looking everywhere for a full list of "OVESETUP" parameters that can
>>> be used in the installer answerfile.
>>>
>>> Searched the red hat manual and found some in:
>>>
>>> "3.6. Passwords in Red Hat Enterprise Virtualization Manager"
>>>
>>> But there are more. I can get it from a finished install but some
>>> parameters only apply to some types of installation.
>>>
>>> I found this one form lzap:
>>>
>>> https://gist.github.com/lzap/7a8cbb7f44d41e4ad171
>>>
>>> But I don't know if it's complete or just for his personal use.
>>>
>>> No hurry, I know you are all busy ;-)
>>>
>> Hi,
>>
>> The simplest way is to perform setup and record the answer file.
>>
>> You can even <Ctrl>C at the summary confirmation question and answer file
>> will be generated for you without installing anything.
>>
>> Full list is available at /usr/share/ovirt-engine/setup/ovirt_engine_setup/,
>> seek *.py and look for @osetupattrs with answerfile=True. Maybe in future we
>> can have utility to extract all with description.
> Also note:
>
> 1. The files there are separated between different packages, so you'll not
> necessarily have all, if you did not install some optional ones.
>
> 2. Not all combinations are supported, and in principle it's possible to manually
> create answer files that will cause setup to fail, or even to succeed but leave
> an unsupported, unexpected system setup. I started writing about this some time
> ago in [1] but got stuck in the middle, and Alon said I should not call it Otopi
> because it does not document Otopi but engine-setup, and he is largely right.
> See also [2], which is not directly related (key is not answerfile=True), but does
> give a relevant example.
>
> [1] http://www.ovirt.org/Otopi
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1101001
Yes that was my problem, I was trying to do AIO install but 
engine-cleanup didn't work because a version mismatch.

So I tried removing everything by hand but the installer never asked me 
the install local VDSM question... Then I thought I'd get smart and just 
edit the answer the installer generated and add the AIO lines to it.  
But nearly all the settings are undocumented so I had to resort to 
searching on what to set them to on pastebin etc. In the end, I 
reinstalled the host as it was quicker to do a fresh install.

Also I want to create puppet files and deploy engine through foreman.

I think as a workaround, I'll do a couple of different installs and rip 
the generated answer file from them. But when a new parameter get's 
introduced, I will never know about it until I run into an issue.

Something like "ovirt-installer --list-answerfile" should be possible 
IMHO, as the installer uses and verifies the parameters on install. I'm 
not a programmer but it should be able to spit out a list them.

Kind regards,

Jorick Astrego
Netbulae