On Wed, May 27, 2009 at 2:49 AM, Sheldon Hearn wrote:
>
> Hi folks,
>
> Is puppetshow still a going concern?
>
> it is referred to by the Puppet Wiki's DocumentationStart page, but
> the target URL produces an "Environment not found" error message:
>
> http://reductivelabs.com/trac/puppetshow
>
>
Greg wrote:
> Only way I know is to make individual objects depend on other objects.
> Can't do it at
> class level... I think there is a feature request somewhere in the
> system for this, because
> I'd like it as well...
>
> Greg
>
> On May 27, 9:56 pm, philipp Hanselmann
> wrote:
>> May some
Hi all,
I have an interesting one - Solaris uses a lot of commands to
configure specific items. A simple
example is coreadm. In this example:
# coreadm -p "/var/core/core_%n_%f_%u_%g_%t_%p"
will set the directory and filename to dump core files (with some
expansion).
The question is - how t
Only way I know is to make individual objects depend on other objects.
Can't do it at
class level... I think there is a feature request somewhere in the
system for this, because
I'd like it as well...
Greg
On May 27, 9:56 pm, philipp Hanselmann
wrote:
> May somebody has answer ...
>
> How can I
On 2009-May-27, at 2:27 PM, Todd Zullinger wrote:
> I can't imagine what that might be though. There aren't any scripts
> or triggers in the augeas* or ruby-augeas packages. Not that I'm
> trying to rule out the unexplained. :)
Yes, since it's not as reproducible as I thought, I meant to add
Rob McBroom wrote:
> This is one that was causing problems. I'm pretty sure the "changes"
> were already in place, so puppet didn't need to do anything.
>
> augeas { "main.cf":
>require => Package["postfix"],
>context => "/files/etc/postfix/main.cf",
>changes => [
>
Hi,
I had the same problem last week and i solved it by creating a facter
plugin that returns all the mountpoints used on my system. I then use
and "if" statement in Puppet configuration to check whether the mount
fact exists or not to do what i want.
I don't know if is the best method to do tha
How do you manage permissions on mount points? Maybe I am missing
something obvious here, but I can't figure out a non-convoluted way to
do this. I want the actual mount point to have 755 permissions, but,
once mounted, the filesystem should have 1777 permissions (ie., /tmp).
I want different p
On 2009-May-27, at 11:24 AM, Todd Zullinger wrote:
> What did the manifests look like?
This is one that was causing problems. I'm pretty sure the "changes"
were already in place, so puppet didn't need to do anything.
augeas { "main.cf":
require => Package["postfix"],
contex
Got it. This was the heart of the issue - I had set the filebucket
backup as "puppet" when i followed the AdvancedPuppetRecipe. Guess
that's what happens when you set a config without knowing what it
does. Now that I realize what a filebucket is, this makes total
sense.
Thanks a bunch for the h
On Wed, May 27, 2009 at 10:10 AM, Todd Zullinger wrote:
> Evan Hisey wrote:
>> The reason augeas is not a dependency is because puppet works just
>> fine without it and a lot of sites do not want or need the extra
>> functions that augeas provides, kind of like the way puppet does not
>> require
Evan Hisey wrote:
> The reason augeas is not a dependency is because puppet works just
> fine without it and a lot of sites do not want or need the extra
> functions that augeas provides, kind of like the way puppet does not
> require any particular software provider to be installed. It is an
> ext
On Wed, May 27, 2009 at 9:54 AM, Rob McBroom wrote:
>
> This may or may not be the right place to ask this, but I'm sure it'll
> lead me there.
>
> I'm using Puppet packages from EPEL (thanks to whoever provides these).
>
> I pushed out some new configs that use Augeas to make changes and they
>
Rob McBroom wrote:
> This may or may not be the right place to ask this, but I'm sure
> it'll lead me there.
>
> I'm using Puppet packages from EPEL (thanks to whoever provides
> these).
Heh, the hard work is writing puppet. Packaging it is relatively
simple.
> I pushed out some new configs that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nigel Kersten wrote:
>>
>> The code is at:
>>
>> http://github.com/shadoi/puppetshow/
>>
>> I've fixed the link.
>
> The github page still has http://reductivelabs.com/trac/puppetshow as
> the homepage link btw James.
>
I know I pinged Blake about
This may or may not be the right place to ask this, but I'm sure it'll
lead me there.
I'm using Puppet packages from EPEL (thanks to whoever provides these).
I pushed out some new configs that use Augeas to make changes and they
threw errors on most of my servers. Installing the "augeas" pac
On Wed, May 27, 2009 at 3:45 AM, James Turnbull wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Sheldon Hearn wrote:
>> Hi folks,
>>
>> Is puppetshow still a going concern?
>>
>> it is referred to by the Puppet Wiki's DocumentationStart page, but
>> the target URL produces an "Envi
May somebody has answer ...
How can I ensure that certain classes get executed on the client side
before the other ones do?
Have a look on the example:
class AA
case $operatingsystem {
"redhat": { include AA::do-first }
default: {}
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sheldon Hearn wrote:
> Hi folks,
>
> Is puppetshow still a going concern?
>
> it is referred to by the Puppet Wiki's DocumentationStart page, but
> the target URL produces an "Environment not found" error message:
>
> http://reductivelabs.com/trac/
Ok, so here's an update ... I think we're getting closer to the
problem.
Since the VMs acquire a new IP each time I start them I made an entry
in the /etc/hosts for the host
puppet.testing.com
Here's what happened on the server and client windows when running
both on the same box:
--- server --
Hi folks,
Is puppetshow still a going concern?
it is referred to by the Puppet Wiki's DocumentationStart page, but
the target URL produces an "Environment not found" error message:
http://reductivelabs.com/trac/puppetshow
If puppetshow is defunct, what are people using as a visual interface
in
Hi
>> Peter Meier wrote:
>>
>>> imho the tripple slashes just mean: puppet://puppet/
>>>
>>> So you might want to do: puppet://$server/
>>
>> I know the first statement isn't correct, since I use triple slashes all
>> the time, and my server's name isn't puppet. The second statement should
>> wor
Hi
> OK, looks like when you use "puppet://puppet.something.com/file",
> puppetbucket.addfile ends up parsing that as just "puppet" - I tried
> changing it to something like "puppet://random.something.com/file" and
> then puppetbucket.addfile looks at random.something.com instead.
> Looks like na
OK, looks like when you use "puppet://puppet.something.com/file",
puppetbucket.addfile ends up parsing that as just "puppet" - I tried
changing it to something like "puppet://random.something.com/file" and
then puppetbucket.addfile looks at random.something.com instead.
Looks like naming puppet ma
One of the reasons I initially missed these command line options is because
I apparently have an issue with "--help" and the fact that I installed
puppet using a gem. Is there some easy way of fixing that? Or is there a
webpage that lists all the command-line args that I'm not seeing?
On Wed, Ma
2009/5/27 Brian Ferris :
> I understand that I can only edit files where permissions allow. But can I
> run puppet without a "puppet" user?
>
> Basically, after reading over the documentation, I noticed a number of
> references to users ("puppet") and paths (/var/...) that puppet needs to run
> t
Hm, it looks like it's not just "puppet:///" - when i specify
puppet://puppet.dev.clarencetso.com, the puppetbucket.addfile xmlrpc
call still ends up trying to look for "server puppet"
(I'm on the newest puppet version btw)
On May 27, 2:49 am, Clarence Tso wrote:
> Hi there,
>
> Thanks for the
27 matches
Mail list logo
