On 09/30/2014 09:23 PM, Garrett Honeycutt wrote:
> On 9/30/14 7:17 PM, Tom Tucker wrote:
>>
>> I just got back from PuppetConf last week and several presenters
>> mentioned using more than one Git repo with Puppet. Some even recommend
>> having a repo per module. For our initial Puppet deployment
On 9/30/14 7:17 PM, Tom Tucker wrote:
>
> I just got back from PuppetConf last week and several presenters
> mentioned using more than one Git repo with Puppet. Some even recommend
> having a repo per module. For our initial Puppet deployment this seems
> a bit excessive. My plan was to have th
All,
Puppet Enterprise 2.8 is now end of life. This brings to a close the
last chapter of the Puppet Enterprise 2 series, as previously
communicated in the Puppet Enterprise Lifecycle[1].
Puppet Enterprise 2.0 was released on November 16, 2011. Since then,
we have added major capabilities, expand
I highly recommend going with Gary Larizza’s functional puppet workflow unless
you’ve got lots of prior experience. You can find part 1 here:
http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-1/
It’s a 3 part series, and there are good follow-ups on r10k and environments
(http://garyl
I just got back from PuppetConf last week and several presenters mentioned
using more than one Git repo with Puppet. Some even recommend having a
repo per module. For our initial Puppet deployment this seems a bit
excessive. My plan was to have three repos for each of our environments
(Dev, QA a
Does the directory /var/run/puppet exist and is that directory writable? Go
to it and try the command 'touch test' as root.
John
John Kennedy (_8(|)
I have a yellow dog:
http://www.theyellowdogproject.com/The_Yellow_Dog_Project/About.html
Anatidaephobia is the fear that somehow, somewhere a duc
I have a particular question about an error message I keep receiving. I
have installed Puppet on Centos 6.5. I have two servers running. One as the
Puppet Master and the other as the Puppet client.
Every time I run this command: puppet master --verbose --no-daemonize
as the root user
I get t
On 9/30/14 2:50 PM, Nicolas lino wrote:
> Hello and sorry for my English.
>
> I have my first module but I have a prblem:
>
> My manifest:
> #
> #
> #
> class nginx {
> $nginx_conf = '/etc/nginx/conf.d'
>
> service { 'nginx':
> ensure => running,
> enable => true,
> hasre
On Sep 30, 2014, at 2:50 PM, Nicolas lino wrote:
> Hello and sorry for my English.
>
> I have my first module but I have a prblem:
>
> My manifest:
> #
> #
> #
> class nginx {
> $nginx_conf = '/etc/nginx/conf.d'
>
> service { 'nginx':
> ensure => running,
> enable => true,
Hello and sorry for my English.
I have my first module but I have a prblem:
My manifest:
#
#
#
class nginx {
$nginx_conf = '/etc/nginx/conf.d'
service { 'nginx':
ensure => running,
enable => true,
hasrestart => true,
require=> File['/etc/nginx/nginx.conf'],
re
Hi all,
We are busy migrating out puppet 2.7 code to puppet 3 and have run into a
problem where we are getting dependency cycles when using tidy.
This mostly happens with stages (and yes, I completely understand why we
should avoid them).
As an example we have a defined class that we use to cre
Thanks a lot to everyone, I'll research on those topics!.
Regards,
Ciro
El sábado, 27 de septiembre de 2014 12:09:33 UTC-4, Jason Antman escribió:
>
> IMO...
>
> The "right" way to do this is to use a parameterized class in your module
> that generates the config files.
>
> Beyond that, it's up
Hunter Haugen writes:
> We actually have a load of tickets in our next sprint to enable future
> parser testing on all of the supported modules and go through making them
> compatible, starting Oct 1st. Good timing on your question, bad timing that
> it's taken us this long to get to it :(.
On Saturday, September 27, 2014 4:52:16 PM UTC-5, bluethundr wrote:
>
> Hello,
>
> When I tried adding a node to my puppet server running puppet 3.7.1 (on
> both server and the client) I'm getting an error stating that puppet can't
> find the node definition:
>
> Warning: Unable to fetch my nod
On Tuesday, September 30, 2014 3:29:23 AM UTC-5, Benjamin Priestman wrote:
>
> I've always used import, not include to get my node definitions into
> site.pp. the new way of doing it, I believe, is to use a manifest
> directory. See
> https://docs.puppetlabs.com/puppet/latest/reference/lang_im
On 09/29/2014 05:19 AM, Kylo Ginsberg wrote:
>
> I'm good with JVM, but C++ feels like a backward step in many
> regards. My judgment here may be clouded by reading too many
> blogpost of them naysayers.
>
>
> C++ should be a forward step from a performance/footprint perspective.
> I'm
On Tuesday, September 30, 2014 1:21:41 AM UTC-5, Richard wrote:
>
> I want to remove all influences have been produced by puppet
> script when the agent failed in executing catalog. so i think if i can use
> resource collectors to collect all the resource using some tag then change
On Monday, September 29, 2014 2:28:02 PM UTC-5, Sam Coffland wrote:
>
> I came a across this post and like what I see but would off the following
> addition to Ian's suggestion so that the expire cache is not executed on
> every puppet run.
>
> exec { 'yum-clean-expire-cache':
> com
>
> I've always used import, not include to get my node definitions into
> site.pp. the new way of doing it, I believe, is to use a manifest
> directory. See
> https://docs.puppetlabs.com/puppet/latest/reference/lang_import.html
Cool! Thanks I'll give that a try. I actually tried it before witho
I also faced with same problem and setting metadata_expire to 1 minute
works for me. Schedule yum clean in puppet run is not good idea, because
you always get at least one resource changed, and never will green nodes in
puppet dashboard.
On Thursday, November 18, 2010 10:56:56 AM UTC+2, Daniel
I've always used import, not include to get my node definitions into site.pp.
the new way of doing it, I believe, is to use a manifest directory. See
https://docs.puppetlabs.com/puppet/latest/reference/lang_import.html
--
You received this message because you are subscribed to the Google Groups
21 matches
Mail list logo
