Page History

...

Stack administration

• Admin user can create / start / stop stacks. We will need to revisit the workflow for admin.

Add stack

• Preconditions
  • Logged in
  • Service exists
• Test steps
  
  • ndslabsctl add stack <key> <name> 
  • ndslabsctl add stack <key> <name> --opt=<comma-separated list of optional services>
• Expected results
  • Stack is added
• Alternate flow
  • Not logged in (401)
  • Service doesn't exist (404)
  • Duplicate stack name (409)

List stacks

List stacks

• Preconditions:
  • Logged in
  • Stack has been added
• Test steps
  
  • ndslabsctl list stacks
• Expected results
  • Summary of stacks is displayed (name, services, status, SIDs)
• Alternate flow:
  
  • Not logged in (401)
  • No stacks (empty list)

Delete stack

• Preconditions:
  • Logged in
  • Stack exists
  • Stack not running
• Test steps
  
  • ndslabsctl delete stack <sid>
  • Stack is deleted (201)
• Alternate flow
  • Not logged in (401)
  • Stack doesn't exist (404)
  • Stack is running (409)
  • Attached volumes are orphaned

Get stack details

• Preconditions:
  • Logged in
  • Stack exists
• Test steps
  
  • ndslabsctl get stack <sid>
• Expected results
  • Stack details, including endpoints and config, are displayed
• Alternate flow
  • Not logged in (401)
  • Stack doesn't exist (404)

Start stack

• Preconditions
  • Logged in
  • Stack exists and started
• Test steps
  
  • ndslabsctl start <sid>
• Expected results
  
  • All stack services (service, replication controller, pods) are started and ready
• Alternate flow
  • Not logged in (401)
  • Stack doesn't exist (404)
  • Stack not started or stopping (409)

Stop stack

• Preconditions
  • Stack started
• Test steps
  • ndslabsctl stop <sid>
• Expected results
  
  • Stack service, replication controller, pods are stopped (200)
• Alternative flow
  • Not logged in (401)
  • Stack does not exist (404)
  • Stack not started (200)

Service administration

Add service (admin only)

• Preconditions:
  • Admin is logged in
• Test steps
  
  • ndslabsctl add service -f <service.json>
  • ndslabsctl add service --file <service.json>
• Expected results
  • Service is added. User can add service/stack.
• Alternate flows
  • Service exists with same key (409 conflict)
  • Logged in user is not admin (401 unauthorized)
• Notes:
  • See ndslabs-specs repos for sample services

...

• Preconditions
  • Logged in
  • Volume exists
  • Stack not running
• Test case:
  • ndslabsctl delete <vol name>
• Expected results:
  
  • Volume is deleted
• Alternative flow
  • Not logged in (401)
  • Volume doesn't exist (404)
  • Stack is running (409)

Stack administration

• Admin user can create / start / stop stacks. We will need to revisit the workflow for admin.

Add stack

• Preconditions
  • Logged in
  • Service exists
• Test steps
  
  • ndslabsctl add stack <key> <name> 
  • ndslabsctl add stack <key> <name> --opt=<comma-separated list of optional services>
• Expected results
  • Stack is added
• Alternate flow
  • Not logged in (401)
  • Service doesn't exist (404)
  • Duplicate stack name (409)

List stacks

List stacks

• Preconditions:
  • Logged in
  • Stack has been added
• Test steps
  
  • ndslabsctl list stacks
• Expected results
  • Summary of stacks is displayed (name, services, status, SIDs)
• Alternate flow:
  
  • Not logged in (401)
  • No stacks (empty list)

Delete stack

• Preconditions:
  • Logged in
  • Stack exists
  • Stack not running
• Test steps
  
  • ndslabsctl delete stack <sid>
  • Stack is deleted (201)
• Alternate flow
  • Not logged in (401)
  • Stack doesn't exist (404)
  • Stack is running (409)
  • Attached volumes are orphaned

Get stack details

• Preconditions:
  • Logged in
  • Stack exists
• Test steps
  
  • ndslabsctl get stack <sid>
• Expected results
  • Stack details, including endpoints and config, are displayed
• Alternate flow
  • Not logged in (401)
  • Stack doesn't exist (404)

Start stack

• Preconditions
  • Logged in
  • Stack exists and started
• Test steps
  
  • ndslabsctl start <sid>
• Expected results
  
  • All stack services (service, replication controller, pods) are started and ready
• Alternate flow
  • Not logged in (401)
  • Stack doesn't exist (404)
  • Stack not started or stopping (409)

Stop stack

• Preconditions
  • Stack started
• Test steps
  • ndslabsctl stop <sid>
• Expected results
  
  • Stack service, replication controller, pods are stopped (200)
• Alternative flow
  • Not logged in (401)
  • Stack does not exist (404)
  • Stack not started (200)

Configuration

Get stack service configuration

...