roboconf-platform
roboconf-platform copied to clipboard
roboconf
The core modules and the platform
Currently, instances are created from the application template. There should be a choice for users. One of the choice should be "empty: model graphically".
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.
In the same way we can define upgrades, we should be able to specify roll-backs. We should be able to specify global or per-component strategies.
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...
We should add a new aspect to Roboconf: continuous deployments. This implies we need to be able to migrate an application. And there are several strategies. We should start with...
Following #258, another strategy should be implemented: the **greedy** one. It consists in... - ... in identifying one or several stable components (such as load balancers). - ... deploying new...
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 which a same application...
In some environments, there should be some roles and/or permissions. For the moment, there are at least three: - Those that can submit an application template. - Those that can...
Write a Jenkins plugin that can execute user scenarios. It could be used to deploy applications after a build. In a first step, there would be no migration of the...
Complete the install guide to explain how to run agents in Docker containers. Use the auto-restart feature as well. The container should be given sudo privileges. It could also be...