-
Notifications
You must be signed in to change notification settings - Fork 924
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[LIBCLOUD-691] Add Onapp IaaS platform support #502
[LIBCLOUD-691] Add Onapp IaaS platform support #502
Conversation
6f27333
to
507fbaa
Compare
Great, thanks. I will review it and add the comments inline. |
name = 'OnApp' | ||
website = 'http://onapp.com/' | ||
|
||
def create_node(self, label, memory, cpus, cpu_shares, hostname, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This method is part of the standard API so all the arguments which are not part of standard API (looks like all of them :)) should have an ex_
prefix.
@MatthiasWiesnerCC bump^^ |
507fbaa
to
932420d
Compare
I took over the onapp integration on our side. I prefixed the non standard parameter with |
a9cee1f
to
ce4e1dd
Compare
ac8bbad
to
5c54d41
Compare
Implement missing support for Virtual Server in OnApp node driver, as described in the OnApp API documentation: https://docs.onapp.com/display/34API/Virtual+Servers
5c54d41
to
9b78efe
Compare
@Kami bump^^ :-) |
Sorry for the delay. The changes looked OK (except a weird test failure - see below), so I went ahead and merged it into trunk. Thanks. There was a just a weird test failure which only happened on every Python version except 2.7.
It turned out the failure was related to using The test passing on 2.7 was just a pure luck :) |
|
||
class OnAppNodeTestCase(LibcloudTestCase): | ||
def setUp(self): | ||
def _request(*args, **kwargs): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, just a quick heads up for the future - we have a framework in place for mocking HTTP responses (pretty much every driver tests use it).
So in the future, please use follow the approach other tests use.
Corresponding issue:
https://issues.apache.org/jira/browse/LIBCLOUD-691