SourceForge : View Wiki Page: Requirements

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

wiki2124: Requirements

Requirements Extracted from Use Case Descriptions

ID	DESCRIPTION	USE CASES	RELEVANCE	DELIVERED	PRIORITY
A.1.1	Attributes to define memory, CPU, disk and network requirements.	A.2 B.1	_	_	_
A.1.2	Attributes to define placement constraints, such as geographical location	A.2	_	_	_
A.1.3	Attributes to allow migrations if is supported by the infrastructure	A.2	Not a functionality to be defined by a Cloud API	_	_
A.1.4	The API should be able to fully express a cluster: 5 VMs, storage for each VM, two networks (a private one connecting the machines, and the public internet also connected to the load balancer), a fixed static IP for the website on the public internet, possible specification of the load balancer itself	E.3	_	_	_
A.1.5	A means to add constraints (non-functional, functional) on attributes declared in a provisioning request	A.1	_	_	_
A.1.6	Resource execution scheduling. Allow provisioned resources to execute sometime in the future from the original request	A.1	_	_	_
A.1.7	Common operating systems should be supported	E.4	_	_	_
A.1.8	Resources should be grouped according to provider policies		_	_	_
A.1.9	On requesting new resource(s) the request should be fully complete/describing		_	_	_

ID	DESCRIPTION	USE CASES	RELEVANCE	DELIVERED	PRIORITY
A.2.1	Methods to start, stop, suspend and resume VMs	A.1 A.2 B.1	_	_	_
A.2.2	Automated management in the event of a disaster	A.1 E.1	_	_	_
A.2.3	Provide ID for each backup disk and for the images	A.2	_	_	_
A.2.4	Provide methods to donwload any backup	A.2	_	_	_
A.2.5	API should offer functionality to enforce the following operations: deploy, shutdown, cancel, checkpoint, save, restore, poll (could be merged with monitoring)	B.1	_	_	_
A.2.6	State model should include: pending, booting, running, suspended, shutdown, cancel, failed	B.1	_	_	_
A.2.7	Listing collections should complete quickly without listing all properties for each entry	C.1	_	_	_
A.2.8	Allow for resource representations be updated and have those changes executed upon VMs	B.4	_	_	_
A.2.9	Support the usage of terminal, web, desktop and automated management interfaces		_	_	_
A.2.10	Support the migration of resources from a physical resource to the cloud, from a cloud to another cloud and from a virtual resource to the cloud		_	_	_

ID	DESCRIPTION	USE CASES	RELEVANCE	DELIVERED	PRIORITY
A.3.1	VPN creation	B.1	_	_	_
A.3.2	Multiple network connection (Public and Private )	A.1 A.2 B.1	_	_	_
A.3.3	Runtime IP change/attachment	B.1 E.1	_	_	_
A.3.4	Tagged Multiple network connections	A.1 A.2 B.1	_	_	_
A.3.5	Support network setups which support an 'Intercloud' setup.		_	_	_

ID	DESCRIPTION	USE CASES	RELEVANCE	DELIVERED	PRIORITY
A.4.1	Use of URIs as mount points - allows reuse of Storage service offerings	A.1	_	_	_
A.4.1	Allow attachment of additional storage at runtime	E.4	_	_	_

ID	DESCRIPTION	USE CASES	RELEVANCE	DELIVERED	PRIORITY
A.5.1	Methods capable to register, upload, update and download disk images	A.2	_	_	_
A.5.2	Updates based on rsync commands to synchronize machines with physical equivalents	E.1	_	_	_
A.5.2	When an upload completes successfully, an identifier to it should be returned	A.2	_	_	_

ID	DESCRIPTION	USE CASES	RELEVANCE	DELIVERED	PRIORITY
A.6.1	Unique IDs for VM images and their components	A.2	_	_	_
A.6.2	It must be possbile to tag resources and their components	E.5	_	_	_
A.6.3	It must be possible to search for resources based on e.g. tags.	E.5	_	_	_

