Earlier  
Posted Nick Remark
#openstack-cyborg - 2017-06-07
15:36:37 zhipeng_ yes that is always our goal
15:36:38 jkilpatr I can agree on a standard rpc interface but that's less complicated than I think you are making it out to be.
15:36:49 zhipeng_ we even wanted to skip the conductor :P
15:37:14 jkilpatr and I nearly got away with it too!
15:37:21 zhipeng_ jkilpatr haha
15:37:40 rushil Lol
15:39:26 zhipeng_ rushil the cyborg ml2 driver would be modeled from your generic driver implementation :P
15:40:37 rushil I wouldn't call it ml2 driver though
15:40:52 zhipeng_ of course we will have another name for it
15:41:14 zhipeng_ aluminum drivers :P
15:41:24 zhipeng_ for cyborg robots
15:41:45 rushil Hehe
15:42:36 jkilpatr Anyways I'll try have a stub up this week (conductor) and then agent next week.
15:42:46 jkilpatr depends on how other tasks go for me.
15:43:44 rushil jkilpatr: Cool
15:43:50 zhipeng_ sounds great, i got another colleague working on cyborg this week, so api code will be developed in parallel
15:44:09 rushil Awesome
15:44:10 zhipeng_ hopefully when we settled the spec, the initial code will come out
15:44:21 zhipeng_ and we could iterate over
15:44:48 zhipeng_ #topic AoB
15:44:52 zhipeng_ any other topics
15:44:59 rushil Btw our group at Lenovo sent out initial emails to vendors to get their drivers aligned with cyborg
15:45:20 zhipeng_ wow
15:45:24 zhipeng_ that is awesome
15:45:45 rushil I'll keep you guys posted on that
15:45:51 zhipeng_ could you disclose the vendor names for now ?
15:45:57 zhipeng_ or should we wait until later
15:46:14 rushil The usual suspects
15:46:35 zhipeng_ e.g ?
15:46:47 rushil Nvidia, AMD
15:47:00 rushil And smaller ones like Micron
15:47:29 zhipeng_ cool !
15:47:30 rushil I'll let y'all know when they are committed to contributing code
15:47:40 zhipeng_ great :)
15:50:41 zhipeng_ okey if there are no other topics, we go to the usual long slumber ~~
15:50:56 zhipeng_ will try to remember to close the meeting an hour later
15:51:05 crushil Cool, thanks zhipeng_
17:00:56 zhipeng_ #endmeeting
17:00:58 openstack Meeting ended Wed Jun 7 17:00:56 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
17:00:59 openstack Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-06-07-15.00.html
17:01:00 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-06-07-15.00.txt
17:01:01 openstack Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-06-07-15.00.log.html
#openstack-cyborg - 2017-06-09
12:36:33 jkilpatr https://docs.google.com/presentation/d/1cDIhkfFBoIME-DQobACaBmU4qWILJ_sW3chEulIP7ZM/edit#slide=id.p
12:36:34 jkilpatr probably useful
13:21:46 jkilpatr zhipengh[m], so I've been thinking should the API be stateless? AKA it gets everything from the conductor, if we do things that way then when we want to support HA we only have to make the conductor HA everything else is already distributed.
13:21:54 jkilpatr but premature optimization is the root of all evil and all that.
13:25:30 zhipengh[m] API stateless meaning we won't have small dB for API right ?
13:26:41 jkilpatr zhipengh[m], that means no cache which puts more load on other components. Everything has a trade off.
13:53:13 zhipengh[m] Let me think about that a little bit
#openstack-cyborg - 2017-06-14
14:35:06 jkilpatr somehow oslo config is more complicated than messaging.
14:59:58 crushil \o
15:00:39 zhipeng hi guys
15:01:19 openstack Meeting started Wed Jun 14 15:01:19 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:19 zhipeng #startmeeting openstack-cyborg
15:01:20 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:22 openstack The meeting name has been set to 'openstack_cyborg'
15:01:37 zhipeng #topic BP discussion
15:01:55 zhipeng #info the api spec has been updated to reflect the latest comment
15:02:05 zhipeng #link https://review.openstack.org/#/c/445814/
15:03:14 zhipeng plz help review it, would be nice to merge it by the end of this week
15:04:22 zhipeng and then I think I will take over the cyborg-nova interaction spec
15:06:08 zhipeng any thoughts on the api spec so far ?
15:06:13 crushil zhipeng, Will do
15:06:26 crushil Need to look at the API spec
15:06:58 zhipeng okey no problem
15:07:05 zhipeng moving on to the next topic
15:07:12 zhipeng #topic code development process
15:07:21 zhipeng crushil how's the code going ?
15:08:22 crushil It's going. I have pushed the WIP up for the driver. I will fill out my code pending your work and jkilpatr's work
15:08:54 jkilpatr morning everyone.
15:09:10 jkilpatr Conductor is very stubby working on getting it hooked up to rabbit today.
15:09:11 zhipeng morning :)
15:09:45 zhipeng crushil have you submitted the code yet ?
15:10:10 jkilpatr yup he did on sudnay
15:10:15 jkilpatr sunday*
15:10:19 crushil Yup
15:10:38 crushil Morning jkilpatr
15:10:44 zhipeng oh did not see that yet
15:11:13 zhipeng well there is a thought when I update the api spec today
15:11:23 jkilpatr I have a patch up for an internal accelerator object because I need one in both the conductor and the agent and didn't want to duplicate code.
15:11:49 zhipeng that the generic driver should morph into a standalone library for local and remote accelerator attach/detach
15:12:19 jkilpatr so that means we have attach/detach library and then the pci passthrough driver build ontop of it?
15:12:23 zhipeng like os-brick
15:12:35 jkilpatr ok no idea what os-brick is
15:13:31 zhipeng every cinder driver has to do attach/detach on its own
15:13:31 zhipeng back in the days
15:13:31 zhipeng so the background story is
15:13:31 zhipeng yes, just import the lib and use it
15:13:39 zhipeng either iSCSI, FC, or what have you
15:14:11 zhipeng then cinder project extract that part of code out and formed a new sub project called os-brick
15:14:23 zhipeng bascially provide a common lib for the attach/detach
15:14:39 zhipeng the benefit is that, you could use it even Nova is not involved
15:14:54 zhipeng for example attach a volume for baremetal host
15:15:45 zhipeng and cinder driver could just include the lib and call the functions they need
15:17:36 crushil zhipeng, So, are you proposing we should move our generic driver code eventually into something like OS-brick?
15:17:59 zhipeng yes that is my current thinking
15:18:12 zhipeng in the near future
15:18:46 crushil I don't understand why though?
15:19:27 jkilpatr for the sake of abstraction
15:19:38 jkilpatr instead of having to attach.nvidiagraphicsdriver

Earlier   Later