Difference between revisions of "TripleO/TuskarGlossary"

Latest revision as of 19:29, 4 February 2014

Overview

Tuskar is built with Triple-O in mind; as such, it may be useful to familiarize yourself with the Triple-O architecture.

Overcloud

Overcloud Role

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 Roles:

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, an Overcloud Role 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:

Deployed' - a Heat Resource is running on the Node
Free - available for use

@@ Line 1: / Line 1: @@
-== Resource Class ==
+== Overview ==
-A Resource Class can be thought of as a cloud 'building block'.  It consists of a set of Racks, and defines the types of VM instances that can be supported by the Nodes in those Racks.
+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 supports four Resource Class types:
+== Overcloud ==
-* '''Controller Class''' Class that provides all services other than compute and storage services
+== Overcloud Role ==
-* '''Compute Class''' Class that defines and provides compute services
-* '''Object Storage Class''' Class that defines and provides object storage services
-* '''Block Storage Class''' Class that defines and provides block storage service
-== Resources ==
+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 Roles:
-== Images ==
+* '''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, an Overcloud Role 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:
+* ''Deployed''' - a Heat Resource is running on the Node
+* '''Free''' - available for use