Difference between revisions of "Murano/Screencasts"
< Murano
m |
|||
Line 7: | Line 7: | ||
==Plans== | ==Plans== | ||
− | * Murano - Application | + | * Murano - Openstack Application Catalog. Quick introduction. |
+ | * Composing Murano Application Package | ||
* MuranoPL as unified tool for integrating applications | * MuranoPL as unified tool for integrating applications | ||
# Introduction (muranoPL is needed vs heat alone) | # Introduction (muranoPL is needed vs heat alone) | ||
Line 15: | Line 16: | ||
# Macroses | # Macroses | ||
# OOP in MuranoPL | # OOP in MuranoPL | ||
− | * | + | * Murano. Step towards universality: Integration with Heat Template (HOT) format |
− | |||
* Dynamic UI and object model generation | * Dynamic UI and object model generation | ||
* Building Murano Images (+ tell about things that can't be done if the agent is NOT available) | * Building Murano Images (+ tell about things that can't be done if the agent is NOT available) |
Revision as of 15:29, 23 May 2014
Murano Screencasts
- Introduction: common information about Murano with deployment of ASP.NET Web Farm as an example
- Murano v0.2 features: Deployment of MS SQL AlwaysOn with Active Directory
- Murano v0.4: Metadata Repository and Dynamic UI
- Murano Demo: Telnet Server on Fedora Linux
- Murano v0.5: Application Catalog for Openstack
Plans
- Murano - Openstack Application Catalog. Quick introduction.
- Composing Murano Application Package
- MuranoPL as unified tool for integrating applications
- Introduction (muranoPL is needed vs heat alone)
- Hello world (+ information about Resources)
- YAQL-expressions - separate demo
- Contracts
- Macroses
- OOP in MuranoPL
- Murano. Step towards universality: Integration with Heat Template (HOT) format
- Dynamic UI and object model generation
- Building Murano Images (+ tell about things that can't be done if the agent is NOT available)