Mission

The OpenStack Community App Catalog will help you make applications available on your OpenStack cloud by providing a community driven catalog containing Glance images, Heat templates and Murano applications.

By providing a public location where OpenStack users can publish and consume artifacts to share and add additional capabilities, all OpenStack clouds become more valuable. For example vendors can publish Glance images for launching new VMs, Heat templates for creating new stacks, or Murano app packages for installing complete applications. When many OpenStack community members are publishing artifacts that users can easily download and install into their clouds this will multiply the value of their OpenStack cloud. Easy access to images, templates and apps will solve the “what now” question some user consider after successfully deploying an OpenStack environment.

FAQ

Q: What is the Community App Catalog?
The Community App Catalog is a collection of ready-to-use applications, Heat templates and machine images that you can immediately deploy into your OpenStack cloud. With the catalog (now in beta), there’s no need to go and collect parts of the applications and services you wish to deploy, work out their detailed infrastructure settings, or create scripts to handle their dependencies. To deploy a Murano app, for example, simply browse and select the one you need and copy the name into Murano in your OpenStack environment. Then click through a handful of parameters and your application is deployed

Q: What can I find in it?

The catalog features useful applications and components to use on your OpenStack Cloud, pre-configured with the necessary settings to deploy and run them

Q: How much does it cost?
There’s no charge to put anything in or get anything out of the App Catalog. Catalog items include both free and licensed software, and some may require payment or specific license terms. You’ll see that in each particular package.

You can now deploy the app into your cloud using Horizon or the Murano client

How to contribute

The OpenStack Community App Catalog is designed to use the same tools for submission and review as other OpenStack projects. As such we follow the OpenStack development workflow. New contributors should follow the getting started steps before proceeding, as a Launchpad ID and signed contributor license are required to add new entries.

Adding content

Edit the YAML file pertaining to the type of entry you are adding (see below for structure examples). The YAML files are validated against the YAML schema files which are located in the same folder as the YAML files. The Stackforge gate checks the file for compliance with the schema, so be sure additions match the appropriate schema.

Glance entries are found in openstack_catalog/web/static/glance_images.yaml

Heat entries are found in openstack_catalog/web/static/heat_templates.yaml

Murano entries are found in openstack_catalog/web/static/murano_apps.yaml

When submitting the entry for review, the commit message must include the catalog entry name, URL to retrieve the asset, and an md5 sum if it is a binary.

For example if you wanted to add a Murano package called "MyLAMPStack.zip", the commit message must show where to retrieve that asset along with the SHA or md5 hash:

url: http://<your-hostname>/MyLAMPStack.zip

hash: 7237de38ebf827e234ca643b725779e4f38f0ef0

Glance image URLs and hashes must be similarly included in the commit message, as in the following example:

Image-URL: http://<your-hostname>/images/ubuntu-14.04-m-agent.qcow2

Image-hash: cbd9ded8587b98d144d9cf0faea991a9

Structure of Glance entry

Glance entries are validated against the file openstack_catalog/web/static/glance_images.schema.yaml found in the apps-catalog repository and for example is formatted like this:

'attributes' section can contain any elements. There is no predefined structure for 'attributes' and the only requirements for them is to be YAML valid entries. So in the example above it will be pretty safe to change 'url' to 'Image URL' and UI will still render this properly as a link. Pease, feel free to add documentation links if there is a any documentation for the image.

Structure of Heat entry

Heat entries are validated against the file openstack_catalog/web/static/heat_templates.schema.yaml found in the apps-catalog repository and for example is formatted like this: