Hi,
bumping an older thread, because that just caught my eye.
On 01/21/2014 11:39 PM, Pete Brown wrote:
I would suggest putting defaults in your modules so you don't need to
set so many variables.
I started actively avoiding that, actually, for the reason that hiera
values may see use in
On Thursday, 6 February 2014 21:37:55 UTC, Larry Fast wrote:
The default value for the private key path in the eyaml CLI is
./keys/private_key.pkcs7.pem. Is there an CLI option to override the
default?
yep :)
$ eyaml --help
Hiera-eyaml is a backend for Hiera which provides OpenSSL
Hey all,
I made a little progress. Turns out that my directory structure under the
'rack' directory may have been contributing to some of the problems I had
been facing.
Originally I had
[root@puppet:/etc/puppet] #tree rack/
rack/
├── tmp
├── public
└── puppetmasterd
└──
Hi,
good thinking, but the CA certificate is not used when accepting SSL
connections (or it shouldn't be, as far as I'm concerned).
You can determine the certificate that is presented using
openssl s_client -connect puppetserver.ops.ss:8445 (assuming that is
your masterport).
You may need to
hey guys,
got it solved! turns out there was nothing wrong with the way it was
configured. Just that the disk had become full. So I cleared some space and
it started working.
[root@puppet:/etc/puppet] #puppet agent --test
Info: Loading facts in
Gareth/Garret
Not sure if it helps, but I've managed to exclude stuff from Coveralls by
using simplecov filters...
E.g.:
https://github.com/fatmcgav/puppet-glassfish/commit/5f7d40c2257f469a297edd04a7dbac068306b82b
Gav
On Friday, 7 February 2014 02:51:26 UTC, Garrett Honeycutt wrote:
On
Thanks James. --help should have been blindingly obvious but it slipped my
flu infested mind. Cheers!
--
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
On 7 February 2014 02:51, gh g...@garretthoneycutt.com wrote:
On 1/26/14 7:50 AM, Gareth Rushgrove wrote:
For anyone else who likes writing tests for their puppet manifests,
I've just added basic code coverage to rspec-puppet:
A blog post here about how to use it:
Our plan for eyaml is that operations owns and protects the private key.
So developers only have access to the public key and after creating new
encrypted values cannot decrypt them. Unless I'm missing something,
developers won't be able to use 'eyaml edit' because it requires the
private
On 07 Feb 2014, at 11:54, Gareth Rushgrove gar...@morethanseven.net wrote:
On 7 February 2014 02:51, gh g...@garretthoneycutt.com wrote:
On 1/26/14 7:50 AM, Gareth Rushgrove wrote:
For anyone else who likes writing tests for their puppet manifests,
I've just added basic code coverage to
Hi,
I need to use an exec resource to execute a shell script, and I'd like to
keep the script on the puppet master.
Is there a way to make the exec resource execute the script directly from
puppet's built-in file server? It doesn't seem to accept the puppet:/// URI
type.
Otherwise I will need
Morning all
I'm trying to work out if it's possible to add auto-require logic to some
of my Glassfish module[1] types.
From what I've read about *autorequire*, the standard usage is to match to
a resource title, as used here[2].
However the challenge I'm hitting is that I don't know the title
John,
I would generally recommend Hot Standby with Streaming Replication for
PostgreSQL replication. The documentation for such is here:
http://www.postgresql.org/docs/9.3/static/high-availability.html Some
people have also had success using Sloney, although I feel this is
somewhat trickier to
Hi,
I suppose that should be possible, although the autorequire block will
be a lot more complex than those you're using right now (obviously,
since those are almost trivial - in a good way :-)
You can filter the list of all resources in the catalog for interesting
things to autorequire. This
Thnx, Felix
I'll try today
On 7 February 2014 02:40, Felix Frank felix.fr...@alumni.tu-berlin.dewrote:
Hi,
good thinking, but the CA certificate is not used when accepting SSL
connections (or it shouldn't be, as far as I'm concerned).
You can determine the certificate that is presented
On Thursday, February 6, 2014 2:17:00 PM UTC-6, Kyle Flavin wrote:
I put this up on the Puppet Ask forum as well. Hopefully the duplication
isn't a big deal, I've been struggling to come up with a good solution to
this.
I'm attempting to migrate a puppet environment from Puppet 2.6 to
Hi,
are you quite certain you moved those .pem files to the correct
location? Apparently, the agent won't pick them up.
Look at the config very carefully, and find out where the new key has
been generated. The agent should not just overwrite the key you had
imported.
HTH,
Felix
On 01/28/2014
Hello John,
Thank you for the suggestions. You were correct it was related to the
'ensure' property.
I discovered the actual cause of the problem to be fuse and symlink
weirdness present in the latest version of Proxmox cluster. It appears
that Puppet first creates a temp file and then moves
Hi Josh,
This assumes Time.new.zone returns a string encoded with the Windows-1250
code page. You are probably better off omitting the source encoding, since
ruby should already know what it is:
Time.new.zone.encode(UTF-8)
Thanks for this information!
While facter 2 isn't out,
I think custom facts would be fine for the case of JAVA_HOME of the OP.
However, feeding data to the resource will not work for the self.instances
method unfortunately.
Custom facts won't work either, as facts are only determined prior to the
catalog compilation. At that point, the installation
Felix
Thanks for the pointers there...
As discussed on #puppet-dev, I've managed to get it working with the
following code: https://gist.github.com/fatmcgav/8864343
However it does raise the question of Is this the most optimal method to
handle this scenario?
As it means iterating the
And now I see why I hadn't found --help helpful. In 2.0.0 eyaml --help
does not give a dump of options. You have to run eyaml cmd --help to see
a list of options for that command. Don't know if that's good or bad. IMO
it would be nice to see more information in top level help.
--
You
I'm really lost as to why this is failing.
file{ 'openvpn.exe':
path = 'C:/ProgramData/puppetfiles/openvpn.exe',
source = puppet:///modules/openvpn/openvpn.exe,
owner = 'SYSTEM',
group = 'Administrators',
mode = 0770,
provider = windows,
ensure = present,
}
gives me this error:
I am just setting up a new puppet server and wanted to find out what the
best practise directory structure is? Ive had a look around on different
forums and on the puppet site and what strikes me is that everyone seems to
lay it out in a different way. Isnt there a recommended way and
First question - what version of puppet?
Second question - can you run puppet apply (or agent) with --trace --debug
--verbose and post the relevant results? We have some recent fixes related
to this.
On Thu, Feb 6, 2014 at 3:27 PM, jmp242 jp10...@gmail.com wrote:
I'm really lost as to why
I'm a Unix guy, and perhaps this is a silly question but...
Does C:/ProgramData/puppetfiles/ directory exists?
Regards
El 07/02/2014 17:31, jmp242 jp10...@gmail.com escribió:
I'm really lost as to why this is failing.
file{ 'openvpn.exe':
path = 'C:/ProgramData/puppetfiles/openvpn.exe',
This is the same directory layout most of us would use if you no setup
environments.
If you want to implement roles/profiles, they are not anything else that
classes defined in modules. For instance
/etc/puppet/modules/role/manifests would have the manifest for roles
definition and
On Thursday, February 6, 2014 12:54:58 PM UTC-6, Jason Hatman wrote:
One of my clients wasn't checking in with puppet so I decided to reinstall
facter and puppet on that client. I did so and now when I try to run
puppet agent it crashes with a lot of ruby errors. This is mavericks so I
28 matches
Mail list logo
