Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Fedcloud-tf:Blueprint EGI Federated Clouds"

From EGIWiki
Jump to navigation Jump to search
Line 14: Line 14:


== Scenario 2: Running my data and VM in the Infrastructure  ==
== Scenario 2: Running my data and VM in the Infrastructure  ==
Leader: Micheal Higgins, CloudSigma
[[Leader: Micheal Higgins, CloudSigma]]


== Scenario 3: Integrating multiple resource providers  ==
== Scenario 3: Integrating multiple resource providers  ==

Revision as of 14:32, 14 October 2011


Introduction

Six scenarios for minimal functionality

Scenario 1: Running a pre-defined VM Image

Leader: Michel Drescher, EGI; Matteo Turilli, Oxford e-Research Centre

Following need to be considered with this scenario

  1. Trust level and Auditing of the VM (since it has to run as Root access)
  2. Different VMs needed based on underlying Infrastructure such as 64 vs 32bits Or VT enabled plus Xen vs KVM
  3. Contextualization i.e. how users should login to this vm , how his public key transfer and active to login as root to this vm

Scenario 2: Running my data and VM in the Infrastructure

Leader: Micheal Higgins, CloudSigma

Scenario 3: Integrating multiple resource providers

Scenario 4: Accounting across Resource Providers

Scenario 5: Reliability/Availability of Resource Providers

Scenario 6: VM/Resource state change notification

Key Capabilities

VM Management

Data access

Information discovery

Accounting

Monitoring

Notification

References

  1. http://go.egi.eu/435: Draft of Federated Clouds profile
  2. http://go.egi.eu/803: Task Force presentations at the EGI Technical Forum 211, Lyon


--Michel 14:40, 26 September 2011 (UTC)