120 likes | 295 Vues
The Hybrid Cloud Framework at PES University, partially funded by EMC, focuses on enhancing cloud computing and big data capabilities. Our architecture integrates OpenStack with Amazon EC2 for seamless workload migration, scalability, and high availability. The implementation utilizes a hierarchical structure with parent-child cell relationships, optimizing resource management between private and public clouds. Future work aims to improve federated security integration and contribute to OpenStack advancements. Contact Prof. Dinkar Sitaram for further details at dinkars@pes.edu.
E N D
Hybrid Cloud Framework Center for Cloud Computing and Big DataDept of CSE, PES University, BangaloreContact: Prof. DinkarSitaram, dinkars@pes.eduPartially funded by EMC
Objectives • Bursting across different deployments • Workload Migration Policies • Support for • Scalability • High Availability • Interface OpenStack with other clouds
Implemented Architecture Top Cell/ Cells Scheduler Pseudo-Child Cell Child Cell Private Cloud Resources Public Cloud Resources
Current Deployment VPN/Firewall Node VPN/NAT Firewall Node Transport Layer Security Top-Cell Public Cloud Pseudo-Child Cell Private Cloud Child Cell
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.
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
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
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
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.
Future Work • Take forward as a contribution to Openstack • Integrate federated security