Difference between revisions of "TripleO/TuskarGlossary"
(→Images) |
(→Resources) |
||
Line 18: | Line 18: | ||
When a Node is provisioned, the Flavors that are defined for that Node's Resource Class are registered in Nova, | 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. | ||
== Images == | == Images == | ||
Images are provisioned on Baremetal Nodes. They allow Overcloud services to run. | Images are provisioned on Baremetal Nodes. They allow Overcloud services to run. |
Revision as of 05:06, 18 September 2013
Resource Class
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 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 hardware configuration. Its definition is aligned with the "instance_type" (aka 'Flavor') used in the OpenStack Nova API.
Flavors are defined for a given ResourceClass 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 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.
Images
Images are provisioned on Baremetal Nodes. They allow Overcloud services to run.