[Spacewalk-list] Spacewalk and Puppet integration

[Thomas Bendler]

Hi Cliff,

2010/6/17 Cliff <cperry at redhat.com>

> Thomas Bendler wrote:
>
>> So my personal view is that it is better to put configuration management
>> completely out of Spacewalk and use Spacewalk to provide an interface to
>> other configuration management engines like puppet. Makes it more flexible
>> and reduce the developer effort.
>>
>
> By 'provide an interface' - can you explain how this would look to
> yourself? :) Full GUI wrapper to puppet (do something like we did with
> cobbler)? Expose in UI certain things? provide pre-canned scripts to
> integrate the two?
>

good question. I think this is a more philosophic question. In principle it
is a good idea for the end user to have an consistent Web UI for IT managing
tasks, on the other hand, if you start using things like puppet in larger
environments you still like to have some kind of access to the "full power"
of puppet. So from my point of view the best way would be a dual view Web
UI, something like a normal view and an expert view. The normal view can
hide more or less everything which points to the used configuration engine
and could have things like templates for common tasks, the expert view gives
direct access to the used configuration engine. Instead of an expert view it
is also thinkable (and maybe the better way) to have puppet organized in a
way that Spacewalk provide something like a custom exit point where custom
scripts and classes could be integrated. So the cobbler integration is a
good starting point but it should be better documentet and there should be a
way to use the "full power".

Regards, Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20100618/8ce67104/attachment.htm>