Thanks for all your suggestions! Restricting access to managed nodes
using iptables occured to me after sending this post (stupid me). I
think that does the trick. If not, I'll try Daniel's approach.
Samuli
On 28 Mag, 06:25, Daniel Pittman wrote:
> sasepp writes:
> > I apologize if this issu
To each their own, of course but between having a set of puppet scripts
and checking everything into svn/cvs, the puppet work functions as
documentation for later. I've been caught more than once coming back
to a system after a year or so trying urgently to remember its specifics.
On Sun, May 30,
"Gabriel - IP Guys" writes:
> Just a idea to float out here among puppet forge users,
>
> Can we have a readme standard? For example, we could have a format like the
> following
FWIW, a *great* model to follow is probably the standard Unix manual page
format, which has had thirty years of workin
On Saturday 29 May 2010, ext Matt Juszczak wrote:
> I have a "basenode" class which installs most of the packages
> needed on a specific server. For the database servers, we ensure
> mysql is installed, setup the directory structure, etc.
>
> But what about "one off" servers? For instance, I have
On Sun, May 30, 2010 at 11:56 AM, Gabriel - IP Guys <
gabr...@impactteachers.com> wrote:
> Can we have a readme standard? For example, we could have a format like
> the following
>
+1 Good idea! I will be easier to know what is the module's feature
-- Carla
--
You received this message becaus
Just a idea to float out here among puppet forge users,
Can we have a readme standard? For example, we could have a format like
the following
# Developer - b...@example.com
# URL http://forge.puppetlabs.com/bob/packagename
#
# Description:
# This does module will install packagename on node.exam
