Feature #3848
Puppet should natively support bootstrapping from scratch.
| Status: | Needs More Information | Start date: | 05/22/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | agent | |||
| Target version: | - | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | ||||
Description
Automatically provisioning puppet clients could be really simple if we had these features.
options: —bootstrap (defaults to no) —bootstrap_environment (defaults to bootstrap)
If these options are on, the client connects to the puppet server and requests a catalog for the bootstrap_environment. If that completes successfully, then the client does another run with whatever settings, plugins, config files have been placed down by the bootstrap run.
History
#1
Updated by R.I. Pienaar about 3 years ago
This would be nice, i do this with an environment now but would be great to have the 2nd run happen in a less sucky way
#2
Updated by James Turnbull about 3 years ago
- Status changed from Unreviewed to Needs Decision
- Assignee set to Luke Kanies
+1 from me.
#3
Updated by Luke Kanies about 3 years ago
- Category set to agent
- Status changed from Needs Decision to Accepted
- Assignee deleted (
Luke Kanies)
I kind of hate this, but I’d rather move here and get it wrong than keep stymying (yes, that’s spelled correctly) progress.
#4
Updated by Nigel Kersten almost 3 years ago
I kind of hate it too.
What if instead we had these features:
- server can set environment of client via node classifier
- manifests can contain an instruction to the client to issue another puppet run after the current one has succeeded
Then we wouldn’t need to deal with this hacky method.
#5
Updated by Nigel Kersten over 1 year ago
- Status changed from Accepted to Needs More Information
That guy who filed this totally needed to provide more info.