Earlier  
Posted Nick Remark
#openstack-cyborg - 2018-01-03
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
15:10:05 zhipeng first one is to land Li Liu and Zhuli's patch
15:10:19 zhipeng let's discuss Li Liu's FPGA data modeling spec first
15:10:33 zhipeng any remaining questions still ?
15:11:00 zhipeng #link http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-01-03-15.00.html
15:11:26 zhipeng there are all the links in the log of last meeting
15:11:36 jkilpatr it looked pretty good to me, didn't post a review thought
15:11:42 jkilpatr I'll go ahead and read over it again and do that.
15:11:45 zhuli zhipeng, sure, I will try my best to make enough cyborg time once I have done with the online emergency this days
15:12:40 zhipeng jkilpatr if you could do it today then you could just directly land it
15:13:15 zhipeng zhuli no problem :)
15:13:23 zhipeng okey next zhuli's patch
15:13:38 zhipeng zhuli have you been able to update the patch with the unit test ?
15:13:45 zhipeng like crushil suggested last time
15:17:11 zhipeng zhuli ?
15:17:51 zhuli I still work on it, but didn't have much time to finish it, as I mentioned I will complete it soon after the online emergency, I think tomorrow night is enough
15:18:22 zhipeng okey then we slate it for Friday for landing
15:19:36 zhuli thanks
15:19:41 zhipeng okey next, shaohe's spec on Intel's FPGA device driver
15:20:18 zhipeng i see crushil's review have not been addressed yet
15:20:48 zhipeng i will ping shaohe to address it this later today
15:21:54 zhipeng then we will still need to keep justin's spec open until the above mentioned three patches got landed
15:22:36 jkilpatr the other patches seem compatible, has anyone noticed any modifications that need to be made to my patch to account for the others?
15:23:29 zhipeng i think mostly will come from zhuli's patch, if there are any
15:23:39 zhipeng zhuli could you make an estimation ?
15:24:41 zhipeng are there any api extensions that needs to be reflected in Justin's spec ?
15:26:22 zhuli sorry, which spec do you mean?
15:26:34 zhipeng justin's internal api
15:26:45 zhipeng #link https://review.openstack.org/525598
15:30:47 zhuli I think this is enough at the moment, my follow up works will base on this and fine tune when needed
15:31:13 zhipeng then I guess we could land Justin's spec right ?
15:31:54 jkilpatr ¯\_(ツ)_/¯
15:32:33 zhuli agree
15:33:10 zhipeng progress !
15:33:48 zhipeng okey the most important ones, let's try to get it done by Friday this week, we can not delay any more

Earlier   Later