Feature #1562

Auto-assign a 'finish deploy' class to new hosts

Added by David Swift over 2 years ago. Updated over 2 years ago.

Status:NewStart date:03/30/2012
Priority:NormalDue date:
Assigned To:Ohad Levy% Done:

80%

Category:Unattended installations
Target version:-
Difficulty:medium Bugzilla link:
Found in release: Pull request:
Story points-
Velocity based estimate-

Description

When using rackspace, internap, or even EC2, the machines come pre-loaded with a base set of packages. The first thing I tend to do with one of these machines is to assign it a bootstrap class, and have it brought up to my current package set, before I assign it any other classes.

For instance, in my 0.4.2 Foreman setup, I have a userdata script that executes a curl call to Foreman from the new instance when it is done with cloud-init. The curl call adds the new host in via the Foreman API. Once I see this host in Foreman, I start assigning classes to it, and then kickoff puppetrun.

It would be handy if, when a new machine notifies Foreman that it is now present, that machine could be assigned to a class based upon either:
1. An API call, or
2. Assignment by rules similar to the TFTP rules for kickstart and such.

and then the new instance can continue the bootstrapping on it's own.

History

#1 Updated by Ohad Levy over 2 years ago

  • % Done changed from 0 to 80
  • Difficulty set to medium

nearly done, prob would be part of the ec2 branch with samples for ubuntu/deb/rhel/fedora

#2 Updated by Ohad Levy over 2 years ago

  • Target version deleted (1.0)

Also available in: Atom PDF