03:04:04 #startmeeting openstack-cyborg 03:04:05 Meeting started Thu Jul 16 03:04:04 2020 UTC and is due to finish in 60 minutes. The chair is Yumeng. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:04:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:04:08 The meeting name has been set to 'openstack_cyborg' 03:04:13 #topic Roll call 03:04:17 #info Yumeng 03:04:21 #info s_shogo 03:04:34 #info brinzhang 03:04:42 #topic Agenda 03:04:43 https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda 03:05:45 s_shogo: can you pls reply the comments or update Programming support https://review.opendev.org/#/c/698190/ ? 03:06:33 Yumeng: do we have the details docs for device compatibility interface by Chinese? or put together http://lists.openstack.org/pipermail/openstack-discuss/2020-July/015902.html 03:06:50 policy refresh is ready to review :https://review.opendev.org/#/c/740542/ still have some tempest error, I will fix them. 03:07:22 I seem missed something with this topic, hope can get catch up that 03:07:24 brinzhang: yes, I see this mail. 03:07:29 Yumeng OK, I'm working with the patch, test issue related to RabbitMQ, and will update that > 698190There are no big issue aside that. 03:08:07 but we have not any Chinese docs about this. 03:08:23 Hi all 03:08:24 Yumeng: xinranwang or shaohe_feng, may have give more help 03:08:35 this seems useful for supporting live migration with accelerators. 03:08:43 Hi all. 03:08:53 brinzhang:yes, I will sync with them 03:09:04 hi swp20,xinranwang__ 03:09:30 I didn't calm down to see this ML, so I want to know more, I think it would be better if there is Chinese material. 03:09:42 hi xinranwang__, swp20^ 03:10:25 We need to keep an eye on this maillist, in case there's some work can be done in cyborg. 03:11:30 xinranwang__: yes! exactly. 03:12:26 I will dig more and try to reply to ML to check things for cyborg. 03:13:04 and next review will be on the specs review. 03:13:21 xinranwang__: ok, later, will seen into 03:15:05 Inspur FPGA DRIVER: https://review.opendev.org/#/c/730760/ no big issue for me, just clarify some needed info will make sense to me. 03:15:22 As my understanding, it is an initial design discussion, anyway, we can have a look :) 03:15:34 Yumeng, i will check your review soon. 03:15:59 Yumeng, what's the use of project_id in arq, should we fill it by instance project_id? Pls see the patch:https://review.opendev.org/#/c/738427/ 03:16:10 xinranwang__: yes, looks like an initial design thought for device migration 03:16:33 xinranwang__: I saw this ML sent by intel, you dont know him? 03:16:58 project_id in arq is necessary, for example it can be used for policy check 03:17:09 I didn't know him before. maybe shaohe's working with them 03:17:56 yeah, shaohe is missing this meetting 03:19:21 btw, just update QAT spec, comments are welcomed. Please check it. 03:19:34 https://review.opendev.org/#/dashboard/self 03:19:41 sorry, wrong link 03:19:41 swp20: oh. sounds amazing. how did we pass the unittests without project_id in arq.... 03:19:50 https://review.opendev.org/#/c/728014/ 03:21:01 xinranwang__: cool. just saw the update. will review again.^ 03:21:15 lol 03:22:53 ok. I nothing more important than review to mention today. 03:23:00 I have 03:23:29 Yumeng , should we add api for cleaning devices as there may be some inconsistent data in db? 03:23:30 Yumeng, swp20: the project_id in some interface is make sense, agree to add 03:24:37 can you share more info? what's the inconsistent data in db? 03:24:51 brinzhang: ok, i will fix the tempest for the project_idpatch. 03:25:19 swap20: cool, thanks 03:25:48 swp20: but not in a hurry. you can also ping me in wechat once convenient. 03:25:50 Yumeng, such as we discuss at PTG, Cyborg db data is inconsistent with Placement db 03:26:00 aha. 03:27:19 or maybe device table is inconsistent with deployables/attributes adn so on.. 03:28:32 cool. i will contact with u in wechat. 03:28:34 from my understanding, if the goal is to solve the inconsistent data in db, it doesn't need to add an api, maybe just some data check, and cleaning by involing current API will make sense 03:28:55 involking 03:29:49 anyway, that's a case to case thing. we might need to discuss more details to decide if we need an API 03:30:11 let's continue in wechat.:) 03:30:12 ok, got it. thanks. 03:30:37 so that's all for today. Thank you guys! 03:30:45 let's wrap up thisĀ meetingĀ and I'll see you all again next week. 03:30:51 Bye. 03:30:58 #endmeeting