Home_greyopenFATE - openSUSE feature tracking > #305641
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Bring Puppet to fully supportable status

Feature state



Dedicate a developer for the duration of the 11.2 cycle to shaking out Puppet on openSUSE, contribute patches upstream correcting integration with our base system, and analyzing what future integration areas (particularly with YaST, but not limited) appear promising.

The objective is to walk through the Puppet documentation (http://reductivelabs.com/trac/puppet/wiki/DocumentationStart ), Turnbull's book (ISBN 159059978), and test out that things work as they should, patching and sending upstream when they do not. Finally, contribute a small "Puppet on SUSE" document to the community detailing any platform-specific factors (you will see there are a number for other distors already).

Additional notes: The plan is to _INSTALL_ the Puppet infrastructure by default. No default-running is planned - I thought it was important to clarify this. Addtionally,
Facter needs to be packaged and supportable alongside Puppet.
Cft should be packaged, but not default installed, and not the target of this focused infrastructure work in this cycle (i.e. Best effort).

User benefit:

The ultimate intent is to integrate a policy management framework into the platform and have it available as default infrastructure.
This has a number of consequencies: for one, the ability of third parties, both internal and external, to leverage the policy language for platform management. Secondly, I want to support the Puppet objective of being a pervasive policy language for *NIX, which may or may not be achievable.
This combines with the set of enabling management technologies we want to have on the platform as blocks to build on: integrated libraries (libzypp, libstorage, ..), management instrumentation (SFCB, management profiles exposing the libraries wherever possible), Stateless YaST interface (to enable access to configuration facilities), and support instrumentation (the Novell Support Link, formerly known as Aurora and Onstar).



  • Install a puppetmaster and puppet client and check whether basic setup works.
  • Setting a policy that a package should be installed should end in zypper installing the package in the machine


icons/user_comment.png F. L. wrote: (9 years ago)


icons/user_comment.png F. L. wrote: (9 years ago)

As per for phone conversation, this requirement is not only about technology ("Policy framework"), but also about the political decision of what solution to adopt - in which context the technology is not an Engineering decision, but a Business one.
I am chosing Puppet on the theory that we will do our bit to help the rise of a cross-*NIX management tool by making it available and supported. If the interest in Puppet contines at this pace, and other things go the right way, we will consider further investment. For now, we just make Puppet (and Facter with it) L3 supported.
If the market keeps moving in this direction, then good, we will integrate beyond the "managing by configuration file" scheme, and look at what YaST integration we can do. If it does not, we just keep the L3 package and move3 on.
Think of it as Perl - it is on Every *NIX, and if you use it is good if not, it does not hurt.

icons/user_comment.png P. R. wrote: (9 years ago)

I think anicka did some experiments with puppet.

icons/user_comment.png D. M. wrote: (9 years ago)

Progress note: integration of the community authored zypper plugin for puppet is integrated (and working) and will be submitted to stable.

icons/user_comment.png D. M. wrote: (9 years ago)

We added a patch to support zypper for puppet package ensure policies, which is submitted.

Marking as in implementation. Could in theory be marked as done if we had any criteria.

Last change: 9 years ago
Loading tags...
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint