[openstack-dev] [Murano] Kilo-1 Dev Milestone Released!

Serg Melikyan smelikyan at mirantis.com
Thu Dec 18 21:13:45 UTC 2014


I forgot to mention that we also released handful of well-tested Murano
application, that can be used both as example and as ready applications for
your cloud. Application are available in our new repository:
https://github.com/stackforge/murano-apps

We released following applications in this milestone:

   - WordPress
   - Zabbix Monitoring
   - Apache HttpServer
   - Apache Tomcat
   - MySql
   - PostgreSql


On Thu, Dec 18, 2014 at 12:56 PM, Serg Melikyan <smelikyan at mirantis.com>
wrote:
>
> Hi folks,
>
> I am happy to announce that first Kilo milestone is now available. You can
> download the kilo-1 release and review the changes here:
> https://launchpad.net/murano/kilo/kilo-1
>
> With this milestone we release several new and important features, that I
> would like to kindly ask to try and play with:
>
>    - Handle auth expiration for long-running deployments
>    - Per-class configuration files
>
> We added support for long-running deployments in Murano. Previously
> deployment time was restricted by token expiration time, in case when user
> started deployment close to token expiration time, deployment was failing
> on Heat stack creation.
>
> We've also implemented support for per-class configuration files during
> this milestone. Murano may be easily extended, for example with support for
> different third-party services, like monitoring or firewall. You can find
> demo-example of such extension here:
> https://github.com/sergmelikyan/murano/tree/third-party
>
> In this example we add ZabbixApi class that handles interaction with
> Zabbix monitoring system installed outside of the cloud and exposes API to
> all the applications in the catalog, giving ability to configure monitoring
> for themselves:
> https://github.com/sergmelikyan/murano/blob/third-party/murano/engine/contrib/zabbix.py
>
> Obviously we need to store credentials for Zabbix somewhere, and
> previously it was done in main Murano configuration file. Now each class
> may have own configuration file, with nice ability to automatically fill
> class properties by configuration values.
>
> Unfortunately these features are not yet documented, please refer to
> commit messages and implementation for details. We would be happy for any
> contribution to Murano and especially contribution to our documentation.
>
>   * https://review.openstack.org/134183
>   * https://review.openstack.org/119042
>
> Thank you!
>
> --
> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
> http://mirantis.com | smelikyan at mirantis.com
>
> +7 (495) 640-4904, 0261
> +7 (903) 156-0836
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelikyan at mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141218/3a93005c/attachment.html>


More information about the OpenStack-dev mailing list