Software Development Kits
SDKs are a vital part of the OpenStack ecosystem, they help developers write applications for OpenStack and other clouds. For a list of the official OpenStack Python client libraries, see OpenStackClients.
- A set of language bindings that provide a language-level API for accessing OpenStack in a manner consistent with language standards.
- A Getting Started document that shows how to use the API to access OpenStack powered clouds.
- Detailed API reference documentation.
- Tested sample code that you can use as a "starter kit" for your own OpenStack applications.
- SDKs treat OpenStack as a blackbox and only interact with the REST/HTTP API.
- Must be sustainable.
- License must be compatible with Apache License v2.
What criteria is used to determine whether or not an SDK can be considered an OpenStack SDK has not been formalized. This has been initially discussed at the OpenStack Grizzly Summit (etherpad). Naturally the SDK will need to meet the definition above. In addition we thought the OpenStack Foundation may want to consider a compatibility test suite that will validate whether or not an SDK supports OpenStack.
These are items that could be used as criteria to define an SDK but themselves require further definition w.r.t. SDKs.
- Handle extensions in some way.
- Backwards compatibility.
- Compatibility with test suite.
Official OpenStack Clients
The OpenStackClients are the native Python bindings for the OpenStack APIs. They are used to implement the command-line interfaces (which ship with the library).
What follows is a list of known SDKs that support OpenStack. This is not a list of official OpenStack SDKs. What constitutes an official OpenStack SDK has not been determined. This is an area the needs more work (see Criteria section).
To date, SDKs that support OpenStack fall into two categories. SDKs that support multiple clouds including OpenStack (aka multi-cloud toolkits) and SDKs that support OpenStack only. If you're aware of any other SDKs, please add them to the lists below.
- clj-openstack is a pure Clojure Binding for OpenStack Clouds
- lfe-openstack is a pure LFE (Lisp Flavored Erlang) language binding for OpenStack Clouds.
- Gophercloud provides a Go binding to OpenStack cloud APIs.
- golang-client is a proposed OpenStack project that is designed to improve the experience of OpenStack end-users who are using the Go programming language by providing them with everything they need to develop applications against OpenStack.
- Apache jclouds is an open source library that helps you get started in the cloud and utilizes your Java or Clojure development skills. The jclouds API gives you the freedom to use portable abstractions or cloud-specific features.
- OpenStack Java SDK is a Java binding for the OpenStack APIs.
- js-openclient is a very opinionated core client which can be used in either Node.js or in the browser (browser support not yet complete) to communicate with a RESTful APIs, including but not limited to any OpenStack-compatible API.
- OpenStack.NET is a .NET SDK for OpenStack.
- pkgcloud is a standard library for Node.js that abstracts away differences among multiple cloud providers.
- Net::OpenStack::Compute provides Perl bindings for the OpenStack Compute API. It also provides a command line tool oscompute for interacting with an OpenStack deployment.
- php-opencloud is a software development kit (SDK) to help developers using PHP to work with OpenStack and other open clouds.
- ZendService_OpenStack is a PHP library that implements the last versions of the OpenStack API. It's 100% compliant with the specification of OpenStack.
- The OpenStackClients are the native Python bindings for the OpenStack APIs. They are used to implement the command-line interfaces (which ship with the library).
- pyrax should work with most OpenStack-based cloud deployments, though it specifically targets the Rackspace public cloud.
- Apache libcloud is a standard Python library that abstracts away differences among multiple cloud provider APIs.