NOTE(dtroyer) Apr 2015: This repo is under heavy revision as it is being revived.
openstack/golang-client is an implementation of OpenStack API client in Go language.
The code follows OpenStack licensing and uses its CI infrastructure
for hosting. It currently implements Identity Service v2
and Object Storage v1.
The initial focus is on building a solid core REST Session and OpenStack
authentication on which to build the usual API interfaces. The architecture
Session and authentication is similar to that used in the current
Python Keystone client library: The
Session object contains the HTTP
interface methods and an authentication object that provides access to
the auth token and service catalog.
Code maturity is considered experimental.
go get git.openstack.org/openstack/golang-client. Or alternatively,
download or clone the repository.
The lib was developed and tested on go 1.3. No external dependencies, so far.
The examples directory contains examples for using the SDK using
real world working code. Each example starts with a two digit number followed
by a name (e.g.,
00-authentication.go). If you have a
config.json file in the
examples directory following the format of
config.json.dist the example can be
go run [example name] setup.go. Or, all the examples can be
executed running the script
run-all.sh from the examples directory.
There are two types of test files. The
*_test.go are standard
golang unit test files. The examples can be run as integration tests.
The tests were written against the OpenStack API specifications. The integration test were successful against the following:
If you use another provider and successfully completed the tests, please email the maintainer(s) so your service can be mentioned here. Alternatively, if you are a service provider and can arrange a free (temporary) account, a quick test can be arranged.
The code repository utilizes the OpenStack CI infrastructure. Please use the recommended workflow. If you are not a member yet, please consider joining as an OpenStack contributor. If you have questions or comments, you can email the maintainer(s).