2009/12/1 Ohad Levy <ohadl...@gmail.com>: > Hi, > > Why not use cobbler external nodes feature to avoid all of this all together
Because right now only some nodes will use cobbler, I already have >250 hosts and I don't want to change all my setup > sounds to me that you should provision your nodes when they have a purpose > if they don't have one, they should keep getting the default node. They get the default node, I just need to identify them using a unique name because I create entries in my monitoring system (and some other things that should be unique in exported resources) Basically I need this to setup a public remote installation system based on gPXE+Cobbler+Puppet. When a server runs gPXE it will boot remotelly from my server, I will provision the OS using Cobbler, it will install and setup Puppet, but when I run puppet, all clients use the "default" node and I have no way to distinguish them. > if its not possible with cobbler, you might take a look at > http://theforeman.org Hmmm... interesting is it a OS provisioning system tied to Puppet? > as far for your question, I think you need a custom fact. That's what I thought, but it's ugly. I'm reading the private_key file from /var/lib/puppet/state/{state,localconfig}.yaml and it works the first time, but if I run puppetd later with a different --fqdn it doesn't change in those files. And I think it's very uglly to read the --fqdn from "ps ax | grep puppetd" Salu2! -- Miguel Armas <k...@canarytek.com> CanaryTek Consultoria y Sistemas SL ModularIT http://www.modularit.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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
