5fca287eb5
There are several instances of "Block Storage Service" in the upstream documentation. As was recently clarified in the docs mailing list, these should be "Block Storage service". This patch applies the fix. Change-Id: I591c100ab031b75f1c0d27d45f53e32401a26e30 Partial-Bug: #1217503
79 lines
3.3 KiB
XML
79 lines
3.3 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<section xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
version="5.0"
|
|
xml:id="architecture">
|
|
<title>Architecture</title>
|
|
<section xml:id="header">
|
|
<title>Header</title>
|
|
<para>
|
|
Copyright 2010-2011 United States Government as represented by the
|
|
Administrator of the National Aeronautics and Space Administration.
|
|
All Rights Reserved.
|
|
Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
not use this file except in compliance with the License. You may obtain
|
|
a copy of the License at
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
License for the specific language governing permissions and limitations
|
|
under the License.
|
|
</para>
|
|
</section>
|
|
<section xml:id="Cinder-System-Architecture">
|
|
<title>Block Storage System Architecture</title>
|
|
<para>
|
|
The OpenStack Block Storage service is intended to run on one or more nodes.
|
|
Block Storage uses a SQL-based central database that is shared by all Block Storage services in the system. The amount and depth of the data fits into a SQL database quite well. For small deployments this seems like an optimal solution. For larger deployments, and especially if security is a concern, Block Storage will be moving towards multiple data stores with some kind of aggregation system.
|
|
</para>
|
|
</section>
|
|
<section xml:id="Components">
|
|
<title>Components</title>
|
|
<para>
|
|
Below you will a brief explanation of the different components.
|
|
/- ( LDAP )
|
|
[ Auth Manager ] ---
|
|
| \- ( DB )
|
|
|
|
|
|
|
|
cinderclient |
|
|
/ \ |
|
|
[ Web Dashboard ]- -[ API ] -- [ AMQP ] -- [ scheduler ] -- [ volume ] -- ( iSCSI )
|
|
\ / |
|
|
novaclient |
|
|
|
|
|
|
|
|
|
|
|
[ REST ]
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>DB: SQL database for data storage. Used by all
|
|
components (LINKS NOT SHOWN)</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Web Dashboard: potential external component that talks to the
|
|
API</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>API: component that receives HTTP requests, converts commands
|
|
and communicates with other components via the queue or HTTP</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Auth Manager: component responsible for users/projects/and
|
|
roles. Can use as back-end a database or LDAP. This is not a
|
|
separate binary, but rather a python class that is used by most
|
|
components in the system.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>scheduler: decides which host gets each volume</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>volume: manages dynamically attachable block devices.</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
</para>
|
|
</section>
|
|
</section>
|