| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2020-11-19 | |||
| 14:40:29 | stephenfin | gtema: There were no API changes in Victoria. There are only minor changes (to the os-hypervisors API) planned for Wallaby so far | |
| 14:40:38 | gtema | yes, it is always _easy_, until you start working on it | |
| 14:40:44 | stephenfin | True :) | |
| 14:40:46 | gtema | oh, changes in hypervisor? | |
| 14:40:57 | gtema | just working on switching it | |
| 14:41:06 | stephenfin | Yes, but I'm doing that so I'll handle the SDK changes when I do it | |
| 14:41:23 | gtema | with few cool things: until 2.53 you use 1 API to search, after - another | |
| 14:41:43 | stephenfin | oh, there's also a spec proposed to remove the final references to 'tenant_id' from the API, in favour of 'project_id'. It's not approved yet but it will be I suspect | |
| 14:41:50 | gtema | and then https://opendev.org/openstack/python-openstackclient/src/branch/master/openstackclient/compute/v2/hypervisor.py#L124 | |
| 14:42:09 | stephenfin | yeah, there's been a lot of that /o\ | |
| 14:42:12 | gtema | I guess tenant_id/project_id is not a big deal at all | |
| 14:42:45 | gtema | wrt this mentioned renaming I am currently thinking to return DictColumn instead of this renaming | |
| 14:43:10 | gtema | I do not think it is really useful to do this renaming, especially that it requires hacking | |
| 14:43:28 | gtema | what do you think? | |
| 14:43:36 | gtema | I agree this is a "breaking" change | |
| 14:44:04 | gtema | but we anyway plan to bump a major release after this rework is done | |
| 14:44:04 | stephenfin | no issues from me | |
| 14:44:15 | gtema | okay, great | |
| 14:44:17 | stephenfin | so long as we signal it with a major version bump, yes | |
| 14:44:28 | gtema | I hope OSC part will arrive today | |
| 14:44:53 | amotoki | from POV of consumers, it would be nice if both of project_id and tenant_id can be used transparently. | |
| 14:45:18 | gtema | I guess since very long time those are everywhere translated to project_id | |
| 14:45:19 | amotoki | I am not sure what part is discussed, nova API interaction or SDK abstraction? | |
| 14:45:48 | gtema | well - more about switching OSC to use SDK for nova part | |
| 14:46:22 | gtema | on the other hand stephenfin has also some UX improvents in head while we touch those | |
| 14:47:09 | gtema | stephenfin - do you have ideas in which order we should touch remaining things? | |
| 14:47:20 | gtema | I was thinking to leave server to be last | |
| 14:47:23 | gtema | since it is huge | |
| 14:47:40 | gtema | but might be better other way around | |
| 14:47:41 | stephenfin | No ideas, no. Whatever suits, really | |
| 14:47:56 | stephenfin | I'm planning to continue closing gaps with OSC and novaclient | |
| 14:48:15 | gtema | okay. For server I will be definitely create smaller patches switching individual commands of the server or server action | |
| 14:48:33 | gtema | since otherwise we will immediately get into some sort of long lock | |
| 14:49:12 | stephenfin | Makes sense | |
| 14:49:32 | stephenfin | I'll keep using the novaclient library to implement the CLIs until the necessary SDK bits are there to switch over | |
| 14:49:42 | gtema | ok | |
| 14:49:55 | stephenfin | because I don't yet understand SDK well enough /o\ | |
| 14:50:22 | gtema | I am not sure what is really better - do switch first and extend, or first extend and then switch to SDK | |
| 14:50:37 | gtema | SDK is a voodoo thanks to mordred ;-) | |
| 14:51:02 | stephenfin | extend and switch means we have a known baseline | |
| 14:51:10 | gtema | there are just few persons around the world probably who completely understand SDK | |
| 14:51:31 | gtema | agree on that, but | |
| 14:51:35 | stephenfin | i.e. I know novaclient works. I don't necessarily know new OSC changes works | |
| 14:51:53 | stephenfin | also, I'm adding missing options more so than missing commands | |
| 14:51:57 | gtema | before the switch I go to SDK and verify it can do everything what API provides | |
| 14:52:35 | gtema | so SDK should be supporting everything for OSC to be able to implement missing params | |
| 14:53:05 | gtema | okay | |
| 14:53:28 | gtema | diablo_rojo - do you have students already you were mentioning in PTG? | |
| 14:53:36 | gtema | the ones who can support this work | |
| 14:54:02 | diablo_rojo | Still working on the one from OSU. | |
| 14:54:17 | diablo_rojo | But the BU students are already working with gouthamr | |
| 14:54:32 | gtema | okay | |
| 14:55:06 | diablo_rojo | I just got the email calling for projects for NDSU students in the spring so I will start working on putting that together tomorrow probably. | |
| 14:55:20 | gtema | great | |
| 14:55:45 | gtema | I think we would be in time with the switch for nova command toward SDK this cycle - we are maybe 40% through currently | |
| 14:56:22 | gtema | maybe we can also start doing that for cinder as well, since I have a feeling those are now also a bit unhappy with OSC functionality | |
| 14:56:22 | openstackgerrit | Stephen Finucane proposed openstack/python-openstackclient master: Make use of comparable 'FormattableColumn' subclasses https://review.opendev.org/761447 | |
| 14:56:23 | openstackgerrit | Stephen Finucane proposed openstack/python-openstackclient master: compute: Fix 'server * -f yaml' output https://review.opendev.org/761205 | |
| 14:56:23 | openstackgerrit | Stephen Finucane proposed openstack/python-openstackclient master: compute: Fix 'usage * -f yaml' output https://review.opendev.org/761595 | |
| 14:56:24 | openstackgerrit | Stephen Finucane proposed openstack/python-openstackclient master: compute: Fix 'server group * -f yaml' output https://review.opendev.org/761596 | |
| 14:56:24 | openstackgerrit | Stephen Finucane proposed openstack/python-openstackclient master: compute: Fix 'hypervisor show -f yaml' output https://review.opendev.org/763004 | |
| 14:56:25 | openstackgerrit | Stephen Finucane proposed openstack/python-openstackclient master: compute: Add 'server group create --rule' option https://review.opendev.org/761597 | |
| 14:56:25 | openstackgerrit | Stephen Finucane proposed openstack/python-openstackclient master: compute: Add 'server show --topology' option https://review.opendev.org/680928 | |
| 14:56:26 | openstackgerrit | Stephen Finucane proposed openstack/python-openstackclient master: trivial: Use plural for appended parameters https://review.opendev.org/761598 | |
| 14:56:48 | gtema | come on stephenfin - you want you work to be logged in the meeting minutes ;-)? | |
| 14:56:57 | diablo_rojo | gtema, stephenfin if you want me to make the NDSU proposal geared toward Nova work I can do that, but I will need your help with the mentoring :) | |
| 14:57:20 | stephenfin | gtema: Gerrit reviews wait for no meeting :) | |
| 14:57:31 | gtema | :D | |
| 14:57:38 | gtema | oh yes, mentoring | |
| 14:57:50 | amotoki | hehe. it might be a good trick to raise your reviews :) | |
| 14:58:09 | gtema | I guess in next couple of month this might be hard with the time for real mentoring | |
| 14:58:10 | stephenfin | diablo_rojo: That's interesting and maybe possible, but I'd need to run it by folks internally first | |
| 14:58:35 | gtema | no problem explaining/onboarding, but not really deeper mentoring | |
| 14:59:15 | gtema | okay, let's see how it evolves | |
| 14:59:18 | diablo_rojo | stephenfin, I think I have till the 30th to put together the project proposal, but I can get an extension if need be (I have in the past). | |
| 15:00:26 | stephenfin | okay, I'll run it by people and see what they think. Should have an answer by EOW | |
| 15:00:41 | diablo_rojo | In the past is been 3-4 students for a semester and I usually met with them once a week for an hour. | |
| 15:00:47 | diablo_rojo | Perfect :) | |
| 15:01:09 | gtema | if we get students we can actually also run in parallel work for cinder part, and not really nova | |
| 15:01:39 | gtema | then we have 200% output in the cycle | |
| 15:02:13 | stephenfin | Sounds good | |
| 15:02:18 | stephenfin | gtema: I think we're at time? | |
| 15:02:24 | diablo_rojo | Good meeting :) | |
| 15:02:25 | gtema | yes, right | |
| 15:02:34 | diablo_rojo | Over by a couple min. | |
| 15:02:34 | gtema | sorry, long thinking | |
| 15:02:42 | diablo_rojo | gtema, no worries :) | |
| 15:02:47 | diablo_rojo | Thanks for hosting! | |
| 15:02:48 | gtema | any questions unanswered? | |
| 15:03:09 | gtema | #endmeeting | |
| 15:03:11 | openstack | Meeting ended Thu Nov 19 15:03:09 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 15:03:12 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/sdk_osc/2020/sdk_osc.2020-11-19-14.02.html | |
| 15:03:13 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/sdk_osc/2020/sdk_osc.2020-11-19-14.02.txt | |
| 15:03:14 | amotoki | thanks all. it is really a nice time to sync our efforts :) | |
| 15:03:15 | openstack | Log: http://eavesdrop.openstack.org/meetings/sdk_osc/2020/sdk_osc.2020-11-19-14.02.log.html | |
| 15:03:23 | gtema | great | |
| 15:03:31 | gtema | thanks everybody for joining | |
| 15:04:10 | gtema | have a nice day/evening/night or whatever else you have now | |
| 15:46:14 | dtantsur | gtema: do we have a calendar file for this meeting. I think I've just learned about it :) | |
| 15:53:06 | gtema | uhm, it's every 3rd thursday of the month | |