TripleO/TuskarIcehouseRequirements

Overview

This document lists known requirements for the Icehouse release, as well as requirements that may not make it into Icehouse, but which will affect our design. The relevant mailing list discussion can be found here.

All requirements here are assumed to be targeted for Icehouse, except where otherwise marked:

• * Maybe Icehouse, dependency on other features being developed in the Icehouse timeframe
• ** After Icehouse

Nodes

Creation

• Manual registration
  • hardware specs from Ironic based on mac address (*)
  • IP auto populated from Neutron (**)
  • Auto-discovery during undercloud install process (*)

Monitoring

• assignment, availability, status
• capacity, historical statistics (*)

Management node

• where triple-o is installed
• created as part of undercloud install process
• can create additional management nodes (**)

Resource nodes

• searchable by status, name, cpu, memory, and all attributes from ironic
• can be allocated as one (and only one) of four node types
  • compute
  • controller
    • each controller node will run all openstack services
      • allow each node to run specified service (**)
      • breakdown by workload (percentage of cpu used per node) (*)
  • object storage
  • block storage
• once allocated, can be unallocated
• Resource class - allows for further categorization of a node type
  • each node type specifies a single default resource class
    • allow multiple resource classes per node type (*)
  • Node profile for a resource class (*)
    • acts as an optional filter for nodes that can be allocated to that class (*)
• nodes can be viewed by node types
  • additional 'group by' with status, hardware specification

Unallocated nodes

• list
• unregister

Archived nodes (**)

• Will be separate openstack service (**)