User story #5037: Add a system variable RUDDER_SERVER_ROLES that describes the roles of the systems, and webapp properties to override them (with 5 roles) - Rudder - Issue Tracker

Actions

Copy link

User story #5037

closed

User story #4928: Allow splitting Rudder into independent role-based entities

Add a system variable RUDDER_SERVER_ROLES that describes the roles of the systems, and webapp properties to override them (with 5 roles)

Added by Nicolas CHARLES over 10 years ago. Updated over 9 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

Jonathan CLARKE

Category:

Web - Config management

Target version:

2.11.0~beta1

Pull Request:

https://github.com/Normation/rudder/p...

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

This system variable would contain, in a key:value form, the roles:hostname for:

rudder-inventory-endpoint
    rudder-inventory-ldap
    rudder-db
    rudder-webapp
    rudder-front

The values would be gathered from the roles of the system (from inventory), or could be overriden by webapp properties, that would be:

rudder.server-roles.ldap
    rudder.server-roles.db
    rudder.server-roles.front
    rudder.server-roles.webapp
    rudder.server-roles.inventory-endpoint

They could take two values, either autodetect (so from the inventories), or specific values

this ticket is like #5016, but with an extra role; for the sake of tracability, everything is listed there

Actions

Copy link

Updated by Nicolas CHARLES over 10 years ago

Nicolas CHARLES wrote:

This system variable would contain, in a key:value form, the roles:hostname for:

rudder-inventory-endpoint
rudder-ldap
rudder-db
rudder-webapp
rudder-front

The values would be gathered from the roles of the system (from inventory), or could be overriden by webapp properties, that would be:

rudder.server-roles.ldap
rudder.server-roles.db
rudder.server-roles.front
rudder.server-roles.webapp
rudder.server-roles.inventory-endpoint

They could take two values, either autodetect (so from the inventories), or specific values

this ticket is like #5016, but with an extra role; for the sake of tracability, everything is listed there