Feature #1527
Add support for per OS classes list.
| Status: | New | Start: | 03/12/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Ohad Levy |
% Done: | 0% |
|
| Category: | Puppet integration | |||
| Target version: | - | |||
| Backlog: | No | Difficulity: | ||
| Votes: | 0 |
Description
Please could the addition of puppet classes to an operating system be possible just as parameters are for instance.
Up to now we have been using a 'base' class that all machines are a member of e.g
/base/service1
/base/service2
to define a common layer of puppet deployment however this is starting to break down as
other operating systems are added such as debian, windows, fedora rawhide where modules
don't work or are just not sensible. In principal we could improve puppet modules to execute sensibly under
windows and use a parameter but just about every module would have to be touched.
In reality it is base of classes per operating system we are looking to deploy.
