One of the challenges CELAR has set itself, as part of its goal to develop elastic resource provisioning for cloud applications, is to be able to seamlessly provision complex multi-tier user applications on different clouds. However, to achieve this, the team had to address the issue that different clouds have different IaaS APIs.
SixSq was tasked with finding a solution for this. We decided to tackle the problem by using a provisioner that could abstractly describe requirements at the cloud level and provision the required resources, which is where SlipStream comes into play. Slipstream does exactly that and we’d like to provide you with an overview of how it is achieved.
SlipStream’s role:
For more technical details on writing a connector for SlipStream, take a look at this blog on the SixSq website.
The user’s role:
Via its REST API, SlipStream can therefore be used as the multi-cloud provisioner as part of a more complex processing pipeline.
CELAR IaaS partners Flexiant and ~okeanos have developed connectors for SlipStream, which allowed CELAR to successfully validate their main application deployment workflows with all the CELAR Platform components integrated.
This is exactly what CELAR does. It first automatically creates native images from high-level recipes or blueprints and deployment definitions. It then deploys applications according to these definitions and monitors their behaviour.
Louise Merifield (SixSq), Konstantin Skaburskas (SixSq)
