On 04/25/14 16:14, jcbollinger wrote:
> On Thursday, April 24, 2014 7:35:10 PM UTC-5, Joachim Schrod wrote:
>
> I have a service where there is one server in my net and many
> clients (actually, all systems are clients): CUPS. In client
> setups, one file has to be changed (client.conf
On 04/25/14 14:34, Felix Frank wrote:
> That'll work, and not at all a bad design choice. But the parameterised
> cups wrapper class is ultimately unnecessary - you can just have all
> nodes include cups::client and make sure that the server(s) also include
> cups::server in a fashion that suits yo
On Thursday, April 24, 2014 7:35:10 PM UTC-5, Joachim Schrod wrote:
>
> Hi,
>
> I've got question about best practice, and am interested in advice
> from you experienced folk.
>
> I have a service where there is one server in my net and many
> clients (actually, all systems are clients): CUPS
That'll work, and not at all a bad design choice. But the parameterised
cups wrapper class is ultimately unnecessary - you can just have all
nodes include cups::client and make sure that the server(s) also include
cups::server in a fashion that suits your general manifest design.
Talking roles/pro
I don't pretend to give you best practices here, but I would personally
create one cups class as an entry point, with two (at least) boolean
parameters: client and server.
client defaults to true and server to false, either using class defaults or
Hiera's base hierarchy level.
Then you could im
