RequirementsSolicitation - Revision history

Ryan Lane: Text replace - "NOTOC" to ""

2013-02-17T23:30:45Z

Text replace - "__NOTOC__" to ""

2010-07-13T16:17:12Z

2010-07-13T11:48:25Z

2010-07-13T11:37:18Z

2010-07-13T11:33:35Z

2010-07-13T11:29:22Z

2010-07-13T03:32:33Z

2010-07-13T03:30:47Z

2010-07-13T03:00:22Z

2010-07-13T02:37:11Z

@@ Line 81: / Line 81: @@
 # The system shall provide the capability to interface with multiple image stores.
 #* '''a)''' The image store interface shall provide support for multiple sources/back-ends.
-#* '''b)''' The image store interface shall provide support for http, nfs, and ec2.
+#* '''b)''' The image store interface shall provide support for RS-CF, http, nfs.
 #* '''c)''' The image store interface shall be modular.
 # The system shall provide support for OVF.

@@ Line 19: / Line 19: @@
 #* '''a)''' if components fail, they shall fail closed
 #* '''b)''' a compromised component shall not lead to cascading compromising of entire system
 ==== API candidate functions ====

@@ Line 63: / Line 63: @@
 * Audit logs of ''who did what'' to cloud resources
 * User provided naming and descriptions facilitate groups
 === Image Caching ===

@@ Line 16: / Line 16: @@
 # The system shall support fully asynchronous API design.
 #* '''a)''' The system shall support the option for synchronous APIs (e.g., IP Address)
 ==== API candidate functions ====
@@ Line 49: / Line 52: @@
 #* '''b)''' ... retrieve details on a shared IP group.
 #* '''c)''' ... delete a shared IP group.
-# use webhooks (http callbacks) to send information on state change
+# use webhooks (http callbacks) to send information on state change?
 === Projects/Groups & Users ===

@@ Line 4: / Line 4: @@
 Live notes may be taken for this topic at: http://etherpad.openstack.org/Requirements
-Requirements solicitation for this Summit will focus on those areas of immediate interest for imminent development. In particular, the API and Image Caching.
+Requirements solicitation for this Summit will focus on those areas of immediate interest for imminent development. In particular, the API and Image Caching, as these somewhat define the bounds of our system (customer interface and storage interface).
 === API ===

@@ Line 40: / Line 40: @@
 #* '''d)''' ... retrieve details of an image.
 #* '''e)''' ... delete a stored image.
-#* '''f)''' ...
+#* '''f)''' ... enable/disable scheduled back-ups of a server.
+#*# indicate schedule for back-ups of a server.
-<!-- # List Backup Schedules -->
+#*# indicate retention policy for scheduled back-ups of a server.
-<!-- # Create/Update Backup Schedule -->
+# ... retrieve a list of shared IP groups.
-<!-- # Disable Backup Schedule -->
+#* '''a)''' ... create shared IP groups.
-<!-- # List Shared IP Groups -->
+#* '''b)''' ... retrieve details on a shared IP group.
-<!-- # Create Shared IP Groups -->
+#* '''c)''' ... delete a shared IP group.
 === Image Caching ===
@@ Line 60: / Line 58: @@
 #* '''c)''' The image store interface shall be modular.
 # The system shall provide support for OVF.

← Older revision		Revision as of 03:00, 13 July 2010
Line 51:		Line 51:

	=== Image Caching ===		=== Image Caching ===
		+
		+	# The system shall provide the capability to cache images.
		+	#* '''a)''' The system shall provide the option not to cache images.
		+	#* '''b)''' The system shall provide the capability to configure expiration policy for an image (e.g., base images)
		+	# The system shall provide the capability to interface with multiple image stores.
		+	#* '''a)''' The image store interface shall provide support for multiple sources/back-ends.
		+	#* '''b)''' The image store interface shall provide support for http, nfs, and ec2.
		+	#* '''c)''' The image store interface shall be modular.
		+	# The system shall provide support for OVF.

@@ Line 38: / Line 38: @@
 #* '''b)''' ... retrieve a list of available images.
 #* '''c)''' ... create an image from an existing server.
 <!-- # List Backup Schedules -->
 <!-- # Create/Update Backup Schedule -->