[User-committee] User-committee Digest, Vol 25, Issue 8

Chris C. Kemp chris.c.kemp at nebula.com
Tue Mar 3 20:55:13 UTC 2015


Sean, Tom, Bill, Karl, Christian,

Thanks for your feedback.  It sounds like there is some interest in this topic from the mailing list.  There are a lot of folks that Bill and I have socialized this idea with that are interested in a live conversation on this topic... most of these folks are not on this mailing list yet.   

Tom - would it be possible for us to work together host a phone call for folks that are interested in discussing this topic live?  Bill and I are happy to lead the call.  

Best,   
Chris

-----Original Message-----
From: user-committee-request at lists.openstack.org [mailto:user-committee-request at lists.openstack.org] 
Sent: Saturday, February 21, 2015 4:00 AM
To: user-committee at lists.openstack.org
Subject: User-committee Digest, Vol 25, Issue 8

Send User-committee mailing list submissions to
	user-committee at lists.openstack.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
or, via email, send a message with subject or body 'help' to
	user-committee-request at lists.openstack.org

You can reach the person managing the list at
	user-committee-owner at lists.openstack.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of User-committee digest..."


Today's Topics:

   1. Re: OpenStack Sample Application (Amrhein, Karl)
   2. Re: OpenStack Sample Application (Sean Dague)


----------------------------------------------------------------------

Message: 1
Date: Fri, 20 Feb 2015 15:55:46 +0000
From: "Amrhein, Karl" <ksa at slac.stanford.edu>
To: "user-committee at lists.openstack.org"
	<user-committee at lists.openstack.org>
Subject: Re: [User-committee] OpenStack Sample Application
Message-ID: <EBBD6BE2-8AC7-4E48-A495-66D05C5ECC15 at slac.stanford.edu>
Content-Type: text/plain; charset="us-ascii"


> ... 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 think this would be a very worthwhile investment, and it would help with adoption of OpenStack by a user community who might be used to using a more traditional computing environment.  
 
And I can see how this would be useful for the science community; it could demonstrate how to rewrite some traditional workflows in a way to take advantage of the more mature capabilities of OpenStack.   

Also, sysadmins could use it to verify or benchmark different vendor OpenStack offerings. 
 
Karl Amrhein
SLAC National Accelerator Laboratory


------------------------------

Message: 2
Date: Fri, 20 Feb 2015 12:03:45 -0500
From: Sean Dague <sean at dague.net>
To: user-committee at lists.openstack.org
Subject: Re: [User-committee] OpenStack Sample Application
Message-ID: <54E768F1.2030909 at dague.net>
Content-Type: text/plain; charset=utf-8

On 02/18/2015 05:09 PM, Chris C. Kemp wrote:
> Hi everyone,
> 
>  
> 
> I've been thinking more about the conversation many of us had at the 
> Paris Summit around the best way to help advance the Application 
> Ecosystem working Group, and in particular the idea of a standard 
> OpenStack "Sample Application.?
> 
>  
> 
> Many of you are aware of the Java J2EE "Pet Store" sample application,
> or the .NET "IBuySpy Portal" sample application.   These applications
> were used to demonstrate the core capabilities of these platforms, and 
> served to illustrate the typical design decisions and tradeoffs 
> developers make when building applications for these platforms.
>   Running an application on OpenStack presents a number of 
> opportunities and challenges to those that may be otherwise familiar 
> with running applications on traditional virtualized infrastructure, 
> or are accustomed to some of the features in various public cloud platforms.
> 
>  
> 
> I, as well as Bill Franklin, have been socializing this idea with some 
> of our peers here in Silicon Valley, and there seems to be a lot of 
> interest in the idea of developing a sample application for OpenStack.
> The application could be itself an OpenStack project, and could have a 
> set of community defined requirements such as "must use OpenStack core 
> capabilities" and could be used to demonstrate portability between 
> different OpenStack implementations.  Furthermore, just as code from 
> PetStore found itself into thousands of applications, this application 
> could serve as a fantastic starting point for developers that are 
> building next generation applications targeting the OpenStack platform.
> 
>  
> 
> 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.  We could then perhaps work with 
> the Foundation to crowdsource a "concept" for the application (It's 
> 2015, I think the OpenStack Community can do better than a Pet Store, 
> or a Spy Shop, right?).  We could, with sufficient interest and 
> sponsorship, have a hackathon around the Vancouver Summit to build the 
> first prototype.  I know there are a few folks from Nebula, HP and other companies that
> would love to chip in.   Please let me know what you think here on the
> mailing list, and if there is enough interest we can schedule an 
> online discussion to discuss further.

Given that the existing OpenStack Infra effort runs across 2 OpenStack Clouds, it might be interesting to see if there are either lessons learned, or a subset that could be used at the example application. The application being a Development Pipeline (given that dev/test is one of the workloads that often comes up).

The upside being that it already exists, does a set of what you want, and any improvements to the effort to use OpenStack better would also be a virtuous cycle to the OpenStack development effort.

The downside is that it already exists, so there is a lot of legacy and bits to understand. And it's organically grown in place, so may not have the crispness expected for this effort.

So I don't want to suggest it's a slam dunk by any means, and at the end of the day might not be a reasonable fit, but it seems like data that should be on the table some where shaping what the final sample application looks like.

	-Sean

--
Sean Dague
http://dague.net



------------------------------

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


End of User-committee Digest, Vol 25, Issue 8
*********************************************



More information about the User-committee mailing list