Feature #7385

design a concept of deployment object

Added by Ohad Levy about 8 years ago. Updated about 4 years ago.

Target version:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:


as a user I would like to:

Create a new deployment type
- Assign hostgroups (and maybe config groups?) which are part of this deployment type
- assign allow compute resources / bare metal discovery per hostgroup
- assign parameters across the deployment, define required parameters per deployment etc
- assign deployment order (which hostgroup is needed first?)
- assign minimum number of hosts per hostgroup/deployment

I'm sure there are more, some background can be used from both stacker (and maybe the engine branch -> and staypuft (

Related issues

Has duplicate Foreman - Support #2276: Foreman should support multiple resource creation definitionRejected2013-03-04


#1 Updated by Marek Hulán about 8 years ago

also to consider: networking layout (subnet roles per deployment), management of interfaces, dynamic puppet parameter values based on these information

#2 Updated by Ohad Levy about 8 years ago

  • Target version set to 1.7.3

#3 Updated by Dominic Cleal about 8 years ago

  • Target version changed from 1.7.3 to 1.7.2

#4 Updated by Romain Vrignaud almost 8 years ago

  • Has duplicate Support #2276: Foreman should support multiple resource creation definition added

#5 Updated by Daniel Lobato Garcia almost 8 years ago is worth considering in my opinion. It has a way of creating providers for new resources, is cloud agnostic and enables multiple providers to be composed. Since one of the strongest points of Foreman is precisely that I think there's a good chance we can use to define Foreman deployments.

#6 Updated by Tomer Brisker about 4 years ago

  • Target version deleted (1.7.2)

Also available in: Atom PDF