<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Joe, regarding apps-catalog for any app deployable on OpenStack (regardless of deployment technology), my two cents is that is a good idea. I also believe, however, that the app-catalog needs to evolve first with features that make it super simple to
understand which artifacts will work on which clouds (out-of-the-box) vs. needing additional required dependencies or cloud operator software. My guess is there will be a lot of discussions related to defcore, and/or tagging artifacts with known public/private
cloud distributions the artifacts are known to work on. To the extent an openstack operator or end user has to download/install 3rd party or stack forge or non defcore openstack components in order to deploy an artifact, the more sophisticated and complicated
it becomes and we need a way to depict that for items shown in the catalog.</div>
<div><br>
</div>
<div>For example, I'd like to see a way to tag items in the catalog as known-to-work on HP or Rackspace public cloud, or known to work on RDO. Even a basic Heat template optimized for one cloud won't necessarily work on another cloud without modification.
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>-Keith</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Joe Gordon <<a href="mailto:joe.gordon0@gmail.com">joe.gordon0@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, May 27, 2015 5:20 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [new][app-catalog] App Catalog next steps<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, May 22, 2015 at 9:06 PM, Christopher Aedo <span dir="ltr">
<<a href="mailto:caedo@mirantis.com" target="_blank">caedo@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I want to start off by thanking everyone who joined us at the first<br>
working session in Vancouver, and those folks who have already started<br>
adding content to the app catalog. I was happy to see the enthusiasm<br>
and excitement, and am looking forward to working with all of you to<br>
build this into something that has a major impact on OpenStack<br>
adoption by making it easier for our end users to find and share the<br>
assets that run on our clouds.<br>
</blockquote>
<div><br>
</div>
<div>Great job. This is very exciting to see, I have been wanting something like this for some time now.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
The catalog: <a href="http://apps.openstack.org" target="_blank">http://apps.openstack.org</a><br>
The repo: <a href="https://github.com/stackforge/apps-catalog" target="_blank">https://github.com/stackforge/apps-catalog</a><br>
The wiki: <a href="https://wiki.openstack.org/wiki/App-Catalog" target="_blank">https://wiki.openstack.org/wiki/App-Catalog</a><br>
<br>
Please join us via IRC at #openstack-app-catalog on freenode.<br>
<br>
Our initial core team is Christopher Aedo, Tom Fifield, Kevin Fox,<br>
Serg Melikyan.<br>
<br>
I’ve started a doodle poll to vote on the initial IRC meeting<br>
schedule, if you’re interested in helping improve and build up this<br>
catalog please vote for the day/time that works best and get involved!<br>
<a href="http://doodle.com/vf3husyn4bdkui8w" target="_blank">http://doodle.com/vf3husyn4bdkui8w</a><br>
<br>
At the summit we managed to get one planning session together. We<br>
captured that on etherpad[1], but I’d like to highlight here a few of<br>
the things we talked about working on together in the near term:<br>
<br>
-More information around asset dependencies (like clarifying<br>
requirements for Heat templates or Glance images for instance),<br>
potentially just by providing better guidance in what should be in the<br>
description and attributes sections.<br>
-With respect to the assets that are listed in the catalog, there’s a<br>
need to account for tagging, rating/scoring, and a way to have<br>
comments or a forum for each asset so potential users can interact<br>
outside of the gerrit review system.<br>
-Supporting more resource types (Sahara, Trove, Tosca, others)<br>
</blockquote>
<div><br>
</div>
<div>What about expanding the scope of the application catalog to any application that can run *on* OpenStack, versus the implied scope of applications that can be deployed *by* (heat, murano, etc.) OpenStack and *on* OpenStack services (nova, cinder etc.).
This would mean adding room for Ansible roles that provision openstack resources [0]. And more generally it would reinforce the point that there is no 'blessed' method of deploying applications on OpenStack, you can use tools developed specifically for OpenStack
or tools developed elsewhere.</div>
<div><br>
</div>
<div><br>
</div>
<div>[0] <a href="https://github.com/ansible/ansible-modules-core/blob/1f99382dfb395c1b993b2812122761371da1bad6/cloud/openstack/os_server.py" target="_blank">https://github.com/ansible/ansible-modules-core/blob/1f99382dfb395c1b993b2812122761371da1bad6/cloud/openstack/os_server.py</a></div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
-Discuss using glance artifact repository as the backend rather than<br>
flat YAML files<br>
-REST API, enable searching/sorting, this would ease native<br>
integration with other projects<br>
-Federated catalog support (top level catalog including contents from<br>
sub-catalogs)<br>
- I’ll be working with the OpenStack infra team to get the server and<br>
CI set up in their environment (though that work will not impact the<br>
catalog as it stands today).<br>
</blockquote>
<div><br>
</div>
<div>I am pleased to see moving this to OpenStack Infra is a high priority.</div>
<div><br>
</div>
<div>A quick nslookup of <a href="http://apps.openstack.org" target="_blank">http://apps.openstack.org</a> shows it us currently hosted on linode at <a href="http://nb-23-239-6-45.fremont.nodebalancer.linode.com/" target="_blank">http://nb-23-239-6-45.fremont.nodebalancer.linode.com/</a>.
And last I checked linode isn't OpenStack powered. <a href="http://apps.openstack.org" target="_blank">apps.openstack.org</a> is a great example of the type of application that should be easy to deploy with OpenStack, since as far as I can tell it just needs
a web server and that is it. So wearing my OpenStack developer hat on, why did you go with linode and not any one of the OpenStack based public clouds [1]? If OpenStack is not a good solution for workloads like this, then it would be great to know how what
needs work.</div>
<div> </div>
<div><br>
</div>
<div>[1] <a href="https://www.openstack.org/marketplace/public-clouds/" target="_blank">https://www.openstack.org/marketplace/public-clouds/</a></div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
There were a ton of great ideas that came up and it was clear there<br>
was WAY more to discuss than we could accomplish in one short session<br>
at the summit. I’m looking forward to continuing the conversation<br>
here on the mailing list, on IRC, and in Tokyo as well!<br>
<br>
[1] <a href="https://etherpad.openstack.org/p/YVR-app-catalog-plans" target="_blank">
https://etherpad.openstack.org/p/YVR-app-catalog-plans</a><br>
<br>
-Christopher<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>