[Spacewalk-list] Spacewalk and Puppet integration

[Thomas Bendler]

Hi Miroslav,

2010/6/15 Miroslav Suchý <msuchy at redhat.com>

> [...]
> I'm sure you know you can directly manage configuration files using
> Spacewalk. Yes Puppet can do a lot of things Spacewalk could not.
> I just want to ask what *you* are missing. Which feature of Puppet you
> would like to see in Spacewalk.
>

I manage all my setups via Spacewalk as of today but I'm currently in the
phase of switching to puppet for several reasons.

   - restart of Services after configuration change (without scripting)
   - separate file area for file distribution (puppet://server/dir/file)
   - Import/Export of configuration files and setups (I have to import each
   channel and file after I've setup a new SW server)
   - Version control and the ability to edit configuration files with a real
   editor (I know you can download the file in SW and upload it again after
   editing but this is less handy than vim/VC)
   - Only one TCP Port needs to be open on the FW
   - Better user management
   - Predefined classes for common services like mail, web, ... server

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.

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