New & Noteworthy

This page lists the enhancements and new features brought by Roboconf 0.9.

Security: RabbitMQ exchanges over SSL

It is now possible to configure RabbitMQ messaging with SSL in Roboconf.
All the exchanges will go through secured channels.

Exchanges between Roboconf and RabbitMQ over SSL

Security: Authentication in the Web Console

Authentication can be enabled in the web console.
Users can be defined in Karaf REALMs, that is to say, in properties files, in databases or in LDAP servers.

Authentication in Roboconf's web console

Once enabled, the web console automatically requires authentication.

# Enable or disable CORS.
# CORS =
# It should be disabled in production environments.
enable-cors = false

# Enable or disable authentication.
# Users are authenticated against the specified REALM.
enable-authentication = false

# The REALM that is used for authentication.
# We use Karaf realms.
authentication-realm = karaf

# The period of validity for a session once a user is logged in.
# Expressed in seconds. Use a negative value for infinite validity.
session-period = -1

Security: Audit Files for Web Access

When authentication is enabled for web access, any access is tracked and user actions are logged for audit purpose.

Log web accesses

New MBeans to monitor Roboconf

Roboconf 0.9 comes with custom MBeans.
It allows to retrieve various Roboconf metrics with JMX.

New MBeans for Roboconf

This can be used, as an example, with Elastic Search and Kibana dashboards.

Example of Kibana dashboard

Commands History

Roboconf commands can be executed on-demand, through the REST API, or automatically, be it by the autonomic or by the scheduler. Commands executions are now traced in a history, giving details about the execution’s result, what triggered the execution, when, etc.

The history is global…

Global commands history

… or can be contextualized for a given application.

Commands history for a given application

Docker Target was redesigned

The Docker target is a way to use Docker containers as a substitute for VMs.
It primarily serves for test purpose.

This target was redesigned to rely on the official Docker images for Robocconf. The image generation process was replaced. Users can now provide a dockerfile that should extend the official agent image.

Docker target was redesigned

On-Premise Deployments

The embedded target aims at using servers that preexist to Roboconf usage.
It requires Roboconf agents to be installed on them.

This target handler was upgraded to pick up a machine amongst a list of provided IP addresses and dynamically give an identity to a Roboconf agent. The agent’s identity can be recycled once the machine is released by Roboconf.

The DM can use and reuse servers from a given pool


A lot of enhancements have been brought to this new version.
And many bugs were fixed too. Please, refer to the release notes for details.