| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2021-09-13 | |||
| 05:57:17 | thomasb06 | The build didn't rerun over my last commit | |
| 05:58:09 | thomasb06 | Next folder in the list seems to be `instance_ha`, if I didn't forget one in the middle | |
| 06:03:43 | gtema | What was you expecting that you say "didn't return"? | |
| 06:06:41 | thomasb06 | Zuul should have run the build again, shouldn't it? | |
| 06:18:55 | gtema | Why? When? | |
| 06:19:59 | gtema | According to https://review.opendev.org/c/openstack/openstacksdk/+/808209 you pushed on Sep. 10 last time, Zuul checked and posted results | |
| 06:29:13 | thomasb06 | Ha, I didn't refresh the web page... My bad | |
| 06:30:28 | thomasb06 | The last one: https://review.opendev.org/c/openstack/openstacksdk/+/808580 | |
| 08:24:59 | thomasb06 | The build fails but it doesn't seem to have something to do with me? | |
| 08:27:00 | gtema | nope, it's not. You can leave comment "recheck" in the web ui. Zuul will restart | |
| 10:04:30 | thomasb06 | indeed, this time it passed. Thanks | |
| 12:55:02 | thomasb06 | class KeyManager: https://review.opendev.org/c/openstack/openstacksdk/+/808761 | |
| #openstack-sdks - 2021-09-14 | |||
| 07:41:23 | thomasb06 | The Message class: https://review.opendev.org/c/openstack/openstacksdk/+/808876 | |
| 10:44:46 | vkmc | hi folks | |
| 10:44:57 | vkmc | trying to tweak and output to be more user friendly | |
| 10:45:10 | vkmc | I'm using this function over here https://github.com/openstack/osc-lib/blob/master/osc_lib/utils/__init__.py#L487 | |
| 10:45:35 | vkmc | basically the resource we have has it's id and the project_id | |
| 10:45:42 | vkmc | wanted to add the project_name as well | |
| 10:45:59 | vkmc | any tips on how to do this? | |
| 10:46:19 | gtema | where do you want to add it to? | |
| 10:46:26 | vkmc | to the output | |
| 10:46:42 | gtema | in the output is load said - which output, which command? | |
| 10:47:05 | vkmc | ah sorry | |
| 10:47:14 | vkmc | manila share group type access list | |
| 10:47:22 | vkmc | so, openstack share group type access list | |
| 10:47:26 | vkmc | patch is here | |
| 10:47:34 | gtema | generally we only "output" what API sends to us | |
| 10:47:40 | vkmc | https://review.opendev.org/c/openstack/python-manilaclient/+/805064 | |
| 10:47:55 | vkmc | more context here | |
| 10:47:56 | vkmc | https://review.opendev.org/c/openstack/python-manilaclient/+/805064/16/manilaclient/osc/v2/share_group_type_access.py#89 | |
| 10:47:58 | gtema | normally we do not add anything else, but there are exceptions where i.e. for server we also extend it with flavor details | |
| 10:48:11 | vkmc | yep, is feeling a bit "against" the design to add that info | |
| 10:50:04 | vkmc | gtema, so this use case is nowhere in some other projects implementations? | |
| 10:50:08 | vkmc | I just want to keep consistency on how we do things | |
| 10:50:20 | gtema | in principle the approach is fine. But definitely this is not really performant to find project each time | |
| 10:50:45 | vkmc | hmm good point | |
| 10:50:50 | gtema | this particular approach of extending output with project_name - no, it's not present anywhere | |
| 10:51:14 | vkmc | I'll discuss with the reviewer | |
| 10:51:35 | gtema | another issue is that the user might not really have priviliges to list/find project. This is unlikely, but you anyway can never say for sure it will work | |
| 10:52:09 | vkmc | so this is an admin operation, in which case that shouldn't be the issue | |
| 10:52:41 | vkmc | unless I'm missing something | |
| 10:52:42 | gtema | ok, but you know - admin of manilla is not necessarily having admin privs in identity | |
| 10:52:48 | vkmc | yep | |
| 10:53:27 | vkmc | it's a good point | |
| 10:53:36 | gtema | cloud operators are keen to really separate privs as much as possible and even you are domain admin but with the project scope token you might not have privs to list projects | |
| 10:54:11 | vkmc | makes sense | |
| 18:08:53 | gouthamr | the admin in this context is a system admin | |
| 18:09:21 | gouthamr | at least by default; although its possible to override | |
| #openstack-sdks - 2021-09-15 | |||
| 18:17:42 | opendevreview | Daniel Speichert proposed openstack/ansible-collections-openstack master: Added missing warn() used in cloud.openstack.quota https://review.opendev.org/c/openstack/ansible-collections-openstack/+/805534 | |
| 18:38:51 | opendevreview | Daniel Speichert proposed openstack/ansible-collections-openstack master: Added missing warn() used in cloud.openstack.quota https://review.opendev.org/c/openstack/ansible-collections-openstack/+/805534 | |
| #openstack-sdks - 2021-09-16 | |||
| 15:45:28 | diablo_rojo | o/ | |
| 15:45:38 | diablo_rojo | Did we want a meeting in 15 min stephenfin gtema?> | |
| 15:45:52 | gtema | well, I also got reminder popup | |
| 15:46:03 | gtema | I am available | |
| 15:50:31 | diablo_rojo | Me too | |
| 15:50:42 | diablo_rojo | Maybe we do some PTG planning? | |
| 15:51:27 | gtema | maybe. I only reserved 1h slot but looking to the current activity I can't really say what to talk about ;-) | |
| 15:54:27 | diablo_rojo | Haha fair. | |
| 15:54:36 | diablo_rojo | I haven't heard from Orran about students yet either. | |
| 15:55:32 | gtema | we have thomasb06 here from Franch recently. I had small session with him last week and gave some tasks | |
| 15:55:55 | gtema | s/Franch/France | |
| 15:56:27 | diablo_rojo | Oh yes! lbragstad had connected him with me and I directed him here to help :) | |
| 15:57:06 | gtema | I have however figured out that replacing cinderclient in OSC must be done pretty urgently. With drop of v2 support there we are going in unpleasant situation for older clouds | |
| 15:58:04 | gtema | I would say block storage in SDK is now pretty in a good shape, but most of things in proper form are now in r1 branch | |
| 15:58:32 | gtema | what somehow forces to merge those quickly back to master | |
| 15:58:54 | gtema | on the other side work on r1 is not complete as I hoped | |
| 16:01:53 | diablo_rojo | Should we start a meeting? | |
| 16:02:00 | gtema | oh yes | |
| 16:02:04 | gtema | how was that | |
| 16:02:14 | opendevmeet | The meeting name has been set to 'sdk' | |
| 16:02:14 | opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 16:02:14 | opendevmeet | Meeting started Thu Sep 16 16:02:14 2021 UTC and is due to finish in 60 minutes. The chair is gtema. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 16:02:14 | gtema | #startmeeting sdk | |
| 16:02:32 | diablo_rojo | nailed it :) | |
| 16:03:04 | diablo_rojo | So what needs to happen then? | |
| 16:03:26 | gtema | well, contribution needs to happen ;-) | |
| 16:03:50 | gtema | I mean we need to bring r1 in shape and merge it to master | |
| 16:04:01 | diablo_rojo | Okay so what does that entail exactly? | |
| 16:04:18 | gtema | completing cleanup of the cloud layer | |
| 16:04:38 | gtema | there I also started generalizing metadata and quotasets for the resources | |
| 16:05:09 | gtema | I want also to do same for quota and limits and create I/F for querying quotas of all services | |
| 16:05:29 | gtema | so that SDK tries all possible methods to get to quota/limit/quotaset/etc for the services | |
| 16:05:43 | gtema | then CLI can only trigger single function in SDK | |
| 16:06:06 | diablo_rojo | Okay. | |
| 16:06:22 | gtema | there's also https://review.opendev.org/c/openstack/openstacksdk/+/805851 | |
| 16:06:34 | gtema | an attempt to change how caching works | |
| 16:06:48 | gtema | cause that is also sort of breaking change | |
| 16:07:10 | gtema | overall - we have already in r1 some "breaking" changes | |
| 16:07:33 | gtema | and I want to complete those before we really do a bang | |
| 16:08:14 | gtema | actually with all the students I have figured out that we miss doc in the form "so you want to understand how SDK works?" | |
| 16:08:59 | gtema | something really describing principles of resource and proxy, cloud layer, guiidelines, etc | |
| 16:09:33 | diablo_rojo | That would be help. | |
| 16:09:51 | gtema | yeah, and it would be help if somebody writes such doc ;-) | |
| 16:10:41 | diablo_rojo | I am happy to help formulate and review and whatnot. | |
| 16:10:56 | gtema | :) | |
| 16:11:00 | diablo_rojo | I suppose I could take a stab on it if we did a call at somepoint to go over what all you think should be included. | |
| 16:11:30 | gtema | yeah, can be arranged | |
| 16:12:38 | gtema | maybe next week if you have time | |
| 16:13:26 | diablo_rojo | Yeah next week works for me | |
| 16:13:58 | gtema | smth like Thursday same time? Or is it still too early? | |