Difference between revisions of "TripleO/TuskarGlossary"
(→Image) |
(→Resource (Rack and Node)) |
||
Line 31: | Line 31: | ||
* '''Controller Rack''' A Rack that belongs to a Controller Resource Class. | * '''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. | + | :* '''* 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. | :* '''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. | + | * '''* 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 | + | :* '''* 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. | + | :* '''* Resource Nodes''' These are all other Nodes in a Resource Rack. |
== Image == | == Image == | ||
An Image is provisioned on Nova Baremetal Nodes. | An Image is provisioned on Nova Baremetal Nodes. |
Revision as of 13:32, 18 September 2013
* Names marked with an asterisk may change in the future
Resource Class
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.
Tuskar supports four Resource Class types:
- Controller Class Class that provides all services other than compute and storage services
- 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
A Flavor is a virtual hardware configuration. Its definition is aligned with the "instance_type" (aka 'Flavor') used in the OpenStack Nova API.
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.
When a Node is provisioned, the Flavors that are defined for that Node's Resource Class are registered in Nova,
Resource (Rack and Node)
There are two kinds of Resources:
- 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.