Correct iso8601 parseing invalid year num

iso8601 should raise reasonable error when parsing timestamp with invalid
years. This is implemented in iso8601 version 0.1.9.
More details please see the bug description and the issue on bitbucket.

Change-Id: I23ec6a125110294f49eb55ced02ff4e5965a0b99
Closes-Bug: #1266398
Update oslo.vmware to be >= 0.2

There are a number of bug fixes that deal with image and session
management.

Change-Id: I27e62ac6a6d4e0bbadf1be3dbc62d38cd68e9f58
Sets the min python-novaclient version to 2.16.0

python-novaclient 2.16.0 introduces RDP support required
by Horizon for the "hyper-v-rdp-console" BP.

Change-Id: I44a0ba108c9272bd6ef7ab71d587367c0eddaaac
Adding support for Django 1.6

Horizon and django_openstack_auth 1.1.4 are both now compatible
with Django 1.6.  Bumping versions of Django to include 1.6 and
django_openstack_auth to force a Django 1.6 compatible version.

Partially-implements blueprint django-1point6

Change-Id: Id753ffa53d2484dab39e530de0a41e85f9e07742
Sets the minimum python-novaclient version to 2.17.0

python-novaclient 2.17.0 introduces external event support,
required for nova/neutron interaction.

Change-Id: I3c03bfccb38ec5029370daf25f60575bc3e00103
Merge "Update oslo.vmware to be >= 0.2"
Switch to SQLAlchemy 0.9

After SQLAlchemy-migrate has been fixed for SQLAlchemy 0.9,
and after the last problem (with Keystone) has been fixed,
we finally can switch to SQLAlchemy 0.9. It is important we
do the switch to SQLAlchemy 0.9.x ASAP, because that is what
distributions (eg: at least Debian) are using. This also
ensure we avoid any future mistakes if we do the gating with
SQLAlchemy 0.9.

This patch sets the cap from <=0.8.99 to <=0.9.99.

Change-Id: I9d2a9e0526359fa1e97df250a63f71496d47367a
Revert "Switch to SQLAlchemy 0.9"

This reverts commit fde324efaf57decd1a33dc61bb1f5f9e93f4d79b
Merge "Adding support for Django 1.6"
Merge "Revert "Switch to SQLAlchemy 0.9""
Merge "Correct iso8601 parseing invalid year num"