Azure Compute Driver #499
driver can be used to crete, destroy, and so forth.
…hon. This is being done to eliminate the requirement for the Azure library to be pre-installed on the system. Users can now simply load up libcloud and be on their merry way with no external requirements.
…ctions are now refactored and the import of that library is not required anymore. Onto testing.
…m role sizes supported
…achieved. Added 307 to the list of possible errors, sometimes these are sent by azure
…s elastacloud sub-id, ensured tests no longer rely on elastacloud pem file. Empty file in fixtures serves as an adequate replacement
… OK. Removed default VM image name map as its already out of date. Ensure line lengths are no greater the 80 characters where appropriate. Fixed unit tests
… Also added existing instance endpoints for a node to the extra dict
… is alaways available on the custom response type objects.
Alright, the pull request has finally been merged into trunk.
I've addressed all the Python version compatibility issues, fixed all the bugs I have found and added some basic docs. Keep in mind I have only tested basic functionality (list sizes, list images, list nodes, create node, destroy node, ...) so there might be more bugs hidden in other places.