Jump to: navigation, search

Difference between revisions of "RequirementsSolicitation"

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.

Revision as of 03:00, 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

  1. 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)
  2. 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

  1. 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.
      1. ... confirm a resized server.
      2. ... revert a resized server.
  2. ... 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) ...


Image Caching

  1. 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)
  2. 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.
  3. The system shall provide support for OVF.