Thursday, 2020-08-27

*** brinzhang_ has joined #openstack-cyborg00:32
*** brinzhang0 has quit IRC00:36
*** brinzhang_ has quit IRC01:31
*** brinzhang_ has joined #openstack-cyborg01:31
*** links has joined #openstack-cyborg02:29
*** efried has quit IRC02:57
*** Yumeng has joined #openstack-cyborg02:59
*** efried has joined #openstack-cyborg03:01
*** s_shogo has joined #openstack-cyborg03:02
Yumenghi xinranwang__, s_shogo  swp20 brinzhang_03:05
brinzhang_hi Yumeng03:05
swp20hi Yumeng03:05
xinranwang__Hi all03:05
*** chenke has joined #openstack-cyborg03:05
Yumenghi chenke03:06
s_shogoHi all03:06
chenkehi all03:06
swp20Hi all03:06
chenkehi yumeng. shogo.03:06
chenkehi wenping.03:06
chenkeI leave some comments on your patches.03:06
swp20yeah, i see.03:06
Yumengs_shogo: I asked haibin to join our meeting today. he will join soon. you guys can discuss Program API things :)03:07
swp20thanks chenke.03:07
s_shogoYumeng great!03:07
Yumengok. let's start03:07
Yumeng#startmeeting openstack-cyborg03:07
openstackMeeting started Thu Aug 27 03:07:58 2020 UTC and is due to finish in 60 minutes.  The chair is Yumeng. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:08
*** openstack changes topic to " (Meeting topic: openstack-cyborg)"03:08
openstackThe meeting name has been set to 'openstack_cyborg'03:08
Yumeng#topic Roll call03:08
*** openstack changes topic to "Roll call (Meeting topic: openstack-cyborg)"03:08
Yumeng#info Yumeng03:08
swp20#info swp2003:08
s_shogo#info s_shogo03:08
xinranwang__#info xinranwang__03:08
brinzhang_#info brinzhang_03:09
*** shaohe_feng has joined #openstack-cyborg03:09
Yumenghi shaohe_feng03:10
shaohe_fenghi all03:10
shaohe_fenghi Yumeng, morning03:10
Yumengcool, we have so many people today03:11
brinzhang_Hi all, we should have a aggrement of the tempary report result of the 3rd-party driver03:11
Yumeng#topic Agenda03:11
*** openstack changes topic to "Agenda (Meeting topic: openstack-cyborg)"03:11
Yumengbrinzhang_: yes, that's one of the topic I want to mention03:12
brinzhang_where to save the tempart results03:12
brinzhang_yeah ^^03:12
*** haibin-huang has joined #openstack-cyborg03:12
Yumengas discussed in Intel QAT driver patch:
brinzhang_I am ok with the qat driver patch, and the inspur fpga driver patch, just with the temparory reulst03:14
xinranwang__do we have a template wiki to show test result?03:14
brinzhang_xinranwant_: may we should have to create a tempate for this03:15
brinzhang_the etherpad is not save, because it can be modified by everyone03:16
xinranwang__IMO, the format of test result is not a big deal. Just to show the driver works.03:16
chenke#info chenke03:17
swp20xinranwang__: your format of test result is good enough.03:18
brinzhang_xinranwang_: not exactly all, we shoul keep the readable of the result, so the format shuold be beautiful ASAP03:18
Yumengxinranwang__: about the template, I'm fine with the structure of your report. I think that make sense to showt the report results and provision results03:19
xinranwang__I remember it was a website call, things like that.03:19
Yumengxinranwang__: just one small question,  we can add openstack accelerator device list to show the report result in cyborg side.03:19
xinranwang__does anyone know that website>03:19
brinzhang_xinranwang_: is also a temparory place too03:20
brinzhang_I am trend to use wiki03:21
xinranwang__brinzhang_:  does everyone can modify it?03:21
Yumengbrinzhang_, xinranwang__: I also have the concern that etherpad and are temparory. anyobe can modify it03:21
xinranwang__Yumeng: ok, sure03:21
brinzhang_xinranwang_: no, but it will be lost with a long time03:22
xinranwang__brinzhang_:  ok, got it.03:22
Yumengwe can create a wiki page to record the driver report result and then add the link to the driver-support table on doc page
xinranwang__It seems a wiki page is the better one03:23
Yumengwhat do you think?03:23
brinzhang_we can use wiki, but how do we let the user or operator know the result exist in wiki?03:23
xinranwang__We can mention this wiki page in cyborg doc03:23
brinzhang_agree, and we can add a column as "temparory result", marked when it merged03:24
shaohe_fengthe should add item to show the link03:24
Yumengyes, agree03:25
brinzhang_such as, Added it in Victoria (Auguest, 2020)03:25
Yumengyes, we can do that.03:26
brinzhang_and past the wiki test result link03:26
xinranwang__lol, like a biography for the driver03:26
Yumengyep =_<03:27
brinzhang_ok, let do it by this way, after meeting, I will send an email to the ML, that everyone should do, if they are not have the third-party CI03:27
Yumengbrinzhang_: cool.03:28
Yumengabout the driver implementation, I have another quesion to discuss03:28
Yumeng VENDOR_MAPS format of GPU,FPGA are different, should we keep consistent?03:29
YumengFPGA is like this
Yumengwhile GPU is like
swp20we can merge them in one dict.03:30
brinzhang_move this to a common file?03:31
xinranwang__Yumeng:  what do you mean by difference03:32
brinzhang_VENDER_MAPS = ['GPU': {'0x8086': 'intel', ..}, 'FPGA': {'','', ...}]03:32
brinzhang_how about like this? that we can maintain this in one place03:32
xinranwang__Just wondering why we should do this. Is there any gap in current implementation?03:34
brinzhang_not array, a dict. VENDER_MAPS = {'GPU': {'0x8086': 'intel', ..}, 'FPGA': {'','', ...}}03:34
brinzhang_xinranwang_: I am not sure what Yumeng want todo, but from the maintain accelerator devices type and vendor, that we can merge this, because we can easy to know what devices that we can support03:36
brinzhang_but as you said, is it make sense?  It make sense to me. ^03:37
Yumengxinranwang__: initially, this is a downstream problem I found in baremetal support.  ironic report Nvidia GPU vendor_id as hexadecimal int, while we accept vendor_id as string03:38
*** wangzhh has joined #openstack-cyborg03:38
xinranwang__brinzhang_: we can this to show all supported resources.03:38
Yumenghere by difference I mean '0x8086' and '10de'03:38
xinranwang__Yumeng:  ok, that's the problem.03:38
xinranwang__It comes from the discovery method. Intel drivers all discover devices from sysfs which contains the hex number.03:39
Yumengseems different,  I not yet look into the details.03:39
Yumengbut should we keep consistent, or just let this go and let any driver do their own way03:40
xinranwang__AFAIK, the gpu driver's result comes from lspci's output.03:40
swp20Inspur FPGA is '1db4' like GPU.03:41
swp20yeah also use lscpi command.03:41
xinranwang__So the problem is that if driver use lspci, the output is now in hex format. We may need to translate it.03:42
Yumengsounds good.03:42
Yumengwe can rethink it and make decision later. not in a hurry.03:43
xinranwang__Yes, we should leave some time to program api discussion.03:43
brinzhang_do we need to maintain a list for the supported device type? we know every product maybe need a driver03:44
YumengYES, We don't have much time left, I wanna leave some time for haibin-huang s_shogo, and  shaohe_feng to discuss Program API03:44
s_shogoyes, that's welcome >> Program API discussion03:45
haibin-huanghello shogo03:46
s_shogohello haibin-huang03:46
s_shogoIs ok to begin discussion about the program API?03:46
haibin-huangso, what is your question?03:48
s_shogohaibin-huang , shaohe, xinran : Let me confirm, what type FPGA do you use for the test of programming API?(N3000?)03:48
s_shogoIMHO, in my concern, to use N3000 with Cyborg, that needs suited driver for N3000 and async program algorithm for that, before trying programming API.03:48
haibin-huangyes, N300003:49
shaohe_fengwe need aysnc03:49
s_shogoOK,t I got it.03:51
s_shogoAs we discussed in previous IRC, I thinks that needs new driver and async, and that seems to be out of scope of this Program API patch..03:52
haibin-huangI think we should consider two points, one is reboot fpga, one is get program status03:52
s_shogoAre there any plan for modifying driver and cyborg mechanism for N3000?03:52
haibin-huangwe have implentation draft for it03:55
haibin-huangbut, we don't know when we can push is upstream03:55
haibin-huangthe Draft is not ready to push it upstream03:57
s_shogoOk, I got it.03:58
s_shogoSo that is better to be reviewed as the target.03:58
s_shogoOf course, the programming method for N3000 is important,that should be discussed as another patch and IRC.03:58
s_shogoI would like to settle out the program patch work as current scope, once.04:00
shaohe_fengOK, but can you add a new API for program status check, just add a UnimplemenationExcetpion(" unsport") ?04:01
shaohe_fengjust define the API04:01
shaohe_fengwe can add a the implementation later.04:02
s_shogoumm, to add a new API for program check is agree,04:03
shaohe_fengOK, thanks04:06
s_shogoThanks, shaohe-feng :)04:08
Yumengs_shogo,shaohe_feng:cool. since we don't have much time left for victoria, I think we should keep the scope of program API patch focused. and add other features later.04:09
s_shogoYumeng Thanks, I agree that.04:09
YumengThanks haibin-huang for coming to join the discussion.04:10
s_shogoThanks haibin-huang, shaohe-feng04:10
YumengThanks s_shogo and shaohe_feng, program API is not easy work.04:11
*** shaohe_feng has quit IRC04:11
Yumengtime is up for today. I will bring up the left topics(PTG things)  on wechat where necessary04:12
YumengThank you all for coming, and I'll see you all again next week04:13
*** openstack changes topic to "Pending patches (Meeting topic: openstack-cyborg)"04:13
openstackMeeting ended Thu Aug 27 04:13:39 2020 UTC.  Information about MeetBot at . (v 0.1.4)04:13
openstackMinutes (text):
*** s_shogo has quit IRC04:14
*** haibin-huang has quit IRC05:22
*** chenke has quit IRC06:11
openstackgerritYumengBao proposed openstack/cyborg master: keep GPU driver's deployable_name unique
*** brinzhang_ has quit IRC07:31
*** brinzhang_ has joined #openstack-cyborg07:32
*** brinzhang_ has quit IRC08:10
*** brinzhang_ has joined #openstack-cyborg08:11
openstackgerritMerged openstack/cyborg master: Optimize microversion support
openstackgerritWenping Song proposed openstack/cyborg master: Add instance project_id for arq patch
openstackgerritWenping Song proposed openstack/cyborg master: Add instance project_id for arq patch
openstackgerritXinran WANG proposed openstack/cyborg master: Add a new driver for Intel QAT card
openstackgerritXinran WANG proposed openstack/cyborg master: Add a new driver for Intel QAT card
openstackgerritXinran WANG proposed openstack/cyborg master: keep FPGA driver's deployable_name unique
*** wangzhh has quit IRC10:48
*** Yumeng has quit IRC11:07
*** efried has quit IRC11:45
*** efried has joined #openstack-cyborg13:23
*** links has quit IRC14:53
openstackgerritzhoulinhui proposed openstack/cyborg master: Remove all usage of six library
*** dustinc has quit IRC16:07
*** xinranwang__ has quit IRC17:54

Generated by 2.17.2 by Marius Gedminas - find it at!