User story #9011
closed
Automatically call rudder-init on postinstall
Description
The idea here is to be able to have a fully automated, non-interactive post-install.
It implies that by default, a new Rudder installation will have all the known network of the machine added in allowed networks.
We need to update the documentation on installation, with a new step "reviewing networks access".
This is possible because we added the network detection in linked ticket (#9010)
We also must provide a way to give the authorized networks to automate rudder install (either by API, or by looking for the existence of a specific env variable and use it in place of auto, or with a dedicated command).
Updated by François ARMAND about 8 years ago
- Related to Architecture #9010: Add an automatic network detection in rudder-init added
Updated by François ARMAND about 8 years ago
- Target version changed from 4.0.0~rc2 to 4.1.0~beta1
Updated by Janos Mattyasovszky almost 8 years ago
I'd not suggest to automatically call rudder-init in the post-install phase. My thinking is, if you'd want to create a docker container hosting Rudder, you'd "init" the environment during the "container build" Phase, before the final instance of the container is created. What if that environment has a different environment?
Additionally, you would not want to init rudder in a building environment, since this would mean init'ing LDAP/DB with values that would vanish when those services would start in the final environment, that might have pgsql and ldap's datadir mapped to an external directory...
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 4.1.0~beta1 to 4.1.0~beta2
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 4.1.0~beta2 to 4.1.0~beta3
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 4.1.0~beta3 to 4.1.0~rc1
Updated by François ARMAND almost 8 years ago
- Target version changed from 4.1.0~rc1 to 4.2.0~beta1
Updated by Alexis Mousset over 7 years ago
- Target version changed from 4.2.0~beta1 to 4.2.0~beta2
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.2.0~beta2 to 4.2.0~beta3
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.2.0~beta3 to 4.2.0~rc1
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.0~rc1 to 4.2.0~rc2
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.0~rc2 to 4.2.0
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.0 to 4.2.1
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.1 to 4.2.2
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.2.2 to 4.2.3
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.2.3 to 4.2.4
Updated by Benoît PECCATTE almost 7 years ago
- Target version changed from 4.2.4 to Ideas (not version specific)
Updated by Alexis Mousset almost 4 years ago
- Status changed from New to Rejected
This was done in 6.0.