Issue #2128 has been updated by Nick Lewis.
James Turnbull wrote: > I think the part that has me befuddled is the code in the names method in > lib/puppet/node.rb. I am confused how this now relates to the changes in > this ticket. That code is trying to infer other possible names for the node, when determining which node declaration in the manifests to use. In addition to the node name itself (previously `certname`, now `node_name_value`), it will use each prefix of the fqdn. If the fqdn isn't available, it will construct one by joining the hostname and the domain. The primary effect is that a node with the fqdn: foo.example.lan will have node declarations searched for in this order: a) if the `node_name` setting on the master is 'cert", then whatever is specified as `node_name_value`. Otherwise, the value of the 'hostname' fact. b) 'foo.example.lan' c) 'foo.example' d) 'foo' In the case where `node_name_value` isn't anything remotely related to the hostname, these don't make a lot of sense as fallbacks. In that case, the `strict_hostname_checking` setting can be enabled to only allow `node_name_value` as a valid node name. ---------------------------------------- Feature #2128: Allow arbitrary fact as node_name identifier https://projects.puppetlabs.com/issues/2128 Author: Bill Bartlett Status: Accepted 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.
