| *** joseppc has joined #openstack-cyborg | 07:29 | |
| *** joseppc has joined #openstack-cyborg | 07:29 | |
| *** joseppc has quit IRC | 08:15 | |
| *** adreznec has quit IRC | 09:30 | |
| *** adreznec has joined #openstack-cyborg | 09:31 | |
| *** jkilpatr has quit IRC | 10:31 | |
| *** jkilpatr has joined #openstack-cyborg | 10:49 | |
| *** mikeH_ has joined #openstack-cyborg | 11:43 | |
| *** mpaolino has joined #openstack-cyborg | 13:03 | |
| *** zhipeng has joined #openstack-cyborg | 13:49 | |
| *** crushil has joined #openstack-cyborg | 13:52 | |
| jkilpatr | \o | 14:57 |
|---|---|---|
| zhipeng | hey | 14:59 |
| goldenfri | hello | 14:59 |
| crushil | \o | 15:00 |
| zhipeng | #startmeeting openstack-cyborg | 15:02 |
| 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:02 |
| openstack | The meeting name has been set to 'openstack_cyborg' | 15:02 |
| zhipeng | #topic BP discussion | 15:03 |
| zhipeng | let's get a quick review of the spec work | 15:03 |
| zhipeng | any outstanding issues ? | 15:03 |
| 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 |
| jkilpatr | ooh there's a new driver patch, let me look at it. | 15:04 |
| zhipeng | haha i also notice that one | 15:05 |
| zhipeng | ping _gryf | 15:05 |
| zhipeng | crushil anything from your side ? | 15:07 |
| crushil | Nope. Just updated the patch like an hour ago. Nothing else. Will look at the summit presentation that you sent this morning | 15:08 |
| 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:10 |
| crushil | jkilpatr, Will do | 15:12 |
| crushil | jkilpatr, In any case, can you still review the latest patch? | 15:15 |
| jkilpatr | already did | 15:15 |
| jkilpatr | well I left one comment. | 15:15 |
| 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:16 |
| jkilpatr | what outstanding as far as reviews go | 15:22 |
| jkilpatr | I think everyone's happy with the agent, speak now or forever hold your -2 | 15:23 |
| jkilpatr | I'm happy with the api patch so +1 | 15:23 |
| jkilpatr | cyborg/nova needs bullet points, too wordy right now. | 15:25 |
| zhipeng | agree jkilpatr on the agent | 15:39 |
| zhipeng | and i think driver's spec after some fixing from crushil | 15:39 |
| zhipeng | should be ok to merge as well | 15:39 |
| zhipeng | the api spec will need further polishing I guess | 15:49 |
| zhipeng | since ClintD also review ed that .... | 15:49 |
| zhipeng | okey let's move to the next topic | 15:50 |
| zhipeng | #topic BoS slide prep | 15:50 |
| zhipeng | ping jkilpatr goldenfri | 15:50 |
| zhipeng | let's discuss the flow | 15:50 |
| 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:51 |
| 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:52 |
| *** mpaolino has quit IRC | 15:53 | |
| zhipeng | 6 is like a starter for the conversation | 15:53 |
| zhipeng | that acceleration is a requirement, no longer just an icing on the top | 15:53 |
| zhipeng | and 7 and 8 provides the history | 15:54 |
| zhipeng | but I guess I should merge these two into one | 15:54 |
| zhipeng | 7 and 8 | 15:54 |
| jkilpatr | do we want to move goldenfri's stuff forward? not sure it makes sense at the back? | 15:54 |
| goldenfri | so I've pinged Blair for some information on GPU requirements because I haven't heard anything recently | 15:55 |
| goldenfri | so I added a slide on GPU | 15:55 |
| goldenfri | but yea I don't think it should go there | 15:55 |
| jkilpatr | ok so, intro, history, why nfv and gpgpu sucks on openstack right now, why everyone needs accelerators, cyborg and it's design | 15:55 |
| goldenfri | makes sense | 15:56 |
| jkilpatr | that would put goldenfri's stuff somehwere around the background slides | 15:56 |
| jkilpatr | goldenfri, go ahead and drop it where you think it makes the most sense right now. | 15:56 |
| zhipeng | maybe 18 should be after 10 ? | 15:57 |
| zhipeng | yes, so what I imagined is that 10 - 12 provides the motivation within the OpenStack | 15:58 |
| zhipeng | Background parts covers high level descriptions, identify the need in a broader sense | 15:59 |
| jkilpatr | then we drill down into the details, sounds great. | 15:59 |
| zhipeng | yes | 15:59 |
| goldenfri | ah ok, I've moved it in there before the "why cyborg" | 15:59 |
| zhipeng | yes that looks good | 15:59 |
| zhipeng | goldenfri could you add another slide of intro on the SWG ? | 16:00 |
| goldenfri | yes, I'm going to work on it more today | 16:00 |
| zhipeng | that way you could kickoff the deep dive discussion with SWG requirements | 16:00 |
| goldenfri | I left the placeholder there | 16:00 |
| zhipeng | :) nice | 16:00 |
| zhipeng | and then Justin pick up and introduce the technical stuff | 16:01 |
| 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 |
| jkilpatr | right zhipeng? or are we using tags on instance creation? | 16:01 |
| goldenfri | yea I wasn't sure about that | 16:01 |
| zhipeng | I think so | 16:01 |
| 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:01 |
| zhipeng | I think for the attach action | 16:02 |
| zhipeng | user should not directly ping cyborg | 16:02 |
| zhipeng | it should just use nova | 16:02 |
| zhipeng | like how nova attach the volume | 16:02 |
| zhipeng | that is why Roman mentioned that there are modifications needed in nova | 16:02 |
| jkilpatr | ok so some special flavor or tag? that's fine Cyborg helps with scheduling and setup in the first place. | 16:03 |
| zhipeng | yep | 16:03 |
| zhipeng | so it would be like nova attach GPU instance-id, and it will call cyborg api | 16:03 |
| goldenfri | so it would still need a tag to work with cyborg? | 16:04 |
| 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 |
| zhipeng | not a tag, but just a resource class I think | 16:04 |
| zhipeng | like a tag | 16:04 |
| jkilpatr | not to mention more thoughtful scheduling, don't fill up instances with accelerators until other computes are full | 16:05 |
| goldenfri | right, that would be huge | 16:05 |
| zhipeng | right | 16:05 |
| goldenfri | like a priority | 16:05 |
| jkilpatr | goldenfri, right now if you have more than one gpu in a machine how do you make sure they all get used? | 16:05 |
| jkilpatr | you just don't? | 16:05 |
| goldenfri | basically, you have to micromanage it | 16:06 |
| jkilpatr | :( | 16:06 |
| goldenfri | well it won't let you spawn if there are no GPUs available | 16:06 |
| jkilpatr | I think cyborg will really shine when gpu virtualization matures | 16:07 |
| jkilpatr | then load monitoring becomes more important because it's a timesliced not a monlithic asset, but getting ahead of ourselves. | 16:07 |
| zhipeng | jkilpatr +1 | 16:07 |
| goldenfri | I agree, there is also the issue of KVM tuning, cpu pinning etc | 16:08 |
| goldenfri | I assume cyborg won't do any of that | 16:08 |
| jkilpatr | goldenfri, why not, just make a driver for it | 16:08 |
| goldenfri | That would be great | 16:08 |
| jkilpatr | drivers just have attach/detach setup/uninstall commands, setup would just be a do nothing function, attach/detach would just pin to a cpu on the same NUMA as the gpu | 16:08 |
| jkilpatr | that's what you want right? | 16:08 |
| jkilpatr | then you would take the instance and tag it for gpu and gpu_pinning drivers and boom its done | 16:09 |
| goldenfri | yea because if you don't do any tuning performance is pretty bad | 16:09 |
| jkilpatr | goldenfri, or you could just include pinning in your gpu 'driver'. This is why I think the drivers are the most important parts of Nova, its just the playbooks/ tools we already make to handle this just standardized to integrate with a management framework (cyborg api) | 16:09 |
| goldenfri | sounds good | 16:10 |
| zhipeng | shall we combine the bio slides into one ? | 16:11 |
| goldenfri | I think so | 16:11 |
| jkilpatr | I don't care too much, but I like my Saturn V picture | 16:12 |
| goldenfri | yea that is a pretty sweet picture | 16:12 |
| zhipeng | haha i like that too | 16:12 |
| zhipeng | Jim you should pick a pic as well | 16:13 |
| goldenfri | yea I will | 16:13 |
| zhipeng | we could shrink the pics to put them at the bottom of the page | 16:13 |
| zhipeng | and sqeeze the text | 16:13 |
| goldenfri | zhipeng where did you want the SWG intro slide? | 16:14 |
| zhipeng | now it is page 10 | 16:14 |
| zhipeng | i put the holder there | 16:14 |
| goldenfri | oh wait I see it | 16:15 |
| goldenfri | I'll add add something about using the gpu drivers for KVM turning later today, I think that is pretty compelling. | 16:16 |
| jkilpatr | goldenfri, the point we're trying to get across is that cyborg drivers can be for anything you want to do to accelerate instances, if it means finding a non numa compute for your program that's great, write one. | 16:17 |
| goldenfri | yea I think that is very important | 16:18 |
| jkilpatr | by providing a framework that's good enough to work with arbitrary accelerators it has to be good enough to do basic tunings, so we may as well make them drivers too so they can take advantage of the management framework | 16:18 |
| jkilpatr | at a high level cyborg is a scripting standard and scripting management engine. | 16:18 |
| zhipeng | and in that thought, Cinder should be this way as well :P | 16:20 |
| zhipeng | all the device mgmt modules should be designed this way | 16:21 |
| goldenfri | :) | 16:21 |
| jkilpatr | zhipeng, see how I slipped in the driver on slide 17 | 16:24 |
| jkilpatr | the diagram as problems because if we draw enough lines to cover everything we have a blob not a slide. | 16:25 |
| zhipeng | haha yes | 16:25 |
| zhipeng | #endmeeting | 16:55 |
| openstack | Meeting ended Wed May 3 16:55:25 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:55 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-05-03-15.02.html | 16:55 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-05-03-15.02.txt | 16:55 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-05-03-15.02.log.html | 16:55 |
| zhipeng | almost forgot ... | 16:55 |
| *** mikeH_ has quit IRC | 16:55 | |
| *** zhipeng has quit IRC | 16:56 | |
| *** mikeH_ has joined #openstack-cyborg | 16:58 | |
| jkilpatr | good catch | 17:08 |
| -openstackstatus- NOTICE: Gerrit on review.openstack.org is being restarted to accomodate a memory leak in Gerrit. Service should return shortly. | 18:52 | |
| *** crushil has quit IRC | 19:39 | |
| *** crushil has joined #openstack-cyborg | 19:53 | |
| *** jkilpatr has quit IRC | 22:05 | |
| *** jkilpatr has joined #openstack-cyborg | 22:39 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!