Open Stack

To chime in on top of Tom’s note, if we want to schedule a sample app hackathon the weekend before the Summit, we should have some space available in the Vancouver convention center. The Foundation staff would be happy to help support and promote those efforts. 

Chris, what are you thinking in terms of timing and plans leading up to the Summit? Happy to help schedule a call for the group to discuss.

Thanks,
Lauren


> On Mar 15, 2015, at 9:05 PM, Tom Fifield <tom at openstack.org> wrote:
> 
> On 20/02/15 04:49, Chris C. Kemp wrote:
>>>> If there was enough interest, we wanted to propose that we bring folks 
>>>> interested together to collaboratively develop a set of "core 
>>>> requirements" for the application.
>> 
>>> Do you not follow this mailinglist? There are already plans for a OpenStack sample application including a document how to use this sample > application. Please get in contact with Tom Fifield and join this working group to share efforts.
>> 
>> Please have a look at the following threads on this mailinglist, written a few days ago.
>> 
>> http://lists.openstack.org/pipermail/user-committee/2015-February/000344.html
>> 
>> http://lists.openstack.org/pipermail/user-committee/2015-February/000348.html
>> 
>> Christian.
>> 
>> I have spoken to top on several occasions in the past week (before he posted this message, I believe), and we have discussed the need to develop code for tutorials.   What I am proposing may be related to this effort, but I believe has a different audience and scope, which is why we wanted to get a conversation going on the mailing list.    Tom can also comment, but I believe the goal for the tutorials is to create fairly small, simple, self-contained code snippets to illustrate how certain things work.  A sample/demo application is a larger more comprehensive application that demonstrates all of the features of OpenStack simultaneously, in a compelling way.  It will also not be static - it will evolve with OpenStack and demonstrate the value of OpenStack's core capabilities.    I believe that sections of code from this larger sample application could be repurposed in the form of tutorials.    In any case, I believe that Tom's initiative was primarily aimed at creating stra
> ightforwa
> rd and easy to understand documentation and tutorials, and what is being proposed here is largely aimed at demonstrating the full breadth of OpenStack's capabilities in a compelling way that will demonstrate interoperability between OpenStack implementations and the overall capabilities of OpenStack's core capabilities.    I hope this provides some additional context.    I welcome you to join the conversation about how these initiatives are related to each other and can be cross-leveraged.   
>> 
>> Chris
> 
> Hi all,
> 
> Sorry for the delay here!
> 
> Let me try to elaborate based on my understanding (jetlagged, didn't
> sleep well, could be wrong):
> 
> =="First App" Tutorial==
> * Create something that Operators like James Dempsey can give to their
> users to allow them to become effective at building cloud applications
> * primary aim: educate on OpenStack APIs via SDKs, secondarily: educate
> on what it means to develop scalable cloud applications, where possible
> * Uses a simple App as a teaching tool, but the App is not the star -
> it's there to make the tutorial not completely dry/artificial and
> provide a logical thread through the different sections
> * The majority of the OpenStack SDK usage/API interactions are in code
> snippets presented to the user in the tutorial, not embedded in the App
> itself
> * App can even be a black box for the first section
> * Aim is as minimal as possible: just provides first steps for using the
> most common calls
> * Looking at a real "Reference" App (below), this tutorial would be
> prerequisite reading for people who wanted to work on producing it
> * Similar examples: "Writing your first Django Application", "Getting
> Started with RabbitMQ"
> 
> 
> ==Sample/Reference App==
> * Full-blown, comprehensive Application coded up so people can basically
> see how all the APIs are used in practice within an app and copy and
> paste things into their own work
> * Covers every part of OpenStack
> * Covers as many APIs as practical
> * as compelling/"flashy" as possible, so it can be used in speeches, etc
> * Java J2EE "Pet Store" sample application, or the .NET "IBuySpy Portal"
> 
> 
> Overall, I think we need both. In systems administration we can learn a
> lot by reading documentation, but sometimes we just want a collection of
> beautiful sample configuration files to understand context better.
> Applying this thinking to our OpenStack App Dev world - a first app
> tutorial with sections to kick-start the learning in various areas, and
> a sample/reference app that developers can keep picking at whenever they
> feel the need.
> 
> Timewise, the "First App" tutorial will happen within the next few
> weeks. This is good because one of the cool ideas Chris may have
> mentioned was to have a competition to come up with Sample/Reference App
> ideas, and having the ability to train up more app developers on the
> OpenStack SDK basics as they compete would be ideal!
> 
> 
> 
> Regards,
> 
> 
> 
> Tom
> 
> 
> 
> 
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee