Difference between revisions of "Murano/ReleaseNotes v0.3"

Revision as of 04:43, 25 November 2013

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 [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 (previously it was done via CLI) and many other improvements. Please see the complete list of changes in this release.

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 [[1]]. Please find sources for our 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

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.

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

@@ Line 1: / Line 1: @@
+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 [[https://wiki.openstack.org/wiki/Murano/ApplicationCatalog|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 (previously it was done via CLI) and many other improvements.
 Please see [https://launchpad.net/murano/+milestone/0.3 the complete list of changes] in this release.
-===What's new===
+===What's New===
-====Usage of Quantum====
+====Linux Services====
-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.
+This release of Murano has full-featured support for managing Linux services and as a reference we added two new Linux based services: telnet and Apache Webserver. Please, find in sources all necessary bits needed to build this services: [https://github.com/stackforge/murano-conductor/blob/release-0.3/data/workflows/LinuxTelnet.xml workflow], [https://github.com/stackforge/murano-dashboard/blob/release-0.3/muranodashboard/services/LinuxTelnet.yaml UI definition].
-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====
+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 [[https://wiki.openstack.org/wiki/Murano/UnifiedAgent|specification]]. Please find [https://github.com/stackforge/murano-agent/tree/release-0.3/python-agent sources] for our new Agent implementation.
-In this release we also introduce Linux Agent, with Linux Agent Murano has ability to provision any Linux based service.
+To create own services based on Linux you may be also interested in documentation about [http://murano-docs.github.io/0.3/administrators-guide/content/ch05.html 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 [http://murano-docs.github.io/0.3/administrators-guide/content/ch03.html 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 [https://launchpad.net/murano/1.0/0.3 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 [https://bugs.launchpad.net/murano Launchpad page]
-* Due to current Heat limitation services that involve load-balancer creation (farms) can be deployed only by tenant administrators.
+* Internet Information Services Web Farm & ASP.NET Application Web Farm services does not work in tenants with many networks
-*  Farm services can't be deployed without KeyPair. If KeyPair is not set load balancer won't be created ([https://bugs.launchpad.net/murano/+bug/1216882 link on bug description]). Deploy will stuck and these messages will show up in logs:
+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.
--08-06 09:10:07 - Unable to deploy instance ipkrmhk0vzq4b6 (asp-farm_instance_0) due to Unexpected state
--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.