> > There is a hook for types that gets called when catalog compilation is
> > complete, but it then only calls the relationship params giving them a
> > chance to resolve their relationships. I'm currently working on a pull
> > request to change that situation though.
> >
>
> Could you give s
On 08/26/2013 11:41 AM, Andy Parker wrote:
> How would you handle reloading in this scenario?
>
>
> I can think of two ways: track all of the files loaded and reload when
> something changes or is added, reload only when told. I lean towards the
> "reload only when told" for a production mast
On Aug 26, 2013, at 2:47 PM, Ashley Penney wrote:
On Mon, Aug 26, 2013 at 5:04 PM, markus wrote:
>
>
> > > I think the system needs to change to eager loading of manifests
> > > (not applying them all, but at least loading them all).
>
> Eager loading all manifests (e.g. by a directory search)
On Mon, Aug 26, 2013 at 5:04 PM, markus wrote:
>
>
> > > I think the system needs to change to eager loading of manifests
> > > (not applying them all, but at least loading them all).
>
> Eager loading all manifests (e.g. by a directory search) could change
> the semantics in unexpected ways, and
> > I think the system needs to change to eager loading of manifests
> > (not applying them all, but at least loading them all).
Eager loading all manifests (e.g. by a directory search) could change
the semantics in unexpected ways, and could fail in cases that would
otherwise work (e.g. if the
On Mon, Aug 26, 2013 at 11:15 AM, Luke Kanies wrote:
> On Aug 26, 2013, at 10:49 AM, Andy Parker wrote:
>
>
> The conclusion that we came to was that the current lazy-loading of puppet
> manifests needs to go away. Lazy loading makes all of the information to
> correctly load types at the right
On Aug 26, 2013, at 10:49 AM, Andy Parker wrote:
> Adrien put a lot of effort into tracking down what was happening in #15106
> (Missing site.pp can cause error 'Cannot find definition Class'). That exact
> issue, as described in that bug, has been fixed, but in the investigation
> Adrien figu
On Mon, Aug 26, 2013 at 10:48 AM, Dustin J. Mitchell wrote:
> The current situation is that master monitoring basically consists of
> a no-op HTTP request. We'd like to get to a point where it includes
> live status of the master. It makes sense for that live status to
> include among other thin
Adrien put a lot of effort into tracking down what was happening in #15106
(Missing site.pp can cause error 'Cannot find definition Class'). That
exact issue, as described in that bug, has been fixed, but in the
investigation Adrien figured out that there are a lot of other problems
that can crop u
The current situation is that master monitoring basically consists of
a no-op HTTP request. We'd like to get to a point where it includes
live status of the master. It makes sense for that live status to
include among other things some manually-flippable "in_service?" kind
of switch.
My understa
I just read over the PR that you linked to. It looks like an interesting
idea, but I have to wonder about it a little bit. This proposal isn't to
add automated metrics to the puppet master to keep track of things like
compile stats, file request stats, etc. It is more of a manual mechanism
for the
Yes - examples will definitely clear up confusion for anyone who has
the same experience as me (which may be very few people!)
Dustin
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails
On Sat, Aug 24, 2013 at 8:09 PM, Tom Linkin wrote:
> Dominic,
>
> I have done this before: https://github.com/trlinkin/puppet-file_param
>
>
A few other things have done this as well. Usually it is when there is a
"resource" that is needed to manage another resource, but isn't a resource
itself
On 2013-26-08 2:26, Dustin J. Mitchell wrote:
On Sun, Aug 25, 2013 at 6:47 PM, Henrik Lindberg
wrote:
At the technical parsing level, yes. This is then validated to only include
what we want to allow. The first implementation is very permissive.
Oh! Then, my reading of the ARM was wrong - I
14 matches
Mail list logo
