VT-CloudCaps:Capacities

From EGIWiki
Revision as of 09:10, 15 April 2013 by Bjoernh (talk | contribs) (Created page with "This page will gather various capacities that we identified as being useful for use cases. The EGI virtualized infrastructure will not be able to provide all of the capacities in...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This page will gather various capacities that we identified as being useful for use cases. The EGI virtualized infrastructure will not be able to provide all of the capacities initially. However, given sufficient demand, they may eventually be implemented.

Id Capacity Description
1 Block Storage

Block storage can be attached to virtual instances at run time. Some cloud stacks even require the use of explicitly attached block storage to make any use of the instances at all.

The benefit of block storage over object storage is that the application within the virtual instance does not need to be aware of it. With block storage appearing to the VM as just another block device, from which an ordinary file system can be mounted, applications will be able to deal with this kind of storage transparently.

2 Object Storage

Object storage is scalable storage in which data objects can be stored. The FCTF have agreed on CDMI to be the access mechanism of choice.

Applications within virtual instances need to make explicit use of object storage in order to make use of it. This is a key difference in comparison to block storage.

3 Messaging