The Murano Service communicates with the following OpenStack components:
Horizon - provides a GUI with ability to use all Murano features;
Keystone - authenticates users and provides the security token that is used to work with OpenStack, hence limiting the user abilities in Murano based on OpenStack privileges;
Heat - is used to provision VMs and other OpenStack resources
Glance - stores VM images, with preconfigured OS and a containing sets of initial scripts
Quantum - provides the network configuration API
Agent - provides agent functionality to communicate with the Orchestration Engine and executes tasks on VMs
REST API
Murano exposes a service endpoint for communication with a client. It exposes API functions to manipulate objects such as environment and service. This component is responsible for translating API function parameters to Object Model attributes and propagating the deployment status from the Orchestration Engine.
Object Model
An internal representation of Services and Environments. All attributes and entities are described in the API specification.
Orchestration Engine
This is the core component which evaluates Object Model changes and creates a plan for implementing these changes on the instances or in the cloud. This component will support extensions via plug-ins. Plugins can add new services and extend existing services for integration.
Metadata Repository
Murano Repository operates with metadata objects: store, display, group and use for deployment. Custom objects can be uploaded to the Murano Metadata Server and these data will be accessible to all Murano components.
Integration with Heat
Heat is a cloud resource management engine that allows you to manipulate resources that represent OpenStack entities (Security Groups, Instances, Floating IPs, Volumes, etc.) and some entities such as AutoScaling groups from a single point of control.
OpenStack resource provisioning is one of the steps required for environment deployment and Heat will be used for that purpose. Heat allows you to define all OpenStack resources in a single document that will be easy to maintain and will not require resorting to multiple OpenStack APIs while keeping the software configuration separate.
