Bug 987785

auto-install should work for puppet. 

Ryan, can you provide details?

This should work, with available parameters of:

puppet_enabled
puppet_server
puppet_certname

This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Created attachment 837153 [details]
attached Screenshot for puppet.png

Test version:
ovirt-node-3.0.1-9.el6_5.noarch.rpm
rhevh-6.5-20131213.0.0.iso
ovirt-node-plugin-puppet-3.0.1-9.el6_5.noarch.rpm

Test as follow:
Using edit-node install ovirt-node-plugin-puppet into rhevh-6.5-20131213.0.0.iso and auto install with this edited iso:
BOOTIF=eth0 storage_init=/dev/sda puppet_enabled=1 puppet_server=dhcp-10-214.nay.redhat.com puppet_certname=dhcp-10-106.nay.redhat.com firstboot

After auto install success, enter into puppet page.Check that configuration info
in TUI page(Seen puppet.png).

But this configuration info was missed in /etc/puppet/puppet.conf
[root@agent2 admin]# cat /etc/puppet/puppet.conf |more
[main]
#    server = ""
#    certname = ""
    # The Puppet log directory.
    # The default value is '$vardir/log'.
    logdir = /var/log/puppet
...

so this bug wasn't fixed in rhevh-6.5-20131213.0.0.iso,need re-assigned this bug again.

Still failed in the follow version:
rhevh-6.5-20131220.0
ovirt-node-3.0.1-13.el6_5.noarch

so need to re-assigned it again

considering the differences of ovirt-node from plan fedora/rhel - i'd expect some puppet recipes won't work.

what's the use case for puppet with ovirt-node in general, and for this specific case?

I am not the original requester but I know getting puppet support for ovirt-node/rhevh is very important to us and I believe a number of Operations groups.

The ability for us to automatically configure parts of the sytem (even just passwords) is very ideal. Noone likes having to go onto 20+ hypervisors and use the ncurses menu to reconfigure systems/change passwords everytime a password rotation is needed.

Us sysadmins love automation :) Ideally RHEV itself would provide a general scripting/automation platform, but being able to work into our existing workflow using puppet would be great. Even being able to use puppet to fire off "build finish" messages to foreman and eventually satellite 6 will be something useful, as people will expect to be able to do full automated pxe installs of rhevh through those tools.

Hope this helps,

Regards,

Graeme

(In reply to Itamar Heim from comment #16)
> considering the differences of ovirt-node from plan fedora/rhel - i'd expect
> some puppet recipes won't work.
> 
> what's the use case for puppet with ovirt-node in general, and for this
> specific case?

Since it has supported to configure puppet from the TUI.This case just want allow support configure puppet from auto install via "puppet_server=xxx" and "puppet_certname=xxx" parameters

Thanks for your input, Graeme. And that - automation and fitting into a deployment - is the reason why we started this.

Itamar, the idea is to provide some "high-level" configuration methods . basically exposing RHEV-H's TUI pages via puppet classes.

There are actually dedicated puppet classes for RHEV-H/Node which will leverage our own logic (not the stock classes) to configure a host.

yes, just need to make it clear "normal" puppet classes aren't going to work since rhev-h is different than RHEL (lack of some rpm/files, need to persist changes, etc.)

Closing old RFEs.
Currently no intention to support puppet as there are other ways to
handle RHEV-H automation.