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: @@
-'''''* Names marked with an asterisk may change in the future'''''
+== Overview ==
-== Resource Class ==
+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].
-A Resource Class can be thought of as a cloud 'building block'.  It consists of a set of Racks, and defines the services provided by the Nodes in those Racks.
+== Overcloud ==
-Tuskar supports four Resource Class types:
+== Overcloud Role ==
-* '''Controller Class''' Class that provides all services other than compute and storage services
+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:
-* '''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
-=== * Flavors ===
+* '''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
-A Flavor is a virtual hardware configuration.  Its definition is aligned with the "instance_type" (aka 'Flavor') used in the OpenStack Nova API.
+On a functional level, an Overcloud Role points to an image in Glance that will be used by Heat for provisioning.
-Flavors are defined for a given Compute Resource Class and semantically describe the types of compute instances that can be launched for that ResourceClass. Each Flavor has a set of Capacities that describe a particular aspect of the virtual hardware configuration, such as cpu, memory or storage.
+== Node ==
-When a Node is provisioned, the Flavors that are defined for that Node's Resource Class are registered in Nova,
+A Node is a single physical compute unit.  It corresponds to a compute Node in Nova Baremetal or Ironic.
-== Resource (Rack and Node) ==
+In Tuskar, a Node can either be:
-There are two kinds of Resources:
+* ''Deployed''' - a Heat Resource is running on the Node
+* '''Free''' - available for use
-* '''Node''' A Node is a single physical compute unit.  It corresponds to a compute Node in Nova Baremetal (and eventually, in Ironic).
-* '''Rack''' A Rack is a physical or logical grouping of Nodes.  It can be thought of as a server rack in a datacenter.  A Rack is assigned to a Resource Class, and can be managed as a single unit.
-There are two types of Racks:
-* '''Controller Rack''' A Rack that belongs to a Controller Resource Class.
-:* '''Management Node''' This Node is responsible for all Undercloud services.  It also controls the rest of the Nodes in the Controller Rack.
-:* '''Controller Node''' These are all other Nodes in a Controller Rack.  Controller Nodes run non-resource Overcloud services.
-* '''Resource Rack'''  A Rack that belongs to a Compute/Object Storage/Block Storage Resource Class.
-:* '''Leaf Management Node''' This Node has responsibility for all other Nodes in the Resource Rack
-:* '''Resource Nodes''' These are all other Nodes in a Resource Rack.
-== Image ==
-An Image is provisioned on Nova Baremetal Nodes.