Rudder

Actions

User story #4654

closed

Added by Matthieu CERDA over 10 years ago. Updated over 9 years ago.

Status:

Released

Priority:

Assignee:

Matthieu CERDA

Category:

Packaging

Target version:

Pull Request:

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

Nowadays, we assume that the user will always use rudder-server-root and rudder-agent as main entry points to install Rudder.

We should at least offer alternatives to have, independently:

Installing rudder-server-root obviously installing the three of'em :)

Subtasks 9 (0 open — 9 closed)

User story #4666: Segment the packaging into independent role-based entities (integration)	Released	Jonathan CLARKE	2014-03-24	Actions
User story #4776: Add rudder-reports dependency to rudder-root-server	Released	Jonathan CLARKE	2014-04-29	Actions
User story #4986: Move rudder-init.sh, rudder-node-to-relay and rudder-root-rename to rudder-webapp package	Released	Jonathan CLARKE	2014-06-09	Actions
Bug #5007: rudder-init and rudder-upgrade scripts are missing exec permissions	Released	Nicolas CHARLES	2014-06-12	Actions
Bug #5009: rudder-init should create inputs directories if needed (and packages should not)	Released	Matthieu CERDA	2014-06-12	Actions
User story #5022: Move rudder-passwords.conf to rudder-webapp package	Released	Nicolas CHARLES	2014-06-13	Actions
User story #5039: Adapt rudder-init and rudder-upgrade to use rudder-server-roles.conf for initialization	Released	Nicolas CHARLES	2014-06-16	Actions
User story #5040: Adapt rudder-node-to-relay to use remote LDAP server and roles	Released	Nicolas CHARLES	2014-06-16	Actions
Bug #4884: On SLES 11, rudder-jetty installation is stopped by post-inst error about insserv	Released	Jonathan CLARKE	2014-05-22	Actions