Actions
Feature #564
closedImplement OUs hierarchy to allow reusing (host) groups with client/OU specific classes and parameters.
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
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
Updated by Ohad Levy over 13 years ago
- Target version deleted (
0.2)
this will probably make it at the next release
Updated by Ohad Levy about 12 years ago
- Assignee changed from Ohad Levy to Greg Blomquist
- Target version set to 1.1
Updated by Ohad Levy almost 12 years ago
- Assignee 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.
Updated by Ohad Levy over 10 years ago
- Related to Feature #3912: Add ability for locations / organizations to inherit from a parent location / organization added
Updated by Ohad Levy over 10 years ago
- Description updated (diff)
- Status changed from New to Closed
- Assignee deleted (
Amos Benari)
Now, with a combination of smart/class parameters, hostgroup, orgs and location nesting, you can get the requested feature.
Closing :)
Actions