Hi,
Until now I work with manifest file. Now I would like to create a perl/php
script that will create the YAML script and should overwrite the manifest
file.
So I edit the file puppet.conf and put:
mode_terminus = exec
external_nodes = /usr/bin/env
The problem is rubygem itself, which was missing. This has to be installed
from the SDK which was not available as repository on th system.
Am Freitag, 13. Juni 2014 14:47:19 UTC+2 schrieb Darin Perusich:
rubygem-ruby-shadow is available in the repo so I don't know what
could be causing
As I know puppet merge both sources ENC and manifest file. You can use
empty manifest file to avoid this behavior. Host name will be available as
first argument to this script, all others facts you can query from
puppetdb. Also you can use hiera as ENC, and all facts will be available
for you
Hi!
I try to install modules in puppet, but it gives an error message
independent of the module I try to install:
myserver:~ # puppet module install rtyler/jenkins
Notice: Preparing to install into /etc/puppet/modules ...
Notice: Downloading from https://forgeapi.puppetlabs.com ...
Error:
--
-- http://23.me.uk/2 --
--Time flies like an arrow; fruit flies like a banana. --
On 16 June 2014 08:52, shlo.af...@gmail.com wrote:
Hi,
Until now I work with manifest file. Now I would like to create a perl/php
script that will create the YAML script and should overwrite the manifest
This time we will talk about mcollective.
The first part we will flood you with some nice slides and a bit of
talking,
The second part, all will setup mcollective on its own VM, and explore
what Mcollective can do and how it works.
Detailed information can be found on our meetup page :
Running puppet 3.6.2 and disable_warnings = deprecations appears to make no
difference to prohibiting the alert about environments.
On Tuesday, June 10, 2014 1:19:05 PM UTC-5, Moses Mendoza wrote:
Puppet 3.6.2 is a security and bug fix release in the Puppet 3.6
series. This release addresses
Hi,
I am new to puppet. In my puppet master side I want to create some
configurations dynamically. For that I have to send those configuration
details along with the puppet agent request to the master. I have plenty of
configurations details to be sent with a request. Does Puppet support this
I was in the exact same situation and found a dirty solution was to simply
to use service iptables stop.
It's a bit of a dirty workaround and definitely wouldn't recommend it on an
open network but it solved the issue for me to use it on a few internal vms.
Hope it helped.
--
You received
It sounds like you want to use facts to make decisions about what
configurations to apply:
http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html
http://docs.puppetlabs.com/guides/custom_facts.html
The usual caveat here tends to be that you should be telling the
HI,
I empty the file nodes.pp, but it look like it's not running.
I make the script to print something to a file, each time it run, but it
write it only when I run it from the command line,
While I expect to have that print each time the Puppet agent run the puppet
command.
Is the hostname
Alex,
The more complete idea would be to trigger when resources have
actually been applied. So I would probably consider a report listener
for this kind of thing, as it shows when a resource has changed rather
than compiled.
I think Chris Spence has a tool for this kind of thing that uses MCO
to
When I install open source Puppet 3.3.1, I follow old instruction of 2.6.0.
I did not install the PuppetDB, unless it came by default installation. Is
it installed with open source puppet 3.3.1?
No it is not. It's a separate step. Follow the documentation:
Debian has announced a long term support for debian squeeze:
https://www.debian.org/News/2014/20140616
I'm wondering if this will mean that Squeeze will stick around at
apt.puppetlabs.com for the same period?
--
Erik Dalén
--
You received this message because you are subscribed to the Google
Hello There,
I've been struggling the last days with this issue. The situation is
happening since I've upgrade Puppet to 3.6.0.
*- Problem:*
On Puppet-Dashboard all Hosts are shown as *Unresponsive* and thousand of
tasks are queued as *Failed*.
*- Environment:*
OS: Debian Wheezy
Hi,
Is there any way in puppet dashboard to hide and unhide nodes from the
command line? I couldn't find anything in the rake API, but I don't really
understand rake that well at this point.
tom
--
You received this message because you are subscribed to the Google Groups
Puppet Users
I've got some newbie puppet questions.
My team has a tremendous amount of linux/computer knowledge, but we're new
to Puppet.
We recently started using puppet to manage some 100 servers. Their configs
are all pretty similar with some small changes.
History
Prior to Puppet, we already had
Ubuntu 14.04 comes with pre-loaded python 3 running side-by-side with the
python 2.7.
To install a package into the python 3 environment, I can simple run pip3
instead of pip.
Is there a way to make the pip package provider run pip3 instead of pip?
Cheers,
Alex
--
You received this message
there is a patch in openstack-infra that is looking to accomplish this.
They are creating different providers for pip vs. pip3 (b/c for their use
case, they have to be able to use both in the same run)
(it's buried in here somewhere)
https://review.openstack.org/#/c/51425/
On Mon, Jun 16,
Hey Marc,
Thanks for reporting this! Could you file a ticket at
https://tickets.puppetlabs.com/browse/CPR with that information? That way
we can be sure to get that package up.
Thanks!
On Sun, Jun 15, 2014 at 11:50 AM, Marc marc.villaco...@gmail.com wrote:
Hi,
Puppetizing my first Centos7
On 13/06/14 14:44, Chris Miller wrote:
How do I grant a user SELECT privileges on the pg_stat_database catalog?
Using the normal postgresql::server::database_grant approach just
returns: 'ERROR: database pg_stat_database does not exist
pg_stat_database isn't a database, it's a view inside
Hello everyone,
I'm trying out the puppet-postgresql module (v. 3.3.3) on Rhel 5 6
machines, installing Postgresql 9.3. When installing manually from the
repos, everything works as expected:
1. yum -y install postgresql93-server
2. service postgresql-9.3 initdb
3. service postgresql-9.3 start
Facter 1.7.6 is a security fix release in the Facter 1.7 series. The Facter
1.7 series was incorrectly omitted from the original security announcement
for Facter. This release addresses CVE-2014-3248. It has no other bug fixes
or new features. All users of Facter 1.7.5 and earlier are encouraged
Well, I found the problem. The initdb command was failing with this error:
runuser: cannot set groups: Operation not permitted
So, the folder was created but not the default database. When I commented
out user group, the command worked on both Rhel 5 6. Is this a bug?
exec {
Greetings,
Does PuppetDB support environments similar to puppet?
I noticed exported resources are crossing from one environment to another.
I would like to prevent this without having to add $environment to every
single tag and
forge modules don't do it anyway, so there must be a some way to
I'm not sure about your #2 and #3. I've not really experienced either of
those and I wouldn't expect they are regular for most people. It would
probably be more helpful if you could post more specifics when one of those
things happens.
As to #1, it maybe depends on how you administer your
Steve,
I think you said you put all your configuration in a single site.pp. This
is often bad form and limits the flexibility of your deployment. Something
we do is layout modules.
The common pattern is:
/etc/puppet/environments/production
- Manifests/site.pp
- Hieradata/*.yaml
- Modules/foo
Hi Everyone
We want to unit test our servers with something like serverspec, but we do
not have the coding skills in the team to write ruby/rspec, and we want a
low barrier to entry for writing tests
Our site isn't small with 3.5K servers, 200 modules, 400 manifests covering
3K resources. Each
28 matches
Mail list logo
