Académique Documents
Professionnel Documents
Culture Documents
What is Rudder?
Why / How Rudder?
Terms and Rampup
How to order new Features / Policies
Log Access and General Information
Availability Dates
Demand of the BU´s and Discussion
Big growth of environment size, Overrides ~14 years old, manual fixes scale badly, dull issues
To be agile, you need more flexibility and more power
Goals
Be simpler and more capable
Configuration is OK now, will be OK tomorrow, and will be OK next year
Configuration is the same among all similar-use systems, independent of age
Easily reproduced
Compliance measurable and accessible
Faster security patch overview / rollout
To start, fill what you know and who’s the main contact
Dev team will handle QA preparations - taking it quite serious!
Fetch existing configurations
Discussing / unifing existing configurations takes some time (3-8 weeks depending on complexity)
Simplify, rewrite existing tools / scripts whereever possible
Create unit tests
Create necessary interface clients for other data sources (DCODB)
Working solution needs sign-off by requester and operations
Then ready to be deployed
System behaviour
No big changes, Rudder works with smallest possible change
Expect /etc/files managed by Rudder to be constantly up to date