| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2017-04-12 | |||
| 15:28:13 | _gryf | I guess, that we can at least build a prototype with minimal changes in Nova, just to sell the idea | |
| 15:29:17 | _gryf | also communicate with nova team about that using irc/mailing list might be helpful | |
| 15:29:49 | _gryf | maybe reserving a slot for that on upcoming summit would be good (if possible, since it is not ptg) | |
| 15:31:32 | jkilpatr | I may or may not be there I haven't gotten final word yet. I didn't get a talk in :( | |
| 15:34:10 | jkilpatr | there's been some chatter about the placement API, we need look into that. | |
| 15:37:09 | _gryf | yes there is. currently it is qualitative aspect discussed (implementation already has started) | |
| 15:37:24 | _gryf | and also nested resource providers is the next topic | |
| 15:38:41 | _gryf | especially the last feature might be really interesting for us in context of exposing VF from accelerators (I assume that GPU also using virtual functions for virtualization) | |
| 15:39:26 | jkilpatr | so nova will have an api to support virtual functions? | |
| 15:40:28 | jkilpatr | also zhipengh[m] is less than 1 light minute away, looks like Saturn will know about his messages before we do. | |
| 15:40:40 | crushil | lol | |
| 15:40:48 | jkilpatr | fun fact Saturn is just over 1 light hour away. | |
| 15:41:00 | _gryf | ヽ（´ー｀） | |
| 15:42:13 | _gryf | jkilpatr, not sure about pci subsystem, but AFAIK plan was to completely map old resource handling with placement API som my cautious guess is yes | |
| 15:42:33 | _gryf | *about pci subsystem plans* | |
| 15:44:09 | jkilpatr | might work with some things, but I get the feeling a lot of work would be required to make drivers compatible with that sort of thing, like manufacturer side work. | |
| 15:46:02 | _gryf | jkilpatr, in which context? | |
| 15:46:28 | _gryf | like, in exposing right part of the virtualized (or not) subsystem to the vm via libvirt/xen/whatever? | |
| 15:47:09 | _gryf | since in the end we have to have a way to make VM to utilize accelerator | |
| 15:47:46 | _gryf | passing pci device is the simplest way, but its implementation in Nova is quite horrible | |
| 15:47:59 | jkilpatr | _gryf, ok maybe I'm confused are we talking about an api for direct pci attachment or an api to mux multiple vm's to a single physical resource | |
| 15:48:23 | _gryf | i guess both | |
| 15:48:25 | _gryf | like | |
| 15:48:58 | _gryf | some accelerators might be consumed only by one vm, since the amount of accelerated functions is… one | |
| 15:49:35 | _gryf | in that case one of the possible way for attachment to the VM is through PCI | |
| 15:50:18 | _gryf | or sort of SR-IOV-like, which basically are the same as PCI passthrough | |
| 15:51:19 | _gryf | otoh, we can have an accelerator which provides several VF (or some other way, like exposing devices on /dev filesystem) | |
| 15:51:43 | _gryf | so there would be many-to-many relation between accelerators and VMs | |
| 15:52:57 | _gryf | what I was talking about was a way to directly attach some accelerated function (using pci pass, vf pass, device pass) to the hypervisor | |
| 15:53:45 | _gryf | on top of that we can start building "drivers" for cyborg | |
| 15:54:16 | jkilpatr | for some accelerators we need to start with 1-1 vm accelerator and wait for others to develop muxing | |
| 15:54:29 | jkilpatr | other things you can just go ahead and do it, for example most network acceleration doesn't care | |
| 15:54:30 | _gryf | every cyborg driver have to have knowledge how it may be attached to the vm | |
| 15:54:37 | _gryf | definitely | |
| 15:56:01 | _gryf | I guess network acceleration is the other type of acceleration, since we do not pass any accelerated functions to the VMs directly, but put such VM within accelerated networking functions, which neutron is handling | |
| 15:56:23 | jkilpatr | I think it's still under the scope of cyborg to make sure those functions are working | |
| 15:56:32 | jkilpatr | even if it's not a neutron thing | |
| 15:56:40 | jkilpatr | and won't that be a wonderful pattern breaker when it comes to driver design. | |
| 15:57:08 | crushil | I think we should end the meeting and we can keep talking about all this after the meeting? | |
| 15:57:44 | _gryf | I guess only zhipengh[m] can stop the meeting | |
| 15:57:52 | crushil | We can try | |
| 15:57:55 | _gryf | k | |
| 15:57:59 | _gryf | #endmeeting | |
| 15:58:05 | _gryf | ¯\(°_o)/¯ | |
| 15:58:07 | crushil | lol | |
| 15:58:21 | jkilpatr | hope zhipengh[m] is ok | |
| 15:58:31 | crushil | Ya | |
| 15:58:31 | jkilpatr | anyawys matrix should cache this for him and he can comment when he's back online | |
| 15:58:39 | _gryf | right. | |
| 16:01:05 | _gryf | ok. thank you guys. Let me update my bp regarding crushil comments, and I'll jump into another round of review. | |
| 16:09:24 | zhipengh[m] | .... Network sucks today | |
| 16:09:34 | jkilpatr | welcome back! | |
| 16:10:02 | zhipengh[m] | I've been cut off from time to time | |
| 16:11:02 | zhipengh[m] | Let me go through the minutes later lol, thank you guys for keeping up the good work | |
| 16:11:14 | zhipengh[m] | Let me end the meeting first just in case ... | |
| 16:11:23 | zhipengh[m] | #endmeeting | |
| 16:11:24 | openstack | Meeting ended Wed Apr 12 16:11:23 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 16:11:26 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-04-12-15.07.html | |
| 16:11:27 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-04-12-15.07.txt | |
| 16:11:28 | openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-04-12-15.07.log.html | |
| #openstack-cyborg - 2017-04-19 | |||
| 15:00:08 | jkilpatr | \0 hey everyone. | |
| 15:00:22 | NokMikeR | Evening | |
| 15:01:21 | zhipeng_ | #startmeeting openstack-cyborg | |
| 15:01:21 | openstack | Meeting started Wed Apr 19 15:01:21 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:23 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 15:01:25 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 15:01:34 | zhipeng_ | hey guys | |
| 15:01:45 | zhipeng_ | :) | |
| 15:02:01 | NokMikeR | Hi Howard, all. | |
| 15:03:27 | zhipeng_ | let's run through the agenda | |
| 15:04:05 | zhipeng_ | i don't see rushil here | |
| 15:07:53 | jkilpatr | did we lose zhipeng_ again? | |
| 15:08:01 | zhipeng_ | no i'm here :P | |
| 15:08:50 | zhipeng_ | okey let's go through the specs | |
| 15:09:00 | zhipeng_ | #topic spec review | |
| 15:09:33 | zhipeng_ | #link https://review.openstack.org/#/c/446091/ | |
| 15:10:18 | jkilpatr | I just replied to some comments there, we're getting down to nit picks so I'd say another round of reviews and it should be done. | |
| 15:10:24 | zhipeng_ | jkilpatr any further comments on this ? | |
| 15:10:40 | zhipeng_ | yes that is my understanding as well | |
| 15:11:37 | zhipeng_ | #link https://review.openstack.org/#/c/447257/ | |
| 15:15:29 | jkilpatr | I think Roman is has most points of interest covered there. | |
| 15:18:00 | zhipeng_ | I remember last time we discuss about how we populate the state | |
| 15:18:30 | zhipeng_ | one of the proposal is to have the agent report back to the API so that there will be no heartbeat required | |
| 15:18:39 | zhipeng_ | does Roman's comment negate that ? | |
| 15:19:09 | jkilpatr | That's the way I'm going in the agent spec now. I don't see how his comment does? | |
| 15:19:53 | zhipeng_ | i mean the comments he made on Rushil's patch | |
| 15:20:40 | jkilpatr | I'm looking at it, that nice diagram shows the agent talking to the api, if the agent reports added/removed accelerators and utilization then no heartbeat is needed | |
| 15:20:47 | jkilpatr | although you could argue that the utilization update is a heartbeat | |
| 15:30:29 | zhipeng_ | did Romen comment that the agent should not talks to the API ? | |
| 15:31:13 | jkilpatr | um looking at his diagram clearly shows the agent talking to the api | |
| 15:32:26 | zhipeng_ | ah I see | |
| 15:35:49 | zhipeng_ | okey I've got no other questions so far | |
| 15:36:28 | jkilpatr | how is the api review going? | |
| 15:36:57 | zhipeng_ | I will need to address Roman's comments as soon as possible lol | |
| 15:37:08 | zhipeng_ | too much travels recently | |
| 15:37:15 | zhipeng_ | too many | |
| 15:37:20 | jkilpatr | happens to the best of us. | |
| 15:37:44 | zhipeng_ | jkilpatr I just remember one thing need to discuss with you | |
| 15:37:52 | zhipeng_ | #topic Boston Summit | |
| 15:38:19 | zhipeng_ | jkilpatr we have a talk selected | |