Johannes Erdfelt 6e5f2d88e6 Add support for header version parameter to specify API version.
bug 844905

The 1.1 API specifies that the API version can be determined by URL path
(eg /v1.1/tenant/servers/detail), Content-Type header
(eg application/json;version=1.1) or Accept header
(eg application/json;q=0.8;version=1.1, application/xml;q=0.2;version=1.1).

Change-Id: I01220cf1eebc0f759d66563ec67ef2f697c6d310
2011-10-04 14:44:34 +00:00
2011-09-20 02:55:56 -07:00
2011-09-09 08:46:58 +02:00
2011-08-16 08:41:52 -04:00
2011-07-26 09:50:05 +04:00
2011-09-29 10:57:27 +01:00
2010-07-15 01:28:51 -04:00
2011-07-29 15:58:41 -04:00
2010-05-27 23:05:26 -07:00
2010-12-20 14:54:27 -06:00
2011-09-30 10:33:15 -05:00
2011-01-10 11:26:38 -08:00

The Choose Your Own Adventure README for Nova:

  You have come across a cloud computing fabric controller.  It has identified
  itself as "Nova."  It is apparent that it maintains compatibility with
  the popular Amazon EC2 and S3 APIs.

To monitor it from a distance: follow @novacc on twitter

To tame it for use in your own cloud: read http://nova.openstack.org/getting.started.html

To study its anatomy: read http://nova.openstack.org/architecture.html

To dissect it in detail: visit http://code.launchpad.net/nova

To taunt it with its weaknesses: use http://bugs.launchpad.net/nova

To watch it: http://hudson.openstack.org

To hack at it: read HACKING

To laugh at its PEP8 problems: http://hudson.openstack.org/job/nova-pep8/violations

To cry over its pylint problems: http://hudson.openstack.org/job/nova-pylint/violations

Description
OpenStack Compute (Nova)
Readme 1.6 GiB
Languages
Python 97.6%
Smarty 2.3%
Shell 0.1%