for Cloud Computing and Big Data Dept of CSE PES University Bangalore Contact Prof Dinkar Sitaram dinkarspesedu Partially funded by EMC Bursting across different deployments Workload Migration Policies ID: 927903
Download Presentation The PPT/PDF document "Hybrid Cloud Framework Center" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Hybrid Cloud Framework
Center for Cloud Computing and Big DataDept of CSE, PES University, BangaloreContact: Prof. Dinkar Sitaram, dinkars@pes.eduPartially funded by EMC
Slide2Bursting across different deployments
Workload Migration PoliciesSupport forScalabilityHigh AvailabilityInterface OpenStack with other cloudsObjectives
Slide3High Level Architecture
Slide4Top Cell/
Cells Scheduler
Child Cell
Pseudo-Child Cell
Private Cloud Resources
Public Cloud Resources
Implemented Architecture
Slide5VPN/Firewall Node
Top-Cell
Private Cloud Child Cell
VPN/NAT
Firewall Node
Public Cloud Pseudo-Child Cell
Transport Layer Security
Current Deployment
Slide6Our 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.Implementation Details
Slide7Currently, not integrated with Federated SecurityFuture 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 parentSecurity
Slide8Nova-Cells Child
Nova-Compute
Interface to the public cloud
Handle incoming Messages and update Top Cell about status
Updates Database and makes call to Interface driver
Interface that speaks to the Public Cloud to execute resource requests
Pseudo-Child Cell
Slide9Work 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 policyIf 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
Child Cell
Pseudo-Child Cell
Private Cloud Resources
Public Cloud Resources
Slide10The 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.Conclusion
Slide11Take forward as a contribution to Openstack
Integrate federated securityFuture Work
Slide12Thank You