Re: [Puppet Users] inventory service vs stored config (conflicts?)
On Wed, Jul 25, 2012 at 11:19 PM, Hai Tao ehai...@gmail.com wrote:
what if I need to install foreman, which uses stored config, right?
Can foreman use the puppetDB as its database?
foreman doesnt really need store configs, see
http://theforeman.org/projects/foreman/wiki/Puppet_Facts
Ohad
On Wed, Jul 25, 2012 at 11:33 AM, Justin Stoller jus...@puppetlabs.com
wrote:
On Wed, Jul 25, 2012 at 11:08 AM, Hai Tao ehai...@gmail.com wrote:
storeconfig also store facts, as I can see from the table list after
I configured stored config:
+--+
| Tables_in_puppet |
+--+
| fact_names |
| fact_values |
| hosts|
| inventory_facts |
| inventory_nodes |
| param_names |
| param_values |
| puppet_tags |
| resource_tags|
| resources|
| source_files |
+--+
then the question is why would inventory needed anymore?
the db settings are the same for both inventory and storeconfigs
(that's why they'll conflicdt). when you tell puppet to use either it
will automatically create the database for you. it creates one puppet
database, and puts tables in there for both storeconfigs and inventory
service. the actual code to retrieve, save and query facts (inventory
service) and puppet resources (storedconfigs) are different however
and even if the tables exist they all won't be populated until you
enable both.
does that make sense?
On Wed, Jul 25, 2012 at 10:46 AM, Justin Stoller jus...@puppetlabs.com
wrote:
they will conflict
you should definitely look into puppetdb as a more scalable solution
than the active_record terminus for both inventory service and
storeconfigs
storedconfigs stores resources from your puppet manifests and
inventory service stores facts.
- Justin
sorry for the top post
On Wed, Jul 25, 2012 at 9:43 AM, Hai Tao ehai...@gmail.com wrote:
I have set up inventory service to save my client's fact, as
[master]
facts_terminus = inventory_active_record
dblocation = {sqlite file path (sqlite only)}
dbadapter = {sqlite3|mysql|postgresql|oracle_enhanced}
dbname = {database name (all but sqlite)}
dbuser = {database user (all but sqlite)}
dbpassword = {database password (all but sqlite)}
dbserver = {database server (MySQL and PostgreSQL only)}
dbsocket = {database socket file (MySQL only; optional)}
the question is if I then config the stored config, will the db
conflicts?
storeconfigs = true
dbadapter = mysql
dbuser = puppet
dbpassword = password
dbserver = localhost
dbsocket = /var/run/mysqld/mysqld.sock
as many are overlaped, such as dbadapter, dbpassword? I also do not
understand what stored config store other than facts.
Thankls.
Hai T.
--
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.
--
Hai Tao
--
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.
--
Hai Tao
--
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
Re: [Puppet Users] a complete solution for puppet
You could try using foreman installer(aka as plain puppet modules)[1], which does take care for the following 1. apache configuration + passenger 2. puppet master (with optional dynamic git branches / environments) 3. foreman stuff if you don't need storeconfigs, then you don't have to use it. if you need to scale to more than one master, my guess is that the main thing to overcome is the CA setup (single CA server etc) and thats the kind of knowledge you need to have regardless of an installer. Ohad [1] https://github.com/theforeman/foreman-installer#readme On Thu, Jul 26, 2012 at 12:20 AM, Hai Tao ehai...@gmail.com wrote: I see. so it is on purpose to make it not easy to use so the enterprise can be sold? :) On Wed, Jul 25, 2012 at 2:02 PM, Christopher Wood christopher_w...@pobox.com wrote: Sounds like you should be talking to your managers about buying Puppet Enterprise. On Wed, Jul 25, 2012 at 02:00:37PM -0700, Hai Tao wrote: Hi, I notice that many components of puppet do not scale well and are not intended for large environment. For example, stored config and inventory service. In order to scale, we need to use puppetDB, right? Another example is the webrick, and which should be replaced by a decent web server such as apache. All these need a lot of new installation of pieces of software and configurations. My question is why the designer of puppet did not consider this and integrate everything into a complete solution at the beginning, rather than having us have to reconfigure everything by hand. Who will use puppet if he has only 50 nodes? -- Hai Tao -- 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. -- Hai Tao -- 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] How to acgieve Inter-Node Dependencies with Puppet?
Hi, Not out of the box. You'd need a combination of puppet and MCollective to get orchestration. Cheers Den On 25/07/2012, at 16:27, ashrith ashr...@cloudwick.com wrote: Hey guys, I am getting started with puppet and started writing some modules which include client-server installation model. I was wondering if there is any possibility of acheving inter-node dependencies using puppet for example: Say, I have dependency between starting servcies on two nodes. First the the service on the sever should start, then only service on the client machines should start. For real world example: Consider, I have Hadoop HA Setup where I want certain services (ZooKeeper's) to start before starting the another services on set of different machines(NameNode's). Is this kind of dependencies supported by Puppet? If so can some one explain me how? Any help is appreciated. Thanks, Ashrith. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/y2zH4VBOAJAJ. 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.
[Puppet Users] Weird cannot reassign variable name on node error when I try to use standalone
Hi -- I'm trying call apply in standalone mode on a configuration I've written. The way I call the command is like this: $ puppet apply manifests/site.pp -v --modulepath modules The directory structure is simple: . manifests/site.pp manifests/nodes.pp modules/ ... site.pp just includes nodes.pp, and nodes.pp looks like this: https://gist.github.com/3181007 When I comment out the node declaration, it all compiles just fine, but with the node declaration, I get this error: Cannot reassign variable name on node ip-xx-xx-xx-xx.eu-west-1.compute.internal Obviously, the node's name in the original doesn't have 'xx's, but a valid IP. Can anybody advise me as to how to get this working? I've tried everything I can think of. Thanks very much for any all assistance, Doug. -- 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 complete solution for puppet
- Original Message -
| Hi,
|
| I notice that many components of puppet do not scale well and are not
| intended for large environment. For example, stored config and
| inventory service. In order to scale, we need to use puppetDB, right?
| Another example is the webrick, and which should be replaced by a
| decent web server such as apache. All these need a lot of new
| installation of pieces of software and configurations.
|
| My question is why the designer of puppet did not consider this and
| integrate everything into a complete solution at the beginning,
| rather
| than having us have to reconfigure everything by hand. Who will use
| puppet if he has only 50 nodes?
|
| --
| Hai Tao
I'm sure that the designers of puppet made every effort to make puppet as
usable and scalable as they could when it was being designed. This is proven
time and time again but the sites that currently have puppet deployed with tens
of thousands of nodes. You should take care when making such bold statements,
but I assume of course that it was not you intention to insult anyone.
We originally rolled puppet out with 10 machines. Managing 10 machines without
puppet was 10 times more work than managing 10 machines with puppet. We had to
log into each host and apply updates as appropriately. We had to develop
management scripts to manage them as well. Puppet helped unify this and ensure
less drift between machines so any more than one machine and puppet can be
really handy.
Now the other thing is that much of Puppet's configuration options can be
swapped out for better scalability. For example the default storage backend
could be MySQL, PostgreSQL or PuppetDB. The built in webrick server swapped
for {Apache,cherokee,nginx}+passenger. The management from CLI to something
like Puppet Dashboard, The Foreman or the Puppet Enterprise solution. It's
completely up to you the route you take.
So does puppet scale well for large environments by default no, but that's ok,
swap out a component that's the bottleneck and move on. It seems that your
complaint is that there isn't a single all-in-one solution for you to choose
from, when in fact there is, Puppet Enterprise. This comes with all the tools
you'd need to scale puppet in a black box style. If you're too cheap and
don't want to pay for that you can try The Foreman installer which does a
pretty good job of installing the toolchain to scale puppet to larger
environments using Apache and Passenger and you don't really need to know squat
about how the components go together. You could find a How To or tutorial
online and just follow it line by line if you want to! Go for it!
At any rate, you're going to have to learn about the toolchain associated with
scaling puppet anyway. You're going to need to learn how to monitor and tweak
Apache and Passenger if you need to scale the web components. You're going to
need to know how to tweak MySQL, PostgreSQL or Puppet DB for stored configs.
For PuppetDB you're also going to have to learn a bit about tuning Java to make
it scale too!
Learn the tools or pay for a tuned black box. You can't have it both ways. If
you want a rather simple way to deploy Puppet+Apache+Passenger+The Foreman, use
The Foreman installer which works quite well. Have fun!
--
James A. Peltier
Manager, IT Services - Research Computing Group
Simon Fraser University - Burnaby Campus
Phone : 778-782-6573
Fax : 778-782-3045
E-Mail : jpelt...@sfu.ca
Website : http://www.sfu.ca/itservices
http://blogs.sfu.ca/people/jpeltier
Success is to be measured not so much by the position that one has reached
in life but as by the obstacles they have overcome. - Booker T. Washington
--
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] cwd dot folders
exec { myexectest:
path= /bin:/usr/bin:/usr/sbin,
cwd = /home/user/.ssh,
creates= /home/user/.ssh/test.txt
command =echo test test.txt,
}
http://docs.puppetlabs.com/references/latest/type.html#exec
http://docs.puppetlabs.com/references/latest/type.html#exec
Do you have provider set in some default Exec -block? If not, then the
default is posix, not shell, which probably doesn't handle stream
redirection.
Cheers,
Paul
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/r3iLc56hE58J.
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 complete solution for puppet
Hey, Chris: so that begs the question, do you think you have some secret or are just happier with fewer flashy gui's, more install/deployment scripts, and so forth. In other words, do you think the scaling of Open Puppet is adequate to scale much larger without the flash? Or, is there something fundamentally holding back Open Puppet from handling thousands, tens of thousands, or hundreds of thousands of nodes, in your opinion? Cheers, Stuart On Wednesday, July 25, 2012 2:52:00 PM UTC-7, Christopher Wood wrote: On Wed, Jul 25, 2012 at 02:20:17PM -0700, Hai Tao wrote: I see. so it is on purpose to make it not easy to use so the enterprise can be sold? :) There are different skill levels at different tasks in the enterprise space, and it is legitimate that some organizations are better off with a prefabbed installer for a configuration management system. I've created a puppet installation of reasonable complexity without puppet enterprise, but that is possibly just me: $ cd files/puppet/svn/prod/trunk $ ls manifests/nodes | wc -l 43 $ find modules -name *pp | wc -l 174 That's not to say I don't salivate a bit at the thought of Puppet Enterprise, but my budget of $0 doesn't help there. Or perhaps a career-long $0 budget has helped, in that I'm more used to building from components instead of buying the package. People who are more used to buying than building may be better off with a different situation than mine. On Wed, Jul 25, 2012 at 2:02 PM, Christopher Wood christopher_w...@pobox.com wrote: Sounds like you should be talking to your managers about buying Puppet Enterprise. On Wed, Jul 25, 2012 at 02:00:37PM -0700, Hai Tao wrote: Hi, I notice that many components of puppet do not scale well and are not intended for large environment. For example, stored config and inventory service. In order to scale, we need to use puppetDB, right? Another example is the webrick, and which should be replaced by a decent web server such as apache. All these need a lot of new installation of pieces of software and configurations. My question is why the designer of puppet did not consider this and integrate everything into a complete solution at the beginning, rather than having us have to reconfigure everything by hand. Who will use puppet if he has only 50 nodes? -- Hai Tao -- 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. -- Hai Tao -- 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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/MW0Ok3Eent8J. 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 and Java/OSGi?
Hi, We are looking for a framework that will facilitate deployment and configuration of our applications. Puppet seems to be one possibility but I have some questions: First of all, our applications are written in Java. Is there an impact concerning the use of Puppet? We also write our applications using OSGi, so our applications are divided in multiple bundles that run on an OSGi framework. Does Puppet support such kind of architecture? Thanks, Mickael -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/dWogtGM2lyMJ. 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] Intermittent freeze on select when running standalone
I have a new Ubuntu LTS VM running a simple manifest directly with puppet apply. About one time in 5 strace reports that puppet is sat there waiting on a select operation with low cpu usage. I'm wondering if this implies it's somehow gone into agent/deamon mode. Also just wondering if this is a puppet or a ruby/OS/VM issue. And why I cannot find anyone else with the same issue. I cannot imagine it's the manifest. It does one file check and two notifies. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/6sOuZGKUncUJ. 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] puppetlabs-release-CODENAME.deb
Are the puppetlabs-release-CODENAME.deb packages signed? I tried executing the following apt-key adv --recv-key --keyserver pool.sks-keyservers.net 4BD6EC30 downloaded puppetlabs-release-precise.deb wget http://apt.puppetlabs.com/puppetlabs-release-precise.deb then tried debsig-verify puppetlabs-release-precise.deb which gave me debsig: Origin Signature check failed. This deb might not be signed. Would like to verify puppetlabs-release-precise.deb before installing it. - Tom -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/713kOP5xmw8J. 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] Infrastructure Design help
Hi guys, I've been tasked with bringing our unix environment under puppet control so I'm trying to source some Infrastructure design guidelines and recommendations examples on how to apparoach designing the environment from a top down approach. By that I mean starting perhaps with the site.pp file and filtering hosts by nodename into various groups like dev, uat prod etc.. What are other groups doing keeping scalability in mind ? I have seen a chapter on Infrastructure design on the old puppetlabs wiki but haven't found anything as of yet on the new puppet docs website. Can anyone point me in the right direction please ? thanks, K -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/UCsFraTZtQ0J. 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] Schema of dependency tree?
On 07/26/2012 02:04 AM, James A. Peltier wrote: Add graph = true to the agent section on your puppet client. Then look in /var/lib/puppet/state/graphs. You can then use dot to generate images of the dependencies. Thank you. FYI, the command is: dot -Tpng resoruces.dot -o resources.png One problem is that it generates very wide images (for example in my case 22'000 x 500 px). Is there a way to make it something like 500 x 22'000, so that dependencies go from left to right and not from top to bottom? It would be much easier to read such a graph... -- 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 complete solution for puppet
I have heard from various other puppet users of Open Puppet installations of tens of thousands of nodes (at least last I heard, there's probably people with more) so it definitely scales that high. Generally they've had to restrict themselves on some features or sometimes use Puppet in slightly strange ways to improve scaling, but people are definitely doing it today. The flash you get from PE just makes things easier. Most of us started with a fairly small Puppet trial and over time developed modules to build up an entire puppet infrastructure. I have a fairly (badly) written module that installs puppetmasters, sets up repos, hiera, databases, everything needed to fully deploy a relatively scalable Puppet infrastructure. I think there's a lot of us out there, maybe a few of us should get together, share what we have, and try to build a combined module that people can use to help bootstrap and scale. On Wed, Jul 25, 2012 at 7:34 PM, Stuart Cracraft smcracr...@me.com wrote: Hey, Chris: so that begs the question, do you think you have some secret or are just happier with fewer flashy gui's, more install/deployment scripts, and so forth. In other words, do you think the scaling of Open Puppet is adequate to scale much larger without the flash? Or, is there something fundamentally holding back Open Puppet from handling thousands, tens of thousands, or hundreds of thousands of nodes, in your opinion? Cheers, Stuart On Wednesday, July 25, 2012 2:52:00 PM UTC-7, Christopher Wood wrote: On Wed, Jul 25, 2012 at 02:20:17PM -0700, Hai Tao wrote: I see. so it is on purpose to make it not easy to use so the enterprise can be sold? :) There are different skill levels at different tasks in the enterprise space, and it is legitimate that some organizations are better off with a prefabbed installer for a configuration management system. I've created a puppet installation of reasonable complexity without puppet enterprise, but that is possibly just me: $ cd files/puppet/svn/prod/trunk $ ls manifests/nodes | wc -l 43 $ find modules -name *pp | wc -l 174 That's not to say I don't salivate a bit at the thought of Puppet Enterprise, but my budget of $0 doesn't help there. Or perhaps a career-long $0 budget has helped, in that I'm more used to building from components instead of buying the package. People who are more used to buying than building may be better off with a different situation than mine. On Wed, Jul 25, 2012 at 2:02 PM, Christopher Wood christopher_w...@pobox.com wrote: Sounds like you should be talking to your managers about buying Puppet Enterprise. On Wed, Jul 25, 2012 at 02:00:37PM -0700, Hai Tao wrote: Hi, I notice that many components of puppet do not scale well and are not intended for large environment. For example, stored config and inventory service. In order to scale, we need to use puppetDB, right? Another example is the webrick, and which should be replaced by a decent web server such as apache. All these need a lot of new installation of pieces of software and configurations. My question is why the designer of puppet did not consider this and integrate everything into a complete solution at the beginning, rather than having us have to reconfigure everything by hand. Who will use puppet if he has only 50 nodes? -- Hai Tao -- 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. -- Hai Tao -- 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 view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/MW0Ok3Eent8J. 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: export a file from a node to another node
On Wednesday, July 25, 2012 3:39:24 PM UTC-5, Nikolaos Hatzopoulos wrote:
so we define that file would be exported from node1 like:
@@file { etc/mynode.txt::
content = ${mycontent}
}
Basically, yes, but
1. You need to specify an absolute path, such as /etc/mynode.txt
2. The title or path you need to specify is the one you want the target
file to have on *node2* (the node that collects the resource). That can
be the same as the original file name, but it does not need to be.
3. If that resource is going to be exported from more than one node,
then each resource title should be unique across all nodes. Incorporating
an identifier for the exporting node is one way to accomplish that. You
should be able to use the 'path' property to specify a target filename and
path different from the resource title if you should need to do so.
and on the node2
File | | ?? I want only the info from node1 not from all nodes that
means I have to group the nodes for the specific action?
who it works here? I am pretty new in puppet but I didn't get it from the
documentation
I have no idea what the specifics of your situation are, so I'm trying to
point you in the right direction, not to hand you a boxed solution to the
problem. You can restrict the resources that will be collected by putting
a selection predicate in the | | spaceship operator. You should be
able to select by title, or it can be very convenient to apply a tag to
your resource and select by that. For example:
#
# For node1
#
# This assumes that only one node will export this file:
@@file { /etc/mynode.txt:
ensure = file,
content = ${mycontent}
}
#
#
# For node2
#
File| title == '/etc/mynode.txt' |
#
Do note that exporting and collecting resources depends on having [thin]
storeconfigs configured on the master. (Because, you know, the master
needs to store nodes' configurations to be able to use them to configure
other nodes.)
I should also say that although Puppet can do this job, it might not be the
most appropriate tool. You might want to consider alternative approaches,
such as (in no particular order)
- put the file under source control, such as in a git or Subversion
repository. Periodically sync any changes on node1 with the repository,
and periodically pull down any changes from the repository to node2.
- schedule a periodic direct copy from node1 to node2, via scp or some
similar remote copy tool
Periodic[ally] in the above is meant to imply use of an automated
scheduler, such as cron.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/9EuGxiFZeOkJ.
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] Re: Weird cannot reassign variable name on node error when I try to use standalone
On Thursday, July 26, 2012 3:41:05 AM UTC-5, biot023 wrote: Hi -- I'm trying call apply in standalone mode on a configuration I've written. The way I call the command is like this: $ puppet apply manifests/site.pp -v --modulepath modules The directory structure is simple: . manifests/site.pp manifests/nodes.pp modules/ ... site.pp just includes nodes.pp, and nodes.pp looks like this: https://gist.github.com/3181007 When I comment out the node declaration, it all compiles just fine, but with the node declaration, I get this error: Cannot reassign variable name on node ip-xx-xx-xx-xx.eu-west-1.compute.internal Obviously, the node's name in the original doesn't have 'xx's, but a valid IP. Can anybody advise me as to how to get this working? I've tried everything I can think of. The problem is in one of the classes declared by class 'imageserver', not in nodes.pp itself. When you comment out the node declaration, no resource declarations remain for any node, so of course there is no error. You didn't say anything about the classes declared by class 'imageserver', so I can't be more specific than that. If I were to take a wild guess, however, it would be that somewhere in there you have a defined type that attempts to assign a value to a local variable $name. The variable names name and title are reserved inside defined types; for each instance, they are pre-assigned to the resource title, and like all puppet variables, their values cannot be reassigned. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Vu0Ytpap1-8J. 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] Re: Infrastructure Design help
The way we are naming the nodes in our puppet environments are like this: First 2 letters: Property acronym 3rd letter: Environment (Prod = p, UAT = u, DEV = d) Next 2/3 letters: Node purpose (Application = app, Database = db, Membase = mb, etc) 2 Numbers: Unique node ID This will allow you to do Regular Expression filters in your site.pp file to apply certain classes to certain nodes for a given property in your various environments. On Thursday, July 26, 2012 6:42:27 AM UTC-4, karl wrote: Hi guys, I've been tasked with bringing our unix environment under puppet control so I'm trying to source some Infrastructure design guidelines and recommendations examples on how to apparoach designing the environment from a top down approach. By that I mean starting perhaps with the site.pp file and filtering hosts by nodename into various groups like dev, uat prod etc.. What are other groups doing keeping scalability in mind ? I have seen a chapter on Infrastructure design on the old puppetlabs wiki but haven't found anything as of yet on the new puppet docs website. Can anyone point me in the right direction please ? thanks, K -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/W6o7y0aDwfcJ. 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] Re: Weird cannot reassign variable name on node error when I try to use standalone
On Thursday, July 26, 2012 8:17:10 AM UTC-5, jcbollinger wrote: Hmm. I just realized that you are using Puppet in apply mode rather than agent mode. The problem may simply be that puppet apply doesn't want to handle node declarations. I don't use Puppet in apply mode, so I'm not sure, but node declarations don't make much sense in that context. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/TXUPq24EBpkJ. 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: Weird cannot reassign variable name on node error when I try to use standalone
Actually, your first answer was bang on the money -- thankyou ever so much for that! I'm now hacking through all the rest of the errors and typos to get it all running -- it's maybe time I looked into the puppet test module! Thanks again, that's really appreciated, Doug. On 26 July 2012 14:23, jcbollinger john.bollin...@stjude.org wrote: On Thursday, July 26, 2012 8:17:10 AM UTC-5, jcbollinger wrote: Hmm. I just realized that you are using Puppet in apply mode rather than agent mode. The problem may simply be that puppet apply doesn't want to handle node declarations. I don't use Puppet in apply mode, so I'm not sure, but node declarations don't make much sense in that context. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/TXUPq24EBpkJ. 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.
[Puppet Users] Puppet updated yum packages without logging?
We just saw an interesting scenario:
Puppet 2.7.18 updated packages on a RHEL 6.2 box to a newer version without
logging that fact.
We've already fixed our code so it doesn't happen again, but I'm wondering if
this is expected behavior or a bug.
* I presume the default ensure behavior on package is latest?The type
reference doesn't say that…
* For now, we've switched to using ensure = present… but I'd have liked the
logs to reflect that update.
Details, if necessary:
Now, we had the code as such:
package {
php:;
php-common:;
php-xml:;
php-domxml;:
}
and there was a single not present package to install (php-domxml).
Interestingly, the package was actually an older package name that's now
handled by a new package (php-xml), which meant that the actual message logged
was a failure.
Jul 25 14:09:43 web01 puppet-agent[1021]:
(/Stage[main]/Php/Package[php-domxml]/ensure) change from absent to present
failed: Could not find package php-domxml
This was the only package message logged, and yet we ended up with newer
versions.
Matthew Barr
Technical Architect
E: mb...@snap-interactive.com
AIM: matthewbarr1
c: (646) 727-0535
--
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 updated yum packages without logging?
Did something else pull that package in as a dependency?
On Thu, Jul 26, 2012 at 7:37 AM, Matthew Barr
mb...@snap-interactive.com wrote:
We just saw an interesting scenario:
Puppet 2.7.18 updated packages on a RHEL 6.2 box to a newer version without
logging that fact.
We've already fixed our code so it doesn't happen again, but I'm wondering
if this is expected behavior or a bug.
* I presume the default ensure behavior on package is latest?The
type reference doesn't say that…
* For now, we've switched to using ensure = present… but I'd have liked the
logs to reflect that update.
Details, if necessary:
Now, we had the code as such:
package {
php:;
php-common:;
php-xml:;
php-domxml;:
}
and there was a single not present package to install (php-domxml).
Interestingly, the package was actually an older package name that's now
handled by a new package (php-xml), which meant that the actual message
logged was a failure.
Jul 25 14:09:43 web01 puppet-agent[1021]:
(/Stage[main]/Php/Package[php-domxml]/ensure) change from absent to present
failed: Could not find package php-domxml
This was the only package message logged, and yet we ended up with newer
versions.
Matthew Barr
Technical Architect
E: mb...@snap-interactive.com
AIM: matthewbarr1
c: (646) 727-0535
--
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] fedoar 17 and puppet dashboard
This has to do with Ruby 1.9.3 being the default (and only) ruby in Fedora 17. Puppe 2.7 in Fedora 17 has a couple of outstanding bugs in the 2.7.x series with Ruby 1.9.3. Reporting is one of them. It can't easily be fixed without modifying behavior. When Puppet 3.0 arrives, this is fixed with Ruby 1.9.3. On Mon, Jul 23, 2012 at 6:50 AM, mauris9...@voila.fr mauris9...@voila.fr wrote: Hello, I add a node Fedora 17. The reports are a aperture in puppet-server in /var/lib/puppet/reports but not in Dashboard. While all other Fedra (16, 15, 14) are visible in Dashboard. Do you have an idea? Thank you. mauris -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/jwBW5rWsEzMJ. 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] Infrastructure Design help
Buy all the books at Amazon on Puppet (there are at least three) and read them all cover-to-cover. Engage the people at puppetlabs. They are friendly. Also read the entire puppetlabs.com site. Install Puppet Enterprise. Get a small test set under control and begin importing recipes from best practice and rolling your own. For a complete deployment, expect significant project time. Don't expect anyone to do the deployment for you. As you go along, debrief to your team and write it up on the group wiki profusely in case you are hit by a truck. When rolling out changes via puppet, be very careful to repository-record vis git every module change, rollout to Dev first, then Test/UAT then gradually , never all at once into production, ever. Good luck! --Stuart Via Apple iPhone 4S on the ATT Wireless Network On Jul 26, 2012, at 3:42 AM, karl k...@hampels.com.au wrote: Hi guys, I've been tasked with bringing our unix environment under puppet control so I'm trying to source some Infrastructure design guidelines and recommendations examples on how to apparoach designing the environment from a top down approach. By that I mean starting perhaps with the site.pp file and filtering hosts by nodename into various groups like dev, uat prod etc.. What are other groups doing keeping scalability in mind ? I have seen a chapter on Infrastructure design on the old puppetlabs wiki but haven't found anything as of yet on the new puppet docs website. Can anyone point me in the right direction please ? thanks, K -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/UCsFraTZtQ0J. 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: export a file from a node to another node
as far as I understand for files you need a unique title in my case
/etc/mynodes.txt
how you can export instead of a file a variable and let's say it has a
unique title
and it has as content a string can you do that?
The scp won't work because I am trying to setup the ssh keys with taking
the key
from a specific node and putting into the authorized_keys file of the other
:) on the other
hand I can make the scp for the root user.. but if you do that what's the
point of using
puppet (i have only linux nodes)?
--Nikos
On Thu, Jul 26, 2012 at 6:01 AM, jcbollinger john.bollin...@stjude.orgwrote:
On Wednesday, July 25, 2012 3:39:24 PM UTC-5, Nikolaos Hatzopoulos wrote:
so we define that file would be exported from node1 like:
@@file { etc/mynode.txt::
content = ${mycontent}
}
Basically, yes, but
1. You need to specify an absolute path, such as /etc/mynode.txt
2. The title or path you need to specify is the one you want the
target file to have on *node2* (the node that collects the resource).
That can be the same as the original file name, but it does not need to be.
3. If that resource is going to be exported from more than one node,
then each resource title should be unique across all nodes. Incorporating
an identifier for the exporting node is one way to accomplish that. You
should be able to use the 'path' property to specify a target filename and
path different from the resource title if you should need to do so.
and on the node2
File | | ?? I want only the info from node1 not from all nodes that
means I have to group the nodes for the specific action?
who it works here? I am pretty new in puppet but I didn't get it from the
documentation
I have no idea what the specifics of your situation are, so I'm trying to
point you in the right direction, not to hand you a boxed solution to the
problem. You can restrict the resources that will be collected by putting
a selection predicate in the | | spaceship operator. You should be
able to select by title, or it can be very convenient to apply a tag to
your resource and select by that. For example:
#
# For node1
#
# This assumes that only one node will export this file:
@@file { /etc/mynode.txt:
ensure = file,
content = ${mycontent}
}
#
#
# For node2
#
File| title == '/etc/mynode.txt' |
#
Do note that exporting and collecting resources depends on having [thin]
storeconfigs configured on the master. (Because, you know, the master
needs to store nodes' configurations to be able to use them to configure
other nodes.)
I should also say that although Puppet can do this job, it might not be
the most appropriate tool. You might want to consider alternative
approaches, such as (in no particular order)
- put the file under source control, such as in a git or Subversion
repository. Periodically sync any changes on node1 with the repository,
and periodically pull down any changes from the repository to node2.
- schedule a periodic direct copy from node1 to node2, via scp or some
similar remote copy tool
Periodic[ally] in the above is meant to imply use of an automated
scheduler, such as cron.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/9EuGxiFZeOkJ.
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.
[Puppet Users] Re: Puppet Dashboard and Ruby 1.8.7 for EL5 systems HOWTO (draft)
Thanks a lot. All this works fine for me.
Le jeudi 5 janvier 2012 02:04:34 UTC+1, Jo a écrit :
NOTE: this is a draft document, just because there are some things here
that I'd really like to improve. Please let me know if you have a better
way to do these things. There's also a few issues with Puppet Dashboard
that appear to be bugs that need either improved documentation or changes
to their source RPM to fix. I'd love to see better ways to fix this.
I am attempting to document how one can take an EL5 system (like CentOS
5.x) to Ruby 1.8.7 and meets the minimum requirements for Puppet Dashboard.
There are many reasons for this:
1. PuppetLabs blames many server-side issues on Ruby 1.8.5's known memory
problems. They have indicated that only Ruby 1.8.7 is supportable.
2. Dashboard requires Ruby 1.8.7
3. Foreman requires Ruby 1.8.7
Requirements:
EL5 system with rpmbuild utilities and ~/rpmbuild structure set up as
documented nearly everywhere. If you use different paths, adjust as
necessary for the remainder of the document.
Step 1: Upgrade Ruby
I have seen recommendations for Koran's Ruby build, but it didn't build on
a fairly stock EL5 system, and included a bunch of unrelated-to-puppet Tk
and JP patches. I found a much simpler spec file that appears to build
properly on EL5 that uses a significantly higher patch level of Ruby, fixes
the autoconf problems. It was trivial to review the few patches on this.
wget http://rbel.frameos.org/stable/el5/SRPMS/ruby-1.8.7.352-5.el5.src.rpm
rpm -i ruby-1.8.7.352-5.el5.src.rpm
rpmbuild -ba ~/rpmbuild/SPECS/ruby.spec
For any of the nodes, you need only put this RPM in your repository and
have Puppet upgrade them. It just works ;-)
For the passenger server, you'll need to get the source RPM from stealth
monkeys. You don't need to change anything at all -- just build the SRC
rpm and it will adjust everything to use Ruby 1.8.7. Very simple.
wget
http://passenger.stealthymonkeys.com/SRPMS/rubygem-passenger-3.0.11-1.src.rpm
rpm -i rubygem-passenger-3.0.11-1.src.rpm
rpmbuild -ba ~/rpmbuild/SPECS/passenger.spec
Step 2: Dashboard Requirements
First you need to get the mysql drivers for Ruby. The EPEL version binds
against ruby 1.8.5, but you can compile their source RPM on your ruby-1.8.7
system and it will work great.
wget ${EPEL_MIRROR_OF_CHOICE}/5/SRPMS/ruby-mysql-2.7.3-1.el5.src.rpm
rpm -i ruby-mysql-2.7.3-1.el5.src.rpm
rpmbuild -ba ~/rpmbuild/SPECS/ruby-mysql.spec
Next thing is that Puppet Dashboard requires a newer version of Ruby Gems,
but it doesn't tell you this. Instead it just barfs weird error messages.
They need to rewrite their Rakefile to explicitly define the minimum
versions.
Thankfully, upgrading gems is very easy.
wget
http://rbel.frameos.org/stable/el5/SRPMS/rubygems-1.8.10-1.el5.src.rpm
rpm -i rubygems-1.8.10-1.el5.src.rpm
rpmbuild -ba ~/rpmbuild/SPECS/rubygems.spec
Unfortunately, I never found a simple way to build RPMs for the three gems
you need. I'd like to fix this next part of the HOWTO in the near future.
For now, the easiest way to get the minimum requirements installed is to
run the following commands.
gem install rake
gem install rdoc
gem install rack -v 1.1.2
You'll observe that we installed a very specific version of Rack. The
reason for this is that Puppet Dashboard includes rack 1.1.2 within the
package, but the default Rakefile doesn't load it -- so it wants you to
have Rack in your normal gems library too. However if the version doesn't
match the same version included in the frozen vendor directory, it
complains about that and barfs. I consider this a bug in the dashboard
packaging: https://projects.puppetlabs.com/issues/11669
However, if you install 1.1.2 and nothing newer, it will work just fine.
Step 3: Install Dashboard
For unknown reasons to me, the source RPM for dashboard can't be extracted
on EL5 unless you pass --nomd5 --nosignature. The good news is that the
source RPM for EL6 compiles without any changes on EL5.
wget
http://yum.puppetlabs.com/el/6/products/SRPMS/puppet-dashboard-1.2.4-1.el6.src.rpm
rpm --nomd5 --nosignature -i puppet-dashboard-1.2.4-1.el6.src.rpm
rpmbuild -ba rpmbuild/SPECS/puppet-dashboard.spec
That's it! You now have puppet dashboard installed with all dependancies.
You can then follow the standard documentation from puppet labs at
http://docs.puppetlabs.com/guides/installing_dashboard.html#installation
Skip the first two #1 bullets and the first #2 bullet and start with the
second #2.
One problem I found was that when I tried to run it under
Passenger/Apache, I was told that it couldn't read the config.ru file. I
had to do the following to fix this:
cd /usr/share/puppet-dashboard
ln ./vendor/rails/railties/dispatches/config.ru config.ru
This is already tracked in https://projects.puppetlabs.com/users/3472
This is working great
[Puppet Users] Re: Please send me your puppet formatting puzzles...
On Thursday, July 26, 2012 10:11:58 AM UTC-5, Henrik Lindberg wrote: Hi, I have been working on a new puppet code formatter for Geppetto for some time, and it is now starting to work quite well. The plan is to release it in Geppetto 3.0. Sounds promising. If you want to, you can help by sending formatting puzzles - i.e. given input x, produce formatted result y. I am esp. looking for code where it is impossible to follow the style guide - long input, use of comments in funny places, etc. Long input is a big one for me. All other comments, or requests regarding formatting are also very welcome. Respond in any way you like although logged issues at https://github.com/cloudsmith/geppetto/issues are preferred. Is there a specific issue that should be used, or should one be filed for these puzzles? -Lee -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ExuKHCEHwVsJ. 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] why enterprise puppet does not use stored config and puppetdb
On Wed, Jul 25, 2012 at 4:30 PM, Hai Tao ehai...@gmail.com wrote: I just installed PE, and notice that it does not use either stored config nor puppetdb. It uses the activerecord to store facts in a mysql db. Why puppetlabs let us to use these but they do not use them in their enterprise version? There are packages for PuppetDB available for PE, and its documentation discusses the installation procedure for PE. It is currently delivered as an add-on for PE users, should they choose to use it. It's slated for inclusion in the main installer in the next major PE release. But certainly, PuppetDB is in active use at many, many sites, including our own infrastructure at Puppet Labs. deepak -- Deepak Giridharagopal / Puppet Labs -- 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] Re: can't get custom restart to work on a windows service
I modified the windows.rb and it seems to work well now. Many thanks!
Dan
On Tuesday, July 24, 2012 5:00:09 PM UTC-6, Dan McManus wrote:
Hi!
I am encountering something that I am not sure is a bug or not, so I
thought I'd post a question.
Running Puppet 2.7.18 on Windows 2003.
Basically, what I want to do is manage nsclient++ on windows. I am able to
manage the files just fine, but restarting doesn't work because of bug
13489 http://projects.puppetlabs.com/issues/13489. So I thought I might
circumvent it thusly:
service { NSClientpp:
ensure = running,
restart = 'c:/program files/nsclient++/scripts/restart.bat',
subscribe = File[c:/program files/nsclient++/nsc.ini],
}
and restart.bat is very simple:
sc stop nsclientpp
perl -e sleep 10
sc start nsclientpp
echo ran c:\restart.txt
it has world read and execute permissions, so it should run, but
restart.txt doesn't get created and the service still won't start on its
own.
My question is whether I am doing something wrong or is this is a bug?
Thanks
Dan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/FkklIRSsF64J.
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 updated yum packages without logging?
No, it updated all the PHP packages that were mentioned in the manifest. There
were about 20 listed, and no actual install happened.
I'm betting that it uses a default action of Latest, and just updated them all
behind the scenes. But I'd expect a logged action on that, as well as a
comment on the default behavior in the type reference.
( I'm not as worried about the docs - there has to be some default, and latest
isn't a terrible one. )
Matthew Barr
Technical Architect
E: mb...@snap-interactive.com
AIM: matthewbarr1
c: (646) 727-0535
On Jul 26, 2012, at 10:57 AM, Michael Stahnke wrote:
Did something else pull that package in as a dependency?
On Thu, Jul 26, 2012 at 7:37 AM, Matthew Barr
mb...@snap-interactive.com wrote:
We just saw an interesting scenario:
Puppet 2.7.18 updated packages on a RHEL 6.2 box to a newer version without
logging that fact.
We've already fixed our code so it doesn't happen again, but I'm wondering
if this is expected behavior or a bug.
* I presume the default ensure behavior on package is latest?The
type reference doesn't say that…
* For now, we've switched to using ensure = present… but I'd have liked the
logs to reflect that update.
Details, if necessary:
Now, we had the code as such:
package {
php:;
php-common:;
php-xml:;
php-domxml;:
}
and there was a single not present package to install (php-domxml).
Interestingly, the package was actually an older package name that's now
handled by a new package (php-xml), which meant that the actual message
logged was a failure.
Jul 25 14:09:43 web01 puppet-agent[1021]:
(/Stage[main]/Php/Package[php-domxml]/ensure) change from absent to present
failed: Could not find package php-domxml
This was the only package message logged, and yet we ended up with newer
versions.
Matthew Barr
Technical Architect
E: mb...@snap-interactive.com
AIM: matthewbarr1
c: (646) 727-0535
--
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.
--
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 updated yum packages without logging?
On Thursday, July 26, 2012 1:16:40 PM UTC-5, Matthew Barr wrote:
No, it updated all the PHP packages that were mentioned in the manifest.
There were about 20 listed, and no actual install happened.
I'm betting that it uses a default action of Latest, and just updated them
all behind the scenes. But I'd expect a logged action on that, as well as
a comment on the default behavior in the type reference.
( I'm not as worried about the docs - there has to be some default, and
latest isn't a terrible one. )
'latest' as a default is a bad idea IMO.. can easily lead to breakage if
things update on their own. But then again, I've always been one that
prefers to explicitly set things, even if it is the default.
Less confusion, or problems if defaults change.
Matthew Barr
Technical Architect
E: mb...@snap-interactive.com
AIM: matthewbarr1
c: (646) 727-0535
On Jul 26, 2012, at 10:57 AM, Michael Stahnke wrote:
Did something else pull that package in as a dependency?
On Thu, Jul 26, 2012 at 7:37 AM, Matthew Barr
mb...@snap-interactive.com wrote:
We just saw an interesting scenario:
Puppet 2.7.18 updated packages on a RHEL 6.2 box to a newer version without
logging that fact.
We've already fixed our code so it doesn't happen again, but I'm wondering
if this is expected behavior or a bug.
* I presume the default ensure behavior on package is latest?The
type reference doesn't say that…
* For now, we've switched to using ensure = present… but I'd have liked
the
logs to reflect that update.
Details, if necessary:
Now, we had the code as such:
package {
php:;
php-common:;
php-xml:;
php-domxml;:
}
and there was a single not present package to install (php-domxml).
Interestingly, the package was actually an older package name that's now
handled by a new package (php-xml), which meant that the actual message
logged was a failure.
Jul 25 14:09:43 web01 puppet-agent[1021]:
(/Stage[main]/Php/Package[php-domxml]/ensure) change from absent to present
failed: Could not find package php-domxml
This was the only package message logged, and yet we ended up with newer
versions.
Matthew Barr
Technical Architect
E: mb...@snap-interactive.com
AIM: matthewbarr1
c: (646) 727-0535
--
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.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/trm-55mAdQ0J.
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 and Ruby 1.8.7 for EL5 systems HOWTO (draft)
Sorry for the top posting.
If you look carefully you should find that this year red hat extend
the 5 and 6 lifetime to 10 year, without extended maintenance support.
But i agree that rhel 5 is not the best plattform for running foreman
or dashboard.
Regards
2012/1/6, Michael Stahnke stah...@puppetlabs.com:
Jo, thanks for this. I do most of the packaging for Puppet Labs (and
quite a bit of the ruby stuff in EPEL). I have a few comments in
line.I'd love to have this on our wiki too, so feel free to post
there as well.
One more thing to keep in mind is that EL5 only has about 2 years of
life left on it. It launched in 2007.
On Wed, Jan 4, 2012 at 5:04 PM, Jo Rhett jrh...@netconsonance.com wrote:
NOTE: this is a draft document, just because there are some things here
that
I'd really like to improve. Please let me know if you have a better way
to
do these things. There's also a few issues with Puppet Dashboard that
appear to be bugs that need either improved documentation or changes to
their source RPM to fix. I'd love to see better ways to fix this.
I am attempting to document how one can take an EL5 system (like CentOS
5.x)
to Ruby 1.8.7 and meets the minimum requirements for Puppet Dashboard.
There
are many reasons for this:
1. PuppetLabs blames many server-side issues on Ruby 1.8.5's known memory
problems. They have indicated that only Ruby 1.8.7 is supportable.
2. Dashboard requires Ruby 1.8.7
3. Foreman requires Ruby 1.8.7
Requirements:
EL5 system with rpmbuild utilities and ~/rpmbuild structure set up as
documented nearly everywhere. If you use different paths, adjust as
necessary for the remainder of the document.
You can install rpmdev-tools and run rpmdev-setuptree and it will
setup a ~/rpmbuild directory and proper building macros for your
system, etc.
Step 1: Upgrade Ruby
I have seen recommendations for Koran's Ruby build, but it didn't build on
a
fairly stock EL5 system, and included a bunch of unrelated-to-puppet Tk
and
JP patches. I found a much simpler spec file that appears to build
properly
on EL5 that uses a significantly higher patch level of Ruby, fixes the
autoconf problems. It was trivial to review the few patches on this.
The http://centos.karan.org/el5/ruby187/ are basically a drop-in
replacement for how the EL5 ruby stack worked, just upgraded to 1.8.7.
I imagine the trouble you had building is due to the method you used
building the packages. RPMs built by EPEL/Centos/RH/Puppetlabs are
built using mock. (http://fedoraproject.org/wiki/Projects/Mock).
Mock assumes a group of packages is installed prior to building. That
list of packages is
install bash bzip2 coreutils cpio curl cvs diffutils fedpkg findutils
gawk gcc gcc-c++ gnupg grep gzip info make patch redhat-release
redhat-release-server redhat-rpm-config rpm-build sed shadow-utils tar
unzip util-linux-ng which xz
If you have those installed, they should build cleanly.
wget http://rbel.frameos.org/stable/el5/SRPMS/ruby-1.8.7.352-5.el5.src.rpm
rpm -i ruby-1.8.7.352-5.el5.src.rpm
rpmbuild -ba ~/rpmbuild/SPECS/ruby.spec
Always nice to have more options for packages. I do kind of get
bothered that I get ruby-tcl bindings all the time :)
For any of the nodes, you need only put this RPM in your repository and
have
Puppet upgrade them. It just works ;-)
For the passenger server, you'll need to get the source RPM from stealth
monkeys. You don't need to change anything at all -- just build the SRC
rpm
and it will adjust everything to use Ruby 1.8.7. Very simple.
wget
http://passenger.stealthymonkeys.com/SRPMS/rubygem-passenger-3.0.11-1.src.rpm
rpm -i rubygem-passenger-3.0.11-1.src.rpm
rpmbuild -ba ~/rpmbuild/SPECS/passenger.spec
Step 2: Dashboard Requirements
First you need to get the mysql drivers for Ruby. The EPEL version binds
against ruby 1.8.5, but you can compile their source RPM on your
ruby-1.8.7
system and it will work great.
This might be able to be fixed in EPEL. Since it dymaically links
against ruby, I would think that having 1.8.5 or 1.8.7 would work.
Could you file a bug at bugzilla.redhat.com on that?
wget ${EPEL_MIRROR_OF_CHOICE}/5/SRPMS/ruby-mysql-2.7.3-1.el5.src.rpm
rpm -i ruby-mysql-2.7.3-1.el5.src.rpm
rpmbuild -ba ~/rpmbuild/SPECS/ruby-mysql.spec
Next thing is that Puppet Dashboard requires a newer version of Ruby Gems,
but it doesn't tell you this. Instead it just barfs weird error messages.
They need to rewrite their Rakefile to explicitly define the minimum
versions.
Really? We ship rubygems 1.3.7 in Puppet Enterprise and I haven't
seen any errors. There are a few deprecation warnings though I
believe. This might be a case of exact versions of several gems all
playing together properly. Our PE preview branch (to be released
later this month) uses:
Gems 1.3.7
Rake 0.8.7
Rack 1.1.3
Dashboard 1.2.4
Thankfully, upgrading gems is very easy.
wget
[Puppet Users] activeMQ client on the puppet server?
on the puppet server ( i have only one), should I install the activeMQ client or server? If client, does it mean I need to install activeMQ server on all my nodes? Thanks. Hai T. -- 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 updated yum packages without logging?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Matthew,
According to the source, defaultto is set to 'installed', of which
'present' is an alias.
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/package.rb
Which means no package updates should have occurred. As for why they
did and why nothing was logged .. that I don't know.
Regards,
Bill Fraser
System Administrator
Pythian
On 12-07-26 10:37 AM, Matthew Barr wrote:
We just saw an interesting scenario: Puppet 2.7.18 updated packages
on a RHEL 6.2 box to a newer version without logging that fact.
We've already fixed our code so it doesn't happen again, but I'm
wondering if this is expected behavior or a bug.
* I presume the default ensure behavior on package is latest?
The type reference doesn't say that…
* For now, we've switched to using ensure = present… but I'd have
liked the logs to reflect that update.
Details, if necessary:
Now, we had the code as such:
package { php:; php-common:; php-xml:; php-domxml;: } and there was
a single not present package to install (php-domxml).
Interestingly, the package was actually an older package name
that's now handled by a new package (php-xml), which meant that the
actual message logged was a failure.
Jul 25 14:09:43 web01 puppet-agent[1021]:
(/Stage[main]/Php/Package[php-domxml]/ensure) change from absent to
present failed: Could not find package php-domxml
This was the only package message logged, and yet we ended up with
newer versions.
Matthew Barr Technical Architect E: mb...@snap-interactive.com AIM:
matthewbarr1 c: (646) 727-0535
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlARkCUACgkQ5xgg9J6hpUt/qACg2oEH5x7qEb2X9YxFbYZh9i+G
Q6EAnRiwQY4bpqKc+SLA6XgUm7z/LJ/S
=8Sxe
-END PGP SIGNATURE-
--
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 and Ruby 1.8.7 for EL5 systems HOWTO (draft)
On Thu, Jul 26, 2012 at 9:40 PM, devzero2000 pinto.e...@gmail.com wrote:
Sorry for the top posting.
If you look carefully you should find that this year red hat extend
the 5 and 6 lifetime to 10 year, without extended maintenance support.
But i agree that rhel 5 is not the best plattform for running foreman
or dashboard.
I agree its probably not, but FYI we added a EL5 repo to foreman 1.0 that
includes ruby as well,
see -
http://theforeman.org/projects/foreman/wiki/RPM's_distribution_based_installationand
http://yum.theforeman.org/releases/1.0/el5/
Ohad
Regards
2012/1/6, Michael Stahnke stah...@puppetlabs.com:
Jo, thanks for this. I do most of the packaging for Puppet Labs (and
quite a bit of the ruby stuff in EPEL). I have a few comments in
line.I'd love to have this on our wiki too, so feel free to post
there as well.
One more thing to keep in mind is that EL5 only has about 2 years of
life left on it. It launched in 2007.
On Wed, Jan 4, 2012 at 5:04 PM, Jo Rhett jrh...@netconsonance.com
wrote:
NOTE: this is a draft document, just because there are some things here
that
I'd really like to improve. Please let me know if you have a better way
to
do these things. There's also a few issues with Puppet Dashboard that
appear to be bugs that need either improved documentation or changes to
their source RPM to fix. I'd love to see better ways to fix this.
I am attempting to document how one can take an EL5 system (like CentOS
5.x)
to Ruby 1.8.7 and meets the minimum requirements for Puppet Dashboard.
There
are many reasons for this:
1. PuppetLabs blames many server-side issues on Ruby 1.8.5's known
memory
problems. They have indicated that only Ruby 1.8.7 is supportable.
2. Dashboard requires Ruby 1.8.7
3. Foreman requires Ruby 1.8.7
Requirements:
EL5 system with rpmbuild utilities and ~/rpmbuild structure set up as
documented nearly everywhere. If you use different paths, adjust as
necessary for the remainder of the document.
You can install rpmdev-tools and run rpmdev-setuptree and it will
setup a ~/rpmbuild directory and proper building macros for your
system, etc.
Step 1: Upgrade Ruby
I have seen recommendations for Koran's Ruby build, but it didn't build
on
a
fairly stock EL5 system, and included a bunch of unrelated-to-puppet Tk
and
JP patches. I found a much simpler spec file that appears to build
properly
on EL5 that uses a significantly higher patch level of Ruby, fixes the
autoconf problems. It was trivial to review the few patches on this.
The http://centos.karan.org/el5/ruby187/ are basically a drop-in
replacement for how the EL5 ruby stack worked, just upgraded to 1.8.7.
I imagine the trouble you had building is due to the method you used
building the packages. RPMs built by EPEL/Centos/RH/Puppetlabs are
built using mock. (http://fedoraproject.org/wiki/Projects/Mock).
Mock assumes a group of packages is installed prior to building. That
list of packages is
install bash bzip2 coreutils cpio curl cvs diffutils fedpkg findutils
gawk gcc gcc-c++ gnupg grep gzip info make patch redhat-release
redhat-release-server redhat-rpm-config rpm-build sed shadow-utils tar
unzip util-linux-ng which xz
If you have those installed, they should build cleanly.
wget
http://rbel.frameos.org/stable/el5/SRPMS/ruby-1.8.7.352-5.el5.src.rpm
rpm -i ruby-1.8.7.352-5.el5.src.rpm
rpmbuild -ba ~/rpmbuild/SPECS/ruby.spec
Always nice to have more options for packages. I do kind of get
bothered that I get ruby-tcl bindings all the time :)
For any of the nodes, you need only put this RPM in your repository and
have
Puppet upgrade them. It just works ;-)
For the passenger server, you'll need to get the source RPM from stealth
monkeys. You don't need to change anything at all -- just build the SRC
rpm
and it will adjust everything to use Ruby 1.8.7. Very simple.
wget
http://passenger.stealthymonkeys.com/SRPMS/rubygem-passenger-3.0.11-1.src.rpm
rpm -i rubygem-passenger-3.0.11-1.src.rpm
rpmbuild -ba ~/rpmbuild/SPECS/passenger.spec
Step 2: Dashboard Requirements
First you need to get the mysql drivers for Ruby. The EPEL version binds
against ruby 1.8.5, but you can compile their source RPM on your
ruby-1.8.7
system and it will work great.
This might be able to be fixed in EPEL. Since it dymaically links
against ruby, I would think that having 1.8.5 or 1.8.7 would work.
Could you file a bug at bugzilla.redhat.com on that?
wget ${EPEL_MIRROR_OF_CHOICE}/5/SRPMS/ruby-mysql-2.7.3-1.el5.src.rpm
rpm -i ruby-mysql-2.7.3-1.el5.src.rpm
rpmbuild -ba ~/rpmbuild/SPECS/ruby-mysql.spec
Next thing is that Puppet Dashboard requires a newer version of Ruby
Gems,
but it doesn't tell you this. Instead it just barfs weird error
messages.
They need to rewrite their Rakefile to explicitly define the minimum
Re: [Puppet Users] Puppet updated yum packages without logging?
I can't reproduce this. I used sudo because it was out-of-date on my system.
[0] root@centos6-64 /tmp rpm -q sudo
sudo-1.7.4p5-9.el6_2.x86_64
[0] root@centos6-64 /tmp yum list available | grep sudo
sudo.x86_641.7.4p5-12.el6_3 updates
[0] root@centos6-64 /tmp puppet --version
2.7.12 (Puppet Enterprise 2.5.2)
[0] root@centos6-64 /tmp cat test.pp
package {
sudo:;
}
[0] root@centos6-64 /tmp puppet apply --verbose test.pp
info: Loading facts in
/opt/puppet/share/puppet/modules/stdlib/lib/facter/root_home.rb
info: Loading facts in
/opt/puppet/share/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
info: Loading facts in
/opt/puppet/share/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/root_home.rb
info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/facter_dot_d.rb
info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/puppet_vardir.rb
info: Applying configuration version '1343301257'
notice: Finished catalog run in 0.18 seconds
[0] root@centos6-64 /tmp rpm -q sudo
sudo-1.7.4p5-9.el6_2.x86_64
[0] root@centos6-64 /tmp yum list available | grep sudo
sudo.x86_641.7.4p5-12.el6_3 updates
So, as you can see, my sudo package didn't update.
On Thu, Jul 26, 2012 at 11:44 AM, Bill Fraser fra...@pythian.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Matthew,
According to the source, defaultto is set to 'installed', of which
'present' is an alias.
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/package.rb
Which means no package updates should have occurred. As for why they
did and why nothing was logged .. that I don't know.
Regards,
Bill Fraser
System Administrator
Pythian
On 12-07-26 10:37 AM, Matthew Barr wrote:
We just saw an interesting scenario: Puppet 2.7.18 updated packages
on a RHEL 6.2 box to a newer version without logging that fact.
We've already fixed our code so it doesn't happen again, but I'm
wondering if this is expected behavior or a bug.
* I presume the default ensure behavior on package is latest?
The type reference doesn't say that…
* For now, we've switched to using ensure = present… but I'd have
liked the logs to reflect that update.
Details, if necessary:
Now, we had the code as such:
package { php:; php-common:; php-xml:; php-domxml;: } and there was
a single not present package to install (php-domxml).
Interestingly, the package was actually an older package name
that's now handled by a new package (php-xml), which meant that the
actual message logged was a failure.
Jul 25 14:09:43 web01 puppet-agent[1021]:
(/Stage[main]/Php/Package[php-domxml]/ensure) change from absent to
present failed: Could not find package php-domxml
This was the only package message logged, and yet we ended up with
newer versions.
Matthew Barr Technical Architect E: mb...@snap-interactive.com AIM:
matthewbarr1 c: (646) 727-0535
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlARkCUACgkQ5xgg9J6hpUt/qACg2oEH5x7qEb2X9YxFbYZh9i+G
Q6EAnRiwQY4bpqKc+SLA6XgUm7z/LJ/S
=8Sxe
-END PGP SIGNATURE-
--
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] activeMQ client on the puppet server?
You only need activeMQ in one spot to do mcollective stuff. So, the Puppet Server is an acceptable place to do that. If you're not yet using mcollective, then you don't need ActiveMQ at all. Mike On Thu, Jul 26, 2012 at 11:41 AM, Hai Tao ehai...@gmail.com wrote: on the puppet server ( i have only one), should I install the activeMQ client or server? If client, does it mean I need to install activeMQ server on all my nodes? Thanks. Hai T. -- 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.
[Puppet Users] Re: Weird cannot reassign variable name on node error when I try to use standalone
On Thursday, July 26, 2012 6:23:39 AM UTC-7, jcbollinger wrote: Hmm. I just realized that you are using Puppet in apply mode rather than agent mode. The problem may simply be that puppet apply doesn't want to handle node declarations. I don't use Puppet in apply mode, so I'm not sure, but node declarations don't make much sense in that context. Nah, node declarations work great with apply mode. The use case is a little fuzzy, but let's say you're doing a whole standalone site w/ puppet apply being run out of cron. Node definitions would mean you still get the traditional benefit of only maintaining one codebase for many heterogeneous nodes, and then you just rsync the whole /etc/puppet directory around to every node. Every node would get a bunch of extraneous code it never uses, but assuming there's no sensitive info in it, you probably don't mind. (Apply mode can use an ENC too, come to think of it.) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/TomA2jZ6UVsJ. 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 updated yum packages without logging?
On Thursday, July 26, 2012 9:57:27 AM UTC-5, Michael Stanhke wrote: Did something else pull that package in as a dependency? That is what I'm inclined to think, Matthew's denial notwithstanding. It is at any rate exactly the behavior that would be expected if some other package were installed or updated that required newer versions of the packages in question. Puppet knows about and logs only the package it actually requests. Furthermore, it does not follow from the failure to install the one new package that no other packages were updated in that run. If yum performed dependency resolution successfully and download all the needed packages, then it would have started installs. The requested package will always be installed last, because it depends directly or indirectly on everything else. If one of the installs fails then yum will fail, but any packages that were successfully installed before the failure will remain installed. This is all a good argument for maintaining your own repositories. If you control the packages available for installation then you don't need to worry (as much) about unwanted updates. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/_6LkTpsE3wsJ. 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] Re: Please send me your puppet formatting puzzles...
I forgot to cross post my reply: On 2012-26-07 18:03, llow...@oreillyauto.com wrote: Is there a specific issue that should be used, or should one be filed for these puzzles? Please just file a new issue, it helps if you also label it with the tag formatter. Meanwhile, the approach on long input is to try to wrap long lines. If there are no wrappable positions, the long input is kept as is. I am currently looking at formatting comments, rewrapping text etc. Looking forward to some puzzles... - henrik On 2012-26-07 18:03, llow...@oreillyauto.com wrote: On Thursday, July 26, 2012 10:11:58 AM UTC-5, Henrik Lindberg wrote: Hi, I have been working on a new puppet code formatter for Geppetto for some time, and it is now starting to work quite well. The plan is to release it in Geppetto 3.0. Sounds promising. If you want to, you can help by sending formatting puzzles - i.e. given input x, produce formatted result y. I am esp. looking for code where it is impossible to follow the style guide - long input, use of comments in funny places, etc. Long input is a big one for me. All other comments, or requests regarding formatting are also very welcome. Respond in any way you like although logged issues at https://github.com/cloudsmith/geppetto/issues https://github.com/cloudsmith/geppetto/issues are preferred. Is there a specific issue that should be used, or should one be filed for these puzzles? -Lee -- 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: export a file from a node to another node
On Thursday, July 26, 2012 10:41:28 AM UTC-5, Nikolaos Hatzopoulos wrote: as far as I understand for files you need a unique title in my case /etc/mynodes.txt how you can export instead of a file a variable and let's say it has a unique title and it has as content a string can you do that? You can only export resources, not variables. You can, however, export resources of any type, including custom and defined types. I'm not quite following what you don't like about the approach I've selected so far, but most objectives of this kind can be realized by exporting and collecting resources of some type, if you really want or need to go through Puppet as the intermediary. The scp won't work because I am trying to setup the ssh keys with taking the key from a specific node and putting into the authorized_keys file of the other :) on the other hand I can make the scp for the root user.. but if you do that what's the point of using puppet (i have only linux nodes)? Not this, actually. Puppet's main purpose is to serve as a central authority and manager for the configuration of nodes under its purview. Copying data from one node to another is conflicts with central authority because it makes the source node the authority for the information copied. If you want Puppet only for this purpose, then you probably don't really want Puppet at all. A solution more in the Puppet style would be to generate all the keys on the master (possibly, but not necessarily, inside Puppet), and have Puppet distribute them to all parties that need them. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Y0BmPZIkL2cJ. 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] activeMQ client on the puppet server?
Yes, I am installing MCollective. So for MCollective, I do need to install MCollective client on the puppet server, while install the MCollective server on the nodes (clients), right? On Thu, Jul 26, 2012 at 12:25 PM, Michael Stahnke stah...@puppetlabs.com wrote: You only need activeMQ in one spot to do mcollective stuff. So, the Puppet Server is an acceptable place to do that. If you're not yet using mcollective, then you don't need ActiveMQ at all. Mike On Thu, Jul 26, 2012 at 11:41 AM, Hai Tao ehai...@gmail.com wrote: on the puppet server ( i have only one), should I install the activeMQ client or server? If client, does it mean I need to install activeMQ server on all my nodes? Thanks. Hai T. -- 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. -- Hai Tao -- 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] Re: librarian-puppet
We went with git super projects and submodules instead of librarian-puppet. Might want to look at using git for management of per puppet-module repositories as well. On Wednesday, July 25, 2012 7:37:10 AM UTC-7, llo...@oreillyauto.com wrote: I've heard this project mentioned a few times and I have found the projects site on github. Is there information available on how to setup the repos that it would pull from (layout etc)? The boxes I would be using this on do not have access to the Puppet Forge but this project looks like it would be useful in addressing somethings I've been trying to decide on how to handle for a while now. I know that as of yet there isn't a way to setup a true private forge, though some options are in the works (pulp, for example). Unfortunately, pulp is currently on officially supported on Fedora/RHEL based systems and YUM repos, though they are working on expanding the options. Any other suggestions or recommendations for getting started with this would be appreciated as well. Thanks. --Lee -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/7UlS4Gcb5-YJ. 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] Intermittent freeze on select when running standalone
And why I cannot find anyone else with the same issue. This sounds very similar, if not the same issue, that I have run into many times before. It happens during a simple puppet apply. I always run apply with --verbose, and since there is no output at all, I figure the command has just hung. Similarly, running strace on the process results in an infinite output of select. ctrl-c does not kill the process - I have to kill the PID from another terminal. I cannot reproduce this issue at will -- it seems to happen randomly. Thanks, Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- 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] activeMQ client on the puppet server?
MCollective server needs to be on all managed hosts including the puppet master. The client can be installed on any node that is required to issue the mco commands (usually the puppet master but can be elsewhere as well). Den On 27/07/2012, at 7:08, Hai Tao ehai...@gmail.com wrote: Yes, I am installing MCollective. So for MCollective, I do need to install MCollective client on the puppet server, while install the MCollective server on the nodes (clients), right? On Thu, Jul 26, 2012 at 12:25 PM, Michael Stahnke stah...@puppetlabs.com wrote: You only need activeMQ in one spot to do mcollective stuff. So, the Puppet Server is an acceptable place to do that. If you're not yet using mcollective, then you don't need ActiveMQ at all. Mike On Thu, Jul 26, 2012 at 11:41 AM, Hai Tao ehai...@gmail.com wrote: on the puppet server ( i have only one), should I install the activeMQ client or server? If client, does it mean I need to install activeMQ server on all my nodes? Thanks. Hai T. -- 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. -- Hai Tao -- 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] activeMQ client on the puppet server?
OK. when I issue a mco ping command, it will discover its own subnet only, or it can across subnets? Thanks. On Thu, Jul 26, 2012 at 2:52 PM, Denmat tu2bg...@gmail.com wrote: MCollective server needs to be on all managed hosts including the puppet master. The client can be installed on any node that is required to issue the mco commands (usually the puppet master but can be elsewhere as well). Den On 27/07/2012, at 7:08, Hai Tao ehai...@gmail.com wrote: Yes, I am installing MCollective. So for MCollective, I do need to install MCollective client on the puppet server, while install the MCollective server on the nodes (clients), right? On Thu, Jul 26, 2012 at 12:25 PM, Michael Stahnke stah...@puppetlabs.com wrote: You only need activeMQ in one spot to do mcollective stuff. So, the Puppet Server is an acceptable place to do that. If you're not yet using mcollective, then you don't need ActiveMQ at all. Mike On Thu, Jul 26, 2012 at 11:41 AM, Hai Tao ehai...@gmail.com wrote: on the puppet server ( i have only one), should I install the activeMQ client or server? If client, does it mean I need to install activeMQ server on all my nodes? Thanks. Hai T. -- 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. -- Hai Tao -- 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. -- Hai Tao -- 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] activeMQ client on the puppet server?
On Jul 26, 2012, at 6:50 PM, Hai Tao ehai...@gmail.com wrote: OK. when I issue a mco ping command, it will discover its own subnet only, or it can across subnets? Hai, I would recommend reading up on how MCollective/ActiveMQ works. There is documentation here: http://docs.puppetlabs.com/mcollective/ In particular pay attention to the stuff on the broadcast paradigm and the publish/subscribe model. -- Eric Shamow Professional Services http://puppetlabs.com/ (c)631.871.6441 -- 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] activeMQ client on the puppet server?
Thanks, Eric ! On Thu, Jul 26, 2012 at 3:57 PM, Eric Shamow e...@puppetlabs.com wrote: On Jul 26, 2012, at 6:50 PM, Hai Tao ehai...@gmail.com wrote: OK. when I issue a mco ping command, it will discover its own subnet only, or it can across subnets? Hai, I would recommend reading up on how MCollective/ActiveMQ works. There is documentation here: http://docs.puppetlabs.com/mcollective/ In particular pay attention to the stuff on the broadcast paradigm and the publish/subscribe model. -- Eric Shamow Professional Services http://puppetlabs.com/ (c)631.871.6441 -- 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. -- Hai Tao -- 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] how /etc/mcollective/facts.yaml be updated with facter
HI, I installed mcollective server on a node, but I do not know how the /etc/mcollective/facts.yaml can be updated with the facter. It looks to me that I need to manually update the file. Can someone advise how the puppet agent can connect to the mcollective on a node? Thanks. -- 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 /etc/mcollective/facts.yaml be updated with facter
- Original Message - From: Hai Tao ehai...@gmail.com To: puppet-users@googlegroups.com Sent: Friday, July 27, 2012 1:09:07 AM Subject: [Puppet Users] how /etc/mcollective/facts.yaml be updated with facter HI, I installed mcollective server on a node, but I do not know how the /etc/mcollective/facts.yaml can be updated with the facter. It looks to me that I need to manually update the file. This is the most popular way: http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML Can someone advise how the puppet agent can connect to the mcollective on a node? -- 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] can dashboard and foreman be used at the same time?
I have been wondering the same thing but I have started using puppetdb. Has anyone got foreman working with puppetdb? On 25 July 2012 07:44, llow...@oreillyauto.com llow...@oreillyauto.com wrote: On Tuesday, July 24, 2012 4:27:39 PM UTC-5, Hai wrote: can dashboard and foreman share the same database then? Yes, I have dashboard and foreman on my test Vm all set to use Puppet'd database. On Tue, Jul 24, 2012 at 11:46 AM, Ohad Levy ohadl...@gmail.com wrote: On Tue, Jul 24, 2012 at 9:28 PM, Hai Tao ehai...@gmail.com wrote: I wonder if I can use dashboard and foreman at the same time, and for the same puppet master? sure, just make sure you have both reports defined and that dashboard and foreman are running on different ports... Ohad Thanks. Hai T. -- 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. -- Hai Tao -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/r7E-mpYq1MsJ. 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.
[Puppet Users] where is live management?
why my open source puppet dashboard does not have the live management tab which shows in the PE dashboard? is there a way that I can set it up? otherwise why do I need to install and configure Mcollective? Thanks. H. T. -- 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] activeMQ client on the puppet server?
On 07/26/2012 11:52 PM, Denmat wrote: MCollective server needs to be on all managed hosts including the puppet master. The client can be installed on any node that is required to issue the mco commands (usually the puppet master but can be elsewhere as well). I have the following setup (names of the RPM packages): puppet-server: - puppetmaster - mcollective-client - rabbitmq-server nodes: - puppet (puppet client) - mcollective (this is mcollective server) So I guess you don't need mcollective server on the puppetmaster machine (if you don't want to run commands on that machine too). -- Jakov Sosic www.srce.unizg.hr -- 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 updated yum packages without logging?
On 07/26/2012 10:52 PM, jcbollinger wrote: On Thursday, July 26, 2012 9:57:27 AM UTC-5, Michael Stanhke wrote: Did something else pull that package in as a dependency? That is what I'm inclined to think, Matthew's denial notwithstanding. It is at any rate exactly the behavior that would be expected if some other package were installed or updated that required newer versions of the packages in question. Puppet knows about and logs only the package it actually requests. Furthermore, it does not follow from the failure to install the one new package that no other packages were updated in that run. If yum performed dependency resolution successfully and download all the needed packages, then it would have started installs. The requested package will always be installed last, because it depends directly or indirectly on everything else. If one of the installs fails then yum will fail, but any packages that were successfully installed before the failure will remain installed. This is all a good argument for maintaining your own repositories. If you control the packages available for installation then you don't need to worry (as much) about unwanted updates. Maybe /var/log/yum.log can tell the story - if there is a list of packages with prefix Updated: followed by the php-domxml with prefix Installed: then it seems quite obvious what happened. Also, Matthew should test the case on a development machine - install the set of packages of older version, and then manually try to run yum install php-domxml. It is enough that php-domxml requires package php to recursively upgrade every php package on the system... -- Jakov Sosic www.srce.unizg.hr -- 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 updated yum packages without logging?
On 07/26/2012 09:24 PM, Michael Stahnke wrote: I can't reproduce this. I used sudo because it was out-of-date on my system. Try to install php and all the modules pre-upgrade versions on some dev machine and then run yum install php-domxml and observe what happens. I bet it's the php-domxml that pulls latest php and in turn recursively pulls everything else as upgrade to satisfy the newest php. -- Jakov Sosic www.srce.unizg.hr -- 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.
