Open Stack

Everett:

you may want to add a question such as  

	* “Why did you use this  library?”

This may give an additional insight and possibly motivation for further actions/development. Some examples 

a) in Python the use of libcloud via the EC2 is popular. Why?: compatibility

b) in the  cloudmesh project we developed our own compatibility library that makes use of the native openstack protocol instead of using lib cloud/EC2 to access openstack. Why: (1) libcloud/EC2 has limited functionality, (2) debugging of production clouds with native protocols (starting thousands of vms), (3) easier integration into user interfaces while leveraging JSON. (4) Together this allows us to have an API that accesses and manages VMS on AWS, Azure, and Openstack the same way but uses in case of Openstack the native protocol instead of lib cloud/EC2.


On Jan 16, 2014, at 5:01 PM, Everett Toews <everett.toews at RACKSPACE.COM> wrote:

> Hi All,
> 
> Inspired by this thread [1], I think it's time we try to formulate some application developer oriented questions for the user survey. Having this information will help us guide OpenStack developers, SDK developers, and other tool developers.
> 
> Sean Dague already proposed the following 3 questions. I've added some more answers to the first to flesh it out. I replaced the work toolkit with code in questions 2 and 3.
> 
> 1. What toolkits do you use to interface with the OpenStack API?
> * OpenStack command line (i.e. nova cli)
> * OpenStack libraries (Python)
> * jclouds (Java)
> * fog (Ruby)
> * pkgcloud (node.js)
> * openstack.net (C#)
> * php-opencloud (PHP)
> * deltacloud (HTTP API)
> * other - please specify
> * none - wrote our own
> 
> 2. If you wrote your own code for accessing the OpenStack API, what wire format are you using?
> * JSON
> * XML
> 
> 3. If you wrote your own code for accessing the OpenStack API, what programming language did you write it in?
> * Python
> * Java
> * Ruby
> * node.js
> * C#
> * PHP
> * Perl
> * C/C++
> * Other (please specify)
> 
> All of the answers would be multi-select. e.g. checkboxes instead of radio buttons.
> 
> Do we need more questions?
> 
> Do we need change the wording of the questions as if it's from the perspective of the OpenStack operators asking their users what tools they are using to develop applications on an OpenStack cloud?
> 
> e.g.  What toolkits *are your users using* to interface with the OpenStack API?
> If *your users wrote their* own code for accessing the OpenStack API, what wire format are *they* using?
> 
> Regards,
> Everett
> 
> [1] http://lists.openstack.org/pipermail/openstack/2014-January/004638.html
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack