Skip to content

Salt cloud openstack availability zone#12866

Closed
syndicut wants to merge 2 commits intosaltstack:developfrom
syndicut:salt_cloud_openstack_availability_zone
Closed

Salt cloud openstack availability zone#12866
syndicut wants to merge 2 commits intosaltstack:developfrom
syndicut:salt_cloud_openstack_availability_zone

Conversation

@syndicut
Copy link
Copy Markdown

Added support for setting node availability zone in openstack
This feature depends on apache/libcloud#295:
https://issues.apache.org/jira/browse/LIBCLOUD-555

@ghost
Copy link
Copy Markdown

ghost commented May 17, 2014

Test Failed.

If the failures are unrelated to your code, don't stress, a core developer will know these apart.
In the future, if possible, please branch off a passing commit to avoid false positives.
Refer to this link for build results: http://jenkins.saltstack.com/job/salt-pr-build/4449/

@techhat
Copy link
Copy Markdown
Contributor

techhat commented May 17, 2014

If this depends on libcloud trunk, it should be documented as such in the code, at the very least.

@gtmanfred
Copy link
Copy Markdown
Contributor

+1 to this, I would prefer if this was only added to kwargs if it actually is set, and in a possibly in a try: except block so that if they aren't running the newest/trunk version of libcloud, they will actually give a good error at why the server boot isn't working.

Other than that, it looks good

@techhat
Copy link
Copy Markdown
Contributor

techhat commented May 17, 2014

I will have to agree with @gtmanfred on this. @syndicut if you don't mind doing that, I would love to merge this.

@syndicut
Copy link
Copy Markdown
Author

Yep, I'll fix it

@grischa
Copy link
Copy Markdown
Contributor

grischa commented May 19, 2014

Oh, I just wrote this as well, saw this pull request too late.
Here is my version: https://github.com/grischa/salt/compare/openstack_availability_zones?expand=1
It solves the first request, a default of None that doesn't add any kwarg.
It does not do a try..except though, but libcloud will just ignore unknown kwargs, I believe. Once libcloud-trunk with zones has a version number we could test that.

@syndicut
Copy link
Copy Markdown
Author

Oh, can you open pull reqest for your commit? I'll close mine

@grischa
Copy link
Copy Markdown
Contributor

grischa commented May 19, 2014

Done, cheers

@syndicut syndicut closed this May 19, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants