Jump to: navigation, search

Murano/ReleaseNotes v0.3

< Murano
Revision as of 17:01, 22 November 2013 by Serg Melikyan (talk | contribs)

Please see the complete list of changes in this release.

What's new

Usage of Quantum

Previously we used Nova Network for managing networks for Murano. Not so long ago we introduced new service - MS SQL Cluster. MS SQL Cluster is based on Failover Clustering and AlwaysOn Availability Groups features of Microsoft Windows and Microsoft SQL Server. These features require disabling some anti-spoofing rules in Nova Network to work. So we migrating to Quantum with this release, to use networking features of OpenStack at full. We rewrote our Heat templates to support Quantum, backported some patches to Quantum from Neutron, and patched Heat to work with Quantum correctly.

Linux Agent

In this release we also introduce Linux Agent, with Linux Agent Murano has ability to provision any Linux based service.

Bugs Fixed

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

Known Issues

Actual bug state can be found in Murano Launchpad page

  • Due to current Heat limitation services that involve load-balancer creation (farms) can be deployed only by tenant administrators.
  • Farm services can't be deployed without KeyPair. If KeyPair is not set load balancer won't be created (link on bug description). Deploy will stuck and these messages will show up in logs:
2013-08-06 09:10:07 - Unable to deploy instance ipkrmhk0vzq4b6 (asp-farm_instance_0) due to Unexpected state
2013-08-06 09:10:07 - Unable to create a Server Farm load balancer on unit ipkrmhk0vzq4b6 (asp-farm_instance_0) due to Unexpected state
  • 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:
Unable to deploy instance demo (demo.com_instance_0) due to Unexpected stack state NOT_FOUND
  • Internet Information Services Web Farm & ASP.NET Application Web Farm services does not work in tenants with many networks

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.