1.2. Architecture
The following diagram provides a high-level overview of the OpenStack architecture.
Each OpenStack service has a code name, which is reflected in the names of configuration files and command-line utility programs. For example, the Identity service has a configuration file called
keystone.conf.
The Service Details section provides more detailed information about the OpenStack service components. Each OpenStack service is comprised of a collection of Linux services, MySQL databases, or other components. Together these provide a functional group. For example, the Table 1.1. Services
| Section | Code name | Description | |
|---|---|---|---|
| Dashboard | Horizon |
A web-based dashboard for managing OpenStack services.
|
| Identity | Keystone | A centralized identity service that provides authentication and authorization for other services, and manages users, tenants, and roles. |
| OpenStack Networking | Neutron | A networking service that provides connectivity between the interfaces of other OpenStack services. |
| Block Storage | Cinder | A service that manages persistent block storage volumes for virtual machines. |
| Compute | Nova | A service that launches and schedules networks of machines running on nodes. |
| Image | Glance | A registry service for virtual machine images. |
| Object Storage | Swift | A service providing object storage which allows users to store and retrieve files (arbitrary data). |
|
Telemetry
| Ceilometer | A service providing measurements of cloud resources. |
|
Orchestration
| Heat | A service providing a template-based orchestration engine, which supports the automatic creation of resource stacks. |
glance-api and glance-registry Linux services, together with a MySQL database, implement the Image service.