| *** tomoe_ has quit IRC | 00:02 | |
| *** cjellick has quit IRC | 00:03 | |
| *** alexpilotti has quit IRC | 00:05 | |
| *** thomasem has quit IRC | 00:15 | |
| *** thomasem has joined #openstack-meeting-3 | 00:15 | |
| *** thomasem has quit IRC | 00:19 | |
| *** sarob has joined #openstack-meeting-3 | 00:27 | |
| *** Sukhdev has quit IRC | 00:29 | |
| *** nati_ueno has joined #openstack-meeting-3 | 00:31 | |
| *** s3wong has quit IRC | 00:31 | |
| *** sdague has quit IRC | 00:33 | |
| *** banix has joined #openstack-meeting-3 | 00:33 | |
| *** sdague has joined #openstack-meeting-3 | 00:33 | |
| *** nedbat has joined #openstack-meeting-3 | 00:34 | |
| *** nati_ueno has quit IRC | 00:43 | |
| *** nati_ueno has joined #openstack-meeting-3 | 00:47 | |
| *** carl_baldwin has quit IRC | 00:47 | |
| *** markmcclain has quit IRC | 00:48 | |
| *** nati_ueno has quit IRC | 00:50 | |
| *** nati_ueno has joined #openstack-meeting-3 | 00:54 | |
| *** tomoe_ has joined #openstack-meeting-3 | 01:06 | |
| *** seizadi has quit IRC | 01:08 | |
| *** nati_ueno has quit IRC | 01:09 | |
| *** tomoe_ has left #openstack-meeting-3 | 01:13 | |
| *** sarob has quit IRC | 01:21 | |
| *** flaviof is now known as flaviof_zzz | 01:37 | |
| *** sarob has joined #openstack-meeting-3 | 01:38 | |
| *** clu_ has quit IRC | 01:39 | |
| *** sarob has quit IRC | 01:42 | |
| *** sarob has joined #openstack-meeting-3 | 01:46 | |
| *** nelsnelson has quit IRC | 01:49 | |
| *** HenryG has joined #openstack-meeting-3 | 01:58 | |
| *** thomasem has joined #openstack-meeting-3 | 01:59 | |
| *** thomasem has quit IRC | 02:04 | |
| *** devlaps1 has quit IRC | 02:25 | |
| *** pgpus has joined #openstack-meeting-3 | 02:29 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 02:30 | |
| *** nedbat has quit IRC | 02:30 | |
| *** gcb has joined #openstack-meeting-3 | 02:44 | |
| *** sankarshan is now known as sankarshan_away | 02:45 | |
| *** seizadi has joined #openstack-meeting-3 | 02:47 | |
| *** seizadi has quit IRC | 02:55 | |
| *** sarob has quit IRC | 02:56 | |
| *** sarob has joined #openstack-meeting-3 | 02:56 | |
| *** sarob has quit IRC | 03:01 | |
| *** pballand has joined #openstack-meeting-3 | 03:07 | |
| *** gcb has quit IRC | 03:12 | |
| *** pgpus has quit IRC | 03:12 | |
| *** yamahata has joined #openstack-meeting-3 | 03:15 | |
| *** sankarshan_away is now known as sankarshan | 03:15 | |
| *** yamahata has quit IRC | 03:16 | |
| *** otherwiseguy has joined #openstack-meeting-3 | 03:16 | |
| *** gcb has joined #openstack-meeting-3 | 03:24 | |
| *** carl_baldwin has quit IRC | 03:26 | |
| *** sarob has joined #openstack-meeting-3 | 03:27 | |
| *** sarob_ has joined #openstack-meeting-3 | 03:29 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 03:29 | |
| *** lcheng has joined #openstack-meeting-3 | 03:30 | |
| *** sarob__ has joined #openstack-meeting-3 | 03:30 | |
| *** sarob has quit IRC | 03:31 | |
| *** sarob_ has quit IRC | 03:33 | |
| *** sarob__ has quit IRC | 03:35 | |
| *** yamahata has joined #openstack-meeting-3 | 03:35 | |
| *** sarob has joined #openstack-meeting-3 | 03:50 | |
| *** lcheng has quit IRC | 04:14 | |
| *** pballand has quit IRC | 04:33 | |
| *** otherwiseguy has quit IRC | 04:34 | |
| *** otherwiseguy has joined #openstack-meeting-3 | 04:34 | |
| *** coolsvap|afk is now known as coolsvap | 04:36 | |
| *** carl_baldwin has quit IRC | 04:45 | |
| *** banix has quit IRC | 04:45 | |
| *** coolsvap is now known as coolsvap|afk | 04:46 | |
| *** coolsvap|afk is now known as coolsvap | 04:53 | |
| *** sarob has quit IRC | 04:55 | |
| *** sarob has joined #openstack-meeting-3 | 04:55 | |
| *** sarob has quit IRC | 04:59 | |
| *** otherwiseguy has quit IRC | 05:05 | |
| *** emagana has joined #openstack-meeting-3 | 05:06 | |
| *** seizadi has joined #openstack-meeting-3 | 05:15 | |
| *** emagana has quit IRC | 05:18 | |
| *** emagana has joined #openstack-meeting-3 | 05:18 | |
| *** emaganap has joined #openstack-meeting-3 | 05:19 | |
| *** emagana has quit IRC | 05:23 | |
| *** sarob has joined #openstack-meeting-3 | 05:30 | |
| *** sarob has quit IRC | 05:34 | |
| *** emaganap has quit IRC | 05:46 | |
| *** emagana has joined #openstack-meeting-3 | 05:47 | |
| *** emaganap has joined #openstack-meeting-3 | 05:48 | |
| *** emagana has quit IRC | 05:51 | |
| *** emaganap has quit IRC | 05:58 | |
| *** emagana has joined #openstack-meeting-3 | 05:59 | |
| *** sarob has joined #openstack-meeting-3 | 06:00 | |
| *** emagana has quit IRC | 06:03 | |
| *** sarob has quit IRC | 06:05 | |
| *** jtomasek has joined #openstack-meeting-3 | 06:07 | |
| *** jtomasek has quit IRC | 06:07 | |
| *** jtomasek has joined #openstack-meeting-3 | 06:12 | |
| *** seizadi has quit IRC | 06:25 | |
| *** lcheng has joined #openstack-meeting-3 | 06:26 | |
| *** sarob has joined #openstack-meeting-3 | 06:30 | |
| *** sarob has quit IRC | 06:35 | |
| *** jamie_h has joined #openstack-meeting-3 | 06:37 | |
| *** jamie_h has quit IRC | 06:39 | |
| *** jamie_h has joined #openstack-meeting-3 | 06:39 | |
| *** jamie_h_ has joined #openstack-meeting-3 | 06:50 | |
| *** jcoufal has joined #openstack-meeting-3 | 06:51 | |
| *** jamie_h has quit IRC | 06:51 | |
| *** jamie_h_ has quit IRC | 06:55 | |
| *** jamie_h has joined #openstack-meeting-3 | 06:56 | |
| *** jamie_h is now known as jamiehannaford | 06:56 | |
| *** jtomasek has quit IRC | 07:08 | |
| *** jtomasek has joined #openstack-meeting-3 | 07:09 | |
| *** catherine_d has joined #openstack-meeting-3 | 07:17 | |
| *** mrunge has joined #openstack-meeting-3 | 07:17 | |
| *** catherine_d has left #openstack-meeting-3 | 07:18 | |
| *** sarob has joined #openstack-meeting-3 | 07:29 | |
| *** sarob has quit IRC | 07:33 | |
| *** ttrifonov_zZzz is now known as ttrifonov | 07:39 | |
| *** jtomasek has quit IRC | 08:00 | |
| *** nelsnelson has joined #openstack-meeting-3 | 08:03 | |
| *** jtomasek has joined #openstack-meeting-3 | 08:05 | |
| *** MaxV has joined #openstack-meeting-3 | 08:19 | |
| *** safchain has joined #openstack-meeting-3 | 08:26 | |
| *** sarob has joined #openstack-meeting-3 | 08:28 | |
| *** sarob_ has joined #openstack-meeting-3 | 08:30 | |
| *** sarob has quit IRC | 08:33 | |
| *** sarob_ has quit IRC | 08:35 | |
| *** gcb has quit IRC | 08:38 | |
| *** amotoki has joined #openstack-meeting-3 | 08:46 | |
| *** igordcard has joined #openstack-meeting-3 | 08:47 | |
| *** gcb has joined #openstack-meeting-3 | 08:52 | |
| *** samchoi has joined #openstack-meeting-3 | 09:10 | |
| *** sankarshan is now known as sankarshan_away | 09:16 | |
| *** samchoi has quit IRC | 09:18 | |
| *** jamie_h has joined #openstack-meeting-3 | 09:26 | |
| *** jamie_h has quit IRC | 09:28 | |
| *** jamie_h has joined #openstack-meeting-3 | 09:28 | |
| *** sarob has joined #openstack-meeting-3 | 09:29 | |
| *** jamiehannaford has quit IRC | 09:29 | |
| *** jamie_h has quit IRC | 09:29 | |
| *** enykeev has quit IRC | 09:29 | |
| *** jamiehannaford has joined #openstack-meeting-3 | 09:30 | |
| *** sarob has quit IRC | 09:33 | |
| *** nedbat has joined #openstack-meeting-3 | 09:37 | |
| *** enykeev has joined #openstack-meeting-3 | 09:38 | |
| *** kashyap has left #openstack-meeting-3 | 09:44 | |
| *** enykeev has quit IRC | 09:48 | |
| *** coolsvap is now known as coolsvap|afk | 09:50 | |
| *** gcb has quit IRC | 09:54 | |
| *** MaxV_ has joined #openstack-meeting-3 | 09:55 | |
| *** MaxV has quit IRC | 09:56 | |
| *** lcheng has quit IRC | 10:15 | |
| *** yamahata has quit IRC | 10:23 | |
| *** HenryG has quit IRC | 10:25 | |
| *** sarob has joined #openstack-meeting-3 | 10:29 | |
| *** sarob has quit IRC | 10:33 | |
| *** MaxV_ has quit IRC | 10:35 | |
| *** julim has joined #openstack-meeting-3 | 10:57 | |
| *** jtomasek_ has joined #openstack-meeting-3 | 11:12 | |
| *** lblanchard has joined #openstack-meeting-3 | 11:13 | |
| *** jtomasek has quit IRC | 11:14 | |
| *** maurosr has quit IRC | 11:18 | |
| *** MaxV has joined #openstack-meeting-3 | 11:18 | |
| *** krotscheck has quit IRC | 11:19 | |
| *** maurosr has joined #openstack-meeting-3 | 11:19 | |
| *** krotscheck has joined #openstack-meeting-3 | 11:21 | |
| *** s1rp has quit IRC | 11:34 | |
| *** s1rp has joined #openstack-meeting-3 | 11:34 | |
| *** HenryG has joined #openstack-meeting-3 | 11:43 | |
| *** yamahata has joined #openstack-meeting-3 | 11:47 | |
| *** MaxV has quit IRC | 11:51 | |
| *** nedbat has quit IRC | 11:53 | |
| *** s1rp_ has joined #openstack-meeting-3 | 11:54 | |
| *** MaxV has joined #openstack-meeting-3 | 11:54 | |
| *** sankarshan_away is now known as sankarshan | 11:54 | |
| *** rossella has joined #openstack-meeting-3 | 11:55 | |
| *** s1rp has quit IRC | 11:55 | |
| *** rossella_s has quit IRC | 11:55 | |
| *** rossella is now known as rossella_s | 11:55 | |
| *** anteaya has quit IRC | 11:58 | |
| *** safchain has quit IRC | 12:00 | |
| *** safchain has joined #openstack-meeting-3 | 12:01 | |
| *** mrunge has quit IRC | 12:07 | |
| *** nedbat has joined #openstack-meeting-3 | 12:18 | |
| *** jamiehannaford has quit IRC | 12:18 | |
| *** jamiehannaford has joined #openstack-meeting-3 | 12:19 | |
| *** nedbat has quit IRC | 12:22 | |
| *** jamiehan_ has joined #openstack-meeting-3 | 12:22 | |
| *** jamiehannaford has quit IRC | 12:24 | |
| *** sarob has joined #openstack-meeting-3 | 12:29 | |
| *** sarob has quit IRC | 12:33 | |
| *** anteaya has joined #openstack-meeting-3 | 12:39 | |
| *** flaviof_zzz has quit IRC | 12:46 | |
| *** DinaBelova2 has joined #openstack-meeting-3 | 12:46 | |
| *** DinaBelova has quit IRC | 12:48 | |
| *** DinaBelova2 is now known as DinaBelova | 12:48 | |
| *** edleafe has quit IRC | 12:51 | |
| *** mwagner_lap has quit IRC | 12:52 | |
| *** edleafe has joined #openstack-meeting-3 | 12:54 | |
| *** flaviof has joined #openstack-meeting-3 | 12:56 | |
| *** jrist has quit IRC | 13:01 | |
| *** jrist has joined #openstack-meeting-3 | 13:02 | |
| *** jcoufal has quit IRC | 13:03 | |
| *** peristeri has joined #openstack-meeting-3 | 13:26 | |
| *** lenrow has joined #openstack-meeting-3 | 13:29 | |
| *** devlaps has joined #openstack-meeting-3 | 13:29 | |
| *** davlaps has joined #openstack-meeting-3 | 13:29 | |
| *** sarob has joined #openstack-meeting-3 | 13:29 | |
| *** nedbat has joined #openstack-meeting-3 | 13:30 | |
| *** jcoufal has joined #openstack-meeting-3 | 13:31 | |
| *** dlenrow has quit IRC | 13:32 | |
| *** sarob has quit IRC | 13:33 | |
| *** lenrow has quit IRC | 13:34 | |
| *** lenrow has joined #openstack-meeting-3 | 13:35 | |
| *** thomasem has joined #openstack-meeting-3 | 13:35 | |
| *** jackib has joined #openstack-meeting-3 | 13:37 | |
| *** coolsvap|afk is now known as coolsvap | 13:38 | |
| *** jackib has quit IRC | 13:38 | |
| *** jackib has joined #openstack-meeting-3 | 13:38 | |
| *** briancurtin has left #openstack-meeting-3 | 13:46 | |
| *** yamahata has quit IRC | 13:47 | |
| *** yamahata has joined #openstack-meeting-3 | 13:47 | |
| *** jaypipes has joined #openstack-meeting-3 | 13:49 | |
| *** pgpus has joined #openstack-meeting-3 | 13:52 | |
| *** jackib has quit IRC | 13:58 | |
| *** xuhanp has joined #openstack-meeting-3 | 14:03 | |
| *** armax has joined #openstack-meeting-3 | 14:04 | |
| *** mwagner_lap has joined #openstack-meeting-3 | 14:14 | |
| *** devlaps has left #openstack-meeting-3 | 14:17 | |
| *** jtomasek_ has quit IRC | 14:21 | |
| *** otherwiseguy has joined #openstack-meeting-3 | 14:24 | |
| *** jamiehan_ has quit IRC | 14:28 | |
| *** jamiehannaford has joined #openstack-meeting-3 | 14:28 | |
| *** sarob has joined #openstack-meeting-3 | 14:29 | |
| *** sarob has quit IRC | 14:33 | |
| *** seizadi has joined #openstack-meeting-3 | 14:42 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 14:46 | |
| *** yamamoto has joined #openstack-meeting-3 | 14:59 | |
| *** Sukhdev has joined #openstack-meeting-3 | 14:59 | |
| *** seizadi has quit IRC | 15:00 | |
| *** ndipanov has quit IRC | 15:02 | |
| *** MaxV has quit IRC | 15:03 | |
| *** MaxV has joined #openstack-meeting-3 | 15:03 | |
| *** mfer has joined #openstack-meeting-3 | 15:11 | |
| *** cjellick has joined #openstack-meeting-3 | 15:15 | |
| *** samchoi has joined #openstack-meeting-3 | 15:22 | |
| *** pballand has joined #openstack-meeting-3 | 15:28 | |
| *** sarob has joined #openstack-meeting-3 | 15:29 | |
| mfer | #startmeeting openstack-sdk-php | 15:30 |
|---|---|---|
| openstack | Meeting started Wed Jun 11 15:30:09 2014 UTC and is due to finish in 60 minutes. The chair is mfer. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:30 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:30 |
| *** openstack changes topic to " (Meeting topic: openstack-sdk-php)" | 15:30 | |
| openstack | The meeting name has been set to 'openstack_sdk_php' | 15:30 |
| mfer | Welcome everyone. Please state your name along with any applicable associations | 15:30 |
| mfer | Matt Farina, HP | 15:30 |
| samchoi | Sam Choi, HP | 15:30 |
| jamiehannaford | Jamie Hannaford, Rackspace | 15:30 |
| mfer | jamiehannaford anyone else from your side of the fence joining us today? | 15:31 |
| jamiehannaford | no I don't think so | 15:31 |
| jamiehannaford | Glen and Shaunak are at confs | 15:31 |
| mfer | ooo, I hope they are having fun | 15:32 |
| mfer | #topic agenda | 15:32 |
| *** openstack changes topic to "agenda (Meeting topic: openstack-sdk-php)" | 15:32 | |
| mfer | #link https://wiki.openstack.org/wiki/Meetings/OpenStack-SDK-PHP | 15:32 |
| mfer | 1. Intro to the PHP SDK if there is anyone new? (mfer) | 15:32 |
| mfer | 2. Reviews in progress - any questions/concerns? (samchoi) | 15:32 |
| mfer | 3. How are we going to handle transport state (like base URLs) for services and resource models? (jamiehannaford) | 15:32 |
| mfer | 4. Do `RemoteObject' and `Object' need to be separate classes? (jamiehannaford) | 15:32 |
| mfer | anything else we should add or remove from the agenda? | 15:32 |
| samchoi | that looks fine to me, it's somewhat shorter than usual so we can have open discussion | 15:33 |
| jamiehannaford | I have nothing else to add - we have a few lingering topics on the mailing list | 15:33 |
| mfer | ok | 15:33 |
| *** sarob has quit IRC | 15:33 | |
| mfer | I think we can skip 1 because we have no one else new. I think for next week we can drop it and address anyone new when we are lucky enough to have them | 15:34 |
| mfer | #topic Reviews in progress - any questions/concerns? (samchoi) | 15:34 |
| *** openstack changes topic to "Reviews in progress - any questions/concerns? (samchoi) (Meeting topic: openstack-sdk-php)" | 15:34 | |
| mfer | samchoi since you brought this one up care to kick us off? | 15:34 |
| *** xuhanp has quit IRC | 15:34 | |
| *** lcheng has joined #openstack-meeting-3 | 15:34 | |
| samchoi | mfer, I left it on the agenda primarily in case there were additional concerns about open reviews | 15:35 |
| *** seizadi has joined #openstack-meeting-3 | 15:35 | |
| jamiehannaford | does anyone have any objections to https://review.openstack.org/#/c/92280/ | 15:35 |
| mfer | jamiehannaford two things. 1) I need to give that one more review. It's on my todo list for today. 2) the commit message needs to say what the commit does rather than the last change he made to it. | 15:36 |
| samchoi | last I checked the sphinx review, it looked pretty good | 15:37 |
| samchoi | I'll take another look today though | 15:37 |
| samchoi | that was previously lower on my priorities since it didn't block other work | 15:37 |
| jamiehannaford | mfer yeah I agree about commit msg - I don't know whether Shaunak squashed previous ones | 15:37 |
| jamiehannaford | how about this one: https://review.openstack.org/#/c/99283/ | 15:37 |
| mfer | i'm not exactly sure. luckly, gerrit lets us change that in the UI now | 15:37 |
| *** pballand has quit IRC | 15:38 | |
| mfer | conceptually I have no issue with it. Just need to do a review of it. | 15:38 |
| *** jcoufal has quit IRC | 15:38 | |
| *** jcoufal has joined #openstack-meeting-3 | 15:38 | |
| mfer | Did any of the relevant docs get updated about the autoloader? I'm not sure where it's at in there | 15:38 |
| jamiehannaford | which docs do you mean? | 15:39 |
| mfer | for example the README.rst file refers to the autoloader | 15:40 |
| jamiehannaford | I'll go through again and replace mentions in the docs | 15:40 |
| mfer | the only one I'd like to discuss conceptually is https://review.openstack.org/#/c/97482/ which I believe we have as a later topic | 15:41 |
| mfer | other than that it's just code reviews on my end | 15:41 |
| jamiehannaford | okay - I don't think there's much point reviewing that until URL one is +2ed | 15:41 |
| mfer | yeah, that's another one I'm conceptually with but need to code review | 15:42 |
| samchoi | so regarding this, are we in agreement that the availability of Composer is assumed? | 15:42 |
| mfer | i have a chunk of time today and tomorrow alotted to do code reviews of these things | 15:42 |
| jamiehannaford | samchoi yes because there's no other way to install our dependencies | 15:42 |
| samchoi | t97482 looks fine to me | 15:42 |
| mfer | samchoi composer or another PSR enabled autoloader (like the symfony one). autoloading is shifted as a responsibility to the consumer | 15:43 |
| samchoi | ok, I was trying to be cautious even though this review seems quite straightforward | 15:43 |
| samchoi | thanks | 15:43 |
| jamiehannaford | the other patch is https://review.openstack.org/#/c/99303/ | 15:43 |
| *** xuhanp has joined #openstack-meeting-3 | 15:43 | |
| jamiehannaford | this was discussed very briefly on irc a week or so back | 15:43 |
| mfer | I think the question on autoloading is a good one. There are still a lot of apps that don't use composer. For them we should have some documentation on autoloading to point them in the right direction. | 15:44 |
| *** banix has joined #openstack-meeting-3 | 15:44 | |
| mfer | jamiehannaford i remember that. i'm fine with the idea as I said then. Glad to see you put some code to it. I'll review that when I'm going through all the other stuff | 15:44 |
| *** rhagarty has quit IRC | 15:44 | |
| mfer | samchoi jamiehannaford do you have anything else on these? it sounds like we just need to put time in reviewing code | 15:45 |
| *** xuhanp has quit IRC | 15:46 | |
| samchoi | yes, that sounds about right | 15:46 |
| mfer | then I think we can move on | 15:48 |
| mfer | #topic How are we going to handle transport state (like base URLs) for services and resource models? (jamiehannaford) | 15:48 |
| *** openstack changes topic to "How are we going to handle transport state (like base URLs) for services and resource models? (jamiehannaford) (Meeting topic: openstack-sdk-php)" | 15:48 | |
| mfer | jamiehannaford care to start this one off? | 15:48 |
| jamiehannaford | based on the mailing list, I like the idea of a stateless transport client | 15:49 |
| jamiehannaford | one thing I was wondering about is how we're going to manage service-specific transport state like endpoint URLs and default headers | 15:49 |
| *** rhagarty has joined #openstack-meeting-3 | 15:50 | |
| jamiehannaford | I don't think a service client or resource model should hold that state, because it's transport-related. But I also agree we shouldn't have it inside the transport client either because it needs to be re-usable | 15:50 |
| mfer | I was asking myself the same question. I know how I've done it in the past. Yesterday I started digging into how others do it in both PHP and other languages. | 15:50 |
| mfer | I don't think I have an answer yet but it's a question I started asking even before you put this on here | 15:51 |
| jamiehannaford | I had an idea | 15:51 |
| *** yisun has joined #openstack-meeting-3 | 15:51 | |
| mfer | or I saw it on here anyway | 15:51 |
| mfer | ya | 15:51 |
| mfer | '? | 15:51 |
| jamiehannaford | I know people aren't comfortable with event subscribers (because it's all a bit abstract with no code), but we could have a subscriber that adds in a base URL/default header array onto a request when its prepared | 15:51 |
| jamiehannaford | so it waits until before a request is sent, then modifies the URL with the endpoint domain | 15:52 |
| jamiehannaford | that subscriber class would hold the responsibility of adding custom details to requests before they're sent | 15:53 |
| mfer | that's similar to what pkgcloud does with the request lib. The default headers are added via events. the url endpoint is handled with a method. | 15:53 |
| jamiehannaford | awesome | 15:53 |
| jamiehannaford | that's pretty much what I was thinking | 15:53 |
| jamiehannaford | you could have another subscriber for controlling authentication | 15:53 |
| mfer | i'm not entirely sure of doing it this way mostly because 1) I'd like to do some more reserch and 2) If we don't go with a service and resource model approach I'd like to know what that means. I say #2 because the python SDK moved away from it so I'd like to be smart about our approach and talk with them and others on it. | 15:54 |
| jamiehannaford | sure | 15:55 |
| jamiehannaford | if we didn't have a service class with affiliated domain models - what would we use instead? | 15:55 |
| jamiehannaford | I know pyrax has the concept of managers | 15:55 |
| mfer | so, before we start coding to something like this we (and I'm happy to do this but I hope others will as well) should do some legwork. | 15:55 |
| mfer | the python SDK is doing something where a class has both state and behavior | 15:56 |
| mfer | so, you call a method on a class with state to affect it | 15:56 |
| jamiehannaford | hmm | 15:56 |
| mfer | so, $object->save() rather than $manager->save($object) | 15:56 |
| mfer | that kind of idea anyway | 15:56 |
| samchoi | I've been tracking the python sdk's design/progress...I'll reach out to their group as well after I get a better feel for their library | 15:57 |
| mfer | yay | 15:57 |
| mfer | cross language sharing :) | 15:57 |
| jamiehannaford | that's we're doing on the current SDK - you'd have a domain model like $container that contains both state and behaviour | 15:57 |
| jamiehannaford | we also have to bear in mind that some things idiomatic in python might not work well in PHP | 15:58 |
| samchoi | jamiehannaford: yea will keep that in mind as well. It's been interesting though because I've had to write/edit both styles. The internal SDK I've worked on uses managers. | 15:58 |
| samchoi | Honestly, I'm not sure if there's truly a clear benefit to either approach at this point. | 15:59 |
| mfer | I've worked on stuff that uses both. Lately I've been following the philosophical debate on how to handle this stuff and the development community is not in agreement | 15:59 |
| *** armax has left #openstack-meeting-3 | 16:00 | |
| jamiehannaford | I think we should think about it more over this week | 16:00 |
| *** MaxV has quit IRC | 16:00 | |
| mfer | how about this, can the three of us take an action to dig into this topic and come back and discuss it when we have more to talk about? | 16:00 |
| samchoi | sure, it's already in progress for me | 16:00 |
| mfer | If Shanuk or Glen are up for digging into this too I'd love to hear their thoughts | 16:01 |
| jamiehannaford | I'll look into the topic of whether a class should both contain state and perform tasks/behaviour | 16:01 |
| *** carl_baldwin is now known as Swami | 16:01 | |
| jamiehannaford | mfer I'll point them to this week's meeting logs so they can weigh in | 16:01 |
| mfer | thanks | 16:01 |
| *** Swami is now known as carl_baldwin | 16:01 | |
| mfer | should we move on to the next topic or is there something else here? | 16:02 |
| jamiehannaford | is it also worth maybe having a small proof of concept? relating to my idea of the event subscribers | 16:02 |
| jamiehannaford | or wait until next week | 16:02 |
| jamiehannaford | when we've researched more | 16:02 |
| mfer | jamiehannaford if you want to that's fine. I'm familiar with the concept to the point that I don't need an example to understand it. | 16:03 |
| mfer | it might be useful for others though | 16:03 |
| samchoi | sounds like we're a bit undecided on the resource/manager design vs what the python SDK has done. Fine with moving on | 16:03 |
| jamiehannaford | fine with moving on too | 16:03 |
| mfer | #topic Do `RemoteObject' and `Object' need to be separate classes? (jamiehannaford) | 16:04 |
| *** openstack changes topic to "Do `RemoteObject' and `Object' need to be separate classes? (jamiehannaford) (Meeting topic: openstack-sdk-php)" | 16:04 | |
| mfer | jamiehannaford would you care to take this away? | 16:04 |
| jamiehannaford | at the moment I don't really understand the separation - do we need 2 separate classes for 1 API resource? | 16:05 |
| mfer | so.... the person who wrote that isn't here. I don't really have an opinion on it. | 16:05 |
| mfer | if you want to try to merge them cleanly into one that seems fine to me | 16:06 |
| samchoi | mfer: took the words out of my mouth | 16:06 |
| jamiehannaford | okay, I'll try and take that on next week | 16:06 |
| mfer | that was easy! yay for easy topics | 16:06 |
| mfer | is there anything else on this or should we move to open discussion time? | 16:06 |
| samchoi | jamiehannaford: mentioned there are several mailing list topics open so seems like a good opportunity to move on | 16:07 |
| jamiehannaford | I'm fine with moving on | 16:07 |
| mfer | #topic open discussion | 16:08 |
| *** openstack changes topic to "open discussion (Meeting topic: openstack-sdk-php)" | 16:08 | |
| samchoi | so it looks like we briefly discussed the transport layer topic... | 16:09 |
| samchoi | leaving us with a discussion on testing approaches (Behat) and philosophies on how users extend the library right? Or was there something else? | 16:10 |
| jamiehannaford | I think that's it | 16:10 |
| *** pgpus has quit IRC | 16:11 | |
| jamiehannaford | so I know folks have concerns with using a BDD tool like behat - shall we go over them? | 16:11 |
| jamiehannaford | one of them was "we don't have business analysts, testers or non-coders - so we don't need BDD" | 16:11 |
| samchoi | sure, good topic to cover now | 16:11 |
| mfer | sure | 16:12 |
| jamiehannaford | so, for me, the main point of using a human-readable language was that it improves communication for EVERYONE on the project | 16:12 |
| jamiehannaford | it allows to collaborate and really pin down what features are going to look like | 16:12 |
| jamiehannaford | so we have a clear idea of what we're coding | 16:13 |
| jamiehannaford | there's nothing worse than spending hours coding a new feature only to realize it has nothing in common with what somebody else had in mind | 16:13 |
| jamiehannaford | BDD is about improving that communication | 16:13 |
| jamiehannaford | and defining features - it's that simple | 16:13 |
| jamiehannaford | here's an example I drafted up for a few Swift features - very rudimentary https://gist.github.com/jamiehannaford/73271df790a6cbb5f940 | 16:13 |
| samchoi | So I think the first thing we should clear up is, are we all in agreement that the php sdk's end users are all developers then? | 16:14 |
| jamiehannaford | we can't make that assumption | 16:15 |
| jamiehannaford | the honest answer is that we don't know who will use our SDK | 16:15 |
| mfer | jamiehannaford who else besides a developer would use the SDK? | 16:15 |
| mfer | and why or how? | 16:15 |
| samchoi | Well given that this is an sdk...I'm wondering who else would realistically use this. I polled members of other sdk teams as well on this matter. | 16:15 |
| mfer | i'm trying to understand where alternatices would come from | 16:16 |
| jamiehannaford | "developer" is not a defined thing, it's a label attached to a wide variety of people with different skillsets | 16:16 |
| jamiehannaford | but that's not really the point | 16:16 |
| jamiehannaford | BDD is about communication on our team | 16:17 |
| jamiehannaford | and understanding how end-users (whoever they are) will use our SDK | 16:17 |
| mfer | BDD is also about process and having a team of people use that process. | 16:17 |
| jamiehannaford | no, BDD is about improving communication | 16:17 |
| mfer | if a team of contributors isn't really interested in that process it's going to have a hard time happening | 16:17 |
| jamiehannaford | what's more important than having good communication on a development team? | 16:18 |
| jamiehannaford | to give you an example: | 16:18 |
| jamiehannaford | the RemoteObject and Object classes | 16:18 |
| jamiehannaford | I still have no idea what they really do | 16:18 |
| jamiehannaford | there's a communication gap there - and any time I spend trying to understand, refactor or undo that miscommunication is time we can better spend | 16:19 |
| jamiehannaford | all I'm saying is that it'd be really cool to have a way to define features consistently and easily | 16:19 |
| mfer | So, when you read the docs at https://github.com/stackforge/openstack-sdk-php/blob/master/src/OpenStack/ObjectStore/v1/Resource/Object.php#L23 you didn't know what the class did? | 16:20 |
| samchoi | I would also mention that from the polling I've done, similar contributors don't seem interested in using a BDD framework for an SDK. After hearing back from a number of guys working on other OpenStack SDKs, I was surprised to see that none of them thought using a BDD framework made sense for an OpenStack SDK | 16:20 |
| jamiehannaford | I didn't understand the reason for separating a "remote object" from an "object" - why that decision was ever made | 16:20 |
| mfer | jamiehannaford ah. i get that question. | 16:21 |
| jamiehannaford | all behat is doing is opening up that decision making process (what goes into a feature) so we don't waste time | 16:22 |
| mfer | jamiehannaford so, the openstack community puts a lot of process in place. most of it so big giant companies can play nicely together. putting this in place would be additional process that other projects in openstack (or PHP in general) aren't doing. That means the people involved need to be sold on doing things this way. | 16:22 |
| mfer | it's a process (it may be a communication process) but it's still process | 16:22 |
| jamiehannaford | two things: | 16:22 |
| jamiehannaford | 1. I don't understand the "well other people aren't doing it" argument - it's cropped up a lot (and even figured in the stateless transport client debate). We should decide based on the merits of something, not by following others | 16:23 |
| jamiehannaford | 2. there are projects inside Rackspace that have been extremely successfuly using BDD/Cucumber | 16:23 |
| *** jcoufal has quit IRC | 16:23 | |
| *** cjellick has quit IRC | 16:23 | |
| mfer | jamiehannaford those are good things to bring up. let's talk about them | 16:23 |
| *** seizadi1 has joined #openstack-meeting-3 | 16:24 | |
| *** cjellick has joined #openstack-meeting-3 | 16:24 | |
| *** seizadi has quit IRC | 16:24 | |
| samchoi | jamiehannaford: to be clear, this isn't about other people using it. Based on the info I've received, nobody else supports using a BDD framework for an OpenStack SDK at the moment. Going back to Matt's point, there would be no support to using this process were it to be put in place. | 16:24 |
| jamiehannaford | samchoi what do you mean by "no support to using this process"? | 16:25 |
| samchoi | I had some extended conversations with contributors to other SDKs and they made a decision not to use a BDD framework | 16:25 |
| jamiehannaford | we'd write the files and run a script | 16:25 |
| mfer | for #1 I'm not opposed to doing different than popular things on the technology front. When it comes to project process I'm a little more skeptical. If we introduce something really different from the other projects we should be excited about it. I'm just not finding that in myself or the others I've talked with. Putting process in place for contributors (and volunteers in some cases) in addition to the hoops we already have | 16:25 |
| mfer | needs some excitement we can share and get behind | 16:25 |
| *** davlaps has quit IRC | 16:25 | |
| jamiehannaford | samchoi could you share those conversations on the mailing list? I'm genuinely interested in the counter-arguments | 16:25 |
| samchoi | I can share some of the insights right now actually | 16:26 |
| samchoi | since the mailing list is quite cluttered | 16:26 |
| samchoi | they come from a wide variety of backgrounds so I expected more variance | 16:26 |
| mfer | and to #2 I'm not sure how those projects are run inside rackspace. there are projects inside HP that could use BDD and I imagine in some groups there are. But, this is a different sort of project. Communication and process are context sensetitive to the people and the projects. | 16:26 |
| * mfer is all ears to hear samchoi | 16:26 | |
| samchoi | So I'm going to roughly paraphrase what I've noted down | 16:27 |
| samchoi | since I didn't ask to directly quote people | 16:27 |
| jamiehannaford | mfer but that's the thing - they're not different whatsoever. Better communication is useful for all projects | 16:27 |
| samchoi | but I'm staying true to their statements | 16:27 |
| samchoi | - It appears to be overkill for an "...SDK when your 'business requirements' are to perform an HTTP GET" | 16:27 |
| samchoi | (mentioned by several devs) | 16:27 |
| samchoi | - if 90% or more of the people on the team are coders.. then why bother writingthings in english.. then taking the time to make a translation layer or using another tool in the chain to generate the code | 16:27 |
| samchoi | (indicating little support for a BDD framework) | 16:28 |
| samchoi | - BDD in itself is not bad, but BDD and "human readable tests" are two different things. Big fan of the former, not so much the latter | 16:28 |
| samchoi | again, these are their statements, possibly shortened, not mine | 16:28 |
| jamiehannaford | BDD is all about human readable tests - it's a communication tool, that is its point | 16:28 |
| jamiehannaford | I can respond to these on the mailing list | 16:29 |
| jamiehannaford | I think we're running out of time | 16:29 |
| mfer | jamiehannaford good catch on the time | 16:29 |
| *** sarob has joined #openstack-meeting-3 | 16:29 | |
| jamiehannaford | were those all the points, sam? | 16:29 |
| *** tjones has joined #openstack-meeting-3 | 16:29 | |
| mfer | jamiehannaford I'll ask one thing. respond in a way that can get people excited and around it. this is about moving people more than the architecture issues. | 16:29 |
| samchoi | there were a few more I believe, but it was quite clear that they did not support using a bdd frmaework | 16:29 |
| mfer | that will help you sell it | 16:30 |
| mfer | ok, we have to run... time for the next meeting. | 16:30 |
| tjones | hi folks you about done? getting ready to start a meeting here now | 16:30 |
| mfer | #endmeeting | 16:30 |
| jamiehannaford | okay | 16:30 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:30 | |
| openstack | Meeting ended Wed Jun 11 16:30:23 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:30 |
| tjones | thanks | 16:30 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-06-11-15.30.html | 16:30 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-06-11-15.30.txt | 16:30 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-06-11-15.30.log.html | 16:30 |
| tjones | #startmeeting novabugscrub | 16:30 |
| openstack | Meeting started Wed Jun 11 16:30:42 2014 UTC and is due to finish in 60 minutes. The chair is tjones. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:30 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:30 |
| *** openstack changes topic to " (Meeting topic: novabugscrub)" | 16:30 | |
| openstack | The meeting name has been set to 'novabugscrub' | 16:30 |
| tjones | hi anyone around? | 16:30 |
| wendar | o/ | 16:30 |
| tjones | hey wendar | 16:31 |
| wendar | hi | 16:31 |
| tjones | thanks for helping. i did the obvious tags this am | 16:31 |
| *** nedbat_ has joined #openstack-meeting-3 | 16:31 | |
| wendar | excellent | 16:31 |
| tjones | #link https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW | 16:31 |
| tjones | left with a couple | 16:31 |
| tjones | #link https://bugs.launchpad.net/nova/+bug/1326566 | 16:32 |
| *** geekinutah has joined #openstack-meeting-3 | 16:32 | |
| tjones | 1st i thought compute, but now im thinking network as it is failing in the network cleanup code | 16:33 |
| wendar | hmmmm... it's one of those cascading problems | 16:33 |
| *** sarob has quit IRC | 16:33 | |
| *** nedbat has quit IRC | 16:33 | |
| tjones | yeah | 16:33 |
| tjones | well the 1st prob is handled properly by compute, but the cleanup is failing | 16:34 |
| wendar | like, something needs to abort after the first error, but is trying to proceed normally | 16:34 |
| *** markmcclain has joined #openstack-meeting-3 | 16:35 | |
| tjones | hmmm - then is could still be compute | 16:35 |
| *** kashyap has joined #openstack-meeting-3 | 16:35 | |
| wendar | it's in ovs | 16:35 |
| geekinutah | sorry, came in late, what bug is this? | 16:36 |
| wendar | (that was a ...) | 16:36 |
| tjones | https://bugs.launchpad.net/nova/+bug/1326566 | 16:36 |
| tjones | so networking then?? | 16:36 |
| * kashyap here | 16:36 | |
| tjones | hey kashyap | 16:36 |
| kashyap | tjones, I'm currently going through NEW bugs - https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New | 16:37 |
| *** sarob has joined #openstack-meeting-3 | 16:37 | |
| kashyap | And, tag appropriate stuff, mostly I'll keep an eye on libvirt stuff but can try others too | 16:37 |
| wendar | tjones: yeah, I'd go with networking | 16:37 |
| tjones | we are just tagging a couple of remianing bugs so the subteam owners can take the next pass | 16:38 |
| kashyap | tjones, Also, libvirt tag for the above bug | 16:38 |
| tjones | ok done | 16:38 |
| tjones | #link https://bugs.launchpad.net/nova/+bug/1326599 | 16:38 |
| tjones | oslo??? | 16:39 |
| wendar | tjones: or api? | 16:39 |
| tjones | really no idea | 16:39 |
| kashyap | Yeah, api, looking at the fix | 16:39 |
| *** mriedem has joined #openstack-meeting-3 | 16:40 | |
| *** sarob_ has joined #openstack-meeting-3 | 16:40 | |
| kashyap | and Nova | 16:40 |
| * mriedem joins late | 16:40 | |
| tjones | hi mriedem we are on https://bugs.launchpad.net/nova/+bug/1326599 | 16:40 |
| tjones | api and nova | 16:40 |
| mriedem | tag with api | 16:40 |
| tjones | well everything is nova ;-) | 16:40 |
| geekinutah | seems like network is the appropriate tag for that guy | 16:40 |
| mriedem | kenichi opened it so he probably knows the isue | 16:40 |
| tjones | #link https://bugs.launchpad.net/nova/+bug/1326901 | 16:41 |
| *** sarob has quit IRC | 16:41 | |
| kashyap | conductor | 16:41 |
| mriedem | yup | 16:42 |
| kashyap | #link FYI - https://wiki.openstack.org/wiki/Bug_Tags#Nova | 16:42 |
| tjones | #link https://bugs.launchpad.net/nova/+bug/1327028 | 16:42 |
| mriedem | for https://bugs.launchpad.net/nova/+bug/1326901 i asked what release they are on | 16:43 |
| mriedem | those details are usually lacking | 16:43 |
| tjones | yeah good idea | 16:43 |
| mriedem | "shit blows up, please figure it out..." | 16:43 |
| tjones | lol | 16:43 |
| kashyap | :-) | 16:43 |
| kashyap | Also, this bug looks woefully short of info -- https://bugs.launchpad.net/nova/+bug/1327028 | 16:43 |
| tjones | next one seems like api but really an opinion | 16:43 |
| tjones | yes that is the one | 16:44 |
| mriedem | yeah, ask for more info, which API is used, which release are they on, what is the request and response, etc | 16:44 |
| tjones | done | 16:44 |
| tjones | #link https://bugs.launchpad.net/nova/+bug/1327406 | 16:45 |
| mriedem | tjones: marked that previous one as incomplete | 16:45 |
| tjones | mriedem: good idea | 16:45 |
| * kashyap wrote this wiki page a while ago -- https://wiki.openstack.org/wiki/BugFilingRecommendations | 16:45 | |
| kashyap | Should probably stick it in most bugs I try to triage | 16:45 |
| tjones | now this next one is networking. kashyap great! i'll start adding that when there is not enough info | 16:46 |
| tjones | #link https://bugs.launchpad.net/nova/+bug/1328367 | 16:47 |
| mriedem | hold up a sec | 16:47 |
| mriedem | https://bugs.launchpad.net/nova/+bug/1327406 | 16:47 |
| mriedem | there was a patch for nova so status changed to in progress and assigned the owern | 16:48 |
| mriedem | *owner | 16:48 |
| mriedem | also tagged with network | 16:48 |
| tjones | i just tagged with network | 16:48 |
| mriedem | this is my first nova bug meeting, but are we not going through the bugs like that in detail? or is this just quickly tagging things? | 16:48 |
| tjones | well this one has a proposed patch - so i was quickly moving over it | 16:49 |
| wendar | mriedem: we're doing quick triage | 16:49 |
| tjones | the purpose is to get things in the column owners awareness - they may not see untagged bugs | 16:49 |
| wendar | essentially, making sure the bugs are raised to the attention of the folks who have agreed to own a particular tag space | 16:50 |
| mriedem | are the column owners actually looking at them though? | 16:50 |
| kashyap | mriedem, They ought to be gone over in detail, I try my best to find root-cause and post deails | 16:50 |
| tjones | some are some are not. i try to send a nag email every once in a while | 16:50 |
| wendar | 1328367 I'm leaning toward compute | 16:50 |
| tjones | wendar: ok makes sense | 16:51 |
| mriedem | also tag with resize and/or migration | 16:51 |
| mriedem | or migrate | 16:51 |
| mriedem | i've been trying to tag resize/migrate bugs also | 16:51 |
| tjones | niether of those are official tags - should we add that to the list? | 16:52 |
| * kashyap is still to do a resize test of Nova instance in multi-node setup to reconfirm a certain bug | 16:52 | |
| mriedem | just something i've been doing | 16:52 |
| kashyap | tjones, Yeah, I was wondering _who_ blesses them as "official" tags | 16:52 |
| mriedem | compute tag is very broad | 16:52 |
| tjones | mikal is the blesser of tags | 16:53 |
| kashyap | True, doesn't mean anything | 16:53 |
| mriedem | resize seems to be a particularly nasty thing for bugs we get | 16:53 |
| wendar | the significant difference is whether anyone is watching the tag | 16:53 |
| mriedem | in part b/c we don't have multi-node tempest testing in the gate | 16:53 |
| wendar | so, if mriedem wants to watch resize or migration, I say add it | 16:53 |
| mriedem | i think it's useful for finding duplicates though | 16:53 |
| mriedem | i don't want to watch it | 16:53 |
| mriedem | but i don't want 20 duplicates | 16:53 |
| kashyap | Uh, yeah. I admit twice I attempted to reproduce a nasty resize bug, got distracted and did something else | 16:53 |
| mriedem | b/c it's not tested upstream | 16:53 |
| tjones | i think we should spend some time in portland talking about this stuff. | 16:54 |
| mriedem | tjones: it's on the agenda | 16:54 |
| tjones | yep | 16:54 |
| tjones | and the reason i am going ;-) | 16:54 |
| tjones | ok last untagged one is https://bugs.launchpad.net/nova/+bug/1328966 | 16:54 |
| mriedem | but my point is, until we have multi-node resize/migrate testing in the gate, we can sub-tag these for compute to avoid duplicates hopefully | 16:54 |
| kashyap | Exactly, the bug I was testing works fine in a single node allinone style setup, but blows up in a 2-node setup | 16:55 |
| wendar | api | 16:55 |
| tjones | duh | 16:55 |
| tjones | i guess i ran out of time on that one | 16:55 |
| wendar | or, it came in 43 minutes ago :) | 16:56 |
| tjones | lol | 16:56 |
| mriedem | tjones: i talked to him about that this morning in nova | 16:56 |
| mriedem | it's triaged | 16:56 |
| mriedem | tag with api | 16:56 |
| tjones | folks - this wiki shows the offical tags and has links to untriaged. if you are a tag owner then please take a look at your column https://wiki.openstack.org/wiki/Nova/BugTriage | 16:56 |
| tjones | mriedem: i know - i just tagged it | 16:56 |
| tjones | there are 171 total untriaged bugs across all columns | 16:57 |
| tjones | https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New | 16:57 |
| tjones | almost out of time. anyone have anything they want to discuss for 1 minute? | 16:59 |
| tjones | kashyap: i've added your wiki to my meeting page. thanks | 16:59 |
| wendar | bug day? | 16:59 |
| kashyap | tjones, Sure, no worries. | 16:59 |
| *** Sukhdev has quit IRC | 16:59 | |
| tjones | well… it was mixed. some people did a lot, many people did not | 16:59 |
| tjones | i've got to go run another meeting. thanks all for helping out today | 17:00 |
| tjones | #endmeeting | 17:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 17:00 | |
| openstack | Meeting ended Wed Jun 11 17:00:24 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:00 |
| wendar | thanks tjones! | 17:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-06-11-16.30.html | 17:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-06-11-16.30.txt | 17:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-06-11-16.30.log.html | 17:00 |
| *** mriedem has left #openstack-meeting-3 | 17:00 | |
| *** Sukhdev has joined #openstack-meeting-3 | 17:00 | |
| *** beyounn has joined #openstack-meeting-3 | 17:02 | |
| *** sankarshan is now known as sankarshan_away | 17:14 | |
| *** jackib has joined #openstack-meeting-3 | 17:14 | |
| *** jmsoares has joined #openstack-meeting-3 | 17:15 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 17:15 | |
| *** pgpus has joined #openstack-meeting-3 | 17:19 | |
| *** anil_rao has joined #openstack-meeting-3 | 17:20 | |
| *** hemanthravi has joined #openstack-meeting-3 | 17:22 | |
| *** jackib has quit IRC | 17:23 | |
| *** aihua has joined #openstack-meeting-3 | 17:25 | |
| *** eghobo has joined #openstack-meeting-3 | 17:25 | |
| *** eguz has joined #openstack-meeting-3 | 17:28 | |
| *** eguz has quit IRC | 17:29 | |
| *** eguz has joined #openstack-meeting-3 | 17:29 | |
| banix | halooo | 17:29 |
| *** vinay_yadhav has joined #openstack-meeting-3 | 17:30 | |
| *** s3wong has joined #openstack-meeting-3 | 17:30 | |
| *** tjones has left #openstack-meeting-3 | 17:30 | |
| SumitNaiksatam | banix: hi | 17:30 |
| banix | advanced services for moving bits on wire? | 17:30 |
| s3wong | hello | 17:30 |
| SumitNaiksatam | hello everyone! | 17:30 |
| hemanthravi | hi | 17:30 |
| vinay_yadhav | Hi | 17:30 |
| anil_rao | Hello | 17:31 |
| SumitNaiksatam | enikanorov kanzhe, there? | 17:31 |
| *** SridarK has joined #openstack-meeting-3 | 17:31 | |
| s3wong | SumitNaiksatam: doesn't seem like kanzhe or kevinbenton is here | 17:31 |
| jmsoares | hi | 17:31 |
| *** Cathy_ has joined #openstack-meeting-3 | 17:31 | |
| cgoncalves | hi | 17:31 |
| SridarK | Hi | 17:31 |
| SumitNaiksatam | s3wong: ah o | 17:31 |
| s3wong | SumitNaiksatam: so I guess I will do update on service insertion/base | 17:31 |
| *** LouisF has joined #openstack-meeting-3 | 17:31 | |
| SumitNaiksatam | s3wong: thanks, lets get started then | 17:31 |
| SumitNaiksatam | #startmeeting Networking Advanced Services | 17:32 |
| openstack | Meeting started Wed Jun 11 17:32:05 2014 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:32 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:32 |
| *** openstack changes topic to " (Meeting topic: Networking Advanced Services)" | 17:32 | |
| openstack | The meeting name has been set to 'networking_advanced_services' | 17:32 |
| SumitNaiksatam | #info agenda: https://wiki.openstack.org/wiki/Meetings/AdvancedServices | 17:32 |
| *** pcm_ has joined #openstack-meeting-3 | 17:32 | |
| SumitNaiksatam | for the last couple of weeks we have started to track the priority blueprints in this meeting | 17:33 |
| SumitNaiksatam | #link https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan | 17:33 |
| *** eghobo has quit IRC | 17:33 | |
| *** aihuaedwardli has joined #openstack-meeting-3 | 17:33 | |
| SumitNaiksatam | before we get into each blueprint, anything anyone wants to bring up at outset? | 17:33 |
| *** rkukura has joined #openstack-meeting-3 | 17:34 | |
| SumitNaiksatam | i am little concerned that our specs are still in review at the end of Juno 1 | 17:34 |
| s3wong | SumitNaiksatam: why back to work so early :-) ? | 17:34 |
| *** emagana has joined #openstack-meeting-3 | 17:34 | |
| SumitNaiksatam | s3wong: ha :-) | 17:34 |
| SumitNaiksatam | i will get back to real work soon | 17:34 |
| SumitNaiksatam | this is just a break ;-) | 17:34 |
| pgpus | Last week few were approved I thought | 17:35 |
| SumitNaiksatam | lets discuss the review logistics in the open discussion | 17:35 |
| SumitNaiksatam | pgpus: not sure which ones you are referring ot | 17:35 |
| SumitNaiksatam | *to | 17:35 |
| SumitNaiksatam | enikanorov: there? | 17:35 |
| pgpus | Mot sure me too but of the 5 we had 2 or 3 were in approved state | 17:36 |
| *** Kanzhe has joined #openstack-meeting-3 | 17:36 | |
| *** geekinutah has left #openstack-meeting-3 | 17:36 | |
| *** yamamoto has quit IRC | 17:36 | |
| SumitNaiksatam | pgpus: only the general Juno plan is approved | 17:36 |
| s3wong | pgpus: I think only SumitNaiksatam 's umbrella bp was approved | 17:36 |
| SumitNaiksatam | s3wong: yeah | 17:36 |
| Kanzhe | hi | 17:36 |
| SumitNaiksatam | enikanorov: doesnt seem to be on | 17:36 |
| gduan | Hi | 17:36 |
| SumitNaiksatam | but Kanzhe is popped in at the right time :-) | 17:37 |
| SumitNaiksatam | #topic Service base definition and Insertion | 17:37 |
| *** openstack changes topic to "Service base definition and Insertion (Meeting topic: Networking Advanced Services)" | 17:37 | |
| Kanzhe | Welcome back, SumitNaiksatam | 17:37 |
| s3wong | good :-) | 17:37 |
| SumitNaiksatam | Kanzhe: thanks :-) | 17:37 |
| pgpus | Ok I don't see any of the 5 approved, may be was referring to some other Blue prints | 17:37 |
| SumitNaiksatam | #link https://review.openstack.org/#/c/93128 | 17:37 |
| SumitNaiksatam | pgpus: ok | 17:37 |
| *** Sukhdev has quit IRC | 17:37 | |
| SumitNaiksatam | Kanzhe: there were a few pending comments on the blueprint | 17:37 |
| s3wong | pgpus: this one is approved #link https://review.openstack.org/#/c/92200 | 17:37 |
| SumitNaiksatam | Kanzhe: are there any issues that you would want to bring up for discussion here? | 17:38 |
| s3wong | SumitNaiksatam: yeah, I saw that you -1 it | 17:38 |
| Kanzhe | SumitNaiksatam: Yes, I will address the comments later today. | 17:38 |
| SumitNaiksatam | Kanzhe: or you can take care of the review comments? | 17:38 |
| SumitNaiksatam | s3wong: yeah i did | 17:38 |
| SumitNaiksatam | s3wong: i can work with you guys though, i will try not be the bottleneck :-) | 17:39 |
| SridarK | Kanzhe: s3wong: I also reviewed today - have some minor clarifications | 17:39 |
| s3wong | SumitNaiksatam: sure, good | 17:39 |
| s3wong | SridarK: yes, I too noticed you have -1 it :-) | 17:39 |
| Kanzhe | SridarK: thanks. | 17:39 |
| SumitNaiksatam | so i would like to poll the other reviewers who have assigned themselves | 17:39 |
| pgpus | I had seen some blue print using protocol:port being used of service insertion with firewall as opposed to L2/L3 insertion we were looking at, so are there multiple blue prints to this topic?\ | 17:39 |
| SumitNaiksatam | pgpus: link? | 17:40 |
| SridarK | s3wong: overall looks good nothing negative here (no pun intended) | 17:40 |
| s3wong | SridarK: it's OK :-) . We will address your concerns | 17:40 |
| pgpus | I will send u later as it was on a diff system so later that | 17:40 |
| SumitNaiksatam | LouisF: are you there? | 17:41 |
| LouisF | yes | 17:41 |
| SumitNaiksatam | dont see regxboi marios here | 17:41 |
| SumitNaiksatam | LouisF: you signed up to review, have you reviewed? | 17:41 |
| LouisF | will do so | 17:41 |
| SumitNaiksatam | i am looking at the list at the top of: | 17:41 |
| SumitNaiksatam | #link https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan | 17:41 |
| LouisF | yes i am commited to review | 17:42 |
| *** HenryG has quit IRC | 17:42 | |
| SumitNaiksatam | LouisF: thanks, hopefully soon :-) | 17:42 |
| s3wong | Kanzhe will update soon, so we would love for everyone to review once the latest one is posted | 17:42 |
| SumitNaiksatam | LouisF: we are already missing our first milestone | 17:42 |
| *** seizadi1 has quit IRC | 17:42 | |
| SumitNaiksatam | is ivar here? | 17:42 |
| *** badveli has joined #openstack-meeting-3 | 17:42 | |
| SumitNaiksatam | probably not | 17:42 |
| SumitNaiksatam | ok so i went through the assigned reviewers | 17:43 |
| SumitNaiksatam | i dont want to start pinging the cores until we have consensus in the team here | 17:43 |
| SumitNaiksatam | anyone has major issues with this spec? | 17:43 |
| SumitNaiksatam | or its just that we havent reviewed it carefully? | 17:43 |
| s3wong | SumitNaiksatam: I am going to San Antonio next week to work with LBaaS team for them to conform to this as they revamp their APIs | 17:43 |
| SumitNaiksatam | s3wong: nice | 17:44 |
| s3wong | So hopefully our own team has reached a consensus by then :-) | 17:44 |
| SumitNaiksatam | s3wong: absolutely | 17:44 |
| Kanzhe | s3wong: SumitNaiksatam It would be great to put an internal target for review feedbacks. | 17:44 |
| SumitNaiksatam | Kanzhe: our target to get this approved was today | 17:45 |
| s3wong | Kanzhe: great idea. LouisF, SridarK? | 17:45 |
| SumitNaiksatam | Kanzhe: or if not approved at least to understand why it is not a being approved | 17:45 |
| Kanzhe | SumitNaiksatam: great! :-) | 17:45 |
| LouisF | will review today | 17:45 |
| SumitNaiksatam | Kanzhe: unfortuntaley we dont yet have enough reviews even within the sub-team here | 17:45 |
| SridarK | s3wong: yes agree | 17:45 |
| SumitNaiksatam | is kevinbenton here? | 17:45 |
| *** eguz has quit IRC | 17:46 | |
| kevinbenton | yes | 17:46 |
| Kanzhe | SumitNaiksatam: agreed. I broadcasted a plea on the mailing list, but was silently ignore. | 17:46 |
| SumitNaiksatam | Kanzhe: mailing list will not help | 17:46 |
| banix | I will review by Friday. | 17:46 |
| SumitNaiksatam | we have to work within our team here first | 17:46 |
| *** eghobo has joined #openstack-meeting-3 | 17:47 | |
| SumitNaiksatam | banix: thanks, i was just going to put you on the spot ;-) | 17:47 |
| gduan | I will review the BP too. | 17:47 |
| SumitNaiksatam | kevinbenton: you have volunteered to review | 17:47 |
| SumitNaiksatam | kevinbenton: are you happy with this spec? | 17:47 |
| SumitNaiksatam | gduan: thanks | 17:47 |
| pgpus | Is trhere anything that needs to be updated to design https://docs.google.com/document/d/1fmCWpCxAN4g5txmCJVmBDt02GYew2kvyRsh0Wl3YF2U/edit?pli=1# | 17:47 |
| SumitNaiksatam | cgoncalves: you also signed up, any comments? | 17:47 |
| s3wong | Kanzhe: update by tonight then :-) ? | 17:47 |
| Kanzhe | s3wong: yes. | 17:48 |
| *** eguz has joined #openstack-meeting-3 | 17:48 | |
| SumitNaiksatam | kevinbenton: i know you are part of the design team, but i would like to see a +1 if you dont have any issues :-) | 17:48 |
| kevinbenton | SumitNaiksatam: I haven’t looked at the latest one, I will review the next upload | 17:48 |
| SumitNaiksatam | kevinbenton: ok thanks | 17:48 |
| cgoncalves | SumitNaiksatam: sure, will do | 17:48 |
| SumitNaiksatam | pgpus: dont look at that document | 17:48 |
| Kanzhe | pgpus: I don't see any design change yet. | 17:48 |
| SumitNaiksatam | pgpus: #link https://review.openstack.org/#/c/93128 | 17:48 |
| s3wong | pgpus: yeah, please ignore the document, and focus on the gerrit spec reivew | 17:49 |
| SumitNaiksatam | #action LouisF kevinbenton gduan banix cgoncalves regxboi marios ivar to review https://review.openstack.org/#/c/93128 by end of week | 17:49 |
| pgpus | ok thanks | 17:49 |
| SumitNaiksatam | hemanthravi: can you review as well? | 17:50 |
| SumitNaiksatam | Kanzhe s3wong: i would request you to please return the review favor with the other blueprints | 17:51 |
| *** badveli has quit IRC | 17:51 | |
| hemanthravi | SumitNaiksatam: yes travelling this week will do it by mon | 17:51 |
| SumitNaiksatam | Kanzhe s3wong: i know you guys are terribly busy, but review begets review ;-) | 17:51 |
| *** garyduan has joined #openstack-meeting-3 | 17:51 | |
| *** gduan has quit IRC | 17:51 | |
| s3wong | SumitNaiksatam: absolutely. Ready to review the other four bps for the team | 17:51 |
| SumitNaiksatam | hemanthravi: thanks, can you please add yourself to the reviewers (or I can do that ;-)) | 17:51 |
| cgoncalves | SumitNaiksatam: as owner of that ^ google doc, should one (you?) add a warning message to it saying that doc is deprecated and pointing to the right URL (blueprint URL)? | 17:52 |
| Kanzhe | SumitNaiksatam: which one? | 17:52 |
| *** eghobo has quit IRC | 17:52 | |
| hemanthravi | SumitNaiksatam: this for 93128 right? | 17:52 |
| SumitNaiksatam | cgoncalves: good suggestion, i will do it, my bad | 17:52 |
| SumitNaiksatam | hemanthravi: correct | 17:52 |
| SumitNaiksatam | Kanzhe: all the others | 17:52 |
| hemanthravi | SumitNaiksatam: i'll do that | 17:52 |
| s3wong | Kanzhe: all the other four below ours #link https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan | 17:52 |
| SumitNaiksatam | Kanzhe: at least the flavors, traffic steering and chaining | 17:52 |
| SumitNaiksatam | enikanorov: there? | 17:53 |
| Cathy_ | I will review the blueprints too, service chaining specifically | 17:53 |
| Kanzhe | SumitNaiksatam: Kanzhe yes. Will do it by the weekend. | 17:53 |
| s3wong | Kanzhe: Oh, and flavor also... | 17:53 |
| SumitNaiksatam | Cathy_: nice, thanks much in advance | 17:53 |
| *** aihuaedwardli has quit IRC | 17:53 | |
| *** badveli has joined #openstack-meeting-3 | 17:53 | |
| SumitNaiksatam | Cathy_: if you feel comfortable please add yourself to the reviewers list: https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan | 17:53 |
| Cathy_ | sure, will do | 17:54 |
| SumitNaiksatam | Cathy_: that way I can hound you ;-P | 17:54 |
| SumitNaiksatam | ok it doesnt seem enikanorov is still not around | 17:54 |
| SumitNaiksatam | #topic Traffic steering | 17:54 |
| *** openstack changes topic to "Traffic steering (Meeting topic: Networking Advanced Services)" | 17:54 | |
| SumitNaiksatam | #link https://review.openstack.org/#/c/92477 | 17:54 |
| SumitNaiksatam | cgoncalves: are you planning a new patch? | 17:55 |
| *** aihuaedwardli has joined #openstack-meeting-3 | 17:55 | |
| cgoncalves | SumitNaiksatam: we'd like first to get input from banix et al. on Joao's last comments | 17:55 |
| SumitNaiksatam | cgoncalves: ok please go ahead, we can have the discussion now and resolve it if possible | 17:56 |
| SumitNaiksatam | banix: ? | 17:56 |
| banix | cgoncalves: will do by end of day (night) today | 17:56 |
| cgoncalves | banix: thanks | 17:56 |
| enikanorov | SumitNaiksatam: sorry, i'm late | 17:56 |
| s3wong | SumitNaiksatam: now we can go to flavor! | 17:56 |
| enikanorov | i'll give an update when you give me a timeslot | 17:56 |
| cgoncalves | all: note that I've submitted three patches for reviewing but marked as WIP | 17:57 |
| cgoncalves | #link https://review.openstack.org/#/q/topic:bp/traffic-steering-abstraction,n,z | 17:57 |
| SumitNaiksatam | enikanorov: no worries, we can do flavors next, people are getting restless without the customary start with flavors discussion ;-P | 17:57 |
| enikanorov | :) | 17:57 |
| SumitNaiksatam | cgoncalves: nice | 17:57 |
| s3wong | cgoncalves: OK - still need to review your spec; sorry for the delay | 17:57 |
| cgoncalves | marked as WIP because BP has not yet been approved | 17:57 |
| SumitNaiksatam | cgoncalves: thats the righ approach, very much appreciate the process you are following | 17:58 |
| cgoncalves | more codebase will follow once more reviewing is given | 17:58 |
| SumitNaiksatam | cgoncalves: which other reviewer do you want to check with? | 17:58 |
| SumitNaiksatam | *reviewers | 17:58 |
| cgoncalves | SumitNaiksatam: I'm not sure it's the best approach to follow, though, but I will follow a similar codebase as ML2 and GP. how does that sound to you all? | 17:59 |
| pgpus | I can provided I get some help on Gerrit from one of you? | 17:59 |
| SumitNaiksatam | cgoncalves: yeah good | 17:59 |
| SumitNaiksatam | pgpus: nice, much appreciated | 17:59 |
| SumitNaiksatam | is Youcef_ here? | 17:59 |
| cgoncalves | SumitNaiksatam: Ryan Moats as he brought some comments too | 17:59 |
| pgpus | OK I will review the 3 of the listed one and work with cgoncalves | 17:59 |
| SumitNaiksatam | cgoncalves: yes, but i dont see ryan here today | 18:00 |
| cgoncalves | pgpus: thanks! | 18:00 |
| SumitNaiksatam | Youcef_ had comments on both this and the insertion bp | 18:00 |
| SumitNaiksatam | *good comments | 18:00 |
| banix | cgoncalves: ryan is out the rest of the week but let me go through your comments | 18:00 |
| cgoncalves | SumitNaiksatam: yes. better take this discussion to gerrit | 18:00 |
| SumitNaiksatam | i will hound him :-) | 18:00 |
| SumitNaiksatam | cgoncalves: ok | 18:00 |
| *** jamiehannaford has quit IRC | 18:00 | |
| cgoncalves | banix: thanks ;) | 18:01 |
| SumitNaiksatam | anyone else want to bring up an technical issue with the traffic steering blueprint? | 18:01 |
| banix | cgoncalves: np | 18:01 |
| SumitNaiksatam | *any | 18:01 |
| *** markmcclain has quit IRC | 18:01 | |
| cgoncalves | I think there may be some other folks interested in this BP | 18:01 |
| cgoncalves | not sure, though, if any of them are here | 18:01 |
| s3wong | cgoncalves: outside of this subteam? | 18:01 |
| *** markmcclain has joined #openstack-meeting-3 | 18:02 | |
| s3wong | cgoncalves: the NFV folks, perhaps? | 18:02 |
| cgoncalves | s3wong: yes. NFV team | 18:02 |
| cgoncalves | s3wong: https://wiki.openstack.org/wiki/Meetings/NFV | 18:02 |
| cgoncalves | s3wong: search for "steering", for instance | 18:02 |
| SumitNaiksatam | #action banix pgpus regxboi Kanzhe s3wong kevinbenton hemanthravi LouisF to review https://review.openstack.org/#/c/92477 and provide feedback by end of week | 18:03 |
| SumitNaiksatam | cgoncalves: yeah | 18:03 |
| SumitNaiksatam | cgoncalves: did you attend the NFV meeting? | 18:03 |
| s3wong | cgoncalves: you may want to add your bp on the wiki page here #link https://wiki.openstack.org/wiki/Meetings/NFV | 18:03 |
| SumitNaiksatam | or anyone else? | 18:03 |
| banix | SumitNaiksatam: liking these action items already :) | 18:03 |
| s3wong | SumitNaiksatam: I have | 18:03 |
| cgoncalves | I also just got a contact from someone else not in these teams asking for more details | 18:03 |
| banix | SumitNaiksatam: sounds like a good way of tracking | 18:03 |
| * SumitNaiksatam hides for cover :-P | 18:03 | |
| cgoncalves | SumitNaiksatam: I did | 18:03 |
| cgoncalves | s3wong: it is listed there. check the bottom of second table | 18:04 |
| SumitNaiksatam | cgoncalves: ok good | 18:04 |
| s3wong | cgoncalves: that's good. Ask them to join as reviewers :-) | 18:04 |
| SumitNaiksatam | s3wong: nice one | 18:04 |
| SumitNaiksatam | banix: i am happy being the bad guy here | 18:04 |
| cgoncalves | s3wong: sure! | 18:04 |
| s3wong | cgoncalves: got it, didn't scroll all down enough. Sorry | 18:04 |
| SumitNaiksatam | cgoncalves: we will have a quick NFV update later, perhaps you can do that | 18:05 |
| SumitNaiksatam | ok flavors | 18:05 |
| SumitNaiksatam | #topic Flavors | 18:05 |
| *** openstack changes topic to "Flavors (Meeting topic: Networking Advanced Services)" | 18:05 | |
| banix | SumitNaiksatam: no i think this is a good way of tracking things; when one have an action item you pay more attention; we all want to do the reviews but things get pushed around wrt priority; so i like the approach | 18:05 |
| SumitNaiksatam | banix: exactly | 18:05 |
| cgoncalves | SumitNaiksatam: later this meeting or? | 18:05 |
| SumitNaiksatam | #link https://review.openstack.org/#/c/90070 | 18:05 |
| SumitNaiksatam | cgoncalves: yes later in the agenda | 18:06 |
| SumitNaiksatam | enikanorov: ? | 18:06 |
| enikanorov | here | 18:06 |
| enikanorov | ok | 18:06 |
| SumitNaiksatam | enikanorov: is there another patch coming? | 18:06 |
| enikanorov | SumitNaiksatam: you mean spec? | 18:06 |
| SumitNaiksatam | enikanorov: yeah | 18:06 |
| enikanorov | yes, i think the only remaining question is about tags format | 18:07 |
| SumitNaiksatam | enikanorov: i meant patch set, sorry | 18:07 |
| *** nati_ueno has joined #openstack-meeting-3 | 18:07 | |
| enikanorov | my understanding was that with many different requirements it might be more flexible to hae it in a form of string | 18:07 |
| SumitNaiksatam | enikanorov: so who is blocking that? | 18:07 |
| *** lcheng has quit IRC | 18:07 | |
| enikanorov | there was a couple of questions along the way about that | 18:07 |
| enikanorov | some asked if we need additional model for Tag | 18:08 |
| SumitNaiksatam | enikanorov: ok | 18:08 |
| enikanorov | and add Tags one by one to Flavor | 18:08 |
| enikanorov | but I think it's too complex to be usable | 18:08 |
| SumitNaiksatam | enikanorov: i made the comment about there being more structure | 18:08 |
| SumitNaiksatam | nati_ueno: there? | 18:08 |
| enikanorov | but technically, what kind of structure it could be? | 18:08 |
| garyduan | enikanorov: Does the spec define how "supported capabilities" are inputed? | 18:09 |
| SumitNaiksatam | enikanorov: i was just thinking something more than a one single flat string for all the tags and valures | 18:09 |
| SumitNaiksatam | *values | 18:09 |
| enikanorov | SumitNaiksatam: so what is that 'something'? | 18:09 |
| SumitNaiksatam | enikanorov: i will not block this | 18:09 |
| SumitNaiksatam | enikanorov: something similar to the dict that i was suggesting in the comments | 18:10 |
| pgpus | Diff services have diff capability so how do we structure flavor, more likely string format with key values should be Ok | 18:10 |
| enikanorov | garyduan: "cap_name:cap_value,cap_name2:cap_value2" | 18:10 |
| *** safchain has quit IRC | 18:10 | |
| pgpus | That spound perfect provided we know service instace can use them with correct interpretation | 18:10 |
| garyduan | enikanorov: what I mean is there is a predefined set of allowed tags that driver can use | 18:10 |
| SumitNaiksatam | garyduan: my earlier suggesting was along similar lines | 18:11 |
| enikanorov | garyduan: I would be glad if someone could help me with defining that | 18:11 |
| *** beyounn has quit IRC | 18:11 | |
| SumitNaiksatam | enikanorov: is there a possibility that two different drivers can have the same capability name and be using them in different ways? | 18:11 |
| enikanorov | although i'm not sure it shoul be necessarily in flavor API implementation | 18:11 |
| *** beyounn has joined #openstack-meeting-3 | 18:12 | |
| enikanorov | SumitNaiksatam: that should be avoided. Capabilites are user facing so they create expectations | 18:12 |
| pgpus | OK unfortunately unlike nova flavor we do not have fixed mem storage like common absractions fully similar across services | 18:12 |
| enikanorov | expectations of consistency | 18:12 |
| SumitNaiksatam | pgpus: yes that is the issue | 18:12 |
| *** lcheng has joined #openstack-meeting-3 | 18:12 | |
| enikanorov | since user doesn't know what implementation he gets, it should be consistent across drivers | 18:13 |
| SumitNaiksatam | enikanorov: but without being prescriptive, it is difficult to be consistent | 18:13 |
| garyduan | enikanorov: what these tags are can be figured out later for each services | 18:13 |
| enikanorov | SumitNaiksatam: please explain? | 18:13 |
| SumitNaiksatam | enikanorov: so who ensures the consistency? | 18:13 |
| garyduan | enikanorov: but where to define them. Are they hard-coded in Neutron? | 18:13 |
| pgpus | Atleast service_type is common across all falvors | 18:13 |
| enikanorov | I think deployers/cloud admins should ensure it | 18:13 |
| SumitNaiksatam | enikanorov: but the deployers are different from the entities who develop the drivers | 18:14 |
| SumitNaiksatam | enikanorov: and we are saying that the drivers express their capabilities | 18:14 |
| pgpus | If Provider has a different concept from same service_type they should be able to override the service_type\ | 18:14 |
| enikanorov | yes, they're different. Those who maintain service should ensure that certain feature works similarly in all drivers | 18:14 |
| enikanorov | also, driver authors should be verbose in defining capabilities supported by their driver | 18:15 |
| garyduan | I think what Sumit means is | 18:15 |
| garyduan | Operator A may want to have tag X, Y, Z | 18:15 |
| garyduan | and B wants tag S, T, W | 18:15 |
| garyduan | as vendor driver, which tag set should it expose? | 18:16 |
| enikanorov | the tag names should be hardcoded unless it's vendor-specific | 18:16 |
| SumitNaiksatam | enikanorov: so essentially, you seem to be saying that at the time of reviewing a driver, we as reviewers should ensure consistency? | 18:16 |
| SumitNaiksatam | * driver code | 18:17 |
| pgpus | Every Service_Type should have atleast two or three standard attributes like for for firewall igress, egress and l2 or l3 should be minmum just for exaple sake | 18:17 |
| s3wong | enikanorov: so should the hardcoded tag names be part of the spec/API/DB? | 18:17 |
| enikanorov | yes, I think every driver should implement some feature X such that user would have same experience with it | 18:17 |
| garyduan | s3wong: my question too. | 18:17 |
| pgpus | So tags S=A has A,B,C ... anything after that | 18:17 |
| enikanorov | and we as reviewers should ensure that | 18:17 |
| *** sarob_ has quit IRC | 18:17 | |
| pgpus | Service-B has, A,B,C.. anything after that | 18:18 |
| SumitNaiksatam | enikanorov: in that case, can i suggest an evolutionary approach | 18:18 |
| pgpus | both S-A & S-B being two implementations of FW | 18:18 |
| *** sarob_ has joined #openstack-meeting-3 | 18:18 | |
| enikanorov | SumitNaiksatam: please explain? | 18:18 |
| SumitNaiksatam | enikanorov: how about we define a module where we note these capability names as they are populated by drivers? | 18:18 |
| pgpus | same with LB that may have S-A A,B,C,D ... and any more | 18:18 |
| enikanorov | SumitNaiksatam: yes, that will work for us | 18:19 |
| SumitNaiksatam | enikanorov: since the problem now seems to be to able to identify these tags at the outset | 18:19 |
| pgpus | and S-B A,B.C,D and any thing more | 18:19 |
| pgpus | but for a give Service A,B,C or A,BC,D must be common minimum | 18:19 |
| SumitNaiksatam | enikanorov: every new tag name should be added to this capabilites module (like a common constants module) | 18:19 |
| enikanorov | SumitNaiksatam: yes, something like that | 18:19 |
| *** HenryG has joined #openstack-meeting-3 | 18:20 | |
| s3wong | SumitNaiksatam: enikanorov: OK - that makes sense, separate framework from service-type-specific attributes | 18:20 |
| SumitNaiksatam | enikanorov: that way we have the tag (names) all defined in one place, which evolve over time, but we ensure that at least people are aware of what is being used | 18:20 |
| enikanorov | SumitNaiksatam: agree | 18:20 |
| garyduan | SumitNaiksatam: these are hardcoded "common tags or specific to service types" tag, right? | 18:20 |
| SumitNaiksatam | enikanorov: we should also ensure that these tag names are documented when they are populated | 18:20 |
| pgpus | OK that looks good so you define a set of constant which are part of standards for that specifc service and rest are optional | 18:20 |
| SumitNaiksatam | pgpus: yes | 18:21 |
| enikanorov | SumitNaiksatam: ok | 18:21 |
| SumitNaiksatam | enikanorov: to help us maintain consistency | 18:21 |
| garyduan | agree | 18:21 |
| SridarK | SumitNaiksatam: enikanorov so there is a review process to get a new tag added ? | 18:21 |
| pgpus | I am ok with that, that will work | 18:21 |
| nati_ueno | Hi! | 18:21 |
| enikanorov | #action enikanorov to add notes on tags consistency to blueprint spec | 18:21 |
| enikanorov | SridarK: common sense? :) | 18:21 |
| SumitNaiksatam | SridarK: that would be part of the review for the driver, enikanorov right? | 18:22 |
| enikanorov | SumitNaiksatam: sure | 18:22 |
| SumitNaiksatam | nati_ueno: hi, wanted to put you on the spot :-) | 18:22 |
| nati_ueno | SumitNaiksatam: Show time! | 18:22 |
| SumitNaiksatam | nati_ueno: did you get a chance to look at the flavors spec? | 18:22 |
| SridarK | enikanorov: SumitNaiksatam yes that will help excess proliferation. | 18:22 |
| s3wong | SridarK: I would imagine who ever add their service's flavor support would have to define tags and have them reviewed | 18:22 |
| SumitNaiksatam | nati_ueno: #link https://review.openstack.org/#/c/90070 | 18:22 |
| nati_ueno | SumitNaiksatam: I didn't read the latest yet. please let me have a look | 18:22 |
| SridarK | s3wong: yes a sort of IANA allocation will keep things sane | 18:23 |
| SumitNaiksatam | nati_ueno: thanks, this is blocker for lots of services’ stuff | 18:23 |
| SumitNaiksatam | SridarK: nice analogy :-) | 18:23 |
| s3wong | SridarK: in here we have Neutron core-dev to serve the role :-) | 18:23 |
| *** sarob_ has quit IRC | 18:23 | |
| enikanorov | let nati_ueno put another -1 so i could resolve his comments as well :) | 18:23 |
| SridarK | :-) | 18:23 |
| SumitNaiksatam | nati_ueno: enikanorov is challenging you to put a +2 i think :-) | 18:24 |
| enikanorov | So with regards to implementation that is under way, I'd like to put everything that is not yet fully decided - out of the patch | 18:24 |
| enikanorov | so it only will consist of API and db part (+UTs of course) | 18:24 |
| nati_ueno | enikanorov: he he that challenge is accepted | 18:24 |
| enikanorov | SumitNaiksatam: eventually, yes :) | 18:24 |
| s3wong | enikanorov: makes sense | 18:24 |
| SumitNaiksatam | enikanorov: have we identified people who will work on each service? | 18:25 |
| enikanorov | SumitNaiksatam: no, i don't think so. garyduan for fwaas, ... ? | 18:25 |
| s3wong | SumitNaiksatam: enikanorov himself for LBaaS? That is, once the dust is settled there :-) | 18:25 |
| enikanorov | i'll gladly help with integration | 18:25 |
| enikanorov | it's a bit early to say about lbaas | 18:26 |
| SumitNaiksatam | #agreed nati_ueno accepts enikanorov challenge to +2 flavors patch https://review.openstack.org/#/c/90070 | 18:26 |
| enikanorov | after the code sprint - may be! | 18:26 |
| garyduan | enikanorov: please also explain in the spec how vendor should expose "specific to vendor" tags | 18:26 |
| *** emagana has quit IRC | 18:26 | |
| garyduan | enikanorov: anything not hardcoded? | 18:26 |
| SumitNaiksatam | garyduan: are you doing fwaas? | 18:26 |
| s3wong | enikanorov: so optimistic :-) | 18:26 |
| garyduan | yes | 18:26 |
| SumitNaiksatam | garyduan: nice | 18:26 |
| enikanorov | garyduan: vendor exposes to admin, admin decides wether to put those caps into flavors | 18:26 |
| SumitNaiksatam | nati_ueno: what about vpnaas? | 18:26 |
| garyduan | enikanorov: ok. | 18:27 |
| *** markmcclain has quit IRC | 18:27 | |
| nati_ueno | SumitNaiksatam: I think there is nothing special for vpnaas | 18:27 |
| SumitNaiksatam | nati_ueno: ok | 18:27 |
| nati_ueno | accoding to the flavor part | 18:27 |
| nati_ueno | I feel there is more and more vendor paramters in the vpnaas, but it is another issue | 18:28 |
| nati_ueno | may be we should bind flavor and such extended parater for validation .. | 18:28 |
| SumitNaiksatam | ok as a team can we agree to resolve all issues with the flavors spec by next week; i would like to see a bunch of +1s by that time | 18:28 |
| *** beyounn has quit IRC | 18:28 | |
| SumitNaiksatam | and i would like to see some +1s to my comment now ;-P | 18:28 |
| rkukura | SumitNaiksatam: I’ll be sure to review that one | 18:29 |
| s3wong | SumitNaiksatam: +1 | 18:29 |
| SumitNaiksatam | rkukura: thanks! | 18:29 |
| SridarK | SumitNaiksatam: +1 | 18:29 |
| garyduan | SumitNaiksatam: +1 | 18:29 |
| Kanzhe | +1 | 18:29 |
| vinay_yadhav | +1 | 18:29 |
| banix | sounds good | 18:29 |
| enikanorov | +1! | 18:29 |
| s3wong | SumitNaiksatam: time's up for the meeting, BTW | 18:30 |
| SumitNaiksatam | #action rkukura s3wong SridarK garyduan Kanzhe vinay_yadhav banix nati_ueno SumitNaiksatam to review flavors patch and resolve issues before next weeks meeting | 18:30 |
| cgoncalves | SumitNaiksatam: +1 (just because I'm scare of being haunted by you) | 18:30 |
| SumitNaiksatam | s3wong: yes we are running a little behind | 18:30 |
| SumitNaiksatam | cgoncalves: ha | 18:30 |
| SumitNaiksatam | cgoncalves: you managed to escpat | 18:30 |
| SumitNaiksatam | few more minutes if people are willing to stay | 18:31 |
| * cgoncalves does the chicken dance | 18:31 | |
| SumitNaiksatam | cgoncalves: ha | 18:31 |
| vinay_yadhav | sumit: TaaS | 18:31 |
| pgpus | Sumit Thanks will follow with cg | 18:31 |
| SumitNaiksatam | vinay_yadhav: yes | 18:31 |
| *** markmcclain has joined #openstack-meeting-3 | 18:31 | |
| SumitNaiksatam | #topic Tap Service | 18:31 |
| *** openstack changes topic to "Tap Service (Meeting topic: Networking Advanced Services)" | 18:31 | |
| s3wong | SumitNaiksatam: let's skip updates on NFV and serviceVM for this week then | 18:31 |
| vinay_yadhav | we have resolved some comment from previous patch and have got some +1 | 18:31 |
| SumitNaiksatam | #link https://review.openstack.org/#/c/96149/ | 18:31 |
| SumitNaiksatam | s3wong: yes | 18:32 |
| garyduan | vinay_yadhav: thanks for initiating the spec | 18:32 |
| s3wong | vinay_yadhav: nice | 18:32 |
| garyduan | vinay_yadhav: have you considered to support one-arm type of service as well | 18:32 |
| SumitNaiksatam | vinay_yadhav: nice work, i do see +1s | 18:32 |
| vinay_yadhav | We would like to see more reviews so that we can get the spec accepted | 18:32 |
| SumitNaiksatam | vinay_yadhav: sorry, i did not get a chance to review the latest | 18:32 |
| garyduan | vinay_yadhav: besides mirroring | 18:32 |
| SumitNaiksatam | vinay_yadhav: any blockers at this point? | 18:32 |
| vinay_yadhav | garyduan: not as of yet | 18:33 |
| vinay_yadhav | i dont see any | 18:33 |
| Kanzhe | vinay_yadhav: I will review your spec this weekend. | 18:33 |
| SumitNaiksatam | Kanzhe: thanks | 18:34 |
| vinay_yadhav | Kanzhe: Thanks | 18:34 |
| SumitNaiksatam | #action SumitNaiksatam Kanzhe garyduan to review https://review.openstack.org/#/c/96149/ | 18:34 |
| vinay_yadhav | cool thanx | 18:34 |
| anil_rao | Thanks | 18:34 |
| garyduan | vinay_yadhav: I will add comments on the spec | 18:35 |
| SumitNaiksatam | i dont see mandeep, so i will skip service chaining, please respond to the review: https://review.openstack.org/#/c/93524 | 18:35 |
| vinay_yadhav | garyduan: thanx | 18:35 |
| s3wong | vinay_yadhav: I will review as well (actually I already added myself as reviewer anyway) | 18:35 |
| SumitNaiksatam | #topic Open Discussion | 18:35 |
| *** openstack changes topic to "Open Discussion (Meeting topic: Networking Advanced Services)" | 18:35 | |
| vinay_yadhav | s3wong: sure | 18:35 |
| *** eguz has quit IRC | 18:35 | |
| SumitNaiksatam | anythin anyone wants to bring up? | 18:35 |
| *** eghobo has joined #openstack-meeting-3 | 18:36 | |
| SumitNaiksatam | i am really hoping that we can get consensus within the team to +1 the specs by next week | 18:36 |
| cgoncalves | SumitNaiksatam: I think jmsoares has something | 18:36 |
| SumitNaiksatam | we can accordingly go to the core reviewers | 18:36 |
| SumitNaiksatam | jmsoares: sure, please go ahead | 18:36 |
| * SumitNaiksatam appreciates everyone staying longer | 18:36 | |
| *** otherwiseguy has quit IRC | 18:36 | |
| jmsoares | about the NFV meeting: apart from logistic stuff, the discussion was focused on 1) Gap analysis (functional), 2) NFV use-cases, and 3) Workload analysis (performance). | 18:36 |
| * SumitNaiksatam and thanks fwaas team for always being patient | 18:37 | |
| SumitNaiksatam | jmsoares: great, thanks for that update | 18:37 |
| jmsoares | 1) What ETSI NFV is defining that doesn't (currently) align with OpenStack. Some members that are in ETSI will try to bring some of the most relevant (to OpenStack) draft documents public. | 18:37 |
| jmsoares | 2) Do a gap analysis focused on NFV use-cases. | 18:37 |
| SumitNaiksatam | jmsoares: any action items for us? | 18:37 |
| jmsoares | this is all I remember :) | 18:37 |
| SumitNaiksatam | jmsoares: sure, any immediate action items for us? | 18:37 |
| jmsoares | not really. | 18:38 |
| s3wong | SumitNaiksatam: currently some NFV team people (including me) will map NFV requirements to the list of BPs | 18:38 |
| SridarK | SumitNaiksatam: no worries | 18:38 |
| SumitNaiksatam | jmsoares: ok | 18:38 |
| s3wong | SumitNaiksatam: I will make sure our BPs get prominently featured :-) | 18:38 |
| SumitNaiksatam | s3wong: great, thanks :-) | 18:38 |
| SumitNaiksatam | SridarK: thanks | 18:38 |
| SumitNaiksatam | ok anything else that we missed? | 18:38 |
| jmsoares | s3wong: exatcly...that's the main action point in the group now. | 18:38 |
| SumitNaiksatam | alrighty, lets call it a wrap | 18:39 |
| s3wong | SumitNaiksatam: +1 | 18:39 |
| SumitNaiksatam | please review the action items after the meeting, and act on them :-P | 18:39 |
| banix | bye everybody | 18:39 |
| SumitNaiksatam | thanks all! | 18:39 |
| SumitNaiksatam | bye | 18:39 |
| s3wong | thanks! | 18:39 |
| SumitNaiksatam | #endmeeting | 18:39 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 18:39 | |
| openstack | Meeting ended Wed Jun 11 18:39:39 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:39 |
| vinay_yadhav | bye | 18:39 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-11-17.32.html | 18:39 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-11-17.32.txt | 18:39 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-11-17.32.log.html | 18:39 |
| *** anil_rao has left #openstack-meeting-3 | 18:39 | |
| *** Kanzhe has quit IRC | 18:39 | |
| *** jmsoares has quit IRC | 18:39 | |
| rkukura | bye | 18:40 |
| *** rkukura has left #openstack-meeting-3 | 18:40 | |
| pcm_ | bye | 18:40 |
| *** s3wong has quit IRC | 18:40 | |
| pgpus | bye | 18:40 |
| SumitNaiksatam | SridarK: garyduan yisun rajesh: there? | 18:40 |
| *** pgpus has quit IRC | 18:40 | |
| garyduan | I am here. | 18:41 |
| SridarK | Hi All, SumitNaiksatam: welcome back | 18:41 |
| SumitNaiksatam | SridarK: thanks :-) | 18:41 |
| *** jamiehannaford has joined #openstack-meeting-3 | 18:41 | |
| SumitNaiksatam | #startmeeting Networking FWaaS | 18:42 |
| openstack | Meeting started Wed Jun 11 18:42:04 2014 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:42 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:42 |
| *** openstack changes topic to " (Meeting topic: Networking FWaaS)" | 18:42 | |
| openstack | The meeting name has been set to 'networking_fwaas' | 18:42 |
| *** hemanthravi has quit IRC | 18:42 | |
| SumitNaiksatam | #info agenda https://wiki.openstack.org/wiki/Meetings/FWaaS | 18:42 |
| SumitNaiksatam | #topic bugs | 18:42 |
| *** openstack changes topic to "bugs (Meeting topic: Networking FWaaS)" | 18:42 | |
| SumitNaiksatam | SridarK: thanks for the terrific work on following up with the bugs | 18:42 |
| badveli | hello all, i would be participating in the meeting | 18:42 |
| SumitNaiksatam | badveli: welcome! | 18:43 |
| badveli | thanks sumit | 18:43 |
| SumitNaiksatam | #link https://bugs.launchpad.net/neutron/+bug/1310857 | 18:43 |
| SridarK | SumitNaiksatam: no worries, thanks to enikanorov: for fixing the last one | 18:43 |
| *** jamiehannaford has quit IRC | 18:43 | |
| SridarK | badveli: hi | 18:43 |
| SumitNaiksatam | enikanorov: thanks | 18:43 |
| SumitNaiksatam | SridarK: link? | 18:43 |
| *** jamiehannaford has joined #openstack-meeting-3 | 18:44 | |
| badveli | hello sridark | 18:44 |
| enikanorov | I need to say that fwaas team need to revisit and clarify state transitions for firewall objects | 18:44 |
| SumitNaiksatam | enikanorov: explain? | 18:44 |
| enikanorov | that was my impression from fixing that gate issue with firewalls | 18:44 |
| *** aihua has quit IRC | 18:45 | |
| *** aihuaedwardli has quit IRC | 18:45 | |
| SridarK | enikanorov: this is also an artifact of the being installed on all routers in the tenant | 18:45 |
| enikanorov | SumitNaiksatam: logic around state transitions is not always clear, it also not quite clear which objects could be updated/deleted from DB in which states | 18:45 |
| SridarK | at least this previous issue | 18:45 |
| SumitNaiksatam | SridarK: yes, i responded to the private email thread yesterday saying pretty much the same | 18:45 |
| SumitNaiksatam | enikanorov: okay, i thought we only have state/status for the firewall resources | 18:46 |
| SumitNaiksatam | enikanorov: and that has a well defined state transition | 18:46 |
| enikanorov | hmm, ok | 18:46 |
| enikanorov | anyway i have changed it a little bit | 18:46 |
| enikanorov | with my latest fix | 18:46 |
| SumitNaiksatam | enikanorov: happy to revisit and fix anything that you may have discovered is inconsistent | 18:46 |
| SumitNaiksatam | enikanorov: link? | 18:47 |
| enikanorov | 1 sec | 18:47 |
| SumitNaiksatam | enikanorov: sure | 18:47 |
| enikanorov | SumitNaiksatam: https://review.openstack.org/#/c/98956/ | 18:47 |
| SumitNaiksatam | enikanorov: thanks | 18:47 |
| SumitNaiksatam | enikanorov: i will take a look, this was approved before i noticed it (i am on personal leave right now) | 18:48 |
| SumitNaiksatam | SridarK: you seemed to have +1'ed | 18:48 |
| enikanorov | btw, SridarK thanks for your recent comment, it explains the issue to me | 18:48 |
| enikanorov | because I was confused of tempest-side of it | 18:49 |
| *** Sukhdev has joined #openstack-meeting-3 | 18:49 | |
| enikanorov | (tempest test waits for firewall to become ACTIVE, but apparently some other router appears and agent changes the status again) | 18:49 |
| SridarK | SumitNaiksatam: yes - i think this is good as with the timing on us being joined at the hip with routers getting added | 18:49 |
| *** prad has joined #openstack-meeting-3 | 18:49 | |
| SridarK | enikanorov: yes | 18:50 |
| enikanorov | SumitNaiksatam: btw I have not yet congratulated you (about the reason of your personal leave :P ) | 18:50 |
| SumitNaiksatam | enikanorov: np, thanks :-) | 18:50 |
| enikanorov | so my congratulations! :) | 18:50 |
| SumitNaiksatam | enikanorov: thanks, quite unexpected, so still coping with it | 18:50 |
| SumitNaiksatam | i mean, unexpected because it was early | 18:51 |
| SumitNaiksatam | 5 weeks early | 18:51 |
| SumitNaiksatam | anyway | 18:51 |
| SumitNaiksatam | so i was again looking at: https://bugs.launchpad.net/neutron/+bug/1310857 | 18:51 |
| *** vinay_yadhav has quit IRC | 18:51 | |
| enikanorov | i see, it's almost always unexpected (in general) :) | 18:51 |
| SumitNaiksatam | enikanorov: hahaha :-) | 18:51 |
| enikanorov | (even if you're expecting it) | 18:51 |
| SumitNaiksatam | enikanorov: yeah | 18:52 |
| garyduan | enikanorov: nice one | 18:52 |
| SumitNaiksatam | the above is the only high priority bug | 18:52 |
| SumitNaiksatam | and the review has been sitting for some time | 18:52 |
| SridarK | yes more comments were added | 18:52 |
| SumitNaiksatam | SridarK garyduan can you also look at: https://review.openstack.org/#/c/90575/ | 18:53 |
| SumitNaiksatam | SridarK: thanks | 18:53 |
| SumitNaiksatam | we need to contact the patch author | 18:53 |
| garyduan | I will | 18:53 |
| SumitNaiksatam | and possilbly markmcclain since he has -2 | 18:53 |
| *** LouisF has quit IRC | 18:54 | |
| garyduan | I reported one bug in Horizon in firewall configuration page | 18:54 |
| SumitNaiksatam | garyduan: thanks, sorry i did not respond to that | 18:55 |
| SumitNaiksatam | garyduan: is it getting attention? | 18:55 |
| garyduan | thanks for SridarK to locate a reviewer for it | 18:55 |
| SumitNaiksatam | garyduan: if not we can ping akihiro | 18:55 |
| SumitNaiksatam | amotoki: there? | 18:55 |
| garyduan | The comment is to add test cases | 18:55 |
| SumitNaiksatam | garyduan: link to review patch? | 18:56 |
| garyduan | https://review.openstack.org/#/c/96654/ | 18:56 |
| *** otherwiseguy has joined #openstack-meeting-3 | 18:57 | |
| *** SridarK has quit IRC | 18:57 | |
| SumitNaiksatam | i took the liberty of adding amotoki to the review | 18:57 |
| SumitNaiksatam | garyduan: let us know if you dont get attention | 18:57 |
| *** SridarK has joined #openstack-meeting-3 | 18:58 | |
| SumitNaiksatam | thanks to abishek for reviewing | 18:58 |
| garyduan | SumitNaiksatam: thanks | 18:58 |
| SridarK | Sorry guys got bounced out | 18:58 |
| SumitNaiksatam | SridarK: np | 18:58 |
| SridarK | garyduan: so u got the review | 18:58 |
| SumitNaiksatam | SridarK garyduan: any other bugs of immediate concern? | 18:58 |
| SumitNaiksatam | SridarK: i have added amotoki as well | 18:58 |
| SridarK | SumitNaiksatam: ok | 18:58 |
| garyduan | SridarK: yes, thanks. KC also reviewed it. | 18:58 |
| garyduan | no | 18:59 |
| SridarK | garyduan: ok | 18:59 |
| SumitNaiksatam | garyduan: ah nice to see KC particpating | 19:00 |
| SumitNaiksatam | we dont have a patch for https://review.openstack.org/#/c/90575/ | 19:00 |
| SumitNaiksatam | it has been claimed | 19:00 |
| SumitNaiksatam | but i dont see a patch | 19:00 |
| *** sarob_ has joined #openstack-meeting-3 | 19:00 | |
| SumitNaiksatam | that said, this is working as designed | 19:01 |
| SumitNaiksatam | sorry i pasted the wrong link | 19:02 |
| SumitNaiksatam | i meant to say we dont have a patch for: #link https://bugs.launchpad.net/neutron/+bug/1323299 | 19:02 |
| SumitNaiksatam | #link SumitNaiksatam SridarK to check with owner of https://bugs.launchpad.net/neutron/+bug/1323299 | 19:03 |
| SumitNaiksatam | #action SumitNaiksatam SridarK to check with owner of https://bugs.launchpad.net/neutron/+bug/1323299 | 19:03 |
| SumitNaiksatam | #action SumitNaiksatam SridarK garyduan to review https://review.openstack.org/#/c/90575/ | 19:03 |
| *** sarob__ has joined #openstack-meeting-3 | 19:04 | |
| *** SridarK_ has joined #openstack-meeting-3 | 19:04 | |
| SumitNaiksatam | enikanorov: you assigned this to yourself: #link https://bugs.launchpad.net/neutron/+bug/1327057 | 19:04 |
| SumitNaiksatam | enikanorov: are you planning on posting a patch? | 19:05 |
| enikanorov | SumitNaiksatam: sure | 19:05 |
| *** SridarK has quit IRC | 19:05 | |
| SumitNaiksatam | enikanorov: i mean i was just asking | 19:05 |
| *** sarob_ has quit IRC | 19:05 | |
| SumitNaiksatam | enikanorov: i know you are swamped | 19:05 |
| SumitNaiksatam | enikanorov: if you dont have time let us know | 19:05 |
| enikanorov | but i'm still able to make some progress :) | 19:06 |
| *** sarob__ has quit IRC | 19:06 | |
| SumitNaiksatam | enikanorov: nice :-) | 19:06 |
| *** sarob has joined #openstack-meeting-3 | 19:06 | |
| SumitNaiksatam | ok we have few more bugs which we have not triaged, will do that | 19:07 |
| SumitNaiksatam | #action SumitNaiksatam to triage “undecided” bugs | 19:07 |
| *** emagana has joined #openstack-meeting-3 | 19:07 | |
| SumitNaiksatam | #topic Juno Plan | 19:08 |
| *** openstack changes topic to "Juno Plan (Meeting topic: Networking FWaaS)" | 19:08 | |
| SumitNaiksatam | #link https://wiki.openstack.org/wiki/Neutron/FWaaS/JunoPlan | 19:08 |
| SumitNaiksatam | SridarK_ garyduan yisun prad: i dont see that the above ^^^ has been updated | 19:08 |
| *** SridarK_ has quit IRC | 19:08 | |
| SumitNaiksatam | sorry, SridarK seems to have updated | 19:09 |
| badveli | sumit, can i look at 1327057 | 19:09 |
| SumitNaiksatam | garyduan: i believe you are blocked on flavors discussion | 19:09 |
| SumitNaiksatam | badveli: sure, can you coordinate with enikanorov | 19:10 |
| *** nati_ueno has quit IRC | 19:10 | |
| badveli | i can work with enikanorov | 19:10 |
| garyduan | SumitNaiksatam: right. | 19:10 |
| garyduan | badveli is sitting next to me. :-) | 19:10 |
| SumitNaiksatam | badveli: i am sorry, i couldn’t decipher your name from the nick | 19:10 |
| SumitNaiksatam | garyduan: ah ok | 19:11 |
| badveli | sumit my name is vishnu, will follow up with enikanorov | 19:11 |
| SumitNaiksatam | garyduan: can you formally introduce badveli to the team? :-) | 19:11 |
| garyduan | Yi also updated his blueprint about Service Object and patch | 19:11 |
| *** SridarK has joined #openstack-meeting-3 | 19:11 | |
| SumitNaiksatam | badveli: Vishnu welcome again | 19:11 |
| SridarK | sorry guys some issue with my machine and keep getting bounced - | 19:12 |
| SumitNaiksatam | garyduan: one sec we will come to the individual blueprint | 19:12 |
| badveli | thanks sumit | 19:12 |
| SumitNaiksatam | SridarK: np | 19:12 |
| SridarK | not sure if u asked me something | 19:12 |
| SumitNaiksatam | SridarK: we assigned you an action item nevertheless :-P | 19:12 |
| SridarK | SumitNaiksatam: :-) | 19:12 |
| garyduan | Vishnu will work with me and Yi, focusing on FWaaS effort | 19:12 |
| prad | SumitNaiksatam, So regarding metering work i have the initial draft of the spec on ceilometer side https://review.openstack.org/#/c/95779/5 .. For HitCounts, Is Rajesh planning to look at it? | 19:12 |
| SumitNaiksatam | garyduan: thanks, thats great | 19:12 |
| SumitNaiksatam | prad: nice, can you please udpate the wiki page with the link | 19:13 |
| prad | SumitNaiksatam, if you guys have time, would probably useful for us to meet up separate and decide whats feasible on FWaaS side for juno-2 | 19:13 |
| SridarK | prad: did u bring up the issue we discussed in the morn | 19:13 |
| SumitNaiksatam | i believe rajesh is not around | 19:13 |
| prad | SumitNaiksatam, ok | 19:13 |
| SumitNaiksatam | prad: we can discussion here or in a separate meeting | 19:13 |
| SumitNaiksatam | prad: please go ahead | 19:13 |
| prad | for one metric we discussed was the usage at the summit.. and i was looking to do that based on create/update events | 19:14 |
| SumitNaiksatam | prad: ok | 19:14 |
| prad | but on ceilometer side, it would be tricky to handle these samples over a period of time | 19:15 |
| prad | even with a transformer | 19:15 |
| SumitNaiksatam | #action prad to update https://wiki.openstack.org/wiki/Neutron/FWaaS/JunoPlan with spec links | 19:15 |
| prad | as we need to grab a definite amount of samples to conclusive determine the usage and there is a chance collector service went down loosing samples | 19:15 |
| SumitNaiksatam | prad: one sec, from a process perspective, we will need specs for any work that needs to be done on the neutron side | 19:15 |
| prad | so in the spec above, i dint add the usage, but would like to see the feasibility | 19:15 |
| SumitNaiksatam | prad: we can coordinate with Rajesh as to who should do it, you or him | 19:16 |
| SumitNaiksatam | prad: if you want to do it, thats great | 19:16 |
| prad | sure | 19:16 |
| SumitNaiksatam | prad: sorry, i interrupted you on the usage part | 19:16 |
| prad | SumitNaiksatam, if we can get the bw/connections info similar to how LBaaS is giving us on FWaaS side, that would be a goos start | 19:16 |
| prad | if you see the metrics table in the spec, i have some info there | 19:16 |
| SumitNaiksatam | #action prad to sync up with RajeshMohan on hit counts, perhpaps suggest a separate meeting with the fwaas team | 19:17 |
| SumitNaiksatam | prad: that is tough | 19:17 |
| prad | ok | 19:17 |
| SumitNaiksatam | prad: link to metrics? | 19:17 |
| prad | SumitNaiksatam, https://review.openstack.org/#/c/95779/5/specs/juno/ceilometer-meter-fwaas.rst | 19:18 |
| SumitNaiksatam | #topic Ceilometer requirements | 19:18 |
| *** openstack changes topic to "Ceilometer requirements (Meeting topic: Networking FWaaS)" | 19:18 | |
| SumitNaiksatam | #link https://review.openstack.org/#/c/95779/5/specs/juno/ceilometer-meter-fwaas.rst | 19:18 |
| SumitNaiksatam | SridarK garyduan yisun: you have thoughts on capturing the usage? | 19:18 |
| prad | SumitNaiksatam, also i see a few api calls that are already there on neutron side.. like list_firewall, list_fw_rule and list_fw_policy which would be useful in general to track a fw existence and bill users | 19:18 |
| SumitNaiksatam | prad: sure | 19:19 |
| prad | SumitNaiksatam, so i can at least get started on implementing one of two on these lines.. the big ones are connections and bw | 19:19 |
| SumitNaiksatam | prad: ok thats good to hear, for that you dont need anything more on the fwaas side? | 19:19 |
| garyduan | Probably not all counters can be retrieved easily from iptables | 19:20 |
| *** SridarK has quit IRC | 19:20 | |
| SumitNaiksatam | garyduan: yeah, my thinking too | 19:20 |
| SumitNaiksatam | garyduan: can we come up with something that is reasonable, perhaps not as detailed? | 19:20 |
| SumitNaiksatam | * but perhaps | 19:20 |
| prad | SumitNaiksatam, for connections and bw.. i do need a call similar to retrieve_pool_stats on lbaas side | 19:20 |
| SumitNaiksatam | prad: yeah, sure i got that | 19:21 |
| SumitNaiksatam | prad: that will require more discussion | 19:21 |
| prad | sure understand | 19:21 |
| SumitNaiksatam | prad: can we say that you have three sets of requirements | 19:21 |
| *** SridarK has joined #openstack-meeting-3 | 19:21 | |
| SumitNaiksatam | prad: there is one set which is already satisfied by the list_* calls | 19:21 |
| prad | SumitNaiksatam, yea other two are usage and stats | 19:22 |
| SumitNaiksatam | prad: then there is the second one for which you need to support with the hit counts | 19:22 |
| prad | yep | 19:22 |
| SumitNaiksatam | prad: and the third is the connection/bandwith tracking | 19:22 |
| SumitNaiksatam | prad: ok | 19:22 |
| SumitNaiksatam | prad: i think we will tackle them in that priority | 19:23 |
| SumitNaiksatam | prad: i find it difficult that we will get to the last one in Juno | 19:23 |
| prad | yea ..i can get the first implemented on ceilometer side without waiting | 19:23 |
| SumitNaiksatam | prad: ok good | 19:23 |
| SumitNaiksatam | prad: thanks for the udpate | 19:23 |
| prad | sure, if we can coordinate with Rajesh soon it would be helpful to make the plan clear for fwaas side | 19:24 |
| prad | sure | 19:24 |
| SumitNaiksatam | and for joining the meeting, to make progress it will be nice if you can participate in these meetings, so we can give you the support you need | 19:24 |
| prad | SumitNaiksatam, will do sir | 19:24 |
| SridarK | SumitNaiksatam: i will also reach out to Rajesh to check | 19:24 |
| SumitNaiksatam | prad: sure, i can send out the email today (unless you or SridarK want to do it) | 19:24 |
| SumitNaiksatam | SridarK: sure go ahead | 19:24 |
| SumitNaiksatam | lets move on | 19:24 |
| prad | thx | 19:24 |
| SumitNaiksatam | #topic Service objects | 19:24 |
| *** openstack changes topic to "Service objects (Meeting topic: Networking FWaaS)" | 19:24 | |
| SumitNaiksatam | i think we can go a little over with our meeting time | 19:25 |
| SumitNaiksatam | yisun: there? | 19:25 |
| SumitNaiksatam | i know i asked a bunch of questions and yisun posted a new patch set | 19:25 |
| garyduan | He is in meeting | 19:25 |
| SumitNaiksatam | garyduan: ok | 19:25 |
| SridarK | I have been reviewing also | 19:25 |
| SumitNaiksatam | garyduan: you can proxy | 19:25 |
| SumitNaiksatam | SridarK: absolutely | 19:25 |
| SumitNaiksatam | SridarK: but i think you are in agreement with the spec | 19:26 |
| SridarK | i am ok - just need clarification on service obj to service group | 19:26 |
| SridarK | yes | 19:26 |
| SridarK | now we are thinking 1 : 1 | 19:26 |
| SumitNaiksatam | whereas i am still having a bit of an issue with there being so much overlap with the firewall rule | 19:26 |
| SridarK | but can we effect a 1 : many (serve obj : src grp) later on | 19:26 |
| garyduan | Sridar, Yi and me had some discussion on the spec, and we are in agreement | 19:26 |
| SridarK | will there be a backwards compatibility issue ? | 19:27 |
| SumitNaiksatam | i am not sure that the neutron core team is going to be happy with the subsets of the attributes being defined in different places | 19:27 |
| *** sarob has quit IRC | 19:27 | |
| garyduan | Service group is optional | 19:27 |
| SumitNaiksatam | i am trying to come up with a more concrete suggestion | 19:27 |
| SumitNaiksatam | garyduan: that is fine | 19:27 |
| *** sarob has joined #openstack-meeting-3 | 19:27 | |
| *** markmcclain has quit IRC | 19:27 | |
| SumitNaiksatam | garyduan: but concern still stand | 19:27 |
| SumitNaiksatam | stands | 19:27 |
| garyduan | current way of inputting protocol and port are still allowed | 19:28 |
| SumitNaiksatam | garyduan: i agree and understand | 19:28 |
| SumitNaiksatam | garyduan: i am trying to figure out if we can reuse existing definitions | 19:28 |
| SumitNaiksatam | does that make sense to the you guys or its just me? | 19:28 |
| SridarK | SumitNaiksatam: by existing what do u mean ? | 19:28 |
| garyduan | SumitNaiksatam: reuse? | 19:29 |
| SumitNaiksatam | SridarK: attributes in the firewall rule | 19:29 |
| SridarK | SumitNaiksatam: hmm - u mean just add to the rule directly ? | 19:29 |
| SumitNaiksatam | i am not comfortable with the same attributes being defined in many difrerent places | 19:29 |
| SumitNaiksatam | SridarK: yeah, i am trying to think what is the good way to do that | 19:29 |
| garyduan | SumitNaiksatam: you mean allowing protocol/port and service group at the same time? | 19:30 |
| *** Cathy_ has quit IRC | 19:30 | |
| SumitNaiksatam | garyduan: i am saying that there is lot of overlap between the firewall_rule and the service_object | 19:30 |
| garyduan | Can we say, the current model is experimental, and we can plan to face out protocol/port setting in firewall rule? | 19:31 |
| *** sarob has quit IRC | 19:32 | |
| SridarK | Hmm! so one will always need to use a service group ? | 19:32 |
| SumitNaiksatam | garyduan: that will be challenging | 19:32 |
| SumitNaiksatam | SridarK: yeah good point, thats the concern | 19:32 |
| garyduan | SridarK: service group and object | 19:32 |
| garyduan | There will be predefined objects | 19:33 |
| SridarK | I guess with service groups - most vendor implementions do have this overlap | 19:33 |
| SumitNaiksatam | can service object use a firewall_rule? | 19:33 |
| SumitNaiksatam | ignore if thats a dumb question | 19:34 |
| garyduan | I am not sure. I will have to ask Yi | 19:34 |
| SumitNaiksatam | garyduan: ok | 19:34 |
| SumitNaiksatam | #topic FWaaS and DVR | 19:35 |
| *** openstack changes topic to "FWaaS and DVR (Meeting topic: Networking FWaaS)" | 19:35 | |
| SumitNaiksatam | did yisun manage to send the email to the mailing list | 19:35 |
| SumitNaiksatam | unfortunately, i could not respond to the thread he started in the team | 19:35 |
| garyduan | He has been in the DVR meeting | 19:35 |
| SumitNaiksatam | garyduan: ok good | 19:36 |
| SumitNaiksatam | garyduan: and how is that shaping up? | 19:36 |
| SumitNaiksatam | garyduan: do we have consensus on an approach? | 19:36 |
| garyduan | There is a way to support FWaaS with DVR | 19:36 |
| SumitNaiksatam | #action yisun to update team on FWaaS/DVR support | 19:36 |
| garyduan | but performance and packet flow is quite complicated | 19:36 |
| garyduan | so still in discussing | 19:37 |
| SumitNaiksatam | garyduan: great, thats good to hear | 19:37 |
| SumitNaiksatam | #action garyduan to check with yisun if service_objects can reuse firewall_rules in some way | 19:37 |
| *** SridarK has quit IRC | 19:37 | |
| SumitNaiksatam | #topic Open Discussion | 19:38 |
| garyduan | by reusing, you mean translate existing protocol/ports to service object? | 19:38 |
| *** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)" | 19:38 | |
| SumitNaiksatam | #undo | 19:38 |
| openstack | Removing item from minutes: <ircmeeting.items.Topic object at 0x23b9f90> | 19:38 |
| *** SridarK has joined #openstack-meeting-3 | 19:39 | |
| SumitNaiksatam | garyduan: i meant that we dont have to repeat the overlapping attributes in two places | 19:39 |
| SridarK | really sorry guys i am having terrible connectivity today | 19:39 |
| *** emaganap has joined #openstack-meeting-3 | 19:39 | |
| garyduan | SumitNaiksatam: I will discuss that with Yi | 19:40 |
| badveli | goal of the service object much more than the firewall rule | 19:40 |
| SumitNaiksatam | SridarK: np, you got back in time before we have you the next action item ;-P | 19:40 |
| badveli | if we go through the bp | 19:40 |
| SumitNaiksatam | badveli: i agree | 19:40 |
| SridarK | :-) | 19:40 |
| SumitNaiksatam | badveli: i dont dispute that | 19:40 |
| SridarK | but we still want to anchor to the FW rule ? | 19:40 |
| SumitNaiksatam | SridarK: i am just thinking loud | 19:41 |
| garyduan | yes. | 19:41 |
| badveli | this is used to group | 19:41 |
| badveli | as per the bp | 19:41 |
| SridarK | SumitNaiksatam: no good - best to hash out now | 19:41 |
| SumitNaiksatam | SridarK garyduan badveli: brain wave (based on what SridarK just said), what if we do attribute extension for firewall_rule? | 19:41 |
| *** emagana has quit IRC | 19:42 | |
| SridarK | oh just have an extension for this new attribute ? | 19:42 |
| badveli | but the service group can be thaught of like a container | 19:42 |
| SumitNaiksatam | SridarK: yeah | 19:42 |
| badveli | and be used by the firewall | 19:42 |
| badveli | rule | 19:42 |
| SumitNaiksatam | badveli: ah good point | 19:42 |
| SumitNaiksatam | let me think a little more | 19:43 |
| SridarK | SumitNaiksatam: yes i agree with badveli - i think that is the intent | 19:43 |
| *** coolsvap is now known as coolsvap|afk | 19:43 | |
| SumitNaiksatam | #action SumitNaiksatam to explore if any attribute extension can be used to support service_object | 19:43 |
| SridarK | SumitNaiksatam: perhaps we can also continue more discussion offline | 19:43 |
| SumitNaiksatam | badveli SridarK: i agree my suggestion was turning the model on its head | 19:43 |
| garyduan | sure | 19:43 |
| SumitNaiksatam | SridarK: yes | 19:43 |
| SumitNaiksatam | so we are 3 mins over time | 19:44 |
| SumitNaiksatam | #topic Open Discussion | 19:44 |
| *** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)" | 19:44 | |
| SumitNaiksatam | SridarK: we dont have zones spec, so i skipped | 19:44 |
| SridarK | SumitNaiksatam: i will get a zones review out real soon | 19:44 |
| SumitNaiksatam | anything else? | 19:44 |
| SumitNaiksatam | SridarK: thanks much | 19:44 |
| *** Sukhdev has quit IRC | 19:44 | |
| SridarK | nothing much else | 19:44 |
| SumitNaiksatam | SridarK: but we really appreciate that you are prioritizing attention to the bugs | 19:44 |
| SridarK | SumitNaiksatam: no worries - it has been "interesting" :-) | 19:45 |
| SumitNaiksatam | SridarK: we need to fix the existing issues even as we plan for new features | 19:45 |
| SumitNaiksatam | SridarK: i am sure, but happy that you are “enjoying” it :-) | 19:45 |
| SridarK | SumitNaiksatam: agree | 19:45 |
| SumitNaiksatam | garyduan prad badveli: anything else you want to discuss? | 19:45 |
| SridarK | SumitNaiksatam: perhaps i should not have said that :-) | 19:45 |
| SumitNaiksatam | SridarK: no i put words into your mouth :-P | 19:46 |
| SridarK | prad: we will follow up more on this metering too | 19:46 |
| SridarK | :-) | 19:46 |
| SumitNaiksatam | btw, i just wanted to say thanks all for your support in the past few days, it was challenging to say the least, and it continues to be so | 19:46 |
| SridarK | SumitNaiksatam: is this time from the morning ur "relaxation" ? | 19:47 |
| SridarK | :-) | 19:47 |
| SumitNaiksatam | :-) | 19:47 |
| SridarK | now u have to get back to some really hard work now | 19:47 |
| SumitNaiksatam | i am not so much concerned about my relaxation | 19:47 |
| SridarK | :-) | 19:47 |
| SumitNaiksatam | SridarK: :-) | 19:47 |
| SumitNaiksatam | all right thanks all, lets call it a wrap for today | 19:47 |
| SridarK | Ok bye all | 19:48 |
| SumitNaiksatam | lots of AIs to deal with :-P | 19:48 |
| SumitNaiksatam | #endmeeting | 19:48 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 19:48 | |
| openstack | Meeting ended Wed Jun 11 19:48:13 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:48 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-06-11-18.42.html | 19:48 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-06-11-18.42.txt | 19:48 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-06-11-18.42.log.html | 19:48 |
| *** pcm_ has left #openstack-meeting-3 | 19:50 | |
| *** nati_ueno has joined #openstack-meeting-3 | 19:52 | |
| *** jamiehannaford has quit IRC | 19:52 | |
| *** sarob has joined #openstack-meeting-3 | 19:54 | |
| *** sarob has quit IRC | 19:58 | |
| *** jackib has joined #openstack-meeting-3 | 20:02 | |
| *** markmcclain has joined #openstack-meeting-3 | 20:02 | |
| *** jackib has quit IRC | 20:02 | |
| *** mwagner_lap has quit IRC | 20:04 | |
| *** jackib has joined #openstack-meeting-3 | 20:04 | |
| *** jackib has quit IRC | 20:09 | |
| *** markmcclain has quit IRC | 20:09 | |
| *** pballand has joined #openstack-meeting-3 | 20:10 | |
| *** nati_ueno has quit IRC | 20:13 | |
| *** jackib has joined #openstack-meeting-3 | 20:17 | |
| *** nati_ueno has joined #openstack-meeting-3 | 20:21 | |
| *** jackib has quit IRC | 20:24 | |
| *** enikanorov has quit IRC | 20:30 | |
| *** emaganap has quit IRC | 20:31 | |
| *** sarob has joined #openstack-meeting-3 | 20:31 | |
| *** emagana has joined #openstack-meeting-3 | 20:31 | |
| *** jamielennox is now known as jamielennox|away | 20:34 | |
| *** sarob has quit IRC | 20:35 | |
| *** mwagner_lap has joined #openstack-meeting-3 | 20:42 | |
| *** MaxV has joined #openstack-meeting-3 | 20:48 | |
| *** mwagner_lap has quit IRC | 20:56 | |
| *** MaxV has quit IRC | 20:59 | |
| *** MaxV has joined #openstack-meeting-3 | 20:59 | |
| *** pballand has quit IRC | 21:01 | |
| *** sarob has joined #openstack-meeting-3 | 21:03 | |
| *** pballand has joined #openstack-meeting-3 | 21:05 | |
| *** mfer has quit IRC | 21:06 | |
| *** sarob has quit IRC | 21:07 | |
| *** emagana has quit IRC | 21:08 | |
| *** sarob has joined #openstack-meeting-3 | 21:17 | |
| *** leifz has quit IRC | 21:18 | |
| *** davidlenwell has quit IRC | 21:18 | |
| *** davidlenwell has joined #openstack-meeting-3 | 21:19 | |
| *** leifz has joined #openstack-meeting-3 | 21:30 | |
| *** banix has quit IRC | 21:31 | |
| *** beyounn has joined #openstack-meeting-3 | 21:33 | |
| *** Sukhdev has joined #openstack-meeting-3 | 21:34 | |
| *** lblanchard has quit IRC | 21:35 | |
| *** flaviof is now known as flaviof_zzz | 21:36 | |
| *** lblanchard has joined #openstack-meeting-3 | 21:38 | |
| *** peristeri has quit IRC | 21:39 | |
| *** SridarK has quit IRC | 21:47 | |
| *** nedbat_ is now known as nedbat | 21:51 | |
| *** mwagner_lap has joined #openstack-meeting-3 | 21:52 | |
| *** markmcclain has joined #openstack-meeting-3 | 21:54 | |
| *** pballand has quit IRC | 22:00 | |
| *** lcheng has quit IRC | 22:02 | |
| *** thomasem has quit IRC | 22:07 | |
| *** sarob has quit IRC | 22:09 | |
| *** sarob has joined #openstack-meeting-3 | 22:10 | |
| *** carl_baldwin has quit IRC | 22:11 | |
| *** nati_ueno has quit IRC | 22:14 | |
| *** nedbat has quit IRC | 22:14 | |
| *** sarob has quit IRC | 22:14 | |
| *** pballand has joined #openstack-meeting-3 | 22:15 | |
| *** lcheng has joined #openstack-meeting-3 | 22:17 | |
| *** markmcclain has quit IRC | 22:19 | |
| *** prad has quit IRC | 22:26 | |
| *** lcheng has quit IRC | 22:26 | |
| *** markmcclain has joined #openstack-meeting-3 | 22:30 | |
| *** nati_ueno has joined #openstack-meeting-3 | 22:31 | |
| *** MaxV_ has joined #openstack-meeting-3 | 22:32 | |
| *** otherwiseguy has quit IRC | 22:32 | |
| *** sarob has joined #openstack-meeting-3 | 22:32 | |
| *** MaxV has quit IRC | 22:34 | |
| *** lblanchard has quit IRC | 22:41 | |
| *** pballand has quit IRC | 22:46 | |
| *** MaxV_ has quit IRC | 22:50 | |
| *** jamielennox|away is now known as jamielennox | 23:00 | |
| *** seizadi has joined #openstack-meeting-3 | 23:11 | |
| *** pballand has joined #openstack-meeting-3 | 23:11 | |
| *** yamahata has quit IRC | 23:21 | |
| *** Sukhdev has quit IRC | 23:34 | |
| *** banix has joined #openstack-meeting-3 | 23:37 | |
| *** pballand has quit IRC | 23:45 | |
| *** pballand has joined #openstack-meeting-3 | 23:48 | |
| *** briancurtin has joined #openstack-meeting-3 | 23:48 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!