Hi,
Actually I want that nobody in my network can change the hostname as some
has already changed the hostname of their node so
I want to restrict a check that nobody in the network or outside network
can change the hostname as they are already provided the sudo access as per
requirement. Also all
Hi puppeteers,
I’m starting from scratch with Puppet 2.7 and I’m trying to avoid some
pitfalls from the past using another configuration management tool. I
think most of the issues I had could be solved by Puppet and Hiera but
being new to the tool and the approach, Im seeking for advice.
I
Hi Everyone;
I am new to puppet and would SO appreciate any help you might be able
to provide!
I am attempting to configure Passenger. I have followed all of the
installation instructions but, when I restart my webserver, it does
not start the puppetmaster nor does it throw any errors. So, I am
http://apt.puppetlabs.com/
Use that and then "apt-get install puppetmaster-passenger". (There's a yum
repository too.) Then you can crib from those configs.
On Fri, Apr 06, 2012 at 05:45:39PM -0700, Jax01 wrote:
> Hi Everyone;
>
> I am new to puppet and would SO appreciate any help you might be
On 12-04-07 10:43 AM, Christopher Wood wrote:
> http://apt.puppetlabs.com/
>
> Use that and then "apt-get install puppetmaster-passenger". (There's a yum
> repository too.) Then you can crib from those configs.
oh, interesting, I didnt' know about this one.. and it's available in
squeeze-backpor
On Thu, Apr 5, 2012 at 10:34 PM, Christophe L wrote:
> Thank you all for your answers !
>
> As a suggestion for the documentation, that would be nice to have
> information about the http://apt.puppetlabs.com/ apt repository on the
> puppet installation page.
That is currently undergoing some work
On Fri, Apr 6, 2012 at 7:40 AM, Andreas Haerter
wrote:
> Hi,
>
> On 05.04.2012 22:42, Brown, Rodrick wrote:
>> I really hate poor documentation.
>>
>> I’m following along in PDF documentation I downloaded from the official
>> site and I’m stuck after I installed rack & passenger modules from
>> ru
I think there's something simple I'm missing about module best practices
and application to nodes.
Let's assume I've been a good module developer: I have a general-purpose
module with no site- or node-specific knowledge, and it defines a number of
classes (generalized with parameters, extlookup
