03:00:37 #startmeeting openstack-cyborg 03:00:37 Ok. thanks. I replied, in my opinion, that's not what this patch should do. I think the theme should be consistent. 03:00:37 Meeting started Thu Mar 12 03:00:37 2020 UTC and is due to finish in 60 minutes. The chair is Sundar. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:00:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:00:41 The meeting name has been set to 'openstack_cyborg' 03:00:57 o/ Sundar 03:01:03 #info chenke 03:01:19 Hi all 03:01:19 #info Yumeng 03:01:20 #info brinzhang 03:01:21 #info s_shogo 03:01:23 Hi all 03:01:25 #info xinranwang 03:02:14 First off, I am happy t o propose s_shogo and brinzhang as core reviewers: http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013230.html 03:03:17 It will take effect next Friday (March 20) barring any objection. 03:03:41 Sundar: It's my honor, thanks, thanks all 03:04:00 brinzhang: welcome, you have earned it. 03:04:03 Congratulations Brin, Shogo. 03:04:08 congrats! brinzhang,and s_shogo 03:04:14 Thanks all! 03:05:17 congratulations! 03:06:16 Thanks Sundar, chenke, Yumeng, xinranwang, s_shogo ^^ 03:06:28 Secondly, we should take stock of our progress in the U release. 03:07:34 Here's the U release planning etherpad: https://etherpad.openstack.org/p/cyborg-ptg-ussuri 03:08:04 Nova integration 03:08:31 Nova integration is making good progress, still hope to finish it by March. 03:09:09 Cyborg client: OpenStackSDK part is done. Hereafter it is incremental improvement, right? 03:09:31 s_shogo, all: ^ 03:11:37 Yes, I'll implement filter function and so on >> client 03:12:19 Would the client be mostly done by Ussuri? Or do you think it'll go to V release? 03:13:02 The SDK including cyborg part was released yesterday. Thus that could be released in U release,IMO. 03:13:44 ( SDK's release cycle is independent from OpenStack's one) 03:13:58 The reason I am asking is, the Cyborg client has been released midcycle. If most functionality is in, we could consider an end-of-cycle release instead of waiting for V. 03:15:04 client is based on v2 API, I think we don't have v2 deployable API now, right ? 03:15:17 OK I got it. Release in U could be chosen 03:15:41 Yes >> xinranwang 03:16:13 The SDK cannot match Cyborg API now? 03:17:10 brinzhang No, the Latest SDK supports many Cyborg API, but that is not perfect like xinranwang mentioned. 03:17:11 I know the v2 microversion in progress, if so, the SDK/cyborgclient maybe cannot works good, rirht? 03:18:01 s_shogo: Ok, later, while I am free, I will test in my evn ^^ 03:18:09 s_shogo: got it. 03:18:18 brinzhang thanks:) 03:18:24 brinzhang: yes, we should support microversion in client side too 03:18:57 brinzhang: The microversion support in the API server side means that the client must specific headers with the microversion number. That is probably the next big infrastructure in the client. Right, s_shogo? 03:19:08 xinranwang: necessary. in clinet we must support microversion to request the Cyborg api 03:19:11 *must send 03:19:42 brinzhang: yes, exactly 03:20:03 s_shogo: I installed cyborgclient by "pip install python-cyborgclient", is that ok by this way? 03:20:37 Yes >>Sundar , xinranwang and me start to investigate a method of supporting them with sdk's functions. 03:20:56 Great. Thanks, s_shogo 03:21:02 xinranwang: Support for deployables in the client is an incremental feature. That brings me to the 2nd item above. /v2/devices API for inventory is done. But /v2/deployables for programming is open. 03:21:42 s_shogo: we should add --os-cyborg-api-version in your client implemation 03:21:58 So, our top 3 priorities for U are still the same as above: Nova integration 03:22:15 The last one includes microversion support. 03:22:29 Sundar: yes, device API is done except upgrade firmware, and deployable v2 is missing 03:23:42 brinzhang Sorry , recently I don't have test the "pip install python-cyborg client" , so I'll test that. I've checked "pip install openstacksdk" includes Cyborg part , yesterday. 03:24:51 s_shogo: ok, hoping get your feedback 03:25:35 s_shogo: so , for now we should install from source code, right? 03:26:33 Yumeng That is certain way, now. 03:26:43 Yumeng: I think pip install is ok, but I think s_shogo should check whether it works fine for all cli 03:27:14 s_shogo: Alright. got it. 03:27:45 I'll check the latest pip status and report that. 03:28:23 great.! thanks 03:28:52 great] 03:30:13 So, our top 3 priorities for U are still the same as above: Nova integration 03:30:24 All agree? 03:30:53 how about default policy refresh? 03:30:58 what is the other 2? 03:31:36 nova-cyborg-interaction, v2 microversion, policy-default-refresh? 03:32:07 brinzhang: Policy refresh is important. I suppose we should add that as 4th 03:32:15 I think completing v2 API is also important 03:32:34 I think anther is SDK/cyborgclient 03:32:44 xinranwang: Other 2 are: Add /v2/devices API for inventory and /v2/deployables for programming 03:33:01 As i said above, and also in Ussuri etherpad 03:33:20 We should add policy refresh because that is important for security. 03:33:47 Activities like improving UT are important too. However, when we publish our cycle highlights, it is usually features 03:34:20 what about microversion, the spec is already merged. 03:34:41 and it is listed in etherpad too. 03:35:07 I think s_shogo is working on other v2 APIs 03:35:19 I effectively included that in the API enhancements above. Adding/changing APIs requires microversion support. 03:35:48 May be I should make it explicit. 03:36:00 I'm working on "programming in deployable" and "enable/disable in device" 03:36:03 policy-default-refresh is based on v2 API. maybe not enough time for all APIs to be implemented in U. but we can implement some, I mean, at least one sample API policy check. 03:36:39 And its spec has been merged. 03:37:24 s_shogo: Oh, do you want me to help on list/show APIs, or you will do it together? I think we can just implement them based on v1 code 03:38:55 Let me restate the priorities like this: Nova integration 03:38:56 xinranwang oh,Thanks! could you implement them is OK? > list/show APIs. Now, I'm simply copy them from v1 code in my env. 03:39:56 s_shogo: I think we just need adapt v1 code to v2 model ;) 03:40:35 I can help on that if needed 03:41:54 xinranwang: May I ask your help that? It may be simple. 03:42:21 s_shogo: sure, I am willing to help. 03:44:16 Thanks , xinranwang 03:44:23 Great. Anything else, folks? 03:45:00 yes, please review microversion patch if you got time 03:45:05 Thanks all 03:45:20 #topic AoB 03:45:51 xinrnwang: Do you need review from outside, like from cdent or Nova folks? 03:46:18 I think we can start review internally 03:46:32 because cyborg use pecan which is different from nova 03:47:23 ok 03:47:32 Anything else? 03:47:38 me 03:48:19 Yes, brinzhang? 03:48:25 I would like to improve the cyborg docs, such as the https://docs.openstack.org/cyborg/latest/ 03:49:00 Many mainly links mostly hard to found, such as the api reference 03:49:47 I think many people cannot remember the all links, so I would like to make it perfect 03:49:52 https://review.opendev.org/#/c/711869/ 03:50:41 I mainly add the api reference here, if there are anything else that I missing, please point and leave comments 03:51:30 Maybe we should have some blueprint, story or doc that describes all the doc changes needed? if we do it one at a time, it may get confusing or we may miss something. 03:52:16 blueprint, story links maybe should in README 03:52:48 of course, maybe we should add a document about how to contribute to Cyborg such as nova 03:53:15 like this one: https://review.opendev.org/#/c/712420/1/doc/source/contributor/contributing.rst 03:54:04 but looks like Cyborg doesnot have these thing need to be record 03:54:38 suggestion step by step to do, after all, we lack so many docs 03:55:07 Could we resume this discussion next week? I need to leave a bit early today. 03:55:36 yeah, nothing else ^^ 03:56:12 Added this to next week's agenda: https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda 03:56:14 Thanks 03:56:53 Thanks a lot, everybody. Good progress so far in U. Let's keep it up! Have a good day. 03:56:57 #endmeeting