Azure Compute Driver #499
Closed
Azure Compute Driver #499
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
…e_driver Libcloud 556 azure compute driver
… Also added existing instance endpoints for a node to the extra dict
…ompute_driver_rebased Support for Virtual Machine Images and handling of Temp Redirects
Conflicts: libcloud/compute/types.py
… 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. @bennettaur @davidcrossland @azurecoder @baldwinSPC @baldwinmathew - thanks to everyone for their contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a continuation of #305.
My goal is to fix bugs, style issues, Python version compatibility issues and any other issues which might pop up during the review and testing and get this merged into trunk.
As you can see in the commit log, I have already changed and fixed a bunch of things, but there are still issues I'm tracking down.
For example, creating a new storage service returns 400 status code without any meaningful error message. I'm digging in, but I have no idea why this is happening yet.