fc586b949d
Murano environment deployment started with empty stack creation so that it can be done prior to keystone token expiration for Heat to establish trusts based on user's token. When environment does nothing with the stack (for example all environment applications are HOT based and deploy into their own stacks) empty stack remains. Because most applications start their deployment with instance/other resources deployment stack will be created early anyway. So this strategy is redundant. Change-Id: Id8ec1df2c83f540b272ef70bd054f70de9da7715 Closes-Bug: #1473129 |
||
|---|---|---|
| contrib | ||
| devstack | ||
| doc/source | ||
| etc | ||
| functionaltests | ||
| meta | ||
| murano | ||
| rally-jobs | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| babel.cfg | ||
| openstack-common.conf | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Murano
Murano Project introduces an application catalog, which allows application developers and cloud administrators to publish various cloud-ready applications in a browsable categorised catalog. Cloud users -- including inexperienced ones -- can then use the catalog to compose reliable application environments with the push of a button.
Project Resources
- Murano Official Documentation
- Project status, bugs, and blueprints are tracked on Launchpad
- Additional resources are linked from the project Wiki page
- Python client
License
Apache License Version 2.0 http://www.apache.org/licenses/LICENSE-2.0