Re: [Puppet Users] Re: revoke / delete node certificate from puppet ca remotely?
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 with '-i /tmp/puppetkey' to connect to the puppetmaster. The
command passed is the FQDN of the system to be reinstalled.
* On the Puppetmaster, I set up an authorized_keys entry for that key that
prepends command="/opt/puppetlabs/bin/puppet node clean
$SSH_ORIGINAL_COMMAND". This restricts SSH to only running that command
for connections involving that key. It will pass the command argument (the
FQDN) along as $SSH_ORIGINAL_COMMAND.
Now, this all assumes that you're not on a public network and thus are
comfortable using services such as SSH in this fashion. I haven't tried
the curl method. My only concern is whether or not curl exists in
installation images. SSH almost always does.
Hope this helps someone.
Jeffrey.
On Tue, Jul 14, 2020 at 6:22 PM Randy Zagar wrote:
> Did you ever get this to work? I used a similar method in an engineering
> lab where systems regularly got re-imaged and, hence, needed to be able to
> revoke and clean their own cert on the puppet-ca
>
> On Thursday, August 17, 2017 at 12:23:10 PM UTC, Jason McMahan wrote:
>>
>> Good morning,
>> We installed a puppet agent on our citrix mgmt servers.
>> The problem became that the way it is done a golden image is used,
>> server_dev. Once sealed that spins off multiple other servers for stage and
>> prod environments.
>>
>> We want to know about the servers, ensure they are in configuration and
>> not drifting between rebuilds and keep reports for a history on them.
>>
>> The idea was to once they are done stop the service (not disable), delete
>> the ssl directory, then revoke and delete the cert on the puppetca.
>>
>>
>> Has anyone else attempt to revoke and delete cert remotely from the
>> puppetca?
>>
>> We are attempting a curl command like
>> curl -X DELETE --tlsv1 --cacert
>> /etc/puppetlabs/puppet/ssl/certs/ca.pem --cert
>> /etc/puppetlabs/puppet/ssl/certs/server.pem--key
>> /etc/puppetlabs/puppet/ssl/private_keys/server.pem -H "Accept:
>> application/json" -H "Content-Type: application/json" -d
>> '{"desired_state":"revoked"}'
>> https://puppetcat:8140/puppet-ca/v1/certificate_status/server?environment=production
>>
>> But everytime we get forbidden 403 whether running curl command from
>> remote server or even the puppetca itself.
>> Attemped to add ip to
>> /etc/puppetlabs/puppetserver/conf.d/puppetserver.conf as well as
>> /etc/puppetlabs/puppetserver/conf.d/ca.conf but still same error.
>>
>>
>> Any help or suggestions would be greatly appreciated.
>> Thank you
>>
> --
> 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 web visit
> https://groups.google.com/d/msgid/puppet-users/8c9be388-990e-4d02-a376-b1d1dca394c9o%40googlegroups.com
>
> .
>
--
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 web visit
https://groups.google.com/d/msgid/puppet-users/CAMvPdm1wssY81SCjB4CxuueVyZ00bY4ZgLyTrkyZyTohQcxYag%40mail.gmail.com.
Re: [Puppet Users] how were your puppet 3-4 upgrades?
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 fbarbe...@gmail.com wrote: Same here. El miércoles, 26 de agosto de 2015, 15:45:07 (UTC+2), Pete Harvey escribió: On 26 August 2015 at 09:16, Fabrice Bacchella fabrice@orange.fr wrote: My biggest problem: there isn't any working dashboard working with Puppet 4. This. Our upgrade to 4 is essentially blocked until Foreman supports it. Pete -- 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 web visit https://groups.google.com/d/msgid/puppet-users/CAMvPdm1dFEOT4T8yP1TojV4jcoc1o2ERjJKZnyurA1Rp_QEAiw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Creating a list of hosts
On Thu, Mar 26, 2015 at 11:29 AM, Peter Berghold salty.cowd...@gmail.com
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 getting stuck on the actual implementation.
Hi! I'd recommend you look at the wonderful puppetdb-query:
https://github.com/dalen/puppet-puppetdbquery
I use it to extract hostnames from PuppetDB to populate various things.
It's been a long time since I set this up but it should be as simple as
installing the module and doing something like this:
manifests/init.pp:
$all_hosts = query_nodes('kernel=Linux')
file { 'fqdns.txt':
content = template('test/fqdns.erb'),
ensure= file,
path = '/foo/bar/fqdns',
}
templates/fqdns.erb:
%- all_hosts.each do |fqdn| -%
%= fqdn %
%- end -%
Hope this helps!
Jeffrey.
--
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 web visit
https://groups.google.com/d/msgid/puppet-users/CAMvPdm1yWn11x0KNf7CVwJ0hDG%3D%3DR4-Wo0po60a-hDH2Qsi90A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Creating a list of hosts
Put the puppetdb directory in /etc/puppet/modules. Good luck. Jeffrey. On Thu, Mar 26, 2015 at 3:58 PM, Peter Berghold salty.cowd...@gmail.com 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 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 web visit https://groups.google.com/d/msgid/puppet-users/CAMvPdm0pmOYTcVZqjJUxXAN553e%3DiRoXCfrxL-8kU9zeCx6DYQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: Puppet Server 0.2.0
On Wed, Oct 1, 2014 at 8:13 AM, jcbollinger john.bollin...@stjude.org 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++ Frequently Questioned Answers http://yosefk.com/c++fqa/ helped me crystallize some of my previously less-focused distaste for C++. Whenever I hear programmers argue about the merits and failings of different programming languages I remember this old joke: At the beginning of the week, we sealed ten BSD programmers into a computer room with a single distribution of BSD Unix. Upon opening the room after seven days, we found all ten programmers dead, clutching each others' throats, and thirteen new flavors of BSD. There's a reason there are dozens (hundreds?) of general purpose programming languages - people can't agree on which is the best tool for a job. Using C++ as the underlying language won't be the end of the world. :) Jeffrey. -- 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 web visit https://groups.google.com/d/msgid/puppet-users/CAMvPdm2bJdSH8ZamhcdXncoYK5tgMRyHD-3pJVTLhC%2BYwcbjow%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Restart ssh daemon when sshdconfig is modified
On Fri, Aug 15, 2014 at 7:31 AM, Vikas Kumar vikas...@gmail.com 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 subscribe line to Augeas[my-ssh]. Good luck, Jeffrey. -- 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 web visit https://groups.google.com/d/msgid/puppet-users/CAMvPdm1i%2BxXj54W-8rBTw5mRXmnQtCzd7sZF7%2B9mzePdcjMAsQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet 3.3.2 with ruby 2.1.0
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 smcracr...@gmail.comwrote: Has anyone else seen this? ruby is 2.1.0 and puppet is 3.3.2. # /etc/init.d/puppetmaster start Starting puppetmaster: /usr/local/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- puppet/util/command_line (LoadError) from /usr/local/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/bin/puppet:3:in `main' FAILED # I rolled back to the earlier version of ruby which handily works. -- 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 web visit https://groups.google.com/d/msgid/puppet-users/af8cd42d-c0af-42f9-90db-14b60620279d%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- 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 web visit https://groups.google.com/d/msgid/puppet-users/CAMvPdm09TRzk08DgC-N6cAVSqpHzLT4ER_kTEAAXNoqpYVskFw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] get a *structured* version of the puppet agent output
+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 any errors on any nodes during their last run of the night (we do not run Puppet during trading hours). I also use Puppet Dashboard for at-a-glance sanity checking and as an easy way to drill down on unresponsive hosts and to easily view reports. The combination of these three tools work very well for me. Jeffrey. On Tue, Nov 26, 2013 at 1:15 PM, R.I.Pienaar r...@devco.net wrote: not everyone shares the same goals so everyone tend to write them, but here you go this is one I wrote http://www.devco.net/archives/2013/10/10/cli-report-viewer-for-puppet.php -- 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 web visit https://groups.google.com/d/msgid/puppet-users/CAMvPdm17zvpCCJfbxp%2BB_CkNGeY-QYfmdgpZoYoc0TnntAG3eQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] PuppetDB 1.4.0 on OpenSuSE
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 [master] autosign = /etc/puppet/autosign.conf ca_name = Puppet CA: puppetmaster.example.com certname = puppetmaster.example.com reports = http,puppetdb reporturl = http://puppetdashboard.example.com:3000/reports/upload ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY storeconfigs = true storeconfigs_backend = puppetdb [test] manifest = /etc/puppet/environments/test/manifests/site.pp modulepath = /etc/puppet/environments/test/modules This was an upgrade, so the certs were already signed and in place. Hope this helps, Jeffrey. On Sun, Sep 29, 2013 at 1:20 PM, Ken Barber k...@puppetlabs.com wrote: On a normal setup puppet master --configprint ssldir and puppet agent --configprint ssldir should return the same thing. And normally you don't have your master configuration on agent nodes. But doing that sort of fallback sounds like a good solution that should cover most cases well. The patch is close, but I think we should probably check all files in advance though not just one, and also warn when we fall through. 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'd be curious to see what your puppet.conf looks like in this case. Also, were the certificates previously signed before the installation occurred? I also believe that having the PuppetDB separate from the Puppetmaster is not an edge case (I'd actually argue it's best practice, especially in this era of virtualization). No disagreements here. ken. -- 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 puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] PuppetDB 1.4.0 on OpenSuSE
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 argue it's best practice, especially in this era of virtualization). Gary Wilson's proposed patch seems to solve the problem - try 'puppet master' first, and then fall back to 'puppet agent'. IMHO if someone has a more complicated setup where that wouldn't work, then the onus should be on them to modify puppetdb-ssl-setup. Thanks for your consideration, Jeffrey. On Fri, Sep 27, 2013 at 6:26 AM, Ken Barber k...@puppetlabs.com wrote: Lastly, the puppetdb-ssl-setup script still does not work when the PuppetDB does not reside on the Puppetmaster. The fix is pretty simple, and the issue is in the bug tracker. I created a question and answer on ask.puppetlabs.com to try and help others that run into it: https://ask.puppetlabs.com/question//puppetdbs-puppetdb-ssl-setup-script-does-not-work-when-the-puppetdb-is-not-on-the-puppetmaster/ So the ticket for those reading along at home is here: http://projects.puppetlabs.com/issues/17523 And I must admit its controversial but saying it 'doesn't work' isn't entirely true. More precisely there are situations where it doesn't work, and I want to hear what people have to add to this - as its a really interesting topic that we probably need some community feedback on. Let me show you an example, with an empty puppet.conf ... the settings returned are identical: root@puppetdb1:~# puppet apply --configprint hostcert /etc/puppet/ssl/certs/puppetdb1.vm.pem root@puppetdb1:~# puppet master --configprint hostcert /etc/puppet/ssl/certs/puppetdb1.vm.pem But when you have overrides in relation to agent/master that create differences between the [master] and [agent] sections things go wrong. Try this one on for size: root@puppetdb1:~# cat /etc/puppet/puppet.conf [master] ssldir = /tmp [agent] ssldir = /tmp2 root@puppetdb1:~# puppet master --configprint hostcert /tmp/certs/puppetdb1.vm.pem root@puppetdb1:~# puppet agent --configprint hostcert /tmp2/certs/puppetdb1.vm.pem So like I said ... this is actually fine for some people, and preferential, but for others its not fine. The question is, what is the better default I think. So in my opinion I would have thought that agent was a better default over master as some people presume, but that changed some time ago in 0.9.2: https://github.com/puppetlabs/puppetdb/commit/de23912a73f6adadf36f26d438939d4c9e49a68b I suppose there are arguments for either direction, but I'm not as clear on the direction to move this to use the [master] section specifically. I can't help but feel its a less common case. Erik - perhaps you can chime in on the thread and give us your reasoning for wanting this in the first place? I guess we have been apprehensive on moving on that ticket because changing default behaviour is often scary ... if we change it its going to break for some people without a doubt. So what is the answer? Perhaps a flag to allow people to choose? What do people think the setting should be, and why? ken. -- 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 puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- 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 puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] PuppetDB 1.4.0 on OpenSuSE
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 to test against):
%if 0%{?sles_version}
BuildRequires: sles-release
%else
BuildRequires: openSUSE-release
%endif
Lastly, the puppetdb-ssl-setup script still does not work when the PuppetDB
does not reside on the Puppetmaster. The fix is pretty simple, and the
issue is in the bug tracker. I created a question and answer on
ask.puppetlabs.com to try and help others that run into it:
https://ask.puppetlabs.com/question//puppetdbs-puppetdb-ssl-setup-script-does-not-work-when-the-puppetdb-is-not-on-the-puppetmaster/
I'd like to thank the PuppetLabs folks for making the specfile MUCH more
OpenSuSE friendly. It only took me ten minutes this time to fix the
problems in the specfile - 1.3.0 took a lot longer.
Thanks!
Jeffrey.
--
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 puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] PuppetDB 1.4.0 on OpenSuSE
Thanks Darin!
Jeffrey.
On Thu, Sep 26, 2013 at 11:01 AM, Darin Perusich da...@darins.net wrote:
Jeff,
I've packaged puppetdb for OpenSUSE/SLES. all versions, and it's
available in the systemsmanagement:puppet repository. It builds
puppetdb fully from source, no binary blobs, 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,
Darin
On Thu, Sep 26, 2013 at 11:51 AM, Jeffrey Watts
jeffrey.w.wa...@gmail.com wrote:
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 to test against):
%if 0%{?sles_version}
BuildRequires: sles-release
%else
BuildRequires: openSUSE-release
%endif
Lastly, the puppetdb-ssl-setup script still does not work when the
PuppetDB
does not reside on the Puppetmaster. The fix is pretty simple, and the
issue is in the bug tracker. I created a question and answer on
ask.puppetlabs.com to try and help others that run into it:
https://ask.puppetlabs.com/question//puppetdbs-puppetdb-ssl-setup-script-does-not-work-when-the-puppetdb-is-not-on-the-puppetmaster/
I'd like to thank the PuppetLabs folks for making the specfile MUCH more
OpenSuSE friendly. It only took me ten minutes this time to fix the
problems in the specfile - 1.3.0 took a lot longer.
Thanks!
Jeffrey.
--
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 puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Enhancement to puppetlabs-vcsrepo
Has anyone had time to look at my diff? Thanks again, Jeffrey. On Fri, Jul 26, 2013 at 4:04 PM, Jeffrey Watts jeffrey.w.wa...@gmail.comwrote: 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 googling on modifying providers, I took a stab at it and I added a export parameter. Attached to the email is my diff. Keep in mind the following: 1) My Ruby sucks, and probably always will. 2) I've never modified a provider before, and I really have no idea what I'm doing. Requests: 1) Am I going about this the right way? 2) Any suggestions as to how to do it better? As per the suggestions in the Module Contributing wiki page, I'm coming here for suggestions/abuse before going further. Thanks! Jeffrey. P.S. It's been a while since I've played with the puppet module command. Nice work! Was very easy. -- 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 puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Enhancement to puppetlabs-vcsrepo
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 googling on modifying providers, I took a stab at it and I added a export parameter. Attached to the email is my diff. Keep in mind the following: 1) My Ruby sucks, and probably always will. 2) I've never modified a provider before, and I really have no idea what I'm doing. Requests: 1) Am I going about this the right way? 2) Any suggestions as to how to do it better? As per the suggestions in the Module Contributing wiki page, I'm coming here for suggestions/abuse before going further. Thanks! Jeffrey. P.S. It's been a while since I've played with the puppet module command. Nice work! Was very easy. -- 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 puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. vcsrepo.diff Description: Binary data
Re: [Puppet Users] mysql access denied on dashboard puppet
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 as well. Just create dashboard_production and you should be okay. J. On Fri, Jun 21, 2013 at 12:54 PM, DJames dominicrja...@gmail.com wrote: i am at a lost, i setup the db schema , database.yml and etc passwords are correct. im getting the below error, im trying to get my dashboard to work .help any? i also chmod the database.yml file to 660 # mysql -u dashboard -p dashboard_production Enter password: ERROR 1045 (28000): Access denied for user 'dashboard'@'localhost' (using password: YES) -- 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 puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- 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 puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Bug in puppetdb-ssl-setup?
Thanks Ken!
J.
On Thu, May 9, 2013 at 7:26 AM, Ken Barber k...@puppetlabs.com 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 PM, Jeffrey Watts jeffrey.w.wa...@gmail.com
wrote:
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/puppetmaster.mycompany.com.pem': No
such
file or directory
I'm planning on running PuppetDB on a separate box from my Puppetmaster.
Digging into the script a bit, the problem seems to be with the use of
the
'puppet master' command to find the certificate information. I use a
monolithic puppet.conf for my master and agents, so it's picking up the
master's configuration instead of the agent's.
Anyhow, this small diff seems to get me past the problem. Is this a bug?
Thanks,
Jeffrey.
# diff -u /usr/sbin/puppetdb-ssl-setup puppetdb-ssl-setup
--- /usr/sbin/puppetdb-ssl-setup 2013-05-06 11:04:25.0 -0500
+++ puppetdb-ssl-setup 2013-05-08 12:57:47.423096218 -0500
@@ -94,10 +94,10 @@
fqdn=`facter hostname`
fi
-mycertname=`puppet master --confdir=$agent_confdir
--vardir=$agent_vardir
--configprint certname`
-mycert=`puppet master --confdir=$agent_confdir --vardir=$agent_vardir
--configprint hostcert`
-myca=`puppet master --confdir=$agent_confdir --vardir=$agent_vardir
--configprint localcacert`
-privkey=`puppet master --confdir=$agent_confdir --vardir=$agent_vardir
--configprint hostprivkey`
+mycertname=`puppet agent --confdir=$agent_confdir --vardir=$agent_vardir
--configprint certname`
+mycert=`puppet agent --confdir=$agent_confdir --vardir=$agent_vardir
--configprint hostcert`
+myca=`puppet agent --confdir=$agent_confdir --vardir=$agent_vardir
--configprint localcacert`
+privkey=`puppet agent --confdir=$agent_confdir --vardir=$agent_vardir
--configprint hostprivkey`
pw_file=${puppetdb_confdir}/ssl/puppetdb_keystore_pw.txt
--
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 puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Bug in puppetdb-ssl-setup?
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/puppetmaster.mycompany.com.pem': No such
file or directory
I'm planning on running PuppetDB on a separate box from my Puppetmaster.
Digging into the script a bit, the problem seems to be with the use of the
'puppet master' command to find the certificate information. I use a
monolithic puppet.conf for my master and agents, so it's picking up the
master's configuration instead of the agent's.
Anyhow, this small diff seems to get me past the problem. Is this a bug?
Thanks,
Jeffrey.
# diff -u /usr/sbin/puppetdb-ssl-setup puppetdb-ssl-setup
--- /usr/sbin/puppetdb-ssl-setup 2013-05-06 11:04:25.0 -0500
+++ puppetdb-ssl-setup 2013-05-08 12:57:47.423096218 -0500
@@ -94,10 +94,10 @@
fqdn=`facter hostname`
fi
-mycertname=`puppet master --confdir=$agent_confdir --vardir=$agent_vardir
--configprint certname`
-mycert=`puppet master --confdir=$agent_confdir --vardir=$agent_vardir
--configprint hostcert`
-myca=`puppet master --confdir=$agent_confdir --vardir=$agent_vardir
--configprint localcacert`
-privkey=`puppet master --confdir=$agent_confdir --vardir=$agent_vardir
--configprint hostprivkey`
+mycertname=`puppet agent --confdir=$agent_confdir --vardir=$agent_vardir
--configprint certname`
+mycert=`puppet agent --confdir=$agent_confdir --vardir=$agent_vardir
--configprint hostcert`
+myca=`puppet agent --confdir=$agent_confdir --vardir=$agent_vardir
--configprint localcacert`
+privkey=`puppet agent --confdir=$agent_confdir --vardir=$agent_vardir
--configprint hostprivkey`
pw_file=${puppetdb_confdir}/ssl/puppetdb_keystore_pw.txt
--
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 puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Multiple Puppet agents on one node?
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 across the entire company I set up those machines to have two separate agent runs with different Puppetmasters. I ran two separate crons with separate names so the two Puppets wouldn't conflict. I manually set the --server, --logdest, --vardir, and --ssldir directives (--ssldir may be extraneous if your local config is $vardir/ssl) on the cronjob's command line. I had no issues running them separately, keep in mind though that it might get hairier if you try and run two different Puppet versions. I never tried doing that. Good luck, and I hope this helps. Jeffrey. On Wed, Feb 20, 2013 at 11:22 AM, Michael Hüttermann mich...@huettermann.net wrote: Hello, can I run two different Puppet agents on one node listening to two different Masters? Thank you for your help. Best regards Michael -- 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 puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Getting Started with Hiera
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 michael.h...@puppetlabs.comwrote: Yup, we have some work to do on this. I recently joined the Puppet Labs documentation team, and getting Hiera better documented is high on my list of priorities. If you don't mind spending the time watching a video of a talk, I can recommend Kelsey Hightower's presentation at PuppetConf '12: http://www.youtube.com/watch?v=z9TK-gUNFHkfeature=youtu.be It provides a walkthrough example that might help you get your arms around Hiera a little better. I've converted the slide deck to a PDF, but it's a little large so please email me directly if you'd like me to forward a copy to you. There are also a few notes on the Hiera github repo, including a note on how to make sure your hierarchy and data files are correctly configured: https://github.com/puppetlabs/hiera/tree/master/docs/tutorials Hope this helps a little, and we'll have more formal documentation out soon. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: The free software tarballs are now difficult to find
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 distribution provided version or they ought to be buying PE. PuppetLabs is a company that makes its money off of Puppet Enterprise. I see nothing wrong with them promoting it or making it the easiest download. They want new folks to see PE first, get it, love it, and not want to leave it. Making the Open Source version more prominently featured on their site doesn't help their business model. I feel that their business model is a good one, and good for everyone - companies that want a more bundled product with support can pay for a product that pays the salaries of developers who make the Open Source version better. Jeffrey. P.S. I don't use Puppet Enterprise. On Mon, Oct 15, 2012 at 10:42 AM, windowsrefund windowsref...@gmail.comwrote: And yet, I haven't heard a single user say anything to the affect of please make us jump through additional hoops in order to download the Free Software releases. In fact, this thread exists because users are speaking out against the change made to the traditional download path. It would be nice to see the site reverted back to the previous behavior. Believe me, users who want PE will get it without having it pushed on them. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: The free software tarballs are now difficult to find
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 being overly dramatic and exaggerating when you say that it's treated like a red headed step-child. We disagree but I think what's changed is pretty minor in the big scheme of things. Jeffrey. On Mon, Oct 15, 2012 at 12:39 PM, windowsrefund windowsref...@gmail.comwrote: This has nothing to do with being adept and also has nothing to do with PL's business model. For a Free Software zealot such as myself, the software and it's community is far more important. It was bad enough to see the business agenda decide to switch to a non-copyleft license and now we're seeing the free software version treated like a red headed step-child. We've seen this trend play itself out hundreds of times over the years and it's starting to look like PL is turning out to be a wolf in sheep's clothing. We'll see... -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: The free software tarballs are now difficult to find
On Mon, Oct 15, 2012 at 2:20 PM, windowsrefund windowsref...@gmail.comwrote: 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 also sell proprietary products. Both contribute considerably to FOSS. But apparently you disagree that it's a relevant comparison - though you decline to state why. I don't think I'm being dramatic at all. I'm simply pointing out my observations when I consider PL's change of direction lately. Again, the move from a copyleft to a non-copyleft license kicked things off. This was followed by catering to the Windows crowd and now the front-end is pushing PE on the community. Look, if it's no big deal and such a minor change, why hasn't the download link just been reverted? In other words, I'm thinking PL does in fact see this as a big deal. I'm simply voicing my distaste. Well then perhaps I ought to point out that your distaste reeks of drama and isn't very constructive. One thing I learned a long time ago is that hyperbole and hostility, while certainly making one feel self-righteous, in the end is pretty worthless as an instrument of change. But perhaps somehow, things will be different this time and your efforts will bear fruit. Good luck! Jeffrey. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: The free software tarballs are now difficult to find
On Mon, Oct 15, 2012 at 3:05 PM, windowsrefund windowsref...@gmail.comwrote: 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 Apple, Microsoft, the bagel I had for breakfast this morning, the outcome of the election and anything else totally irrelevant If you're going to disregard arguments that don't support your conclusions then you're not interested in a serious discussion. Look, don't start trying to paint me in a negative light here. I'm not the one who has taken specific actions designed to alienate the free software community. Let's get back to the topic at hand. Someone obviously made the decision to make the community jump through yet another hoop in order to obtain and therefore, use, the free software version over PE. Who made that decision and how was that justified? More importantly, who is making the call to not revert the page now that objections have been raised? Windows (may I call you by your first name?), you seem to forget that I complimented your ideals before politely disagreeing. Your responses have been disproportionate to the discussion. Right now it's my opinion that you're more interested in ranting and raving on the Internet behind a dubious nom de plume than having a real discussion on this issue. Please prove me wrong. Jeffrey. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How to prevent puppet clients from updating to version 3?
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 misteritg...@gmail.com wrote: I'm sending this email to start this thread, feel free to comment as appropriate. I'm going to assume that it's going to take a while for most people to actually realise that the puppet update may be giving them some issues, so, comments and suggestion please! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet 2.7 v 3.0 in the PuppetLabs yum repo
+1 On Wed, Oct 3, 2012 at 9:02 AM, Rilindo Foster rili...@mac.com 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 and only update when I know that the new version is sound. So I am not sure what the hubbub is all about. If you are not controlling what you push out, don't be surprised when something breaks. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Regression in SUSE package for puppet-dashboard-1.2.7
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) gdbm.so()(64bit) iconv.so()(64bit) libruby.so.1.8()(64bit) md5.so()(64bit) nkf.so()(64bit) openssl.so()(64bit) pty.so()(64bit) readline.so()(64bit) rmd160.so()(64bit) sdbm.so()(64bit) sha1.so()(64bit) sha2.so()(64bit) socket.so()(64bit) stringio.so()(64bit) strscan.so()(64bit) syck.so()(64bit) syslog.so()(64bit) thread.so()(64bit) wait.so()(64bit) zlib.so()(64bit) ruby = 1.8.7.p72-5.30.5 Jeffrey. On Mon, Apr 23, 2012 at 1:38 PM, Darin Perusich da...@darins.net wrote: Actually ruby(abi) is defined as a Provides in ruby.spec for SuSE, see link below, but I don't know why it fails to pick it up. You can simply force the puppet-dashboard package with --nodeps and it works just fine. https://build.opensuse.org/package/view_file?file=ruby.specpackage=rubyproject=openSUSE%3A12.1%3AUpdaterev=dbf21799e3d1bb8b3b21b5aa109d7530 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Regression in SUSE package for puppet-dashboard-1.2.7
SuSE doesn't use the ruby(abi) dependencies. That's a Red Hat thing. The
good news is that it's trivial to rebuild the RPM so that it works with
SLES. I posted a diff a while back on this list - it's what I use.
Keep in mind that this was for an older version, so YMMV. Good luck.
Jeffrey.
$ diff puppet-dashboard.spec puppet-dashboard.spec-sles
2c2
%global initrddir /etc/rc.d/init.d
---
%global initrddir /etc/init.d
9c9
Release:1%{?dist}
---
Release:2%{?dist}
17,18c17,18
Requires: ruby(abi) = 1.8, rubygems, ruby-mysql
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,136
* Wed Dec 07 2011 Jeffrey Watts jwa...@adknowledge.com - 1.2.3-2
- Modified it to work on SLES
On Fri, Apr 20, 2012 at 2:44 AM, Julien C. cornu...@gmail.com wrote:
Hi,
I'm using the following repository :
http://download.opensuse.org/repositories/home:/eclipseagent:/puppet/openSUSE_12.1/
And I'm having a weird error when I try to update puppet-dashboard :
Problem: nothing provides ruby(abi) = 1.8.7 needed by
puppet-dashboard-1.2.7-6.1.noarch
My ruby (1.8.7.p357-2.3.1.i586) seems up-to-date and I didn't have this
message when I installed 1.2.6
Any idea what I'm missing ?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet on OpenSuSE SLES
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. Mostly what I did was comment out the Red Hat specific dependencies - it was really easy. You can build without Augeas if you're not using it. Good luck. Jeffrey. On Mon, Mar 12, 2012 at 5:19 AM, Julien C. cornu...@gmail.com wrote: Hi, I'm a big fan of Puppet and managed to have my company accept it. However, I'm having issues deploying it (I'm used to the debian version which works perfectly out of the box) : - There doesn't seem to be an official repository for Suse (I've seen it mentionned in the bugtracker but yum.puppetlabs.com doesn't contain SUSE packages). - I can't find a package for ruby-shadow. - I can't find a package for augeas either. I circumvented these problems by installing Puppet by hand (tarball) and writing ugly code (execs) to manage config files and user passwords. However, I'd like to know if I missed anything or if you can suggest solutions for any of these 3 issues... -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Need modules for cron
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', '-c', printf $(($(echo
$::ipaddress | awk -F . \'{print \$1+\$2+\$3+\$4}\') % 30)))
$cron_time2 = $cron_time1 + 30
cron { 'puppet-cron':
ensure = present,
command = $puppet_command,
minute = [$cron_time1, $cron_time2],
user= 'root',
}
Hope this helps,
Jeffrey.
On Thu, Mar 8, 2012 at 10:20 AM, Jeeva 19.mu...@gmail.com wrote:
We are planning to run the puppet client as a cron rather than running
as a daemon. Could you please help me in creating a module for running
the puppet client as a cron
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Master VMs
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 slowing down. Jeffrey On Thursday, March 1, 2012, Scott Merrill wrote: Is anyone running their Puppet Master server(s) as virtual guests? If so, how big are those VMs in terms of memory and virtual CPUs, and how many Puppet clients are they serving? Thanks! Scott -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Master VMs
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 slowing down. I doubt I'll ever need to go to a physical server. I run Dashboard on another VM. Jeffrey On Thursday, March 1, 2012, Scott Merrill wrote: Is anyone running their Puppet Master server(s) as virtual guests? If so, how big are those VMs in terms of memory and virtual CPUs, and how many Puppet clients are they serving? Thanks! Scott -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.comjavascript:; . To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com javascript:;. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] enterprise puppet architecture
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 Puppet and Dashboard. Jeffrey. On Wed, Feb 22, 2012 at 10:36 AM, Brown, Rodrick rbr...@knight.com wrote: I have no experience with Puppet and will like to start planning out my puppet architecture. I will be using puppet to manage a large CentOS/RHEL network thousands of systems. Is there a general deployment guide targeted for large enterprise puppet deployments. Also is there any way to extend puppet using Python or using Python to interface with Puppet’s API? ** -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: neatest way to determine a major version of centos/linux?
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, would I need to put that block in
modulename/lib/facter/operatingsystemmajor.rb? I assume I'd need to put
that in every module that'd use it. Is there a better way? I currently
use that block in 3 or 4 modules.
Thanks!
Jeffrey.
On Sun, Feb 12, 2012 at 6:25 PM, Gary Larizza g...@puppetlabs.com wrote:
There's also the 'operatingsystemrelease' fact that will evaluate to the
full version. You could do this:
Facter.add('operatingsystemmajor') do
setcode do
Facter.value('operatingsystemrelease').split('.').first
end
end
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: neatest way to determine a major version of centos/linux?
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 simply be where things
like that live? What's the minimum I'd need to have in it? An init.pp
with simply class global { }? Are there other, better ways?
Thanks again,
Jeffrey.
On Mon, Feb 13, 2012 at 11:29 AM, Gary Larizza g...@puppetlabs.com wrote:
Hi Jeffrey,
You're correct about the placement of the file, however you don't need to
include it in EVERY module you use. That fact only needs to be in ONE of
your modules for every node to utilize it as a Facter fact (currently, ANY
Facter facts that are in your $modulepatch get loaded by ALL of your nodes).
So repeating this code is very redundant. Does this makes sense?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: neatest way to determine a major version of centos/linux?
Oh, that really clears it up. Thanks! Jeffrey. On Mon, Feb 13, 2012 at 11:48 AM, Gary Larizza g...@puppetlabs.com 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 node. For example, if this fact lived in the mysql module, you DO NOT NEED to have 'include mysql' in the node declaration for the node to have access to the custom fact. Custom facts get synced down to the clients via Pluginsync, and ALL custom facts that are in ANY modules in your $modulepath will automatically get synced down to ALL Puppet nodes BEFORE Puppet starts running REGARDLESS of whether that module's classes are declared in a node declaration. BTW, don't misinterpret the emphasis for yelling - just trying to emphasize specific points that I might have glossed-over previously :) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet capacity with apache+passenger, server saturated
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 | awk -F . \'{print \$1+\$2+\$3+\$4}\') % 30)))
$cron_time2 = $cron_time1 + 30
Now, that's if you want to have your systems check in twice per hour. You
can adjust it accordingly if you want quicker or longer check-in intervals.
Jeffrey.
On Tue, Dec 20, 2011 at 7:46 AM, Trevor Vaughan tvaug...@onyxpoint.comwrote:
One other thing to look at is how many nodes are hitting your server at
once.
If you're not using the ip_to_cron function from the Cron Patterns
page, you might want to take a look at it.
http://projects.puppetlabs.com/projects/1/wiki/Cron_Patterns
Some people are also using MCollective to to a more controlled call-in of
nodes.
Trevor
On Fri, Dec 16, 2011 at 7:56 AM, Antonio Xanxess
antonio.sanchez.agui...@gmail.com wrote:
Hi everyone,
I have a problem with my Puppet server, the server is overloaded and
processes need to add half of my farm nodes yet!
The server is hosted on a blade with the following characteristics:
Processors: 8 cores
Memory Ram: 12 Gb
Operating System: Debian Squeeze
Version of parcel:
2.7.1-1 ~ bpo60 puppet 1
puppet-common 2.7.1-1 ~ bpo60 1
2.7.1-1 ~ bpo60 1 puppetmaster
puppetmaster 2.7.1-1 ~ bpo60-1 common
puppet vim 2.7.1-1 ~ bpo60-1
The number of nodes that I have now is 1927 and I'm in the middle of
the deployment process. The nodes do not use the demon puppet, but I
created a cron task that runs dispersed to run in one hour intervals.
With these data the server is currently using on average 4 cores, but
the RAM is used almost entirely (it has 1 GB free of 12)
I would like to know some technical expert for the optimization of
services, anything you can think of will help me because I am a bit
blocked
I've been thinking about creating another puppetmaster and use a load
balancer, but in my case would have security problems because the
connections are behind the balancer and servers unencrypted would be
in different physical locations, having to go unencrypted information
by the network.
Thank you and if you need some data from the server will put.
A greeting!
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com
-- This account not approved for unencrypted proprietary information --
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] a question about ensure file exists
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 chateau.x...@gmail.comwrote:
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:
file { /aaa/bbb/ccc/aaa
ensure = 'present';
}
if directory ccc not yet been created, puppet client excute will get an
error message.
Does puppet have any function to auto mkdir -p this path an make sure the
file exist?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [SPAM] Re: [Puppet Users] problem with fund service
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 d...@alden.name wrote: I'm running Scientific Linux 6.1. What do you mean by upstart script? I get the same think with /etc/init.d/funcd status as I do service funcd status -- both return funcd is not running and the exit status is 3. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Dashboard or Forman on SLES?
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 rubygem-rake. Jeffrey. On Thu, Dec 8, 2011 at 4:53 AM, Wiesel82 wiese...@gmx.ch wrote: Hi all, i planned for a startup to install one of this gui tools. But if i look in the documentation, or google it, i find no results which helps. If i would like to install the rpm package i get the following dependencies problems rpm -i puppet-dashboard-1.2.3-1.el6.noarch.rpm warning: puppet-dashboard-1.2.3-1.el6.noarch.rpm: Header V4 RSA/SHA1 signature: NOKEY, key ID 4bd6ec30 error: Failed dependencies: chkconfig is needed by puppet-dashboard-1.2.3-1.el6.noarch initscripts is needed by puppet-dashboard-1.2.3-1.el6.noarch rpmlib(FileDigests) = 4.6.0-1 is needed by puppet- dashboard-1.2.3-1.el6.noarch ruby(abi) = 1.8 is needed by puppet-dashboard-1.2.3-1.el6.noarch ruby-mysql is needed by puppet-dashboard-1.2.3-1.el6.noarch rubygem(rake) is needed by puppet-dashboard-1.2.3-1.el6.noarch rpmlib(PayloadIsXz) = 5.2-1 is needed by puppet- dashboard-1.2.3-1.el6.noarch and for foreman rpm -i foreman-0.4-0.2.noarch.rpm error: Failed dependencies: chkconfig is needed by foreman-0.4-0.2.noarch initscripts is needed by foreman-0.4-0.2.noarch ruby(abi) = 1.8 is needed by foreman-0.4-0.2.noarch rubygem(json) is needed by foreman-0.4-0.2.noarch rubygem(rake) = 0.8.3 is needed by foreman-0.4-0.2.noarch rubygem(rest-client) is needed by foreman-0.4-0.2.noarch rubygem(sqlite3-ruby) is needed by foreman-0.4-0.2.noarch I don't find some packages for Sles 11 SP1. Did anybody installed one of this tools on Sles 11 SP1? Best regards Wiesel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Is puppet right for us?
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, or relying on the community? What languages does your team work on primarily? For example, folks that work with Ruby a lot would probably do better with Puppet and Chef. As a sysadmin, I often see developers get distracted by arguments about what's best or the most technically advanced. Often they forget that in the end the real answer is often which tool gets the job done the quickest, with the least amount of labor, and is the most supportable. Jeffrey. On Thu, Dec 8, 2011 at 12:44 PM, Daniel Pittman dan...@puppetlabs.comwrote: Instead, I suggest you focus on your ability to learn the concrete use of the tool, and on how effectively you can solve problems with them; doing a small trial of each - solve the same mid-sized problem three times, giving each a day or two - and see what you think works best for your company and culture. There is no silver bullet. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Is puppet right for us?
I've found Puppet to be unreliable running as a daemon - I suspect due to older versions of ruby floating around. So I switched to running it from cron, and it works a lot better. Memory usage doesn't seem to be an issue, and the agent only runs for a few seconds. Use Puppet Dasboard (or something like it) and/or use Nagios to make sure those cron jobs run. I use both. The main thing is to have Puppet managing itself and the cron job. I have ours set up to run the cron job twice an hour, using the concatenated IP address modulo 30 and modulo 30 + 30 as the times (to keep the clients from hammering the Puppetmaster all at once). Let me know if you go with Puppet and I'll show you how I did it. Part of the reason we chose Puppet was the quantity of documentation and working examples and the helpfulness of the community. I support (and implement) our Puppet environment here at my job. I would highly recommend Mr Turnbull's Pro Puppet book. It is VERY sysadmin focused and will save you a lot of time. The sections on environments, modules, and Dashboard were really helpful. Jeffrey Sent from my iPad On Dec 8, 2011, at 2:59 PM, Luke lutay...@gmail.com wrote: This tool will be used by primarily system admins to automate server builds app installs, configurations etc. The devs will use it in their own environment to help automate some of their tasks. I don't think we have too much Ruby expertise since we are mostly a Java shop. In terms of performance I have read that CFengine uses much less memory and can be faster than puppet. Can anyone comment on the agent and server memory usage? I have read that the puppet agent can use 85mb and the server upwards to 1GB after 20-30agents. Is that accurate? 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 jeffrey.w.wa...@gmail.com 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, or relying on the community? What languages does your team work on primarily? For example, folks that work with Ruby a lot would probably do better with Puppet and Chef. As a sysadmin, I often see developers get distracted by arguments about what's best or the most technically advanced. Often they forget that in the end the real answer is often which tool gets the job done the quickest, with the least amount of labor, and is the most supportable. Jeffrey. On Thu, Dec 8, 2011 at 12:44 PM, Daniel Pittman dan...@puppetlabs.comwrote: Instead, I suggest you focus on your ability to learn the concrete use of the tool, and on how effectively you can solve problems with them; doing a small trial of each - solve the same mid-sized problem three times, giving each a day or two - and see what you think works best for your company and culture. There is no silver bullet. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
