Open Stack

        Hello to the list - I am the product manager at SUSE for our
        OpenStack distribution. I'm not able to make the face-to-face
        next week, but here is my feedback based on our customers'
        input:
        
        #1 is the most critical impediment to production deploy. We had
        already identified this as part of the initial WTE work last
        year. 
        
        #2 is really up to the ISV to declare support for their
        application running on OpenStack and is ultimately a statement
        about the underlying hypervisor/OS of the compute node.
        
        #3 has not come up outside of making sure the network
        definitions are correct
        
        #4 (even if Arkady did not number it) also comes up frequently.
        While most enterprises would agree that applications *should* be
        written for the cloud, they don't necessarily want to run two
        different environments, (one for the old stuff and one for the
        new), nor do they want to re-write all of their existing apps.
        
Pete


On Tue, 2015-01-20 at 11:12 -0600, Arkady_Kanevsky at DELL.com wrote:
> Great discussion.
> I had attended Enterprise WG meeting at Kilo meeting.
> While some of discussions were outside the scope of what OpenStack can do several actually do.
> 
> Here is the list I had compiled:
> 1. Support for upgrade and update. (nova made the most strides on that. And some of the code was moved to Oslo and is used by others. Cinder and Heat are starting to use it for their upgrade. But till all "core" projects support non-disruptive upgrade the whole openstack solution cannot be upgrade either. There are tons of caveat, including HA, live migration to make it truly upgradable. For updates, if we maintain some discipline, like not update DB schema, we should be close.) Need in depth dive into it.
> 
> 2. Applications certified to work on OpenStack. This is outside of OpenStack code base or any current work. 
> 
> 3. Solution validator as part of OpenStack code base. We have Tempest, Grenade and Rally as OpenStack code base. But they are mostly targeted for internal CI and not as released component.
> 
> There is always whining and complaining that OpenStack does not take into account Enterprise application requirements into account. Mostly about resiliency, and performance guarantees. And we can do some work on that also.
> 
> Let's pick a couple we can make impact on instead of boiling the ocean.
> 
> 
> See you all  next week.
> Arkady
> 
> Arkady Kanevsky, Ph.D.
> Director of SW development
> Dell ESG
> Dell Inc. One Dell Way, MS PS2-47
> Round Rock, TX 78682, USA
> Phone: 512 723 5264
> 
>  
> 
> -----Original Message-----
> From: Andreas Jaeger [mailto:aj at suse.com] 
> Sent: Tuesday, January 20, 2015 2:54 AM
> To: product-wg at lists.openstack.org
> Subject: Re: [Product] Reference Architectures
> 
> On 01/19/2015 09:51 PM, Shamail wrote:
> > Hi Rocky,
> > 
> > I changed the topic to separate the voting from the RA topic that you mentioned.  I think it's a good idea but I would be glad to share a "user reference architecture" initiative that the WTE (Win The Enterprise) WG is planning to work on ASAP.  This concept is slightly different from what you described below since these reference architectures will be driven by customer deployment examples versus prescribed architectures given scale or projects.  I'd be interested in determining whether the need for both exists or whether one (or the other) is a superset.
> > 
> > Happy to discuss further when we meet in person.   
> > 
> > Thanks,
> > Shamail
> > 
> >> On Jan 19, 2015, at 3:39 PM, Rochelle Grober <rochelle.grober at huawei.com> wrote:
> >>
> >> I believe Rob Hirschfeld will be in attendance so, Rob (and I if he wants me) can cover the DefCore and Refstack session.  Rob is certainly the expert on DefCore.
> >>
> >> I'd also like to propose a session on defining/finding a project manager to start creating some reference architectures with tested installs.  Right now there is a discussion on the Operators' list on a small installation, 3-5 nodes, with HA.  This could be a fine first reference architecture with all the code and docs to make it similar (or better) to install than devstack.  This is also a good architecture for prospective users for prototyping, testing, or small business installation.  Spec'ing this out during the summit, or at least getting a good start, along with a volunteer project manager, would be a very worthwhile endeavor for the meetup.
> >>
> 
> Regarding reference architectures, have you seen the OpenStack Architecture Design Guide?
> 
> http://docs.openstack.org/arch-design/content/
> 
> Enhancing that one would be great!
> 
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>    GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
>        Graham Norton, HRB 21284 (AG Nürnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
> 
> 
> _______________________________________________
> Product-wg mailing list
> Product-wg at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
> _______________________________________________
> Product-wg mailing list
> Product-wg at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg

-- 
Pete Chadwick
Senior Product Manager
SUSE
pchadwick at suse.com
(M) +1.617.281.2847

www.suse.com