openstack/nova
Code Issues Proposed changes

Docs: Add Placement to Nova system architecture

Browse Source 
Changes in svg:
- schema with nova-network is removed and one with Neutron is made as default
- Placement service is added to a party
- titles and arrows are aligned

Change-Id: If7e4a0b92c8713dabcb16a5e7820fbf479d82917
This commit is contained in:
Andrey Volkov 2018-07-19 18:10:25 +03:00
parent 50f40854b0
commit 3a26ad77e8
2 changed files with 1158 additions and 410 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1564
doc/source/_static/images/architecture.svg
View File

File diff suppressed because it is too large Load Diff
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 53 KiB

After

Width:  |  Height:  |  Size: 44 KiB

4
doc/source/user/architecture.rst
View File

@ -48,7 +48,7 @@ Components
----------
Below you will find a helpful explanation of the key components
of a typical (non-cells v1) Nova deployment.
of a typical Nova deployment.
.. image:: /_static/images/architecture.svg
:width: 100%
@ -56,9 +56,9 @@ of a typical (non-cells v1) Nova deployment.
* DB: sql database for data storage.
* API: component that receives HTTP requests, converts commands and communicates with other components via the **oslo.messaging** queue or HTTP.
* Scheduler: decides which host gets each instance.
* Network: manages ip forwarding, bridges, and vlans.
* Compute: manages communication with hypervisor and virtual machines.
* Conductor: handles requests that need coordination (build/resize), acts as a
database proxy, or handles object conversions.
* `Placement <https://docs.openstack.org/nova/latest/user/placement.html>`__: tracks resource provider inventories and usages.
While all services are designed to be horizontally scalable, you should have significantly more computes than anything else.