Murano/ReleaseNotes v0.3

This version of Murano contains several features and improvement, where ability to manage Linux instances is major one. Murano was always capable to manage instances with any Operation System, but only now, after first moves towards our new mission we added full-featured support for managing Linux instances. This release also introduce direct support for Quantum, ability to mark images uploaded to Glance with Murano specific metadata and many other improvements. Please see the complete list of changes in this release.

Linux Services
This release of Murano has full-featured support for managing Linux services, as a reference two new Linux based services was added: telnet and Apache Webserver. Please, find in sources all necessary bits was needed to build this services: workflow, UI definition.

Murano Agent was built specially for Windows using .NET Framework as a platform and PowerShell as execution engine. To support configuration management on GNU/Linux was required to rewrite Agent on Python. We re-designed, extended and improved ideas that we had before, and only after that we rewrote Agent using Python. Now Murano can work with any implementation of a agent as long as it is complies to the new [|specification]. Please find sources for the new Agent implementation.

To create own services based on Linux you may be also interested in documentation about how to build image with GNU/Linux.

Leveraging Quantum
Previous releases of Murano was designed and tested against nova-network and even if it could be run over Quantum there was no difference in behavior from users point-of-view. All instances created by Murano was running in the same network as instances created directly from nova. Or, in case of Quantum simply in the default tenant network.

In this release limited support for Quantum is added. Each environment created in own network and separated from others on L2 level. This feature adding additional security and separation between services running in environments. Limited support means that user has not direct control over networks that managed by Murano, but in next versions, targeting Openstack Havana with Neutron, we have plans to add ability to manage networks in Murano by the user.

This feature is not enabled by default, please find how to enable support for Quantum.

Marking Images
In this release we introducing new UI for marking images with Murano specific metadata, previously this was done only via CLI.

Marking images is required for close integration between services capabilities and base-image that should support this capabilities. At first this feature was used only to identify images with Murano Agent baked in. Currently this feature is used for separation supported images by Operation System. For example, for windows services, only windows images can be chosen.

This feature is a base for support of fine-grained, hierarchical filters in in workflows for selecting base image for the application.

Bugs Fixed
A complete list of bugs fixed in Murano v0.3 can be found here.


 * User could not create two * Farms services in one environment
 * User is unable to deploy MS SQL Cluster
 * Need to add 'python-MySQLdb' in requirements list for Murano API service

Improvements
In this release was added many improvements related to work with SSL. Murano now can use SSL to secure communication on all levels.

Known Issues
Actual bug state can be found in Murano Launchpad page

This services are based on Heat, particularly on resource called AWS::ElasticLoadBalancing::LoadBalancer, that currently does not support specification of any network related params. Without support for network specification LoadBalancer does not work on OpenStack deployments with Quantum deployment schemes that allow multiple networks inside tenant.
 * Internet Information Services Web Farm & ASP.NET Application Web Farm services does not work in tenants with many networks

Unable to deploy instance demo (demo.com_instance_0) due to Unexpected stack state NOT_FOUND
 * User can select incorrect parameters for service, like incompatible flavor and VM image or if tenant resource quota exceeded. In this case user will see the following error in the log: