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

From EGIWiki
Jump to: navigation, search
m
(Scenario 1: Running a pre-defined VM Image)
Line 6: Line 6:
  
 
== Scenario 1: Running a pre-defined VM Image  ==
 
== Scenario 1: Running a pre-defined VM Image  ==
 +
Following need to be considered with this scenario
 +
* Trust level and Auditing of the VM (since it has to run as Root access)
 +
* Different VMs needed based on underlying Infrastructure such as 64 vs 32bits Or VT enabled  plus Xen vs KVM
 +
* 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  ==
 
== Scenario 2: Running my data and VM in the Infrastructure  ==

Revision as of 12:35, 4 October 2011


Introduction

Six scenarios for minimal functionality

Scenario 1: Running a pre-defined VM Image

Following need to be considered with this scenario

  • Trust level and Auditing of the VM (since it has to run as Root access)
  • Different VMs needed based on underlying Infrastructure such as 64 vs 32bits Or VT enabled plus Xen vs KVM
  • 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

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)