OpenStack Community App Catalog Review: Issue #2

Welcome to the second edition of the OpenStack Community App Catalog Digest, where we’ll fill you in on what’s going on and how you can contribute.

In the news

Since our last issue, the Community App Catalog group approved two new types of assets. The first, from the January 14 meeting, is Mistral Workflows, which enable you to define very specifically what should happen when, and in response to what. The other, from the January 21 meeting, is TOSCA Service Templates, which are much like Heat templates.  (In fact, the Heat Translator project, which converts them to Heat templates, simply calls them “Templates”.)

Also under discussion has been the issue of whether the cloud-side backed project, Glare (Glance artifacts) would be a separate project under the Big Tent or a part of the Community App Catalog itself.  At issue is the idea that if Glare is part of Glance, it may be in a position of simply proxying or duplicating Glance functionality, and in a limited way, as Glance only works with the command line and web interfaces (as opposed to having a REST interface).  The community expects to make some sort of decision at the next meeting, Thursday, February 4th, 2016 at 17:00 UTC (9am Pacific).

Also on the agenda for Thursday’s meeting:

  • Status updates
  • Resource commitments for Glare/API work (check our first issue to learn more about Glare)
  • Integration with Horizon: Using form parameters may not work in near future
  • Integration with Horizon: How about a stab at integration tests?
  • Open discussion

You can see all of the available agendas at Meetings/app-catalog wiki page. Don’t forget, these meetings are open to anyone in the community; if you want to be involved in some of these decisions, put them in your calendar: the OpenStack Community App Catalog team meets on Thursdays at 1700 UTC in the Freenode IRC channel #openstack-meeting-3.

Further Reading

Dear all, in our first issue we talked about two editorial articles. The first, a comparison of using a Murano App versus using a Glance image to add an application to the Community App Catalog by Ilya Stechkin, Kirill Zaitsev, Dmytro Dovbii, Alexey Deryugin, and Pavel Karpov, has been published and we’d love to hear your comments. We’d also like to know: what’s on your mind?  What do you want to know more about?

Next up is an article about the importance of the Community App Catalog in the Mirantis Unlocked validation process. We’ll explain how to validate your application and why you’d want to add the application to the Community App Catalog. Using the Kubernetes Murano App as an example, we’ll show you how we are moving this app through all steps of the validation process.

Helpful hint: Adding a new app to the Community App Catalog

Interested in adding your app to the Community App Catalog right now? The process is well described on the wiki page, where you can also find information on how to update content that has already been published. For example, you might want to update the hash for a binary asset, or update a link if the URL has changed.

One more thing…

Is your app already published in the Community App Catalog? Feel free to send Ilya the news about this glorious event, and we’ll be happy to celebrate you in our next monthly Community App Catalog Review.  

Have a great month. We’ll see you in March!

Latest Tweets

Suggested Content

WEBINAR
Edge Computing: A Unified Infrastructure for All the Different Pieces