Difference between revisions of "Jacket"

Revision as of 03:39, 4 February 2016

Overview

More and more enterprise are thinking about how to leverage the usage of private cloud and public cloud. Public cloud have very good scalability and have cost advantage in many cases, while Private cloud have more security assurance and have more feasibility for IT administrator. It is a hard decision to choose just one of them. A traditional Cloud Broker can provider a basic multi-cloud management function, but it is not a good experience for the administrator, since they still feels like they are using multiple separated clouds with a unified UI style. What's worse is that they need to learn one more type of operational mode and API besides the existing clouds APIs.

A hybrid cloud solution is required, which will provide smooth inter-cloud management which makes you feels just like managing one cloud, and it should provide the existing standard API and operational mode which makes you shorten learning curve and easy to integrate with industry existing services.

Jacket project will solve the problem. It will be an adaptor

Use Case

Unified Management of Multiple Clouds

A typical web application is composed with 3 different tiers, the load balancer tier, the web front tier, and the app backend tier. Users have a private cloud based on OpenStack or VMware and so on, which just has less resources but more secure than public clouds. So they can use the standard OpenStack API to launch the web service's backend virtual machines in private cloud, launch the load balancer and web front virtual machines in the public clouds.

Chanleges

Architecture