Hey,
We just got hit with the same problem on Debian Squeeze:
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8.13) (6b18-1.8.13-0+squeeze2)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
--
Daniele Sluijters
--
You received this message because you are sub
uns, so we tried stuff like 'require
puppet/util' or 'require puppet/util/plugin' but eventually we always end
up with a error similar to:
> uninitialized constant Puppet (NameError)
It would seem that Puppet code loads a lot of stuff itself instead of
letting Ruby hand
ustom type
to a branch/environment for testing.
--
Daniele Sluijters
On Wednesday, 15 August 2012 19:06:03 UTC+2, Douglas wrote:
>
> My issue may be related to this bug:
>
> http://projects.puppetlabs.com/issues/13858
>
> "Custom types in environments require loading i
mething like a hiera_all that would return a hash with
the node name as key and value the m_interface stanza for that node.
At this point I'm not even sure this can be done so, anyone got any bright
ideas?
Kind regards,
--
Daniele Sluijters
--
You received this message because you are
t you update that ticket.
--
Daniele Sluijters
On Wednesday, 15 August 2012 07:17:38 UTC+2, Sam Morrison wrote:
>
> Hi,
>
> I'm trying to install dashboard on precise and I get the below error.
> I'm using the latest version that is available in the puppet apt
>
h I'm
guessing one would have to tell Puppet its libdir now looks like
/var/lib/puppet/master/lib/<%= environment %> for it to work.
On Thursday, 16 August 2012 16:37:10 UTC+2, jcbollinger wrote:
>
>
>
> On Thursday, August 16, 2012 3:26:23 AM UTC-5, Daniele Sluijters
own YAML
file, that's an interesting solution and one I'll definitely be looking
into to.
--
Daniele Sluijters
On Thursday, 16 August 2012 10:37:23 UTC+2, Daniele Sluijters wrote:
>
> Hello,
>
> We've been using Hiera for a while and one of the things I'd li
and DNS files from them without going through Puppet but
that defeats the purpose. Plus one'd have to remember to run that code
before committing.
--
Daniele Sluijters
On Thursday, 16 August 2012 23:08:26 UTC+2, Alexander Swen wrote:
>
>
>> I hadn't thought of just separ
sts with an exitcode of:
9:35:14 r...@chell.portal.daenney.net ~ echo $?
1 ↵
1
So, unless you can run that command as the actual user that owns the brew
installation this just won't work.
--
Daniele Sluijters
On
Hi,
Are you sure there's no rack 1.3.5 somewhere around your system? If there
is it is probably found in the $RUBYLIBDIR path before the one installed
from gem so you're still seeing the error.
If not, then it's getting interesting...
--
Daniele Sluijters
On Wednesday, 15 Au
low me to explicitly pass in environment variables that I
really need set in that case but the docs don't seem to know anything about
that.
Kind regards,
--
Daniele Sluijters
--
You received this message because you are subscribed to the Google Groups
"Puppet Users"
Hi,
Sorry, I got confused between two things. It's not the actual Exec type.
it's when a provider executes a command that the environment cannot be set.
--
Daniele Sluijters
On Wednesday, 3 October 2012 15:00:54 UTC+2, Stephen Gran wrote:
>
> Hi,
>
> On Wed, 201
n nginx in front and you can just tell f5 where to find your
unicorn(s).
You will, in both cases, need something like God, supervisord or something
else to check and restart the Puppet Master in case it stops/crashes.
--
Daniele Sluijters
On Wednesday, 28 November 2012 20:21:35 UTC+1, DJames wro
:
keyring.gpg 09-Jan-2013 14:51 2.5K
However, I've yet to see an announcement about this. So, was this actually
done by Puppet Labs or is something else going on?
Kind regards,
--
Daniele Sluijters
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&
correctly and everything started working again.
How the issue occurred in the first place still remains a bit of a mystery.
--
Daniele Sluijters
On Thursday, 10 January 2013 09:02:14 UTC+1, Daniele Sluijters wrote:
>
> Hi,
>
> I just started getting errors from APT: W: GPG er
doc` just needs to get fixed (which could then use YARD once a Handler and
Parser have been written).
--
Daniele Sluijters
On Thursday, 11 April 2013 10:56:16 UTC+2, Sven Sporer wrote:
>
> I know that Puppet 3.1 uses YARD to document the Ruby code (not
> manifests). The question is if t
ntents of the rules key. Since we know it's an
array you can loop over it
acl <%= rule['aclname'] =%> <%= rule['acltype'] =%> <%= rule['arg'] =%>
<% end %>
<% end %>
This probably won't work out of the box like this but it
ravis so we can run
integration tests. Hunter, thank you for being so interested in this
project and pushing me to release it.
—
Daniele Sluijters
Nedap | Steppingstone
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe
ailed runs through Nagios, we actually use a
plugin that checks the report age and its content on every node.
--
Daniele Sluijters
On Wednesday, 7 August 2013 15:32:48 UTC+2, Klavs Klavsen wrote:
>
> It seems very cool. Thank you for sharing.
>
> One thing that I would be missing, before be
Hey,
That's awesome, let me know how it goes. I'm not sure how well it will be
able to handle itself at the scale of your infrastructure but only one way
to find out!
--
Daniele Sluijters
On Thursday, 8 August 2013 01:47:07 UTC+2, Erik Dalén wrote:
>
> Cool stuff will try it
Hey,
Great work! I really like the addition of puppetdb-anonymize, that's going
to help me out in a few situations.
--
Daniele Sluijters
On Friday, 9 August 2013 01:59:25 UTC+2, Ken Barber wrote:
>
> PuppetDB 1.4.0 is now available for download! This is a new feature
> release
Hey,
Good catch, I'll get that fixed asap.
--
Daniele Sluijters
On Tuesday, 13 August 2013 22:36:35 UTC+2, Ellison Marks wrote:
>
> Er, excuse me, I misspoke. As it is it relies on having python 2.7+, not 3
> for the formatting. Still, the Redhat family, by default, is still
Oh goody this looks awesome.
--
Daniele Sluijters
On Tuesday, 1 October 2013 01:56:49 UTC+2, Chris Price wrote:
>
> PuppetDB 1.5.0 is now available for download! This is a new feature
> release that contains a few bug-fixes as well.
>
> =
It's not just the Precise packages that are missing. The complete Debian
suite is missing too, squeeze, wheezy, jessy and sid.
On Tuesday, 1 October 2013 04:59:16 UTC+2, blkperl wrote:
>
> No packages for precise/raring? Its missing debs for 1.5.0. Lucid seems
> fine
>
> Thanks,
> William
>
>
>
n November, I'm hoping I'll be able to show you at least some of that.
As usual you can get the code from:
* pypuppetdb: https://github.com/nedap/pypuppetdb or `pip install
pypuppetdb`
* puppetboard: https://github.com/nedap/puppetboard
--
Daniele Sluijters
--
You received this mes
, don't patch custom things into Puppet or Hiera etc, that will
break, eventually.
--
Daniele Sluijters
On Monday, 21 October 2013 20:54:13 UTC+2, Kurt Wall wrote:
>
> Hi everyone,
>
> We are working on enhancing our internal testing so we can improve the
> overall quality o
HI,
It should be possible to do something like this:
$users = [a,b,c]
$users += [d,e]
Or, $users = [[a,b,c] [d,e]] etc.
Perhaps a better question, what is it you're trying to do, exactly, that
you need this?
--
Daniele Sluijters
On Monday, 21 October 2013 20:21:18 UTC+2, Sergey Arl
it's staring me in the face but I'm just not
seeing it.
--
Daniele Sluijters
--
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+unsu
sh the complete configuration and send a
pull request towards Puppetlabs to clarify a few things in the docs about
how to
achieve all this.
--
Daniele Sluijters
On Thursday, 24 October 2013 15:59:13 UTC+2, Daniele Sluijters wrote:
>
> Hey,
>
> I've been battling this all day so
oint it to puppet:///modules/ssh/$osfamily/sshd_config
Good luck,
--
Daniele Sluijters
On Thursday, 24 October 2013 22:16:00 UTC+2, John wrote:
>
> I've written and deployed a simple Linux SSH module. But I need to modify
> to include support for FreeBSD and AIX. On top of that, I
Hey,
One other tip, fully qualify everything to avoid weird behaviour in puppet:
- $::osfamily, not $osfamily
- $::ssh::params, not $ssh::params
- include ::ssh::params, not ssh::params
--
Daniele Sluijters
On Thursday, 24 October 2013 22:16:00 UTC+2, John wrote:
>
> I've written a
Hey Eric,
I was curious if you could elaborate a bit more on the choice of JIRA. I'm
currently in the exact opposite spot, migrating away from JIRA to Redmine.
--
Daniele Sluijters
On Thursday, 24 October 2013 22:18:12 UTC+2, Eric Sorenson wrote:
>
>
> We're working on some
log and get applied. If not we return an
empty array so nothing happens, you can also chose not to provide a default
in which case it will error.
As for how to organise roles and profile in Puppet, Craig Dunn has a very
nice post that should get you started:
http://www.craigdunn.org/2012/05/23
c0 -a type
# Gentoo and Debian call "x86_86" "amd64".
# Gentoo also calls "i386" "x86".
--
Daniele Sluijters
On Thursday, 24 October 2013 16:49:57 UTC+2, beyonddc...@gmail.com wrote:
>
> Hi all, hopefully this is a quick question. I would like to know why
from?
--
Daniele Sluijters
--
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 view this discussion on the w
Hi,
DenyHosts is not an option for me since I can't predict which hosts will be
connecting from the outside. Fail2ban solves that issue by looking for odd
behaviour instead of asking me to whitelist.
Thanks for the suggestion though,
--
Daniele Sluijters
On Tuesday, 29 October 2013 18:
Hi,
Ah indeed, I misread the puppetlabs-denyhosts module. I had a look at the
DenyHosts project but that seems limited to SSH alone. My fail2ban has
rules that scan logs of our web servers, mail etc.
--
Daniele Sluijters
On Wednesday, 30 October 2013 01:39:56 UTC+1, Don Hoffman wrote:
>
&
Hi,
Have you tried --environment=42A?
--
Daniele Sluijters
On Wednesday, 30 October 2013 09:47:13 UTC+1, AVE1810 wrote:
>
> Hi,
>
> When I run puppet agent --test --environment 42A, I have the following
> warning :
> Warning: Local environment: "42A" doesn&#
#x27;t
matter but it's nice for in your
calendar):
https://www.eventbrite.com/e/puppet-community-fosdem-meetup-tickets-5242929744
Now I just have to hope a few people will show up :).
--
Daniele Sluijters
--
You received this message because you are subscribed to the Google Groups
&
places would be extremely
helpful.
Just to avoid any confusion, this is no way an official Puppet Labs events
nor am I affiliated with Puppet Labs. This is just a call to socialise from
one community member to the rest.
--
Daniele Sluijters
On Friday, 10 January 2014 22:28:12 UTC+1, Johan De Wi
om the Solbosch
campus.
--
Daniele Sluijters
On Tuesday, 14 January 2014 17:02:45 UTC+1, Felix.Frank wrote:
>
> On 01/14/2014 04:22 PM, Erik Dalén wrote:
> > I'll be there (and at puppet camp amsterdam before and cfgmgmt.eu
> > <http://cfgmgmt.eu> the days after)
pport query pagination and
a few other long-standing feature requests.
Enjoy and as usual you can contact me or join #puppetboard for any help.
--
Daniele Sluijters
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this g
post.com/2014/01/21/belgian-cuisine-food_n_4617498.html
Johan: Do we have an idea yet where we can crash with 20-30 people?
--
Daniele Sluijters
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop recei
in. So, if you want food, please
register :).
See you soon!
--
Daniele Sluijters
On Thursday, 23 January 2014 11:27:36 UTC+1, Johan De Wit wrote:
>
> On 01/23/2014 11:18 AM, Daniele Sluijters wrote:
> > Hi everyone,
> >
> > This is starting to shape up nicely. W
Facts get sent at the start to the Puppet master so bringing an interface
online during a Puppet run won't make it available as a Fact during that
run, only on the next run as then the Facts are collected again. Your best
bet is to make it conditional, check for the existence of the Fact and onl
Hey,
It should work, Puppetboard is supposed to just pass in the settings to
pypuppetdb so unless we really screwed up somewhere that shouldn't be the
issue.
Can you show me your settings.py file?
--
Daniele Sluijters
On Saturday, 8 February 2014 23:35:43 UTC+1, Johan De Wit wrote:
&
and set SSL_VERIFY to the path
of ca_crt.pem. In that case the file SSL_VERIFY points to will be used to
verify PuppetDB's server certificate instead of the OS truststore.
I hope this fixes the issue for you.
--
Daniele Sluijters
On Monday, 10 February 2014 20:16:51 UTC+1, Johan De Wit wr
Hi,
What you're actually running into is that you want the nagios::commandes
class to be executed after the nagios package has been installed.
In that case, use the before metaparameter:
package { 'nagios':
ensure => present,
before => Class['nagios::commandes'],
}
This should fix your
Niels: Thank you for the Arch packages, I'll add them to the README's.
Jose: I'm not sure what you're getting at, what do you understand as
outofsync? Nodes that haven't checked in in a while show up, if that
timeframe is too big for you can modify the settings.
--
D
and the works
--
Daniele Sluijters
--
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 view this discussio
Use virtual users.
Instead of declaring your users as 'real', add a @ in front of them. Now
they are virtual so they aren't automatically created by Puppet, you need
to explicitly realise them, for example based on a tag or group they're a
member in.
You can do it along the lines of:
Users <|
to Puppet but with (perceived) errors in grammar, style
or formatting. Only a few are actually about code or command errors and a
few about terminology that's used before it's been explained or other
issues that could potentially hamper the users understanding.
--
Daniele Sluijters
On Thu
Hi,
I think a good start would be to turn on profiling, aka profiling=true in
puppet.conf or puppet agent --profile. The output will show up in the
master's logs.
--
Daniele Sluijters
On Friday, 11 April 2014 22:55:45 UTC+2, David Danzilio wrote:
>
> Hi Everybody.
>
> I&#x
e me to handle that case and throw my own error message. I'm perfectly
fine with the error message Puppet gives you in that case so I disable that
check.
--
Daniele Sluijters
On Friday, 11 April 2014 00:32:39 UTC+2, Rich Burroughs wrote:
>
> I saw one of the Puppet Labs webinars about
, it just ships with it. It'll also enable a bunch of things that will
make your life more pleasant as a module author or maintainer. If you're
using opensource modules it's likely they'll shortly start dropping 2.7
support if they haven't already with the coming of Puppe
The environment caching is already there, use the environment_timeout
setting. Mine is set to unlimited and I reload at deploy time by touching
tmp/restart.txt. This so far seems to work really well.
On Thursday, 22 May 2014 19:26:47 UTC+2, Tristan Smith wrote:
>
> Dang. That does look an awful
> - Don't use automatic hiera lookups. This removes the magic and makes it
more clear to everyone that the data is coming from hiera.
Hold on a sec; if you mean data bindings with 'automatic hiera lookups',
most certainly use them. Do not ever hardcode hiera() functions in
parameter lookups in
Sounds great! <3 and happy birthday (albeit a few days late but feel free
to consume more cake).
On Wednesday, 25 June 2014 18:53:25 UTC+2, Ashley Penney wrote:
>
> The 1st anniversary of the module team!
>
> Hello from the module team here at Puppet Labs! I’m starting this email
> with a lie b
ate you're stuck with manually patching an upstream module and
carrying that change. Depending on how you deploy your environment this
might be difficult to do.
--
Daniele Sluijters
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" g
have come to
expect at least some 'breakage' on .Y releases, regardless of wat semver
says (that's not anything personal towards Puppet Labs, it happens on a lot
of projects).
--
Daniele Sluijters
--
You received this message because you are subscribed to the Google Groups
&quo
First, congratulations this is awesome and will make a lot of people very
happy!
Second, typo in the README: puppet strings serever, that's one 'e' too many.
Third, is there an example module annotated with yard-style documentation
to give a people an idea of how to get this going? Some example
sicProvider, AuthUserFile and AuthGroupFile.
Until you have authentication set up, replace that Require line with:
Order deny,allow
Allow from all
Let me know if this works for you,
--
Daniele Sluijters
--
You received this message because you are subscribed to the Goo
settings.py as documented
here: https://github.com/nedap/puppetboard#settings
--
Daniele Sluijters
--
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 pu
host people would need to
be logged in to your master to intercept it. Your settings.py then looks
like this:
PUPPETDB_HOST = 'localhost'
PUPPETDB_PORT = 8080
PUPPETDB_TIMEOUT = 60
Once that works for you don't forget to change the LOGLEVEL back to 'info'.
--
Daniel
With the future parser we can now add type annotations to a whole bunch of
things. Usually it's pretty easy, just chuck the type in front of the
variable and you're done. But what if you have multiple variables or class
parameters beneath each other, do we align them, how do we align them, and
There's no need for CGI magic through the Puppet Master, you can talk to
PuppetDB directly. See the PuppetDB API
documentation:
https://docs.puppetlabs.com/puppetdb/latest/api/commands.html#examples-using-curl
On Wednesday, 10 December 2014 13:01:34 UTC+1, Ryan Anderson wrote:
>
> You could try
these two myself I've let them
slide.
I've created issues for transferring the maintainer/stewardship of both
projects on their respective repositories in the puppet-community
organization on Github. If you feel you're up for the challenge please have
a look and reply to them.
--
D
67 matches
Mail list logo
