Project

General

Profile

Actions

User story #9011

closed

Automatically call rudder-init on postinstall

Added by Benoît PECCATTE over 7 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Packaging
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

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).


Related issues 1 (0 open1 closed)

Related to Rudder - Architecture #9010: Add an automatic network detection in rudder-initReleasedAlexis Mousset2016-09-12Actions
Actions #1

Updated by François ARMAND over 7 years ago

Actions #2

Updated by François ARMAND over 7 years ago

  • Description updated (diff)
Actions #3

Updated by François ARMAND over 7 years ago

  • Description updated (diff)
Actions #4

Updated by François ARMAND over 7 years ago

  • Description updated (diff)
Actions #5

Updated by François ARMAND over 7 years ago

  • Target version changed from 4.0.0~rc2 to 4.1.0~beta1
Actions #6

Updated by Janos Mattyasovszky over 7 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...

Actions #7

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.0~beta1 to 4.1.0~beta2
Actions #8

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.0~beta2 to 4.1.0~beta3
Actions #9

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.0~beta3 to 4.1.0~rc1
Actions #10

Updated by François ARMAND about 7 years ago

  • Target version changed from 4.1.0~rc1 to 4.2.0~beta1
Actions #11

Updated by Alexis Mousset almost 7 years ago

  • Target version changed from 4.2.0~beta1 to 4.2.0~beta2
Actions #12

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.2.0~beta2 to 4.2.0~beta3
Actions #13

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.2.0~beta3 to 4.2.0~rc1
Actions #14

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.2.0~rc1 to 4.2.0~rc2
Actions #15

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.2.0~rc2 to 4.2.0
Actions #16

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.2.0 to 4.2.1
Actions #17

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.2.1 to 4.2.2
Actions #18

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.2.2 to 4.2.3
Actions #19

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.2.3 to 4.2.4
Actions #20

Updated by Benoît PECCATTE about 6 years ago

  • Target version changed from 4.2.4 to Ideas (not version specific)
Actions #21

Updated by Alexis Mousset about 3 years ago

  • Status changed from New to Rejected

This was done in 6.0.

Actions

Also available in: Atom PDF