Earlier  
Posted Nick Remark
#openstack-cyborg - 2018-01-03
15:30:29 Li_Liu Each Physical Functions can have multiple Virtual Functions
15:32:13 Li_Liu Also, we have a Attribute table which stores k-v pairs referencing back to the Deployables table
15:32:45 zhipeng is this aligned with the nested resource provider spec ?
15:32:50 Li_Liu this way, we can track arbitrary type of attributes for generic types
15:32:55 zhipeng (which expected to be done in Queens)
15:33:20 Li_Liu It does, actually
15:33:40 zhipeng cool
15:34:00 zhipeng thx for the intro, everyone plz help review the spec
15:34:08 Li_Liu the Deployable is counterpart to resource providers in NOVA
15:34:13 zhipeng zhuli will also reflect the changes in the spec on the fly
15:34:19 Li_Liu Thanks a lot guys
15:35:30 zhipeng moving on to the next
15:35:43 zhipeng #info 5. Intel's FPGA device driver
15:35:56 zhipeng #link https://review.openstack.org/530720
15:36:23 zhipeng shaohe_feng_ could you help introduce the spec ?
15:38:45 shaohe_feng_ zhipeng: yes
15:39:43 shaohe_feng_ zhipeng: this spec is going to provide the fpga information to the Li_Liu's spec
15:40:27 shaohe_feng_ zhipeng: and support a program interface for FPGA
15:41:06 shaohe_feng_ When cyborg agent starts or does resource check periodically, the cyborg FPGA driver should enumerate the list of the FPGA devices, and report the details of all available FPGA accelerator on the host. Such as BDF, PID, VID, IMAGE_ID, PF/VF type.
15:41:33 zhipeng this has any impact on your work @crushil ?
15:41:37 shaohe_feng_ When user uses empty FPGA regions as its accelerator, cyborg agent should call driver's program() interface. Cyborg agent should provide BDF of VF, and local image path to the driver. More details ref
15:44:05 crushil I'm not sure
15:44:17 crushil I need to look at the spec
15:44:55 shaohe_feng_ zhipeng: I'm not familiar with other vendor's FPGA. Not sure we need a virtual FPGA driver interface.
15:45:58 zhipeng crushil okey
15:46:22 zhipeng shaohe_feng_ I think Li_Liu could help you with the insight of other vendor implementation
15:46:23 shaohe_feng_ o, sorry. the driver should can program any FPGA regions not only empty region
15:46:51 shaohe_feng_ zhipeng: that's greate
15:47:10 shaohe_feng_ will update the spec.
15:47:26 zhipeng cool
15:47:39 zhipeng okey then we have the last non-priority patch
15:47:49 zhipeng #info 6. SPDK driver code
15:48:01 zhipeng #link https://review.openstack.org/513704
15:48:02 shaohe_feng_ the agent decide which region need to be re-program.
15:49:03 zhipeng the SPDK code is developed by people in my team, so if we could squeeze it in Queens then it would be great, if not it is also not an issue
15:49:13 zhipeng will ping you guys when it is ready
15:49:23 zhipeng #topic Queens Priorities
15:49:40 zhipeng I would suggest the following priorities for this month
15:49:40 jkilpatr proof of concept?
15:49:53 zhipeng jkilpatr ya like that
15:50:10 zhipeng we have patches need to be merged in spdk in the first place to make it work
15:50:27 zhipeng but it is non-priority so no hurry on that one
15:50:55 zhipeng i will handle that quietly on my side :P
15:51:05 zhipeng okey back to priority suggestion
15:51:30 zhipeng #info suggestion 1: land LiLiu and zhuli's patch this week
15:52:00 zhipeng i know there are a lot of reviews to be done, but let's try to crunch it this week
15:52:17 zhipeng so that crushil and justin's work could move ahead
15:52:58 zhipeng #info suggestion 2: we land justin's and shaohe's spec by the end of next week
15:53:38 zhipeng meaning that once we agreed upon the API layer implementation this week, we could crunch out the conductor/agent/driver interface pretty much next Wed
15:54:14 zhipeng and we should be okey to have a full picture for the internal API spec, as well as shalhe's driver spec to align with it
15:54:31 Li_Liu sounds great
15:54:42 zhipeng #info suggestion 3: at the moment we keep the vendor driver code in-tree since there are not a lot
15:54:43 jkilpatr I'll give it a go.
15:54:51 jkilpatr agreed
15:55:00 jkilpatr no reason to make things more complicated until it becomes an issue.
15:55:07 zhipeng yep
15:55:29 zhipeng anyone else comment on my three suggestions ?
16:02:52 zhipeng crushil ?
16:03:18 crushil 3
16:03:43 crushil We should keep it in-tree
16:03:53 crushil We are not in that position yet to move it out of tree
16:04:03 vipparthy zhipeng, who can help me to identify driver specs to be written for different FPGA's in our team ?
16:04:06 zhipeng crushil exactly
16:04:14 crushil And apologies for delays. I'm in a conference right now
16:04:27 zhipeng no problem :)
16:05:09 zhipeng vipparthy you could go over the log, there are info points that could help you identify it
16:06:28 zhipeng so if there are no other issues, I will close the meeting on time-ish :P
16:06:43 zhipeng let's go to work and try to deliver an awesome first release
16:07:05 crushil \o/
16:09:23 zhipeng #endmeeting
16:09:25 openstack Meeting ended Wed Jan 3 16:09:23 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
16:09:26 openstack Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-01-03-15.00.html
16:09:27 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-01-03-15.00.txt
16:09:29 openstack Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-01-03-15.00.log.html
16:23:29 vipparthy thank you folks
#openstack-cyborg - 2018-01-10
15:00:57 crushil \o
15:01:47 zhipeng yo
15:01:57 zhipeng #startmeeting openstack-cyborg
15:01:58 openstack Meeting started Wed Jan 10 15:01:57 2018 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:59 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:02 openstack The meeting name has been set to 'openstack_cyborg'
15:02:10 zhipeng #topic Roll Call
15:02:19 zhipeng #info Howard
15:04:23 zhipeng anyone else ?
15:05:09 jkilpatr #info Justin
15:05:13 jkilpatr morning.
15:05:22 zhipeng morning !
15:05:25 zhipeng :P
15:05:39 jkilpatr I say to the guy burning the midnight oil
15:06:03 zhipeng not there yet, but soon lol
15:06:06 vipparthy Good Morning folks
15:06:46 zhipeng morning !
15:07:08 zhipeng let's wait for another 4 mins see if anyone else will join,especially zhuli
15:07:18 zhipeng have tried to ping him but no success
15:07:36 crushil #info Rushil
15:07:44 zhuli #info zhuli
15:08:35 zhuli sorry for the late, I'm still at work in company
15:09:25 zhipeng zhuli let's try to survive this month lol
15:09:37 zhipeng #topic Queens Release Prep Progress
15:09:51 zhipeng so action items from last meeting

Earlier   Later