Difference between revisions of "Fedcloud-tf:WorkGroups:Brokering"
Jump to navigation
Jump to search
Line 81: | Line 81: | ||
| Create/Start/Stop/Reboot/Destroy instances. Dynamic linking, actions on resources, contextualization. Supports X.509 and VOMS auth. | | Create/Start/Stop/Reboot/Destroy instances. Dynamic linking, actions on resources, contextualization. Supports X.509 and VOMS auth. | ||
| <span style="color:green"> '''Low'''</span> | | <span style="color:green"> '''Low'''</span> | ||
| rOCCI is an OCCI 1.1 implementation | | rOCCI-cli is an OCCI 1.1 client implementation compatible with multiple server implementations. | ||
|} | |} | ||
Revision as of 01:45, 4 February 2014
Main | Roadmap and Innovation | Technology | For Users | For Resource Providers | Media |
Leader: Alvaro Simon, JR1
Collaborators
Role | Institution | Name |
---|---|---|
Collaborator | OeRC | Matteo Turilli |
Collaborator | BSC | Daniele Lezzi |
Scope
This workgroup deals with the issues around cloud brokering. With 10+ resource providers lined up to be federated into the EGI cloud testbed, users need effective ways to access cloud resources. The goal is for a user to have a choice between a unified, abstracted view of the cloud testbed as a whole and the opportunity to target specific providers for their needs. As a consequence, this workgroup is concerned with both brokers and OCCI clients.
Roadmap
- Collect information about existing solutions for cloud brokering compatible with the OCCI and CDMI management interfaces;
- Collect information about existing solutions for OCCI and CDMI clients;
- Make an inventory of the available solutions;
- Choose a broker and a client for the testbed;
- If possible, join the development teams of the chosen solutions to the task force;
- Coordinate with the TF Resorce Providers to deploy the chosen solutions;
- Extend the demo testbed addressing a real-life use case.
Clients Comparison Table
Client/API | URL | OS | Support | OCCI/CDMI | Functionalities | Effort required | Comments |
---|---|---|---|---|---|---|---|
Hybridfox | http://code.google.com/p/hybridfox/ | Win/OS X/Linux | AWS/Eucalyptus/OpenStack/OpenNebula/HP Cloud | NO | Manage Images/Instances/Elastic IPs/Security Groups/Key-pairs | Low | Hybridfox does not support x509 auth, it uses EC2 auth for OpenNebula and OpenStack |
DeltaCloud | http://deltacloud.apache.org | Win/OS X/Linux | EC2/Eucalyptus/OpenStack/OpenNebula/vSphere | NO | Create/Start/Stop/Reboot/Destroy instances | Medium | DeltaCloud uses its own delta-cloud driver for each framework instead of OCCI. It provides storage support for S3, Warlus, Azure and Google Storage. |
Aeolus | http://aeolusproject.org/about.html | Win/OS X/Linux | Same as DeltaCloud | NO | Create/Start/Stop/.. instances. Manage different instances and Images from different private, public, or hybrid cloud providers. | Medium | Aeolus uses DeltaCloud cross-cloud abstraction library and it includes some extra functionalities. It includes Aeolus Conductor/Composer/Orchestrator/HA Manager |
rOCCI-cli | https://github.com/gwdg/rOCCI-cli | Linux | OpenNebula (rOCCI-server)/OpenStack (OCCI-OS)/Synnefo (snf-occi) | YES | Create/Start/Stop/Reboot/Destroy instances. Dynamic linking, actions on resources, contextualization. Supports X.509 and VOMS auth. | Low | rOCCI-cli is an OCCI 1.1 client implementation compatible with multiple server implementations. |
Cloud Brokering Solutions
Resource Brokers
Name | URL | Cloud SW Support | OCCI | External API | Functionalities | Effort required | Comments |
---|---|---|---|---|---|---|---|
CompatibleOne | http://www.compatibleone.org/ | OpenStack, OpenNebula, Azure, Vcloud | Yes, supports OCCI, but implements his own OCCI interface for each of the stacks (PROCCI). | Accounting, Brokering, User management, Monitoring. | High |
| |
VMDIRAC | https://github.com/DIRACGrid/VMDIRAC/wiki | OpenNebula, OpenStack, CloudStack and Amazon EC2 | Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. | Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, VM Horizontal Auto-scaling. | Medium |
| |
SlipStream™ | http://sixsq.com/products/slipstream.html | StratusLab, OpenStack, Abiquo, CloudSigma and Amazon EC2 | Supports OCCI via rOCCI-cli integration | EC2 via bridge (experimental), proprietary SlipStream REST APIs | VM image creation and deployment, contextualisation, VM cluster automated deployments. | Medium |
|
Application Brokers
Name | URL | Cloud SW Support | OCCI | External API | Functionalities | Effort required | Comments |
---|---|---|---|---|---|---|---|
COMPSs | http://www.bsc.es/compss | OpenNebula, Amazon, Azure, OpenStack | Yes, support of rOCCI servers and OCCI+OVF | OGF-BES SOAP | Automatic parallelization and orchestration of applications and services, elasticity, auto scaling | Medium |
|
VMDIRAC | https://github.com/DIRACGrid/VMDIRAC/wiki | OpenNebula, OpenStack, CloudStack and Amazon EC2 | Yes, it supports rOCCI, OpenNebula "OCCI 0.8", Amazon EC2, OpenStack Nova 1.1 and CloudStack 2 APIs. | Accounting, monitoring, brokering, scheduling, HEPiX and SSH based VM contextualisation, VM Horizontal Auto-scaling. | Medium |
|