Issue #2128 has been updated by Nick Lewis. Status changed from Accepted to Merged - Pending Release
Pushed this to 2.6.x in commit:3d09ca82e57d0c8836b77623d876cd5dc9a3a5e6. This provides settings node_name_value and node_name_fact. The node_name_value defaults to certname, and is used as the catalog requested by the agent. node_name_fact specifies a fact to use to determine the node_name_value. The two settings are mutually exclusive, because it would be ambiguous which ought to take precedence. The node_name_value is used for everything except authentication/authorization. That means it is the "host" referred to in a report, the name under which fact and node YAML are saved, etc. This name should still be unique for each node. It may also be good to deprecate the node_name setting, which is rather misleading, and eventually repurpose it for what is currently node_name_value. ---------------------------------------- Feature #2128: Allow arbitrary fact as node_name identifier https://projects.puppetlabs.com/issues/2128 Author: Bill Bartlett Status: Merged - Pending Release Priority: High Assignee: Nick Lewis 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.
