SourceForge : View Wiki Page: FeatureMatrix

Search Wiki Pages Project: occi-wg Wiki > FeatureMatrix > View Wiki Page

wiki2183: FeatureMatrix

This feature matrix shows the various requirements as implemented by various Cloud Infrastructure APIs. While avoiding being a superset of every possible feature, OCCI should have ticks across the board if it is to be an implementation candidate for all providers (for example, if we don't implement both persistent and ephemeral resources then some providers will not be able to use OCCI even if they each typically only support one or the other).

Feature Matrix

Feature	Requirement	OCCI	EC2	EH	FS	GG	SC	CS	VM	??
Authentication via HTTP	Client compatibility
Authentication via request signing	Untrusted third-party requests
Ephemeral compute resources	Lightweight servers
Persistent compute resources	Stopped servers
Ephemeral storage resources	Temporary storage
Persistent storage resources	Permanent storage
Multiple storage resources	Complex architectures
Multiple network resources	Complex architectures
Static IPs	Internet-facing applications
Firewalling	Basic network security
Load balancing	Horizontal scalability
Billing	Business
Resource categories	Organisation of resources
Resource search	Finding resources
Resource tagging	Organisation of resources
Collections (pass-by-reference)	Enumeration
Collections (pass-by-value)	Serialisation

Legend

OCCI	Open Cloud Computing Interface
EC2	Amazon Elastic Compute Cloud
EH	Elastichosts
FS	Flexiscale
GG	Gogrid
SC	Sun Cloud API
SH	Slicehost
CS	Rackspace (formerly Mosso) Cloud Servers
GN	Globus Nimbus (WSRF interface)
EU	Eucalyptus - see EC2
VM	VMware vSphere (vCloud may be similar)

Notes

Ephemeral means "destroyed when stopped"
Persistent means "exists when stopped"
Multiple network and storage resources means "per compute resource"

CloudServers

Uses custom HTTP headers for authentication

EC2:

Ephemeral and persistent storage provided by AMI and EBS respectively.
Firewalling provides "poor man's private network"
API returns all resources for a given account (unsuitable for many resources)

FlexiScale

Uses dedicated login/logout functions over SOAP for authentication(?)

Attachments:

unknown.png [FeatureMatrix/unknown.png]

help.png [FeatureMatrix/help.png]

cross.png [FeatureMatrix/cross.png]

tick.png [FeatureMatrix/tick.png]

Show Details