Difference between revisions of "TripleO/TuskarGlossary"
< TripleO
m (Tzumainn moved page Tuskar/Glossary to TripleO/TuskarGlossary: move Tuskar under TripleO program) |
(Updated with Icehouse terminology) |
||
Line 3: | Line 3: | ||
Tuskar is built with Triple-O in mind; as such, it may be useful to familiarize yourself with the [https://github.com/openstack/tripleo-incubator#architecture Triple-O architecture]. | Tuskar is built with Triple-O in mind; as such, it may be useful to familiarize yourself with the [https://github.com/openstack/tripleo-incubator#architecture Triple-O architecture]. | ||
− | + | == Overcloud == | |
− | == Resource | + | == Resource Category == |
− | + | One way an Overcloud can be configured is by specifying the scale of the services that will run once it is deployed (e.g., 3 Controller instances and 2 Compute instances). These services are specified by Resource Categories: | |
− | + | * '''Controller''' - provides all services other than compute and storage services | |
+ | * '''Compute''' - defines and provides compute services | ||
+ | * '''Object Storage''' - defines and provides object storage services | ||
+ | * '''Block Storage''' - defines and provides block storage service | ||
− | + | On a functional level, a Resource Category points to an image in Glance that will be used by Heat for provisioning. | |
− | |||
− | |||
− | |||
− | == | + | == Node == |
− | + | A Node is a single physical compute unit. It corresponds to a compute Node in Nova Baremetal or Ironic. | |
− | + | In Tuskar, a Node can either be: | |
− | + | * '''Resource''' - a Heat Resource is running on the Node | |
− | + | * '''Free''' - available for use | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | * ''' | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | * ''' | ||
− | |||
− | |||
− | |||
− |
Revision as of 15:06, 14 January 2014
Contents
Overview
Tuskar is built with Triple-O in mind; as such, it may be useful to familiarize yourself with the Triple-O architecture.
Overcloud
Resource Category
One way an Overcloud can be configured is by specifying the scale of the services that will run once it is deployed (e.g., 3 Controller instances and 2 Compute instances). These services are specified by Resource Categories:
- Controller - provides all services other than compute and storage services
- Compute - defines and provides compute services
- Object Storage - defines and provides object storage services
- Block Storage - defines and provides block storage service
On a functional level, a Resource Category points to an image in Glance that will be used by Heat for provisioning.
Node
A Node is a single physical compute unit. It corresponds to a compute Node in Nova Baremetal or Ironic.
In Tuskar, a Node can either be:
- Resource - a Heat Resource is running on the Node
- Free - available for use