Difference between revisions of "Fedcloud-tf:WorkGroups:Brokering"
Jump to navigation
Jump to search
Line 34: | Line 34: | ||
*Extend the demo testbed addressing a real-life use case. | *Extend the demo testbed addressing a real-life use case. | ||
== Clients Comparison Table == | == Clients Comparison Table == | ||
{| width="90%" cellspacing="0" cellpadding="5" style="border:1px solid black; | {| width="90%" cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;" | ||
|- style="background-color:darkgray;" | |- style="background-color:darkgray;" | ||
! Client/API | ! Client/API | ||
! URL | ! URL | ||
! OS | ! OS | ||
! Suppport | ! Suppport | ||
! OCCI/CDMI | ! OCCI/CDMI | ||
! Functionalities | ! Functionalities | ||
! Effort required | ! Effort required | ||
! Comments | ! 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 | |||
|- | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | | | ||
|- | |- | ||
| | | | ||
Line 69: | Line 69: | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
|} | |} |
Revision as of 09:25, 11 May 2012
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 | Suppport | 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 |