#FIWARE Application Manager GE: Murano
- Introduction
- GEi overall description
- Build and Install
- API Overview
- Testing
- Advanced topics
- Support
- License
This is the code repository for FIWARE Application Manager GE - Murano, FIWARE Cloud implementations of the OpenStack Murano components with docker. We are working directly over OpenStack Community so the information that we keep here is specific to the FIWARE implementation. The rest can be found in the OpenStack Community directly.
This project is part of FIWARE. Check also the FIWARE Catalogue entry for Murano
Any feedback on this documentation is highly welcome, including bugs, typos or things you think should be included but aren't. You can use github issues to provide feedback.
The Murano Project introduces an application catalog to OpenStack, enabling application developers and cloud administrators to publish various cloud-ready applications in a browsable categorized catalog. Cloud users -- including inexperienced ones -- can then use the catalog to compose reliable application environments with the push of a button.
The key goal is to provide UI and API which allows to compose and deploy composite environments on the Application abstraction level and then manage their lifecycle. The Service should be able to orchestrate complex circular dependent cases in order to setup complete environments with many dependent applications and services. However, the actual deployment itself will be done by the existing software orchestration tools (such as Heat), while the Murano project will become an integration point for various applications and services.
For latest releases of Murano please refer to OpenStack releases For release notes of Murano projects please refer to release note pages for murano, murano-dashboard, python-muranoclient, and murano-agent.
FIWARE Murano, keep the specific configuration of OpenStack Murano to be applied in FIWARA Lab environment besides with the docker file to use Murano with dockers.
If you planned to install Murano from the OpenStack you can follow the oficial OpenStack Murano Installation Guide
In addition to the oficial Murano documentation, to be FIWARE Murano aware, we need to install some extensions to Murano core library. It involves mainly the addition of:
- the FiwareMuranoInstance instance: this is a Murano instance which includes the region and the GE NID (in case required) in the deployed VMs. This is required for FIWARE monitoring.
- the script key: There is a support script which includes a support key to be used by region administrators to give support to users.
- the murano agent configuration file: It includes different murano-agent configuration files for services to be included in the different linux distributions.
fiware-murano repository contains a script which installs all the FIWARE specific requirements. This script is in charge of:
- creating the virtualenv,
- installing the Murano CLI, required for uploading Murano specific requirements,
- generating the zip file including Murano specific requirements,
- uploading the core library, including the specifc requirements into Murano instance.
To execute it, it is required to export admin credentials to access to the Cloud, where Murano is part of.
$ export OS_USERNAME={the admin user name}
$ export OS_PASSWORD={the password for admin user}
$ export OS_TENANT_NAME={the admin tenant name}
$ export OS_REGION_NAME={the region}
$ export OS_AUTH_URL={the auth url for keystone}
Then, just go to folder scripts and execute the script (this script should be executed inside scripts folder): $ cd scripts $ ./upload_fiware_things.sh
To add the new information, wee need to copy it into the murano official meta folder. We assume that {murano_folder} is the folder where Openstack murano has been deployed
$ git clone https://github.com/telefonicaid/fiware-murano {murano_folder}
$ cp -rf /opt/fiware-murano/meta {murano_folder}
Also we need to add the FIWAREMuranoInstance to the manifest core library.
$ echo " io.murano.resources.FiwareMuranoInstance: resources/FiwareMuranoInstance.yaml" >> meta/io.murano/manifest.yaml
We create a zip file
$ cd {murano_folder}/meta/io.murano
$ zip -r ../../io.murano.zip *
$ cd ./../../
Then, we execute the command package-import for the Murano client library (considering we are configuring Murano against FIWARE Lab)
$ tox -e venv -- murano --murano-url http://localhost:8082 --os-username $OS_ADMIN_USERNAME --os-password $OS_PASSWORD \
--os-tenant-name $OS_ADMIN_USERNAME --os-auth-url=$OS_AUTH_URL\
package-import --exists-action u --is-public io.murano.zip
The murano service API is a programmatic interface used for interaction with murano. You can obtain more details about it in the following page OpenStack Murano API.
Murano has a suite of tests that are run on all submitted code, and it is recommended that developers execute the tests themselves to catch regressions early. Developers are also expected to keep the test suite up-to-date with any submitted code changes. See Murano Unit Tests for more details.
All Murano services have tempest-based automated tests, which allow to verify API interfaces and deployment scenarios. See Murano automated tests tempest tests for more details.
- Welcome to Murano Documentation
- Murano workflow
- Container-based deployment
- Development Guidelines
- Contribution guidelines, especially important if you plan to contribute with code to OpenStack Murano.
- Murano TroubleShooting and Debug Tips
Ask your thorough programmming questions using stackoverflow
and your general questions on FIWARE Q&A. In both cases please use the tag fiware-murano
(c) 2015-2016 Telefónica I+D, Apache License 2.0