| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2020-11-19 | |||
| 14:03:09 | stephenfin | o/ | |
| 14:03:18 | gtema | ping gouthamr | |
| 14:03:38 | gouthamr | o/ | |
| 14:03:47 | gtema | do we want to use meetpad for voice meeting, or due to the time differences better in text ;-) | |
| 14:04:56 | gtema | no opinions? | |
| 14:05:47 | gtema | agenda for the meeting is under https://etherpad.opendev.org/p/openstacksdk-meeting-agenda | |
| 14:05:49 | amotoki | I have no strong preference on it, but most openstack projects use irc meetings and text meeting would be preferred in general. | |
| 14:05:59 | gtema | no problem | |
| 14:06:00 | diablo_rojo | Please just text lol | |
| 14:06:09 | gtema | oki, was thinking | |
| 14:06:27 | gtema | #topic Add Resolution of TC stance on the OpenStackClient Patch | |
| 14:06:35 | diablo_rojo | This way we have logs and don't need to take notes. | |
| 14:06:54 | gtema | I left my +1 (yet again) | |
| 14:07:20 | gtema | I am (not actually really wondering) - even this way there is some resistance from the community | |
| 14:08:08 | gtema | what is the plan of TC, to push on it or still try to get agreement from everyone | |
| 14:08:09 | gtema | ? | |
| 14:08:17 | gtema | https://review.opendev.org/#/c/759904/ | |
| 14:08:29 | diablo_rojo | We are trying to get that merged as a way forward. | |
| 14:08:48 | diablo_rojo | I do think its close, people just want more detail than we originally wanted to provide. | |
| 14:09:17 | gtema | this is already expressed very "weak". Is there a plan to really have a harder control? | |
| 14:10:53 | gtema | ok, moving next, since there is actually no further action points | |
| 14:10:57 | gtema | #topic Gerrit Breach Audit | |
| 14:11:31 | gtema | I did audit immediately when it was announced, but most likely forgot to send info about that | |
| 14:11:46 | diablo_rojo | the resolution is more of a stepping stone towards the end goal. A diplomatic way of starting to make progress. | |
| 14:11:50 | gtema | I have updated the linked etherpad with the info as well | |
| 14:11:54 | diablo_rojo | Oh cool, so all good then? | |
| 14:11:56 | diablo_rojo | Perfect. | |
| 14:12:00 | diablo_rojo | Thanks gtema! | |
| 14:12:04 | gtema | welcome | |
| 14:12:30 | stephenfin | gtema: You mean force patches for OSC? Not beyond the TC proposal, no. We need to rely on soft power more than hard power. It's not possible to force things through without the approval of the team, so we need to work to win those people over | |
| 14:12:31 | amotoki | gtema: did you audit all repos under openstacksdk? | |
| 14:12:38 | gtema | I reviewed both from gerrit side and from the attached commits. But due to the amount of projects under the SDK team ;-) I might have missed something | |
| 14:12:56 | gtema | sdk, python-openstackclient, openstackclient, os-service-types | |
| 14:13:05 | gtema | cliff, osc-lib | |
| 14:13:06 | stephenfin | fwiw, I think only Glance have pushed back. Everyone else is onboard, though not everyone has allocated resources (my nova is purely spare time stuff) | |
| 14:13:19 | amotoki | gtema: https://governance.openstack.org/tc/reference/projects/openstacksdk.html#deliverables lists our repos | |
| 14:13:45 | gtema | oh yes. shade as well | |
| 14:13:53 | stephenfin | tja | |
| 14:14:00 | stephenfin | *that's effectively EOL though | |
| 14:14:04 | gtema | will again ensure requestsexceptions and js-openstack-lib are covered | |
| 14:14:18 | gtema | tja - sounds so "german" | |
| 14:14:45 | gtema | don't tell me you are located in germany :) | |
| 14:15:37 | gtema | #topic Manila SDK work in Wallaby | |
| 14:16:02 | gtema | as mentioned - I think we generally need to start merging Manila bits into SDK | |
| 14:16:05 | gouthamr | hey! this was me. i had an update to share, and a couple of questions | |
| 14:16:26 | gtema | I know from own experience it is extremely hard to both add new services (complete) | |
| 14:16:33 | gtema | and also reviewing is terrible | |
| 14:16:50 | gtema | thus suggestion - get small things with resource by resource | |
| 14:17:10 | gouthamr | i agree, i saw your comment on | |
| 14:17:19 | gouthamr | #link https://review.opendev.org/#/c/638782/ (WIP: Add support for shared file systems (manila)) | |
| 14:17:45 | gouthamr | we'll break the patch down into individual resources | |
| 14:17:57 | gtema | I would suggest you have a look yourself whether what is already there is working or not | |
| 14:18:10 | gtema | if yes - remove WIP status and let the reviews start | |
| 14:18:33 | stephenfin | gouthamr: Are you planning to work on OSC integration in parallel? | |
| 14:18:45 | gouthamr | yeah, the WIP never fell off of it, because the original author has moved on; and we're trying to pick up the work this cycle | |
| 14:18:53 | gtema | he - interesting question, since manila has own client | |
| 14:19:08 | amotoki | gtema: will the OSC integration be implemented as a plugin, right? | |
| 14:19:23 | gtema | afaik it is already a plugin | |
| 14:19:24 | amotoki | no gtema. i would like to mention gouthamr | |
| 14:19:32 | gouthamr | stephenfin: yes, the OSC work is ongoing - we've about 50% parity with the python-manilaclient | |
| 14:19:35 | gtema | https://opendev.org/openstack/python-manilaclient | |
| 14:19:50 | gouthamr | and yes, the native client houses the plugin ^ | |
| 14:19:59 | amotoki | thanks. it is nice | |
| 14:20:24 | stephenfin | gouthamr: okay, good to hear :) | |
| 14:20:52 | gtema | I guess once the SDK part lands they can start consuming it to hopefully generally reduce efforts | |
| 14:21:16 | gouthamr | +1 | |
| 14:21:36 | gouthamr | great, my update is that we're working with a few new university contributors to submit the openstacksdk bits | |
| 14:21:37 | gtema | I see manila is really evolving on the API part | |
| 14:21:58 | gouthamr | hopefully, i'll have them here in the next meeting :) | |
| 14:22:00 | gtema | are there lots of changes planned for this cycle? | |
| 14:22:53 | gouthamr | gtema: yes, we do hope to finish the openstacksdk by X, so much of the user facing resources you see in https://review.opendev.org/#/c/638782/ are planned for wallaby | |
| 14:23:22 | gtema | I mean on manila itself | |
| 14:23:41 | gtema | when the change was initially started I know it was pretty close to cover all APIs | |
| 14:23:47 | gouthamr | i don't anticipate changes in manila, wdym? | |
| 14:23:51 | gtema | but since then lots of new APIs were added | |
| 14:23:56 | gouthamr | oh | |
| 14:24:09 | gtema | okay, I thought you might be knowing | |
| 14:24:11 | gouthamr | that'll not stop happening though :) | |
| 14:24:36 | gtema | okay then | |
| 14:24:39 | gtema | moving on | |
| 14:24:41 | amotoki | do we need functional test coverage in SDK in addition to unit test? it can be the next step though. | |
| 14:25:16 | gtema | I think better to add those as well, but no objections of doing this in a follow-up | |
| 14:25:24 | stephenfin | if we're doing functional tests, we need to think about how we do so | |
| 14:25:31 | gtema | tests are taking sometimes 70% of the change itself | |
| 14:25:31 | stephenfin | the functional tests in OSC are _very_ racy | |
| 14:25:52 | gtema | that's absolutely correct stephenfin | |
| 14:26:06 | gtema | mostly those racy tests are coming from nova ;-) | |
| 14:26:16 | stephenfin | unfortunately so :( | |
| 14:26:43 | gtema | for sure we would need to start using more projects not to really corrupt things | |
| 14:26:55 | stephenfin | yup | |
| 14:27:11 | stephenfin | work for the future though, once we've more gaps closed | |
| 14:27:37 | gtema | oki | |
| 14:27:45 | gouthamr | i had a couple of other questions | |
| 14:27:51 | gouthamr | and gtema answered one of them in the etherpad | |
| 14:28:18 | gtema | the remaining is about tracking, right? | |
| 14:28:27 | gouthamr | does openstacksdk work need a spec? we intend to write one to plan our work | |
| 14:28:42 | gtema | we do not use specs currenlty | |
| 14:28:45 | gouthamr | ah | |
| 14:28:57 | gtema | I do not know whether those were ever used in SDK/OSC | |
| 14:29:21 | amotoki | I don't think we need a spec. what we need is just to be aware of the effort as impls would be straight-forward. | |