"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "doc/source/architecture.rst" between
masakari-8.0.0.tar.gz and masakari-9.0.0.tar.gz

About: OpenStack Masakari provides "Instances High Availability Service" for OpenStack clouds by automatically recovering failed Instances (currently for KVM-based Virtual Machine(VM)s).
The "Ussuri" series (latest release).

architecture.rst  (masakari-8.0.0):architecture.rst  (masakari-9.0.0)
skipping to change at line 19 skipping to change at line 19
Unless required by applicable law or agreed to in writing, software Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations License for the specific language governing permissions and limitations
under the License. under the License.
Masakari System Architecture Masakari System Architecture
============================ ============================
Masakari is comprised of two services api and engine, each performing different Masakari comprises of two services api and engine, each performing different
functions. The user-facing interface is a REST API, while internally Masakari functions. The user-facing interface is a REST API, while internally Masakari
communicates via an RPC message passing mechanism. communicates via an RPC message passing mechanism.
The API servers process REST requests, which typically involve database The API servers process REST requests, which typically involve database
reads/writes, sending RPC messages to other Masakari engine, reads/writes, sending RPC messages to other Masakari engine,
and generating responses to the REST calls. and generating responses to the REST calls.
RPC messaging is done via the **oslo.messaging** library, RPC messaging is done via the **oslo.messaging** library,
an abstraction on top of message queues. an abstraction on top of message queues.
Masakari engine will run on same host where masakari api is running, and have The Masakari engine will run on the same host where the Masakari api is
a `manager` that is listening for `RPC` messages. running, and has a `manager` that is listening for `RPC` messages.
The manager also, optionally, has periodic tasks. The manager too has periodic tasks.
Components Components
---------- ----------
Below you will find a helpful explanation of the key components Below you will find a helpful explanation of the key components
of a typical Masakari deployment. of a typical Masakari deployment.
.. image:: ./images/architecture.png .. image:: /_static/architecture.png
:width: 100% :width: 100%
* DB: sql database for data storage. * DB: sql database for data storage.
* API: component that receives HTTP requests, converts commands and * API: component that receives HTTP requests, converts commands and
communicates with masakari engine via the **oslo.messaging** queue. communicates with masakari engine via the **oslo.messaging** queue.
* Engine: Executes recovery workflow and communicates with nova via HTTP. * Engine: Executes recovery workflow and communicates with nova via HTTP.
 End of changes. 4 change blocks. 
6 lines changed or deleted 6 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)