<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body ocsi="0" fpstyle="1" style="word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font-family:Calibri,sans-serif">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">There's an alternate vision which is simply, resources that can be launched in an OpenStack environment directly.<br>
<br>
Solum, Mistral, Glance, etc fit into that definition. This is kind of how it is arranged today.<br>
<br>
Even with the high level app store only vision I proposed, these other types of catalog entries will probably be needed since the higher level app store's apps will probably depend on them...<br>
<br>
Say I want to create a Cloud Application that as part of it, launches a rather obscure, hard to build database software as the backend of a set of web servers... Having that part of the app be a Glance Image might be the best way to go. So your Cloud App would
depend on maybe a heat template, and a couple of Glance Images (the appliance and a generic Linux one being loaded too).
<br>
<br>
I know the glance folks want to support storing these things as part of their artefact api, which is good, but there still is the discovery part of it that the app catalog can provide...<br>
<br>
So, maybe we really need two different types of things in the catalog.<br>
* Applications (thing that a user will launch, and optionally answer a few questions)<br>
* Resources (OpenStack resources. Glance, Heat, Solum, Mistral, etc Artefacts that Applications use, or users can manually use directly if they have the know how.)<br>
<br>
Then when the application catalog users that are not developers go to the ui, it would only present the first category of things.<br>
<br>
Thanks,<br>
Kevin<br>
<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF872303"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Keith Bray [keith.bray@RACKSPACE.COM]<br>
<b>Sent:</b> Wednesday, May 27, 2015 4:48 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [new][app-catalog] App Catalog next steps<br>
</font><br>
</div>
<div></div>
<div>
<div>Kevin, I like your vision. Today we have images, heat templates, Murano packages. What are your thoughts on how to manage additions? Should it be restricted to things in the OpenStack namespace under the big tent? E.g., I'd like to see Solum language
packs get added to the app-catalog. Solum is currently in stack forge, but meets all the criteria I believe to enter OpenStack namespace. We plan to propose it soon. Folks from various companies did a lot of work the past few summits to clearly distinguish,
Heat, Murano, Mistral, and Solum as differentiated enough to co-exist and add value to the ecosystem.</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><Fox>, Kevin M <<a href="mailto:Kevin.Fox@pnnl.gov" target="_blank">Kevin.Fox@pnnl.gov</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" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, May 27, 2015 6:27 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" target="_blank">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 dir="ltr"><style id="owaParaStyle" type="text/css">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
BODY {direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;}P {margin-top:0;margin-bottom:0;}BODY {scrollbar-base-color:undefined;scrollbar-highlight-color:undefined;scrollbar-darkshadow-color:undefined;scrollbar-track-color:undefined;scrollbar-arrow-color:undefined}BODY {scrollbar-base-color:undefined;scrollbar-highlight-color:undefined;scrollbar-darkshadow-color:undefined;scrollbar-track-color:undefined;scrollbar-arrow-color:undefined}BODY {scrollbar-base-color:undefined;scrollbar-highlight-color:undefined;scrollbar-darkshadow-color:undefined;scrollbar-track-color:undefined;scrollbar-arrow-color:undefined}</style>
<div>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt">I'd say, tools that utilize OpenStack, like the knife openstack plugin, are not something that you would probably go to the catalog to find. And also, the recipes that you would use
with knife would not be specific to OpenStack in any way, so you would just be duplicating the config management system's own catalog in the OpenStack catalog, which would be error prone. Duplicating all the chef recipes, and docker containers, puppet stuff,
and ..... is a lot of work...<br>
<br>
The vision I have for the Catalog (I can be totally wrong here, lets please discuss) is a place where users (non computer scientists) can visit after logging into their Cloud, pick some app of interest, hit launch, and optionally fill out a form. They then
have a running piece of software, provided by the greater OpenStack Community, that they can interact with, and their Cloud can bill them for. Think of it as the Apple App Store for OpenStack. Having a reliable set of deployment engines (Murano, Heat, whatever)
involved is critical to the experience I think. Having too many of them though will mean it will be rare to have a cloud that has all of them, restricting the utility of the catalog. Too much choice here may actually be a detriment.<br>
<br>
If chef, or what ever other configuration management system became multitenant aware, and integrated into OpenStack and provided by the Cloud providers, then maybe it would fit into the app store vision?<br>
<br>
Thanks,<br>
Kevin
<div style="font-family:Times New Roman; color:#000000; font-size:16px">
<hr tabindex="-1">
<div id="divRpF167114" style="direction:ltr"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Joe Gordon [<a href="mailto:joe.gordon0@gmail.com" target="_blank">joe.gordon0@gmail.com</a>]<br>
<b>Sent:</b> Wednesday, May 27, 2015 3:20 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [new][app-catalog] App Catalog next steps<br>
</font><br>
</div>
<div></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>
</div>
</div>
</div>
</blockquote>
</span></div>
</div>
</div>
</body>
</html>