Project

General

Profile

Actions

Feature #564

closed

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

Added by Marcello de Sousa almost 14 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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 2 (0 open2 closed)

Related to Foreman - Feature #1578: Implement organizations and extend environments in ForemanClosedAmos BenariActions
Related to Foreman - Feature #3912: Add ability for locations / organizations to inherit from a parent location / organizationClosedJoseph MagenActions
Actions

Also available in: Atom PDF