Open Stack

Hi Tim,

Those dates look fine to me. In terms of questions asked in an updated 'OpenStack User Survey' I would lobby for addition or clarification of stories for those 'API users' building research, academic, and/or enterprise applications on top of OpenStack deployments.

Current great questions in this vein:
1) What best describes your involvement with OpenStack?
   *  "Consumer of an OpenStack cloud - has API or dashboard credentials for one or more OpenStack resource pools, including an Application Developer" - involvement with OpenStack

2) "What tools are you using or plan on using to deploy/configure your applications?"


Perhaps a new question for such non-operator "application users/developers" addressing their scope and complexity? Something like one of these:


*         How many applications are you involved in supporting on top of an OpenStack deployment?

*         'Stacks' are clusters of integrated collections of VMs deployed together. How many separately-maintained application-stacks (R&D stack, load-test stack, staging-stack, prod-stack) are you involved in supporting on top of an OpenStack deployment?

*         How many concurrent VMs are typically running in support of end-user, research or enterprise applications in your environment's OpenStack deployment?

We could really use such data (mapped against the Industry field of the survey) to further flesh out the "enterprises are/aren't ready for OpenStack" marketing perception being pondered in the 'Win the Enterprise' working group.
Evan Scheessele
HP Publishing Solutions

From: Tim Bell [mailto:Tim.Bell at cern.ch]
Sent: Tuesday, July 15, 2014 11:32 AM
To: User-committee at lists.openstack.org
Subject: [User-committee] User Survey


We have run a user survey prior to each of the OpenStack summits for the past two years.

My default proposal would be to run another one before Paris to see how the community is evolving.

In Hong Kong, we had not planned to present but in the end, an impromptu meetup was organised (which led amongst other things to the start of the operations meet up).

Given that we're hoping to organise an operations 'design' style track at Paris, I would propose to include a quick highlight presentation in that session along with a more detailed document for those who wish to drill down further.

The other question is expiry of clouds which have not been updated. I think that if the data on a deployment has not been updated within 12 months, it should not be considered within the statistics.

Given the timing of the summit at the start of November, a timing such as below would seem reasonable:


-        1st September - Questions finalised

-        15th September - User Survey pages updated and published on openstack.org. Requests to update sent out.

-        7th October - Survey closed

-        4th November - Results published

Any thoughts ?

Tim


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20140716/8208e3fc/attachment.html>