On 24/01/12 19:53, Nigel Kersten wrote:
What if you made two functions:
1. declare_capability(foo)
This would essentially just create an empty resource, Capability[foo]. If
multiple modules tried to declare the same capability, it would error, just
like
we do today with duplicate
Hi folks,
Over the last week or so I've been banging my head against the wall trying
to get dashboard working and trying to figure out why end of file reports
are happening during some of my puppet runs. In the process of hacking
around I've managed to trash my puppetmaster so I'm going to do
On Tue, Jan 24, 2012 at 7:39 PM, Nick oinksoc...@letterboxes.org wrote:
I want to assert a file exists - but in a way that doesn't have the potential
to
create conflicting resource definitions.
I know this has been asked many times before:
How can I check whether a file exists, like
On Wed, Jan 25, 2012 at 6:11 AM, Nick oinksoc...@letterboxes.org wrote:
On 24/01/12 19:53, Nigel Kersten wrote:
What if you made two functions:
1. declare_capability(foo)
This would essentially just create an empty resource, Capability[foo]. If
multiple modules tried to declare the same
Go with Debian or an Ubuntu LTS version instead of the latest Ubuntu,
you'll have much longer support:
http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases
http://en.wikipedia.org/wiki/Debian#Releases
Enjoy!
Walter Heck
On Wed, Jan 25, 2012 at 16:48, Peter Berghold
On Wed, Jan 25, 2012 at 05:14:51PM +0200, Walter Heck wrote:
Go with Debian or an Ubuntu LTS version instead of the latest Ubuntu,
you'll have much longer support:
http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases
http://en.wikipedia.org/wiki/Debian#Releases
I concur with the
inline
On Wed, Jan 25, 2012 at 09:48:27AM -0500, Peter Berghold wrote:
Hi folks,
Over the last week or so I've been banging my head against the wall trying
to get dashboard working and trying to figure out why end of file
reports are happening during some of my puppet runs.� In
Unfortunately I am unable to reproduce this except outside the target
virtualized environment, currently unavailable due to resource concerns.
So far courier-imap and courier-pop restart as they should elsewhere.
On Tue, Jan 17, 2012 at 05:34:06PM +0100, Felix Frank wrote:
On 01/13/2012 07:08
I have been reading about the LDAP ENC at the wiki
http://projects.puppetlabs.com/projects/puppet/wiki/LDAP_Nodes.
I am considering using the LDAP ENC, but I have a couple of concerns
when it comes to the implementation.
- It seems that the example using the entry attribute 'ipHostNumber'
as a
On Jan 25, 2012, at 8:44 AM, Brian Wong wrote:
I have been reading about the LDAP ENC at the wiki
http://projects.puppetlabs.com/projects/puppet/wiki/LDAP_Nodes.
I am considering using the LDAP ENC, but I have a couple of concerns
when it comes to the implementation.
- It seems that the
I'd rather use Ubuntu LTS but that's not a valid template with my VPS
provider unfortunately. Ubuntu 11 64 bit is available and seems to work OK
for now. Debian 6 had become my standard but it would seem there was an
issue with Debian 6 and the hypervisor the VPS provider uses and last I
heard
On 25/01/12 14:57, Nan Liu wrote:
To sum up, it appears that this feature is missing for a reason, but why?
And
what's the best workaround available?
I'm assuming you mean if a resources exist in the catalog and not the
question of whether a file exist on the agent since they are
On Jan 25, 2012, at 8:30 AM, Nick wrote:
But then I have to anticipate every possible value of $shell and define
resources for them. Anything which is not defined like this is not usable
within the scheme, because there will be no file resource to realize and
require. And of course, it also
On Wed, Jan 25, 2012 at 08:53:15AM -0800, Jo Rhett wrote:
On Jan 25, 2012, at 8:30 AM, Nick wrote:
But then I have to anticipate every possible value of $shell and define
resources for them. Anything which is not defined like this is not usable
within the scheme, because there will be no
On Tue, Jan 24, 2012 at 1:28 AM, Felix Frank
felix.fr...@alumni.tu-berlin.de wrote:
Hi,
there was a discussion in the can we deprecate defined() in Telly
thread about how we can even begin to design Forge modules without it.
A recurring problem is that multiple modules rely on certain
On 25/01/12 16:59, Christopher Wood wrote:
Also, could you expound? I don't know any production scenario where it's
desirable to have anything other than an exact known configuration of hosts.
Well, it's one thing to have an exact known and audited configuration.
It'd be another to try and
Can anyone offer a reason for having a folder with a path of
/etc/puppet/modules/manifest ?
I think I got overzealous making /etc/puppet/modules/module-name/manifest
directories, but I am still new enough to Puppet to be unsure -- and I am smart
enough NOT to just delete it without checking
I don't have a solution but I do want to chime in and state that modules
that
exist just to collect together virtual resources is a horrible thing.
We're just
talking about working around the way Puppet works right now rather than
defining what the end solution should be.
I would be happiest
On Wed, Jan 25, 2012 at 9:59 AM, Ashley Penney apen...@gmail.com wrote:
I don't have a solution but I do want to chime in and state that modules
that
exist just to collect together virtual resources is a horrible thing.
We're just
talking about working around the way Puppet works right now
On 01/25/2012 06:59 PM, Ashley Penney wrote:
After all, if they've been included on the host all of those attributes
should apply so I can't see a dangerous downside to this.
Nan provided some killer arguments (imho) in the proper cross-dependency
thread.
--
You received this message because
On Wed, 25 Jan 2012 09:59:10 -0500
Nan Liu n...@puppetlabs.com wrote:
[...]
i.e. Say there were two unrelated modules which said slightly
different but *compatible* things:
Module a:
file { /foo/bar:
ensure = 'present',
owner = 'root',
content = blah blah,
}
The directory that probably represents is /etc/puppet/manifests (with an
s)... however, not seeing your puppet installation, there is a chance
that it could be needed for something. The best bet is probably to
(temporarily) move it out of the way and see if things start complaining
(puppet agent
On Thu, Jan 19, 2012 at 9:18 AM, Nigel Kersten ni...@puppetlabs.com wrote:
I'm looking for strong opinions on whether we should or shouldn't deprecate
the defined() function for Telly, the next major Puppet release this year.
jcbollinger put it quite well in another thread:
Use of the
Just got done installing apache2, passenger, puppet, dashboard over the
day...
Ran my first puppetd --test and got the following:
# puppetd --test
info: Loading facts in root_home
info: Loading facts in facter_dot_d
info: Loading facts in concat_basedir
info: Loading facts in root_home
info:
This looks like you've got a puppet agent that is newer than the version of
your master.
On Wed, Jan 25, 2012 at 12:36 PM, Peter Berghold salty.cowd...@gmail.comwrote:
Just got done installing apache2, passenger, puppet, dashboard over the
day...
Ran my first puppetd --test and got the
master and agent are on the same box. they should be the same version.
On Wed, Jan 25, 2012 at 3:53 PM, Nigel Kersten ni...@puppetlabs.com wrote:
This looks like you've got a puppet agent that is newer than the version
of your master.
On Wed, Jan 25, 2012 at 12:36 PM, Peter Berghold
do you have multiple versions of puppet installed?
If you're in bash:
$ type --all puppet{,d,masterd}
Do you get different versions returned for:
$ puppet --version
$ puppetd --version
On newer installs you should be using puppet agent instead of puppetd
(We moved to git-style subcommands a
There is only one version of puppet (agent and master) on the system. This
system was installed from bare metal this morning.
On Jan 25, 2012 4:24 PM, Nigel Kersten ni...@puppetlabs.com wrote:
do you have multiple versions of puppet installed?
If you're in bash:
$ type --all puppet{,d,masterd}
Thanks for responding.
My brain must have an excess of fuzz to not remember that method.
The old Make the Change and See If It Breaks technique ! :)
However, your observation of manifest/manifests was on target. My stray
directory has a final s, and to my delight, removing it had no (negative)
Just for completeness:
# type --all puppet{,d,masterd}
puppet is /usr/bin/puppet
puppetd is /usr/bin/puppetd
puppetmasterd is /usr/bin/puppetmasterd
# puppet --version
2.7.9
# puppetd --version
2.7.9
# puppetmasterd --version
2.7.9
On Wed, Jan 25, 2012 at 4:37 PM, Peter Berghold
Welcome to the first maintenance release for Facter in the new year.
It includes contributions from the following people: Adrien Thebo,
Barrie Bremner, Gary Larizza, Jonathan Boyett, Josh Cooper, Ken
Barber, Marcus Vinicius Ferreira, Matt Dainty, Michael Kincaid, Moses
Mendoza, Pieter Lexis
This
I was looking through the Puppet style guide for something unrelated,
and noticed that it explicitly discourages doing things in this exact
manner:
http://docs.puppetlabs.com/guides/style_guide.html - Section 11.9.
Does the style guide need updated then?
Justin
On Jan 13, 4:17 pm, Gary Larizza
If anyone has any ideas, please share. I'm at a loss.
YAML from Puppet Enterprise 2.0.0 default ENC:
---
name: rcf-cm-master.our.org
parameters: {}
classes:
- core-permissions
YAML from my Python ENC using PyYAML. This
On Wed, Jan 25, 2012 at 15:15, jblaine cjbla...@gmail.com wrote:
If anyone has any ideas, please share. I'm at a loss.
YAML from Puppet Enterprise 2.0.0 default ENC:
---
name: rcf-cm-master.our.org
parameters: {}
classes:
- core-permissions
When you run your script by hand, does it exit 0 ?
Does it do so when the user you are running the master as (pe-puppet I
believe in this case) runs the script?
On Wed, Jan 25, 2012 at 3:15 PM, jblaine cjbla...@gmail.com wrote:
If anyone has any ideas, please share. I'm at a loss.
YAML
ahah. I'm sorry, I sent you down completely the wrong path.
title405 Method Not Allowed/title
/headbody
h1Method Not Allowed/h1
pThe requested method PUT is not allowed for the URL /production/report/
slcupuppet.slc.sharkrivertech.com./p
hr
That error was for the report processor, not the
I ran into the same error briefly on RHEL 6 with Puppet 2.7.9. After
downgrading to 2.7.8 master, everything works as expected. There's so
few difference when running git diff 2.7.8..2.7.9, I can't see what
could possibly cause this bug. And in the process of trying to confirm
the bug and
Welcome to the first maintenance release for Puppet in the
new year. Since we skipped a December release, this release is rather
large.
Thanks for the help during Triage-a-thon. It was a great event. See
the Puppet Labs blog for the recap.
We have several section of release notes this month
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff,
Thanks for the concise write-up, it was really helpful for parsing through all
of the different arguments.
I would like to second the idea that Aaron Grewell had earlier that some sort
of exception handling be allowed and that some other
Yes, the code outputs nothing and calls sys.exit(1) if the host cannot be
found in our database. Running as pe-puppet, which the stock ENC runs
as from what I can tell, it runs fine and $? is 0.
[ 5 minutes later ]
Oh jeez.
I was misreading the red Log info for it, assuming it was the same
old
On Wed, Jan 25, 2012 at 17:19, jblaine cjbla...@gmail.com wrote:
IDEA: Allow for a special YAML document to be spit out by custom ENCs
when error conditions in the ENC are hit. It would contain information that
can be shown in the console/reports ?
Sounds good. I am happy to look at
This is a fantastic reply and I appreciate the work you put into it. I
have just one
question. As it stands functions can only apply to partial catalogs and
not to the
full catalog. Is this a fundamental design decision that cannot be
changed? Perhaps
it would be interesting to speculate on
No questions or problems today, just thought the list might like to
see that puppet is being used by a (another) site/company with a ton
of traffic:
http://blog.reddit.com/2012/01/january-2012-state-of-servers.html
I'm hoping I can persuade them to talk a bit more about how they use
puppet and
On Wed, Jan 25, 2012 at 5:25 PM, Ashley Penney apen...@gmail.com wrote:
All I know is that telling users If you download 5 modules from puppet
forge
make sure you go through them all, extract any duplicating resources into
random modules that exist purely to allow you to realize packages
44 matches
Mail list logo
