Am 23.03.2014 09:57, schrieb Stefan Schulte:
That's what I'd do, too. But you can use `creates` paramter to do the
check, there is no need to invoke an external command.
exec { 'create_mntpoint_/mnt/foo':
command = '/bin/mkdir -m 0755 /mnt/foo',
creates = '/mnt/foo',
}
Hello all,
Was hoping for some guidance around integrating AWS with our current puppet
environment. Is it as simple as setting the puppet.conf on AWS instances to
point to our current puppet master and opening up the firewall on those
ports, is anyone doing this ? current puppet master is not
Hi Stefan
you're solution is what I did before I posted to the list, but I feel it's
too much of a hack and think that there are cleaner and better ways to do
it.
On Sun, Mar 23, 2014 at 9:57 AM, Stefan Schulte
stefan.schu...@taunusstein.net wrote:
On 21.03.2014 19:53, José Luis Ledesma
Peter
I like your approach very much and think I'll implemente it :-)
TIA
Paolo
On Fri, Mar 21, 2014 at 6:48 PM, Peter Bukowinski pmb...@gmail.com wrote:
It may not be the nicest way to handle it, but it's not all that
cumbersome. If your mount command is modifying the permissions,
Am 21.03.2014 18:48, schrieb Peter Bukowinski:
exec { 'fix_mount_perms':
command = 'chmod 2755 /app_dir chown root:root /app_dir',
refreshonly = true,
}
Setting the exec's refreshonly parameter to true prevents it from
running every time, but it will run any time the mount resource
Hi,
On 03/24/2014 07:53 AM, Dirk Heinrichs wrote:
But that's not the OP's problem. Creating the mount point can be
perfectly accomplished with a file resource. The problem is to adjust
permissions AFTER mounting something there w/o having to wait for the
next agent run.
the point of using
That's what the notify parameter in the mount resource does.
-- Peter
On Mar 24, 2014, at 5:38 AM, Dirk Heinrichs d...@recommind.com wrote:
Am 21.03.2014 18:48, schrieb Peter Bukowinski:
exec { 'fix_mount_perms':
command = 'chmod 2755 /app_dir chown root:root /app_dir',
refreshonly
Am 24.03.2014 12:10, schrieb Peter Bukowinski:
That's what the notify parameter in the mount resource does.
Yes, you're right. I always use subscribe instead of notify and didn't
even recognize you use the latter ;)
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering
It is as simple as the firewall setting you mention.
Regards,
Stefan Zipkid Goethals.
On Mon, Mar 24, 2014 at 8:03 AM, kdo k...@hampels.com.au wrote:
Hello all,
Was hoping for some guidance around integrating AWS with our current
puppet environment. Is it as simple as setting the
Thanks a ton garrett.
I need to only run puppet client on hp-ux.
On Mon, Mar 24, 2014 at 2:15 AM, Garrett Honeycutt
g...@garretthoneycutt.comwrote:
On 3/22/14, 5:33 PM, Rakesh Kathpal wrote:
Hi,
I have been successfully able to install puppet on hu-ux, all I am
looking is to run
A puppet init script would essentially be:
case $1 in
start)
echo Starting puppet agent
puppet agent --verbose
;;
stop)
echo Stopping puppet agent
kill `cat /var/run/puppet/agent.pid`
;;
esac
To make it work on HP-UX, copy the init script into /sbin/init.d, then
create sym-links in
looks great.. !!!
Thanks a lot Ryan..
On Mon, Mar 24, 2014 at 6:40 PM, Ryan Anderson ryan.c.ander...@gmail.comwrote:
A puppet init script would essentially be:
case $1 in
start)
echo Starting puppet agent
puppet agent --verbose
;;
stop)
echo Stopping puppet agent
kill `cat
Hi folks,
Has anyone done any work managing the Windows local computer certificate
store with puppet?
Specifically, I want to check if a certificate is installed, if it is I
want to check the thumbprint, private key and validity, and
install/re-install it if required.
I have done a fair bit
Hi All.
How I post more parameters to define, for example key type and fqdn in
this sample?
$keys = [[ key1, key2 ]
pubkey { $keys: user = $login }
define pubkey($user) {
ssh_authorized_key { ${user}@fqdn-${name}:
ensure = present,
key= $name,
user =
Hi all,
I just noticed that some of my servers are having trouble while running
`apt-get update`, apparently due to TLS issues with apt.puppetlabs.com.
`apt-get update` returns:
W: Failed to fetch
https://apt.puppetlabs.com/dists/lucid/main/source/Sources.gz server
certificate verification
On Friday, March 21, 2014 2:09:12 AM UTC-5, Sebor wrote:
Hi!
I have the entry in my site.pp:
user { 'testuser':
name = 'testuser',
ensure = 'present',
home = '/export/home/testuser',
password = '$5$3dA8tfNG$XIKm1FRM3limH12jzdSVjQAcCWzxj64H6BI/n66',
roles = 'root',
managehome = true,
}
On Mar 24, 2014, at 2:46 AM, A. Gorlov gorlo...@gmail.com wrote:
Hi All.
How I post more parameters to define, for example key type and fqdn in
this sample?
$keys = [[ key1, key2 ]
pubkey { $keys: user = $login }
define pubkey($user) {
ssh_authorized_key {
Life saver! For us it pointed out we needed -y flags on the commands being
executed.
Thank you :)
On Wednesday, January 15, 2014 1:39:54 PM UTC, Ken Barber wrote:
This is my exec:
exec {'make nodejs':
command = /usr/bin/make,
creates =
On Sun, Mar 23, 2014 at 12:46 PM, krish das.srikris...@gmail.com wrote:
Just a hunch Windows 2008 R2 is 64 bit...
http://docs.puppetlabs.com/windows/running.html#file-system-redirection-in-64-bit-windows-versions
and another small check... wondering if puppet run is invoking a
On Sun, Mar 23, 2014 at 8:43 PM, Stuart Whelan
stu...@somepointinthefuture.co.nz wrote:
Hi folks,
Has anyone done any work managing the Windows local computer certificate
store with puppet?
Specifically, I want to check if a certificate is installed, if it is I
want to check the
This is done already.
question about changes in
$keys = [ key1, key2 ]
pubkey { $keys: user = $login }
to post some other values to define
понедельник, 24 марта 2014 г., 18:54:15 UTC+4 пользователь Peter Bukowinski
написал:
On Mar 24, 2014, at 2:46 AM, A. Gorlov gorl...@gmail.com
Hi All,
Was wondering if anyone knew of any good books or resources for learning
Test Driven Development of Puppet including puppet-rspec, beaker and
Jenkins. Yes, I know that beaker is more for acceptance testing than unit
testing, but I still see it as part of the testing tool chain that
Thanks for pointing this out, I've raised an internal ticket with the
operations team and will update this thread when I hear back.
--eric0
On Monday, March 24, 2014 7:10:09 AM UTC-7, Christopher Orr wrote:
Hi all,
I just noticed that some of my servers are having trouble while running
Normally, I'd say create_resources(), but that needs a hash of hashes, not
a hash of arrays. Might I ask what the numbers represent, if they aren't
present in the define?
On Sunday, March 23, 2014 10:10:24 PM UTC-7, backg...@gmail.com wrote:
Given this hash of arrays:
$players = {
'joe'
We are periodically seeing the error
*Could not retrieve catalog from remote server: Error 400 on SERVER: Could
not find class webadminserver*
In our puppet agent logs even though the module/webadminserver files are
there.
But I'm wondering if there is a timing/file refresh issue involved.
Today looking for a solution to this I came up with a nice solution. I know
this is old but I'm posting it just in case is useful for somebody:
on hiera.yaml:
:hierarchy:
- 'host/%{::domain}/%{::hostname}'
- 'domain/%{::domain}'
- 'role/%{system_role}'
- 'common'
on site.pp
node
Today looking for a solution to this I came up with a nice solution. I know
this thread is old but I'm posting it just in case is useful for somebody:
on hiera.yaml:
:hierarchy:
- 'host/%{::domain}/%{::hostname}'
- 'domain/%{::domain}'
- 'role/%{system_role}'
- 'common'
on site.pp
I think this is fixed now; I used openssl s_client and whereas it used to
have:
---
Certificate chain
0
s:/serialNumber=tQHCVE0ajtkIENLLN1O5pr4WMtvwn/eA/C=US/ST=Oregon/L=Portland/O=Puppet
Labs, Inc./CN=*.puppetlabs.com
i:/C=US/O=GeoTrust, Inc./CN=GeoTrust SSL CA
1
This seems overly complicated. If you use an ENC then you can put arbitrary
facts into the data returned by the ENC as parameters. Since the ENC is
processed before Hiera you can set your hierarchy based on those parameters
and you can put anything else you want in there too.
My ENC is similar to
at the very least, I'd alter the process you use to copy the new modules
dir into something like $puppetconfigdir/modules_MMDDYYSTUFF and then doing
2 mv's:
mv modulepathdir modulepathdir.old
mv modules_MMDDYYSTUFF modulepathdir
and then puppet should be good, you can start the rm -rf on module
I did try to use the path C:\Windows\sysnative but Puppet complains the
path does not exist. I'll give the poweshell module a go and see what is
the outcome.
On Tuesday, March 25, 2014 12:15:09 AM UTC+8, Josh Cooper wrote:
On Sun, Mar 23, 2014 at 12:46 PM, krish
i was getting failure messages when doing a puppet run and found that by
downgrading my puppet client by several versions ( from 2.7.25 to 2.7.13)
fixed the issue. master is on 2.7.25. now have user management working in
AWS from our existing puppet master. thanks for getting back to me
On
32 matches
Mail list logo
