Earlier  
Posted Nick Remark
#openstack-cyborg - 2018-01-17
16:13:14 zhipeng yes NokMikeR
16:13:22 NokMikeR Great :)
16:14:09 zhipeng okey meeting adjourned
16:14:13 zhipeng #endmeeting
16:14:15 openstack Meeting ended Wed Jan 17 16:14:13 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
16:14:16 openstack Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-01-17-15.03.html
16:14:17 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-01-17-15.03.txt
16:14:18 openstack Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-01-17-15.03.log.html
16:14:49 Vipparthy Thank you folks
16:14:56 NokMikeR Thanks all, bye
16:15:12 Dutch Thanks!
17:51:07 guhcampos Hi folks, a quick question: I may need to implement our driver for cyborg. Is there a way to write it as a plugin? Like a separate python package that can be installed alongside cyborg? Or do I have to add it to cyborg's tree alongside the generic driver?
17:54:46 crushil_ guhcampos, Add it to Cyborg's tree alongside the generic driver
17:55:28 guhcampos crushil_, thanks. I needed this confirmation to pressure management to sign the contributor agreement
#openstack-cyborg - 2018-01-24
14:55:03 Vipparthy GM and GE folks
14:59:43 zhipeng yo
14:59:55 zhipeng Vipparthy good day :)
15:00:05 zhipeng #startmeeting openstack-cyborg
15:00:06 openstack 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 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:10 openstack The meeting name has been set to 'openstack_cyborg'
15:00:24 zhipeng #topic Roll Call
15:00:41 crushil \o
15:00:48 zhipeng #info Howard
15:01:40 crushil #info Rushil
15:01:50 Li_Liu #info Li Liu
15:03:02 zhipeng let's wait for a few minutes for others to show up
15:05:59 zhipeng guys if you are here for the meeting
15:06:09 zhipeng please use #info to identify yourself
15:06:33 helloway #info helloway
15:06:55 Dutch #info Dutch
15:07:20 Amol #info amol
15:07:47 Vipparthy #info Vipparthy
15:07:59 zhipeng Amol which company are you from ?
15:09:51 Amol Hi Zhipeng . I am from nvxltech
15:10:16 zhipeng ah thx, same with Vipparthy right ?
15:10:25 Amol Yup
15:11:54 zhipeng cool :)
15:12:10 zhipeng Ok I see Intel folks flowing in, let's start the discussion
15:12:21 zhipeng #topic Queens Release Final Push
15:13:00 dolpher Hi
15:13:38 zhipeng #info Generic Driver
15:13:43 zhipeng #link https://review.openstack.org/525057
15:13:58 shaohe_feng_ hello all
15:14:01 zhipeng crushil have you look at the comments from shaohe_feng_ and others ?
15:15:06 crushil zhipeng, yup. I'm working on the patch rn. Will push a new patchset by this week
15:15:46 zhipeng I have to cut the release branch Monday next week, so the window is pretty tight :)
15:16:15 zhipeng I will need your workflow+1 during the weekend crushil :P
15:16:32 crushil Hmmm. Ok
15:16:43 crushil I will be online on the weekend
15:16:47 zhipeng This is the final frenzy kicks in
15:16:52 zhipeng gr8t thx :)
15:16:57 zhipeng okey moving on
15:17:07 zhipeng #info Intel FPGA driver
15:17:19 zhipeng #link https://review.openstack.org/531129
15:17:54 zhipeng Li_Liu has shaohe_feng_ addressed your comments ?
15:18:57 Li_Liu I havn't had the chance to look at the new patch yet
15:19:05 Li_Liu Doing it now
15:19:22 zhipeng okey
15:19:46 zhipeng shaohe_feng_ other than the comments you received, code-wise is your patch ready ?
15:19:52 Dutch I can also add some input to help keep things vendor neutral
15:20:05 zhipeng Dutch absolutely
15:20:39 shaohe_feng_ zhipeng: I have test it on our platform, it can works.
15:21:06 shaohe_feng_ zhipeng: but maybe we still need to introduce rootwraper
15:21:07 zhipeng okey then here are my suggestions:
15:21:27 zhipeng no rootwrapper for queens :)
15:21:33 zhipeng we need to discuss that in Dublin
15:21:47 zhipeng So here are my suggestions at the patch :
15:22:02 shaohe_feng_ the program need root for both intel and xilinx
15:22:05 zhipeng again due to the tight release window, we will have to land this patch this weekend
15:22:17 dolpher 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 zhipeng as I understand the comments are mostly on vendor neutral, as dolpher just mentioned
15:22:44 Li_Liu dolpher, I agree
15:23:00 dolpher we need to make the interface generic in the end.
15:23:06 zhipeng so I would suggest to change the patch accordingly to reflect that this is an Intel FPGA driver
15:23:15 Li_Liu only issue I have is in cyborg/accelerator/drivers/fpga/util.py
15:23:26 zhipeng and let's try to harmonize it in the long run
15:23:40 zhipeng poor gerrit
15:24:22 shaohe_feng_ gerrit need rest :)
15:25:27 zhipeng anyway, shaohe_feng_ you captured my suggestion ?
15:26:14 shaohe_feng_ yes
15:26:24 zhipeng great :)
15:26:29 zhipeng next item
15:26:45 zhipeng #info Justin leftovers: conductor interaction with Placement
15:26:51 zhipeng not sure if zhuli is here
15:27:32 zhipeng 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 zhipeng and also an extension at the agent level to implement the discover function in full
15:28:22 zhipeng This is also another big hole we need to fix in a short time
15:28:36 zhipeng shaohe_feng_ can your team help on the agent side ?
15:29:07 zhipeng what we need is an equal counterpart of "resource_tracker.py" in cyborg
15:29:19 shaohe_feng_ OK
15:29:32 zhipeng which I assume is the discover interface that is very basic at the moment
15:29:57 shaohe_feng_ yes.
15:30:33 zhipeng okey thx :) zhuli and Li_Liu will coordinate on the conductor side
15:30:38 zhipeng moving on
15:30:40 Li_Liu sure
15:30:44 zhipeng #info fix on devstack
15:31:10 shaohe_feng_ resource_tracker.py will check resource periodically
15:32:12 zhipeng shaohe_feng_ we can simplify that for queens
15:32:23 zhipeng and write to db instead of a provider-tree like cache

Earlier   Later