Re: [Puppet Users] Puppet, inventory, and single sources of truth.
On Thu, Oct 30, 2014 at 2:28 AM, Robin Lee Powell rlpow...@digitalkingdom.org wrote: On Wed, Oct 29, 2014 at 02:09:25AM -0700, Gavin Williams wrote: Sounds like The Foreman [1] might be a good option if you want to manage 'should', not 'is'... [1] http://theforeman.org/ *nod* Thanks, I should look at that again; it's been a while. Unfortunately our internal abstraction isn't host/VM/node based at all; it's based on sites (i.e. foo.company.com is a site, as is bar.company.com), which have one or more associated nodes. Foreman supports multiple Organizations and locations out of the box, especially since this is a common usage case. Ohad Having read https://docs.puppetlabs.com/puppet/latest/reference/subsystem_catalog_compilation.html and poking around a bit, I've had the following additional thoughts: 1. External Facts ( https://docs.puppetlabs.com/facter/latest/custom_facts.html#external-facts ) 2. generate() + stdlib's loadyaml() to just grab the values out of a bunch of on-disk files via a shell script or something 3. Mush all the values into one tree *in Hiera*. Currently all the values are in hiera but split up, so one node might see: sites: alice: premium: true And another might see: sites: bob: premium: false But certain parts of the code need to see: sites: alice: premium: true bob: premium: false I could simply de-hierachicalize (lol) all such information so that it's in one big blob in hiera somewhere. That gets ugly, though, just because it's one giant file; it's a lot easier on my users when each site is its own file. I wonder if there's a way to tell hiera Please load every file in this directory for every node? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20141030002856.GC6484%40stodi.digitalkingdom.org . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CACUhpZELirniW3%3DpRBMOCYB%2BP%2BhK4JYSUdEgp0v-gaAhYjMQxg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: puppetdb, foreman, one particular node has a problem
On Wed, Oct 16, 2013 at 11:07 AM, Steve Wray stevedw...@gmail.com wrote: It turned out that there was an update to the foreman package which completely broke Puppets ability to enroll new nodes. Call me old fashioned, I've been a Debian sysadmin for over 10 years, but on a 'stable' system an apt-get upgrade is not supposed to break things. Thats one of the things Debian is famous for. Just so happens my server is running Ubuntu server 'long term support' version and I expected something similar there. Would you mind sharing information about which version did you upgrade from - to ? we take releases very seriously (usually 4 RC with full packages) before rolling out an upgrade, I'm sorry it didn't work for you this time. Ohad -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] The Foreman: Query facts from ENC PuppetDB?
On Wed, Aug 28, 2013 at 9:13 PM, Stephen Price ste...@gmail.com wrote: Thanks! I'll check it out. I think eventually I can see using Foreman more for stuff like ENC and provisioning, but I wanted to proceed cautiously by just starting with reporting and fact pushing. For now, the example cron script works ok. if you turn on enc functionality, the enc script would actually upload the facts prior to query enc data (as facts might affect the enc output). Ohad On Wed, Aug 28, 2013 at 9:41 AM, Ellison Marks gty...@gmail.com wrote: There's a beta frontend for puppetdb floating around the list called puppetboard. It handles reports, as well as a few other things. It's pretty sweet, all things considered. https://groups.google.com/forum/#!searchin/puppet-users/puppetboard/puppet-users/PVbPY3z8uFI/5yFZgVIG5wEJ On Tuesday, August 27, 2013 10:45:55 PM UTC-7, Stephen Price wrote: Sorry, I meant I'm using Hiera as an ENC. I did see that PuppetDB has report storage, but without an easy way to use that data (short of creating my own interface utilizing queries to PuppetDB), it's not very useful yet. I figured Foreman would be a decent drop-in for reports. I got a suggestion from someone else to take a look at creating a custom facts terminus and have the master sending facts directly to both Foreman and PuppetDB, but that means designing my own REST interface. Kind of daunting. Thanks for the tip though. I'll poke around foreman-users for some ideas. On Tue, Aug 27, 2013 at 9:03 PM, Ken Barber k...@puppetlabs.com wrote: I've been using PuppetDB as an ENC for a while, So PuppetDB is not an ENC, do you mean Foreman? but I haven't really utilized it for stored configs or anything. I was mostly interested in replacing Dashboard's reporting capabilities, but PuppetDB doesn't yet do anything (that I can see) with reports. So PuppetDB has experimental report storage: http://docs.puppetlabs.com/**puppetdb/1.4/connect_puppet_** master.html#edit-puppetconfhttp://docs.puppetlabs.com/puppetdb/1.4/connect_puppet_master.html#edit-puppetconf So I'm currently looking into setting up a separate Foreman server. I saw the script mentioned in the manual that's meant to be run as a cron job on the master, which should push facts to the Foreman, but is there a way to do the reverse, and have the Foreman query the Master or PuppetDB directly for facts? So this is possibly not the correct forum to ask? If you don't get an answer, you might want to ask on foreman-users: https://groups.google.com/**forum/#!forum/foreman-usershttps://groups.google.com/forum/#!forum/foreman-users ken. -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/** topic/puppet-users/**I0KzcD3wl0s/unsubscribehttps://groups.google.com/d/topic/puppet-users/I0KzcD3wl0s/unsubscribe . To unsubscribe from this group and all its topics, send an email to puppet-users...@**googlegroups.com. To post to this group, send email to puppet...@googlegroups.com. Visit this group at http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- Stephen Price -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/I0KzcD3wl0s/unsubscribe. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- Stephen Price -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Problem retreiving catalog
On Thu, Apr 25, 2013 at 5:24 PM, gen...@allantgroup.com andyr...@gmail.com wrote: On Thursday, April 25, 2013 3:19:55 AM UTC-5, ohad wrote: On Thu, Apr 25, 2013 at 2:00 AM, gen...@allantgroup.com andyr7...@gmail.com wrote: I updated some of my gems, and I think it may be the reason I am getting the following error when the agents try to retrieve a catalog. err: Could not retrieve catalog from remote server: Error 400 on SERVER: The single-table inheritance mechanism failed to locate the subclass: 'Host::Managed'. This error is raised because the column 'type' is reserved for storing the class in case of inheritance. Please rename this column if you didn't intend it to be used for storing the inheritance class or overwrite Puppet::Rails::Host.**inheritance_column to use another column for that information. this looks like the development version of foreman, are you using it together with storeconfigs? Ohad Yes, it is the development version of foreman and yes I am using storeconfigs. Is there a solution to this, or should I downgrade foreman to stable? One of the upcoming changes in 1.2 is to no longer share the db with storeconfigs (as its being replaced in favor of puppetdb anyway)... therefore, if you want to use the latest version and 1.2 at the same time, you would need to dump the db into a new foreman db (or puppet). Ohad Thanks, Andy Ruby 1.8.7, I believe apache is using passenger 2.2.11. I tried 3.0.19, but then I get errors in the apache log about not finding files in the /usr/share/puppet/rack/**puppetmasterd/public, which AFAICT are application generated. Everything was working fine before updating the gems. I was updating the gems because I was trying to get foreman working again after updating it. I do not know much about ruby or passenger, so I could use some help figuring out how to fix this issue. At least puppet-dashboard is working, it just isn't getting any new reports due to the problems with puppet. Thanks, Andy -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@**googlegroups.com. To post to this group, send email to puppet...@googlegroups.com. Visit this group at http://groups.google.com/**group/puppet-users?hl=enhttp://groups.google.com/group/puppet-users?hl=en . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Problem retreiving catalog
On Thu, Apr 25, 2013 at 2:00 AM, gen...@allantgroup.com andyr...@gmail.com wrote: I updated some of my gems, and I think it may be the reason I am getting the following error when the agents try to retrieve a catalog. err: Could not retrieve catalog from remote server: Error 400 on SERVER: The single-table inheritance mechanism failed to locate the subclass: 'Host::Managed'. This error is raised because the column 'type' is reserved for storing the class in case of inheritance. Please rename this column if you didn't intend it to be used for storing the inheritance class or overwrite Puppet::Rails::Host.inheritance_column to use another column for that information. this looks like the development version of foreman, are you using it together with storeconfigs? Ohad Ruby 1.8.7, I believe apache is using passenger 2.2.11. I tried 3.0.19, but then I get errors in the apache log about not finding files in the /usr/share/puppet/rack/puppetmasterd/public, which AFAICT are application generated. Everything was working fine before updating the gems. I was updating the gems because I was trying to get foreman working again after updating it. I do not know much about ruby or passenger, so I could use some help figuring out how to fix this issue. At least puppet-dashboard is working, it just isn't getting any new reports due to the problems with puppet. Thanks, Andy -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] OS provisionning of physical server usinsg puppet ?
On Mon, Feb 4, 2013 at 5:59 PM, ml mldmld1...@gmail.com wrote: Hi all, I'm a newbie in puppet I read the documentation and according to me, puppet is a language to manage OS and to check compliance to OS template. I read that puppet enterprise can deploy Vmware vm template and Amazon EC2 VM. But it seem's that puppet core can't deploy physical server The only way I imagine is to build a pxe server, and images including puppet agent. Is it correct ? I'm looking for an open source tool supported tool by a company to deploy physical and VM servers, on Linux and Windows. Checkout http://theforeman.org Ohad Thank you ML. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] How to collect hostnames or host ips
On Tue, Jan 29, 2013 at 4:30 AM, Dusty Doris du...@doris.name wrote:
I'd like to be able to collect all the hostnames (fqdn) or ips of certain
hosts to be used in setting up firewall rules. I'd like to search for
hosts that have included a particular class, perhaps by simply setting a
tag when that resource is included.
eg:
node 'node1' {
include 'somewebclass'
}
class somewebclass {
tag 'web'
# other stuff
}
Then in another class, I'd like to find all my 'web' hosts and allow them
access in a firewall rule.
eg:
class somedbclass {
tag 'db'
iptables { allow db access:
proto = 'tcp',
dport = '3306'
source = Node | tag == 'web' |,
jump = 'ACCEPT'
}
}
So, ultimately, I'd need that Node | tag == 'web' | to be an array of
hostnames or ipaddresses.
This is just an example to try to explain what I am doing. Does anyone
know how to do this? Can I do this in puppet? Do I need to write my own
function to handle this? Or, can I use something like hiera or puppetdb to
do this?
Thanks for any tips.
if you use foreman, this is kind of trivial, see
http://blog.theforeman.org/2012/01/getting-foreman-search-results-into.html
Cheers,
Ohad
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Puppet dashboard not enabling inventory
On Mon, Jan 14, 2013 at 3:28 PM, GRANIER Bernard (MORPHO) bernard.gran...@morpho.com wrote: I think that a dashboard is a great things, I will look to foreman even if inventory seems missing in foreman. Not sure what you mean by that - we get plenty of inventory in foreman :) Ohad -- 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] Have Puppet *call* REST APIs
On Fri, Jan 4, 2013 at 4:22 PM, Rob Johnson r...@cloudera.com wrote: Hi Craig, Thanks for your reply. I'm looking to post requests to a server that configures properties of that server after standing it up. So, I would envision sending requests from puppet master in this case to one server. It would happen likely after a bunch of other installations occurred first (that's standard RPM deployment). So it's: 1) Install a bunch of software on numerous machines including server process on a specific machine. (simplified, there's more config I have to do here) 2) Start up the master server. 3) Configure the master server via REST API Posts. I mainly need to check the replies for return status I think. Don't need to process the requests too much. Does that make sense? I probably have to build some custom plugins or something to do this right? I was thinking about exec calls to curl or something, but that seems a little kludgy. Just remember once difference between exec and a puppet function, an exec happens on the client(agent) so you would need to allow access to all of your clients, a function runs on the server, however that happens during catalog run, so you dont really know what the client did, you would need to check the report from the client to know for sure. good luck, Ohad Thanks for any advice, it's much appreciated! Rob On Friday, January 4, 2013 5:02:16 AM UTC-6, Craig Dunn wrote: I hope this is just not my Google-fu lacking, but can you configure Puppet modules to make REST API calls inherently with Puppet? I'm talking about 3rd party REST APIs, not Puppet's API. I'm thinking of rolling my own plugin, but wondered if I'm missing something here. Can you provide a bit more information on what you're trying to do? If are you are trying to look up a value from a REST API call you could use Hiera with the http backend. Or are you trying to get Puppet to post data to a REST API when it runs? And if so do you want this to happen on the agent when the resource gets applied, or on the server during catalog compilation in the form of a function? Whether or not you are doing anything with the data returned from your call will make a difference here. Craig -- Craig Dunn Professional Services Puppet Labs Inc. http://www.puppetlabs.com -- 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/-/XP2goJEbl-UJ. 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 automate agent installation on nodes
On Fri, Jan 4, 2013 at 9:23 AM, Nilesh nilesh.chaudha...@gmail.com wrote: Thanks for the reply :) I am using vCenter as a provisioing engin . I will try this option and let you know ... You can try Foreman[1], which among of its features, it creates your vm, install its os and deploy puppet, later on it can monitor your puppet service and of course, tell puppet which classes to apply. cheers, Ohad [1] theforeman.org On Thursday, January 3, 2013 7:25:01 PM UTC+5:30, Ygor wrote: What do you use to provision ? I am still working with non-virtual servers and I use Cobbler to install / configure Puppet “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin Hobbes) - Original Message - From: Nilesh nilesh.c...@gmail.com To: puppet...@googlegroups.com Sent: Thursday, January 3, 2013 6:13:23 AM Subject: [Puppet Users] How to automate agent installation on nodes Hello Everyone Can anyone please let me know once I am done with VM provisioing with vmware how to allocate hostname and install puppet agent on that node automatically. Thanks :) -- 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/-/**35pXckQzOCoJhttps://groups.google.com/d/msg/puppet-users/-/35pXckQzOCoJ. To post to this group, send email to puppet...@googlegroups.com. To unsubscribe from this group, send email to puppet-users...@** googlegroups.com. For more options, visit this group at http://groups.google.com/** group/puppet-users?hl=enhttp://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/-/fROc8zavh8oJ. 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: Puppet cloud provisioning and VMware mac address allocation?
On Wed, Jan 2, 2013 at 2:58 PM, mbia...@edrans.com wrote: Hi Ohad, Yes, you are right, Foreman team is great with this community - I didn't meant otherwise. All I want is to explore options to fetch mac addresses assigned by vsphere. that's all. Anyone can shed some light from experience? You can get that kind of info directly from vsphere using its API, or using a ruby library such as rbvmomi or a higher level class such as fog. good luck, Ohad thanks all. On Sunday, December 30, 2012 5:58:32 PM UTC, mbi...@edrans.com wrote: Hi all, I've been working on fully automating the VM provisioning for some months now and one piece I could not resolve yet is to automate the dhcp/dns automation and just because I cannot obtain the VM mac address that vsphere/vcenter will allocate to a new vm. I am aware of 3rd party tools such as foreman, but in fact, I am concerned they do not follow puppet release cycle, or it's not their priority ;) I am sure that I am not the first one facing this bottleneck when ~200/300 VMs needs to be created. For theas reason I would like to know from those faced this issue and how they worked it out in an efficient manner. Thanks for sharing your thoughts! Best, Martin -- 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/-/MTgHLf2RdzkJ. 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 cloud provisioning and VMware mac address allocation?
On Sun, Dec 30, 2012 at 7:58 PM, mbia...@edrans.com wrote: Hi all, I've been working on fully automating the VM provisioning for some months now and one piece I could not resolve yet is to automate the dhcp/dns automation and just because I cannot obtain the VM mac address that vsphere/vcenter will allocate to a new vm. I am aware of 3rd party tools such as foreman, but in fact, I am concerned they do not follow puppet release cycle, or it's not their priority ;) Do you mind mentioning what do you mean? The foreman team care a lot about our users and puppet community in general I am sure that I am not the first one facing this bottleneck when ~200/300 VMs needs to be created. For theas reason I would like to know from those faced this issue and how they worked it out in an efficient manner. Thanks for sharing your thoughts! Best, Martin -- 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/-/Y5EdQWBTcbMJ. 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] Web interface to Facter information, system config reporting?
On Wed, Dec 19, 2012 at 9:27 PM, Forrie for...@gmail.com wrote: In our department, we recently bought an install of HP's SIM agent -- it's some hacky configuration reporting and management platform that also facilitates firmware updates, etc. I don't care for it. For one, it requires root logins, but it also has agents that report -- it also may have the ability to change the system. My boss is looking for information that is presented in a GUI and easily reportable. I'm thinking Facter is a good candidate here - we can tell it what version of software (SSH, etc), OS, etc. But, it's all command-line. I'm wondering if there is (or if someone is working on) a web-based GUI that can report these statistics (we don't need the overhead of something like puppet-dashboard). And for misc things, we can always write custom facts. Of course, this would only apply to systems that are running puppet. We have others that are not. I've seen some other hacks out there that do different types of reporting - if there's some better approach (open source), that would be great to know about. While its not limited to inventory only, Foreman [1] can generate pretty looking graphs, and show you all of your facts (including custom) and the ability to search and feed that to any external service via a simple api. You can disable most of foreman functionality, and simply get facts (and maybe puppet reports if you are interested in puppet state and not just inventory) without all of the other nice features (enc classifications, provisioning, vm, cloud etc). Hope this helps, Ohad [1] - http://theforeman.org Thanks. -- 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/-/7L0fdmA0VNIJ. 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] PE VMware VM deployment (localization problem)
On Thu, Dec 13, 2012 at 11:36 AM, Benoit BARTHELEMY benoit.barthel...@gmail.com wrote: Hi Guys ! I'm currently evaluating Puppet's cloud provisioner on vmWARE. I think I just ran into a silly localisation problem : [root@puppet ~]# puppet node_vmware list notice: Connecting ... notice: Connected to myVcenter as Puppet (API version 4.1) notice: Finding all Virtual Machines ... (Started at 10:30:37 AM) notice: Control will be returned to you in 10 minutes at 10:40 AM if locating is unfinished. Locating: 100% |oo| Time: 00:00:00 notice: Complete /Centres de données/myCluster/vm/Modeles/Linux/mymodel powerstate: poweredOff [...] template: true puppet node_vmware create --name=deploy_puppet --template=/Centres de données/myCluster/vm/Modeles/Linux/mymodel err: The --template option must be a path, for example /Datacenters/Solutions/vm/templates/puppet_template. err: Try 'puppet help node_vmware create' for usage I think the french translation of vCenter is messing up with fog, anyone experiencing the same issue ? yes, thats true, sadly fog does not support vcenter in a non English setup. Regards, Benoit BARTHELEMY -- 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/-/s5bGi3N_gOoJ. 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: Module class parameter override question
On Fri, Dec 7, 2012 at 9:37 PM, Ugo Bellavance u...@lubik.ca wrote:
I realize that maybe these modules have been built to be used only with
foreman. Is that a decent assumption? And if so, is there a simple apache
module somewhere? I only want to do the basics, check packages, service,
and create vhosts. I may be better writing my own...
Ideally we would like to share reuse the modules as much as possible,
they are not aimed to work just for the installer ( a lot of people use
them for a lot of different usage cases).
specifically, you tried to override a class that has no param class
attached to it.
saying that, we are going a process of parameteriziing all of our classes,
so if you would like to send a patch / pull request we would gladly accept.
Ohad
On Friday, December 7, 2012 11:49:19 AM UTC-5, Ugo Bellavance wrote:
Hi,
I am experimenting with foreman's apache module and there is this class
here:
class apache::service {
$http_service = $::operatingsystem ? {
/(Debian|Ubuntu)/ = 'apache2',
default = 'httpd',
}
service { $http_service:
ensure = running,
enable = true,
hasstatus = true,
hasrestart = true,
alias = 'httpd',
subscribe = Package['httpd']
}
exec { 'reload-apache':
command = /etc/init.d/${http_service} reload,
onlyif = '/usr/sbin/apachectl -t',
require = Service['httpd'],
refreshonly = true,
}
}
I want to apply this class to a specific host, but I want to override the
enable parameter so that it is false.
I tried this:
node 'server1' {
class { 'apache::service':
enable = false,}
}
But I always get this error:
Could not retrieve catalog from remote server: Error 400 on SERVER:
Invalid parameter enable at /etc/puppet/manifests/nodes/**nodes.pp:40
Any help would be appreciated.
Thanks,
Ugo
--
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/-/bLajZTaZ-McJ.
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 report aggregation
On Thu, Dec 6, 2012 at 11:29 AM, Luke Bigum luke.bi...@lmax.com wrote: On Wednesday, December 5, 2012 12:50:43 PM UTC, ohad wrote: You could use foreman for that? filtering the hosts via search should allow you to find the exact resources you are looking for? Ohad Hi Ohad, I haven't looked at The Foreman in a while but in my mind it's more like Puppet Dashboard - correct me if I'm wrong. What I'm aiming for is a tool that can aid change / release management where we run Puppet --noop across the estate, gather all the reports, then summarise what changes will be applied (resolv.conf changes on all hosts, fstab changes on 20 hosts, service X refreshes on Y hosts). You should be able to setup a search term that would match your requirement it might be best to use the API for that (http://bit.ly/Uq033I), since you would get all of your reports already parsed and you could cross reference the info with a puppet env, fact etc. Ohad I don't really want to be searching for explicit resources changing across hosts, it's the resources I don't know about that worry me ;-) Is the foreman worth a look in this case? -Luke On Tue, Dec 4, 2012 at 11:00 PM, Luke Bigum luke@lmax.com wrote: Hi all, Can anyone recommend any tools for Puppet report aggregation? I'm interested in something that can take a given set of Puppet reports and summarise to me what resources have changed across all hosts. If nothing exists I will look to write one myself. In that case, is Puppet report format 3 valid for Puppet 3.0? http://projects.puppetlabs.**com/projects/puppet/wiki/**Report_Format_3http://projects.puppetlabs.com/projects/puppet/wiki/Report_Format_3 Thanks, -Luke -- 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/-/**Fcx6zByYGPQJhttps://groups.google.com/d/msg/puppet-users/-/Fcx6zByYGPQJ . To post to this group, send email to puppet...@googlegroups.com. To unsubscribe from this group, send email to puppet-users...@** googlegroups.com. For more options, visit this group at http://groups.google.com/** group/puppet-users?hl=enhttp://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/-/zk_ospPVmYkJ. 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 report aggregation
You could use foreman for that? filtering the hosts via search should allow you to find the exact resources you are looking for? Ohad On Tue, Dec 4, 2012 at 11:00 PM, Luke Bigum luke.bi...@lmax.com wrote: Hi all, Can anyone recommend any tools for Puppet report aggregation? I'm interested in something that can take a given set of Puppet reports and summarise to me what resources have changed across all hosts. If nothing exists I will look to write one myself. In that case, is Puppet report format 3 valid for Puppet 3.0? http://projects.puppetlabs.com/projects/puppet/wiki/Report_Format_3 Thanks, -Luke -- 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/-/Fcx6zByYGPQJ. 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: Puppet version 2.7 or 3?
On Mon, Nov 19, 2012 at 1:16 PM, David Schmitt da...@dasz.at wrote: On Mon, 19 Nov 2012 11:21:34 +0100, David Schmitt da...@dasz.at wrote: bash-4.1$ rpm -qa | grep foreman foreman-1.0.1-4.20121022.el6.noarch foreman-postgresql-1.0.1-4.20121022.el6.noarch foreman-proxy-1.0.0-3.20121022.el6.noarch That I didn't notice, is that those are from 2012-10-22, which is not quite nightly. Seems like the repo at http://yum.theforeman.org/nightly/el6/x86_64/?C=M;O=D has stopped updating? Sorry about that, jmontleon fixed that. Best Regards, David -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet version 2.7 or 3?
On Thu, Nov 15, 2012 at 4:56 PM, llowder llowde...@gmail.com wrote: On Thursday, November 15, 2012 8:47:29 AM UTC-6, vioilly wrote: Hi, I am just rolling out a new puppet deployment. Which version should i go for, 2.7 or 3.1? I am looking to use the open source version. If you plan on using an ENC, specifically TheForeman, or a lot of modules from the Puppet Forge, you might want to start with 2.7 That being said, Foreman is very close to having Puppet 3 support working, and more and more modules on the Forge are being made 3.0 compatible every day. For the record, Puppet 3 support was added to foreman a couple of days ago. Ohad Puppet 2.7 is currently on 2.7.19 with 2.7.20 in RCs, and Puppet 3 is at 3.0.1, so it is still a little rough around the edges, but the fact that hiera is integrated and it has the databindings is one very nice feature of 3.0.x. It's also considerably faster. There are advantages and disadvantages to both, and I am sure others will weigh in as well, but hope this helps. Many thanks, Oli -- 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/-/UuxZtnjHn30J. 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: Foreman failing for db::migrate for puppet 3.0 with the following error :rake aborted! uninitialized constant HostObserver
On Thu, Oct 18, 2012 at 8:30 PM, Nishant Jain nishant.cit...@gmail.comwrote: I am using the following version of Ruby :ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] On Thursday, October 18, 2012 2:20:24 PM UTC-4, Nishant Jain wrote: Hello Everybody, I am trying to configure foreman for puppet 3.0. on centos 6.3 I have followed the instructions provided over here to install foreman:- http://theforeman.org/** projects/foreman/wiki/RPM's_**distribution_based_**installationhttp://theforeman.org/projects/foreman/wiki/RPM's_distribution_based_installation I have installed the following rpm: http://yum.theforeman.org/** development/el6/foreman-**release.rpmhttp://yum.theforeman.org/development/el6/foreman-release.rpm I have done the settings for the files in /etc/foreman as follows:- settings.yaml has the following contents: :puppet_server: puppet :unattended: true :puppetconfdir: /etc/puppet/puppet.conf :login: false :require_ssl: false database.yaml has the following contents: # SQLite version 3.x # gem install sqlite3 development: adapter: sqlite3 database: db/development.sqlite3 pool: 5 timeout: 5000 # Warning: The database defined as test will be erased and # re-generated from your development database when you run rake. # Do not set this db to the same as development or production. test: adapter: sqlite3 database: db/test.sqlite3 pool: 5 timeout: 5000 #production: # adapter: sqlite3 # database: db/production.sqlite3 # pool: 5 # timeout: 5000 production: adapter: mysql database: puppetdb username: puppetdb password: puppetdb host: 10.12.14.107 socket: /var/run/mysqld/mysqld.sock I am getting the following error when am trying to execute db:migrate command: su - foreman -s /bin/bash -c /usr/share/foreman/extras/** dbmigrate It fails with the following error: /usr/lib/ruby/gems/1.8/gems/**ruby_parser-2.3.1/lib/ruby_ **parser_extras.rb:10: warning: already initialized constant ENC_NONE /usr/lib/ruby/gems/1.8/gems/**ruby_parser-2.3.1/lib/ruby_**parser_extras.rb:11: warning: already initialized constant ENC_EUC /usr/lib/ruby/gems/1.8/gems/**ruby_parser-2.3.1/lib/ruby_**parser_extras.rb:12: warning: already initialized constant ENC_SJIS /usr/lib/ruby/gems/1.8/gems/**ruby_parser-2.3.1/lib/ruby_**parser_extras.rb:13: warning: already initialized constant ENC_UTF8 ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! uninitialized constant HostObserver When i tried to run it with trace option I get the following output: /usr/lib/ruby/gems/1.8/gems/**ruby_parser-2.3.1/lib/ruby_**parser_extras.rb:10: warning: already initialized constant ENC_NONE /usr/lib/ruby/gems/1.8/gems/**ruby_parser-2.3.1/lib/ruby_**parser_extras.rb:11: warning: already initialized constant ENC_EUC /usr/lib/ruby/gems/1.8/gems/**ruby_parser-2.3.1/lib/ruby_**parser_extras.rb:12: warning: already initialized constant ENC_SJIS /usr/lib/ruby/gems/1.8/gems/**ruby_parser-2.3.1/lib/ruby_**parser_extras.rb:13: warning: already initialized constant ENC_UTF8 ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! uninitialized constant HostObserver /usr/lib/ruby/gems/1.8/gems/**rake-0.9.2.2/lib/rake/ext/**module.rb:36:in `const_missing' /usr/lib/ruby/gems/1.8/gems/**activesupport-3.0.15/lib/** active_support/inflector/**methods.rb:113:in `constantize' /usr/lib/ruby/gems/1.8/gems/**activesupport-3.0.15/lib/** active_support/inflector/**methods.rb:112:in `each' /usr/lib/ruby/gems/1.8/gems/**activesupport-3.0.15/lib/** active_support/inflector/**methods.rb:112:in `constantize' /usr/lib/ruby/gems/1.8/gems/**activesupport-3.0.15/lib/** active_support/core_ext/**string/inflections.rb:43:in `constantize' /usr/lib/ruby/gems/1.8/gems/**activemodel-3.0.15/lib/active_**model/observing.rb:66:in `instantiate_observer' /usr/lib/ruby/gems/1.8/gems/**activemodel-3.0.15/lib/active_**model/observing.rb:39:in `instantiate_observers' /usr/lib/ruby/gems/1.8/gems/**activemodel-3.0.15/lib/active_**model/observing.rb:39:in `each' /usr/lib/ruby/gems/1.8/gems/**activemodel-3.0.15/lib/active_**model/observing.rb:39:in `instantiate_observers' /usr/lib/ruby/gems/1.8/gems/**activerecord-3.0.15/lib/** active_record/railtie.rb:83 /usr/lib/ruby/gems/1.8/gems/**activesupport-3.0.15/lib/** active_support/lazy_load_**hooks.rb:36:in `instance_eval'
Re: [Puppet Users] Static IP assignment
On Wed, Oct 17, 2012 at 5:02 PM, Matthew Burgess matthew.2.burg...@gmail.com wrote: On Wed, Oct 17, 2012 at 3:49 PM, GordonJB g.bonth...@gmail.com wrote: So I take it that when the new VM announces itself to the network, it will go off to the DHCP server and pick a static IP if there is one defined already for it's MAC address in a config file somewhere? Yes, that's correct. You can also set up a generic pool of addresses that a VM may get one from if you don't know its MAC address, but then you're not guaranteed to get the same IP address every time. The problem I encountered with VMWare VMs was that the MAC address wasn't generated until the VM was first powered on, so configuring DHCP ahead of time wasn't possible. As we didn't have any automated provisioning set up, the process was to do an initial boot and interrupt the boot process fairly quickly and power the VM off. Then I'd grab the MAC address from VSphere and pop it into the DHCP server's config. just FYI - Foreman creates the vm, then fetch the vm new mac, create a dhcp entry with that mac, and at the end powers on the vm. Ohad Is there a way to have a MAC address/IP pairing generated if one does not exist? I think the approach I'd take with this is to have a fairly small pool of addresses used for temporary IPs while a box is being provisioned. Once the box is up, you could have another puppet module that would figure out, using some other policy (potentially as simple as doing a DNS lookup on your VM's hostname), what the IP address of the box should be, find the MAC address of the NIC (exposed by facter), then put that in to the DHCP server's config. Automated provisioning solutions such as Foreman or Razor (http://puppetlabs.com/blog/puppet-razor-module/) may have better/other ways of doing it, but that would be my initial approach. That Razor page also links to Puppetlabs' own DHCP module (https://github.com/puppetlabs/puppetlabs-dhcp), so I'd be prone to try that for your DHCP config needs first, before looking at modules on the Forge. Regards, Matt. -- 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] RHEL Kickstart and Puppet certificates
On Wed, Sep 12, 2012 at 12:51 PM, Ano nym tuz1...@gmail.com wrote: Hello everybody, we´re using Red Hat Kickstarts for some systems. On every new kickstart we´ve to delete the client certificate first on the master. Ist there a best practise to renew the certificate or delete it remotely on the master? if you use something like Foreman [1] it can do it automatically for you. Ohad [1] http://theforeman.org kind regards, Ano -- 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/-/6U_6f-jW734J. 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: RHEL 6 and ActiveRecord issues
On Tue, Sep 11, 2012 at 12:40 AM, Avishai Ish-Shalom avis...@fewbytes.comwrote: We have puppet master running on CentOS 6.3; you need: activerecord 3.1.x, rails 3.1.x (we are using 3.1.8) storeconfigs is using activerecord backend with mysql adapter - do not use the mysql2 adapter why not? afaik, rails 3.x recommends using mysql2 adapter. . On Tuesday, May 1, 2012 9:57:14 PM UTC+3, Jeff Chapin wrote: All, I am trying to install puppet master version 2.7.13 on Red Hat Enterprise Linux 6, and utilize stored configs. I followed the guide here: http://projects.puppetlabs.** com/projects/1/wiki/Using_**Stored_Configurationhttp://projects.puppetlabs.com/projects/1/wiki/Using_Stored_Configuration When I run puppet --noop on one of the clients, I get the following error: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload active_record: uninitialized constant ActiveRecord warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Googling this error has a smattering of hits, including one that recommends using the 3.0.11 version of the Active Record gem, but I get the same error. I have installed both the 3.2.3 and 3.0.11 versions of the ActiveRecord gem (3.0.11 was recomended here: https://groups.google.com/**group/puppet-users/browse_** thread/thread/55f29e9454ad5675https://groups.google.com/group/puppet-users/browse_thread/thread/55f29e9454ad5675 **) This error occurs regardless of the DB backend I tie to. I have tried both the postgres and mysql documentation. # ruby --version ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] # puppet --version 2.7.13 # puppetmasterd --version 2.7.13 I have searched the puppetlabs issue tracker and found a possibly related issue:Debian Squeeze package puppetmaster: Could not autoload active_record: uninitialized constant ActiveRecord(http:// projects.puppetlabs.com/**issues/14080http://projects.puppetlabs.com/issues/14080). This indicates that I may be missing a related package or gem -- but I don't even know where to start tracking down the missing package. On IRC it has been suggested that I install rubygem-activerecord, but this does not appear to be in the EPEL repo -- Haus on IRC found a 2.3.8 version of this package that I installed to test, but I get the same error. I managed to get a different error briefly, when I was running multiple versions of activerecord, activeresource and activesupport -- installed through a mix of gem and yum. Deleting the non-yum versions returned me to the existing error, so I am chalking that up as a fluke at this time. Any help would be appreciated. Jeff -- 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/-/aU1B9g6Ft68J. 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: Configuring hosts with data from other hosts
On Sun, Aug 19, 2012 at 10:31 AM, treydock treyd...@gmail.com wrote: Ive struggled with the same problem of distributing variables and other generated data amongst hosts. For external resources Ive found a great use in configuring a BackupPC server. Each node builds their backup configuration file with tag 'backuppc_server_conf' and the server retrieves all the generated files with that tag. What I havent been unable to solve, is making each nodes hiera values accessable to each other. My hierarchy is $fqdn-common. The very crude workaround Ive used is in a module, query foreman for all fqdn's. Then pass that to a define that 'redefines' fqdn variable before calling hiera. Is there alternatively a way to query resources like all mysql::db types? I would like to just get all the mysql::db instances on a given node so other nodes could use that data. This could be another way to configure backuppc or generate monitoring checks. not sure if you already sorted that out or not, but thats the idea behind the search function that queries foreman, see http://blog.theforeman.org/2012/01/getting-foreman-search-results-into.html Ohad - Trey -- 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/-/5a1FTfRCFSsJ. 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: Automatic cleanup of client certificate ?
On Thu, Aug 16, 2012 at 10:42 AM, jerome jerome.steunenb...@gmail.comwrote: Hello, Thanks a lot for your input. Steve's solution is not possible in my environment because I do not have the previous client cert on reinstallation. Nan's solution seems to work fine in my context: On the server: /etc/puppet/autosign.conf: *.mydomain On the client:/etc/puppet/puppet.conf [agent] certname=mydesktop-201208160928.mydomain # rm -rf /var/lib/puppet/ssl # puppet agent --test This is generated at install time of course. The cert is automatically signed. It works fine if you just change the certname again and relaunch the agent. The nice side-effect is that I can have a cleanup script on the server that does a puppet cert clean for all mydesktop-*.mydomain except the most recent one. If you are interested, you could also use foreman, which would deploy your systems and automatically clean up the certs for you. Ohad Thanks, Jerome On Wednesday, August 15, 2012 2:53:59 PM UTC+2, jerome wrote: Hello, I'm new to Puppet and evaluating it against Cfengine and Chef for the management of multiple thousands of Ubuntu desktops. The desktops can be reinstalled at any time by technical site operators and they may or may not change the computer name. This happens fairly often and if the name stays the same, I get: err: Could not request certificate: The certificate retrieved from the master does not match the agent's private key because the desktop's SSL certificate changes when the desktop is rebuilt. To solve this problem I need to go on the server and do a: puppet cert clean fqdn of client But this is not practical in an environment where many computers can be reinstalled at any time. Is there a solution to this ? Can the agent tell the master to clean the key for its hostname ? I do not have this issue with cfengine, because the identifier is simply the MD5 of the certificate, not the hostname. I just need to cleanup the list of unused certificates on the server side every once in a while. Thanks, Jerome -- 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/-/d_BB73QJ0J0J. 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] Ruby program example to post to The Foreman
On Wed, Aug 15, 2012 at 4:11 PM, wernerbahlke werner.bah...@gmail.comwrote: Hi, I want to use The Foreman to pass variables between nodes. Does somebody have an example of a Ruby parser which does POSTs to The Foreman and can be used in my manifests?. With the exception of a Perl example I have only seen examples for GET operations, for example foreman.rb. I will start with foreman.rb and modify it but any hints would be very helpful. We are writing full ruby binding for foreman 1.1, have a look at https://github.com/theforeman/foreman_api the binding are auto generated from the API documentation, so I'm guessing the binding in question are a bit out of date (you could generate them your self assuming you have a recent git version. saying all of that, we did not do the host object just yet. Ohad Thanks, Werner -- 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/-/c6MFTXmAZEEJ. 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] Foreman 1.0.1 Released
Hi All, I'm happy to release another version of foreman, this time, a bit less exciting. This is a maintenance release for 1.0 version, that contain only the following bugs fixes: Bug #1543: Imported host, could not edit host as domain was not set. Bug #1750: Editor adds a spare at line 1 character position 1 when editing an existing template Bug #1778: Provisioning Templates editor does not save Bug #1780: EPEL snippet broken Bug #1781: clone host can fail Bug #1783: Default template set generates incorrect snippet names if snippet name uses underscore Bug #1789: Parent hostgroup name is truncated when its sub-group is a sub-string of the parent hostgroup name Bug #1792: json output of groups gone with v1. Bug #1793: Better handle case when a domain has no DNS proxy set Have fun, Ohad -- 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] Installing phusion passenger with puppet
On Mon, Jul 30, 2012 at 11:18 AM, doug livesey biot...@gmail.com wrote: Hi -- all the docs I can seem to find are related to running puppet with passenger, but not installing it. Does anyone know of any recipes I can use to actually install passenger with my server's Ruby and Apache installs? Thanks, Sure, you can grab some manifests from here (wioks on both deb/rhel kind of systems) https://github.com/theforeman/foreman-installer Ohad 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. -- 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] 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] 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
[Puppet Users] Re: [foreman-users] Re: Foreman 1.0 released!
On Mon, Jul 23, 2012 at 9:23 PM, Clay clay...@gmail.com wrote: this is still development release not stable release? nope, thats a stable 1.0 release. Ohad -- You received this message because you are subscribed to the Google Groups Foreman users group. To view this discussion on the web visit https://groups.google.com/d/msg/foreman-users/-/4K8fEWOhwsIJ. To post to this group, send email to foreman-us...@googlegroups.com. To unsubscribe from this group, send email to foreman-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/foreman-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] Foreman 1.0 released!
Hello, I'm very excited and pleased to share the release of Foreman 1.0 Since the change log is quite extensive, I would simply refer you to the change log [1] and would highly suggest to read it if you are upgrading. About Foreman: Foreman is an opensource management tool, design to help you to manage your infrastructure. Foreman takes over provisioning(bare metal, virtual or in the cloud)[2], interfacing with puppet to configure your servers, and provides an easy to use UI / API to control and review your server state. I'm also very happy to see that Foreman users, contributes (thanks guys!!) and ecosystem is growing, that includes a mobile app [3] and a CLI that was contributed by our community. I'm assuming packages would be available shortly. have fun, Ohad [1] http://theforeman.org/projects/foreman/wiki/ReleaseNotes#Release-Notes-for-10 [2] http://theforeman.org/projects/foreman/wiki/Screencasts [3] http://www.remoteadmin.co -- 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 can I list classes available on the puppet master?
On Mon, Jul 16, 2012 at 2:57 PM, Kamil Winczek ka...@winczek.com wrote:
On 12 Jul 12 08:54 -0700, llow...@oreillyauto.com wrote:
Is there a way to get a list of all the classes available from the
puppet
master?
I have 2 goals for this - one is documentation in a human readable
form,
and the other is potentially importing that data into dashboard.
Hi,
How about simple:
find . -name '*.pp' -exec awk '/^class [a-zA-Z]/ {print $2}' {} \;
You can also use foreman Proxy [1] to get that info for you :)
Ohad
[1] - http://theforeman.org/projects/smart-proxy/wiki
[1]
?
--
Kamil Winczek, Gentoo Linux user, post no: 1443
GG:888677, M:kamil[at]winczek.com, JID:crs[at]jabster.pl
For a list of all the ways technology has failed to improve
the quality of life, please press three. - Alice Kahn
--
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: Any one interested attending a puppetcamp in Israel?
Adding a couple more public mailing lists just in case. On Sun, Jul 22, 2012 at 5:37 PM, Oded Ben-Ozer oded.beno...@gmail.comwrote: We are trying to see how much people are interested so please let me know if you want to attend and or I know someone else who wants to attend. From puppetlabs.com - Puppet is IT automation software that helps system administrators manage infrastructure throughout its lifecycle, from provisioning and configuration to patch management and compliance. Using Puppet, you can easily automate repetitive tasks, quickly deploy critical applications, and proactively manage change, scaling from 10s of servers to 1000s, on-premise or in the cloud. Some info on puppetcamp events in other locations : http://puppetlabs.com/community/puppet-camp/ Oded Ben Ozer -- 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] Remote site puppet infrastructure
On Wed, Jul 18, 2012 at 4:20 PM, Jake - USPS jacob.m.mcc...@usps.govwrote: I'm trying to figure out if there is a common/working setup that people are using to host puppet in remote sites. At first our setup was that we have several puppetmasters (PM) in site A and a couple in our smaller site B. In site A we are also hosting Foreman and our mysql DB for storeconfigs. site A and B are connected via a WAN that is fairly slow. With this setup the issue I ran into was a lot of puppet agent runs in site B would timeout. They connect to their PM in site B just fine, but then the site B PM needs to connect to the storeconfigs DB in site A. This connection usually takes too long. So we end up with about 50% error rate in site B while having a 0% error rate in site A. I've tried to address this by using async_storeconfigs which seemed to help a lot but ran into https://projects.puppetlabs.com/issues/12140 which was a dealbreaker. Something else I've tried is just having agents in site B use the PMs in site A (so no more PM in site B). This helps a lot, but we still get errors. The 50% error rate drops down to about 1% error rate. It seems the traffic from agent to PM is less then the traffic from PM to DB? Not only did the error rate go down, but config retrievals sped up. One thing I'm wondering is if there is a way to setup a mysql storeconfigs DB in site B to reduce latency. Either only nodes in site B will use storeconfigs in site B or maybe site A and B are 'clustered' somehow over WAN? I'm not very strong with mysql skills though so I'm not sure what all can be done with it to address the issues I'm facing ... So I was wondering does anyone else manage remote sites? Is there a way to do it while still maintaining a central storeconfigs DB and 'dashboard/ENC' (don't want to have 'login here to view these nodes, login there to view these other nodes)? Thanks for all comments! I think thats one of the known shortcoming of storeconfigs, and one of the main reasons I've never used them personally in the past. What is your usage case fore storeconfigs? I always found ways to avoid using it (e.g. by storing the data i need somewhere else). I had (job N-1) about 15 sites (each with PM's) working really nice, but without storeconfigs.. Ohad Jake -- 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/-/Wb3Mae8Kd3YJ. 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-server-3.0.0-0.1rc3.2 with foreman-1.0.0-0.4
On Wed, Jul 4, 2012 at 6:49 PM, pdpinfo pdp...@tiscali.it wrote: Hi all, just trying a lab with newest versions: - puppet-server: 3.0.0-0.1rc3.2 - passenger: 3.0.12-1 - foreman: 1.0.0-0.4 I hit problems with foreman 1.0 not able to work with Puppet 3.0. Foreman 1.0 worked correctly with puppet-server 2.7.17-1 (fresh-installed). Upgrading the package (from foreman-devel repo) to latest version, Foreman service fails with error: ... /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:278:in `convert': Error converting value for param 'hostcert': Error converting value for param 'certdir': Error converting value for param 'ssldir': Could not find value for $confdir (Puppet::Settings::InterpolationError) Any hints ? I'm guessing puppet internals changed a bit, mind opening an issue on foreman tracker ? as a work around, you could probably change lib/foreman/default_settings/loader.rb not to use Puppet settings.. Ohad Thank you -- 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/-/qQ6yvf73SvUJ. 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 node report
On Sat, Jun 30, 2012 at 5:35 AM, hai wu haiwu...@gmail.com wrote: Thanks Tim. The problem is if you have multiple puppetmaster servers with different Puppet[:reportdir] on different local drives, thus for each node report yaml file, you would have to go to each puppetmaster server to retrieve the latest report file for that node, which is not ideal, as the copy is already stored in puppet dashboard, the problem is puppet dashboard would purge the file right away after loading it into database, and there's no way to retrieve that via API. If you would consider using Foreman [1], there is a very simple api to consume that state, e.g. https://server/hosts/fqdn/reports/last A lot of people use that along side with monitoring tools (such as nagios) to generate alerts etc. cheers, Ohad On 6/29/12, Tim Mooney tim.moo...@ndsu.edu wrote: In regard to: [Puppet Users] puppet node report, hai wu said (at 3:04am on...: Is there a way to download latest node report log from puppet dashboard? There's a way to do just about anything, but before you write some complicated web screen-scraping code to get the report from the web interface of dashboard, consider just enabling additional report backends and instead pulling the data from there. There was a very good blog post about when puppet reports a few weeks ago, check it out for more information on other reporting backends that are available and how you might go about developing your own (perhaps one for a database). See http://puppetlabs.com/blog/when-puppet-reports-part-1/ Note also there's a part 2 that you'll want to check out. The most straightforward method would probably be to enable the yaml backend and just pull the data from there. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 -- 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 node report
On Sat, Jun 30, 2012 at 9:35 AM, Ohad Levy ohadl...@gmail.com wrote: On Sat, Jun 30, 2012 at 5:35 AM, hai wu haiwu...@gmail.com wrote: Thanks Tim. The problem is if you have multiple puppetmaster servers with different Puppet[:reportdir] on different local drives, thus for each node report yaml file, you would have to go to each puppetmaster server to retrieve the latest report file for that node, which is not ideal, as the copy is already stored in puppet dashboard, the problem is puppet dashboard would purge the file right away after loading it into database, and there's no way to retrieve that via API. If you would consider using Foreman [1], there is a very simple api to consume that state, e.g. and of course, [1] is http://theforeman.org https://server/hosts/fqdn/reports/last A lot of people use that along side with monitoring tools (such as nagios) to generate alerts etc. cheers, Ohad On 6/29/12, Tim Mooney tim.moo...@ndsu.edu wrote: In regard to: [Puppet Users] puppet node report, hai wu said (at 3:04am on...: Is there a way to download latest node report log from puppet dashboard? There's a way to do just about anything, but before you write some complicated web screen-scraping code to get the report from the web interface of dashboard, consider just enabling additional report backends and instead pulling the data from there. There was a very good blog post about when puppet reports a few weeks ago, check it out for more information on other reporting backends that are available and how you might go about developing your own (perhaps one for a database). See http://puppetlabs.com/blog/when-puppet-reports-part-1/ Note also there's a part 2 that you'll want to check out. The most straightforward method would probably be to enable the yaml backend and just pull the data from there. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 -- 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 node report
On Sat, Jun 30, 2012 at 11:42 PM, hai wu haiwu...@gmail.com wrote: This is good to know. It seems foreman has its own report plugin script (foreman.rb), so it should not be a problem if I use both at the same time for reporting purposes. Puppet dashboard uses reporturl, as long as foreman would keep its current plugin (reports = foreman), there should be no conflict of using both, correct? It seems foreman has a new feature using reporturl, I won't be able to use that as reporturl is currently pointing to puppet dashboard .. yeah, it doesn't really matter, you can use either of them regardless. Ohad On 6/30/12, Ohad Levy ohadl...@gmail.com wrote: On Sat, Jun 30, 2012 at 5:35 AM, hai wu haiwu...@gmail.com wrote: Thanks Tim. The problem is if you have multiple puppetmaster servers with different Puppet[:reportdir] on different local drives, thus for each node report yaml file, you would have to go to each puppetmaster server to retrieve the latest report file for that node, which is not ideal, as the copy is already stored in puppet dashboard, the problem is puppet dashboard would purge the file right away after loading it into database, and there's no way to retrieve that via API. If you would consider using Foreman [1], there is a very simple api to consume that state, e.g. https://server/hosts/fqdn/reports/last A lot of people use that along side with monitoring tools (such as nagios) to generate alerts etc. cheers, Ohad On 6/29/12, Tim Mooney tim.moo...@ndsu.edu wrote: In regard to: [Puppet Users] puppet node report, hai wu said (at 3:04am on...: Is there a way to download latest node report log from puppet dashboard? There's a way to do just about anything, but before you write some complicated web screen-scraping code to get the report from the web interface of dashboard, consider just enabling additional report backends and instead pulling the data from there. There was a very good blog post about when puppet reports a few weeks ago, check it out for more information on other reporting backends that are available and how you might go about developing your own (perhaps one for a database). See http://puppetlabs.com/blog/when-puppet-reports-part-1/ Note also there's a part 2 that you'll want to check out. The most straightforward method would probably be to enable the yaml backend and just pull the data from there. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 -- 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. -- 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] Extending Puppet using Rubygems
On Sun, Jun 24, 2012 at 3:38 AM, Kelsey Hightower kel...@puppetlabs.comwrote: There is a pending pull request that adds the ability for Puppet to load Faces, parser functions, and report processors installed via Rubygems. https://github.com/puppetlabs/puppet/pull/873 This means in addition to extending Puppet via pluginsync you would be able to simply do something like this: gem install puppetlabs-cloud-provisioner That would bring in all the gem dependancies and be ready for use without restarting Puppet. For more examples take a look at this ticket: http://projects.puppetlabs.com/issues/7788 I would really love to get some feedback around this, and if you like it, add your vote to the ticket. +1, esp as if you use pluginsync on clients and master you end up pulling the same content (even if its only required on the master) to the clients. ohad Thanks. -- 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/-/dfuw73cfR9AJ. 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 and Ruby 1.9
On Mon, Jun 18, 2012 at 10:27 PM, Kinzel, David david.kin...@encana.comwrote: On Mon, Jun 18, 2012 at 10:02:10PM +0300, Ohad Levy wrote: On Mon, Jun 18, 2012 at 9:32 PM, Forrie for...@gmail.com wrote: What is the status of compatibility with Puppet 2.7.16+ and Ruby 1.9? I searched through this group and found some older posts. I am not certain what the core issues are (and there's probably a PuppetLabs page for it, I bet). afair, there is an issue with ssl requests on fedora 17 which is ruby 1.93. The certificate verify issue was just recently fixed in puppet. Do you know which version of puppet solves the issue? thanks, Ohad We've had no show-stoppers with an fairly modern puppet 2.7.x and ruby 1.9 in our environment. Ohad This email communication and any files transmitted with it may contain confidential and or proprietary information and is provided for the use of the intended recipient only. Any review, retransmission or dissemination of this information by anyone other than the intended recipient is prohibited. If you receive this email in error, please contact the sender and delete this communication and any copies immediately. Thank you. http://www.encana.com -- 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 and Ruby 1.9
On Tue, Jun 19, 2012 at 5:37 PM, Kinzel, David david.kin...@encana.comwrote: From: puppet-users@googlegroups.com [mailto: puppet-users@googlegroups.com] On Behalf Of Ohad Levy Sent: Tuesday, June 19, 2012 8:13 AM To: puppet-users@googlegroups.com Subject: Re: [Puppet Users] Puppet and Ruby 1.9 Do you know which version of puppet solves the issue? thanks, Ohad 2.7.16 should be good: https://projects.puppetlabs.com/issues/8858 hmm.. it looks like https://projects.puppetlabs.com/issues/9084 which is targeted for puppet 3.x Ohad This email communication and any files transmitted with it may contain confidential and or proprietary information and is provided for the use of the intended recipient only. Any review, retransmission or dissemination of this information by anyone other than the intended recipient is prohibited. If you receive this email in error, please contact the sender and delete this communication and any copies immediately. Thank you. http://www.encana.com -- 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 and Ruby 1.9
On Mon, Jun 18, 2012 at 9:32 PM, Forrie for...@gmail.com wrote: What is the status of compatibility with Puppet 2.7.16+ and Ruby 1.9? I searched through this group and found some older posts. I am not certain what the core issues are (and there's probably a PuppetLabs page for it, I bet). afair, there is an issue with ssl requests on fedora 17 which is ruby 1.93. Ohad 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. -- 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] Get host deployment status report with REST
On Mon, May 28, 2012 at 3:10 PM, Juan A. S. oke...@gmail.com wrote:
Hi
Is it possible to get the (last) deployment host report (or the list of
reports) for a specific node? I need to access it using REST, to know if
the deployment was succesful, and if not, the list of messages, like in the
dashboard...
If so, how would be the ACL? Now I have this, to allow the clients submit
their reports:
# allow all nodes to store their reports
path /report
method save
allow *
I'm not 100% if its not possible with the latest version of puppet, but
its possible using foreman, something like:
curl -s -u admin:password https://foreman/hosts/certname/reports/last -k
-H 'Accept:application/json' |prettify_json.rb
{
report: {
id: 396001,
summary: Modified,
status: {
applied: 1,
skipped: 0,
failed_restarts: 0,
restarted: 0,
failed: 0
},
host: certname,
logs: [
{
log: {
sources: {
source: /Stage[main]/Ntp::Service/Service[ntpd]/ensure
},
messages: {
message: ensure changed 'stopped' to 'running'
}
}
},
{
log: {
sources: {
source: Puppet
},
messages: {
message: Finished catalog run in 1.81 seconds
}
}
}
],
reported_at: 2012-05-28T11:07:02Z,
metrics: {
time: {
schedule: 0.001669,
config_retrieval: 1.55911207199097,
package: 0.006316,
exec: 0.329731,
total: 2.95773607199097,
cron: 0.000795,
service: 0.56894,
mailalias: 0.000378,
filebucket: 0.000226,
group: 0.001368,
yumrepo: 0.005424,
file: 0.479179,
user: 0.004598
},
changes: {
total: 1
},
events: {
success: 1,
total: 1
},
resources: {
changed: 1,
out_of_sync: 1,
total: 75
}
}
}
}
cheers,
Ohad
Regards and thanks in advance.
--
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/-/G26AQKHHSLUJ.
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] Managing Puppet modules as RPMs
On Sun, May 27, 2012 at 9:10 AM, devzero2000 pinto.e...@gmail.com wrote: Sorry for the top posting. Imnsho, rpm had always permitted to have multiple package version if they not conflict, in fact the usual case is the kernel. Anyway your question is most rpm related: so if you like i suggest you to ask to a rpm mailing list. as far as i know, kernel is a very specific usage case, and while rpm does support it, yum does not (kernel multi version in yum is hard coded). Ohad Best regards 2012/5/27, Anthony Shortland anth...@dtosolutions.com: We're using Puppet as part of a broader toolchain that relies on delivering software for deployment using sets of Yum-based RPM packages. We've setup system, role and application specific Yum repositories on an environment-by-environment basis that ensure that the required set of RPM versions flow appropriately (e.g. from development to QA to staging and hence to production). In this spirit we're packaging our Puppet modules as sets of RPMs too so the correct versions of the system, role and application specific modules flow along with everything else. The problem arises when you consider the conflict that arises between the natural use of Yum-based RPM installation and the Puppet master's module delivery mechanisms. Puppet allows modulepath to be set on an environment-by-environment basis, of course, thus supporting delivering different versions of modules from a master managing several environments. The restriction lies with Yum/RPM's inability to allow multiple versions of the same (relocatable) package to be installed on the same system (even good old System V packages could do that!). I'm looking for workarounds that aren't too egregious to either system! Here are the ideas we've come up with so far: Hack the RPM package names to include a version discriminator (e.g. packageV1-1.0-noarch.rpm rather than package-1.0-noarch.rpm) to allow them all to be installed on Puppet master Use Yum/RPM to install the modules directly on the client systems and find a way to restrict the Puppet master to managing the manifests rather than attempting to install the modules too. Is the second method workable? It seems to be a blend between agent and apply modes. We don't want to use apply mode since we really value using the master (even supplemented with Hiera) to act as the resource model provider to deliver configuration attributes to the agents as well as act as the node provider for Rundeck (used for distributed orchestration) using the Puppet/Rundeck plug-in (which doesn't seem to be environment aware - but that's another story!). We'd appreciate any comments and feedback on this. Thanks, Anthony. -- 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. -- Inviato dal mio dispositivo mobile -- 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] Get host deployment status report with REST
On Mon, May 28, 2012 at 7:54 PM, Juan A. S. oke...@gmail.com wrote:
U., I am not using Foreman, just the Puppet REST service or Puppet
Dashboard. Any idea?
afaik, thats not possible today with just puppet/dashboard.
Ohad
Thanks.
El lunes, 28 de mayo de 2012 14:30:16 UTC+2, ohad escribió:
On Mon, May 28, 2012 at 3:10 PM, Juan A. S. oke...@gmail.com wrote:
Hi
Is it possible to get the (last) deployment host report (or the list of
reports) for a specific node? I need to access it using REST, to know if
the deployment was succesful, and if not, the list of messages, like in the
dashboard...
If so, how would be the ACL? Now I have this, to allow the clients
submit their reports:
# allow all nodes to store their reports
path /report
method save
allow *
I'm not 100% if its not possible with the latest version of puppet, but
its possible using foreman, something like:
curl -s -u admin:password https://foreman/hosts/**certname/reports/last
-k -H 'Accept:application/json' |prettify_json.rb
{
report: {
id: 396001,
summary: Modified,
status: {
applied: 1,
skipped: 0,
failed_restarts: 0,
restarted: 0,
failed: 0
},
host: certname,
logs: [
{
log: {
sources: {
source: /Stage[main]/Ntp::Service/**Service[ntpd]/ensure
},
messages: {
message: ensure changed 'stopped' to 'running'
}
}
},
{
log: {
sources: {
source: Puppet
},
messages: {
message: Finished catalog run in 1.81 seconds
}
}
}
],
reported_at: 2012-05-28T11:07:02Z,
metrics: {
time: {
schedule: 0.001669,
config_retrieval: 1.55911207199097,
package: 0.006316,
exec: 0.329731,
total: 2.95773607199097,
cron: 0.000795,
service: 0.56894,
mailalias: 0.000378,
filebucket: 0.000226,
group: 0.001368,
yumrepo: 0.005424,
file: 0.479179,
user: 0.004598
},
changes: {
total: 1
},
events: {
success: 1,
total: 1
},
resources: {
changed: 1,
out_of_sync: 1,
total: 75
}
}
}
}
cheers,
Ohad
Regards and thanks in advance.
--
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/-/**G26AQKHHSLUJhttps://groups.google.com/d/msg/puppet-users/-/G26AQKHHSLUJ
.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe@*
*googlegroups.com puppet-users%2bunsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/**
group/puppet-users?hl=enhttp://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/-/LEM0wLL6GQsJ.
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] Passenger on redhat 6
On Thu, May 24, 2012 at 1:48 PM, David Schmitt da...@dasz.at wrote: On Thu, 24 May 2012 15:26:10 +0530, Aditya Patawari adi...@adityapatawari.com wrote: On Thu, May 24, 2012 at 1:28 PM, David Schmitt da...@dasz.at wrote: Hi, does anyone have a mod_passenger for RHEL6 from a trusted source, where I *don't* have to compile on the server? I'm trying to upgrade the puppetmaster/dashboard here and the docs on the wiki (http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger) are not helpful either. I have been using Phusion Passenger repo in production since a few months and so far no complains. URL: http://passenger.stealthymonkeys.com/rhel/6/$basearch Except that - as far as i understood it - those packages require a compiler and a local compile. try out https://github.com/theforeman/puppet-passenger, works without a compiler. Ohad Best Regards, David -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: modifying declared user/group types without resorting to inheritance?
On Thu, May 17, 2012 at 8:44 PM, Joshua Hoblitt jhobl...@cpan.org wrote:
On Thursday, May 17, 2012 7:11:18 AM UTC-7, jcbollinger wrote:
On May 16, 8:51 pm, Joshua Hoblitt jhobl...@cpan.org wrote:
as that would
preclude ::dev and ::prod being included on the same node.
why do you say that? That might become the case if you discovered
other, similar requirements, especially going the other direction, but
you could do what you describe with inheritance without
preventing ::dev and ::prod from both being included. Example:
class users::common {
user {
'alice': uid = 501, gid = 501;
'bob': uid = 502, gid = 502;
}
group { 'special-access': gid = 99 }
}
class users::dev inherits users::common {
user { 'charlie': uid = 601 }
Group['special-access'] {
members = 'bob'
}
}
class users::prod {
user { 'dave': uid = 701 }
}
[snip]
# shouldn't be a problem:
node hybrid {
include 'users::common'
include 'users::dev'
include 'users::prod'
}
In order for this to work for me both ::dev ::prod would need to
inherit from ::common and extend the same group definition. Without some
sort of multiple inheritance support that would end up with a Group type
declared twice or am I missing something?
I understand
that heira is good at dealing with this sort of situation. Is there
some
magic way of looking up data in heira without dumping foreman as an
enc?
No magic is required just for that. Hiera and Foreman themselves are
pretty much orthogonal. A bit of magic might be needed if you want to
use Foreman to set values that Hiera will provide, but that's what
hiera-foreman claims to do.
It sounds like I need to look further into Hiera...
another option would be to consider foreman smart variables.
Ohad
-Josh
--
--
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/-/9Bo_IP28_sUJ.
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] Foreman and default configs for all nodes
On Thu, May 10, 2012 at 8:43 PM, Miles Monteleone scratchys...@gmail.comwrote:
I'm having some issues applying a default set of modules to all of my
nodes managed by Foreman. I have around 20 nodes split among 4
environments. I have a node {default...} stanza in site.pp, but due to the
way puppet handles ENCs, nothing from this is applied to my nodes. I have
looked at host groups in Foreman, but they don't seem to do what I want,
since they are applied per-environment. Basically I just want to duplicate
the behavior of node {default} in Foreman. I don't care which environment
they are in. Any ideas?
you could always get foreman data, and merge it with your own set of
defaults (via your own simple enc script).
Ohad
--
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/-/X_QcI-6iqf0J.
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] Facts of other nodes
On Wed, May 9, 2012 at 10:33 PM, Joe joe.topj...@cybera.ca wrote:
Hello,
I'm trying to figure out the best solution for using facts of other
nodes in manifests.
I understand the use of exported configs and the concat module but, I
think, when using someone's contributed module, unless they wrote the
module using those solutions, I would have to rewrite the module
myself.
Here is the best way I can explain the particular problem I'm running
into. Maybe I'm totally on the wrong path with this.
class my_mysql_server {
class { 'mysql::server': }
# other stuff as needed
# ...
}
node node1.example.com {
class { 'my_mysql_server': }
}
node node2.example.com {
class { 'some::app::db':
db_username = 'foo',
db_password = 'password',
db_host = $my_mysql_server::fqdn,
}
}
In this case, 'some::app' is a contributed module. $db_host in 'db.pp'
simply references a single variable in a template - not a loop and not
using concat.
This does work, but I'm not entirely comfortable with it. For one, if
my_mysql_server is never applied, $fqdn will not be available. This
generally won't happen in the above example, but it's still a concern
I have. Secondly, if I choose to apply my_mysql_server to two nodes,
there would be more than one result for db_host. I'm not exactly sure
how to get around this.
What's the best practice for this type of situation? Should I just
hard-code the fqdn of my_mysql_server and be done with it? Or is there
a more dynamic way to do this?
if you are interested in using foreman, see
http://blog.theforeman.org/2012/01/getting-foreman-search-results-into.html
Ohad
Thanks,
Joe
--
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 3.0 and Hiera
On Fri, May 4, 2012 at 12:05 PM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
From: Pieter van de Bruggen pie...@puppetlabs.com
snip
* How should we integrate hiera_array() and hiera_hash() ?
* How should we integrate hiera ’s “default” and “override”
parameters?
* How should we handle overlaps between data supplied by Hiera
and data supplied in a parameterized class include?
Given:
class foo($something=default) { }
I think the plan was that there would be a priority order as below:
- someone wrote in a manifest: class{foo: something = something}
- an ENC supplied the values for something on the class foo
- someone did include foo or class{foo: } this would consult hiera
- if hiera does not have an answer it would default to default
Would be possible to define which function is called in this case? by
default that should be heira, but in case someone wants something else, I
think we should allow that?
Ohad
--
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] trouble w/ Foreman as ENC, agents and environments
On Fri, Apr 27, 2012 at 9:15 PM, droog72 steve@gmail.com wrote: Hi, I have a Puppet Enterprise (2.0) puppetmaster running with Foreman, and having trouble getting it working as an External Node Classifier. In short, if I manually add a test client into site.pp, it will retrieve the proper catalog / classes, but I would like to avoid having to do that. I'm also using environments (production/testing/ development) as well, but think I have most of this configured correctly - on the puppetmaster's puppet.conf - I do have: node_terminus = exec external_nodes = /etc/puppetlabs/puppet/node.rb node.rb does exist and is owned by pe-puppet, executable, etc. I've verified I can view the yaml for a test client using the script. and I have stanzas for each environment in the master's puppet.conf - [production] modulepath=/etc/puppetlabs/puppet/production/modules [testing] ...etc.. and the client's puppet.conf has : environment = testing under the agent stanza. Running: puppet agent --test --environment testing will run, but doesn't apply any classes. I'm not sure what else I may be missing? Thanks in advance. beside checking your logs, you should also make sure you can run that script as the puppetmaster user and not root. Ohad -- 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] Hudson/Jenkins updating host parameter?
On Fri, Feb 10, 2012 at 7:18 AM, mkochco mkoc...@gmail.com wrote: Can I get suggestions on how to accomplish step 3. I know foreman provides a REST API but it doesn't appear to allow modification of host parameters. AFAIK, all parameters can be modified over the API, including host parameters.. feel free to provide more details on the foreman users list. Cheers, Ohad -- 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] Search which the agent on which a specified module is been installed
On Wed, Feb 1, 2012 at 7:01 AM, sateesh bbalasate...@gmail.com wrote: Hi, Can we get the list of IPs from server where the specified module is installed. There is a search functionality in the Chef to do this. Is there any way in puppet? If you are using Foreman[1], you could utilize its search functionality to get that kind of a data using a rest api[2]. You could even utilize that information from within puppet using a sample puppet function [3] cheers, Ohad [1] - http://theforeman.org [2] - http://theforeman.org/projects/foreman/wiki/Search_API [3] - http://blog.theforeman.org/2012/01/getting-foreman-search-results-into.html Thanks in advance, Sateesh B. -- 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 Dashboard and Ruby 1.8.7 for EL5 systems HOWTO (draft)
On Thu, Jan 5, 2012 at 3:04 AM, Jo Rhett jrh...@netconsonance.com wrote: First many thanks for your efforts! 3. Foreman requires Ruby 1.8.7 Just wanted to correct that, the upcoming version would, but we still maintain a supported version 0.4.x that works on RHEL5 with no issues. Thanks, Ohad -- 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] New Foreman and Smart Proxy Release
Hi All, This is a maintenance release, and most likely the last release of foreman supporting Ruby older than 1.87 (The proxy would still run on older versions of ruby as far as we can support it). if you have no idea what foreman is about, feel free to review http://theforeman.org/projects/foreman/wiki/Features This release mostly contains many small UI fixes and features, PostgreSQL related bugs and dashboard notifications. If you are provisioning hosts via foreman, it is highly recommended to upgrade to this version, as it solves an issue when foreman was unable to rollback actions on failures #1386 [1] (e.g. dns / dhcp records etc). The complete change log for foreman can be found here [2] and for the proxy at [3] [1] - http://theforeman.org/issues/1386 [2] - http://theforeman.org/versions/show/17 [3] - http://theforeman.org/versions/show/18 Many thanks to all contributes and users, Have fun, Ohad -- 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] script to find non-puppet systems
On Wed, Dec 21, 2011 at 12:24 AM, Corey Osman co...@logicminds.biz wrote: Hi, Just curious if anybody had written a script to find systems that don't have puppet installed by doing a port scan or something else. I would like to have my puppetmaster send an email when it finds a system that doesn't have puppet installed and possibly take action by installing it. Does anybody have some good ideas how a system can be detected as a non-puppet system? One idea would be to use net-snmp to query the list of installed packages. But this requires net-snmp to be running snmpwalk -v 2c -c public hostname 1.3.6.1.2.1.25.6.3.1.2 | grep puppet another option, while scoped to a given subnet, is that you can find out all mac addresses of all of your systems minus all the mac addresses coming from facter. Ohad Corey Osman co...@logicminds.biz Green I.T and Datacenter Automation Specialist -- 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] Can Puppet be configured to one-time deployment for modules?
On Tue, Dec 20, 2011 at 6:49 PM, Swampcritter mawors...@gmail.com wrote: We are developing in-house RHEL VM provisioning (similar to Satellite/ Spacewalk) along with a customized kickstart template, but also including Puppet to handle the actual configuration of the While being biased, I would recommend you to look at other open source projects in the same scope, such as Foreman[1], might save you some time eventually. Ohad FYI - I'm Foreman's maintainer. [1] - http://theforeman.org environment. One thing we need to see is does Puppet have a variable that will deploy one module only once and not check against it just in case the configuration file it has created has been altered or not and try to revert back. Example: Boot using PXEBoot w/ DHCP, build RHEL VM using custom kickstart configuration, create local repo file with pointers to in- house repository and comment out the variables to use the RHN driven one, download from the repo and apply the RHN/Errata updates, then reconfigure the rc.local to install Puppet on the reboot and apply the actual environment requirements (i.e. check to see if its a Apache web server, Oracle database, Weblogic/JBoss portal, etc). The last part is the deciding factor -- as this part of the requirements are quite possibly going to change via the developers that are actually using the environment for testing and tweaking the RHEL OS memory and TCP communication needs (/etc/sysctl.conf) or the Apache /etc/httpd/httpd.conf code. We don't want Puppet to revert back the code variables as these are being modified by hand and not using SVN or any other type of code version control at this time. Anyone know if module exclusion is possible for a deploy once, don't touch again scenario? -- 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] Foreman push_facts script
On Wed, Nov 30, 2011 at 5:12 PM, Ken Barber k...@puppetlabs.com wrote: Hi Carles, You probably want the foreman-users mailing list for foreman related questions, so I'm cross-posting for you. As part of the ENC script, facts can be pushed up to foreman whenever a node does a 'puppet run'. There are probably other pre-built mechanisms for doing this however specific to foreman. https://github.com/ohadlevy/puppet-foreman/blob/master/foreman/templates/external_node.rb.erb ken. 2011/11/30 Carles Amigó carles.am...@softonic.com: Installing the new version of Foreman in our current Puppet environment and I don't really want to share the same database as we rely so much in exported resources. As I've read in http://theforeman.org/projects/foreman/wiki/Puppet_Facts it's possible to push the Puppet facts using the push_facts script, however it's no longer available in github: https://github.com/ohadlevy/puppet-foreman/blob/master/foreman/files/push_facts.rb Is this method still valid? While Ken solution is the preferred method, the original script can be found here: https://github.com/ohadlevy/puppet-foreman/blob/1fec77660a1d32337fc053a5789bf6116ccd7b31/foreman/files/push_facts.rb Ohad -- 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] Foreman API, problem when creating hostgroups
CC foreman users list.
2011/11/20 Poul Sørensen poulhsoren...@gmail.com:
I am trying to create a hostgroup using the Foreman API
(foreman-0.4-0.1rc1.noarch):
Using perl v.5.14.2, REST::Client et. al., ending up with sending:
POST /hostgroups
{name:api-created-
hostgroup,architecture_id:,medium_id:,environment_id:,operatingsystem_id:,ptable_id:,puppetmaster:puppet.dev.somewhere.com,root_pass:}
which returns a 422-error
[that is: 422 Unprocessable Entity (WebDAV) (RFC 4918) - The request
was well-formed but was unable to be followed due to semantic errors.]
Processing HostgroupsController#create (for 10.20.7.81 at 2011-11-20
22:14:54) [POST]
Parameters: {architecture_id=, name=api-created-hostgroup,
puppetmaster=puppet.dev.somewhere.com, action=create,
root_pass=[FILTERED], medium_id=, ptable_id=,
environment_id=, controller=hostgroups,
operatingsystem_id=}
Failed to save: Name can't be blank or contain trailing white spaces.
Completed in 47ms (View: 2, DB: 12) | 422 Unprocessable Entity [http://
puppet.dev.somewhere.com/hostgroups]
it looks like you are missing the hostgroup parameter hash, afair, if
you look at the look, all attributes are values of the key hostgroup.
btw: make sure that you are using the right content-type
(application/json) and pass along the user credentials (as basic auth)
if they are required in your setup.
Ohad
btw: 0.4. has been released and has a lot of enchantments in the api
area, might worth upgrading.
I can easily do GET /hostgroups and all the other GET's documented
in the API, so I _think_ that my usage is correct...
but I guess something must be wrong somewhere:
Failed to save: Name can't be blank or contain trailing white spaces.
I even tried with GET/POST (from LWP)
GET
http://apiusername:apiuserpassw...@puppet.dev.somewhere.com/hostgroups?format=json
works fine
echo '{name:api-created-
hostgroup,architecture_id:,medium_id:,environment_id:,operatingsystem_id:,ptable_id:,puppetmaster:puppet.dev.somewhere.com,root_pass:}'
| POST
http://apiusername:apiuserpassw...@puppet.dev.somewhere.com/hostgroups?format=json
{errors:[[name,can't be blank or contain trailing white
spaces.]]}
Hope you can point out my error!
Poul
--
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: [foreman-users] dropping support for ruby 1.85?
On Thu, Nov 17, 2011 at 5:42 PM, Markus Falb wne...@gmail.com wrote: On 16.Nov.2011, at 08:58, Ohad Levy wrote: On Wed, Nov 16, 2011 at 6:30 AM, Jo Rhett jrh...@netconsonance.com wrote: On Nov 9, 2011, at 5:47 AM, Ohad Levy wrote: Ruby 1.87 support Foreman 0.4 would be the last major version supporting Ruby older then 1.87. This has to be done since the upstream rails community no longer supports older versions, which means that critical security patches are no longer available if we keep supporting that. if required, we would release 0.4.x maintenance releases, but since ruby 1.87+ is available on most distribution these days, you are encouraged to upgrade. No distribution based on RHEL5 has a supported version of ruby other than 1.85 AFAIK. It's pretty much a roll-your-own-RPM for 1.87, and that's not possible for most sites. The way I see it: Don't upgrade to ruby 1.87 == known security holes that could exploit your foreman server (impacting everyone). This is not how RHEL works! The version stays the same all 7 years of lifetime of the distribution but they are backporting security relevant stuff. Therefore you can not tell from the version number if software is vulnerable. Actually, one can expect, and this is what one pays redhat for, that there are NO security holes in their ruby packages. Trust me, I know, I work for redhat. if its not clear, what it means, is that if you want to run it on RHEL5, you can either keep running the current 0.4.x versions or upgrade your ruby stack. otherwise use a more recent distribution. I've tried very hard to make foreman accessible to as many distributions as possible, and as i look at foreman becoming important piece in the infrastructure puzzle, I can't ignore security issues. Ohad Please see https://access.redhat.com/security/updates/backporting/ Upgrade to ruby 1.87 == Pain of migrating foreman to a newer distribution (impacting only a subset of the users)** We are also planning to have a maintenance release in the 0.4.x versions, so critical bugs (and probably less than critical) would be fixed there as well. Fine, btw. regular RHEL 5 lifecycle ends on March 31, 2014 https://access.redhat.com/support/policy/updates/errata/ Best Regards, Markus -- You received this message because you are subscribed to the Google Groups Foreman users group. To post to this group, send email to foreman-us...@googlegroups.com. To unsubscribe from this group, send email to foreman-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/foreman-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] [foreman-users] dropping support for ruby 1.85?
On Thu, Nov 17, 2011 at 8:55 PM, Jo Rhett jrh...@netconsonance.com wrote: On Nov 17, 2011, at 10:30 AM, Ohad Levy wrote: if its not clear, what it means, is that if you want to run it on RHEL5, you can either keep running the current 0.4.x versions or upgrade your ruby stack. otherwise use a more recent distribution. Given that upgrading the ruby stack means either build your own RPMs from scratch or download from a random internet site this is going to limit the number of sites which can do this. Since we understand its a pain upgrading to a newer distribution, we've built a puppet module which helps with foreman installation... if you have any better ideas of how we can try helping our ruby community... Ohad -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- 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] Reopening sqlite3 db
On Tue, Nov 15, 2011 at 7:16 PM, Klaus Ethgen klaus+use...@ethgen.de wrote: Hello, I am not sure if I trigger a bug and if so it could also be in ruby sqlite3 backend. However, maybe I do something totally wrong. I have the following part in puppet.conf: [master] storeconfigs = true dblocation = /var/lib/puppet/state/clientconfigs.sqlite3 dbadapter = sqlite3 Now every time a client (agent in puppet speak) is run I get one more connection to the database: lsof -np $(pgrep puppet) ... puppet 23542 puppet 7u IPv4 1180771 0t0 TCP *:8140 (LISTEN) puppet 23542 puppet 9w REG 252,1 71 2621 /var/log/puppet/rails.log puppet 23542 puppet 10u REG 252,1 156672 2684 /var/lib/puppet/state/clientconfigs.sqlite3 puppet 23542 puppet 11u REG 252,1 156672 2684 /var/lib/puppet/state/clientconfigs.sqlite3 Next run: lsof -np $(pgrep puppet) ... puppet 23542 puppet 7u IPv4 1180771 0t0 TCP *:8140 (LISTEN) puppet 23542 puppet 9w REG 252,1 71 2621 /var/log/puppet/rails.log puppet 23542 puppet 10u REG 252,1 156672 2684 /var/lib/puppet/state/clientconfigs.sqlite3 puppet 23542 puppet 11u REG 252,1 156672 2684 /var/lib/puppet/state/clientconfigs.sqlite3 puppet 23542 puppet 12u REG 252,1 156672 2684 /var/lib/puppet/state/clientconfigs.sqlite3 And so on until the maximum is reached and the puppetmaster do not work anymore. I encountered this bug with many versions on different linux distributions. For example: Ubuntu 10.04 Puppet 2.7.6 libsqlite3-ruby1.8 1.2.4-2.1 Do anybody has an idea what I can do to handle that? which version of activerecord? might wan tot try upgrading it -- Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -- 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] Reopening sqlite3 db
On Wed, Nov 16, 2011 at 12:41 PM, Klaus Ethgen klaus+use...@ethgen.de wrote: Ohad Levy ohadl...@gmail.com schrieb: I encountered this bug with many versions on different linux distributions. For example: Ubuntu 10.04 Puppet 2.7.6 libsqlite3-ruby1.8 1.2.4-2.1 Do anybody has an idea what I can do to handle that? which version of activerecord? might wan tot try upgrading it How do I find the version? On ubuntu there is no separate activerecord package. On SuSI where I have the same problem, activerecored is version 2.1.2 try with the gem command. 2.1.x is fairly old and is probably the cause for your problems Ohad -- Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -- 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] Advocacy Material
On Fri, Nov 11, 2011 at 11:36 AM, Daniel Shaw dan...@point-oh.net wrote: Hi, I have dabbled with Puppet in previous positions, had success and loved it. My current employer does not have in place any systems management tools and is an ideal candidate for another Puppet installation. I obviously need to run this by a superior before I can implement it on production systems.. So, can anyone point me to any good less-technical overview articles, presentations or videos? I need to have something to present, and it'd be great to not re-invent the wheel as I imagine there must be some material out there. You can probably look for various presentation, just to name a few http://projects.puppetlabs.com/projects/1/wiki/Puppet_Presentations Ohad Regards, Daniel -- 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: dropping support for ruby 1.85?
On Wed, Nov 16, 2011 at 6:30 AM, Jo Rhett jrh...@netconsonance.com wrote: On Nov 9, 2011, at 5:47 AM, Ohad Levy wrote: Ruby 1.87 support Foreman 0.4 would be the last major version supporting Ruby older then 1.87. This has to be done since the upstream rails community no longer supports older versions, which means that critical security patches are no longer available if we keep supporting that. if required, we would release 0.4.x maintenance releases, but since ruby 1.87+ is available on most distribution these days, you are encouraged to upgrade. No distribution based on RHEL5 has a supported version of ruby other than 1.85 AFAIK. It's pretty much a roll-your-own-RPM for 1.87, and that's not possible for most sites. The way I see it: Don't upgrade to ruby 1.87 == known security holes that could exploit your foreman server (impacting everyone). Upgrade to ruby 1.87 == Pain of migrating foreman to a newer distribution (impacting only a subset of the users)** We are also planning to have a maintenance release in the 0.4.x versions, so critical bugs (and probably less than critical) would be fixed there as well. Ohad ** which imho is a non issue, as : 1. there is a fully automated puppet module to install foreman 2. you only need to pass the db and a couple of config files. -- 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 node network configuration
On Mon, Nov 14, 2011 at 10:52 AM, Will S. G. w...@arw.in wrote: Hello everyone, I'm fairly new to the DevOps realm, and while I've written my fair share of bash loops and such, I figured it was time to learn something new. That being said, I've been working on automating the kickstart process (no cobbler yet). I've configured my Kickstart script (CentOS 6) to do the dirty work of installing the OS, configure local yum repo (%post), and then install puppet. What I would like to do is to set up a list of MAC addresses, along with the IP addresses a head of time, and then have puppet rewrite the networking configuration of the host based on MAC address after it has successfully signed the certificate and communicated with the client host. Possible? If so, any guidance, examples or tips on how to achieve this? Perhaps, more importantly, would this be the right approach? or you can simply use foreman [1], you can see a screencast here [2] [1] http://theforeman.org [2] http://www.youtube.com/watch?v=vqmsaQbY5Jw Ohad -- 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 node network configuration
On Mon, Nov 14, 2011 at 1:52 PM, Scott Merrill ski...@skippy.net wrote: On Nov 14, 2011, at 4:01 AM, John Kennedy skeb...@gmail.com wrote: On Mon, Nov 14, 2011 at 08:52, Will S. G. w...@arw.in wrote: What I would like to do is to set up a list of MAC addresses, along with the IP addresses a head of time, and then have puppet rewrite the networking configuration of the host based on MAC address after it has successfully signed the certificate and communicated with the client host. Possible? If so, any guidance, examples or tips on how to achieve this? Perhaps, more importantly, would this be the right approach? While this can be done, I think using DHCP would be better here. DHCP can be configured to serve static IP addresses based on the MAC address. You can then use puppet to maintain DHCP configuration. I'm eyeing a similar configuration. In our network, we don't control the network, only the Linux servers, so configuring DHCP isn't really an option. I'd like to see how others are tackling this in similarly restricted environments. Using gpxe? Ohad Cheers, Scott -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Stored config error Could not autoload active_record: uninitialized constant ActiveRecord
On Mon, Nov 14, 2011 at 2:10 PM, Tom tomhay...@gmail.com wrote: Hi, Attempting to get Puppet, Ruby Ent, Foreman, and Passenger working on Centos 6 but ran into this problem with stored configs. Tried getting stored configs working through MySQL but when I run = puppet agent --test --debug --no-daemonize -v on the Puppet Master I get this error = err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload active_record: uninitialized constant ActiveRecord warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Gems installed = gem list actionmailer (3.1.1) actionpack (3.1.1) activemodel (3.1.1) activerecord (3.1.1) activeresource (3.1.1) activesupport (3.1.1) arel (2.2.1) builder (3.0.0) bundler (1.0.21) daemon_controller (0.2.6) erubis (2.7.0) fastthread (1.0.7) hike (1.2.1) i18n (0.6.0) mail (2.3.0) mime-types (1.17.2) multi_json (1.0.3) mysql (2.8.1) passenger (3.0.9) polyglot (0.3.3) rack (1.3.5) rack-cache (1.1) rack-mount (0.8.3) rack-ssl (1.3.2) rack-test (0.6.1) railties (3.1.1) rake (0.9.2.2) rdoc (3.11) rubygems-update (1.8.11) sprockets (2.1.0, 2.0.3) thor (0.14.6) treetop (1.4.10) tzinfo (0.3.31) So activerecord 3.1.1 is installed but I think it might be related to a library path...I am fairly new to Puppet so not sure how to get around this issue. You should use the gem bin that is installed from REE Ohad Any help kindly appreciated. Thanks Tom -- 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] New Foreman Release
So, its been a long time, and finally we got a new foreman release :) Download - http://theforeman.org/foreman-latest.tar.bz2 RPMS http://yum.theforeman.org DEB - http://deb.theforeman.org Some of this version highlights: * New UI that doesn't SUCK. * host groups can now be nested * hostgroups can now act as a as templates, including VM attributes etc. * Introducing Smart Variables * Most of Foreman_configuration has been moved into the UI itself, this does not require a restart every time you change something, only core settings remain in the settings file. * audit log now capture class assignments * Solaris (sparc and intel) provisioning support * OpenSUSE provisioning support * BMC NIC management * Introducing Foreman CLI * Many API improvements * added rundeck integration * dhcp subnets can now be imported via the proxy Smart Proxy version In order to use provisioning support with this version of Foreman, you are required to* update your proxy* to the latest 0.3 release. Ruby 1.87 support Foreman 0.4 would be the last major version supporting Ruby older then 1.87. This has to be done since the upstream rails community no longer supports older versions, which means that critical security patches are no longer available if we keep supporting that. if required, we would release 0.4.x maintenance releases, but since ruby 1.87+ is available on most distribution these days, you are encouraged to upgrade. All in all, this version has around 180 features/bugs fixed, so its our largest so far - full details at [1] Full release notes [2] We've also added another means of communications (besides IRC and mailing lists, Google+ page [3]) I would like to thank anyone who contributed to the project, I'm having lots of fun :-) Ohad [1] - http://theforeman.org/versions/show/13 [2] - http://theforeman.org/projects/foreman/wiki/ReleaseNotes [3] - https://plus.google.com/u/0/b/102496134326414788199 -- 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: Announce: Puppet Dashboard 1.2.2 Available
On Sat, Oct 22, 2011 at 4:18 AM, Michael Stahnke stah...@puppetlabs.com wrote: On Fri, Oct 21, 2011 at 7:10 AM, Steve Snodgrass phe...@gmail.com wrote: My apologies, I didn't completely investigate the problem before complaining. My reposync cron job is not pulling down dashboard 1.2.2 to my local mirror from the EL6 x86_64 directory. After looking, I found that while the file is present on your web server, reposync is ignoring it because your repo metadata is out of date. I verified that 1.2.2 is missing from the primary.xml file, but you can tell just from the timestamps - the RPM is from 10/10 10:53, whereas the metadata is from 10/10 10:19. It would be helpful if you would automate a createrepo job to either run periodically or as part of your release process. Thanks. I think we updated the repodata today. Agreed, though, repodata should be updated when new packages arrive ;) One can use mtime checksum on the directory to trigger createrepo ;) Ohad On Oct 20, 5:06 pm, Michael Stahnke stah...@puppetlabs.com wrote: On Thu, Oct 20, 2011 at 9:46 AM, Steve Snodgrass phe...@gmail.com wrote: Is this going to make it into the yum repo? Thanks. What is this in this context? Dashboard 1.2.2 is available in the yum repo for EL6. On Oct 10, 2:33 pm, Michael Stahnke stah...@puppetlabs.com wrote: This is a maintenance release of Puppet Dashboard 1.2.2. This release is available for download at:http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. RPMs are also available on yum.puppetlabs.com. See the Verifying Puppet Download section at:http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.2http://projects.puppetlabs.com/projects/dashboard Documentation is available at:http://docs.puppetlabs.com/dashboard/index.html # Highlights for this release ## (#9940) dashboard-workers can be managed as service The stop command in the puppet-dashboard-workers init script would fail when run using a puppet service resource. This had something to do with the way sudo works on EL. Removing the sudo from the stop function allows the service to be managed by puppet reliably. And because it is stopping the process, and not creating the process, it doesn't matter whether it runs as root or puppet-dashboard. ## (#9429) Prevent editing node name The uneditable node name was displayed in a text input control, which was less than ideal for a number of reasons. Now it's plain text. ## (#9429) makes node name field readonly during edit action The readonly attribute of the node name text field is set via the @readonly_name instance variable. When nil, the node name can be edited. This commit prevents the node name from being edited, though it can be set normally during node creation. ## (#9429) adds attr_readonly to name in the node model Changes to the name attribute of nodes are ignored, via the attr_readonly attribute in the model. In the view, readonly input controls are assigned a #EEE background. spec tests updated with readonly changes. ## (#9282) Change user in database.yml.example to dashboard Previously, our database.yml.example file suggested handing the keys to the root MySQL user to Dashboard, which is a poor security practice. This commit changes the default user suggestion to dashboard, which is the default MySQL user used in Puppet Enterprise. ## (#9262) causes the contents of .section divs to scroll when overflowing This is a short-term solution to a larger problem. Dashboard is split into two columns, the sidebar (20% of window width), and the main content pane (80% of window width). The problem is when dealing with large strings of non-breaking text (e.g. file paths), the containing element runs off the screen unless accomodations are made (e.g. overflow: auto;). The better--long term--fix is to replace the 20%/80% column layout with one that allows the main content pane variable width. Thus, the entire window scrolls horizonally when elements overflow instead of requiring short-term fixes for each offending element. ## (#9215) Add a Rake task that removes nodes v1.2.2 === 484b323 Change node:delete to node:del for consistency 56b141c (#9215) Rename node:del to node:delete 20cf5fe (#9954) Add a rake task to add classes to a nodegroup d9eca18 (#9954) Add a rake task to list nodeclasses e75b51d (#9953) Add a rake task for listing nodegroups 14b93a2 Maint: adding VERSION_LINK to .gitignore 8725921 (#9940) dashboard-workers can be managed as service ce3868f (#9429) Prevent editing node name edbb48e (#9429) makes node name field readonly
Re: [Puppet Users] puppet-foreman
On Tue, Oct 18, 2011 at 8:00 PM, Corey Osman co...@logicminds.biz wrote: Hi, I created a centOS6 EC2 instance last night and ran the foreman puppet module but it came back with a few years. Was hoping somebody could help me understand these errors. [root@ip-10-170-77-129 config]# echo include foreman | puppet --modulepath /root/puppet-foreman/ err: /Stage[main]/Foreman::Config::Enc/File[/var/lib/puppet/yaml/foreman]/ensure: change from absent to directory failed: Cannot create /var/lib/puppet/yaml/foreman; parent directory /var/lib/puppet/yaml does not exist [root@ip-10-170-77-129 config]# mkdir /var/lib/puppet/ clientbucket/ client_data/ client_yaml/ facts/ lib/ ssl/ state/ Should the foreman puppet module be altered to say client_yaml instead of yaml? Was the foreman module was created with an older puppet version in mind? Or is this because I didn't start my puppetmaster before using the foreman module. Yeah, I was a bit too lazy to write down a fact for that, if you dont have a master, you probably want to tweak the parameters not to install the enc script. Ohad Corey Osman co...@logicminds.biz Green I.T and Datacenter Automation Specialist -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Official puppetlabs position on cron vs puppet as a service?
On Mon, Oct 10, 2011 at 2:05 PM, Jonathan Gazeley
jonathan.gaze...@bristol.ac.uk wrote:
On 08/10/11 21:22, Chris Phillips wrote:
What better way to monitor the puppet runs than by executing that run as
part of the check?
I assume your Nagios plugin execution timeout must be insanely long? :)
In the past I have considered using Nagios for things other than monitoring,
and likewise using Puppet for things other than configuration. On both
counts I decided it was probably best to set a boundary and not wilfully
abuse these tools, since it's likely to go wrong sooner or later! In my
organisation we use Nagios only to monitor, and Puppet only to configure.
Have fun!
Jonathan
If you are using foreman, its very easy to query the last puppet
report state, e.g.
curl -k -u $user:$pass https://foreman/hosts/`hostname
-f`/reports/last?format=json |prettify_json.rb
{
report: {
reported_at: 2011-10-10T13:03:02Z,
metrics: {
time: {
group: 0.001799,
class: 0.002389,
config_retrieval: 2.4686119556427,
cron: 0.00056,
schedule: 0.002556,
service: 0.702501,
yumrepo: 0.081921,
total: 4.6954209556427,
mailalias: 0.000351,
package: 0.012924,
exec: 0.336481,
file: 1.079741,
filebucket: 0.000226,
user: 0.00536
},
events: {
total: 0
},
resources: {
total: 212
},
changes: {
total: 0
}
},
id: 269755,
summary: Success,
host: super.tlv.redhat.com,
logs: [
],
status: {
failed: 0,
restarted: 0,
applied: 0,
skipped: 0,
failed_restarts: 0
}
}
}
Ohad
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Official puppetlabs position on cron vs puppet as a service?
On Mon, Oct 10, 2011 at 5:16 PM, Craig White craig.wh...@ttiltd.com wrote:
that always seems to redirect me to 'login' (even though I am passing the -u
username:password)
I'm guessing you have ssl redirection turned on and you are using http
instead of https?
Ohad
Craig
On Oct 10, 2011, at 6:32 AM, Ohad Levy wrote:
On Mon, Oct 10, 2011 at 2:05 PM, Jonathan Gazeley
jonathan.gaze...@bristol.ac.uk wrote:
On 08/10/11 21:22, Chris Phillips wrote:
What better way to monitor the puppet runs than by executing that run as
part of the check?
I assume your Nagios plugin execution timeout must be insanely long? :)
In the past I have considered using Nagios for things other than monitoring,
and likewise using Puppet for things other than configuration. On both
counts I decided it was probably best to set a boundary and not wilfully
abuse these tools, since it's likely to go wrong sooner or later! In my
organisation we use Nagios only to monitor, and Puppet only to configure.
Have fun!
Jonathan
If you are using foreman, its very easy to query the last puppet
report state, e.g.
curl -k -u $user:$pass https://foreman/hosts/`hostname
-f`/reports/last?format=json |prettify_json.rb
{
report: {
reported_at: 2011-10-10T13:03:02Z,
metrics: {
time: {
group: 0.001799,
class: 0.002389,
config_retrieval: 2.4686119556427,
cron: 0.00056,
schedule: 0.002556,
service: 0.702501,
yumrepo: 0.081921,
total: 4.6954209556427,
mailalias: 0.000351,
package: 0.012924,
exec: 0.336481,
file: 1.079741,
filebucket: 0.000226,
user: 0.00536
},
events: {
total: 0
},
resources: {
total: 212
},
changes: {
total: 0
}
},
id: 269755,
summary: Success,
host: super.tlv.redhat.com,
logs: [
],
status: {
failed: 0,
restarted: 0,
applied: 0,
skipped: 0,
failed_restarts: 0
}
}
}
Ohad
--
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.
--
Craig White ~ craig.wh...@ttiltd.com
1.800.869.6908 ~~ www.ttiassessments.com
Need help communicating between generations at work to achieve your desired
success? Let us help!
--
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] Trigger when on any package change
On Thu, Sep 29, 2011 at 10:22 PM, GeekBiker wentworth.r...@gmail.com wrote:
I need to exec a program if ANY packages have been modified (added,
removed, updated, etc). I tried subscribing to Package with a
wildcard, but that isn't supported.
Is there any way to trigger an exec if there were any packages changes
were made or if yum was executed?
Specifically, I need to execute rkhunter --propupd so we will stop
getting false alarms whenever we update a bunch of systems.
--
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 could setup a file resource on the rpm db file with mtime, which
notifies an exec, something like
file {/var/lib/rpm: checksum = mtime, notify = Exec...}
this way every time that file would change, your exec would be triggered.
Ohad
--
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: Official puppetlabs position on cron vs puppet as a service?
On Mon, Sep 26, 2011 at 12:29 AM, Scott Smith sc...@ohlol.net wrote: Ohad, was rand_fqdn not sufficient for you? well.. I did it a long time ago, so I'm not 100% sure, but I think the main reason was to allow to manage cron entries over an interval, e.g. 3 times an hour, or 7 times a day in a random fashion. Ohad On Sep 25, 2011 1:03 PM, Ohad Levy ohadl...@gmail.com wrote: On Sun, Sep 25, 2011 at 10:33 PM, treydock treyd...@gmail.com wrote: On Sep 24, 9:42 pm, Aaron Grewell aaron.grew...@gmail.com wrote: We had frequent inexplicable daemon crashes on Solaris, but not on RHEL5 (at least not yet) . Given known issues with memory leakage in older Ruby releases Cron seemed more likely to be reliable. We stuck a random wait in the Cron job to spread load on the master and so far it works well. On Sep 24, 2011 7:22 AM, treydock treyd...@gmail.com wrote: On Sep 23, 5:42 pm, Brian Gupta brian.gu...@brandorr.com wrote: Over the years many shops have come to start running puppet via cron to address memory leaks in earlier versions of Ruby, but the official position was that puppet was meant to be run as a continually running service. I am wondering if the official position has changed. On one hand many if not all of the early Ruby issues have been fixed, on the other, the addition of mcollective into the mix as a lightweight agent for triggering adhoc puppet runs, and other tasks somewhat lowers the requirements for puppet to be run as a service. (Or out of cron for that matter). I understand that in cases where old Ruby versions are for whatever reason mandated the answer may be different. Thanks, Brian -- http://aws.amazon.com/solutions/solution-providers/brandorr/ Could those memory leak problems cause the Puppet daemon to crash with no logs indicating why? I have about 20 systems all running CentOS 5 and 6, with Puppet 2.6.9, and I now have to have Zabbix run a /etc/ init.d/puppet start everytime the daemon crashes which is almost on a daily basis for every client. Would be interested to know of a known fix or if the only fix is the workaround of using Cron. Thanks - Trey -- 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. Could you share how you did the random wait? I may have to switch to a cron job with how often my daemons are crashing and having to be restarted by Zabbix. I used the ip_to_cron function from http://projects.puppetlabs.com/projects/1/wiki/Cron_Patterns afterwards, I just do a sleep random 59, so its also random within the minute. Ohad Thanks - Trey -- 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. -- 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: Official puppetlabs position on cron vs puppet as a service?
On Sun, Sep 25, 2011 at 10:33 PM, treydock treyd...@gmail.com wrote: On Sep 24, 9:42 pm, Aaron Grewell aaron.grew...@gmail.com wrote: We had frequent inexplicable daemon crashes on Solaris, but not on RHEL5 (at least not yet) . Given known issues with memory leakage in older Ruby releases Cron seemed more likely to be reliable. We stuck a random wait in the Cron job to spread load on the master and so far it works well. On Sep 24, 2011 7:22 AM, treydock treyd...@gmail.com wrote: On Sep 23, 5:42 pm, Brian Gupta brian.gu...@brandorr.com wrote: Over the years many shops have come to start running puppet via cron to address memory leaks in earlier versions of Ruby, but the official position was that puppet was meant to be run as a continually running service. I am wondering if the official position has changed. On one hand many if not all of the early Ruby issues have been fixed, on the other, the addition of mcollective into the mix as a lightweight agent for triggering adhoc puppet runs, and other tasks somewhat lowers the requirements for puppet to be run as a service. (Or out of cron for that matter). I understand that in cases where old Ruby versions are for whatever reason mandated the answer may be different. Thanks, Brian -- http://aws.amazon.com/solutions/solution-providers/brandorr/ Could those memory leak problems cause the Puppet daemon to crash with no logs indicating why? I have about 20 systems all running CentOS 5 and 6, with Puppet 2.6.9, and I now have to have Zabbix run a /etc/ init.d/puppet start everytime the daemon crashes which is almost on a daily basis for every client. Would be interested to know of a known fix or if the only fix is the workaround of using Cron. Thanks - Trey -- 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. Could you share how you did the random wait? I may have to switch to a cron job with how often my daemons are crashing and having to be restarted by Zabbix. I used the ip_to_cron function from http://projects.puppetlabs.com/projects/1/wiki/Cron_Patterns afterwards, I just do a sleep random 59, so its also random within the minute. Ohad Thanks - Trey -- 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] Software inventory
On Wed, Sep 21, 2011 at 7:45 PM, Glenn Bailey replic...@dallaslamers.org wrote: Howdy, Before I go about writing one myself, anyone out there written a software inventory module/fact for gathering a list of all installed rpms/debs on a system? Got a few ideas floating around in my head, but wanted to see if/what other folks have done .. Not sure what exactly you are looking for, but a few years ago I wrote a rails [1] app to collect and show/search etc all packages across all hosts etc in a db Ohad [1] https://github.com/ohadlevy/dish -- I've seen things you people wouldn't believe. Attack ships on fire off the shoulder of Orion. I watched C-beams glitter in the dark near the Tannhauser gate. All those moments will be lost in time... like tears in rain... Time to die. -- 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] Storeconfigs seem slow
On Tue, Sep 13, 2011 at 12:41 AM, Justin Lambert jlamb...@localmatters.com wrote: Thanks for the response. We're using Posrgres, and the catalog build seems a bit slow, but nothing compared to the client runtime which is where I've been focusing. Your assessment is correct, it is just the nagios server that is extremely slow (~20 mins), there is minimal/no impact to the client machines. We're at about the 100 hosts, but have closer to 1500 services - maybe we have exceeded what storeconfigs can do then. If that is the case, is there a recommended alternative that isn't manually maintaining config files? It seems like most of the processing time is spent client side and I haven't been able to figure out why. Even doing an md5sum on all of the files from the CLI takes less than 2 seconds. While it would require you to generate the templates yourself, you can use foreman query script [1] to get the data you need based on all sort of conditions. Ohad [1] - https://github.com/ohadlevy/puppet-foreman/blob/master/foreman/lib/puppet/parser/functions/foreman.rb On Mon, Sep 12, 2011 at 3:30 PM, Gabriel Filion lelu...@gmail.com wrote: Hi, On 11-09-12 04:43 PM, Justin Lambert wrote: We are moving to have our nagios servers generate their nagios configs based on what services are installed on specific hosts (as well as the hosts registering themselves). What we have found is that our runtimes have gone through the roof on this and I'm trying to figure out why (summary below from a puppet run). The config pull takes a while, but the majority of the time is spent on the client side. Running puppet with -d has a large chunk of this time with nothing being updated on the screen and one processor core being pegged. We're running 2.6.9 on SL6.0 x86_64. What db backend are you using for stored configs? If you're using the sqlite3 backend, I'd recommend switching to mysql or postgresql. The sqlite3 backend is mainly there for easing puppet dev, but it's way too slow for production use.. I'm not sure if I have an unreasonable number of resources and I need to do things differently or if I have a problem on my client I need to address. Any insight or direction to go down to continue debugging? Normally the client run time shouldn't change much with or without exporting nagios resources, except on the Nagios server (the one extracting the puppet resources). In my experience, exporting native Nagios resources on Nagios clients and collecting them on the Nagios server doesn't seem to be scaling very well. But still, it's usable with around 100 hosts and 500 services.. -- Gabriel Filion -- 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] Slightly OT: Puppet + OpenQRM
On Tue, Sep 6, 2011 at 6:44 PM, treydock treyd...@gmail.com wrote: I've recently been looking to move my KVM management (currently via Puppet and virt-manager) to something web-based and robust (ie Cloud), and came across OpenQRM. Looking at the features list it mentions puppet Class/Machine management. Has anyone that uses Puppet extensively given this a try? I'd like to get input on how this works. The only ENC or GUI interface I've used with Puppet is Foreman (which is awesome btw), but this peaked my interest. Thus far I've tried Cloudstack (a few months ago) and Convirt, both were great, but not what I needed. BTW not sure if you saw it, but foreman supports libvirt/kvm out of the box, and we are working on adding additional actualization management support such as rhevm (once released -- in the upcoming weeks), vmware and ec2. if you have any improvement suggestions, or why foreman was not good enough, would love to hear that.. thanks, Ohad Any input on experiences with OpenQRM as it relates to Puppet would be great, thanks. - Trey -- 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] Cross-nodes modules: howto?
On Tue, Sep 6, 2011 at 3:13 PM, Francis GALIEGUE f...@one2team.com wrote: Let's say I have a web application which I want to deploy separately: * the static content and appropriate configuration on a machine with Apache on it, * the dynamic content and appropriate configuration on a machine with Tomcat on it. Is there a possibility to write a module which takes as an argument the name of the Apache node and the name of the Tomcat node, along with appropriate configurations for Apache and Tomcat, and which would do what is appropriate so that this web application be installed/updated/removed? Thats one of the reasons of why I started the stacker application [1], would be nice to know if it answers your usage case. Screencast here: http://ohadlevy.fedorapeople.org/stacker.ogv Ohad [1] https://github.com/ohadlevy/stacker -- Francis Galiegue ONE2TEAM Ingénieur système Mob : +33 (0) 683 877 875 Tel : +33 (0) 178 945 552 f...@one2team.com 40 avenue Raymond Poincaré 75116 Paris -- 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] Run of Puppet configuration client already in progress
On Wed, Sep 7, 2011 at 9:14 AM, sanjiv singh sanjiv.is...@gmail.com wrote: Hi all, I have deployed puppet 0.25.5 ecosystem. Initially configuration done on client. After some time , as fire following command on client : $ /usr/sbin/puppetd --test --debug . . . notice: Ignoring --listen on onetime run notice: Run of Puppet configuration client already in progress; skipping puppet deamon stopped with above error msg. when there was no puppet process running. it seems , it is becuz of improper shut down of puppet deamon previously. Now when i m tring fire puppet deamon , it unable to start bcuz of some temp file created. what cloud be the issue ? how to resolve it ? puppetd --enable (or just delete the lock file) Ohad thanks, Sanjiv Singh Impetus Infotech -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Slightly OT: Puppet + OpenQRM
On Wed, Sep 7, 2011 at 11:03 PM, linuxbsdfreak linuxbsdfr...@gmail.com wrote: Hi Ohad, Does foreman support Xen?. Honestly, I switched to KVM a few years ago and never looked at Xen again, however, saying that, we support libvirt, so I think it should be straight forward as simply to changing the domain xml template (in vendor/plugins/virt/templates). Ohad Regards, Kevin On 7 Sep., 08:10, Ohad Levy ohadl...@gmail.com wrote: On Tue, Sep 6, 2011 at 6:44 PM, treydock treyd...@gmail.com wrote: I've recently been looking to move my KVM management (currently via Puppet and virt-manager) to something web-based and robust (ie Cloud), and came across OpenQRM. Looking at the features list it mentions puppet Class/Machine management. Has anyone that uses Puppet extensively given this a try? I'd like to get input on how this works. The only ENC or GUI interface I've used with Puppet is Foreman (which is awesome btw), but this peaked my interest. Thus far I've tried Cloudstack (a few months ago) and Convirt, both were great, but not what I needed. BTW not sure if you saw it, but foreman supports libvirt/kvm out of the box, and we are working on adding additional actualization management support such as rhevm (once released -- in the upcoming weeks), vmware and ec2. if you have any improvement suggestions, or why foreman was not good enough, would love to hear that.. thanks, Ohad Any input on experiences with OpenQRM as it relates to Puppet would be great, thanks. - Trey -- 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 athttp://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] Managing dynamic instances with puppet
On 2011 9 1 18:44, Galed Friedmann galed.friedm...@onavo.com wrote: Hello, My organization is currently running a complete production environment on Amazon EC2, and I'm now trying to implement some automations and scaling with puppet. I have several instances which I want them to be almost automatic, meaning that whenever is needed more instances will come up, and when they're not needed they will be stopped. This should eventually be automatically is possible, I don't want to know or care if they came up or down, and especially do not want to configure anything manually when that happens. I currently have a nice puppet configuration, when a node comes up it get's it's entire configuration from puppet, and exports several of it's resources to remote nodes (such as nagios, and also some other instances' /etc/hosts file using the Host resource). This is working fairly well, what I'm still not sure how to perform is node deletion. I want to achieve a way that when a node goes down, it's exported resources will also disappear from the remote instances (meaning nagios will stop monitoring that host and it's Host resource will be deleted from the remote server). The only way I find this possible is by running some cron on the master server that purges the exported resources DB every once in a while and using the purge function on the clients to remove resources that are not longer managed. While this sounds reasonable it scares me a bit because of several issues: - The master will need to purge the DB around the same time the nodes check their manifests again (so I'll have an updated DB all the time) - I also have several unmanaged resources (like other nagios checks that I'm not managing through puppet currently). Will performing a purge on nagios resources will cause ALL existing checks that are not managed by puppet to disappear? Has anyone ever dealt with this kind of dilema? Are there are any other best practices to perform this? I'd really appreciate the help! Yes, you can use puppet report status or last compile time. I currently implemented it via foreman api instead of store configs, but the principal should be the same. Ohad Thanks, Galed. -- 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/-/Ap4R3tDnoMgJ. 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] Deploy an application on multiple hosts as one unit
Hi, I wanted to see if I could deploy an application, which runs on multiple hosts, as a proof of concept, I've created Stacker [1] Screencast [2]* showing it in a high level. Any feedback is appreciated :) thanks, Ohad [1] - https://github.com/ohadlevy/stacker [2] - http://ohadlevy.fedorapeople.org/stacker.ogv * stupid youtube wont understand the video format, (ffmpeg/meconder and friends didn't work either that well) vlc/mplayer seems to play it nicely me is looking for better screencast software on linux. -- 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] Check for dead clients
On Tue, Aug 30, 2011 at 4:12 PM, It Dept i...@ukcrd.com wrote: Hello, Is there a built in way to get notifications about clients which have not updated in a defined time period? For example, if a client is configured to poll the master every hour, and 2 hours elapse without the client polling the master, is there a way to have the master inform us of this failure? Thanks Sounds like one of the tasks foreman [1] was designed for. You can configure email reporting, or view it in the UI, or send alerts to your favorite monitoring software... Ohad [1] - http://theforeman.org -- 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] eggdrop-puppet-notificator
On Wed, Aug 31, 2011 at 2:17 PM, Alexander Fortin
alexander.for...@gmail.com wrote:
Hi folks.
I've just written a small plug-in for Eggdrop:
https://github.com/shaftoe/eggdrop-puppet-notificator
Maybe someone here is running both a puppet master and an eggdrop process on
the same machine and wishes to get notified about missing nodes (via IRC
and email). I like very much that Dashboard tells me which node is missing
for more than 60mins, but I didn't know how to get notified too, so... I'm
sure there are better ways to do it but this was just the easier I've seen,
so of course any comment/bug report etc is very appreciated ;)
nice! any chance you would consider adding a query to foreman?
easy to get that info via:
curl http://foreman/hosts/out_of_sync?format={json,yaml}
Ohad
--
Alexander Fortin
http://about.me/alexanderfortin/
--
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] Announce: Dashboard 1.2.0 is available now
On Sat, Aug 27, 2011 at 2:36 PM, Tim Connors tim.w.conn...@gmail.com wrote: On Fri, 26 Aug 2011, Michael Stahnke wrote: * Dashboard now requires Ruby 1.8.7 to operate I've always found it odd that sysadmins would opt for such an unstable language. One where minor revisions are often backwards incompatible changes to the language. The ruby design seems to this particular sysadmin, to be contraindicative of something that can be well sysadminned. So it seems odd that it's the backbone of such an important sysadmin tool. All distributions have a reasonable method of including a good selection of perl modules. And perl is pretty stable over time. But this choice of not debugging the problems with ruby 1.8.5 leads to it being impossible to host dashboard on redhat 5 entirely. I don't have the freedom of not chosing rhel at work. If I provisioned a new rhel6 server for the new puppet infrastructure, then I'd just be pushing back the problem until next year when dashboard decided to come out with ruby dependencies of 1.8.7. Is there a great need for choosing bleeding edge features of an unstable language for a sysadmin tool that's meant to be around for a long time because of the amount of investment required in setting it up? /rant, part question -- AFAIR, all major distributions (that has a stable long running life cycle) already include ruby 1.87. imho - if you are building new infrastructure today, there is little sense to install it on an obsolete distribution. saying that, you can always use an older version to match your distribution ;) Ohad Tim Connors -- 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] Step by step guide to setting user passwords
On Wed, Aug 3, 2011 at 12:21 PM, Peter Meier peter.me...@immerda.ch wrote:
Can someone walk me through the steps of sending out a password to all
my computers for user student.
I do this a lot:
yes 'PASSWORD' | passwd username
Then you can extract the password from /etc/shadow
also see here:
http://serverfault.com/questions/87874/how-should-someone-create-an-encrypted-password-for-etc-shadow
No need to go over /etc/shadow or use mkpasswd (which is not available
that easy on all distros). How about
# salt=`pwgen 8 1`; pass=`pwgen -s 12 1`;ruby -e puts \
ARGV[0].crypt('\$6\$' ARGV[1] '\$') $pass $salt; echo $pass
$6$eemaihic$3gwFGQxMWE8n/KMZlNe3O9dVoQC5zCXrtabhpCLeDp54eYTGK8WAHovxYZLaQf8YF93Hwfh466CQ966Xoh6O81
FmstT8KObWVu
crypt might yield a different output depending on the c crypt lib, so
in theory it may not work across all os's.
Ohad
?
~pete
--
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] Help setting up Ubuntu preseed for Puppet Clients
On Tue, Aug 2, 2011 at 11:39 PM, Jfro jason.shir...@gmail.com wrote: I have another newbie question: I am installing Ubuntu 10.4 LTS via a preseed file for a classroom computer lab. Can anyone help me with installing Puppet client via the preseed file? Step by step instructions would be greatly appreciated. as Foreman [1] already provides provisioning support for Debian/Ubuntu, you can simply copy and reuse the preseed default templates[2]. Ohad [1] - http://theforeman.org [2] - https://github.com/ohadlevy/foreman/blob/develop/app/views/unattended Ohad Here's what I think I need to do: 1. Install the Puppet package. I'm using the command below. Is this correct? d-i pkgsel/puppet 2. Set up the /etc/puppet/puppet.conf to include the Puppet Master server info. I think I need to host the puppet.conf file on my preseed server and place is on the new machine. What is the command to do this? 3. Have puppet client send it's key to the master. Can I run a late_command script to accomplish this? Can you provide the script? 4. What else am I missing? Sorry I'm such a newbie, but I appreciate your help. This will eventually help manage a great computer lab for the kids. Thanks. -- 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/-/wCO0259HWvoJ. 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/facter and update reporting
On Tue, Jul 26, 2011 at 4:59 PM, Khoury Brazil khoury.bra...@gmail.com wrote: On Mon, Jul 25, 2011 at 10:46 PM, Ohad Levy ohadl...@gmail.com wrote: On Tue, Jul 26, 2011 at 5:04 AM, Khoury Brazil khoury.bra...@gmail.com wrote: On Sat, Jul 23, 2011 at 8:15 PM, Jacob Helwig ja...@puppetlabs.com wrote: On Fri, 22 Jul 2011 19:28:37 -0700, Khoury wrote: Hi All, Does anyone have any experience with debian/ubuntu and or OS X with regard to reporting on updates? I'm interested in getting update (specifically security) states for compliance (SOX, PCI, etc) purposes. I know there's spacewalk for things like this, but I'm kind of hoping to avoid going the centos/redhat route for my servers. I'm thinking of using unattended-upgrade --debug --dry-run on Debian/ Ubuntu and maybe softwareupdate on OS X to build custom facts. a few couple of years ago I built a simple web UI [1] for tracking down packages / versions / hosts. it should probably work, while you can either use mcollective, or a simple cron or whatever to send the packages data into that service. Ohad [1] - https://github.com/ohadlevy/dish That's actually very useful, regardless of whether or not it solves my particular problem. I'm definitely going to have to check it out. I've just played around with it and upgraded it to rails 3, feel free to contact me privately or on irc if you have any issues with it. Ohad Thanks in advance. Best, Khoury Sounds like you want the collection functionality that you get with MCollective. I'm afraid I haven't played around with it as much as I'd like, but I'm sure others can chime in with details. -- Jacob Helwig , | Join us for PuppetConf, September 22nd and 23rd in Portland, OR | http://bit.ly/puppetconfsig ` -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQGcBAEBAgAGBQJOK45iAAoJEHJabXWGiqEBtMgMALpWYg+B9DqmcVgZMkg1sNVo MGQaIXL9WGtZWH37CeTdP92SDIXK2GPUUFL7GZCzEBf0sSAbjg1FI5UaGUduH5/K 6USlI/85NEBdf84iwhJ/MUIKcjaGkYZPlHJe7vFeKry3+TEpPWgNAfXk9s+IoqVS XAECFczwJOJZbgJ9zPG8fayXe5cMjHhvHYvWKO9selMxAVEFkteOamQ/hjKKEb92 C9hKuYOfwOdgodzEPn5KQYb3OQLQ1yqP09mcaKlNjdBoYvGuIUNM0tyBkuH3YqT2 rvLz0cBfrQ4IbTnbI4oLIApzRgqbAwUXP9J2Aou18AydTMhVmLxoBTCsVCz+lG13 WmcgLyc1ly1tzGptDVZc+0z/6cTZSbpUg6qW2JLTEOzKjiR1DhYs8n2MlOuKNE53 FulPKJmeiGAnSTH+noeOlfpSXlkigAVBY+jMs4aUsAUfamEkdSD1cnvZtnDhnee0 XSfGcS6Qmrz2Ghgnb9RH2wbYS+elqsDUrbBa0vBycQ== =QUn5 -END PGP SIGNATURE- Unfortunately mcollective wouldn't really work for me. It would, for servers, for the most part. So I might utilize it for those. But I'm looking at managing OS X clients too, many of which are laptops. My understanding of mcollective is that it requires the connectivity between the servers to be always on. That wouldn't work well for laptops. Thanks for the recommendation though. I'd completely spaced that mcollective existed. -- 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. -- 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/facter and update reporting
On Tue, Jul 26, 2011 at 5:04 AM, Khoury Brazil khoury.bra...@gmail.com wrote: On Sat, Jul 23, 2011 at 8:15 PM, Jacob Helwig ja...@puppetlabs.com wrote: On Fri, 22 Jul 2011 19:28:37 -0700, Khoury wrote: Hi All, Does anyone have any experience with debian/ubuntu and or OS X with regard to reporting on updates? I'm interested in getting update (specifically security) states for compliance (SOX, PCI, etc) purposes. I know there's spacewalk for things like this, but I'm kind of hoping to avoid going the centos/redhat route for my servers. I'm thinking of using unattended-upgrade --debug --dry-run on Debian/ Ubuntu and maybe softwareupdate on OS X to build custom facts. a few couple of years ago I built a simple web UI [1] for tracking down packages / versions / hosts. it should probably work, while you can either use mcollective, or a simple cron or whatever to send the packages data into that service. Ohad [1] - https://github.com/ohadlevy/dish Thanks in advance. Best, Khoury Sounds like you want the collection functionality that you get with MCollective. I'm afraid I haven't played around with it as much as I'd like, but I'm sure others can chime in with details. -- Jacob Helwig , | Join us for PuppetConf, September 22nd and 23rd in Portland, OR | http://bit.ly/puppetconfsig ` -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQGcBAEBAgAGBQJOK45iAAoJEHJabXWGiqEBtMgMALpWYg+B9DqmcVgZMkg1sNVo MGQaIXL9WGtZWH37CeTdP92SDIXK2GPUUFL7GZCzEBf0sSAbjg1FI5UaGUduH5/K 6USlI/85NEBdf84iwhJ/MUIKcjaGkYZPlHJe7vFeKry3+TEpPWgNAfXk9s+IoqVS XAECFczwJOJZbgJ9zPG8fayXe5cMjHhvHYvWKO9selMxAVEFkteOamQ/hjKKEb92 C9hKuYOfwOdgodzEPn5KQYb3OQLQ1yqP09mcaKlNjdBoYvGuIUNM0tyBkuH3YqT2 rvLz0cBfrQ4IbTnbI4oLIApzRgqbAwUXP9J2Aou18AydTMhVmLxoBTCsVCz+lG13 WmcgLyc1ly1tzGptDVZc+0z/6cTZSbpUg6qW2JLTEOzKjiR1DhYs8n2MlOuKNE53 FulPKJmeiGAnSTH+noeOlfpSXlkigAVBY+jMs4aUsAUfamEkdSD1cnvZtnDhnee0 XSfGcS6Qmrz2Ghgnb9RH2wbYS+elqsDUrbBa0vBycQ== =QUn5 -END PGP SIGNATURE- Unfortunately mcollective wouldn't really work for me. It would, for servers, for the most part. So I might utilize it for those. But I'm looking at managing OS X clients too, many of which are laptops. My understanding of mcollective is that it requires the connectivity between the servers to be always on. That wouldn't work well for laptops. Thanks for the recommendation though. I'd completely spaced that mcollective existed. -- 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] facts_terminus = rest
On 2011 7 15 22:22, Glenn Bailey replic...@dallaslamers.org wrote: I scrapped the idea and just gonna go with using activemq and connecting to the DB directly. I think this may scale better in the long run anyway ;-) Not to hijack the thread, but multiple puppetmasters facts, rest etc is supported for a long time with foreman. Ohad On Thu, Jul 14, 2011 at 10:09 PM, Scott Smith sc...@ohlol.net wrote: I personally couldn't get it to work (no facts in Dashboard), but only spent a short amount of time on it. On Thu, Jul 14, 2011 at 1:50 PM, Glenn Bailey replic...@dallaslamers.org wrote: Anyone using this? I'm trying to setup a separate inventory server for multiple puppet masters to report back. For testing purposes I have in my auth.conf: path /facts auth any method find, search allow * Then on the slave puppet masters I have in the puppet.conf [master] section: facts_terminus = rest inventory_server = SERVER.DOMAIN.BLAH inventory_port = 8140 Then when I run I puppet agent --test, I simply get the following: err: Could not retrieve catalog from remote server: Error 400 on SERVER: certificate verify failed Throwing the puppet master into debug mode and I see the exact same error w/o anything else. I can't seem to find any documentation on this sans the standard: http://docs.puppetlabs.com/guides/inventory_service.html I saw a previous mention about a possible bug on the mailing list here: http://groups.google.com/group/puppet-users/browse_thread/thread/682402305dc01ea9 But never saw anything else .. :-( Does the master fact server need to be a certificate authority as well? -- I've seen things you people wouldn't believe. Attack ships on fire off the shoulder of Orion. I watched C-beams glitter in the dark near the Tannhauser gate. All those moments will be lost in time... like tears in rain... Time to die. -- 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. -- I've seen things you people wouldn't believe. Attack ships on fire off the shoulder of Orion. I watched C-beams glitter in the dark near the Tannhauser gate. All those moments will be lost in time... like tears in rain... Time to die. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: A Question about mixing Puppet with other things
On Tue, Jul 12, 2011 at 6:26 PM, Dan White y...@comcast.net wrote: This tells me RedHat picked Foreman over Cobbler. It does not tell me WHY. Their reasons may not apply to my situation. I am not trying to be difficult, but I find that I cannot accept an opinion on a technical issue without technical information to back it up. Also, this is for my job, so I need to be able to justify my decision with more than The folks on the puppet mailing list told me to do it this way. I think I can try to break it down in different ways. First, Foreman was created after realizing that Just pxe booting, or just using puppet, does not cover everything. With the notion of self service (e.g. people who don't know how to use puppet and or lack access to your manifests) foreman was aiming to bridge that gap. Therefore, it was designed as a web service from day one, taking into account multiple users, permissions, different views etc etc. Another goal, was that you wont need to open 5 different consoles in order to provision a host, that eventually lead to integrating: dns, dhcp, tftp, puppetca, virtual machine creation, puppet class assignments, hierarchical variables support, audit log etc all in one place. Foreman users have come up with interesting usages cases, from using it purely for monitoring puppet to ramp up whole datacenters. its API is used today to feed external monitoring services, provision hosts, update on the fly many hosts, and there is even a mobile app who utilize foreman. Foreman is also not restricted to a specific subnet, datacenter etc, rather is supposed to work across network segments and different backend software (e.g. ms dns server, isc dhcp server etc) using its smart proxy architecture. My hope, is that by using Foreman, you can provide your users much better service, taking you out of the deployment loop, e.g. You users can consume your services, without you being actively part of it. I obviously didnt cover every single aspect of foreman, but I hope it gives you some useful information, if not, simply ask, or join our mailing list or irc room (#theforeman) to ask more questions. Ohad “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin Hobbes) - Brian b...@uga.edu wrote: On Jul 7, 2:47 pm, Dan White y...@comcast.net wrote: In Pro Linux System Administration Mr. Turnbull discusses Cobbler and Puppet In Pro Puppet he discusses Foreman and Puppet. Would anyone out there be willing and able to talk about the differences between Cobbler and Foreman as they relate to Puppet and what factors I should consider in choosing one of them ? Red Hat is using Foreman in CloudForms System Engine, their successor to Satellite. I'd take this as a strong vote of confidence in Foreman. https://www.redhat.com/archives/spacewalk-list/2011-July/msg00019.html All the best, Brian -- 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] Re: A Question about mixing Puppet with other things
On Tue, Jul 12, 2011 at 10:53 PM, Scott Smith sc...@ohlol.net wrote: Doesn't the Foreman use Cobbler for managing PXE and Kickstart? not at all. Ohad -scott On Tue, Jul 12, 2011 at 8:26 AM, Dan White y...@comcast.net wrote: This tells me RedHat picked Foreman over Cobbler. It does not tell me WHY. Their reasons may not apply to my situation. I am not trying to be difficult, but I find that I cannot accept an opinion on a technical issue without technical information to back it up. Also, this is for my job, so I need to be able to justify my decision with more than The folks on the puppet mailing list told me to do it this way. “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin Hobbes) - Brian b...@uga.edu wrote: On Jul 7, 2:47 pm, Dan White y...@comcast.net wrote: In Pro Linux System Administration Mr. Turnbull discusses Cobbler and Puppet In Pro Puppet he discusses Foreman and Puppet. Would anyone out there be willing and able to talk about the differences between Cobbler and Foreman as they relate to Puppet and what factors I should consider in choosing one of them ? Red Hat is using Foreman in CloudForms System Engine, their successor to Satellite. I'd take this as a strong vote of confidence in Foreman. https://www.redhat.com/archives/spacewalk-list/2011-July/msg00019.html All the best, Brian -- 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] A Question about mixing Puppet with other things
On Thu, Jul 7, 2011 at 9:47 PM, Dan White y...@comcast.net wrote: In Pro Linux System Administration Mr. Turnbull discusses Cobbler and Puppet In Pro Puppet he discusses Foreman and Puppet. Would anyone out there be willing and able to talk about the differences between Cobbler and Foreman as they relate to Puppet and what factors I should consider in choosing one of them ? Not sure if I can describe every change, but I can say that foreman was designed to work with Puppet from day one. Feel free to review Foreman [1] and its features [2] to decide for your self. Ohad [1] - http://theforeman.org [2] - http://theforeman.org/projects/foreman/wiki/Features I want to use Puppet with Something-Else to manage a group of servers and desktops and other machines in a centralized, automated, configurable and repeatable fashion. I want to be able to do operating system installations, patches and/or updates, and maintenance activity. Thanks. “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin Hobbes) -- 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] howto trigger action on another client
On Fri, Jun 24, 2011 at 11:14 AM, Andreas Kuntzagk andreas.kuntz...@mdc-berlin.de wrote: Hi, I want to automate installation of GridEngine with puppet. GE comes with some prepared script for automatic installation. Unfortunately this is to be run on the GE master to install the executions host (=clients). (This then will run some commands on the exec host via ssh) So from puppet's perspective if an agent on an execution host notices that GE is not installed but should it has to tell the agent on the GE master to run the install script. Is there an easy (puppet) way to do it? My idea is to have the exec host write its name into a file hosts_to_install on a common NFS and have the master check that file. But maybe there are better ways. Does anybody here has some other GE related recipes? regards, Andreas and another idea, if you are using foreman[1], you can collect all hosts which are member of the GE group. You could also ask for their facts, so you could build a meaningful GE configuration. see this puppet function [2] Ohad [1] - http://theforeman.org [2] - https://github.com/ohadlevy/puppet-foreman/blob/master/foreman/lib/puppet/parser/functions/foreman.rb -- 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 CA expired
On Mon, Jun 27, 2011 at 4:52 PM, j...@squirk.org j...@squirk.org wrote: Le 16/06/2011 20:12, Nathan Clemons a écrit : Thanks. I think having to go out across the board once every 5 years is quite acceptable, although advance warning from the master that it's going to happen would definitely be a good thing. Jean: Kudos to running Puppet for 5 years! :) yes i was planning to install cfengine when the first puppet appeard, i really liked the way of thinking of the creator that seemed to me a very good approach of the issue so i jumped in. as i needed to make change to all the nodes i simply recreated a 20year CA and got to everynode removing the ssl certs and sign again all nodes on the master. If someone knows how to spot a client coming to puppet and failing the ssl handcheck it would help a lot to spot the one i missed out if any ! :) one simple way is simply to look at foreman puppet certificate list. you can also query it via the api, and evaluate the certificate expire date. Ohad regards, Jean. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet Dashboard without MySQL
On Mon, Jun 27, 2011 at 9:40 PM, Douglas Garstang doug.garst...@gmail.com wrote: On Mon, Jun 27, 2011 at 10:49 AM, Nan Liu n...@puppetlabs.com wrote: On Mon, Jun 27, 2011 at 10:35 AM, Douglas Garstang doug.garst...@gmail.com wrote: Actually, to be more specific, our nodes are stored in yaml files, and I'd like to keep them that way, and continue to have the yaml files as the source of truth, not a MySQL database. Puppet dashboard should read from those yaml files. Doug. You can use Dashboard in any of the following combination: ENC Reporting ENC + Reporting. Kinda wanted to use it for more than reporting. Shame, really. It would be nice if there was a tool that could translate any external node format. not sure what do you mean by translate, but Foreman can import information from other ENC's Ohad 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. -- 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.