ID	DESCRIPTION	USE CASES	RELEVANCE	DELIVERED	PRIORITY
A.7.1	Pull-based monitoring that request the status of the elements such as network , VM ...	A.1 A.2	_	_	_
A.7.2	Publish/subscribe monitoring that request events occur in the VM or networks such as Errors on some component, changes in the VM state and other periodic notifications	A.2	_	_	_
A.7.3	Attributes that define simple quick call to poll the list of servers, drives, etc	C.1	_	_	_
A.7.4	Attributes about resource consumption of the VM from the hypervisor (CPU, memory...)	A.1 A.2	_	_	_
A.7.5	Management reports should be generated from in some of the following formats XML, PDF		_	_	_

ID	DESCRIPTION	USE CASES	RELEVANCE	DELIVERED	PRIORITY
B.1.1	Use of X509 Certificates	B.1	_	_	_
B.1.2	Use of ACL	B.1 , A.1	_	_	_
B.1.3	Attributes in the VM description to define Security levels	A.1	_	_	_
B.1.4	Transport and user level security	A.1	_	_	_
B.1.5	Allow geographical region be specified and adhered to	b.4	_	_	_

ID	DESCRIPTION	USE CASES	RELEVANCE	DELIVERED	PRIORITY
B.2.1	Capacity requirements for recovery / failover	E.1	_	_	_
B.2.2	Attributes in the VM describes to define QoS level	A.1	_	_	_
B.2.3	Attributes in the VM describes to define Isolation level	A.1	_	_	_
B.2.4	Attributes in advanced reservation functionality	B.1	_	_	_
B.2.5	Allow VM response time be specified	B.4	_	_	_

ID	DESCRIPTION	USE CASES	RELEVANCE	DELIVERED	PRIORITY
B.3.1	No development tools or libraries for the final user, doing it as simple as possible	E.2	_	_	_
B.3.2	Simple JSON syntax make Ajax interface much simpler to implement	C.1	_	_	_
B.3.3	Clear definition of units (MB, GB etc) used in requests	A.2 C.1	_	_	_

ID	DESCRIPTION	USE CASES	RELEVANCE	DELIVERED	PRIORITY
B.4.1	Support a backup functionality of cloud resources		_	_	_
B.4.2	The interface should reconsider failover, disaster recovery and business continuity plans		_	_	_

Hide Details

	Versions		Associations		Attachments		Back Links

Version	Version Comment	Created By
Version 20		Thijs Metsch - 07/28/2009
Version 19		Thijs Metsch - 07/27/2009
Version 18	Added one-liner: Cloud services storefront (e.g. US Federal Government)	Sam Johnston - 07/22/2009
Version 17		Thijs Metsch - 07/09/2009
Version 16	added comments on one-liners	Andy Edmonds - 07/09/2009
Version 15		Thijs Metsch - 07/09/2009
Version 14	updates	Andy Edmonds - 06/08/2009
Version 13	added use case B.4 requirements	Andy Edmonds - 06/08/2009
Version 12	minor updates	Andy Edmonds - 06/08/2009
Version 11	use case C.1 additions	Andy Edmonds - 06/08/2009
Version 10	more updates from current use cases	Andy Edmonds - 06/08/2009
Version 9	updates to requirements	Andy Edmonds - 06/08/2009
Version 8	Moving use case requirement collection up one level	Andy Edmonds - 06/08/2009
Version 7	added one-liners from samj presentation	Sam Johnston - 06/04/2009
Version 6		Ignacio M. Llorente - 05/05/2009
Version 5		Ignacio M. Llorente - 05/05/2009
Version 4		Richard Davies - 04/15/2009
Version 3		Ignacio M. Llorente - 04/15/2009
Version 2		Ignacio M. Llorente - 04/15/2009
Version 1		Andy Edmonds - 04/14/2009