Alexis is a system engineer, and a Rudder developer since 2015.
He works on Rudder's configuration policies library, agents and
internal server components, and he (almost) enjoys documenting things.
A RUDDER walkthrough: manage your configurations through compliance
This talk is designed for people wanting to discover or learn more about how things are done on a day-to-day basis with Rudder. Based on our experience helping Rudder users achieve their automation and compliance goals, this session will detail real-world examples, and describe and explain step-by-step the development and application of policies.
We will cover:
- policy development workflow (advanced reporting analysis, debugging methods)
- best practices in policy organization
- various productivity tips
- reporting and compliance focused policies (component names, rules organization, et.)
- commonly encountered problems
- API usage to collect information (Excel export, ...)
- audit vs. configuration
Designing the future of agent-server communication in RUDDER
Rudder is currently used to manage more than 10k machines from the same central server,
but our agent-server communication (using HTTP for inventory collection,
syslog for reporting and a custom protocol for policy updates) was limiting us in terms of
security, performance and extensibility.
With Rudder 6, we have introduced a new communication infrastructure
to match present and future challenges with consistent security,
better performance, improved continuity through
immediate action triggers, while staying compatible with our
fully asynchronous, pull-based workflow.
The talk will focus on the design choices we made, from the use of Rust for our new
server component, to the network and message protocols we use.
It will also highlight the reasons and constraints behind them,
including ensuring a minimal operation overhead and an easy and smooth transition with no breaking change.