| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2020-03-06 | |||
| 19:18:18 | umbSublime | Thank you ! Through all our discussions in the last few days I learned so much about the SDK's and OSC's inner workings ! | |
| 19:20:46 | mordred | yay! what a successful week then! | |
| 19:39:38 | openstackgerrit | Monty Taylor proposed openstack/python-openstackclient master: Honor api version settings in config like CLI https://review.opendev.org/711732 | |
| 19:40:04 | mordred | umbSublime: ^^ can you try that and see if it fixes the issue for you when you set the compute_api_version on the CLI? | |
| 19:40:06 | mordred | gah | |
| 19:40:10 | mordred | in the clouds.yaml | |
| 19:40:44 | mordred | it injects the value into the stream similarly to how it works with --os-compute-api-version which WAS working for you | |
| 19:44:22 | umbSublime | I'll give it a shot shortly and report back | |
| 19:49:39 | umbSublime | Before and after the patch `print(version_opt)` returns 2.1 (to make sure it's not a lib version issue let me just test in fresh venv) | |
| 19:50:11 | mordred | so weird | |
| 19:51:06 | umbSublime | Sobasically i don't enter the patch because `version_opt = str(self.cloud.config.get(option, default_version))` appears to be setting the value to '2.1'. Where does that 'default_version' come from | |
| 19:55:35 | mordred | oh. that is weird ... let me see | |
| 19:56:29 | mordred | ah. it's in the compute module | |
| 19:56:41 | mordred | but why does the cli arg work | |
| 19:57:39 | mordred | it's possible it's too late in the week to fully wrap my head around this :) | |
| 19:59:14 | mordred | umbSublime: actually ... | |
| 20:00:06 | mordred | so - in that line you just referenced ... | |
| 20:00:24 | mordred | option should be "compute_api_version" right? | |
| 20:01:06 | mordred | if you print self.cloud.config it should be a dict - and if you have compute_api_version in your clouds.yaml it should have compute_api_version in that dict - which means that line _should_ be returning your setting and not the default fallback value | |
| 20:15:18 | umbSublime | checking now, (sorry was AFK) | |
| 20:16:22 | mordred | no worries! | |
| 20:17:03 | mordred | thanks for trying out all the things :) | |
| 20:17:25 | umbSublime | option isn't in the dic, so the the .get returns default_version | |
| 20:18:28 | umbSublime | I see though that for other services I get and int. for example for identity Option=3 | |
| 20:20:47 | umbSublime | herr nvm I did this without thinking | |
| 20:21:01 | umbSublime | I didn't notice option wasn't the key name, but a var containing the key name | |
| 20:25:03 | umbSublime | mordred, here is self.cloud.config -> https://hastebin.com/ugiketotup.py | |
| 20:25:39 | mordred | wow. yeah - that sure doesn't have compute_api_version in there | |
| 20:25:47 | mordred | you sure it's in your clouds.yaml? | |
| 20:27:16 | mordred | http://paste.openstack.org/show/790413/ | |
| 20:27:17 | umbSublime | https://hastebin.com/ifulonekaq.cpp | |
| 20:27:19 | mordred | there's mine | |
| 20:27:48 | umbSublime | vexx <3 | |
| 20:28:33 | mordred | you're calling this like openstack --os-cloud=ucne1 hypvisor list | |
| 20:29:42 | umbSublime | no :(, with env_var OS_CLOUD_CONFIG_NAME=ucne1 | |
| 20:29:59 | mordred | that shold still be fine - do you have the other things set via env vars? | |
| 20:30:33 | umbSublime | nothing related to OS_COMPUTE_API_VERSION | |
| 20:31:03 | umbSublime | Just noticed I also have `OS_REGION_NAME=ncsa-east-ne1`, but I don't think that should cause issues | |
| 20:31:32 | mordred | oh wait ... no, OS_REGION_NAME is still a selector and fine | |
| 20:31:33 | mordred | BUT | |
| 20:31:39 | umbSublime | it works with --os-cloud though :O | |
| 20:31:42 | mordred | change OS_CLOUD_CONFIG_NAME=ucne1 to OS_CLOUD= | |
| 20:31:55 | mordred | change OS_CLOUD_CONFIG_NAME=ucne1 to OS_CLOUD=ucne1 | |
| 20:32:11 | umbSublime | 'compute_api_version': '2.53', | |
| 20:32:16 | mordred | \o/ | |
| 20:32:43 | mordred | now does the hypervisor list work without --os-compute-api-version ? (eithe with or without that patch) | |
| 20:32:57 | umbSublime | works with the patch, let me check without | |
| 20:33:52 | umbSublime | :facepalm: it works without the patch. It was env all along :/ | |
| 20:33:56 | mordred | yay! | |
| 20:34:09 | mordred | well - still ... there are some things here I want to refactor :) | |
| 20:34:24 | mordred | but even better ... now we don't have to get any patches released for you | |
| 20:34:34 | umbSublime | XD | |
| #openstack-sdks - 2020-03-07 | |||
| 18:57:26 | openstackgerrit | Merged openstack/python-openstackclient master: Add bindep file https://review.opendev.org/711055 | |
| #openstack-sdks - 2020-03-09 | |||
| 10:51:23 | brtknr | mordred: any idea when openstack modules will be removed from upstream ansible and users will need to wholly rely on collections? | |
| 11:56:06 | rm_work | mordred: going to be good to make an SDK release today you think? :D | |
| 12:59:43 | openstackgerrit | Riccardo Pittau proposed openstack/openstacksdk master: Extract check temp_url_key logic https://review.opendev.org/710973 | |
| 13:10:37 | openstackgerrit | Riccardo Pittau proposed openstack/openstacksdk master: [WIP] Import generate_temp_url from swiftclient https://review.opendev.org/711640 | |
| 14:25:04 | mordred | rm_work: yes! | |
| 14:25:25 | mordred | brtknr: not sure when exactly, but it should be done by the 2.10 release | |
| 14:26:58 | brtknr | mordred: is there a deprecation notice for this somewhere? | |
| 14:31:23 | openstackgerrit | Monty Taylor proposed openstack/openstacksdk master: Set max_microversion to 2.53 for hypervisors https://review.opendev.org/711294 | |
| 14:48:38 | mordred | slaweq: neutron change for you: https://review.opendev.org/#/c/711513/ | |
| 14:49:14 | slaweq | mordred: sure, looking | |
| 14:55:26 | mordred | brtknr, rm_work: remote: https://review.opendev.org/711932 Release 0.42.0 of openstacksdk | |
| 14:55:41 | rm_work | thanks :) | |
| 14:56:39 | brtknr | mordred: yay | |
| 15:09:21 | slaweq | mordred: I just commented in https://review.opendev.org/#/c/711513/ | |
| 15:17:20 | mordred | slaweq: oh good point on the request-side | |
| 15:17:51 | mordred | that seems like something we should add a more general feature to the neutron proxy / resources for | |
| 15:18:17 | mordred | "query_parameter, requires_extension='blah'" ... or something. | |
| 15:18:44 | dtantsur | something similar to microversions, but with extensions? | |
| 15:19:27 | slaweq | mordred: dtantsur yes, we need something like that | |
| 15:19:48 | slaweq | otherwise we will break sdk for clouds without this extension enabled | |
| 15:22:16 | mordred | yah | |
| 15:23:46 | mordred | dtantsur: although I think the difference in this case is for neutron we'd want to be able to tie individual properties of a resource to a needed extension so that attempting to set one if the given extesion isn't there can return a decent error | |
| 15:23:48 | mordred | hrm | |
| 15:23:54 | mordred | actually ... | |
| 15:25:13 | mordred | slaweq: do we really need to do that? if someone tries to set stateful on a cloud that doens't have it - neutron will just throw the error, right? so an sdk-side indication that it needs an extension would be an optimization? | |
| 15:27:33 | slaweq | mordred: actually You're right, if user will not pass "stateful" parameter during e.g. creation of SG then it will be fine | |
| 15:28:03 | slaweq | so maybe we don't need any additional discovery | |
| 15:31:51 | openstackgerrit | Rodolfo Alonso Hernandez proposed openstack/python-openstackclient master: Add "fields" parameter to ListSecurityGroup query https://review.opendev.org/710825 | |
| 15:43:07 | openstackgerrit | Merged openstack/openstacksdk master: Extract check temp_url_key logic https://review.opendev.org/710973 | |
| 16:05:15 | openstackgerrit | Merged openstack/openstacksdk master: Add retired and retired_reason fields to baremetal node https://review.opendev.org/711032 | |
| 16:14:33 | mgoddard | Hi, seeing some issues with os_ironic in Ansible 2.9.6 and openstacksdk 0.41.0 | |
| 16:14:58 | mgoddard | If a node already exists, we get KeyError: 'uuid' | |
| 16:15:45 | mgoddard | it seems to be because the node create response contains a 'uuid' field, but node patch returns 'id'. Possibly something Munch is doing? | |
| 16:15:50 | mgoddard | dtantsur: seen that ^? | |
| 16:17:22 | TomStappaerts | slaweq could you specify what you would like to see added at https://review.opendev.org/#/c/711513/ ? Would just a stateful=True check be sufficient or do you want to create two SG and check on those? | |
| 16:17:37 | TomStappaerts | And am I correct in saying that would be a follow-up patchset? | |
| 16:23:59 | dtantsur | mgoddard: first time I hear about it | |
| 16:24:14 | dtantsur | have a traceback somewhere? | |
| 16:24:50 | mgoddard | dtantsur: as much of a traceback as you'll get from ansible | |
| 16:24:57 | dtantsur | heh | |
| 16:25:05 | mgoddard | os_ironic.py L355 | |
| 16:25:13 | mgoddard | os_ironic.py L331 | |
| 16:25:27 | mgoddard | they line up with the ansible stable-2.9 branch | |
| 16:25:33 | dtantsur | sdk is supposed to return id in all cases | |
| 16:25:45 | mgoddard | os_ironic always uses uuid :) | |
| 16:25:49 | mgoddard | and previously worked | |
| 16:27:53 | dtantsur | why on earth would it work previously, I wonder... | |