Upgrade to Pro — share decks privately, control downloads, hide ads and more …

What happened in RUDDER in 2018 and what’s next?

Rudder
February 04, 2019

What happened in RUDDER in 2018 and what’s next?

Let’s take a look at Rudder’s new features from 2018, both in terms of the features of versions 4.3 and 5.0 as well as the new documentation and our platform for building and distributing binaries.

We will then present the provisional roadmap for 2019: let’s go to Rudder 5.1 and 5.2.

Alexis Mousset
Configuration Management Camp 2019

Rudder

February 04, 2019
Tweet

More Decks by Rudder

Other Decks in Technology

Transcript

  1. What happened in RUDDER in 2018 and what’s next? CONTINUOUS

    AUDITING & CONFIGURATION Alexis Mousset 4th February 2019
  2. plugins Zabbix Centreon AIX Windows Branding User management API authorizations

    Reporting Change validation Scale-out relays Datasources GLPI Notification Auth backends External node reports Vault
  3. cf-serverd relayd inventory / HTTPS reports / HTTPS policies /

    TLS (5309) remote / TLS (5309) cf-serverd agent
  4. rule A rule B group A group B directive A

    directive B technique version 1 nodes
  5. rule A rule B group A group B directive A’

    directive B technique version 2 nodes
  6. rule A rule B group A group B directive A

    directive B technique directive A’
  7. @format = 0 @version = 1.0 resource NTP() resource state

    configuration(serviceName: string) { file(“/etc/ntp.conf”).content(“server 10.23.2.1”) val p = package(“ntp”).present() match p { Kept | Repaired => Kept Error => NTP_utilities.PackageInOtherReality } service(serviceName).started() } mod NTP_utilities { enum Error { PackageInOtherReality , ServiceUndead } }