Yes, the file is only on the master (and not exactly maintained by the
Puppet but the provisioning framework) and it looks something like this:
Slackware, Linux, i-num=1
Jaguar, MacX, i-num=6
Chicago, this_Win, i-num=2
Daytona, an_other_Win, i-num=7
RedHat, Linux, i-num=5
Lion, MacY,
Hello everyone,
It's been way to long since the release but I finally had some time to sort
a few things out and release updates to both pypuppetdb and Puppetboard.
For those of you who have no idea what this is about:
* pypuppetdb is a library to work with the PuppetDB API in Python;
*
Ok, so I finally opted for inserting a full node from one DB into
another, since getting the resources should be quite easy with a GET.
But then I run into a problem when running the replace catalog command
(with an empty catalog):
curl -vv -G -H Accept: application/json
If I try to add a fictitious resource:
{\type\: \Service\,
\title\: \iptables\,
\exported\: false,
\file\: \/etc/puppet/modules/puppetdb/manifests/server.pp\,
\line\: 121,
\tags\: [\node\, \puppetdb\],
\parameters\: {
\ensure\ : \running\}
}
I get:
2013-10-15
Just my 2 cents... is better if you use stdlib - concat function for
/etc/hosts... you can have a default section for all the hosts and a
customized one for specific cases. You avoid conflicts as well.
Cheers
On Monday, October 14, 2013 4:28:39 PM UTC+1, mike wrote:
Hello,
I fix the problem
Ticket updated :)
--
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to
Hehe, sorry for the auto-reply... but I made it work, and I wanted to
post it for reference.
The key was to add also the edges: it can't be an empty list.
For the record, doing:
# curl -vv -G -H Accept: application/json
'http://localhost:8080/v2/commands' --data-urlencode 'payload={
command:
Put in $your_module_name/lib/puppet/parser/functions/am_running_oss.rb
module Puppet::Parser::Functions
newfunction(:am_running_oss, :type = :rvalue ) do |args|
#inFile = /tmp/OSs.txt
inFile = args[0]
gos = {}
if File.exist?(inFile)
open(inFile,
- Original Message -
From: jcbollinger john.bollin...@stjude.org
To: puppet-users@googlegroups.com
Sent: Tuesday, October 15, 2013 2:08:10 PM
Subject: Re: [Puppet Users] Re: Status of Data in modules
On Tuesday, October 15, 2013 12:52:39 AM UTC-5, David Schmitt wrote:
On
I created an issue. Never done one before so I may have balls it up a bit.
I added you as a watcher
Wasn't sure how to even properly begin with a pull request. I've barely
used Git so the proper process of pulling and merging is out of my skill
set right now.
On Wednesday, October 9,
Noticed that a matching issue was opened a few days ago, so I marked the
one I opened as duplicate and just added a comment on the open issue
instead.
On Tuesday, October 15, 2013 9:11:42 AM UTC-6, Jason Harmon wrote:
I created an issue. Never done one before so I may have balls it up a
I had a working puppet server and added the Dashboard. Then I got the
inventory part of dashboard working.
Now I've got what looks like one last error I can't get past:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find terminus mabospuppet01 for
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find terminus puppetsvr for indirection catalog
I had a working puppet install (new) with 2 agents working well. I added
puppet dashboard and the inventory part which is also working well.
However, clients
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Error 400 on SERVER: Could not retrieve facts for mabosthoule-m2:
Could not find terminus puppetsvr for indirection facts
error changed from catalog to facts..
--
You received this message because you are
Hello puppet-users,
We're pleased to announce that Puppet Enterprise 3.1 is immediately available
for download: http://puppetlabs.com/misc/pe-files/
This latest release introduces the Puppet Enterprise event inspector, a new
reporting tool that identifies what changed, where and how in your
On Tue, Oct 15, 2013 at 6:51 AM, Pablo Fernandez pablo.fernan...@cscs.chwrote:
Hehe, sorry for the auto-reply... but I made it work, and I wanted to
post it for reference.
The key was to add also the edges: it can't be an empty list.
For the record, doing:
# curl -vv -G -H Accept:
Hi all!
I'm trying to setup a puppet module for sudo that will write multiple files
with separate data for each file, all dependent on the hiera hierarchy.
Here's the relevant portion of my hiera.yaml:
:hierarchy:
- datacenter/app/role/node/%{::clientcert}
-
To get the agent, you need to install mcollective-service-agent as well,
not just mcollective-service-common. Don't forget to restart the
mcollective daemon after installing.
On Thursday, October 10, 2013 2:34:07 AM UTC-7, Vincent Nawrocki wrote:
Hi all !
I'm working on mcollective for a
Just upgraded, looks awesome!
On Tuesday, October 15, 2013 12:07:19 AM UTC-7, Daniele Sluijters wrote:
Hello everyone,
It's been way to long since the release but I finally had some time to
sort a few things out and release updates to both pypuppetdb and
Puppetboard.
For those of you
On Thu, Oct 10, 2013 at 6:12 AM, Pablo Fernandez pablo.fernan...@cscs.chwrote:
Thanks Ken,
I took a look at the Command API and seems to be quite interesting, but
it triggers a few more questions.
As a reminder (also for others), what I wanted to do was to add exported
resources from
Thanks for the reference, John.
We need to ensure that these remote mounts are owned/grouped by specific
UID/GID -- hence why I had ownership involved there. We could do this via
UID/GID only (not name) if that works better? I don't understand how
apply that ownership to /home/201301 would
Hi All,
I've been working on yet another Puppet module to deploy and manage Splunk.
Yep, I know that there are already many out there, but none do what I need
and also work the way we work and also have control of the various conf
files built in.
It's still a work in progress and isn't fully
I personally couldn't get hiera to work with nested directories in the
hiera.yaml.
In my case the hierarchy would look like:
:hierarchy:
- defaults
- %{::clientcert}
- %{::server_role}
- %{::app_name}
- %{::datacenter}
- global
You might try it flattened like that and see
I couldn't get hiera integrated with PE 3.0.1 to work with nested
hierarchies, so this is what my hierarchy looks like:
:hierarchy:
- defaults
- %{clientcert}
- %{domain}
- %{osfamily}
- %{environment}
- global
Regards,
Alex
On Tuesday, March 19, 2013 2:30:16 PM UTC-7, Larry Fast
Thanks for the reply, Alex! I'm using puppet-3.3 and the nested directory
works fine...at least for more simple modules, heh!
David
On Tuesday, October 15, 2013 2:47:34 PM UTC-7, Alex Scoble wrote:
I personally couldn't get hiera to work with nested directories in the
hiera.yaml.
In my
Yeah, I'll have to try again after upgrading to PE 3.1 which was just
released.
Thanks,
Alex
On Tuesday, October 15, 2013 3:43:00 PM UTC-7, David Patterson wrote:
Thanks for the reply, Alex! I'm using puppet-3.3 and the nested directory
works fine...at least for more simple modules, heh!
On Tuesday, October 15, 2013 8:08:10 AM UTC-5, jcbollinger wrote:
I'm not saying that categorically getting rid of ::params classes is a
viable target. In fact, I don't really understand why it was ever an
objective in the first place. On the other hand, I don't see why it makes
Dumb question...have you tried loading the data into a hiera array since
that's apparently what it's looking for?
Another dumb question...what's the pipe (|) for in your yaml data?
Unfortunately, the hiera documentation on the Puppet site is a bit thin and
I don't see that in the examples.
On Friday, October 11, 2013 7:12:32 PM UTC-5, Chuck wrote:
What would be nice but not necessary:
1) defined variable automatically have classname added to avoid global
conflicts.
eg.
Module: apache
variable: port
becomes global hiera: apache::port
+1
Defining a variable in
Yes to the array. I get this error when I try:
# Error: Could not run: Hiera type mismatch: expected Array and got Hash
As for the pipe, it preserves newlines:
http://en.wikipedia.org/wiki/YAML#Newlines_preserved
On Tuesday, October 15, 2013 7:38:50 PM UTC-7, Alex Scoble wrote:
Dumb
Great thanks...still learning.
On Tue, Oct 15, 2013 at 7:53 PM, David Patterson
pattersondav...@gmail.comwrote:
Yes to the array. I get this error when I try:
# Error: Could not run: Hiera type mismatch: expected Array and got Hash
As for the pipe, it preserves newlines:
I have about 75 nodes now and recently added 6 of them. They are all
running Debian squeeze and all have exactly the same Puppet packages. One
is giving an error when I try to enroll it:
Failed to import facts: PG::UndefinedColumn: ERROR: column environment
of relation hosts does not exist
32 matches
Mail list logo
