-
-
Today, the Roboconf term `target` includes:
- the definition of the IaaS on which VM will be deployed: Amazon, OpenStack, Docker, ...
- the image to push into the VM to run it. This image includes the…
-
Manipulate the Roboconf Agent means have a way to change the state of a Agent.
Imagine a component with the start script is just "service toto start". Now we connect to the machine, we run the comman…
-
On "**start**", Roboconf waits that all dependencies are started before to start a component. So a component is started after all its dependencies.
On "**stop**", Roboconf stops the component, next it…
-
Nowadays, the keyword "**import**" defines a dependency between two Roboconf components. This dependency is resolved at start-up time. Both components can be deployed concurrently, without dependency …
-
When a VM fails to be created, Roboconf marks the VM in error but does not explain why. We might add a better error message for users.
-
This strategy is so smart that I have not found it yet.
And it will most likely require some research work about it, and maybe some new features in Roboconf.
-
Some properties, like credentials, must be kept secret.
They are also dependent of the environment. Developement, tests, pre-production, production, production site... can be various environments in w…
-
We need to go farther in automation.
Currently, we can execute a command...
* ... explicitely (through the web administration).
* ... on schedule.
* ... automatically, when some conditions are m…
-
[QPID](https://qpid.apache.org/) is an AMQP server that could be used as an alternative to RabbitMQ. We should support it. This requires we make the **roboconf-messaging** bundle more modular, with a …