CloudStack Collab Conference 2014

- My experience writing Citrix proprietary service "Disaster Recovery Orchestration Solution" on top of CloudStack. It implements replicating (and later on synching up with the latest changes) CloudStack VM object along with all its data (networking rules, secondary ips for VM's nics, userdata, etc) from one Availability Zone to another, without direct DB modification, using just CloudStack APIs. The service can be used as a part of Disaster Recovery Solution if deployed with partner products for actual storage data replication. Although the component code is not an open source, I think the feature high level architecture design overview as well as the pitfalls I've faced/overcame while writing integration component on top of CloudStack, can be useful.

CloudStack manages hypervisor hosts as clusters. It will deploy the vm's to ensure proper hosts capacity are used max. Due to some operations by user on vm's like stop/migrate/destroy hosts usage in the clusters will be in inefficient state.
To solve this issue we can have a new Manager who will regularly checks host capacity and implement Server Consolidtion by taking the actions:
1. Live migrate the vm's if possible along with storage. Migrate them such that hosts are fully utilized.
2. After redistributing the vm's Shutdown the hosts which are empty.
3. When load is getting increased,power-on the hosts remotely by WOL(Wake On Lan) mechanisam.

Over the past year we have developed and deployed a SaaS Cloud Mobility platform that enables OEMs and Cloud operators to reduce the friction of onboarding Enterprise customers at scale: by using our Open API users can migrate large volumes of servers 'as-is' to any cloud target (we currently support vCloud and vSphere, AWS, Openstack and Cloudstack as targets - and any combination of physical, virtual and cloud source servers).

In this talk, we'd like to share the challenges that we have faced in developing our system, how we've solved some of them and what opportunities this opens to both developers (who can build third-party clients against our API) and operators (who can use our SaaS to accelerate Cloud adoption).

We are also planning to open-source our core Model software and we'll be seeking feedback from the community as to the best way to do so.