openstack/deb-murano
Code Issues Proposed changes
f72d767a93
deb-murano/doc/source/intro/architecture.rst
Maria Zlatkova 3621ce1142 [Docs] Restructuring 
* Moves the remaining guides from the Draft folder
* Removes already rewritten articles (Murano TroubleShooting and Debug Tips)
* Restructures the main page
* Fixes build errors
* Adds minor editorial changes to some sections

Change-Id: I1aa961f34860b22241b69d41045da445d223be06
Partial-Bug: #1603950
2016-11-10 13:12:15 +02:00

1.1 KiB
Raw Blame History

Architecture

Murano is composed of the following major components:

  • murano command-line client
  • murano-dashboard
  • murano-api
  • murano-engine
  • murano-agent

They interact with each other as illustrated in the following diagram:

Murano architecture

All remote operations on users' servers, such as software installation and configuration, are carried out through an AMQP queue to the murano-agent. Such communication can easily be configured on a separate instance of AMQP to ensure that the infrastructure and servers are isolated.

Besides, Murano uses other OpenStack services to prevent the reimplementation of the existing functionality. Murano interacts with these services using their REST API through their python clients.

The external services used by Murano are:

  • the Orchestration service (Heat) to orchestrate infrastructural resources such as servers, volumes, and networks. Murano dynamically creates heat templates based on application definitions.
  • the Identity service (Keystone) to make murano API available to all OpenStack users.