| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2017-06-14 | |||
| 15:25:09 | jkilpatr | Anyways back on topic. RPC vs messaging vs direct linking | |
| 15:25:19 | zhipeng | indeed | |
| 15:25:47 | jkilpatr | rpc places the responsibility for error handling into the caller, so for example if I where to have the conductor call attach via rpc then the conductor would need to handle possible errors (at least the way I understand it) | |
| 15:26:08 | jkilpatr | in general I think API -> conductor should be RPC | |
| 15:26:19 | jkilpatr | and conductor -> agents should be message passing | |
| 15:26:32 | jkilpatr | and then agents -> drivers should be just direct linking (we import the python modules on the same machine) | |
| 15:27:06 | zhipeng | i think it makes sense on the agent->driver side | |
| 15:27:08 | jkilpatr | adding a messaging/rpc server to every driver is just bad design, what if you load 100 drivers? do you just have 100 new servers that need to run and listen | |
| 15:27:20 | zhipeng | but considering scaling problem, conductor should still rpc to agent ? | |
| 15:29:45 | jkilpatr | so rpc would be less messaging load sure, but then what if the command fails, we have to put the error handling into the conductor | |
| 15:29:51 | jkilpatr | where I'd argue it really does not belong | |
| 15:30:23 | jkilpatr | I guess we could have a wrapper to handle all failures on the agent. but I'm still not super happy with the idea. | |
| 15:30:33 | jkilpatr | opinions on this are appreciated. | |
| 15:31:28 | zhipeng | as far as I know, when we deploy cyborg, conductor is more than likely on a different node than the agent | |
| 15:31:40 | zhipeng | so even taking into consideration of the error handling | |
| 15:31:50 | zhipeng | RPC would still be a preferred choice | |
| 15:51:11 | jkilpatr | ok then. | |
| 15:52:10 | jkilpatr | I still need to figure out how oslodb works so that the conductor can save stuff out. | |
| 15:53:07 | zhipeng | right :) | |
| 15:55:26 | jkilpatr | so we should probably define when we want to merge these components, do we want to go all the way to first POC with everything in reviews? | |
| 15:56:15 | zhipeng | i think i could try | |
| 15:57:55 | jkilpatr | it's going to make all up tests a little frustrating (trying to get all the components together) but I'm fine with that. | |
| 15:59:50 | zhipeng | well we definitely will be expecting failures :P | |
| 15:59:52 | zhipeng | for sure | |
| #openstack-cyborg - 2017-06-15 | |||
| 16:37:13 | ttk2[m] | zhipengh: did you forget to end the meeting again? | |
| 20:53:22 | zhipengh[m] | Ahhh shit ... | |
| #openstack-cyborg - 2017-06-20 | |||
| 02:17:30 | zhipeng | #link https://twitter.com/nopainkiller/status/876941606846320642 | |
| 02:17:51 | zhipeng | fyi I just did a OVS Orbit podcast with Ben Plaff at LinuxCon Beijing | |
| 02:18:09 | zhipeng | on OVS and Cyborg, the episode will likely be online around early July | |
| 02:18:18 | zhipeng | would be a good publicity for Cyborg :) | |
| 02:18:43 | zhipeng | and I also update our master slide deck a bit to reflect a possible relationship between Cyborg and OVS | |
| 02:18:50 | zhipeng | as well as Cyborg and Cillium | |
| 02:21:03 | zhipeng | #link https://docs.google.com/presentation/d/1xXjqlMaXjXe7mn-iwoETGcTPnTbqCDfpaT6yqlZ8srE/edit?usp=sharing | |
| 02:21:11 | zhipeng | and if i remember correctly .. | |
| 02:21:14 | zhipeng | #endmeeting | |
| 02:21:16 | openstack | Meeting ended Tue Jun 20 02:21:14 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 02:21:17 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-06-14-15.01.html | |
| 02:21:18 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-06-14-15.01.txt | |
| 02:21:19 | openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-06-14-15.01.log.html | |
| 02:21:28 | zhipeng | lol .... | |
| #openstack-cyborg - 2017-06-21 | |||
| 14:59:16 | jkilpatr | Morning everyone. | |
| 15:01:03 | zhipeng | morning evenning | |
| 15:01:20 | zhipeng | the longest openstack team meeting will soon commence | |
| 15:01:56 | crushil | \o | |
| 15:02:53 | NokMikeR | Morning / Afternoon & Evening folks :) | |
| 15:03:14 | NokMikeR | did you close the chatbot last time? | |
| 15:03:21 | jkilpatr | some time the next day | |
| 15:03:22 | zhipeng | yes lol | |
| 15:03:25 | NokMikeR | :) | |
| 15:03:40 | jkilpatr | the cyborg team works so hard we're always meeting | |
| 15:03:45 | zhipeng | it is good that we got our own weird tradition lol | |
| 15:03:47 | NokMikeR | space is good in a recording its somewhere the listener can place their mind. | |
| 15:04:01 | zhipeng | NokMikeR exactly | |
| 15:04:07 | zhipeng | ok here we go | |
| 15:04:12 | zhuli | :P | |
| 15:04:18 | NokMikeR | <brace brace brace> | |
| 15:04:18 | openstack | Meeting started Wed Jun 21 15:04:18 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 15:04:18 | zhipeng | #startmeeting openstack-cyborg | |
| 15:04:19 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 15:04:21 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 15:04:25 | zhipeng | hey zhuli welcome | |
| 15:04:57 | zhipeng | okey on Mike's note, I want to share something in case you missed from our last super long meeting minutes | |
| 15:05:26 | zhipeng | So I met with Ben Plaff from OVS, and did an OVS Orbit episode with him, on Cyborg and OVS-DPDK | |
| 15:05:47 | zhipeng | I updated our master deck to add some materials related to ovs-dpdk | |
| 15:06:02 | zhipeng | #link https://docs.google.com/presentation/d/1xXjqlMaXjXe7mn-iwoETGcTPnTbqCDfpaT6yqlZ8srE/edit?usp=sharing | |
| 15:06:03 | jkilpatr | cool, I'll have to go and look at that. | |
| 15:06:21 | zhipeng | so the podcast will come out likely around early next month | |
| 15:06:47 | zhipeng | and given Ben's status in open source networking, I think this is a good publicity for Cyborg :) | |
| 15:07:56 | jkilpatr | Agreed, hopefully we can have something to show at that time too. | |
| 15:08:40 | zhipeng | yep :) | |
| 15:08:50 | zhipeng | ok let's move on to our original agenda | |
| 15:08:59 | zhipeng | #topic BP and coding discussion | |
| 15:09:04 | zhipeng | #link https://review.openstack.org/#/q/status:open+project:openstack/cyborg | |
| 15:09:26 | zhipeng | For the api/db spec | |
| 15:09:46 | zhipeng | I will address and provide a update for crushil and zhuli's comments | |
| 15:09:51 | zhipeng | hopefully tmr | |
| 15:10:05 | zhipeng | any other major concerns over the api spec ? | |
| 15:10:37 | jkilpatr | I'm happy with it. | |
| 15:11:03 | jkilpatr | If we're down to correcting typos it means it's mostly done | |
| 15:11:09 | zhipeng | cool | |
| 15:11:37 | zhipeng | so on the stubs patches, any outstanding issue so far ? | |
| 15:12:18 | jkilpatr | I managed to patch my pep8 errors this morning, now I'm working on transport urls and how to configure them, it's more confusing than I expected configuration to be. | |
| 15:12:34 | jkilpatr | good news is once I get that working we can have a common configuration segment that takes care of it | |
| 15:13:25 | zhipeng | great ! | |
| 15:13:42 | zhipeng | #info agent stub https://review.openstack.org/473486 | |
| 15:13:55 | zhipeng | #info conductor stub https://review.openstack.org/472662 | |
| 15:14:10 | zhipeng | #info generic driver stub https://review.openstack.org/473186 | |
| 15:15:42 | zhipeng | crushil any problems from your side ? | |
| 15:15:46 | NokMikeR | regarding the api, how aligned is it with ETSI NFV specs? | |
| 15:15:56 | crushil | Nope. I will fill out the driver as time goes by | |
| 15:15:58 | jkilpatr | should we consider going ahead and reviewing/landing the generic driver? I don't know what more we want from the dummy driver. | |
| 15:16:08 | zhipeng | I've try to align with it as much as possible | |
| 15:16:34 | zhipeng | jkilpatr I will take a look at that tmr my timezone | |
| 15:16:42 | crushil | jkilpatr, We can, but we need agent and API code completely mapped out before the generic driver can be completely filled out | |
| 15:16:58 | zhipeng | crushil actually not entirely | |
| 15:17:21 | zhipeng | you could see my definitions in the api spec | |
| 15:17:59 | zhipeng | anyways I will review and comment the patch see if we are good to go to land the first code | |
| 15:18:08 | crushil | Ok, I will fill it out this week and remove the WIP | |
| 15:18:42 | jkilpatr | crushil, yes but adding onto it in the other patches is possible. I just don't want to end up with siloed commits where everyone is waiting on everything to work so they have to keep pulling stuff into their own commits | |
| 15:18:43 | zhipeng | great | |