RETIRED, further work has moved to Debian project infrastructure
8c91052b47
Methods in MuranoPL now can be marked with Usage attribute to specify whether particular method available for remote call or not. By default usage is Runtime (not available for remote call). Workflow: migrateVm: Usage: Action Arguments: - killExisting: Contract: $.bool() Default: True Change-Id: If3da3c6bf67aa79d522d82abbf3b5378f72e87ae Partially-Implements: blueprint application-actions |
||
---|---|---|
contrib | ||
doc/source | ||
etc | ||
functionaltests | ||
meta | ||
murano | ||
tools | ||
.gitignore | ||
.gitreview | ||
babel.cfg | ||
common.inc | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
setup.sh | ||
test-requirements.txt | ||
tox.ini |
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, which may be used by the cloud users (including the inexperienced ones) to pick-up the needed applications and services and composes the reliable environments out of them in a "push-the-button" manner.
Project Resources
Project status, bugs, and blueprints are tracked on Launchpad:
Developer documentation can be found here:
Additional resources are linked from the project wiki page:
License
Apache License Version 2.0 http://www.apache.org/licenses/LICENSE-2.0