The Puppet Labs Issue Tracker has Moved:

Feature #7215

Add node classification to the `puppet node init` action.

Added by Anonymous over 3 years ago. Updated about 1 year ago.

Status:ClosedStart date:04/22/2011
Priority:NormalDue date:
Assignee:-% Done:


Category:cloud provisioner
Target version:-
Keywords: cloud_provisioner Affected URL:
Branch: Affected PE version:

We've Moved!

Ticket tracking is now hosted in JIRA:

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


This will close up the bulk of the CloudPack bootstrapping problem.

Related issues

Related to Puppet Enterprise (Public) - Feature #7508: Add FOSS Puppet installation to CloudPack bootstrap process Closed 05/12/2011
Related to Puppet Enterprise (Public) - Feature #8284: node classification should be based on facts Needs More Information 07/07/2011


#1 Updated by Jeff McCune over 3 years ago

  • Project changed from Puppet to Cloud-Provisioner

#2 Updated by Jeff McCune over 3 years ago

  • Assignee deleted (Anonymous)
  • Roadmapped set to No

Nice to have for release

Dan and I believe this is a “nice to have” for release, but not required.

#3 Updated by Nigel Kersten over 3 years ago

  • Category set to cloudpack

#4 Updated by Dan Bode about 3 years ago

  • Status changed from Accepted to Closed

The init method has actually had done node classification for a while.

#5 Updated by Charlie Sharpsteen about 1 year ago

  • Project changed from Cloud-Provisioner to Puppet Enterprise (Public)
  • Category deleted (cloudpack)

#6 Updated by Kenn Hussey about 1 year ago

  • Category set to cloud provisioner

Also available in: Atom PDF