It was a busy week last week, but we're back to our monthly release candidates
for our projects.
This is an enhancement/fix release candidate of Puppet. A major focus on this
release was Windows support. Puppet now works on Windows as agent. Another focus
was on the RAL around using it with toolin
This was a module out of the puppetmaster printed book. I've found a few
other typos as well...perhaps I should disregard it if it's not accurate.
On Mon, Oct 3, 2011 at 7:27 PM, Todd Zullinger wrote:
> Sam Roza wrote:
> > I think that the issue is due to my puppet installation (from EPEL)
> > n
Sam Roza wrote:
> I think that the issue is due to my puppet installation (from EPEL)
> not configuring the init.d script properly.
It's configured fine as it is. :)
> puppetmasterd doesn't think it is a service.
You want to use service { 'puppetmaster': ... } in your manifests.
--
Todd
If it helps, I've put together a ppa repository for personal use
(https://launchpad.net/~vladgh/+archive/stable).
It's based mostly on the official packaging with some minor changes for the
updated source to work. It's tested on Ubuntu Natty
You can use the debian folders as you wish as a startin
This is a maintenance release candidate of Puppet Dashboard 1.2.2rc1.
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages as well as a tarball.
Release candidate packages will not placed on yum.puppetlabs.com.
See the V
>
> about. In fact, I think if you were to use periods it would confuse
> DNS resolve because it follows the same convention as stated in the
> RFC. If I were external trying to look up host.server.domain.com, my
> DNS would try to look for a nameserver for server.domain.com. You
> would still be f
Now that sounds cool.
On Mon, Oct 3, 2011 at 3:42 PM, R.I.Pienaar wrote:
>
>
> it would be pretty trivial to create an encrypted hiera backend that
> can only be decrypted by machines that have a key stored on their disks.
>
> You'd check into SCM the encrypted file and on your masters store the
This is stored inside of the compiled catalog.
Catalogs are saved on the client where they are applied
the default location is:
/var/lib/puppet/client_yaml/catalog/CERTNAME.yaml
On Mon, Oct 3, 2011 at 3:44 PM, Bruno Leon wrote:
> Hi,
>
> is there a way to get the value of a parameter passed t
In both cases for hiera and trocla doesn't the password end up in the
catalog and don't other things like the dashboard consume the catalog?
Does that mean the passwords are available in dashboard?
Is there a way to cause the client to pull down the password without
including it in the catalog?
Hi,
is there a way to get the value of a parameter passed to a parameterized
class ?
I've searched quite a lot and did not came out with a solution.
Thanks
--
Bruno
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send
- Original Message -
> Sure, but that doesn't really address the issue (at least not
> out-of-box). Hiera puts your data outside your manifests, but at
> least in our case it's still in revision control. Are you putting
> your Hiera data elsewhere? If so, how do you control access to it?
Sure, but that doesn't really address the issue (at least not out-of-box).
Hiera puts your data outside your manifests, but at least in our case it's
still in revision control. Are you putting your Hiera data elsewhere? If
so, how do you control access to it?
This came up recently for us as wel
Have a look at hiera.
--
Bruno
On 11-10-03 06:02 PM, Alan Evans wrote:
Puppet Uesrs,
How do you deal with sensitive data in your puppet config that does
not belong in revision control? Think about things like SSL keys or
passwords.
i.e.
/etc/ldap.conf
...
binddn cn=foo,dc=example,dc=com
bin
Puppet Uesrs,
How do you deal with sensitive data in your puppet config that does
not belong in revision control? Think about things like SSL keys or
passwords.
i.e.
/etc/ldap.conf
...
binddn cn=foo,dc=example,dc=com
bindpw mysocratesnote
...
As of now we store the bindpw as a variable then re
The actual issue is that in version 2.6.9, the service is installed as
"puppetmaster" in init.d instead of "puppetmasterd".
Easy fix, once I had my head in the right place.
Thanks again.
On Mon, Oct 3, 2011 at 12:23 PM, Sam Roza wrote:
> I think that the issue is due to my puppet installation
I think that the issue is due to my puppet installation (from EPEL) not
configuring the init.d script properly. puppetmasterd doesn't think it is a
service.
Thanks for pointing me in the right direction.
On Mon, Oct 3, 2011 at 10:27 AM, Craig White wrote:
>
> On Oct 3, 2011, at 6:50 AM, Sam wro
After a very busy week on the security front last week, we are back to
monthly release/RC cycles.
Facter 1.6.2rc1 is a maintenance release containing fixes, updates and
refactoring.
This release is available for download at:
http://puppetlabs.com/downloads/facter/facter-1.6.2rc1.tar.gz
See the
On Oct 3, 2011, at 7:39 AM, Evan Stachowiak wrote:
> Hi,
>
> I'm attempting to distribute a known host ssh key (for github) to an
> Ubuntu 10.04 host. Puppet is distributing the key into /etc/ssh/
> ssh_known_hosts as:
>
> github.com ssh-rsa [really long ssh-rsa key]
>
> However, Ubuntu seems
On Oct 3, 2011, at 6:50 AM, Sam wrote:
> I have a puppetmaster module. In it is an 'ensure => running'
> declaration. Runs of puppetd fail on this with the following error:
>
> err: /Stage[main]/Puppet::Master/Service[puppetmasterd]/ensure: change
> from stopped to running failed: Could not star
I have a puppetmaster module. In it is an 'ensure => running'
declaration. Runs of puppetd fail on this with the following error:
err: /Stage[main]/Puppet::Master/Service[puppetmasterd]/ensure: change
from stopped to running failed: Could not start
Service[puppetmasterd]: Execution of '/sbin/servi
Hi all,
I'm currently redoing our puppet setup and trying to start with new design
from the ground up to implement all of the puppet 2.6+ goodness, but I'm
getting tripped up with the complexity of the design. I want to do things
the right way, but I don't want to introduce additional complexit
Hi,
I'm attempting to distribute a known host ssh key (for github) to an
Ubuntu 10.04 host. Puppet is distributing the key into /etc/ssh/
ssh_known_hosts as:
github.com ssh-rsa [really long ssh-rsa key]
However, Ubuntu seems to expect the key in this format:
|1|[really long ssh-rsa key]
(note
Hi all,
I use a number of exported resources, some of which are exported custom
definitions.Since
upgrading to 2.7.5, I've seen an issue which is driving me up the wall
trying to debug it. Hopefully
someone can help :)
Consider the following three snippets of code:
*$modulepath/ntp/manifests/n
On 03/10/11 14:24, Todd Zullinger wrote:
Stefan Schulte wrote:
I guess facter as a standalone executable doesn't look into
/var/lib/puppet. Try running
FACTERLIB=/var/lib/puppet/lib/facter facter
as described in the custom facts guide [1]
[1] http://docs.puppetlabs.com/guides/custom_fact
Stefan Schulte wrote:
> I guess facter as a standalone executable doesn't look into
> /var/lib/puppet. Try running
>
> FACTERLIB=/var/lib/puppet/lib/facter facter
>
> as described in the custom facts guide [1]
>
> [1] http://docs.puppetlabs.com/guides/custom_facts.html#an-example
Or use the -p
On Mon, Oct 03, 2011 at 05:52:51AM -0700, John Bower wrote:
> Hello,
>
> I installed the latest puppet through Gems, installation went well, I
> created the certs and puppet agent --test works well. I was able to
> create a resource user on the puppet server.
>
> However I am unable to run a simp
Hello,
I installed the latest puppet through Gems, installation went well, I
created the certs and puppet agent --test works well. I was able to
create a resource user on the puppet server.
However I am unable to run a simple "puppet user" command, here is
what happens on the client
I looked aro
On Mon, Oct 03, 2011 at 12:08:23PM +0100, Jonathan Gazeley wrote:
> On 03/10/11 11:14, Stefan Schulte wrote:
> > On Mon, Oct 03, 2011 at 11:00:18AM +0100, Jonathan Gazeley wrote:
> >> Hi all,
> >>
> >> I'm experiencing some difficulty getting custom facts to run. I've
> >> installed them on the pup
On 03/10/11 11:14, Stefan Schulte wrote:
On Mon, Oct 03, 2011 at 11:00:18AM +0100, Jonathan Gazeley wrote:
Hi all,
I'm experiencing some difficulty getting custom facts to run. I've
installed them on the puppetmaster in:
${modulepath}/${module}/lib/facter/*.rb
and from there they appear to be
On Mon, Oct 03, 2011 at 11:00:18AM +0100, Jonathan Gazeley wrote:
> Hi all,
>
> I'm experiencing some difficulty getting custom facts to run. I've
> installed them on the puppetmaster in:
>
> ${modulepath}/${module}/lib/facter/*.rb
>
> and from there they appear to be copied properly onto the c
Hi all,
I'm experiencing some difficulty getting custom facts to run. I've
installed them on the puppetmaster in:
${modulepath}/${module}/lib/facter/*.rb
and from there they appear to be copied properly onto the clients, where
they end up in:
/var/lib/puppet/lib/facter/*.rb
On all clients
On Mon, Oct 03, 2011 at 01:31:48AM -0700, Galed Friedmann wrote:
> Hey,
> I've stumbled across a weird thing, wanted to know if it is intentional or
> maybe a bug..
>
> When using the 'noop' metaparemeter inside a manifest, for example:
>
> file{ "/tmp/test":
>
> ensure => file,
>
> noop => tr
Hey,
I've stumbled across a weird thing, wanted to know if it is intentional or
maybe a bug..
When using the 'noop' metaparemeter inside a manifest, for example:
file{ "/tmp/test":
ensure => file,
noop => true,
}
Running this in a normal puppet run will run this in noop like it should.
When
33 matches
Mail list logo
