Public | Automated Build

Last pushed: 2 years ago
Short Description
Full Description

Murano Helloworld


Hello world for OpenStack Murano. For those who just started to get Murano set up for prototype or testing, it is common to run into dependencies issue of various python packages managed via native package management system and pip. The goal of this exercise is to set up Murano quickly in a docker container so that developers can focus on exploring Murano features instead of spending valable time on setting up dev environment.

This was based on the steps from and


  1. Install docker (e.g., on Ubuntu:
  2. In existing OpenStack, create a network/subnet connected to external network and configure DNS servers by editing the subnet so that the VMs can pull packages from internet during Murano deployment.
  3. User must have heat_stack_owner role in order to deploy Murano catalogy.

Start Murano Services

git clone

Edit to set parameters to your OpenStack deployments. At a minimum, you will need to adjust the following parameters.


Optionally, if you want Murano to use rabbitmq on your existing OpenStack and keep the one on the container for VMs, set the following parameters.


To start

# sudo ./

To access Murano dashboard, point your browser to Adjust the URL to your container host hostname/IP address.

The following services are running inside the container:

  • Murano API service
  • Murano Engine
  • Horizon with Murano dashboard
  • rabbitmq and mysql

Upon container start, Murano service and endpoints are created in keystone.

Deploy application catalog

To deploy application catalog, follow the steps in

You can also attach to the docker container to run murano cli client. By default, the container name is "murano" as set in the script.

# docker exec -it murano bash

~/murano# export OS_USERNAME=admin
~/murano# export OS_PASSWORD=password
~/murano# export OS_AUTH_URL=
~/murano# export OS_TENANT_NAME=admin

Sample commands:
~/murano# murano package-list
~/murano# murano environment-list


By default, the script places logs files at /tmp/murano/logs on the docker host.

  • murano-dashboard.log
  • murano-init.log
  • mysqld.log
  • murano-api.log
  • murano-engine.log
  • murano-rabbitmq.log

Useful information on the VMs deployed by Murano.

  • /var/log/murano-agent.log
  • /etc/murano/agent.conf
  • /etc/resolve.conf. Make sure your DNS servers show up there.

Common issues:

  • OpenStack username/password are wrong. Check murano-init.log.
  • OpenStack rabbitmq username/password are wrong or firewall blocks rabbitmq port. Check murano-engine.log and murano-api.log
  • DNS servers not configured for the subnet. This will cause the VM not being able to pull packages from internet.
  • Time skew between your docker host and OpenStack. This may show up as SSL error or 403 Proxy unacknowledged in /var/log/murano-agent.log on the VM.
Docker Pull Command
Source Repository