c6036a4c8e
Files converted: - common/ch_getstart.xml - common/section_getstart_compute.xml - common/section_storage-concepts.xml - common/section_getstart_object-storage.xml - common/section_getstart_block-storage.xml - common/section_getstart_networking.xml - common/section_getstart_dashboard.xml - common/section_keystone-concepts.xml - common/section_getstart_image.xml - common/section_getstart_telemetry.xml - common/section_getstart_orchestration.xml - common/section_getstart_trove.xml - common/section_getstart_sahara.xml - common/section_getstart_conceptual_arch.xml - common/section_getstart_logical_arch.xml Change-Id: I41318a887af6855f3a25e6adedbbd9e75f431332 Implements: blueprint reorganise-user-guides
44 lines
1.8 KiB
ReStructuredText
44 lines
1.8 KiB
ReStructuredText
.. :orphan:
|
|
|
|
Logical architecture
|
|
~~~~~~~~~~~~~~~~~~~~
|
|
|
|
To design, deploy, and configure OpenStack, administrators must
|
|
understand the logical architecture.
|
|
|
|
As shown in Conceptual architecture, OpenStack consists of several
|
|
independent parts, named the OpenStack services. All services authenticate
|
|
through a common Identity service. Individual services interact with each
|
|
other through public APIs, except where privileged administrator commands
|
|
are necessary.
|
|
|
|
.. TODO (DC) Add link to figure in get_started_conceptual_architecture.rst
|
|
|
|
Internally, OpenStack services are composed of several processes. All
|
|
services have at least one API process, which listens for API requests,
|
|
preprocesses them and passes them on to other parts of the service. With
|
|
the exception of the Identity service, the actual work is done by
|
|
distinct processes.
|
|
|
|
For communication between the processes of one service, an AMQP message
|
|
broker is used. The service's state is stored in a database. When
|
|
deploying and configuring your OpenStack cloud, you can choose among
|
|
several message broker and database solutions, such as RabbitMQ, Qpid,
|
|
MySQL, MariaDB, and SQLite.
|
|
|
|
Users can access OpenStack via the web-based user interface implemented
|
|
by the OpenStack dashboard, via `command-line
|
|
clients <http://docs.openstack.org/cli-reference/content>`__ and by
|
|
issuing API requests through tools like browser plug-ins or :command:`curl`.
|
|
For applications, `several SDKs <http://developer.openstack.org/#sdk>`__
|
|
are available. Ultimately, all these access methods issue REST API calls
|
|
to the various OpenStack services.
|
|
|
|
.. TODO (DC) on line 30, Add link to get_started_openstack_dashboard.RST
|
|
|
|
The following diagram shows the most common, but not the only possible,
|
|
architecture for an OpenStack cloud:
|
|
|
|
.. image:: figures/openstack-arch-kilo-logical-v1.png
|
|
:alt: Logical architecture
|