This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.occi-wg/wiki/SingleTechnicalIntegrationToSupportMultipleServiceProviders at Sun, 06 Nov 2022 12:21:16 GMT SourceForge : View Wiki Page: SingleTechnicalIntegrationToSupportMultipleServiceProviders

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin

Web Site
Search Wiki Pages Project: occi-wg     Wiki > SingleTechnicalIntegrationToSupportMultipleServiceProviders > View Wiki Page
wiki2136: SingleTechnicalIntegrationToSupportMultipleServiceProviders

Use Case: Single technical integration to support multiple service providers

  • Name: Single technical integration to support multiple service providers
  • Contact: Richard Davies, ElasticHosts.
  • Description: (This is the major benefit ElasticHosts sees from a standardized IaaS API). Today, each cloud provider (ElasticHosts, GoGrid, Amazon, etc.) integrates independently with every other player in the cloud ecosystem (CohesiveFT, RightScale, etc), producing O(n^2) separate technical integrations. In the future, if all cloud providers and cloud ecosystem partners use a single standard API, then we have O(n) technical integrations, and all potential partnerships can immediately interoperate.
  • Non-functional Requirements
    • Uptake: Standardized IaaS API needs strong uptake in by both cloud providers and cloud ecosystem.
 




The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.occi-wg/wiki/SingleTechnicalIntegrationToSupportMultipleServiceProviders at Sun, 06 Nov 2022 12:21:23 GMT