Earlier  
Later
New Search
Posted Nick Remark
#openstack-cyborg - 2018-07-25
14:55:15 Li_Liu shaohe_feng, is it sufficient for you?
14:55:17 zhipeng are there any conflict ?
14:55:39 xinran__ client lib depends on cyborg api we don’t have allocation api right now. How we handle that ?
14:55:43 zhipeng I think shaohe added the provider_tree and also make sure the interaction happens on the agent level
14:56:03 zhipeng xinran__ will zhenghao's patch handle that ?
14:58:15 shaohe_feng Li_Liu, zhipeng I'm back.
14:58:16 shaohe_feng sorry
14:58:24 Li_Liu I guess shaohe_feng re-implemented my part in his new patch..
14:58:43 shaohe_feng It support the sub-provider.
14:58:57 shaohe_feng actually, I did not re-implemented it.
14:59:05 shaohe_feng I leverage it from nova
14:59:07 Li_Liu shaohe_feng, I have implemented the SchedulerReportClient in https://github.com/openstack/cyborg/blob/master/cyborg/services/report.py
14:59:34 shaohe_feng Li_Liu, yes, I know your implementations.
14:59:48 Li_Liu so what the difference between your SchedulerReportClient and my SchedulerReportClient? just curious
14:59:58 shaohe_feng no sup-provider.
15:00:09 shaohe_feng it support nest provider.
15:00:24 shaohe_feng I think these code should be in a lib
15:00:31 Li_Liu i see, but should be put them together?
15:00:32 shaohe_feng so nova and cyborg can share.
15:00:50 Li_Liu just use your code
15:01:02 shaohe_feng yes. Maybe it need to remove the old one.
15:01:03 Li_Liu ignore my implementation for now then
15:01:11 Li_Liu ok
15:01:19 zhipeng okey
15:01:30 shaohe_feng And the best solution, move them to a common lib shared by nova and cyborg or other project
15:01:42 xinran__ zhipeng: yeah but we need modify that in the future
15:01:55 zhipeng xinran__ yes for sure
15:02:03 wangzhh xinran__， IMHO, we can use PATCH for allocation as my patch in rocky. Or we can design new API interface and parallel development.
15:02:03 shaohe_feng zhipeng, you can talk about with nova's guy, do they have plan to do it?
15:02:19 zhipeng shaohe_feng I think it is a reasonable request
15:02:33 zhipeng since provider tree has also been implemented for nova-compute
15:02:39 openstackgerrit Merged openstack/cyborg master: Add "interface_type" field in deployable DB https://review.openstack.org/584296
15:02:57 xinran__ wangzhh: and deallocate also by patch method ?
15:02:59 zhipeng hey look who's here
15:03:08 Li_Liu a lot of reimplementations cross different project just for this part...
15:03:13 shaohe_feng zhipeng, yes. Need need for us to maintain same code with other project. :)
15:03:31 wangzhh Yes.
15:03:39 wangzhh xinran__
15:03:44 shaohe_feng Li_Liu, yes. too many. but we should avoid.
15:03:55 Li_Liu agree
15:04:00 zhipeng okey next on drivers
15:04:05 shaohe_feng And that is cyborg should focus on
15:04:18 shaohe_feng that is not
15:04:20 shaohe_feng sorry.
15:04:35 zhipeng we now have gpu and opae based fpga drivers on the fly
15:05:02 zhipeng need brianx__ to start the Xilinx driver ASAP lol
15:05:10 xinran__ Coco: did you modify the driver discover() method to get interface type?
15:05:11 zhipeng let's start with a simple version
15:05:47 Coco I think the yes
15:06:14 Coco I will check again.
15:07:29 Coco I use the "pci" as the "interface_type" value at this moment, since it's fpga driver.
15:08:12 wangzhh I think discover should have common data structure.
15:08:22 shaohe_feng I have list cyborg tasks in the etherpad. include this one
15:08:25 Coco I agree with wangzhh
15:08:26 shaohe_feng No one take it at present.
15:09:02 shaohe_feng Yes. maybe an object
15:09:02 Coco 27th also the deadline?
15:09:17 shaohe_feng then it can not need schema verify
15:09:53 shaohe_feng anyway, the goal is unify the discover data
15:10:22 Coco I can take it, but can't make sure it can be done by 27th.
15:10:41 Li_Liu when discover() reports data, it should be in Cyborg understandable format
15:10:41 zhipeng does that affect the API behaviour ?
15:11:01 shaohe_feng Coco, great, thanks.
15:11:09 wangzhh zhipeng, no. Just affect agent.
15:11:28 wangzhh To report data.
15:11:29 Li_Liu no affect on api I don't think
15:11:32 zhipeng okey then there is no hurry
15:11:34 shaohe_feng Coco, have you looked at sundar's VAN?
15:11:37 Li_Liu yup
15:11:59 shaohe_feng Coco, can we leverage it?
15:12:07 shaohe_feng yes, not hurry.
15:12:13 Coco what's the link?
15:12:28 shaohe_feng the spec, let me show you.
15:13:15 Coco ok, thks.
15:13:35 shaohe_feng #link https://review.openstack.org/#/c/577438/
15:13:46 shaohe_feng it is used for os-acc
15:14:21 shaohe_feng you can have a check, does the drivers can use it?
15:16:02 Coco ok, i will check tomorrow.
15:16:08 shaohe_feng Thanks.
15:16:42 zhipeng Yumeng__ are you still around ?
15:16:54 zhipeng the doc work should start now
15:17:52 Li_Liu hmm
15:18:16 Li_Liu I will focus on that after warpping up the program api
15:18:33 Li_Liu will as Yumeng and others for help
15:18:59 zhipeng yes will need to work together, to comb through the implementations :)
15:19:23 Li_Liu yup
15:20:29 shaohe_feng guess she is in sleep. :)
15:20:47 Coco OK, we already had doc wechat group.
15:21:57 shaohe_feng more sleep can keep a girl beauty. :)
15:22:10 Coco ....
15:22:25 Coco I need to go sleep too.
15:22:37 zhipeng okey
15:22:38 Li_Liu have a good sleep guys :)
15:22:40 seungwook I think it takes some time for me to catch up the dialog.
15:22:52 zhipeng let's try to nail client lib down this week lol
15:23:17 zhipeng #endmeeting
15:23:18 seungwook Good night all ~ ^^
15:23:18 openstack Meeting ended Wed Jul 25 15:23:17 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:23:20 openstack Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-07-25-14.00.html
15:23:21 shaohe_feng so any one want to about the placement?

Earlier   Later