Open Stack

This can be re-distributed as 'portable app' as long as the underlying clouds are 'compatible'.

-----Original Message-----
From: Christopher Aedo [mailto:doc at aedo.net] 
Sent: Monday, April 11, 2016 8:06 AM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>; user-committee <user-committee at lists.openstack.org>
Subject: Re: [User-committee] [all] [app-catalog] Newton summit schedule

On Sat, Apr 9, 2016 at 8:41 AM, Yih Leong, Sun. <yihleong at gmail.com> wrote:
> I think it needs to relate to 'workload'.
> The Enterprise WG is working on a series of workload reference architecture.
> These architecture documents will include sample Heat template for 
> each type of workload. We can work together and include Murano if resources permitted.
> These will be published in conjunction with the OpenStack Sample Config.
> http://www.openstack.org/software/sample-configs/

I like the of focusing on workloads and associating them with the right reference architecture to support them.  That however seems like the intended application(s) would be very closely tied to the configuration of the cloud itself.  That scenario does not lend itself to re-distributing an application for use by other users (i.e. a portable app that can be used by multiple different clouds).  Unless I'm misunderstanding?

You mention Murano here as well - why?  Hopefully you have not conflated the Community App Catalog with Murano :)  They're different animals entirely!

-Christopher


>
> On Friday, April 8, 2016, Christopher Aedo <doc at aedo.net> wrote:
>>
>> Hello!  I'm tagging "all" in hopes of getting more attention and some 
>> good attendance and conversations going in Austin.  The sessions are 
>> on the schedule[1] so please join us!
>>
>> In addition to the time we hope to spend with the Horizon team, we'll 
>> also talk about what I think is one of the biggest things holding 
>> back growth of the catalog - the question of how to develop an app 
>> meant for OpenStack (and how best to package and distribute them).  
>> This impacts the larger OpenStack ecosystem as well, and I'm hoping 
>> to solicit more opinions and views either in person or via the 
>> mailing list[2].
>>
>> Looking forward to some great conversations in Austin!
>>
>> [1]
>> https://www.openstack.org/summit/austin-2016/summit-schedule/global-s
>> earch?t=App%20Catalog
>> [2]
>> http://lists.openstack.org/pipermail/user-committee/2016-April/000722
>> .html
>>
>> -Christopher
>>
>> _______________________________________________
>> User-committee mailing list
>> User-committee at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee

_______________________________________________
User-committee mailing list
User-committee at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee