We have a Puppet config that stores files outside of modules, along with
appropriate auth.conf entries to support this.For the most part, it has
just worked and I haven't felt any need to muddle with it - so I was
surprised to find a bevy of these errors in the logs:
Mar 11 18:24:51 centra
like this because they help me
learn more about Puppet.
Jon Forrest
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegrou
the problem.
I'm not sure why this works. I suspect it's because adding the ".x86-64"
somehow prevents the pattern from matching Percona. I'm going to
check this.
This approach is easier than creating a custom fact.
Thanks for all the suggestions.
Jon Forrest
--
You
On 4/24/2014 7:01 AM, jcbollinger wrote:
That's not necessarily a naive assumption, but it does suggest that you
haven't fully grasped the Puppet paradigm. You seem to be thinking in
terms of how to persuade Puppet to execute specific commands, but you
should be thinking in terms of how to accu
ebuild to change what Percona provides
2) Use something like (untested)
exec { "/usr/bin/yum -y remove mysql":
onlyif => "/bin/rpm -qa |/bin/fgrep mysql"
3) Just presume that MySQL won't be installed in the first place.
I could do this but I'd like my modules to be mor
deleted. However, this package wasn't
actually installed, e.g.
# rpm -qa | fgrep PackageKit
#
Why would that second message appear? I didn't ask for the
package to be created, plus the package wasn't actually created.
Thanks,
Jon Forrest
--
You received this message because you
On Wed, Apr 23, 2014 at 8:54 AM, jcbollinger wrote:
>
>
> On Tuesday, April 22, 2014 2:16:22 PM UTC-5, Jon Forrest wrote:
>>
>> (I found a discussion from 6/22/09 on this topic, but that was a long time
>> ago.)
>
> Did the discussion give you reason to think that
(I found a discussion from 6/22/09 on this topic, but that was a long time
ago.)
Using Puppet 3.5.1 on CentOS 6.5 I recently created the following:
package {
[ "PackageKit"]:
ensure => absent,
}
However, when I ran Puppet, I got
Error: Execution of '/bin/rpm -e PackageKit-0.5.8-2
#x27;t care about typos, grammar, style, or
formatting can ignore all that and only look at the true errors.
I knew that not everyone would be interested in what I found. That's
why I clearly labeled my postings so that people who didn't care about
issues in the book could ignore what I
://www.dropbox.com/s/qmcdgdo4bvq620q/propuppet2.txt
Jon Forrest
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To v
Here are the issues I found in Chapters 11 and 12.
Jon Forrest
M = mistake
U = unclear
T = typo
E = text change
C = comment
(U) Pg. 249 Most readers won't know what "an orchestration framework" is.
I know I don't.
(C) Pg. 249 "commands dispatched to systems in this
On 3/22/2014 4:03 PM, Julien Deloubes wrote:
Hi John,
thanks for your work.
I think i found another typo or maybe there is something i don't understand?
(T) Pg. 51 "file { ::$ssh::params::ssh_service_config:" ->
"file { $::ssh::params::ssh_service_config:"
Very good find. I missed that one. I'
Here are the issues I found in Chapters 10.
Jon Forrest
M = mistake - all readers should be aware of this
U = unclear - chances are readers will wonder about this
T = typo - a trivial uncontroversial text change
E = text change - most readers won't care but editors should
C = comment -
Here are the issues I found in Chapters 8 and 9.
Jon Forrest
M = mistake
U = unclear
T = typo
E = text change
C = comment
(T) Pg. 191 "like librarian puppet" ->
"like librarian-puppet"
(T) Pg. 191 "rspec-puppet, rspec-system and integrating" ->
"rspec-p
ob is located, or whether telecommuting
is allowed.
Jon Forrest
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.co
Here are the issues I found in Chapter 7. Short chapter - many typos.
Only 5 more chapters to go.
Jon Forrest
M = mistake
U = unclear
T = typo
E = text change
C = comment
(M) Pg. 169 "an external node carrier (ENC)" ->
"an external node classifier (ENC)"
(C) Pg. 169
on with Apress
> and the other authors.
>
> Thanks again,
> Spencer
>
> On Monday, March 10, 2014 4:31:26 AM UTC, Jon Forrest wrote:
>>
>>
>>
>> On Wednesday, March 5, 2014 10:29:07 AM UTC-8, Spencer Krum wrote:
>> Hi Jon,
>>
>> > My n
at do you think?
What I'm planning on doing is continuing on as I have been. I'm going to
post my lists, chapter
by chapter, to this list. You, and anybody else, are free to do whatever
you want with them, such as putting
them up on GitHub. I clearly label these postings so any
Here are the issues I found in Chapter 6. There were an awful lot
of typos.
Jon Forrest
M = mistake
U = unclear
T = typo
E = text change
C = comment
(E) Pg. 155 "multiple hosts that have a relationship" ->
"multiple related hosts"
(E) Pg. 155 "resources and their i
(unless yours is better). It's too bad this book has so many issues.
I wasn't expecting this when I started. It's almost as if nobody proof
read it, although its editor tells me otherwise.
Jon Forrest
--
You received this message because you are subscribed to the Google Grou
Here are the issues I found in Chapter 5.
M = mistake
U = unclear
T = typo
E = text change
C = comment
(T) Pg. 141 "classes, inheritance, variables and environment configuration" ->
"classes, inheritance, variables, and environment configuration"
(E) Pg. 141 "This integration is used" ->
"This i
Again, nothing that a good proof edit couldn't fix.
Jon Forrest
(U) Pg. 100 Listing 4-2 shows package resource definitions appearing as
the result
of running 'puppet resource service'. Are we supposed to do anything
with these definitions?
(U) Pg. 100 In Listing 4-2 why
again
in the 2nd edition. This error even appears in their errata for
the 1st edition.
In spite of what appears below, I think Pro Puppet is pretty good,
and is definitely worth reading. But Apress better be careful, because
they're in danger of becoming as bad as Packt in their editorial
qua
; with the ";vdsmdummy;" bridge device.
>
I'm having the same problem on a node without Infiniband, but with VDSM
installed. This is with
version 1.7.5 of facter on CentOS 6.5 (with all patches).
This doesn't seem to prevent anything from working. It would be nice if it
ything else) is wasteful. In time, the lack of
client parallelization
could be a competitive weakness as Puppet competes in the marketplace.
(I don't know
what the status of client parallelization is in the competition right now).
Jon Forrest
--
You received this message because you are sub
ow which actions
it should do safely in parallel.
If any other the experts have anything to add I'd love
to hear it.
Jon Forrest
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiv
Puppet did not like that:
Sep 12 01:08:18 my-server puppet-agent[10063]: Failed to apply catalog:
Parameter ensure failed on Service[pcscd]: Invalid value "disabled".
Valid values are stopped, running. at
/etc/puppet/manifests/classes/disabled-services.pp:10
I changed it back to "ensure =>
it.
Adding
File
{
mode => 644,
}
to the class makes the problem go away but this really
isn't a solution.
Any ideas what might be causing this?
Cordially,
Jon Forrest
--
You received this message because you are subscribed to the Google Groups "Puppet
Users"
/docs.puppetlabs.com/references/stable/type.html#file
there is a sample resource definition that also contains
"backup => main" but it doesn't answer this question.
I'm guessing that it just means the puppetmaster server but
it would be nice to see the official definition.
Cordi
On 3/4/2012 8:12 PM, Brian Troutwine wrote:
(First of all, sorry for the jumbled first paragraph. I was
trying to do two things at once).
An interesting thought. If you enable graph output in your puppet.conf
http://docs.puppetlabs.com/references/stable/configuration.html#graph
you can i
this. Am I missing something? Is this a good
idea?
Cordially,
Jon Forrest
--
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
you improve your junk email filter. I believe it's
not the job of the list maintainer to "protect" email addresses
unless the maintainer claims up from that postings will be
anonymous.
Cordially,
Jon Forrest
--
You received this message because you are subscribed to the Google
do a regular run.
In fact, this is only a special case of the more
general problem of getting access to any file generated
by a puppet run without actually putting the files
in the ultimate destination. In other words, it would
be like a --test run except files will be generated and
kept.
Jon Fo
On 9/10/2011 6:57 PM, Jonathan Stanton wrote:
Maybe I'm missing something here, but I think Jon was asking
something a bit different -- he doesn't want to check the validity of
the erb template (i.e. ruby syntax check) but syntax check the named
zone file generated by the template.
Precisely.
making a normal puppet run so that the bad
files won't get distributed.
Can anybody point me to a technique for doing this?
Cordially,
Jon Forrest
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email
;ve found so far. Some of these are
embarrassingly trivial but some are true mistakes. I expect
to find more.
Jon Forrest
--
Pro Puppet Errata
M = mistake
U = unclear
T = typo
E = text edit
(E) 1) Page 1, first two sentences. "configuration" -> "configurations"
(U)
rename it to ruby.1.8.7 with a
symlink of "ruby" so that the installation is consistent with shebang paths.
Yeah - complex. :)
You are, of course, right :-)
Thanks,
Forrest
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&quo
ne problem I've observed is ruby will need to be "installed" in
/local/company/ruby first, where I later rename it to ruby.1.8.7 with a
symlink of "ruby" so that the installation is consistent with shebang paths.
Thanks,
Forrest
--
You received this message be
38 matches
Mail list logo
