Open Stack

Thanks Flanders for the summary!

Everyone, we’re closing this discussion next week before our meeting, drafting a final, and submitting that for approval. So if you want to chime in, please do so before Monday (July 11th)

:D
Patricia

Everyoe'
From: David F Flanders <dff.openstack at gmail.com<mailto:dff.openstack at gmail.com>>
Date: Tuesday, June 28, 2016 at 1:00 AM
To: user-committee <user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>>
Subject: Re: [User-committee] [app] What is an App?

+1 for a worthwhile discussion.

Accordingly, here are some "bullet points" from the discussion thus far, which I would hope to receive some further clarification if not summarised to your liking:

i.) An OpenStack cloud application is functionality deployed via: a.) an SDK/API, b.) atop instances (VMs, Containers), c.) through an application platform (i.e. PaaS, HPC, etc)

ii.) From an "end user perspective" a cloud "app" should be installed via "one click"; alternatively "cloud sofware" will require some installation processes.

iii.)  There are three broad categories of application being built for OpenStack: a.) [Cloud Hosted] Apps built atop SDKs/APIs, b.) [Cloud Optimised + Cloud Native] Apps built atop OpenStack (not necessarily aware of infrastructure it is using), c.) [Cloud App Components] app-software which are components for AppDev+DevOpps+SysAdmin.

iv.) There should be further consideration by the user-committee to support application developers who do not want to know about the infrastructure atop which they are deploying their application.  Especially for the purpose of collecting use cases from these application developers.

v.) Usability is a problem.  Container communities (because they are made up of application developers) are scratching these issues.  What can we learn from them?

As a bit-o-fun see a quick word count of keywords from the emaisl thus far (including re-quoted) lines:

59OpenStack
28App
18something
16like
15software
15app
14use
13project
13using
12users
12think
11definition
11want
11projects
10SDK
10API
10Ecosystem
10provide
9make
9now
9infrastructure
9cloud
9feature
8work
7cross
7application
7example
7support
7things
7developers
6willing
6user
6need
6community
6Ansible
6time
6question
6problem
6currently
5Application
5scope
5Cloud
5will
5enough
5resources
5top
5may
5Neutron
5deployed
5seem
5just
5group
5set
5web
5instances
5objectives
5click
5built
5applications
5say
5specific
4audience
4experience
4capital
4every
4Nova
4others
4focused
4define
4shall
4making
4cases
4deploy
4refer
4install
4via
4run
4SDK's
4start
4mobile
4Apps
4place
4storage
4someone
4worked
4long
4apps
4examples
4without
4difficult
4access
4API's
4also
4Wordpress
3though
3got
3land
3care
3happen
3Blog
3directly
3criteria
3create
3provision
3help
3Trove
3goal
3address
3form
3Core
3type
3wordpress
3back
3right
3Let
3issue
3person
3random
3two
3much
3getting
3IRC
3general
3issues
3common
3questions
3rely
3Catalog
3point
3however
3modules
3clarify
3large
3whether
3try
3else
3advocate
3lingo
3mission
3trying
3replication
3discussion
3outside
3problems
3engineer
3mind
3end
3tools
3around
3Training
3asked

Best, Flanders




--
=================
Twitter: @DFFlanders<https://twitter.com/dfflanders>
Skype: david.flanders
Based in Melbourne, Australia


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20160706/8611fad2/attachment-0001.html>