<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>Ah. So maybe rather then filter out, gray out?<br>
<br>
Thanks,<br>
Kevin <strong>
<div><font face="Tahoma" color="#000000" size="2"> </font></div>
</strong>
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> Jeremy Stanley<br>
<b>Sent:</b> Wednesday, May 27, 2015 5:31:51 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>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On 2015-05-28 00:20:48 +0000 (+0000), Keith Bray wrote:<br>
> Maybe. I'm not up to speed on defcore/refstack requirements.. But,<br>
> to put the question on the table, do folks want the OpenStack<br>
> App-catalog to only have support for the<br>
> "lowest-common-denominator" of artifacts and cloud capabilities,<br>
> or instead allow for showcasing all that is possible when using<br>
> cloud technology that major vendors have adopted but are not yet<br>
> part of refstack/defcore?<br>
<br>
I sort of like the idea that the App Catalog can steer service<br>
providers and solutions deployers to support more official OpenStack<br>
services. Say I run ProviderX and haven't yet implemented/exposed<br>
Heat to my customers. Now someone adds KillerAppY to<br>
apps.openstack.org as a Heat template. It's entirely likely that<br>
more customers may try to convince me to add Heat support (or will<br>
start leaving for other providers who do). That's market pressure<br>
driving companies toward better support for OpenStack, with a lot<br>
more carrot than stick.<br>
-- <br>
Jeremy Stanley<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</span></font>
</body>
</html>