OW2Con - Configurations, do you prove yours?
0 likes199 views
The document discusses the challenges of configuration management in infrastructure automation, highlighting issues such as diluted expertise across multiple teams and the complexity of obtaining and understanding crucial information. It emphasizes the importance of observability to enhance trust and compliance in configuration states, which aids various team roles in monitoring system performance. The document also outlines how specific tools like Rudder can facilitate improved observability and compliance reporting.
![Definition
Configuration management is a systems
engineering process for establishing and
maintaining consistency of a product [...]
throughout its life.
Configuration_management
“](https://image.slidesharecdn.com/rudderow2con-configurationsdoyouproveyoursv2-190612110406/85/OW2Con-Configurations-do-you-prove-yours-5-320.jpg)
OW2Con - Configurations, do you prove yours?
- 1. Configurations: Do you prove yours ? Main theme: Infrastructure automation Alexandre BRIANCEAU alexandre@rudder.io @abrianceau
- 2. How are the servers doing? No error nor change in logs means success? Aren’t we missing something?
- 3. Main challenges faced nowadays 3 DEV QA PRODUCTION RECOVERY DEV SEC OPSMGMT EXTERN Multiple teams, diluted expertise, harder reporting Heterogeneous systems, reduced visibility, ease of use and understanding
- 4. Getting and understanding the info is complex Operators, Managers, Experts, APIs have differents needs Frustration if we need a third party to get data We mistrust what we don’t understand
- 5. Definition Configuration management is a systems engineering process for establishing and maintaining consistency of a product [...] throughout its life. Configuration_management “
- 6. How DevSecOps can help to understand? Culture AutomationShare Measure
- 7. Let's remember: What does configuration management do? configuration target state feedbackconfiguration
- 8. Let's remember: What does configuration management do? configuration target state feedbackconfiguration feedbackconfiguration feedbackconfiguration
- 9. Definition (again) Observability is a measure of how well internal states of a system can be inferred from knowledge of its external outputs. Observability “
- 10. Monitoring VS Observability: having a factual & deep insight monitoring observabilityVS
- 11. Why we need Observability in Configuration Management? Causality AgencyPerspective trust and prove configuration states provide insights relevant to different needs help teams find the best levers for their job A B
- 12. Let’s take an implementation example...
- 13. These concepts are core to Rudder Everyone/thing can be an actor of configuration management
- 14. Observability and how Rudder can prove the compliance? PARAM RULE ● Id DIRECTIVE ● Id ● (Components) GROUP ● Id RUDDER config (global) ● Policy Mode ● Schedule... NODE ● Properties ● Policy Mode ● Schedule... Environmental context ● Id : . . . ● Generated : . . . Files Node configuration Historisation Historisation RUN ● Reports ● Reports ● ... ● ... METADATA ● node id ● config id ● run timestamp RUN ● Reports ● Reports ● ... ● ... METADATA ● node id ● config id ● run timestamp ● Signature Get config Send configuration reports Expected reports (node id, config id, timestamp) Run reports Historisation Compliance historised Send expected reportsMetadata ● Integrity ● Signature Config ● For Rule R, Directive D1, Component C Event logs Change request
- 15. What can we do with observability in configuration mgmt? 15
- 16. Thank you ! Any questions ?