Roadmap

Our long term vision

When companies adopt DevOps they need to have a guarantee that their infrastructure remains compliant with the quality and security standards prescribed by their IT Management that Rudder is designed to provide.

Rudder was born in the core of the cloud computing and DevOps, in the era of the global revolution of the modern IT systems. It is all about how the IT infrastructure is consumed by the business for quick and frequent deployment of its new business applications or how the system administrators have to manage today the hardware and its system foundation when their role is also to keep the system running and guarantee the quality, the respect of security standards, the compliance with the regulations all the way remaining flexible and open to new business requirements.
Everyday the gap between the application operators and system operations are growing bigger due to the wide use of application containers that are deployed automatically based on its 'Build' infrastructure and automated tests organized and supervised by an orchestrator. As a result, the pressure on the 'Run' to continue with its historical mission is enormous.
It is an evidence today that all those needs follow its own rules. The time is money for the deployment of creative and bright applications capable to handle the business requirements on its day to day shift with the most appropriate application stack. On the long term the mission of the 'run' is not to implement various latest technologies but to rationalize its infrastructure in order to comply with the internal rules, to guarantee the reliable technical foundations, running continuously, to control and eliminate risks and at the same time to satisfy all the business requests and requirements.
none

Rudder prides itself for being a dedicated solution to help operations to run the infrastructure and to accomplish efficiently their 'RUN' mission via 3 key approaches:

Accessibility

Vigilance

Visibility

Our middle term vision

The long term vision brings us to place Rudder in the context of a new corporate IT perspective. Nevertheless, this ambitious role shall be achieved progressively that is why we prefer to give priority today to the following three development aspects :

Visual representation and quick overview of the applied configurations on the infrastructure and its compliance to the initial prescribed configurations are key.

Rudder of Normation is designed to visualize the lapse between the targeted and applied configurations and to enable various types of users to view this chart at the user interface. The visual representation is accessible through a different model of approaching the IT system in order to extract in a glance the state of the infrastructure, the rules applied incorrectly, to identify the cause of the problem (as an example, to distinguish the incorrect application of the new rule from the general configuration problem affecting the whole datacenter). To make it come true, the configuration objects of the IT system needs to be organized by categories in accordance with multiple criteria and tags.

The tendency to keep up with the target configuration is the consequence of the appropriate vision on the IT system implementation that is unique for each corporate.

The user has the choice to implement the strategy to control and apply changes by Rudder, if needed. The capacity to modify the configuration may start with the automated correction as soon as the gap is identified by Rudder agent or just to alert on the gap to apply the change manually by request, via change management or the automated categorization by type of modifications in accordance with the internal process and validation workflow.

The creation of configuration rules and access to the configuration referential accessible to anybody of the team.

In our vision on Rudder evolution, we plan to integrate the following major features. The functional enrichment of the Rudder Technique Editor that the creation of new Techniques remain simple but performing. This is also about the renewal of user experience, leur creation, delivery and sharing.

Next version

4.0 of Rudder - mid 2016

Rudder 4.0 will open a wealth of new usage possibilities by enabling users to easily verify configuration across thousands of hosts, before enforcing it (or not). An improved Technique editor will make it even easier to share complex configuration tasks with beginners.

  • New "verify only" mode to disable changes on a selection of nodes or directives compliance
  • Make exposed parameters in Directives configurable via the Technique editor techniques
  • Support for FreeBSD, Solaris and GNU/Linux Slackware as managed nodes agent

Latest version

3.2 of Rudder of January 2016

Rudder 3.2 is currently the latest version of Rudder. This version is named "Caravel".

  • Improved host isolation for configuration policies by distributing user Techniques only to nodes that use them security
  • Automatic naming for directives, new rudder agent sub-commands, and more UX
  • New technique to import JSON data techniques
  • Make Rudder group memberships available to Technique writers techniques
  • Make detailed compliance statistics available in the REST API API
  • Compatibility with CFEngine Enterprise for managing agents and distributing promises via the Mission Portal integration
  • Plugin to import Rudder nodes and groups in Ansible inventory integration
  • Plugin to import Rudder nodes and groups as Rundeck targets integration