15:00:05 #startmeeting openstack-cyborg 15:00:06 Meeting started Wed Jan 24 15:00:05 2018 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:10 The meeting name has been set to 'openstack_cyborg' 15:00:24 #topic Roll Call 15:00:41 \o 15:00:48 #info Howard 15:01:40 #info Rushil 15:01:50 #info Li Liu 15:03:02 let's wait for a few minutes for others to show up 15:05:59 guys if you are here for the meeting 15:06:09 please use #info to identify yourself 15:06:33 #info helloway 15:06:55 #info Dutch 15:07:20 #info amol 15:07:47 #info Vipparthy 15:07:59 Amol which company are you from ? 15:09:51 Hi Zhipeng . I am from nvxltech 15:10:16 ah thx, same with Vipparthy right ? 15:10:25 Yup 15:11:54 cool :) 15:12:10 Ok I see Intel folks flowing in, let's start the discussion 15:12:21 #topic Queens Release Final Push 15:13:00 Hi 15:13:38 #info Generic Driver 15:13:43 #link https://review.openstack.org/525057 15:13:58 hello all 15:14:01 crushil have you look at the comments from shaohe_feng_ and others ? 15:15:06 zhipeng, yup. I'm working on the patch rn. Will push a new patchset by this week 15:15:46 I have to cut the release branch Monday next week, so the window is pretty tight :) 15:16:15 I will need your workflow+1 during the weekend crushil :P 15:16:32 Hmmm. Ok 15:16:43 I will be online on the weekend 15:16:47 This is the final frenzy kicks in 15:16:52 gr8t thx :) 15:16:57 okey moving on 15:17:07 #info Intel FPGA driver 15:17:19 #link https://review.openstack.org/531129 15:17:54 Li_Liu has shaohe_feng_ addressed your comments ? 15:18:57 I havn't had the chance to look at the new patch yet 15:19:05 Doing it now 15:19:22 okey 15:19:46 shaohe_feng_ other than the comments you received, code-wise is your patch ready ? 15:19:52 I can also add some input to help keep things vendor neutral 15:20:05 Dutch absolutely 15:20:39 zhipeng: I have test it on our platform, it can works. 15:21:06 zhipeng: but maybe we still need to introduce rootwraper 15:21:07 okey then here are my suggestions: 15:21:27 no rootwrapper for queens :) 15:21:33 we need to discuss that in Dublin 15:21:47 So here are my suggestions at the patch : 15:22:02 the program need root for both intel and xilinx 15:22:05 again due to the tight release window, we will have to land this patch this weekend 15:22:17 Li_Liu, Dutch: current implementation in fpga/intel is specific to intel FPGA, for Xilinx, we may need to create a directory of fpga/Xilinx 15:22:44 dolpher, I agree 15:22:44 as I understand the comments are mostly on vendor neutral, as dolpher just mentioned 15:23:00 we need to make the interface generic in the end. 15:23:06 so I would suggest to change the patch accordingly to reflect that this is an Intel FPGA driver 15:23:15 only issue I have is in cyborg/accelerator/drivers/fpga/util.py 15:23:26 and let's try to harmonize it in the long run 15:23:40 poor gerrit 15:24:22 gerrit need rest :) 15:25:27 anyway, shaohe_feng_ you captured my suggestion ? 15:26:14 yes 15:26:24 great :) 15:26:29 next item 15:26:45 #info Justin leftovers: conductor interaction with Placement 15:26:51 not sure if zhuli is here 15:27:32 but as I have discussed with zhuli and Li_Liu offline previously, we will need to quick modify and copy-paste of nova-sched report.py 15:28:00 and also an extension at the agent level to implement the discover function in full 15:28:22 This is also another big hole we need to fix in a short time 15:28:36 shaohe_feng_ can your team help on the agent side ? 15:29:07 what we need is an equal counterpart of "resource_tracker.py" in cyborg 15:29:19 OK 15:29:32 which I assume is the discover interface that is very basic at the moment 15:29:57 yes. 15:30:33 okey thx :) zhuli and Li_Liu will coordinate on the conductor side 15:30:38 moving on 15:30:40 sure 15:30:44 #info fix on devstack 15:31:10 resource_tracker.py will check resource periodically 15:32:12 shaohe_feng_ we can simplify that for queens 15:32:23 and write to db instead of a provider-tree like cache 15:32:33 but anyways, back to the topic 15:32:43 #link https://review.openstack.org/536251 15:32:56 another good patch from Jinghan to make devstack working 15:33:16 crushil if you thinks it ok you could just land it :) 15:34:55 zhipeng, Ok. Will look at it later today 15:35:15 gr8t thx :) 15:35:50 okey folks that is all we need to do for Queens, I see Nova is still panicking on landing patches, so we are not alone :) 15:36:05 let's try to wrap it up before next Mon 15:36:18 :) 15:36:49 release is always driving people insane 15:37:53 #action crushil to update the generic driver patch, and work with Howard to land all the remaining patches 15:38:21 I thought the release data was feb 4th? 15:38:24 #action shaohe_feng_ to update the patch to reflect the patch is Intel FPGA driver 15:38:44 crushil that is like hard cutof, we have to run through the CIs and other stuff 15:38:47 docs ... 15:38:53 Hmmm 15:39:08 so I left out a week of time for more panicking stuff lol 15:39:11 Ok, so are we cutting RC1, RC2, etc. 15:39:12 ? 15:39:18 not for this release 15:39:22 Ok 15:39:29 We need to start doing that from Rocky 15:39:30 but for Rocky we are gonna use the MS1,MS2,... 15:39:37 Ok, makes sense 15:39:42 yes, so that things are not so in chaos 15:40:39 #action zhuli Li_Liu and shaohe_feng_ works on the Placement interaction patch (report and discovery) 15:41:09 I can help review all the patches 15:41:30 crushil counting on you man lol 15:41:55 okey now moving away from the crazy real world problem 15:42:07 #topic Dublin Rocky PTG Planning 15:42:30 zhipeng, I won't be there most probably 15:43:06 crushil waaaaat ! 15:43:12 #link https://etherpad.openstack.org/p/cyborg-ptg-rocky 15:43:29 zhipeng, Ya. We have MWC the same week 15:43:36 ah shit 15:43:44 forget about MWC 15:44:14 so Dutch Amol Vipparthy will you guys be present at Dublin ? 15:44:30 In case I can not work out the VISA.. do you guys have video conference in PTGs? 15:44:41 Li_Liu I could set that up 15:44:43 I'll see if I can make it 15:45:18 ok 15:45:50 so in any case, please propose the topic you would like to discuss on the etherpad 15:46:46 other than the specific topics 15:47:01 the important general topic we will cover is the planning for Rocky 15:47:29 and the items are 1. finishing up Nova interaction bits 2. Burn fucntionality 3. Quota support 15:47:44 these are the major general items I could think of for the next release 15:47:58 any other suggestions ? 15:49:30 does 15:50:17 cyborg support multi tenant? 15:51:02 shaohe_feng_ that questions should be divides in two 15:51:28 functionality wise, cyborg should definitely support multi-tenancy, hence the quota feature planning 15:51:55 but client wise, I haven't see strong use case for a tenant consuming client necessary for cyborg now 15:52:51 Howard, by "Burn Functionality", you mean program FPGA right? 15:54:55 Li_Liu yes 15:55:42 ok, if we don't have a proposal yet. I can submit a spec later next week or so 15:55:42 Would that be for the role (partial reconfig.) or the shell (static) region? 15:55:53 I think so Dutch 15:55:59 Li_Liu no hurry :) 15:56:22 Dutch would also need your input for Rocky cycle :) 15:56:40 to make the driver interface more vendor neutral 15:56:51 Yeah, no problem. I can help. 15:57:23 We could have the option to program both shell and role. 15:57:50 Any way something to think about 15:58:37 and feel free to post the idea on the etherpad 15:58:45 okey we had a full meeting today :) 15:58:50 #topic AoB 15:59:01 zhipeng leverage glance to store the image? 15:59:03 Zhipeng, Sorry for lte respone, I can help on Rocky planning 15:59:04 any other buisness before I cry to sleep ? 15:59:22 Vipparthy much appreciated ! :) 15:59:37 shaohe_feng_ yes definitely part of the discussion 15:59:52 glance should be the default choice 16:00:09 please update me with specifics so WE can take it from here 16:00:18 you can always reach me on my email 16:00:30 amvipparthy@gmail.com 16:02:22 we will usually update it via the community dev mailinglist 16:02:30 so also stay tuned on that :) 16:02:59 Sure 16:03:32 okey if there are no other questions, meetings adjourn , thanks everyone :) 16:03:35 #endmeeting