Issue #2128 has been updated by Jeff McCune.

# auth.conf #

Jacob,

The auth.conf setting you mentioned in the commit history actually breaks 
"normal" Puppet Agents that have a certificate name matching their node name.

This is the auth.conf I'm using at a site that uses both certificate names 
matching node names AND a common certificate named 'all-catalog-access'.

<pre>
# allow nodes to retrieve their own catalog (ie their configuration)
path ~ ^/catalog/([^/]+)$
method find
allow $1
allow all-catalog-access
</pre>

This is necessary because only the FIRST match is used to authenticate clients 
in auth.conf as per the [REST Access Control 
documentation](http://docs.puppetlabs.com/guides/rest_auth_conf.html)
----------------------------------------
Feature #2128: Allow arbitrary fact as node_name identifier
https://projects.puppetlabs.com/issues/2128

Author: Bill Bartlett
Status: In Topic Branch Pending Merge
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.

Reply via email to