[Viper-users] Getting started with viper

Davor Ocelic docelic at spinlocksolutions.com
Mon Oct 5 16:38:12 EDT 2009

On Sun, Oct 04, 2009 at 08:04:13PM +0200, Timm Essigke wrote:
> Going a bit beyond the current scope of viper: Since puppet is well
> suited for recipes fitting for different Linux/Unix distributions, I
> think it could be a great extension to support also other installers.
> I have no experience with RH kickstart or SUSE autoyast, but having a
> quick look, it seems that one could have some general definition
> within viper which is mapped to the autoinstall file syntax of the
> chosen distribution. A plugable API would be great, that  it can be
> extended further without diving deep into viper code. Guess there are
> similar autoinstall files in the BSD and Solaris world.
> The information, which is needed by the installer is always almost the
> same. I think it is doable, if one does not support all installer
> options, but only those required for a minimal installation. The rest
> can (and should) be done within puppet.

Yes, sure. I think it'd be easy to keep the format of data in LDAP
as debconf keys, but produce valid Kickstart files for RedHat etc.

> >>         sed 's/\s\+$//' $p | ldapadd  -x -D cn=admin,ou=clients \
> >>                 -w nevairbe   || exit 1
> >>
> >> Can you explain this a bit more? The spaces are necessary for proper
> >> functioning, i.e. if you remove the spaces like you show with sed,
> >> it would remove spaces from all places, and if nothing else, it'd
> >> break ldif continuation lines which begin with space, and partman
> >> partitioning schemes which also have strict spacing rules.
> The sed expression says: remove 1..n spaces before a newline ($). It

Ah... Didn't notice the $ at the end. Ok.


More information about the Viper-users mailing list