Am 30.01.2014 08:05, schrieb Dirk Heinrichs:
Am 29.01.2014 17:27, schrieb Simon Hildrew:
Can you raise an issue on the github project
at https://github.com/sihil/hiera-eyaml-gpg with details on how you
produced the error?
Sure.
https://github.com/sihil/hiera-eyaml-gpg/issues/11
Bye...
You can change the path to authorized_keys as it is done in my ssh puppet
module (http://forge.puppetlabs.com/thbe/ssh). The next version of this
module will give you the possibility to deploy usernames with keys as
parameters but I'm not sure when I'll find time to implement this. Till now
you
Must admit i would be interested in seeing what other peoples approaches
has been for this, we have been thinking about going down the route of
getting the war files and any relevant library files put into a rpm/deb
package and getting puppet to install the rpm though the OS package manager.
Greetings,
Thanks for the response.
The pkginventory is already doing this inside of util/pkg.rb:
rpm -qa --qf %{NAME}\t%{VERSION}-%{RELEASE}
I am fully aware of how multiple kernels work. As stated, the kernel was
just an example. I need/want every package installed returned to me and the
I use puppetboard too - it's really great, and much lighter on the
database. A big improvement on puppet-dashboard.
Only one issue remains, that means I must keep my puppet-dashboard..
There's a bug in the puppetdb-terminus - so nodes which manifest fails
compilation fails - does NOT get a
Here we go:
Part 1: Custom Fact (modules/users/lib/facter/user_home.rb)
require 'etc'
Etc.passwd { |user|
Facter.add(home_#{user.name}) do
setcode do
user.dir
end
end
}
When you are creating a user, you
Hi,
I am having similar issue, cant figure out why. Can any one help me with
this ??
thanks,
Teja.
On Friday, August 10, 2012 5:29:27 AM UTC-7, Axel Bock wrote:
hm, nevermind, I somehow solved it. although I'm not (yet) sure how. It
involved a lot of restarting and deleting :)
thanks
Hi everyone,
I've booked at Sogno d’Italia for approx. 30 people. They are expecting us
somewhere between 19h00 and 19h20 (that's 7PM for the Americans).
I've changed the Eventbrite event to allow tickets up to 35 which means
there's
about 15 places left if you want to join in. So, if you want
Hi,
Thanks for the reply Richard,
I will try this and share the details!
-Kaustubh
On Wednesday, January 29, 2014 2:13:13 PM UTC-5, Richard Berwald wrote:
I recently faced the same challenge. I did not want to group by osfamily
but by another fact.
I came up with this solution:
1)
we used to package into rpms as well
On 30 January 2014 11:50, PaulC paul.can...@gmail.com wrote:
Must admit i would be interested in seeing what other peoples approaches
has been for this, we have been thinking about going down the route of
getting the war files and any relevant library
On Wednesday, January 29, 2014 2:00:28 PM UTC-6, Jon Jaroker wrote:
Hello,
Would anyone know what the error message Could not set present on ensure:
Function not implemented means. It is appearing in Puppet 2.7.13 on a
File resource type. The --debug flag does not give any hints.
On Wednesday, January 29, 2014 7:16:45 PM UTC-6, Doug_F wrote:
All,
I have a problem where I was mucking about in a Module which failed. One
of my Debian nodes I was testing it on started acting funky. Now my single
Debian node is getting some weird module activity.
Classes defined by
On Thursday, January 30, 2014 8:22:35 AM UTC-6, jcbollinger wrote:
Looking at the Facter source, however, it seems pretty likely that the
problem revolves around the file /etc/debian_version having been removed
from the node.
Hmm. Having re-read the problem description, I am less
Hi,
Awesome, thanks Daniele! I have just registered for the dinner, though
I'm still not 100% sure I'll be there (there's an air controller strike,
argh!).
But I'll be lurking around, like (almost) every year :-)
For a photo : https://github.com/thias
I'll be mostly interested in discussing
Hi all,
I have an install routine that should never be executed by puppet
automatically.
But I would like to execute it sometimes by running something like this:
puppet agent -t --ignoreschedules --tags never
One idea is to create a schedule
class never{
schedule { 'never':
repeat = 0,
}
Hi,
I think the explaination of Gareth is wrong.
absend will uninstall a package
I am using absend to uninstall package and here is a web site about that.
http://www.puppetcookbook.com/posts/remove-package.html
Best regards
Andreas
--
You received this message because you are subscribed to
On 30 January 2014 15:41, Andreas Dvorak andreas.dvo...@gmail.com wrote:
Hi,
I think the explaination of Gareth is wrong.
No, he's exactly right. And please be careful with your spelling...it's
'absent', not 'absend'. Your puppet manifests are not scripts/sets of
instructions. They
Hi,
I am trying to install Apache with a default set of config files. I have
the following class:
class base_apache {
case $operatingsystem {
windows: {
file { 'apache_installer_package':
path= 'D:/Downloads/Puppet/',
ensure
Hi,
Simple :
User[‘david’]-File[‘/haha’]
Ref: http://docs.puppetlabs.com/learning/ordering.html
Dominique Arpin
Tél. Interne: 140-4156
Tél. 514 285.2929 Poste: 140-4156
De : puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] De la
part de David Portabella
Envoyé : 30
For illustrating purposes,
I need a *david* user with home directory /haha/david,
and at the same time, the directory /haha also needs to be owned by *david*.
this code does not work,
because user requires the /haha directory, and the /haha directory requires
the david user,
so we have a
Hi,
If you want to check if a server is compliant with a defined end state,
you can set noop=true in the resources, or just run puppet in noop mode.
Regards
El 30/01/2014 16:51, Matthew Burgess matthew.2.burg...@gmail.com
escribió:
On 30 January 2014 15:41, Andreas Dvorak
again,
it is a circular dependency.
what you are saying is to first create user and then file.
but to create the user, we need the file first also.
On Thursday, January 30, 2014 5:31:10 PM UTC+1, Arpin Dominique (Nter)
wrote:
Hi,
Simple :
User[‘david’]-File[‘/haha’]
Ref:
hi, im still new to puppet, but from linux logic cant you just first ensure
file is there with (deployment)-group permissions - create user (with same
group) - change permissions
On Fri, Jan 31, 2014 at 12:51 AM, David Portabella
david.portabe...@gmail.com wrote:
again,
it is a circular
Actually, simpler than that.
Using the stdlib puppet-forge module, I can say
$homedirdir = dirname ( $userhome )
and then
exec { mkdir-${username}:
command = /bin/mkdir -p ${homedirdir},
unless = test -d ${homedirdir},
}
When the user
Something like managehome = false ?
On 30 Jan 2014 16:51, David Portabella david.portabe...@gmail.com wrote:
again,
it is a circular dependency.
what you are saying is to first create user and then file.
but to create the user, we need the file first also.
On Thursday, January 30, 2014
The puppet stand is located in the K building, on the second level.
Please feel free to 'pop by' ...
see you @ fosdem
On 01/30/2014 03:48 PM, Matthias Saou wrote:
Hi,
Awesome, thanks Daniele! I have just registered for the dinner, though
I'm still not 100% sure I'll be there (there's an
PuppetDB 1.6.0 final
* RC1: January 7th, 2014.
* RC2: January 14th, 2014.
* RC3: January 22nd, 2014.
* Final: January 30th, 2014.
PuppetDB 1.6.0 Downloads
Available in native package format in the pre-release repositories at:
http://yum.puppetlabs.com and
Puppi?
On 30 Jan 2014 13:52, Andrey Kozichev akozic...@gmail.com wrote:
we used to package into rpms as well
On 30 January 2014 11:50, PaulC paul.can...@gmail.com wrote:
Must admit i would be interested in seeing what other peoples approaches
has been for this, we have been thinking about
We package the war into a RPM and then use an exec statement to extract the war.
Matt
On Jan 30, 2014, at 3:50 AM, PaulC paul.can...@gmail.com wrote:
Must admit i would be interested in seeing what other peoples approaches has
been for this, we have been thinking about going down the route
Due to the run time issue with puppet/ruby calling powershell windows
update and i could nt be able to open the zip file
http://forge.puppetlabs.com/liamjbennett/windows_autoupdate
So I am using instead registry setting to disable the auto update, any
suggestions for the below
confine
Hi All,
The puppet and puppet user groups stand is located in the K building, on
the second floor, somewhere in the middle.
Feel free to pop by to say hello
See you @ fosdem
--
Johan De Wit
Open Source Consultant
Red Hat Certified Engineer (805008667232363)
Puppet Certified
solved thank you
On Wednesday, January 15, 2014 2:15:00 PM UTC-7, Vassiliy Vins wrote:
Hi!
I've created 2 files:
file *test.pp* with code :
class copy {
file {testfile:
path = /home/vassiliy/myfile,
source = puppet:///mpoint/client1/testfile,
mode = '644'
}
}
and file site.pp
Dear Puppet Enterprise Users,
Puppet Enterprise 3.1.2 is now available.
This is a bug fix and security release of Puppet Enterprise. All users of
Puppet Enterprise 3.x are encouraged to upgrade when possible to
Puppet Enterprise 3.1.2
Puppet Enterprise 3.1.2 includes fixes to address a
Dear Puppet Enterprise Users,
Puppet Enterprise 2.8.5 is now available.
This is a bug fix release of Puppet Enterprise. All users of
Puppet Enterprise 2.8.x are encouraged to upgrade when possible to
Puppet Enterprise 2.8.5.
Puppet Enterprise 2.8.5 includes fixes to address a regression in
Usually package into an RPM, but not always, which installs into
something like /usr/{lib|share}/package/something.war and then create
a link to it from the tomcat webapps directory. Tomcat's autodeploy
will take care of unpacking it.
--
Later,
Darin
On Thu, Jan 30, 2014 at 3:13 PM, Matthew
/etc/debian_version is in place and facter on the box returns correctly.
If I run the puppetmaster in debug I can see it checking hiera for RedHat
not Debian values as it does when another debian client contacts it.
On Thursday, January 30, 2014 7:32:41 AM UTC-7, jcbollinger wrote:
On
Greetings,
I am trying to puppetize a process that goes like this:
1) remove package a.i386
2) create repo file
3) install package a.x86_64 from repo
4) update config_file_1
5) update config_file_2
6) update config_file_3
7) start service
Shouldn't be too hard right? Except I have played with
One correction: It was brought to our attention that the announcement
referenced OpenSSL CVE-2013-6449. That was incorrect. The correct advisory
is CVE-2013-6550, for more information, see
http://puppetlabs.com/security/cve/cve-2013-6450.
On Thu, Jan 30, 2014 at 1:08 PM, Rob Braden
That issue should be fixed soon, I'm told. The reports do get sent to
puppetboard, but the report processor throws an unhandled exception
because it references one of the 'metrics' hash fields, which is empty
in failed reports (this should be fixed in master to log an error
message instead).
39 matches
Mail list logo
