puppet 2.6.8 I have been going over and over ''Pro Puppet'' book and http://projects.puppetlabs.com/projects/puppet/wiki/LDAP_Nodes /etc/puppet/puppet.conf includes in the [master] section: node_terminus = ldap ldapserver = ubuntu.ttinet ldapbase = ou=Hosts,dc=ttinet,dc=local and LDAP contains the below (derived from an ldapsearch) # andromeda.ttinet, Hosts, ttinet.local dn: cn=andromeda.ttinet,ou=Hosts,dc=ttinet,dc=local cn: andromeda.ttinet description: Andromeda objectClass: device objectClass: top objectClass: puppetClient objectClass: ipHost ipHostNumber: VALID_LOCAL_IP puppetClass: base environment: production I''ve restarted both puppetmaster and apache (Dashboard is running on passenger) and still, I don''t see the above system in ''Nodes'' though I haven''t run or even installed puppet on that system. Shouldn''t it show up in Dashboard as a node that has never reported? I''m trying to figure out how to get Dashboard to import the ENC ''nodes'' from LDAP. Logs don''t show any errors and I do have ruby-ldap installed... # ruby -rldap -e "puts :installed" installed -- Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Jun 22, 2011, at 2:37 PM, Craig White wrote:> I''ve restarted both puppetmaster and apache (Dashboard is running on passenger) and still, I don''t see the above system in ''Nodes'' though I haven''t run or even installed puppet on that system. Shouldn''t it show up in Dashboard as a node that has never reported? > > I''m trying to figure out how to get Dashboard to import the ENC ''nodes'' from LDAP.Someone can correct me if I’m wrong, but I believe the Dashboard is just another possible destination for reports. It has no awareness of the Puppetmaster or it’s configuration (like `node_terminus`). The Puppetmaster, on the other hand, does know about the Dashboard (via the `reports` setting) and can send reports there, but not until after there’s something to report (which would be a Puppet run on that node). So I think what you’re seeing is expected behavior. The node should show up after its first Puppet run. If you want it to be more automatic, you may have to write something that queries LDAP and modifies the MySQL database. If you use Python, I’ve got a library that simplifies getting servers out of LDAP. Let me know if you’re interested. -- Rob McBroom <http://www.skurfer.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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Jun 29, 2011, at 8:23 AM, Rob McBroom wrote:> On Jun 22, 2011, at 2:37 PM, Craig White wrote: > >> I''ve restarted both puppetmaster and apache (Dashboard is running on passenger) and still, I don''t see the above system in ''Nodes'' though I haven''t run or even installed puppet on that system. Shouldn''t it show up in Dashboard as a node that has never reported? >> >> I''m trying to figure out how to get Dashboard to import the ENC ''nodes'' from LDAP. > > Someone can correct me if I’m wrong, but I believe the Dashboard is just another possible destination for reports. It has no awareness of the Puppetmaster or it’s configuration (like `node_terminus`). The Puppetmaster, on the other hand, does know about the Dashboard (via the `reports` setting) and can send reports there, but not until after there’s something to report (which would be a Puppet run on that node). > > So I think what you’re seeing is expected behavior. The node should show up after its first Puppet run. > > If you want it to be more automatic, you may have to write something that queries LDAP and modifies the MySQL database. If you use Python, I’ve got a library that simplifies getting servers out of LDAP. Let me know if you’re interested.---- I am still uncertain whether we will have enough servers to actually bother with maintaining hosts in LDAP just for puppet. I demonstrated OpenLDAP for my boss and we are discussing rfc2307 implementation at which point I would have to maintain hosts in LDAP and it might make sense to tie them all in to puppet. I think you confirmed that I am not seeing nodes from LDAP in the Dashboard not because of anything I am doing wrong so I''ll leave it for now. Thanks Craig -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Jun 29, 2011, at 11:40 AM, Craig White wrote:> I am still uncertain whether we will have enough servers to actually bother with maintaining hosts in LDAP just for puppet.Might not be worth it if it’s “just for puppet”, but once you have everything in LDAP, there are limitless possibilities for automation. I’ll just paste something from one of my previous messages on this list:> … if you put details for your systems in LDAP, there’s so so much you can automate outside of Puppet as well. Every scripting language understands LDAP, so use your imagination. > > One good example is a web-based front-end to allow manger types to view the information (as sort of an inventory tracking tool). The reason databases like this get out of date is that keeping them current is a pain. The only way it works is if *not* keeping it current is even *more* painful. Puppet can help with this. If you don’t go into LDAP and add a node and classify it as a web server, it literally won’t function as a web server. So when a human looks at the information about a system via the web, they know it has to be correct. > > We also use information in LDAP to configure our monitoring system. Again, this keeps you on your toes. If you don’t add it to LDAP, it doesn’t get monitored. If you don’t remove it from LDAP when it’s gone, you’ll get annoyed with alerts that it went down. > > And there are the daily tasks that can be sped up, like connecting (in a loop or via cluster SSH) to all systems with certain attributes. Answering the constant requests for “a list of all the XYZ servers with ABC”, running `ssh-keyscan`, populating a local file for hostname completion in your shell, etc.And to add to that, I’ve recently started looking at Fabric which allows you define a list of hosts in different “roles”. I can have these lists generated in real-time based on LDAP when the command runs. -- Rob McBroom <http://www.skurfer.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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.