I've always thought there should be an implicit X::disabled class that gets
included for every host where X isn't included.
Then if I create said class, it gets automatically executed on all hosts that
don't include X. As it is now, one still has to go through and add X::disabled
to every host
No, you're right, at least as far as I've been able to tell – though I
certainly may have overlooked something.
The puppetmaster only gets the configs from one environment, so you're stuck
using that. There are other consequences as well, such as defined resources
using the definition in the se
>
> Puppet does not keep track of the state before applying a resource.
> Even if Puppet *did* track prior state, there would still be an issue
> of choosing which of possibly many prior states to revert to.
I'm not asking puppet to know what to do, which I agree is ridiculous. I'm
saying that i
>
> That still isn't sensible. It simply is not safe to assume that the
> absence of class X in a node's catalog is a signal that X::disabled
> should be included in that catalog. For instance, suppose I have a
> pair X, X::disabled of classes specific to OS X. I don't want *either
> one* on my
[Following up a little late]
> Is anyone using node inheritance and happy with how it works? If so, can you
> describe your setup briefly?
I make very limited use of node inheritance. I use
node basenode {
include $operatingsystem
[other stuff I want absolutely everywhere]
}
node default i
In testing the move to 0.25 (tried with both 0.25.0 and 0.25.1rc1),
I'm now getting the following error, seemingly everywhere that notify/
require is used:
For example:
err: Could not run Puppet configuration client: Parameter notify
failed: No title provided and title '{"title"=>"smb",
"t
On Sep 29, 2009, at 10:25, Darrell Fuhriman wrote:
> In testing the move to 0.25 (tried with both 0.25.0 and 0.25.1rc1),
> I'm now getting the following error, seemingly everywhere that
> notify/require is used:
As an additional piece of info, 0.24.8 client continue to functi
> Is it that you're using Service[smb] rather than Service['smb'] ?
I thought of that, but that doesn't seem to matter - the other example
I give uses single quotes everywhere, and other failures are similar.
d.
--~--~-~--~~~---~--~~
You received this message
Well, I've tracked it down a bit further.
I updated activerecord to 2.3.4 before installing puppet, since I'm
using storedconfigs. If I remove this gem and leave 2.2.2 installed,
everything seems to work as expected.
So, tracking it down a bit further, it seems that everything works
with A
>
> sort of git hook, but I'm not sure how to implement it efficiently and
> securely with a shared repository on another server. I went looking
I thought about this, but abandoned it. Hooks in git have to be
configured on each repository, since there is no central repository,
as such.
I k
10 matches
Mail list logo
