Feature #564

Implement OUs hierarchy to allow reusing (host) groups with client/OU specific classes and parameters.

Added by Marcello de Sousa over 2 years ago. Updated 6 months ago.

Status:New Start:01/04/2011
Priority:Normal Due date:
Assigned to:Amos Benari % Done:

0%
Category:-
Target version:-
Backlog:Yes Difficulity:
Votes: 0

Description

This could help solving the following example:
I have the following types of hosts:

- hostA1...hostA10 - Front-end running apache + squid + iptables + auth daemon + parameters client1
- hostB1...hostB5 - Front-end running tomcat + squid + iptables + auth daemon + parameters client1
- hostC - Back-end CMS server running apache + squid + auth daemon + parameters client1
- hostD - DB server running mysql + auth daemon + parameters client1

Now I want to create the same environment for client2, so everything should be the same except the "parameters"

From the IRC discussion:

<ohadlevy> marcellods: so you want to include them all in another hostgroup, just that you could share the params?
and what you do today, is simulating that, simply by riding the domain concept to do the same, 
and I think that the right concept, is an organization, where each org is a different customer

Related issues

related to Foreman - Feature #1578: Implement organizations and extend environments in Foreman Closed 04/18/2012

History

Updated by Ohad Levy over 2 years ago

  • Target version deleted (0.2)

this will probably make it at the next release

Updated by Ohad Levy almost 2 years ago

  • Category deleted (External Nodes)
  • Backlog changed from No to Yes

Updated by Ohad Levy 10 months ago

  • Assigned to changed from Ohad Levy to Greg Blomquist
  • Target version set to 1.1

Updated by Ohad Levy 6 months ago

  • Assigned to changed from Greg Blomquist to Amos Benari
  • Target version deleted (1.1)

we are going to merge first Orgs and locations support first, then we'll add hierarchy.

Also available in: Atom PDF