Hi all,
Recently I've hit against this problem which is proving to be a
formidable foe. We have an in-house developed ENC and use
parameterised classes just about everywhere and as a result enjoy a
fairly flexible way of handing out configurations and very well-
defined interfaces between componen
Thanks for the replies so far from all. It does seem like it is both a
problem with the fact that I decided to explicitly version our
application modules and provide a mechanism for tieing configuration
"blueprints" in the ENC side to the version of the application module
in use, but no such mechan
on of this particular feature? Evidently nobody has decided to
follow up my question on the actual feature request.
Best Regards,
Oliver Hookins
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, sen
On Aug 31, 10:09 am, Kenneth Holter wrote:
> Hello all.
>
> Are there any rule of thumb regarding using "inherits" versus "include"? For
> example, if I'm creating the class "syslog::base" which should servere as a
> building block for syslog clients, should I go for a "class syslog::client
> inhe
On Sep 15, 11:01 am, Alan Barrett wrote:
> On Tue, 14 Sep 2010, Bruce Richardson wrote:
> > On Tue, Sep 14, 2010 at 08:34:00AM -0400, Ryan Coleman wrote:
> > > Hi Oliver, try:
>
> > >http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environ...
>
> > I've never been fond of the way RoR
On Sep 15, 5:53 pm, Nikolay Sturm wrote:
> * Oliver [2010-09-14]:
>
> > What mechanism is there (or is needed) in order to make
> > cucumber-puppet aware of the environment (or at least modulepath)
> > settings?
>
> The environment is just another node fact. As long as you don't use yaml
> node fi
On Sep 16, 12:38 pm, Ben Tullis wrote:
> Thanks for the response, but I think you've misunderstood the first
> bit.
>
> > Rails logs are not rotated by default. The rails world would use a
> > capistrano task:
>
> >http://blog.daeltar.org/logrotate-with-capistrano-generated-configura
>
> > This
Part of my rollout scripts contains a "puppet --parseonly" check of
all of our manifests and modules to do basic pre-runtime checks of
syntax (or so I thought). It basically finds all applicable modules
and echos an "import $MODULENAME" for each to the standard input of
puppet, to which I also pass
in
> puppet modules directory. You can do that trought INCROND
> (http://linux.die.net/man/8/incrond- crontab like) or homemade scripts
> (perl, python, etc).
>
> Read more at:http://www.linuxjournal.com/article/8478
Thanks, that's a good suggestion that I had considered before. I
On Oct 18, 10:22 pm, Carl Caum wrote:
> Is there a way to run your own puppetforgerepository? We are interested
> versioning and distributing our modules the same way we do our custom RPMs.
> We want to use puppet-module-tool and configure it to point to our local
> repository.
Hmm, no replie
10 matches
Mail list logo