Open Stack

Any possibility to put this up at gerrit so that these discussions are
tracked.

On Friday, July 22, 2016, Caballero Abraham, Rodrigo <
rodrigo.caballero.abraham at intel.com> wrote:

> I would then suggest:
>
> An OpenStack application is an application, toolset, or platform, that is
> built using, deployed atop, or that runs atop, OpenStack services, APIs, or
> SDKs.
>
>
>
> *From:* Igor Marnat [mailto:imarnat at mirantis.com
> <javascript:_e(%7B%7D,'cvml','imarnat at mirantis.com');>]
> *Sent:* Thursday, July 21, 2016 7:37 AM
> *To:* Sun, Yih Leong <yih.leong.sun at intel.com
> <javascript:_e(%7B%7D,'cvml','yih.leong.sun at intel.com');>>
> *Cc:* Stefano Maffulli <stefano at openstack.org
> <javascript:_e(%7B%7D,'cvml','stefano at openstack.org');>>;
> user-committee at lists.openstack.org
> <javascript:_e(%7B%7D,'cvml','user-committee at lists.openstack.org');>
> *Subject:* Re: [User-committee] [app] What is an App?
>
>
>
> I'd say that "built using", "deployed atop" and "run atop" from the first
> part describes relationships between Apps and OpenStack in more specific
> manner than "has direct interaction" from the last one. Latter one is
> somewhat vague, isn't it?
>
>
> Regards,
>
> Igor Marnat
>
>
>
> On Thu, Jul 21, 2016 at 6:33 AM, Sun, Yih Leong <yih.leong.sun at intel.com
> <javascript:_e(%7B%7D,'cvml','yih.leong.sun at intel.com');>> wrote:
>
> I also think that the 3rd point is too wide. We should target on
> application that has "direct interaction" with OpenStack components.
>
> Cloud applications in the perspective of the App Ecosystem Working Group
> include
> 1. applications built using OpenStack SDK’s or API’s; or
> 2. applications deployed atop OpenStack using Heat, Murano, or 3rd party
> deployment/management tools (e.g. ansible, puppet, chef); or
> 3. PaaS platform that run atop OpenStack (e.g. CloudFoundry, OpenShift,
> k8s)
>
> In fact, the above three can be summarized into one "generalized
> statement":
> An OpenStack application is an application, toolset or platform that has
> direct interaction with OpenStack services, its API or SDKs.
>
>
>
>
> -----Original Message-----
> From: Christopher Aedo [mailto:doc at aedo.net
> <javascript:_e(%7B%7D,'cvml','doc at aedo.net');>]
> Sent: Wednesday, July 20, 2016 4:14 PM
> To: Sterrett, Craig <craig.sterrett at intel.com
> <javascript:_e(%7B%7D,'cvml','craig.sterrett at intel.com');>>
> Cc: Stefano Maffulli <stefano at openstack.org
> <javascript:_e(%7B%7D,'cvml','stefano at openstack.org');>>;
> user-committee at lists.openstack.org
> <javascript:_e(%7B%7D,'cvml','user-committee at lists.openstack.org');>
> Subject: Re: [User-committee] [app] What is an App?
>
> On Wed, Jul 20, 2016 at 3:43 PM, Sterrett, Craig <craig.sterrett at intel.com
> <javascript:_e(%7B%7D,'cvml','craig.sterrett at intel.com');>> wrote:
> >On Wed, Jul 20, 2016 at 2:48 PM, Stefano Maffulli <stefano at openstack.org
> <javascript:_e(%7B%7D,'cvml','stefano at openstack.org');>> wrote:
> >> On 07/20/2016 02:21 PM, Montenegro, Patricia wrote:
> >>> As promised here’s the draft I propose we vote on next meeting:
> >>
> >> I'm glad we're using the mailing list some more, thanks for the nudge.
> >>
> >> I'm rewriting the definition using bullet points to make it more
> readable:
> >>
> >>         Cloud applications in the perspective of the App Ecosystem
> Working
> >>         Group include
> >>
> >>           * applications built using OpenStack SDK’s or API’s; or
> >>           * applications deployed atop OpenStack using Heat, Murano, or
> >>             3rd party deployment/management tools; or
> >>
> >> (this includes ansible, puppet, chef, etc, correct?)
> >>
> >>           * applications running within containers, or PaaS solution
> >>             atop OpenStack.
> >>
> >> This is last part I am not convinced about.
> >>
> >> PaaS on top of OpenStack is PaaS, traditionally has been outside of
> >> OpenStack scope. CloudFoundry or OpenShift or k8s or the next thing
> >> are
> >> *applications* for OpenStack, and OpenStack should serve them, not
> >> what runs on top of them (on top of OpenStack).
> >>
> >> I fear we get the scope of this group too wide if we define
> >> "OpenStack Applications" as applications that run on CloudFoundry or
> Docker Swarm.
> >>
> >> Other thoughts?
> > Yes to "(this includes ansible, puppet, chef, etc, correct?)"
> > I don't know if we can put in sample names because I don't feel like we
> want to promote one over the other since they are not OpenStack products,
> but if people think it's OK, then lets add some.
> >
> > I personally feel like we need to include the 3rd bullet, for PaaS/containers,
> because it's such a hot topic, just look at how many of the talks in Austin
> were Kubernetes, Docker, etc.  I don't know how much we will do, or can
> do to support apps on top of those solutions, but personally I feel like we
> need to at least mention them.
> >
>
> Thank you Patricia and Craig for putting this together!
>
> I agree with Stefano to a degree on this.  The third bullet seems too wide
> to me since it kind of skips an abstraction layer (at least the way I'm
> thinking about this).  I also agree that we need to cover the containers
> and PaaS as well though.  What about shortening it to:
>
> * PaaS and container solutions running atop OpenStack
>
> That's clearer to me, in that we're still considering the concepts of
> container solutions (like kubernetes) and PaaS solutions but putting the
> focus at that layer rather than what runs above them?  Then we're still
> talking about the things that touch OpenStack so it's consistent with the
> other bullet.
>
> -Christopher
>
> > Craig Sterrett
>
> >>
> >> /stef
>
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> <javascript:_e(%7B%7D,'cvml','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
> <javascript:_e(%7B%7D,'cvml','User-committee at lists.openstack.org');>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20160722/dd9ed46f/attachment.html>