roboconf-platform
roboconf-platform copied to clipboard
Migration handlers: greedy strategy
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 instances of all the other components.
- ... basculating the stable instances to the new instances.
- ... deleting the old unstable instances.
This strategy relies on the idea some components are stable in time and can hide migrations. And it is called greedy because it duplicates a part of the entire application. At some time, the old and the new version coexist.