Bug 911413

Summary:	RFE: Allow configuration via puppet
Product:	Red Hat Enterprise Linux 6	Reporter:	Mike Burns <mburns>
Component:	ovirt-node	Assignee:	Ryan Barry <rbarry>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.5	CC:	acathrow, bsarathy, cboyle, cshao, fdeutsch, gouyang, hadong, huiwa, jboggs, leiwang, lnovich, mburns, mgoldboi, ovirt-bugs, ovirt-maint, rbarry, ycui
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-node-3.0.1-7.el6	Doc Type:	Enhancement
Doc Text:	The Red Hat Enterprise Virtualization Hypervisor can now be configured through Puppet for ease of use. It also provides an alternative to basic PXE to deployment and configuration.	Story Points:	---
Clone Of:	853429	Environment:
Last Closed:	2014-01-21 19:26:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	853429
Bug Blocks:

Description Mike Burns 2013-02-14 22:41:56 UTC

+++ This bug was initially created as a clone of Bug #853429 +++

Description of problem:
Currently Node can be configured using a number of kargs, furthermore Engine related stuff is configured using VDSM. It would be nice if a configuration management system like puppet could be used to configure the Node too.
This would be helpful for a foreman integration as well as for configuring additional stuff like sysctl.

--- Additional comment from Fabian Deutsch on 2012-08-31 09:37:59 EDT ---

And this feature could also be used to configure e.g. OpenStack components on node. This would also work around cluttering the cmdline with all sorts of arguments which leads to problems with PXE.

This might also be inetersting for bug #832000

One idea is to create a puppet Node class and a minimalistic puppet client which re-uses puppets REST API [1] or using the upstream client.

[1] http://docs.puppetlabs.com/guides/rest_api.html

Comment 8 haiyang,dong 2013-10-11 10:37:54 UTC

Test version:
rhev-hypervisor6-6.5-20130930.0.auto665.el6.iso
ovirt-node-3.0.1-3.el6.noarch
ovirt-node-plugin-puppet-3.0.1-3.el6.noarch.rpm

Test steps:
1. Using edit-node install ovirt-node-plugin-puppet into rhev-hypervisor6-6.5-20130930.0.auto665.el6.iso:
edit-node --repo=edit-node.repo --install=ovirt-node-plugin-puppet-3.0.1-3.el6.noarch.rpm rhev-hypervisor6-6.5-20130930.0.auto665.el6.iso
2.clean install this iso .Login it and enter into puppet page, could configure 
puppet now.

But i met Bug 1016373, Bug 1016386, Bug 1016393, so need wait for these bugs was fixed to verify this bug.

Comment 10 Cheryn Tan 2013-11-08 00:29:27 UTC

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.

Comment 12 haiyang,dong 2014-01-07 06:52:48 UTC

Test Version:
rhevh-6.5-20131220.0.iso
ovirt-node-3.0.1-13.el6_5.noarch
ovirt-node-tools-3.0.1-13.el6_5.noarch.rpm
ovirt-node-plugin-puppet-3.0.1-13.el6_5.noarch.rpm
 
Test Cases:
(a) Using edit-node tools to install ovirt-node-plugin-puppet package --Pass			
(b) Shown correctly info of puppet plugin in Plugins page --Pass			
(c) Enable puppet function in Puppet page to connect puppet master --Pass			
(d) Disable puppet function in Puppet page to disconnect puppet master -- Pass			
(e) Support to configure puppet for Automated Installation	--FAILED		

For configure puppet failed during auto install, i have report bz#987785 to track it.
So the base functions work well for support puppet. so change the status into "verified".

Comment 14 errata-xmlrpc 2014-01-21 19:26:17 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0033.html