| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2017-04-26 | |||
| 15:27:37 | zhipeng | to move things along | |
| 15:27:50 | zhipeng | do we have any spec that we think is LGTM ? | |
| 15:28:00 | zhipeng | justin's agent one ? | |
| 15:28:21 | _gryf | more or less | |
| 15:29:02 | _gryf | probably we'll update that bp if needed during implementation | |
| 15:29:12 | zhipeng | _gryf good thinking | |
| 15:29:35 | zhipeng | I think next week we could look to freeze yours, justin's and crushil's spec | |
| 15:31:32 | zhipeng | from the bottom of my heart really appreciate you guys's work | |
| 15:31:45 | zhipeng | it has been amazing to see your comments | |
| 15:33:01 | zhipeng | #topic DB spec problem | |
| 15:33:30 | zhipeng | so let's switch to another problem, as I mentioned in the last meeting, Mellanox team withdrew from the DB spec | |
| 15:33:38 | zhipeng | any ideas how should we move on that topic ? | |
| 15:36:23 | zhipeng | my thinking was to take it over and grab some of the nasca design Mellanox introduced before | |
| 15:36:33 | zhipeng | or shall we start from ground on that ? | |
| 15:40:40 | zhipeng | okey i think I will try to split the nasca part out first, and put it into the sandbox | |
| 15:40:50 | zhipeng | for references of the design | |
| 15:41:53 | zhipeng | #action Howard to split out the nasca code for the sandbox, and left out the DB spec for the moment | |
| 15:45:30 | zhipeng | #topic Boston Summit | |
| 15:45:58 | zhipeng | so first item, we have a session selected at the Boston Summit | |
| 15:46:27 | zhipeng | goldenfri jkilpatr and me are the co-presenters and we are working on the slide now | |
| 15:46:51 | zhipeng | will send out to the team for a broader review once we have laid out a concrete ground | |
| 15:47:20 | _gryf | don't forget to drop the link to the recorded presentation :) | |
| 15:47:20 | zhipeng | another thing is that scientific wg has invited us to do lightening talks and short sessions | |
| 15:47:37 | zhipeng | _gryf no problem :) | |
| 15:48:18 | zhipeng | so if any of you guys will be at Boston, I would encourage you guys to present the lightening talks on behalf of the team | |
| 15:48:29 | zhipeng | crushil will you be at Boston | |
| 15:48:36 | crushil | zhipeng, No | |
| 15:48:39 | _gryf | I'm not be there | |
| 15:48:50 | NokMikeR | same here, not going. | |
| 15:48:58 | NokMikeR | There in spirit :) | |
| 15:49:12 | zhipeng | Okey :) | |
| 15:49:56 | zhipeng | anyways would love to have you guys to help introduce our work to the broader community | |
| 15:50:36 | zhipeng | #topic AoB | |
| 15:50:50 | zhipeng | floor are all yours | |
| 15:51:09 | _gryf | as a matter of fact, my division is focusing on different goals, so my involvement in openstack development dropped to 0 | |
| 15:51:36 | NokMikeR | :( | |
| 15:53:19 | zhipeng | _gryf changed to k8s ? | |
| 15:53:35 | zhipeng | oh just remember another topic, k8s is starting to draft CDI | |
| 15:53:45 | zhipeng | which is strongly related to our work here | |
| 15:53:50 | zhipeng | shall we have a voice there ? | |
| 15:54:26 | _gryf | zhipeng, nope, I'll not be contributing to k8s (at least not at my work hours) | |
| 15:55:01 | zhipeng | _gryf understood. You are always welcomed as the brain here if you have time to work on any items :) | |
| 15:56:10 | _gryf | yeah… I'm still on ITC, so you can ping me, so I might be able to help | |
| 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 | |