Mitaka Series Release Notes


Bug Fixes

  • Core Library’s init scripts used to have various problems detecting pre-installed (by DIB) murano-agent on non-ubuntu images. Agent setup script now checks wider list of directories before attempting to install murano-agnet and service script now does not impose strict script location.

  • Murano engine no longer logs methods string(), json(), and yaml() of the ‘io.murano.system.Resources’ class. This is done to prevent UnicodeDecodeError’s when transferring binary files to murano agent.


Bug Fixes

  • Murano is now able to deploy applications in the environments with disabled Neutron Security Groups. Detection is based on the presence of ‘security-group’ Neutron extension.


Security Issues

  • cve-2016-4972 has been addressed. In ceveral places Murano used loaders inherited directly from yaml.Loader when parsing MuranoPL and UI files from packages. This is unsafe, because this loader is capable of creating custom python objects from specifically constructed yaml files. With this change all yaml loading operations are done using safe loaders instead.

Bug Fixes

  • Fixed a bug when the UI dialog was not displayed in Murano Dashboard for applications which don’t have UI definitions bundled in the package but generate them based on the package contents instead. This usually affected HOT-based packages and other non-muranopl-based applications.


New Features

  • Now all native MuranoPL methods (those that are written in Python) have “?muranoMethod” metadata key referring to MuranoMethod instance for the method.

  • Classes to work with Cinder volumes were added to core library. Now it is possible to create new volume from various sources or use existing volume. Also it is possible to attach volumes to instances and boot instances from volumes.

  • Class configs are now also versioned. For class version 1.2.3 the following file names will be examined: In addition for classes of version 0.x.y file name without version suffix are also examined as a last attempt so the backward compatibility is retained

  • New plugin ‘murano_heat-translator_plugin’ was added. Now it is possible to deploy applications from CSAR templates.

  • Enable mocks in MuranoPL tests cases.

  • Added murano-test-tunner command to run murano package tests.

  • Introduced two YAQL inject functions to enable mocks def inject(target, target_method, mock_object, mock_name) and def inject(target, target_method, yaql_expr).

  • New method type: extension methods. Extension methods enable you to “add” methods to existing types without modifying the original type. Extension methods are a special kind of static method, but they are called as if they were instance methods on the extended type. Extension methods are identified by “Usage: Extension” and the type they extend is determined by their first argument contract. Thus such methods must have at lease one parameter.

  • New type-level keyword “Import” which can be either list or scalar that specifies type names which extensions methods should be imported into class context and thus become available to type members.

  • Added filter by ‘Name’ which only matches package name.

  • All HOT template outputs are put into a single dictionary property ‘templateOutputs’ rather than in a generated property per each output. As a result there are no more constraints on output names.

  • Added magnum plugin to murano, that allows creating/deleting of magnum baymodels and bays from MuranoPL

  • Added ability to extend MuranoPL entities with custom metadata.

  • For MuranoPL classes new key “Usage” was added. By default it is “Class”. But it can also be “Meta” to define meta-class. Meta-class has all the capabilities of regular classes and in addition has 3 new attributes: Cardinality, Applies and Inherited.

  • It is possible to attach meta-class instances to packages, classes (including other meta-classes), properties, methods and method arguments. Each of them got new “Meta” key containing list (or single scalar) of meta-class instances.

  • Now it is possible to have several classes in one YAML file. Classes are separated using YAML document separator (3 dashes). Empty documents are skipped. If the class doesn’t have Namespace section corresponding section from the previous class in the same file is used. Thus it is possible to declare namespace prefixes once at the file header. Even if there are several classes in one file all of them are still required to be declared in manifest file.

  • Add multiple engine workers

  • New operator is was added to MuranoPL. Now it is possible to test if MuranoPL object is of particular type.

  • Murano engine is now capable of caching packages on disk for reuse. This is controlled by packages_cache directory path and enable_packages_cache boolean parameter (true by default). The packages are cached in a eventlet/inter-process safe manner and are cleaned up as soon as newer version of the package becomes available (unless it’s used by ongoing deployment)

  • Added public field to environment templates. GET method for api now displays public templates from other projects(tenants).

  • Added public filter to environment templates api.

  • Added clone action to environment templates.

  • Basic reflection capabilities were added to MuranoPL. Now it is possible to get type info with typeinfo() function and using it as a starting point obtain information about the class, its methods and properties as well as the package of the class. Reflected properties can be used to obtain or set its value in a given object or invoke its method.

  • Static methods and properties were introduced. Both properties and methods can be marked as Usage: Static Statics can be accessed using / ns:Class.method(), / :Class.method() to access class from current namespace or type(‘’).property / type(‘’).method() to use full type name.

  • io.murano.configuration.Linux methods are now static

  • Heat stacks created by murano during environment deployment now have ‘murano’ tag by default. This is controlled by stack_tags config parameter.

  • Murano was migrated to yaql 1.1

  • New format MuranoPL/1.3 can be specified in manifest files. MuranoPL/1.3 is identical to MuranoPL/1.2 but except for the fact that MuranoPL/1.3 packages cannot be imported to earlier Murano versions. Thus applications that use new features of yaql 1.1 should use this format version.

Known Issues

  • Enabling multiple workers might break workflows under BSD and Windows systems

Upgrade Notes

  • When updating to Mitaka, the operator should update service name and type for endpoint in keystone from “application_catalog” to “application-catalog” if SQL is used for catalog back-end driver.

Bug Fixes

  • Murano is now able to work with keystone configured to use a templated catalog.

  • It was impossible to explicitly provide attribute owner class to getAttr/setAttr methods without using namespace prefix or if the type was not from the core library.

  • Murano is now able to assign correct floating IPs when using multiple external networks. It attempts to choose one that shares a router with internal network.

  • Avoid race condition during parallel upload of packages, when packages have same tags.

  • Fixed incorrect murano behaviour if deployed on devstack with keystone v3 by default.

  • RequestContext now serialises it’s roles. This should allow murano to work correctly (and allow rules like “role:xxx” in policy.json) when using oslo.context prior to 2.2.0 and oslo.policy