Hi all,
Our Puppet t-shirts are due for a redesign:
http://www.puppetlabs.com/blog/tshirt-contest/
Be sure you submit cool tagline for our new shirts and enter for a chance to
win an Ar.drone (
http://store.apple.com/us/product/H1991ZM/A?fnode=MTY1NDA3NA&mco=MjA1MTA3MzY
)
and a ticket to Puppet C
Hi Patrick,
On 02/11/2011 07:40 PM, Patrick wrote:
[...]
> 1) So, just some random advice. If you're using the same server to
> serve files and catalogs, you can skip listing the server and just
> use 3 slashes like this:
> puppet:///files/rpm-sles11sp1/ruby-shadow-$myrshadowversion.x86_64.rpm
Jacob Helwig wrote:
> We're back with a maintenance release: 2.6.5. This release addresses a
> number of bugs in the 2.6.x branch and adds a handful of features and
> documentation updates.
For those using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/
Thanks for the 411, Looks like I will just deal with the config file
on the client. I can't say that would be my preferred way but I can
deal with that.
Thanks for the reponses and it's not a big deal. I can't complain too
much when my work load is going to be decreasing greatly when I get
this
On Fri, Feb 11, 2011 at 11:52 AM, Monkeys Typing
wrote:
> I have a mostly working set of modules to replace our kickstart and
> about a dozen scripts.
>
> I am having issues with attempting to populate my AD account-owned
> user folders in the initial puppet run. The machines i am testing
> with
I have a mostly working set of modules to replace our kickstart and
about a dozen scripts.
I am having issues with attempting to populate my AD account-owned
user folders in the initial puppet run. The machines i am testing
with are all CentOS 5.5 so far.
I have defined 3 additional stages,
Stag
BTW: I'm using puppet 0.25.5
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more o
I'm running puppetmaster with passenger and it's breaking my puppetrun
capabilities. If run puppetrun running from webbrick it runs, if I run it
with apache/passenger, it gives me an error.
bash-3.2# /usr/sbin/puppetrun --host client.dev.domain.com
Triggering client.dev.domain.com
warning: pe
On Fri, Feb 11, 2011 at 10:30 AM, trey85stang wrote:
> Finally figured it out, Maybe this is a bug I am not sure. But I was
> setting the environment only from the external_nodes script. I was
> not making any changes to the client config. When I add the
> environment to the puppet.conf on the
On Fri, Feb 11, 2011 at 01:34, luke.bigum wrote:
> Before I raise a feature request, is there a way to force the name of
> the .repo file a yumrepo is created in?
Nope, sorry. The code doesn't support that at this time. Fixing it
wouldn't be terribly hard, and as long as the default behaviour
On Fri, Feb 11, 2011 at 00:40, Thorsten Biel wrote:
> On Feb 11, 2011, at 07:25, John Warburton wrote:
>
>> Does anyone have any experiences with puppet in the DMZ they can share?
[…]
>> How do people get around the "common" rule that DMZ servers should not
>> initiate network connections back to
On Feb 11, 2011, at 3:31 AM, Jan wrote:
> Hi *,
>
> we have plans to handle the update process of puppet related packages by
> our local update server. However, for now we need do deal with the
> situation by fetching the respective rpms to the client and install them
> by using the rpm provider
On 11/02/11 18:06, Jason Wright wrote:
> I've completed rolling out 2.6.3 and it's completely resolved our issues.
That's terriffic!
Thanks for sharing this good news.
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
You received this message because you are subscribed to the Google Group
On Feb 11, 2011 10:30 AM, "trey85stang" wrote:
>
> Finally figured it out, Maybe this is a bug I am not sure. But I was
> setting the environment only from the external_nodes script. I was
> not making any changes to the client config. When I add the
> environment to the puppet.conf on the cli
Finally figured it out, Maybe this is a bug I am not sure. But I was
setting the environment only from the external_nodes script. I was
not making any changes to the client config. When I add the
environment to the puppet.conf on the client everything now works as
expected.
Not exactly the way
On Thu, Feb 3, 2011 at 7:53 AM, Felix Frank
wrote:
> On 02/03/2011 04:46 PM, Matthew Macdonald-Wallace wrote:
>> OK, thanks, that answers the question about whether we can go
>> backwards (we can't, we're using Regexes and a few other things!)
>>
>> Anyone know if a Puppet 2.6.2 client can talk to
On Fri, Feb 11, 2011 at 9:06 AM, Jason Wright wrote:
> I've completed rolling out 2.6.3 and it's completely resolved our issues.
>
> Thanks for the help,
Wahoo! That's awesome to hear Jason.
It might be worth starting canarying 2.6.5rc2, as you're doing report
submissions, and we've got a fix in
I'm having an issue solving dependencies inside defines, where the paths to
various resources are variable. It seems like puppet isn't expanding all of
the variables when it constructs the catalog, so it's unable to find the
resources necessary to build things in the right order.
I've construc
I've completed rolling out 2.6.3 and it's completely resolved our issues.
Thanks for the help,
Jason
On Wed, Feb 9, 2011 at 12:18 PM, Jason Wright wrote:
> I rolled out 2.6.3 to four puppetmasters yesterday as part of a canary
> and while it's been less than 24 hours, there are already encouragi
Hi all,
I'm running puppet 0.25.5 and I'm running into an issue with virtual
defines for setting up my NGinx Vhosts.
The define is as follows:
class nginx{
...
# Setup a resource to create the configuration files
define nginx_vhost($website_listen_port = "80",$ssl_enabled = "false"){
$
Hi *,
we have plans to handle the update process of puppet related packages by
our local update server. However, for now we need do deal with the
situation by fetching the respective rpms to the client and install them
by using the rpm provider.
So in order to proceed with the installation I woul
You can put a puppet server in the DMZ that you deploy puppet manifest
changes to via SSH, then only allow 8140 access to the dmz boxes. I
would say shipping catalogs out there is sort of overkill. You can also
make this master use a separate CA, etc. I think a few simple measures
like this wou
On Feb 11, 2:24 am, Felix Frank
wrote:
> Ah, not quite - puppet drops it privileges when installing authorized
> keys and does it as the target user. There is an interesting bug in
> 0.25.5 that will keep puppet from filebucketing and thus installing keys
> because of this behaviour, but I digre
Hi list,
Before I raise a feature request, is there a way to force the name of
the .repo file a yumrepo is created in? By default if no existing repo
exists, the file name that gets created for it is $name.repo. It would
be nice if you could specify the file name, for example on CentOS
systems you
Hi,
On Feb 11, 2011, at 07:25, John Warburton wrote:
> Does anyone have any experiences with puppet in the DMZ they can share?
>
> At my puppet master training (Hi Hunter), it was mentioned some people
> compile their catalogs inside, then ship them out to servers in the DMZ to be
> applied.
>> 4 drwx-- 2 neuroadm neuro 4096 Feb 3 21:02 .
>> 4 drwx-- 3 neuroadm neuro 4096 Feb 3 21:02 ..
>> 4 -rw--- 1 root root 578 Feb 3 21:02 authorized_keys
>
> So Puppet is sometimes failing with a permission failure while
> attempting to synchronize the authorized_keys resource.
On Thu, Feb 10, 2011 at 12:59, Forrie wrote:
> Facter will display the values associated with network_* specific
> settings. Shouldn't there be a way to display all connected (active)
> networks in one command? For example:
FWIW, I would say the answer is best: not while facter only returns
>> the background. However, (per orig post) the result of no quotes:
>
>> ... require => Package[$packagelist], ...
>
>> was the following :
>
>>> warning: Not using cache on failed catalog
>
>> ... and the somewhat obscure:
>
>>> warning: Configuration could not be instantiated: w
On Thu, Feb 10, 2011 at 22:25, John Warburton wrote:
> Does anyone have any experiences with puppet in the DMZ they can share?
We looked at how to integrate puppet into a network that needed
medical-in-confidence certification back in Australia, which is
probably about the same level of security
Hi.
On 02/09/2011 03:08 AM, Liberty Young wrote:
> All,
>
> In my test bed, i've noticed that the init.d script as present in the
> git source (puppet-2.6.4/conf/redhat) doesn't seem to work. Puppet
> fails to periodically update its configuration cached, reporting in
> var/log/message
> "puppet-
30 matches
Mail list logo
