Age | Commit message (Collapse) | Author | |
---|---|---|---|
2012-11-13 | Even when using boto < 2.6 force the unlazying to occur | Joshua Harlow | |
It seems like its possible that boto 2.5.2 and below have the lazy loading metadata dictionary so as a precaution we will always take the hit of unlazying the metadata dictionary by traversing it which in the non-lazy dictionary case has no effect (its marginal). This also removes the need to check the boto version and the dependency on setup tools just for this case. | |||
2012-11-12 | pep8 and pylint fixups | Scott Moser | |
2012-11-12 | add comment to get_instance_userdata reguarding empty/un-provided userdata | Scott Moser | |
2012-11-09 | Fix the none return problem. | Joshua Harlow | |
2012-10-24 | Move the comment to the top + mark as fixing. | Joshua Harlow | |
LP: #1068801 | |||
2012-10-24 | Handle the case where newer versions of boto | Joshua Harlow | |
are used that lazily load the metadata from the ec2 metadata service. 1. Add a ec2_utils module that checks which version of boto is being used and under the right versions the metadata dictionary will be expanded. 2. Use this new ec2_utils module in the cloudstack and ec2 datasources as there entrypoints into boto. |