7ec78aef2d
was incorrectly placed in trunk/training-guide non-plural, now trunk/training-guides. also add redirect from trunk/openstack-training and trunk/training-guide to the new location. Change-Id: I0648a9604dc6a1d6c7480a90c07871608a8752ca Closes-Bug: #1255684
64 lines
3.2 KiB
XML
64 lines
3.2 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>Cinder-System-Architecture</title>
|
|
<para>
|
|
==========================
|
|
The Cinder Block Storage Service is intended to be ran on one or more nodes.
|
|
Cinder uses a sql-based central database that is shared by all Cinder 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, cinder 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 backend to DB 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> |