Issue #2128 has been updated by Jacob Helwig.
Regarding the `auth.conf` question: Looks like we forgot to mention this here
in the ticket, even though we put it in the commit message:
commit 1c70f0ce54022b55119b9e2d6d60cd1ae9bc019e
Author: Nick Lewis <[email protected]>
Date: Thu Jun 2 16:24:16 2011
(#2128) Add support for setting node name based on a fact
This adds the node_name_fact setting, which specifies a fact to use to
determine the node name. This allows dynamically determining the node
name
without having to modify puppet.conf or command line options.
Using this setting requires modifying auth.conf to allow nodes to
request
catalogs not matching their certnames.
For example, this would allow any authenticated node to retrieve any
catalog:
# $confdir/auth.conf
path ~ /catalog/.+
allow *
The node_name_fact and node_name_value options are mutually exclusive,
because
it is ambiguous which setting should take precedence.
Paired-With: Jacob Helwig <[email protected]>
Regarding 0.24.8: The change as written requires agent/master combinations
where both have the change, so 0.24.8 won't work.
----------------------------------------
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.
