Difference between revisions of "RequirementsSolicitation"
| Line 40: | Line 40: | ||
#* '''d)''' ... retrieve details of an image. | #* '''d)''' ... retrieve details of an image. | ||
#* '''e)''' ... delete a stored image. | #* '''e)''' ... delete a stored image. | ||
| − | #* '''f)''' ... | + | #* '''f)''' ... enable/disable scheduled back-ups of a server. |
| − | + | #*# indicate schedule for back-ups of a server. | |
| − | + | #*# indicate retention policy for scheduled back-ups of a server. | |
| − | + | # ... retrieve a list of shared IP groups. | |
| − | + | #* '''a)''' ... create shared IP groups. | |
| − | + | #* '''b)''' ... retrieve details on a shared IP group. | |
| − | + | #* '''c)''' ... delete a shared IP group. | |
| − | |||
| − | |||
=== Image Caching === | === Image Caching === | ||
| Line 60: | Line 58: | ||
#* '''c)''' The image store interface shall be modular. | #* '''c)''' The image store interface shall be modular. | ||
# The system shall provide support for OVF. | # The system shall provide support for OVF. | ||
| + | #* '''a)''' Question: should we be supporting multiple VMs in a single OVF manifest? | ||
| + | #* '''b)''' Question: what (other) portions of OVF should we be supporting? | ||
| + | # Question: What back-up approach should we be supporting (e.g., deltas? full back-ups, etc.)? | ||
Revision as of 03:30, 13 July 2010
Requirements Solicitation
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.
API
General Requirements
- The system shall support the capability to run multiple APIs.
- a) The system shall support the capability for each API to run in it's own URL namespace. (e.g., Rackspace vs. EC2)
- 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
- The system shall support the capability to ...
- a) ... retrieve a list of servers.
- b) ... create a server.
- c) ... get details of a server.
- d) ... update the name of a server.
- e) ... update the administrative password of a server.
- f) ... delete a server.
- g) ... retrieve a list of addresses.
- h) ... retrieve a list of public addresses.
- i) ... retrieve a list of private addresses.
- j) ... share an IP address.
- k) ... unshare an IP address.
- l) ... reboot a server.
- m) ... rebuild a server.
- n) ... resize a server.
- ... confirm a resized server.
- ... revert a resized server.
- ... retrieve a list of available configurations (flavors).
- a) ... retrieve details of a selected configuration.
- b) ... retrieve a list of available images.
- c) ... create an image from an existing server.
- d) ... retrieve details of an image.
- e) ... delete a stored image.
- f) ... enable/disable scheduled back-ups of a server.
- indicate schedule for back-ups of a server.
- indicate retention policy for scheduled back-ups of a server.
- ... retrieve a list of shared IP groups.
- a) ... create shared IP groups.
- b) ... retrieve details on a shared IP group.
- c) ... delete a shared IP group.
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.
- a) Question: should we be supporting multiple VMs in a single OVF manifest?
- b) Question: what (other) portions of OVF should we be supporting?
- Question: What back-up approach should we be supporting (e.g., deltas? full back-ups, etc.)?
