Issue #2128 has been updated by Jacob Helwig.
Jeff McCune wrote: > > OK, could we please use the node id and node_name terms for clarity? > No, because they only perpetuate an existing conflation of concepts. "node name" as you have described it is simply the "certificate name", and should never be confused with the "node name", and should never be (directly) used for identifying the agent to the master. The "node name" is a completely separate entity (though historically wasn't represented as such), that just happens to default to the value of the "certificate name". "node identifier" is the "node name". After the changes that Nick and I have made will be represented on its own (though will still default to the value of the "certificate name"). The pre-existing "node_name" setting only confuses matters, and should be deprecated under its current name, since it isn't actually about setting the node name, but about how we generate the list of "fallback node names" to use when doing node lookups on the master. (See: `lib/puppet/node.rb`) ---------------------------------------- Feature #2128: Allow arbitrary fact as node_name identifier https://projects.puppetlabs.com/issues/2128 Author: Bill Bartlett Status: Accepted Priority: High Assignee: Category: node Target version: 2.6.x Affected Puppet version: 0.24.7 Keywords: Branch: Currently, the only fact available as a node_name identifier is the hostname. I would like to have the capability of having any fact be the node_name identifier. Use Case: The reason this discussion came about is EC2. When an EC2 node is brought up, the hostname is not known. If we were to have a large, auto-scaling infrastructure, it is currently very difficult (impossible?) to automate bringing these EC2 nodes into puppet. One possible solution is to allow any fact as a node_name, and then for each particular EC2 instance type that one would need scaling (apache, memcache, mysql all come to mind among many others), the AMI would be customized with a custom fact. An example could be a fact called "hostclass" that would then be set to "ec2_apache", "ec2_memcache", or similar. This allows the auto-created machine, which we would otherwise be unable to differentiate from any other EC2 node, access to puppet in an automated way. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
