Earlier  
Posted Nick Remark
#openstack-cyborg - 2018-05-07
15:12:07 sum12 Does any one have plans to travel to PTG in Denver ?
15:12:28 sum12 Oh and BTW i work for suse and am already involved in other project
15:14:05 jiapei Welcome sum12
15:19:03 sum12 thanks jiapei
#openstack-cyborg - 2018-05-08
03:58:51 openstackgerrit Sundar Nadathur proposed openstack/cyborg master: Specification for Cyborg/Nova interaction for scheduling. https://review.openstack.org/554717
06:22:29 openstackgerrit Merged openstack/cyborg master: uncap eventlet https://review.openstack.org/560486
07:09:52 openstackgerrit Sundar Nadathur proposed openstack/cyborg master: Specification for Cyborg/Nova/Glance interaction in the compute node, including os-acc library API. https://review.openstack.org/566798
22:10:23 openstackgerrit Sundar Nadathur proposed openstack/cyborg master: Specification for Cyborg/Nova interaction for scheduling. https://review.openstack.org/554717
22:18:59 openstackgerrit Sundar Nadathur proposed openstack/cyborg master: Specification for Cyborg/Nova/Glance interaction in the compute node, including os-acc library API. https://review.openstack.org/566798
#openstack-cyborg - 2018-05-09
04:30:47 openstackgerrit Li Liu proposed openstack/cyborg master: Added attribute object and its unit tests https://review.openstack.org/565382
04:40:25 openstackgerrit Li Liu proposed openstack/cyborg master: Added attribute object and its unit tests https://review.openstack.org/565382
06:26:32 xinran__ hi, all. does cyborg have api doc?
13:59:54 xinran__ meeting?
14:00:00 zhipeng yes
14:00:39 xinran__ :)
14:01:06 openstack Meeting started Wed May 9 14:01:06 2018 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:06 zhipeng #startmeeting openstack-cyborg
14:01:07 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:09 openstack The meeting name has been set to 'openstack_cyborg'
14:01:36 zhipeng #topic Roll Call
14:01:41 zhipeng #info Howard
14:01:54 sum12 #info sum12
14:02:00 NokMikeR #info Mike
14:02:01 edleafe #info Ed
14:02:01 Helloway #info Helloway
14:02:43 Li_Liu #info Li_Liu
14:02:54 shaohe #info shaohe
14:03:02 zhipeng Hi sum12, could you introduce a bit about yourself ?
14:03:20 xinran__ #info xinran__
14:03:35 sum12 Hey, I am Sumit. I work for SUSE and have been part of some other projects already.
14:03:49 sundar Hi Sumit
14:03:50 zhipeng welcome :)
14:03:58 Li_Liu Hi Sumit
14:04:05 sum12 Thanks everyone :)
14:04:31 NokMikeR Welcome
14:04:34 sundar #info Sundar
14:04:56 shaohe welcome sum12
14:05:29 sum12 glad to be here, thanks sundar zhipeng Li_Liu NokMikeR sundar
14:06:17 zhipeng okey let's get into business
14:06:25 zhipeng #topic driver subteam meeting time
14:07:11 zhipeng so shaohe has helped started a poll
14:07:19 zhipeng and it seems three options are at the top
14:08:11 sundar Could somebody post the poll link here?
14:08:12 zhipeng UTC 1:00am Mon, UTC 2:00pm Mon, UTC 8:30am Wed
14:08:59 zhipengh[m] #link https://doodle.com/poll/pa3gi78yncsr7qee
14:10:34 shaohe sundar: any prefer on the time?
14:10:38 zhipeng let's pick one :)
14:11:23 Li_Liu I am good with anytime at night(which is morning back in China)
14:12:00 sundar Yes, Shaohe. I clicked on the doodle now. Sunday eve or Mon 7 am PST are both good
14:13:31 zhipeng ok let's do the Mon UTC 2:00pm
14:13:57 zhipeng which will be 10:00pm at China, 10:00 am EST, 7:00am PST
14:15:19 zhipeng it's the most popular time
14:15:22 zhipeng okey ?
14:15:32 sundar Sounds good to me!
14:15:32 NokMikeR ok
14:16:02 zhipeng #agreed driver subteam meeting time every Mon UTC1400
14:16:04 Li_Liu Monday?
14:16:15 zhipeng Monday
14:16:17 Li_Liu ok
14:16:21 Li_Liu sounds good
14:16:42 zhipeng #topic new core reviewer promotion
14:17:06 zhipeng in order to increase our review bandwidth, i hereby promote Sundar to be the new core reviewer
14:17:24 zhipeng Sundar has been very active and taking charge of several important specs
14:17:57 zhipeng so as usual, we will have one week time for any feedback, and acknowledgment of the promotion next Wed :)
14:18:26 kosamara #info kosamara
14:18:29 sundar Thanks, zhipeng
14:18:41 Li_Liu gratz :)
14:19:03 shaohe gratz :)
14:19:19 zhipeng well not yet :)
14:19:39 zhipeng let's wait for a week for feedback
14:20:00 sundar Thanks, Li_Liu and shaohe :). As zhipeng says, one week from now, we will know.
14:20:06 zhipeng but would like to thanks for Sundar's great effort so far
14:20:12 zhipeng :)
14:20:16 zhipeng okey moving on
14:20:41 zhipeng #topic KubeCon feedback
14:20:58 zhipeng okey last week i attend KubeCon and the resource mgmt wg deep dive session
14:21:34 zhipeng k8s res mgmt wg is the center in k8s which deals with general and acceleration resources
14:22:10 zhipeng My takeaway is that the support for a general accelerator mgmt, is still not in any shape in k8s
14:22:23 zhipeng Google is interested in GPU passthrough support for ML, mainly
14:23:32 zhipeng so if anyone wants to introduce any feature in-tree
14:24:26 zhipeng that would require a PoC up-front
14:24:59 zhipeng many things we discussed here, like vGPU types, general accelerator support including FPGA and others
14:25:05 zhipeng are viewed non-priority
14:25:22 zhipeng the resource class/resource api PRs are also long shot
14:25:28 zhipeng according to vishnu
14:27:29 sundar zhipeng: Agreed with your assessments. If we can get just one feature in -- passing annotations to the device plugin API -- that will help us meet most basic FPGA use cases, IMHO
14:27:55 zhipeng Sasha mentioned Intel team has finished a FPGA DPI PoC
14:28:04 zhipeng but also just pre-programmed FPGAs
14:28:39 sundar We can couple that with a scheduler extension. However, scheduler extensions are not viewed favorably because the scheduler fra,ework itself may change and the APIs may change along with it.
14:29:00 zhipeng yes, and also DPI is designed at the node level
14:29:09 sundar However, we can do a POC base don it, including programming support, and revamp it when the APIs change. Just my thought. :)
14:29:15 zhipeng and a mostly "reschedule" focused mechanism
14:29:36 sundar Yes, we do have a POC that does only pre-programmed use case. That does not show the strength of FPGAs, which is reprogramming
14:30:01 zhipeng so DPI is designed to mostly work for hot-plug use case, not scheduling upfront
14:30:22 zhipeng the scheduling will be retriggered once the node discover the DPI Plugin
14:30:35 zhipeng anyways it is the current lay of land
14:31:04 zhipeng so my thinking is, maybe it is reasonable to introduce a CRD framework for cyborg into k8s community
14:31:35 zhipeng so that we could have all of our data model preserved, has leeway on the api and scheduling design
14:31:46 zhipeng maintain a k8s-ish API interface
14:32:12 zhipeng and a out-of-band general accelerator mgmt functionality, not bound to DPI development

Earlier   Later