I use a different scheme for doing this in our environment. When I reimage
physical hardware I use an unattended Kickstart script that does the
following:
* Saves an private key to /tmp/puppetkey via a here document (allows me to
embed it into the script and SSH wants it as a file)
* Uses SSH wit
Agreed.
Between the AIO packaging, change in configuration file locations, lack of
dashboards, and the many other minor annoyances I do not feel the benefits
of 4 outweigh the hassle of upgrading. 2->3 was much, much less painful.
Jeffrey.
On Thu, Aug 27, 2015 at 1:46 PM, Felix Barbeira wrote:
Put the puppetdb directory in /etc/puppet/modules.
Good luck.
Jeffrey.
On Thu, Mar 26, 2015 at 3:58 PM, Peter Berghold
wrote:
> OK... excuse me for being a bit dense... but how do you install this
> thing? i've unzipped it and it isn't very obvious to me...
>
--
You received this message bec
On Thu, Mar 26, 2015 at 11:29 AM, Peter Berghold
wrote:
> I need a push in the right direction. I have a need to have a subset of
> hosts in my environment "register" themselves to receive rsync updates from
> a central host. I realize that the right approach is exported resources
> but I'm get
On Wed, Oct 1, 2014 at 8:13 AM, jcbollinger
wrote:
>
> I'm fine with C (which I use a lot), and I love Java, JVM and all. I'm
> satisfied with a wide variety of scripting languages. Although it's not
> chic, I even like Fortran for certain uses. But I hate C++.
>
> As for a link, the C++ Frequ
On Fri, Aug 15, 2014 at 7:31 AM, Vikas Kumar wrote:
> Dear All,
>
> I am trying to restart SSH daemon whenever /etc/ssh/sshd_config is
> modified. This is my class, it modifies the file but does not restarts the
> daemon. I have tried to use both *notify* and *subscribe* in vain.
>
Change your s
Stuart, by doing a simple Google search I show from the release notes that
Puppet 3.2 added Ruby 2.0 support, but I see no mention of the addition of
Ruby 2.1 support.
My guess is that it's not been added.
Jeffrey.
On Fri, Dec 27, 2013 at 3:42 PM, Stuart Cracraft wrote:
>
> Has anyone else seen
+1
I've been using this script for the last month to view the "last run"
details, and it works very well. Here at my shop I am not worried about
changes, but I am worried about errors. I wrote a small Python script that
queries PuppetDB (if you're not using it, use it) and reports if there were
Ken, here's my puppet.conf:
[main]
logdir = /var/log/puppet
modulepath = /etc/puppet/modules
rundir = /var/run/puppet
ssldir = $vardir/ssl
[agent]
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
server = puppetmaster.example.com
show_diff = true
[
My concern is that after downloading the PuppetDB RPM from PuppetLabs it
should not throw errors on installation, which it currently does if you
install it on a server that is not the master. I also believe that having
the PuppetDB separate from the Puppetmaster is not an edge case (I'd
actually a
lobs, has SuSE compatible
> init/systemd scripts, etc.
>
> Download Top level for all repos:
> http://download.opensuse.org/repositories/systemsmanagement:puppet/
>
> Build Project:
> https://build.opensuse.org/package/show/systemsmanagement:puppet/puppetdb
> --
> Later,
>
I just built the PuppetDB 1.4.0 RPMs on OpenSuSE 12.1. The specfile works
much better on OpenSuSE now. Two issues came up, however:
The 'BuildRequires:sles-release' needs to have a conditional around it so
that it can tell between SLES and OpenSuSE. I think this works (I don't
have a SLES box t
Has anyone had time to look at my diff?
Thanks again,
Jeffrey.
On Fri, Jul 26, 2013 at 4:04 PM, Jeffrey Watts wrote:
> Hello! I was looking at using the puppetlabs-vcsrepo module for a
> project, but it seems to be missing a feature I need. Specifically, I need
> to be able to do o
Hello! I was looking at using the puppetlabs-vcsrepo module for a project,
but it seems to be missing a feature I need. Specifically, I need to be
able to do one of the following two things:
svn cat URL > FILENAME
svn export URL
Looking at the code, they do not seem supported. So, after some go
If you followed the instructions on the website it calls for you to create
a database named "dashboard". However, the example database.yml that comes
with the software calls for the database to be called
"dashboard_production". This bit me in the ass, and I suspect that it
might have bitten you a
Thanks Ken!
J.
On Thu, May 9, 2013 at 7:26 AM, Ken Barber wrote:
> Hi Jeffrey,
>
> It is a 'bug', and a known one at that:
>
> http://projects.puppetlabs.com/issues/17523
>
> Feel free to watch/vote for it.
>
> ken.
>
> On Wed, May 8, 2013 at 7:04
I'm setting up PuppetDB for the first time (and on OpenSuSE, yay). After
some tinkering I've gotten the package rebuilt and working. However, on
first setup puppetdb-ssl-setup fails with the following message:
# /usr/sbin/puppetdb-ssl-setup
cp: cannot stat
`/var/lib/puppet/ssl/private_keys/puppe
Michael, I'll try and help. I had a set of servers at my last employer
where I had to run two separate agents from cron. That particular team had
been using Puppet to manage an application which was no longer being
actively developed and was on life support.
Therefore, when I deployed Puppet acr
I'd like to second Michael's suggestion. Kelsey's various presentations
involving Hiera and data bindings were all excellent, and really cleared
things up for me.
Jeffrey.
On Mon, Nov 19, 2012 at 11:57 AM, Michael Hall
wrote:
> Yup, we have some work to do on this. I recently joined the Puppet
On Mon, Oct 15, 2012 at 3:05 PM, windowsrefund wrote:
> Well for starters, this isn't a RHEL mailing list and we're not talking
> about the RHEL solution. If we're going to just start comparing things in
> order to find justification for any and all actions, why stop there? Let's
> compare to Appl
On Mon, Oct 15, 2012 at 2:20 PM, windowsrefund wrote:
>
> Nothing about RHEL has anything to do with this thread.
>
Well, I used it as an example of a similar business model. I think it's a
very germane comparison. Both are commercial companies that sell support
for Open Source programs and als
I admire your conviction but keep in mind that Red Hat and others have done
a similar thing and it's only been good for the community. Perhaps you
don't use RHEL, but you certainly use one of the many innovations that were
funded by dollars that came from RHEL subscriptions.
I also think you're b
My view on the matter has always been this. Most people already know how
to find Puppet (it's usually in their distribution already). This change
might inconvenience people slightly, but it's not a big deal for the
technically adept. The folks who aren't technically adept should use their
distri
+1
On Wed, Oct 3, 2012 at 9:02 AM, Rilindo Foster wrote:
> I usually explicitly set the $puppetversion in my manifest for my
> environment. Furthermore, I have my own mirror copied from puppet labs repo
> and install it from that location instead. That way, I have control of what
> I push out an
This update will serve to educate them that using ensure => latest for
critical packages like this in a production environment is not a good idea.
:)
Jeffrey.
On Wed, Oct 3, 2012 at 9:36 AM, Mister Guru wrote:
> I'm sending this email to start this thread, feel free to comment as
> appropriate
I should have clarified - I'm using SLES10 and 11 and ruby(abi) isn't
provided See here:
> rpm -q ruby --provides
/usr/bin/ruby
bigdecimal.so()(64bit)
bubblebabble.so()(64bit)
cparse.so()(64bit)
curses.so()(64bit)
dbm.so()(64bit)
digest.so()(64bit)
dl.so()(64bit)
etc.so()(64bit)
fcntl.so()(64bit)
ysql
< Requires: ruby > 1.8.7, rubygem(rake)
---
> Requires: rubygems, ruby-mysql
> Requires: ruby > 1.8.7, rubygem-rake
22,25d21
< Requires(post): chkconfig
< Requires(preun): chkconfig
< Requires(preun): initscripts
< Requires(postun): initscripts
137a134
I took the RHEL/EPEL RPMs for ruby-shadow and puppet and rebuilt them for
SLES. There are very few things that need changing. The RHEL/EPEL RPMs
have really well put together SPECfiles.
I believe I posted the SPECfile diff for puppet to this list a month or so
ago. You might search the archives
Here's what I do. I use generate() to calculate the run times for our jobs
so that each server runs twice per hour at a pseudo-random but consistent
time. I use the IP address of the server, modulo 30.
# Generate the times when the cronjob will run
$cron_time1= generate('/usr/bin/env', 'sh',
I am. I run ours on a 1GB RAM VM with 2 vCPUs. We manage about 500 Linux
servers, each checking in every 30 mins. It's pretty much idle, though I'm
gradually rolling out our modules so our catalog currently compiles fast.
I'm using Webrick, and plan on moving to Passenger/Apache whenever it
starts
I am. I run ours on a 1GB RAM VM with 2 vCPUs. We manage about 500 Linux
servers, each checking in every 30 mins. It's pretty much idle, though I'm
gradually rolling out our modules so our catalog currently compiles fast.
I'm using Webrick, and plan on moving to Passenger/Apache whenever it
starts
To answer your first question, I highly recommend reading "Pro Puppet" by
Turnbull and McCune. It's a very sysadmin-focused book and talks in depth
about how to make Puppet scale. My setup here is much smaller (about 600
SLES and RHEL servers), and it did a great job of helping me get set up
with
Oh, that really clears it up. Thanks!
Jeffrey.
On Mon, Feb 13, 2012 at 11:48 AM, Gary Larizza wrote:
>
> And I don't think I've cleared this up for you - you DON'T NEED TO INCLUDE
> the class in a node declaration for a node to have that module's custom
> facts loaded and available to your nod
Yes, thanks. My only concern though is that catalogs will fail to compile
if that particular module that it's located in isn't included in that node
definition. I worry that any successors will not be able to easily figure
out what I've done.
Could I create a module named "global" and have it si
Gary, I've been solving this problem by using the following inline_template
in the modules that need to get the major release version:
$os_major_ver = inline_template("<%= operatingsystemrelease.split('.')[0]
%>")
I'm new to Puppet, and I like the elegance of your example below - to
implement it,
Any reason you can't do the following?
file { "/aaa/bbb/ccc"
ensure => 'directory',
}
Jeffrey.
On Thu, Dec 15, 2011 at 9:43 PM, chateau Xiao wrote:
> hi all:
> if we need to ensure a file exist in a folder that not yet been created.
> puppet will simplely report error.
> for example:
>
>
Here's how I do it, which IMHO works really well in most situations and is
much simpler. No external scripts, no custom functions. We take the IP
address of the system, strip out the periods, and modulo 30 it:
$cron_time1= generate('/usr/bin/env', 'sh', '-c', "printf $(($(echo
$::ipaddress | a
ysql
< Requires: ruby > 1.8.7, rubygem(rake)
---
> Requires: rubygems, ruby-mysql
> Requires: ruby > 1.8.7, rubygem-rake
22,25d21
< Requires(post): chkconfig
< Requires(preun): chkconfig
< Requires(preun): initscripts
< Requires(postun): initscripts
137
I just took the SRPM, commented out the Requires lines that have chkconfig
and initscripts in them, and removed ruby(abi) from the other Requires
lines. Then I just rebuilt it and it works just fine.
Note that a couple of your failed dependencies are legit - you need to
install ruby-mysql and rub
Not sure if you're aware, but 'init' is no longer init. Upstart is the
default init in many distributions, though Fedora/RHEL (and others) are now
moving to systemd, which is much better.
rpm -qf /sbin/init
Jeffrey.
On Fri, Dec 9, 2011 at 9:38 AM, David Alden wrote:
>
> I'm running Scientific
e?
>
> I guess which tool would you consider to be the quickest, easy to
> implement etc? From what I am seeing the community here seems to be
> much more active than the others. I have yet to get a response on the
> other forums.
>
> On Dec 8, 4:39 pm, Jeffrey Watts wrote:
I should also add that a very important consideration is to take in mind
_who_ will be working with this. Are they developers, sysadmins, QA? Will
the people working on it be spending a lot of time with
Puppet/Chef/CFengine, or just a little? Are you planning on writing a
bunch of custom modules
42 matches
Mail list logo
