| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2020-03-12 | |||
| 02:37:37 | brinzhang | If anyone can get this clearly, can push a commit that we can check together | |
| 02:37:50 | chenke | Sundar cool. The latest commit message is clear. | |
| 02:38:20 | openstackgerrit | YumengBao proposed openstack/cyborg master: Fix GPU's improper cpid_type allowed value and attach_handle_type value https://review.opendev.org/709433 | |
| 02:38:49 | openstackgerrit | YumengBao proposed openstack/cyborg master: Fix GPU's improper cpid_type allowed value and attach_handle_type value https://review.opendev.org/709433 | |
| 02:39:02 | brinzhang | Sundar, chenke, xinranwang, Yumeng, I want to start use launchpad, do you think all? | |
| 02:40:19 | Sundar | brinzhang: launchpad for blueprints? | |
| 02:40:39 | brinzhang | I think it's easier to manager bug,blueprint, as I know cinder,nova,neutron all use it | |
| 02:41:35 | Sundar | I have no objection either way. But we would need to migrate all stories in Storyboard to launchpad. | |
| 02:42:22 | brinzhang | Any tools can do? | |
| 02:49:23 | Sundar | brb in 10 min | |
| 02:51:29 | chenke | Didn't it have been discussed in the email before? According to the opinions of community leaders, cyborg has already used storyborad, so there is no need to change it back. I think storyborad is good. | |
| 02:57:51 | Sundar | back | |
| 02:59:31 | brinzhang | chenke: I removed -1 from that patch, but I think Sundar's concern is right, how about change the fpga_program_v2 to fpga_program in this patch? | |
| 03:00:37 | Sundar | #startmeeting openstack-cyborg | |
| 03:00:37 | chenke | 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 | openstack | 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 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 03:00:41 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 03:00:57 | Sundar | o/ Sundar | |
| 03:01:03 | chenke | #info chenke | |
| 03:01:19 | xinranwang | Hi all | |
| 03:01:19 | Yumeng | #info Yumeng | |
| 03:01:20 | brinzhang | #info brinzhang | |
| 03:01:21 | s_shogo | #info s_shogo | |
| 03:01:23 | s_shogo | Hi all | |
| 03:01:25 | xinranwang | #info xinranwang | |
| 03:02:14 | Sundar | 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 | Sundar | It will take effect next Friday (March 20) barring any objection. | |
| 03:03:41 | brinzhang | Sundar: It's my honor, thanks, thanks all | |
| 03:04:00 | Sundar | brinzhang: welcome, you have earned it. | |
| 03:04:03 | chenke | Congratulations Brin, Shogo. | |
| 03:04:08 | Yumeng | congrats! brinzhang,and s_shogo | |
| 03:04:14 | s_shogo | Thanks all! | |
| 03:05:17 | xinranwang | congratulations! | |
| 03:06:16 | brinzhang | Thanks Sundar, chenke, Yumeng, xinranwang, s_shogo ^^ | |
| 03:06:28 | Sundar | Secondly, we should take stock of our progress in the U release. | |
| 03:07:34 | Sundar | Here's the U release planning etherpad: https://etherpad.openstack.org/p/cyborg-ptg-ussuri | |
| 03:08:04 | Sundar | Nova integration | |
| 03:08:31 | Sundar | Nova integration is making good progress, still hope to finish it by March. | |
| 03:09:09 | Sundar | Cyborg client: OpenStackSDK part is done. Hereafter it is incremental improvement, right? | |
| 03:09:31 | Sundar | s_shogo, all: ^ | |
| 03:11:37 | s_shogo | Yes, I'll implement filter function and so on >> client | |
| 03:12:19 | Sundar | Would the client be mostly done by Ussuri? Or do you think it'll go to V release? | |
| 03:13:02 | s_shogo | The SDK including cyborg part was released yesterday. Thus that could be released in U release,IMO. | |
| 03:13:44 | s_shogo | ( SDK's release cycle is independent from OpenStack's one) | |
| 03:13:58 | Sundar | 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 | xinranwang | client is based on v2 API, I think we don't have v2 deployable API now, right ? | |
| 03:15:17 | s_shogo | OK I got it. Release in U could be chosen | |
| 03:15:41 | s_shogo | Yes >> xinranwang | |
| 03:16:13 | brinzhang | The SDK cannot match Cyborg API now? | |
| 03:17:10 | s_shogo | brinzhang No, the Latest SDK supports many Cyborg API, but that is not perfect like xinranwang mentioned. | |
| 03:17:11 | brinzhang | I know the v2 microversion in progress, if so, the SDK/cyborgclient maybe cannot works good, rirht? | |
| 03:18:01 | brinzhang | s_shogo: Ok, later, while I am free, I will test in my evn ^^ | |
| 03:18:09 | xinranwang | s_shogo: got it. | |
| 03:18:18 | s_shogo | brinzhang thanks:) | |
| 03:18:24 | xinranwang | brinzhang: yes, we should support microversion in client side too | |
| 03:18:57 | Sundar | 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 | brinzhang | xinranwang: necessary. in clinet we must support microversion to request the Cyborg api | |
| 03:19:11 | Sundar | *must send | |
| 03:19:42 | xinranwang | brinzhang: yes, exactly | |
| 03:20:03 | brinzhang | s_shogo: I installed cyborgclient by "pip install python-cyborgclient", is that ok by this way? | |
| 03:20:37 | s_shogo | Yes >>Sundar , xinranwang and me start to investigate a method of supporting them with sdk's functions. | |
| 03:20:56 | Sundar | Great. Thanks, s_shogo | |
| 03:21:02 | Sundar | 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 | brinzhang | s_shogo: we should add --os-cyborg-api-version <cyborg-api-ver> in your client implemation | |
| 03:21:58 | Sundar | So, our top 3 priorities for U are still the same as above: Nova integration | |
| 03:22:15 | Sundar | The last one includes microversion support. | |
| 03:22:29 | xinranwang | Sundar: yes, device API is done except upgrade firmware, and deployable v2 is missing | |
| 03:23:42 | s_shogo | 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 | brinzhang | s_shogo: ok, hoping get your feedback | |
| 03:25:35 | Yumeng | s_shogo: so , for now we should install from source code, right? | |
| 03:26:33 | s_shogo | Yumeng That is certain way, now. | |
| 03:26:42 | brinzhang | Yumeng: I think pip install is ok, but I think s_shogo should check whether it works fine for all cli | |
| 03:27:14 | Yumeng | s_shogo: Alright. got it. | |
| 03:27:45 | s_shogo | I'll check the latest pip status and report that. | |
| 03:28:23 | Yumeng | great.! thanks | |
| 03:28:52 | chenke | great] | |
| 03:30:13 | Sundar | So, our top 3 priorities for U are still the same as above: Nova integration | |
| 03:30:24 | Sundar | All agree? | |
| 03:30:53 | brinzhang | how about default policy refresh? | |
| 03:30:58 | xinranwang | what is the other 2? | |
| 03:31:36 | brinzhang | nova-cyborg-interaction, v2 microversion, policy-default-refresh? | |
| 03:32:07 | Sundar | brinzhang: Policy refresh is important. I suppose we should add that as 4th | |
| 03:32:15 | xinranwang | I think completing v2 API is also important | |
| 03:32:34 | brinzhang | I think anther is SDK/cyborgclient | |
| 03:32:44 | Sundar | xinranwang: Other 2 are: Add /v2/devices API for inventory and /v2/deployables for programming | |
| 03:33:01 | Sundar | As i said above, and also in Ussuri etherpad | |
| 03:33:20 | Sundar | We should add policy refresh because that is important for security. | |
| 03:33:47 | Sundar | Activities like improving UT are important too. However, when we publish our cycle highlights, it is usually features | |
| 03:34:20 | xinranwang | what about microversion, the spec is already merged. | |
| 03:34:41 | xinranwang | and it is listed in etherpad too. | |
| 03:35:07 | xinranwang | I think s_shogo is working on other v2 APIs | |
| 03:35:19 | Sundar | I effectively included that in the API enhancements above. Adding/changing APIs requires microversion support. | |
| 03:35:48 | Sundar | May be I should make it explicit. | |
| 03:36:00 | s_shogo | I'm working on "programming in deployable" and "enable/disable in device" | |
| 03:36:03 | Yumeng | 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 | Yumeng | And its spec has been merged. | |
| 03:37:24 | xinranwang | 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 | Sundar | Let me restate the priorities like this: Nova integration | |
| 03:38:56 | s_shogo | xinranwang oh,Thanks! could you implement them is OK? > list/show APIs. Now, I'm simply copy them from v1 code in my env. | |