EGI Document 435-v7

EGI Cloud Architecture

Permalink:
https://documents.egi.eu/document/435
Document #:
EGI-doc-435-v7
Document type:
Internal document
Submitted by:
Unknown
Updated by:
Unknown
Document Created:
31 Mar 2011, 17:13
Contents Revised:
02 May 2011, 16:16
Metadata Revised:
17 May 2017, 07:30
Viewable by:
  • Public document
Modifiable by:

Quick Links:
Latest Version

Other Versions:
Abstract:
EGI Cloud Architecture and its technical roadmap are now maintained on WIKI:
https://wiki.egi.eu/wiki/Federated_Cloud_Architecture

===============

The purpose of this document is to define a technical roadmap for the interoperable integration of virtualised resources from different resource providers to provide an integrated federated virtualised resources infrastructure for exploitation by EGI’s user community. To achieve interoperability between the individual deployments, while allowing individual sites the flexibility to deploy the software that they wish, some interfaces will need to be constrained to clearly defined specifications.
This document defines a minimal set of usage scenarios that when supported will provide key functionality for the end-users wishing to utilise ‘cloud’ interfaces provided as part of EGI. From these scenarios a number of functional areas are defined and from these functional areas a set of standards and specifications are identified that will define interaction across this functional areas.
These scenarios and specifications are identified to promote discussion amongst the end-user community (as a starting point for their use) and for resource-providers (to verify the deployability of these interfaces). There will be follow on discussion within the TCB, NGIs interested in engaging in these developments, that will be the main focus at the User Virtualisation Workshop to be held in Amsterdam 12-13th May 2011.

Files in Document:
Topics:
Authors:
Notes and Changes:
Document is deprecated - please visit https://wiki.egi.eu/w/index.php?title=Fedcloud-tf:Blueprint:Introduction&oldid=29319#High-level_scenarios for more recent information.

DocDB, Contact: Document Database Administrators