| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2017-04-26 | |||
| 15:56:15 | _gryf | *IRC | |
| 15:56:36 | zhipeng | _gryf fantastic :) | |
| 16:03:27 | ttk2[m] | Ok so I looked at the nasca patch for like 30s but I don't think I understand what it's supposed to do exactly? Anyone mind going over it. | |
| 16:04:43 | zhipeng | ttk2[m] I think they basically developed a prototype that utilize the resource provider for accelerator provisioning | |
| 16:05:22 | ttk2[m] | Ah that sounds cool. I'll have to give it a try. | |
| 16:06:01 | zhipeng | yes, so the original plan was to have Mellanox team provide the DB design spec from their nasca proposal | |
| 16:06:29 | zhipeng | since Cyborg has a very similar requirement | |
| 16:06:36 | zhipeng | as far as I understand | |
| 16:08:47 | NokMikeR | sorry need to run, till next time. | |
| 16:09:00 | zhipeng | no problem Mike | |
| 16:09:19 | zhipeng | we are just running over the regular time as we always do :P | |
| 16:15:13 | _gryf | zhipeng, endmeeting? | |
| 16:15:48 | zhipeng | i'm not sure if Justin still got anything to share | |
| 16:16:38 | zhipeng | okey let me just end it now, in case my network breaks again :P | |
| 16:16:44 | zhipeng | thanks team for the discussion | |
| 16:16:48 | zhipeng | #endmeeting | |
| 16:16:50 | openstack | Meeting ended Wed Apr 26 16:16:48 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 16:16:51 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-04-26-15.10.html | |
| 16:16:53 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-04-26-15.10.txt | |
| 16:16:55 | openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-04-26-15.10.log.html | |
| #openstack-cyborg - 2017-05-03 | |||
| 14:57:48 | jkilpatr | \o | |
| 14:59:28 | zhipeng | hey | |
| 14:59:50 | goldenfri | hello | |
| 15:00:42 | crushil | \o | |
| 15:02:23 | zhipeng | #startmeeting openstack-cyborg | |
| 15:02:24 | openstack | Meeting started Wed May 3 15:02:23 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 15:02:26 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 15:02:29 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 15:03:07 | zhipeng | #topic BP discussion | |
| 15:03:20 | zhipeng | let's get a quick review of the spec work | |
| 15:03:27 | zhipeng | any outstanding issues ? | |
| 15:04:14 | jkilpatr | waiting for Roman to get back to me on my last patchset, he commented he had one comment on patchset 4 left but I think I addressed all of them so ¯\_(ツ)_/¯ | |
| 15:04:48 | jkilpatr | ooh there's a new driver patch, let me look at it. | |
| 15:05:10 | zhipeng | haha i also notice that one | |
| 15:05:21 | zhipeng | ping _gryf | |
| 15:07:51 | zhipeng | crushil anything from your side ? | |
| 15:08:33 | crushil | Nope. Just updated the patch like an hour ago. Nothing else. Will look at the summit presentation that you sent this morning | |
| 15:10:12 | jkilpatr | crushil, look at my slide on drivers, if our visions diverge we need to hash that out. Looking at your latest patch I'm not quite sure. | |
| 15:12:35 | crushil | jkilpatr, Will do | |
| 15:15:15 | crushil | jkilpatr, In any case, can you still review the latest patch? | |
| 15:15:20 | jkilpatr | already did | |
| 15:15:38 | jkilpatr | well I left one comment. | |
| 15:16:18 | crushil | I will try to come back sooner with the next patchset. I was busy with downstream things for the past month. Should have more time this month, hopefully | |
| 15:22:52 | jkilpatr | what outstanding as far as reviews go | |
| 15:23:14 | jkilpatr | I think everyone's happy with the agent, speak now or forever hold your -2 | |
| 15:23:56 | jkilpatr | I'm happy with the api patch so +1 | |
| 15:25:09 | jkilpatr | cyborg/nova needs bullet points, too wordy right now. | |
| 15:39:36 | zhipeng | agree jkilpatr on the agent | |
| 15:39:53 | zhipeng | and i think driver's spec after some fixing from crushil | |
| 15:39:57 | zhipeng | should be ok to merge as well | |
| 15:49:29 | zhipeng | the api spec will need further polishing I guess | |
| 15:49:40 | zhipeng | since ClintD also review ed that .... | |
| 15:50:00 | zhipeng | okey let's move to the next topic | |
| 15:50:07 | zhipeng | #topic BoS slide prep | |
| 15:50:27 | zhipeng | ping jkilpatr goldenfri | |
| 15:50:43 | zhipeng | let's discuss the flow | |
| 15:51:43 | jkilpatr | zhipeng, so the flow I'm getting right now is we introduce ourselves, talk a little about cyborg as a cool project for Telecom/NFV, then we get into talking about why everyone needs and can use accelerators, and how cyborg will make that usecase easy for everyone, original stakeholders included | |
| 15:52:36 | jkilpatr | are slides 7 and 8 redundant? and maybe we want to move 6 somewhere after 7 once we go from "hey nomand was a project for nfv hardware" to "cyborg is for everyone" | |
| 15:53:34 | zhipeng | 6 is like a starter for the conversation | |
| 15:53:51 | zhipeng | that acceleration is a requirement, no longer just an icing on the top | |
| 15:54:03 | zhipeng | and 7 and 8 provides the history | |
| 15:54:12 | zhipeng | but I guess I should merge these two into one | |
| 15:54:17 | zhipeng | 7 and 8 | |
| 15:54:59 | jkilpatr | do we want to move goldenfri's stuff forward? not sure it makes sense at the back? | |
| 15:55:00 | goldenfri | so I've pinged Blair for some information on GPU requirements because I haven't heard anything recently | |
| 15:55:15 | goldenfri | so I added a slide on GPU | |
| 15:55:26 | goldenfri | but yea I don't think it should go there | |
| 15:55:47 | jkilpatr | ok so, intro, history, why nfv and gpgpu sucks on openstack right now, why everyone needs accelerators, cyborg and it's design | |
| 15:56:14 | goldenfri | makes sense | |
| 15:56:15 | jkilpatr | that would put goldenfri's stuff somehwere around the background slides | |
| 15:56:34 | jkilpatr | goldenfri, go ahead and drop it where you think it makes the most sense right now. | |
| 15:57:07 | zhipeng | maybe 18 should be after 10 ? | |
| 15:58:25 | zhipeng | yes, so what I imagined is that 10 - 12 provides the motivation within the OpenStack | |
| 15:59:11 | zhipeng | Background parts covers high level descriptions, identify the need in a broader sense | |
| 15:59:25 | jkilpatr | then we drill down into the details, sounds great. | |
| 15:59:30 | zhipeng | yes | |
| 15:59:32 | goldenfri | ah ok, I've moved it in there before the "why cyborg" | |
| 15:59:46 | zhipeng | yes that looks good | |
| 16:00:22 | zhipeng | goldenfri could you add another slide of intro on the SWG ? | |
| 16:00:34 | goldenfri | yes, I'm going to work on it more today | |
| 16:00:41 | zhipeng | that way you could kickoff the deep dive discussion with SWG requirements | |
| 16:00:41 | goldenfri | I left the placeholder there | |
| 16:00:45 | zhipeng | :) nice | |
| 16:01:03 | zhipeng | and then Justin pick up and introduce the technical stuff | |
| 16:01:11 | jkilpatr | goldenfri, looking at your speaker notes. From what I understand you would spawn an instance then ping cyborg and say "attach a gpu to this instance" and cyborg takes care of the rest | |
| 16:01:21 | jkilpatr | right zhipeng? or are we using tags on instance creation? | |
| 16:01:35 | goldenfri | yea I wasn't sure about that | |
| 16:01:57 | zhipeng | I think so | |
| 16:01:58 | jkilpatr | the api design makes it look like the latter, but the nova interaction is fuzzy, if we attach the accelerator after the instance is spawned how do we make sure it's in the right spot? migration | |
| 16:02:22 | zhipeng | I think for the attach action | |
| 16:02:30 | zhipeng | user should not directly ping cyborg | |
| 16:02:35 | zhipeng | it should just use nova | |
| 16:02:40 | zhipeng | like how nova attach the volume | |
| 16:02:59 | zhipeng | that is why Roman mentioned that there are modifications needed in nova | |
| 16:03:02 | jkilpatr | ok so some special flavor or tag? that's fine Cyborg helps with scheduling and setup in the first place. | |
| 16:03:11 | zhipeng | yep | |
| 16:03:57 | zhipeng | so it would be like nova attach GPU instance-id, and it will call cyborg api | |
| 16:04:12 | goldenfri | so it would still need a tag to work with cyborg? | |
| 16:04:29 | jkilpatr | goldenfri, yes but cyborg would help handle other bits, like making sure the gpu is working, that it's not overloaded etc | |
| 16:04:33 | zhipeng | not a tag, but just a resource class I think | |