1 / 12

Hybrid Cloud Framework

Hybrid Cloud Framework. Center for Cloud Computing and Big Data Dept of CSE, PES University, Bangalore Contact: Prof. Dinkar Sitaram , dinkars@pes.edu Partially funded by EMC. Objectives. Bursting across different deployments Workload Migration Policies Support for Scalability

lixue
Download Presentation

Hybrid Cloud Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Hybrid Cloud Framework Center for Cloud Computing and Big DataDept of CSE, PES University, BangaloreContact: Prof. DinkarSitaram, dinkars@pes.eduPartially funded by EMC

  2. Objectives • Bursting across different deployments • Workload Migration Policies • Support for • Scalability • High Availability • Interface OpenStack with other clouds

  3. High Level Architecture

  4. Implemented Architecture Top Cell/ Cells Scheduler Pseudo-Child Cell Child Cell Private Cloud Resources Public Cloud Resources

  5. Current Deployment VPN/Firewall Node VPN/NAT Firewall Node Transport Layer Security Top-Cell Public Cloud Pseudo-Child Cell Private Cloud Child Cell

  6. Implementation Details • Our implementation of a hybrid cloud consists of OpenStack as the primary cloud and Amazon EC2 as the foreign cloud. • Cells Architecture of OpenStack is deployed to have a parent cell and child cells. • The driver in pseudo-cell was re-written to be an EC2 driver.

  7. Security • Currently, not integrated with Federated Security • Future work • The driver uses the EC2 authentication and provides the EC2 virtualization platform to spawn the VM on EC2. • The VM spawned on EC2 returns the endpoints which are used to update the databases of children and parent

  8. Pseudo-Child Cell Handle incoming Messages and update Top Cell about status Nova-Cells Child Updates Database and makes call to Interface driver Nova-Compute Interface that speaks to the Public Cloud to execute resource requests Interface to the public cloud

  9. Work Flow • Request for compute resources arrives at parent or top cell. • The cells scheduler of the parent checks capabilities of all its child cells and selects a target cell as per policy • If the target cell is not the EC2 pseudo-child cell then the scheduler routes the request to the target cell and it spawns a VM using local resources. • If the request is routed to the EC2 pseudo-child cell then the VM is spawned using resources of Amazon by using its API provided in the driver. • Once the VM is spawned in Amazon, it returns the endpoints to the target cell. This cell extracts required metadata from these endpoints. • Each child updates their databases and then push the metadata to the parent to be updated in the parent. Top Cell/ Cells Scheduler Pseudo-Child Cell Child Cell Public Cloud Resources Private Cloud Resources

  10. Conclusion • The proposed architecture is simple in implementation for many well-known clouds as it leverages hierarchical features already found in clouds such as OpenStack and Eucalyptus. • This architecture has been implemented for federation between multiple OpenStack clouds and OpenStack-Amazon federation.

  11. Future Work • Take forward as a contribution to Openstack • Integrate federated security

  12. Thank You

More Related