| *** david_lyle_ has quit IRC | 00:00 | |
| *** markmcclain has quit IRC | 00:04 | |
| *** lblanchard has quit IRC | 00:05 | |
| *** SumitNaiksatam has quit IRC | 00:11 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 00:19 | |
| *** wchrisj has quit IRC | 00:37 | |
| *** devlaps1 has quit IRC | 00:37 | |
| *** sarob has joined #openstack-meeting-3 | 00:49 | |
| *** dolphm has quit IRC | 00:49 | |
| *** cjellick has quit IRC | 00:50 | |
| *** wchrisj has joined #openstack-meeting-3 | 00:51 | |
| *** sarob has quit IRC | 00:53 | |
| *** dolphm has joined #openstack-meeting-3 | 00:54 | |
| *** wchrisj has quit IRC | 00:56 | |
| *** julim has quit IRC | 00:56 | |
| *** wchrisj has joined #openstack-meeting-3 | 01:00 | |
| *** wchrisj has quit IRC | 01:12 | |
| *** wchrisj has joined #openstack-meeting-3 | 01:18 | |
| *** fungi has quit IRC | 01:29 | |
| *** banix has joined #openstack-meeting-3 | 01:36 | |
| *** wchrisj has quit IRC | 01:36 | |
| *** wchrisj has joined #openstack-meeting-3 | 01:43 | |
| *** alexpilotti has quit IRC | 01:43 | |
| *** sarob has joined #openstack-meeting-3 | 01:50 | |
| *** sarob has quit IRC | 01:56 | |
| *** wchrisj has quit IRC | 02:01 | |
| *** wchrisj has joined #openstack-meeting-3 | 02:11 | |
| *** mwagner_lap has joined #openstack-meeting-3 | 02:46 | |
| *** sarob has joined #openstack-meeting-3 | 02:53 | |
| *** xianghui has joined #openstack-meeting-3 | 02:54 | |
| *** sarob has quit IRC | 02:56 | |
| *** sarob has joined #openstack-meeting-3 | 02:57 | |
| *** jthopkin has joined #openstack-meeting-3 | 02:57 | |
| *** dguitarbite has joined #openstack-meeting-3 | 02:58 | |
| *** sarob__ has joined #openstack-meeting-3 | 02:58 | |
| *** sarob has quit IRC | 03:01 | |
| *** sarob__ has quit IRC | 03:05 | |
| *** sarob has joined #openstack-meeting-3 | 03:06 | |
| *** sarob has quit IRC | 03:10 | |
| *** jthopkin has quit IRC | 03:13 | |
| *** sarob has joined #openstack-meeting-3 | 03:16 | |
| *** fungi has joined #openstack-meeting-3 | 03:32 | |
| *** sarob has quit IRC | 03:46 | |
| *** MaxV has joined #openstack-meeting-3 | 03:46 | |
| *** sarob has joined #openstack-meeting-3 | 03:46 | |
| *** wchrisj has quit IRC | 03:48 | |
| *** MaxV has quit IRC | 03:50 | |
| *** sarob has quit IRC | 03:51 | |
| *** banix has quit IRC | 03:53 | |
| *** dguitarbite has quit IRC | 03:58 | |
| *** wchrisj has joined #openstack-meeting-3 | 04:00 | |
| *** banix has joined #openstack-meeting-3 | 04:03 | |
| *** dguitarbite has joined #openstack-meeting-3 | 04:04 | |
| *** eghobo has joined #openstack-meeting-3 | 04:26 | |
| *** wchrisj has quit IRC | 04:33 | |
| *** sarob has joined #openstack-meeting-3 | 04:47 | |
| *** banix has quit IRC | 04:49 | |
| *** sarob has quit IRC | 04:53 | |
| *** xianghui has quit IRC | 05:00 | |
| *** amotoki has joined #openstack-meeting-3 | 05:06 | |
| *** SumitNaiksatam has quit IRC | 05:07 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 05:10 | |
| *** xianghui has joined #openstack-meeting-3 | 05:17 | |
| *** tmazur has joined #openstack-meeting-3 | 05:36 | |
| *** sarob has joined #openstack-meeting-3 | 05:50 | |
| *** sarob has quit IRC | 05:54 | |
| *** david-lyle has joined #openstack-meeting-3 | 05:57 | |
| *** david-lyle has quit IRC | 06:02 | |
| *** yamahata has quit IRC | 06:21 | |
| *** eghobo has quit IRC | 06:41 | |
| *** MaxV has joined #openstack-meeting-3 | 06:48 | |
| *** sarob has joined #openstack-meeting-3 | 06:51 | |
| *** MaxV has quit IRC | 06:53 | |
| *** sarob has quit IRC | 06:56 | |
| *** sarob has joined #openstack-meeting-3 | 07:01 | |
| *** sarob has quit IRC | 07:05 | |
| *** mrunge has joined #openstack-meeting-3 | 07:31 | |
| *** MaxV has joined #openstack-meeting-3 | 07:31 | |
| *** jtomasek has quit IRC | 07:32 | |
| *** jcoufal has joined #openstack-meeting-3 | 07:47 | |
| *** sarob has joined #openstack-meeting-3 | 07:54 | |
| *** d0ugal has joined #openstack-meeting-3 | 07:58 | |
| *** d0ugal has quit IRC | 07:58 | |
| *** d0ugal has joined #openstack-meeting-3 | 07:58 | |
| *** sarob has quit IRC | 07:58 | |
| *** MaxV has quit IRC | 08:09 | |
| *** tmazur has quit IRC | 08:09 | |
| *** saju_m has joined #openstack-meeting-3 | 08:12 | |
| *** ttrifonov_zZzz is now known as ttrifonov | 08:18 | |
| *** MaxV has joined #openstack-meeting-3 | 08:41 | |
| *** nacim has joined #openstack-meeting-3 | 08:44 | |
| *** sarob has joined #openstack-meeting-3 | 08:55 | |
| *** sarob has quit IRC | 09:02 | |
| *** jrist has quit IRC | 09:11 | |
| *** johnthetubaguy has joined #openstack-meeting-3 | 09:24 | |
| *** jrist has joined #openstack-meeting-3 | 09:24 | |
| *** lucian1 has joined #openstack-meeting-3 | 09:27 | |
| *** sarob has joined #openstack-meeting-3 | 09:58 | |
| *** jtomasek has joined #openstack-meeting-3 | 10:00 | |
| *** sarob has quit IRC | 10:02 | |
| *** mwagner_lap has quit IRC | 10:52 | |
| *** sarob has joined #openstack-meeting-3 | 10:59 | |
| *** sarob has quit IRC | 11:05 | |
| *** johnthetubaguy is now known as johnthebpguy | 11:15 | |
| *** lblanchard has joined #openstack-meeting-3 | 12:01 | |
| *** sarob has joined #openstack-meeting-3 | 12:02 | |
| *** sarob has quit IRC | 12:06 | |
| *** johnthetubaguy has joined #openstack-meeting-3 | 12:08 | |
| *** johnthebpguy has quit IRC | 12:09 | |
| *** jpomero has quit IRC | 12:09 | |
| *** xianghui has quit IRC | 12:26 | |
| *** jcoufal has quit IRC | 12:50 | |
| *** jcoufal has joined #openstack-meeting-3 | 12:51 | |
| *** sarob has joined #openstack-meeting-3 | 13:03 | |
| *** yamahata has joined #openstack-meeting-3 | 13:03 | |
| *** sarob has quit IRC | 13:08 | |
| *** dguitarbite has quit IRC | 13:11 | |
| *** julim has joined #openstack-meeting-3 | 13:17 | |
| *** mfer has joined #openstack-meeting-3 | 13:26 | |
| *** peristeri has joined #openstack-meeting-3 | 13:42 | |
| *** banix has joined #openstack-meeting-3 | 13:44 | |
| *** wchrisj has joined #openstack-meeting-3 | 13:57 | |
| *** ttrifonov is now known as ttrifonov_zZzz | 13:58 | |
| *** nextone92 has joined #openstack-meeting-3 | 14:06 | |
| *** sarob has joined #openstack-meeting-3 | 14:06 | |
| *** jthopkin has joined #openstack-meeting-3 | 14:07 | |
| *** amotoki has quit IRC | 14:09 | |
| *** sarob has quit IRC | 14:10 | |
| *** safchain has joined #openstack-meeting-3 | 14:12 | |
| *** nextone92 has quit IRC | 14:12 | |
| *** markmcclain has joined #openstack-meeting-3 | 14:17 | |
| *** markmcclain has quit IRC | 14:17 | |
| *** markmcclain has joined #openstack-meeting-3 | 14:19 | |
| *** saju_m has quit IRC | 14:22 | |
| *** xianghui has joined #openstack-meeting-3 | 14:31 | |
| *** xianghui has quit IRC | 14:33 | |
| *** xianghui has joined #openstack-meeting-3 | 14:36 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 14:47 | |
| *** johnthetubaguy1 has joined #openstack-meeting-3 | 14:52 | |
| *** johnthetubaguy1 has quit IRC | 14:53 | |
| *** johnthetubaguy1 has joined #openstack-meeting-3 | 14:53 | |
| *** rossella_ has joined #openstack-meeting-3 | 14:53 | |
| *** xianghui has quit IRC | 14:55 | |
| *** ajo has joined #openstack-meeting-3 | 14:55 | |
| ajo | hi carl_baldwin ;) | 14:55 |
|---|---|---|
| carl_baldwin | ajo: Greetings | 14:56 |
| *** xianghui has joined #openstack-meeting-3 | 14:56 | |
| *** rook has joined #openstack-meeting-3 | 14:58 | |
| ajo | hi rook ;) | 14:58 |
| rook | ajo hey! thanks for the heads up | 14:58 |
| carl_baldwin | Well, let's get started. | 15:00 |
| carl_baldwin | #startmeeting neutron_l3 | 15:00 |
| openstack | Meeting started Thu Mar 13 15:00:20 2014 UTC and is due to finish in 60 minutes. The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| *** openstack changes topic to " (Meeting topic: neutron_l3)" | 15:00 | |
| openstack | The meeting name has been set to 'neutron_l3' | 15:00 |
| carl_baldwin | #topic Announcements | 15:00 |
| *** openstack changes topic to "Announcements (Meeting topic: neutron_l3)" | 15:00 | |
| carl_baldwin | #link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam | 15:00 |
| *** Sudhakar_ has joined #openstack-meeting-3 | 15:00 | |
| carl_baldwin | First, I didn’t plan for daylight savings time when I chose the time for this meeting. | 15:01 |
| carl_baldwin | The time shift has caused a bit of a problem for me. | 15:01 |
| carl_baldwin | I'd like to suggest a couple of possible meeting times. Both Thursday. | 15:01 |
| carl_baldwin | The first is an hour earlier. I know that makes things very early for a few in Western US. | 15:02 |
| ajo | For me it's actually better , +1 | 15:02 |
| *** julim has quit IRC | 15:02 | |
| carl_baldwin | The second is two hours later which could be difficult for others in other parts of the world. | 15:02 |
| safchain | for me both are ok | 15:03 |
| *** julim has joined #openstack-meeting-3 | 15:03 | |
| safchain | HI all btw | 15:03 |
| carl_baldwin | safchain: hi | 15:03 |
| ajo | safchain, hi :) | 15:03 |
| *** ywu has joined #openstack-meeting-3 | 15:04 | |
| carl_baldwin | I'll wait a few days for others who might be reading the meeting logs to chime email. Ping me on irc or email with any concerns. I'll announce the meeting time before next week. And, I'll consider the next shift in daylight savings time. ;) | 15:04 |
| ajo | sure, thanks carl_baldwin | 15:05 |
| carl_baldwin | #topic l3-high-availability | 15:05 |
| *** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)" | 15:05 | |
| carl_baldwin | safchain: Anything to report? | 15:05 |
| *** johnthetubaguy has quit IRC | 15:05 | |
| safchain | currently I'm working on the conntrackd integration, | 15:05 |
| safchain | The assaf's patch has to be reworked a bit to support multicast | 15:06 |
| carl_baldwin | I need to review again. Anything new on the FFE? I fear that it didn't happen. | 15:07 |
| *** sarob has joined #openstack-meeting-3 | 15:07 | |
| safchain | I don't know if all of you have tested patches | 15:07 |
| safchain | carl_baldwin, no new for FFE | 15:07 |
| *** mwagner_lap has joined #openstack-meeting-3 | 15:07 | |
| *** cjellick has joined #openstack-meeting-3 | 15:07 | |
| *** pcm_ has joined #openstack-meeting-3 | 15:08 | |
| ajo | I couldn't test yet safchain, but I will try to allocate some time for it. | 15:08 |
| carl_baldwin | Okay. The sub team page has links and information about reviewing and testing but I'll admit I've not yet tested. | 15:08 |
| *** cjellick has quit IRC | 15:08 | |
| safchain | carl_baldwin, I think this is almost everything for me, just need more feed back with functionnal test | 15:08 |
| *** cjellick has joined #openstack-meeting-3 | 15:09 | |
| ajo | safchain, do you have some functional test examples? | 15:09 |
| ajo | I could get some people on our team to provide feedback on that. | 15:09 |
| carl_baldwin | Okay, I am looking forward to running it. I need a multi host development setup soon anyway. | 15:09 |
| carl_baldwin | #link https://docs.google.com/document/d/1P2OnlKAGMeSZTbGENNAKOse6B2TRXJ8keUMVvtUCUSM/edit# | 15:09 |
| safchain | ajo, I will add some test use cases on the doc. | 15:10 |
| carl_baldwin | ajo: ^ This is the doc. | 15:10 |
| *** SumitNaiksatam has quit IRC | 15:10 | |
| ajo | Thanks, I mean, if we have already some kind of initial functional test written for this. I will keep a link to this doc for manual testing. | 15:11 |
| safchain | ajo, not yet | 15:11 |
| ajo | ok, it's not easy | 15:11 |
| safchain | ajo, but tempest test should works with HA enabled | 15:12 |
| ajo | ok, that's a good start | 15:12 |
| *** sarob has quit IRC | 15:12 | |
| carl_baldwin | safchain: anything else? | 15:12 |
| *** YorikSar has joined #openstack-meeting-3 | 15:13 | |
| safchain | It's ok for me | 15:13 |
| carl_baldwin | #topic neutron-ovs-dvr | 15:13 |
| *** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)" | 15:13 | |
| carl_baldwin | Doesn't look like Swami is around. | 15:14 |
| carl_baldwin | Swami is still working on detailing changes to L3. | 15:14 |
| carl_baldwin | The doc for L2 is up. Could use more review. | 15:14 |
| carl_baldwin | #link https://docs.google.com/document/d/1depasJSnGZPOnRLxEC_PYsVLcGVFXZLqP52RFTe21BE/edit#heading=h.5w7clq272tji | 15:14 |
| safchain | Sure, I plan to review it by the end of the week | 15:15 |
| carl_baldwin | Also looking in to integrating the HA L3 and HA DHCP was discussed. | 15:15 |
| carl_baldwin | safchain: great | 15:16 |
| Sudhakar_ | hi all... | 15:16 |
| ajo | hi Sudhakar_ | 15:17 |
| carl_baldwin | Sudhakar_: hi | 15:17 |
| safchain | carl_baldwin, yes I'll try to ping swami after reviewing the doc | 15:17 |
| Sudhakar_ | carl_baldwin, is there a doc about HA DHCP? | 15:17 |
| safchain | hi Sudhakar_ | 15:17 |
| Sudhakar_ | hi ajo... | 15:17 |
| carl_baldwin | Sudhakar_: I don't think there is a doc yet about it. Only some initial discussion expressing interest in starting that work. | 15:17 |
| Sudhakar_ | hi carl | 15:17 |
| Sudhakar_ | Did Swami initiate the discussion? | 15:18 |
| carl_baldwin | Sudhakar_: yes | 15:18 |
| Sudhakar_ | Ok. I have some context then.. | 15:18 |
| Sudhakar_ | I am Swami's colleague ..based out of India | 15:18 |
| Sudhakar_ | basically we were thinking of an Agent monitoring service....which can be used to monitor different agents ... | 15:19 |
| Sudhakar_ | typically useful for L3 and DHCP when we have multiple NNs | 15:19 |
| ajo | Sudhakar_, something like rpcdaemon ? | 15:20 |
| Sudhakar_ | not exactly.. | 15:20 |
| Sudhakar_ | a thread which can started from plugin itself... | 15:20 |
| Sudhakar_ | and act based on the agent report_states... | 15:20 |
| *** mrunge has quit IRC | 15:21 | |
| ajo | Sudhakar_, what kind of actions? | 15:21 |
| Sudhakar_ | for ex: if a DHCP agent hosting a particular network goes down ....and we have another active DHCP agent in the cloud... | 15:22 |
| Sudhakar_ | agent monitor detects that this DHCP agent went down and trigger rescheduling the network's DHCP on to the other agent.. | 15:22 |
| ajo | A few weeks ago, I was proposing that daemon agents could provide status via status file -> init.d "status", but it could be complementary. | 15:22 |
| ajo | aha, it makes sense Sudhakar_ | 15:23 |
| Sudhakar_ | currently we have agent_down_time configuration which will help us decide on rescheduling... | 15:23 |
| carl_baldwin | Sudhakar_: Do you have any document describing this that we could review offline? | 15:23 |
| Sudhakar_ | we could have another parameter altogether to avoid mixing up.. | 15:23 |
| safchain | Sudhakar_, It seems there is something like that for LBaaS | 15:23 |
| ajo | yes, a document on those ideas would be interesting, | 15:23 |
| Sudhakar_ | we are refining the doc... will publish it for review soon.. | 15:23 |
| carl_baldwin | Actually, I made a mistake above. I said HA DHCP where I should have said, more precisely, distributed DHCP. | 15:24 |
| carl_baldwin | Sudhakar_: Great. | 15:24 |
| ajo | aha carl_baldwin , the one based in openflow rules? | 15:24 |
| Sudhakar_ | Ok ..:) | 15:24 |
| Sudhakar_ | Distributed DHCP was another thought...but i don't have much idea on that yet... | 15:25 |
| carl_baldwin | ajo: open flow rules could play a part but that did not come up explicitly. | 15:25 |
| ajo | understood | 15:25 |
| carl_baldwin | #topic l3-agent-consolidation | 15:26 |
| *** openstack changes topic to "l3-agent-consolidation (Meeting topic: neutron_l3)" | 15:26 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 15:26 | |
| carl_baldwin | This work is up for review but the bp was pushed out to Icehouse. | 15:26 |
| carl_baldwin | yamahata: anything to add? | 15:26 |
| yamahata | carl_baldwin: nothing new this week. | 15:27 |
| carl_baldwin | #topic bgp-dynamic-routing | 15:27 |
| *** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)" | 15:27 | |
| carl_baldwin | #link https://blueprints.launchpad.net/neutron/+spec/bgp-dynamic-routing | 15:27 |
| carl_baldwin | #link https://blueprints.launchpad.net/neutron/+spec/neutron-bgp-mpls-vpn | 15:27 |
| carl_baldwin | nextone92: are you around? | 15:28 |
| *** sarob has joined #openstack-meeting-3 | 15:28 | |
| carl_baldwin | I spent some time reviewing the bgp-mpls bp this week and made some notes. | 15:28 |
| carl_baldwin | It looks like a few key people aren't around this week to discuss. So, I'll try again next week. | 15:29 |
| carl_baldwin | #topic DNS lookup of instances | 15:30 |
| *** openstack changes topic to "DNS lookup of instances (Meeting topic: neutron_l3)" | 15:30 | |
| *** markmcclain has quit IRC | 15:30 | |
| carl_baldwin | Really quick, I’m almost done writing a blueprint for this. Then, I need get it reviewed internally before I can post it. | 15:30 |
| carl_baldwin | I hope to have more to report on this next week. | 15:30 |
| ajo | sounds interesting, thanks carl_baldwin | 15:30 |
| carl_baldwin | #topic Agent Performance with Wrapper Overhead | 15:30 |
| *** openstack changes topic to "Agent Performance with Wrapper Overhead (Meeting topic: neutron_l3)" | 15:30 | |
| carl_baldwin | #link https://etherpad.openstack.org/p/neutron-agent-exec-performance | 15:31 |
| carl_baldwin | This has come up on the ML this week. I have worked on it some so I created this etherpad. | 15:31 |
| rossella_ | carl_baldwin: nice summary on the etherpad | 15:32 |
| ajo | yes, thanks carl_baldwin :) | 15:32 |
| *** nextone92 has joined #openstack-meeting-3 | 15:32 | |
| carl_baldwin | rossella_: ajo: thanks | 15:32 |
| carl_baldwin | So, there are a number of potential ways to tackle the problem. | 15:32 |
| carl_baldwin | I'm wondering what could be done for Icehouse. | 15:33 |
| nextone92 | carl_baldwin - sorry I'm so late to join the meeting | 15:33 |
| *** Swami has joined #openstack-meeting-3 | 15:34 | |
| Sudhakar_ | carl_baldwin, thanks for putting up the doc. looking forward on this.. | 15:34 |
| ajo | Yes, I had that thought too carl_baldwin | 15:34 |
| rossella_ | Icehouse is now | 15:34 |
| rossella_ | we can't do much | 15:34 |
| Swami | Carl: Sorry I am late today | 15:34 |
| safchain | yes, I will have a look to this etherpad | 15:34 |
| carl_baldwin | Swami: nextone92: Hi | 15:34 |
| Swami | Carl: hi | 15:34 |
| ajo | Yuriy's idea (priviledged agent) doesn't look bad from the point of view of keeping all in python. But looks like it requires more changes into neutron. Too bad to be at the end of the cycle. | 15:35 |
| carl_baldwin | rossella_: I fear you are right. There isn't much unless we can find bugs that could be fixed in short order. | 15:35 |
| YorikSar | o/ | 15:35 |
| YorikSar | I'm that Yuriy. | 15:35 |
| *** jcoufal has quit IRC | 15:35 | |
| ajo | Ho YorikSar ! :) | 15:35 |
| ajo | Hi :) | 15:35 |
| YorikSar | I don't think it'll become very intrusive | 15:35 |
| carl_baldwin | ajo: YorikSar: My thinking is similar. It may be a very good long term solution. | 15:35 |
| carl_baldwin | YorikSar: I noticed your additions to the ether pad only this morning so I have not had a chance to review them. | 15:36 |
| YorikSar | We basically need to replace execute() calls with smth like rootwrap.client.execute() | 15:36 |
| ajo | I'm just worried with, for example, memory consumtion. We must keep all instances tied tight... to avoid leaking "agents" | 15:36 |
| YorikSar | ajo: They can kill themselves by timeout. | 15:37 |
| YorikSar | Then we won;t leak them. | 15:37 |
| ajo | And at client exit | 15:37 |
| ajo | May be, for ones running inside a netns: kill by timeout | 15:37 |
| YorikSar | ajo: Yeah. Which can end up basically the same. | 15:37 |
| ajo | the system-wide ones: kill by client exit + longer timoeut | 15:38 |
| ajo | carl_baldwin, do you think this approach could have the potential to be backported to Icehouse if it's tackled from now to the start of Juno? | 15:38 |
| *** lblanchard has quit IRC | 15:39 | |
| YorikSar | ajo: I'm thinking about trying to push this to oslo.rootwrap, actually. So backporting will be minimal, but it'll be another feature. | 15:40 |
| carl_baldwin | ajo: I don't think it adds features and it wouldn't change the database. So, I think there might be hope for it. | 15:40 |
| ajo | carl_baldwin, do we have a bug filed for this? | 15:40 |
| carl_baldwin | ... not a new feature from the user perspective. More of an implementation detail. | 15:40 |
| ajo | Yes, we're killing a cpu-eating-bug.... | 15:41 |
| YorikSar | carl_baldwin: Oh, yes. Agree. | 15:41 |
| carl_baldwin | It is a significant implementation detail though. | 15:41 |
| ajo | yes, I agree carl_baldwin | 15:41 |
| carl_baldwin | I don't think there is one overarching bug for this. | 15:42 |
| carl_baldwin | I have filed detailed bugs for some of the individual problems that I've found and fixed. | 15:42 |
| ajo | carl_baldwin, I can fill a bug with the details | 15:42 |
| carl_baldwin | ajo: Great. | 15:42 |
| ajo | (basically, the start of the latest mail thread) | 15:42 |
| ajo | #action fill bug about the rootwrap overhead problem. | 15:43 |
| ajo | is it done this way? | 15:43 |
| ajo | sorry, I'm almost new to meetings | 15:43 |
| haleyb | carl_baldwin: perhaps for icehouse all we can do is continue chipping away at unnecessary calls, and maybe get your priority change in? my $.02 | 15:44 |
| carl_baldwin | ajo: I think you need to mention your handle after action. But, yes. Everyone should feel free to add their own action items. | 15:44 |
| ajo | #action ajo fill bug about the rootwrap overhead problem. | 15:44 |
| *** david-lyle has joined #openstack-meeting-3 | 15:44 | |
| Swami | is that even possible for icehouse, at this time | 15:44 |
| rossella_ | haleyb: +1 | 15:44 |
| YorikSar | I'm going to work on POC for that agent soon, btw. | 15:44 |
| carl_baldwin | haleyb: Yes. I'm hoping to wrap up that priority change this week as a bug fix. | 15:45 |
| YorikSar | It's going to be interesting stuff to code :) | 15:45 |
| *** jpomero has joined #openstack-meeting-3 | 15:45 | |
| ajo | may be, for icehouse, I could try to spend some time in reducing the python subset in the current rootwrap, and get a C++ translation we can use. | 15:45 |
| carl_baldwin | Swami: I imagine there is little that can be done for Icehouse. Only bug fixes and I imagine that significant changes will not be accepted. | 15:45 |
| Swami | Yes that's my thought as well. | 15:46 |
| ajo | (automated one), but I'm unsure about the auditability of such solution. that might require some investigation. | 15:46 |
| carl_baldwin | ajo: It might be worth a try. That is something I'm not very familiar with though. | 15:46 |
| ajo | carl_baldwin: may be it's not much work <1 week, I could try to allocate the time for that with my manager... | 15:47 |
| ajo | I have found speed improvements of >x50 with the C++ translation, but the python subset is rather reduced. | 15:47 |
| carl_baldwin | ajo: Remember that we need to reduce start up time and not necessarily execution speed. | 15:48 |
| ajo | Yes, that's greatly reduced, let me look for some numbers I had. | 15:48 |
| *** eghobo has joined #openstack-meeting-3 | 15:48 | |
| carl_baldwin | ajo: sounds good. | 15:48 |
| carl_baldwin | There are updates to "sudo" and "ip" that can help at scale. These fall outside the scope of the Openstack release. | 15:48 |
| YorikSar | I wouldn't actually call switching to some subset of Python staying with Python. it'd still be some other language. | 15:49 |
| carl_baldwin | Is there any documentation existing in openstack about tuning at the OS level? | 15:49 |
| YorikSar | But it might worth it to compare our approaches and probably come up with some benchmark. | 15:49 |
| ajo | 1 sec. getting the numbers | 15:49 |
| carl_baldwin | If so, I thought we could add some information from the ether pad to that document. If not, it could be created. | 15:50 |
| mwagner_lap | carl_baldwin, not sure if there any docs on tuning at the OS level | 15:50 |
| ajo | http://fpaste.org/85068/25818139/ | 15:50 |
| mwagner_lap | assuming you are talking about the neutron server itself | 15:50 |
| ajo | [majopela@redcylon ~]$ time python test.py | 15:50 |
| *** cjellick_ has joined #openstack-meeting-3 | 15:50 | |
| ajo | real0m0.094s | 15:50 |
| ajo | [majopela@redcylon ~]$ time ./test | 15:50 |
| ajo | real0m0.004s | 15:50 |
| carl_baldwin | #action carl_baldwin will look for OS level tuning documentation and either augment it or create it. | 15:51 |
| ajo | carl_baldwin, there is an "iproute" patch, and a "sudo" patch, could you add them to the etherpad? | 15:52 |
| carl_baldwin | FWIW, my efforts at consolidating system calls to run multiple calls under a single wrapper invocation have shown that it is extremely challenging with little reward. | 15:52 |
| carl_baldwin | ajo: I believe those patches are referenced from the etherpad. | 15:53 |
| ajo | ah, thanks carl_baldwin | 15:53 |
| ajo | you're right , [3] and [2] | 15:53 |
| carl_baldwin | ajo: Some of them are rather indirect. I'll fix that. | 15:53 |
| carl_baldwin | #action carl_baldwin will fix references to patches to make them easier to spot and follow. | 15:54 |
| *** cjellick has quit IRC | 15:54 | |
| ajo | carl_baldwin, doing it as we talk, :) | 15:54 |
| carl_baldwin | ajo: cool, thanks. | 15:54 |
| carl_baldwin | So, ajo and YorikSar We'll be looking forward to seeing what you come up with. Keep the ether pad up and we'll collaborate there. | 15:56 |
| *** alexpilotti has joined #openstack-meeting-3 | 15:56 | |
| YorikSar | ok | 15:56 |
| carl_baldwin | Anything else? | 15:56 |
| carl_baldwin | #topic General Discussion | 15:57 |
| *** openstack changes topic to "General Discussion (Meeting topic: neutron_l3)" | 15:57 | |
| *** xianghui has quit IRC | 15:57 | |
| ajo | carl_baldwin, | 15:57 |
| ajo | I've seen neighbour table overflow messages from kernel, | 15:58 |
| ajo | when I start lots of networks, | 15:58 |
| ajo | have you seen this before? | 15:58 |
| ajo | lots (>100) | 15:58 |
| safchain | ajo, which plugin/agent ? | 15:58 |
| haleyb | ipv6 error? i think we've seen that too | 15:58 |
| ajo | normal neutron-l3-agent | 15:58 |
| ajo | with ipv4 | 15:58 |
| *** cjellick has joined #openstack-meeting-3 | 15:59 | |
| ajo | and openvswitch | 15:59 |
| carl_baldwin | I believe that we have seen it but I did not work on that issue directly. So, I cannot offer the solution. | 15:59 |
| *** johnthetubaguy has joined #openstack-meeting-3 | 15:59 | |
| ajo | It's in my todo list | 15:59 |
| ajo | I tried to tune the ARP garbage collection settings on the kernel | 15:59 |
| *** cjellick_ has quit IRC | 16:00 | |
| ajo | but, I'm not sure if it's namespace related | 16:00 |
| *** johnthetubaguy1 has quit IRC | 16:00 | |
| *** johnthetubaguy has quit IRC | 16:00 | |
| haleyb | ajo: found my notes - yes, found and solution is to increase size - gc_thresh* | 16:00 |
| carl_baldwin | I've got a hard stop at the hour. Feel free to continue discussion in the neutron room or here if no one has this room. | 16:00 |
| carl_baldwin | Thank you all who came and participated. | 16:00 |
| safchain | thx carl_baldwin | 16:01 |
| haleyb | ajo: neighbor table is shared between all namespaces | 16:01 |
| carl_baldwin | Please review the meetings logs and get back to me about potential time change for this meeting. | 16:01 |
| Sudhakar_ | thanks carl | 16:01 |
| carl_baldwin | Bye! | 16:01 |
| carl_baldwin | #endmeeting | 16:01 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:01 | |
| openstack | Meeting ended Thu Mar 13 16:01:23 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-03-13-15.00.html | 16:01 |
| nextone92 | thanks! | 16:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-03-13-15.00.txt | 16:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-03-13-15.00.log.html | 16:01 |
| Swami | thanks carl, bye | 16:01 |
| *** Sudhakar_ has left #openstack-meeting-3 | 16:01 | |
| *** nextone92 has left #openstack-meeting-3 | 16:01 | |
| ajo | aha haleyb yes, I've been working with the same, but still getting ARP errors, | 16:01 |
| ajo | I will investigate in more detail :) | 16:02 |
| ajo | Thanks carl_baldwin | 16:02 |
| ajo | bye everybody :) | 16:02 |
| haleyb | double values, then keep going until they go away :) | 16:02 |
| ajo | hehe :) | 16:02 |
| rossella_ | bye | 16:02 |
| ajo | thanks haleyb , I'll try it | 16:02 |
| *** johnthetubaguy has joined #openstack-meeting-3 | 16:02 | |
| *** jcoufal-mobile has joined #openstack-meeting-3 | 16:03 | |
| *** Swami has left #openstack-meeting-3 | 16:05 | |
| *** rossella_ has left #openstack-meeting-3 | 16:06 | |
| *** cnesa has joined #openstack-meeting-3 | 16:07 | |
| *** markmcclain has joined #openstack-meeting-3 | 16:08 | |
| *** cjellick has quit IRC | 16:09 | |
| *** YorikSar has left #openstack-meeting-3 | 16:10 | |
| *** pcm_ has left #openstack-meeting-3 | 16:10 | |
| *** cjellick has joined #openstack-meeting-3 | 16:13 | |
| *** cjellick has quit IRC | 16:14 | |
| *** cjellick has joined #openstack-meeting-3 | 16:14 | |
| *** johnthetubaguy has quit IRC | 16:16 | |
| *** johnthetubaguy has joined #openstack-meeting-3 | 16:16 | |
| *** jcoufal-mobile has quit IRC | 16:17 | |
| *** jcoufal-mobile has joined #openstack-meeting-3 | 16:18 | |
| *** devlaps has joined #openstack-meeting-3 | 16:19 | |
| *** cjellick_ has joined #openstack-meeting-3 | 16:22 | |
| *** sarob has quit IRC | 16:22 | |
| *** sarob has joined #openstack-meeting-3 | 16:23 | |
| *** cjellick has quit IRC | 16:23 | |
| *** sarob has quit IRC | 16:27 | |
| *** jcoufal-mobile_ has joined #openstack-meeting-3 | 16:28 | |
| *** jcoufal-mobile has quit IRC | 16:28 | |
| *** jcoufal-mobile_ has quit IRC | 16:28 | |
| *** jcoufal-mobile has joined #openstack-meeting-3 | 16:29 | |
| *** cjellick_ has quit IRC | 16:30 | |
| *** cjellick has joined #openstack-meeting-3 | 16:30 | |
| *** jthopkin has left #openstack-meeting-3 | 16:31 | |
| *** jcoufal-mobile_ has joined #openstack-meeting-3 | 16:31 | |
| *** jcoufal-mobile_ has quit IRC | 16:33 | |
| *** jcoufal-mobile has quit IRC | 16:33 | |
| *** sarob has joined #openstack-meeting-3 | 16:37 | |
| *** sarob has quit IRC | 16:42 | |
| *** lblanchard has joined #openstack-meeting-3 | 16:48 | |
| *** sarob has joined #openstack-meeting-3 | 16:53 | |
| *** jtomasek has quit IRC | 17:00 | |
| *** lpetrut has joined #openstack-meeting-3 | 17:01 | |
| *** beyounn has joined #openstack-meeting-3 | 17:02 | |
| *** lpetrut_ has joined #openstack-meeting-3 | 17:03 | |
| *** lpetrut has quit IRC | 17:05 | |
| *** freesoftware has joined #openstack-meeting-3 | 17:07 | |
| *** coasterz has joined #openstack-meeting-3 | 17:07 | |
| *** nacim has quit IRC | 17:14 | |
| *** kathmandude has joined #openstack-meeting-3 | 17:18 | |
| *** kathmandude has quit IRC | 17:23 | |
| *** sarob has quit IRC | 17:25 | |
| *** SridarK has joined #openstack-meeting-3 | 17:34 | |
| *** GlenTheN00b has joined #openstack-meeting-3 | 17:42 | |
| *** freesoftware has quit IRC | 17:42 | |
| *** MaxV has quit IRC | 17:42 | |
| *** kathmandude has joined #openstack-meeting-3 | 17:43 | |
| *** lpetrut_ has quit IRC | 17:43 | |
| *** kathmandude has quit IRC | 17:45 | |
| *** kevinbenton has joined #openstack-meeting-3 | 17:46 | |
| *** sarob has joined #openstack-meeting-3 | 17:48 | |
| *** jpomero has quit IRC | 17:56 | |
| *** hemanthravi has joined #openstack-meeting-3 | 17:57 | |
| *** s3wong has joined #openstack-meeting-3 | 18:00 | |
| SumitNaiksatam | Hi Neutron Folks! :-) | 18:00 |
| s3wong | Hello SumitNaiksatam | 18:00 |
| hemanthravi | hi sumit | 18:00 |
| banix | Hi there | 18:00 |
| SumitNaiksatam | s3wong: hemanthravi banix: hi | 18:01 |
| beyounn | hi | 18:01 |
| banix | hi s3wong | 18:01 |
| SridarK | Hi | 18:01 |
| s3wong | banix: hi | 18:01 |
| *** pcm_ has joined #openstack-meeting-3 | 18:01 | |
| banix | hi sumit | 18:01 |
| *** jpomero has joined #openstack-meeting-3 | 18:01 | |
| *** mandeep has joined #openstack-meeting-3 | 18:02 | |
| *** prasadv has joined #openstack-meeting-3 | 18:02 | |
| *** SridharRamaswamy has joined #openstack-meeting-3 | 18:02 | |
| SumitNaiksatam | lets wait a min for eugene | 18:02 |
| pcm_ | hi | 18:02 |
| mandeep | SumitNaiksatam: hi | 18:02 |
| SumitNaiksatam | pcm_: hi, thanks for joining | 18:02 |
| SumitNaiksatam | mandeep: hi | 18:02 |
| *** enikanorov_ has joined #openstack-meeting-3 | 18:02 | |
| pcm_ | SumitNaiksatam: glad to be here | 18:02 |
| s3wong | very late for Eugene now | 18:02 |
| prasadv | sumitNaiksatam:hi | 18:02 |
| SumitNaiksatam | enikanorov_: hi | 18:02 |
| enikanorov_ | hi folks | 18:02 |
| SumitNaiksatam | lets get started | 18:02 |
| s3wong | but he is here :-) | 18:02 |
| cgoncalves | hi | 18:03 |
| SumitNaiksatam | #startmeeting Networking Advanced Services | 18:03 |
| openstack | Meeting started Thu Mar 13 18:03:10 2014 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:03 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:03 |
| *** openstack changes topic to " (Meeting topic: Networking Advanced Services)" | 18:03 | |
| openstack | The meeting name has been set to 'networking_advanced_services' | 18:03 |
| *** OSM has joined #openstack-meeting-3 | 18:03 | |
| SumitNaiksatam | I was pinged by a lot of folks during the past few days about the status of the general services' framework | 18:03 |
| SumitNaiksatam | and what went into Icehouse, and what remains to be done | 18:04 |
| *** obondarev has joined #openstack-meeting-3 | 18:04 | |
| SumitNaiksatam | hence I though it would be good for the various services' team to converge here | 18:04 |
| SumitNaiksatam | we used to have this meeting before but we suspended it to support more pressing issues facing Neutron | 18:04 |
| *** OSM is now known as songole | 18:04 | |
| SumitNaiksatam | unfortunately we did not get much into Icehouse in terms of the services' framework | 18:05 |
| *** GlenTheN00b has quit IRC | 18:05 | |
| SumitNaiksatam | moreover we are also reconsidering some of the existing abstractions - namely service-types | 18:05 |
| SumitNaiksatam | lets get started with that | 18:05 |
| SumitNaiksatam | #topic Flavors Framework | 18:05 |
| *** openstack changes topic to "Flavors Framework (Meeting topic: Networking Advanced Services)" | 18:05 | |
| SumitNaiksatam | #link https://wiki.openstack.org/wiki/Neutron/FlavorFramework | 18:05 |
| *** thinrichs has joined #openstack-meeting-3 | 18:06 | |
| SumitNaiksatam | enikanorov_: put out the wiki and started a thread on the mailing list as well | 18:06 |
| s3wong | SumitNaiksatam: quickly skim through it this morning, it seems very abstract. It only adds a flavor type on top of existing service type and provider driver | 18:06 |
| SumitNaiksatam | s3wong: okay | 18:06 |
| enikanorov_ | s3wong: correct | 18:06 |
| SumitNaiksatam | so i see the following points that we probably need to consider (and then i will yield to enikanorov_) | 18:07 |
| enikanorov_ | the idea is to choose provider based on service capabilities requirested by the user | 18:07 |
| SumitNaiksatam | 1. the framework has to have generic application to Neutron services | 18:07 |
| SumitNaiksatam | 2. it should provide for representation of different “flavors” of the same service | 18:07 |
| SumitNaiksatam | 3. in terms of service matching we need to decide desire versus exact match semantics | 18:08 |
| SumitNaiksatam | 4. and the name :-) ( we can punt this to the mailer) | 18:08 |
| SumitNaiksatam | enikanorov_: is that reasonable characterization of the discussion till date? | 18:08 |
| enikanorov_ | yes, pretty much! | 18:08 |
| pcm_ | enikanorov_: would like to hear more about how the flavor translate to a specific driver instance... fuzzy to me | 18:08 |
| hemanthravi | does it allow for def of a new type of service along with associated params? | 18:09 |
| pcm_ | maybe some concrete examples would help me (I'm dense :) | 18:09 |
| *** sarob__ has joined #openstack-meeting-3 | 18:09 | |
| enikanorov_ | pcm: the flavor represends requirements (capabilities) that user wants from the service. some drivers support some caps, others don't | 18:09 |
| *** kathmandude has joined #openstack-meeting-3 | 18:09 | |
| enikanorov_ | how capabilities are represented is yet to be defined | 18:09 |
| enikanorov_ | initially I proposed quite free form of definition like {'parameter': allowed_values (or range)} | 18:10 |
| pcm_ | enikanorov_: so, say for VPN, where may have multiple drivers that can all meet the need, how does one select a specific driver? | 18:10 |
| enikanorov_ | as an alternative, flavor could be a set of tags | 18:10 |
| *** sarob has quit IRC | 18:10 | |
| enikanorov_ | pcm_: via scheduling, it can be random, it can consider available appliances | 18:10 |
| enikanorov_ | that is yet to be decided | 18:11 |
| enikanorov_ | the proposal is that scheduler asks drivers for resources that match the flavor | 18:11 |
| s3wong | pcm_ : good point. Since the intention is to hide vendor name, that selection is very unpredictable | 18:11 |
| enikanorov_ | and then choses the backedn depending on scheduling algorithm | 18:11 |
| SumitNaiksatam | enikanorov_: on the representation of capabilities, the base set of attributes can be abstract with the possibility to extend to specifics | 18:12 |
| SridarK | enikanorov_: There could be a use case where one might want to pick a specific vendor implementation as perhaps this has been validated earlier | 18:12 |
| SridarK | should this be considered ? | 18:12 |
| SumitNaiksatam | SridarK: my point ^^^ | 18:12 |
| enikanorov_ | SumitNaiksatam: to me it should be a part of Admin API, where admin can create flavors in relatively free form | 18:12 |
| SumitNaiksatam | incorporate base set of abstract attributes | 18:13 |
| SumitNaiksatam | enikanorov_: yes | 18:13 |
| enikanorov_ | SumitNaiksatam: but also we need to be bw compatible, so I'm thinking about some default flavors, that drivers can export | 18:13 |
| SumitNaiksatam | and then allow for free form attributes as well, in case the admin wants to expose | 18:13 |
| s3wong | enikanorov_: admin can then specify vendor name into the available flavors then? | 18:13 |
| SumitNaiksatam | enikanorov_: yes, defaults can make it backward compatible | 18:13 |
| enikanorov_ | SridarK: I think in this case that could be solved by the flavor that will be provider-specific | 18:13 |
| SridarK | ok would we get into a proliferation of flavors | 18:14 |
| enikanorov_ | s3wong: yes, like that, add 'provider' parameter to a flavor and it will map to a specific provider, for instance | 18:14 |
| *** lenrow_ has joined #openstack-meeting-3 | 18:14 | |
| banix | s3wong: that sounds like a reasonable option | 18:14 |
| pcm_ | +1 ^^ | 18:14 |
| SridarK | s3wong: +1 | 18:14 |
| enikanorov_ | flavor workflow should definitely allow what is allowed with provider workflow | 18:14 |
| s3wong | yes, so now flavor definition is an provider API, and selection API is tenant API? | 18:15 |
| SumitNaiksatam | enikanorov_: to pcm_'s question we can also don't have to have exact match semantics | 18:15 |
| enikanorov_ | yes, selection is tenant API | 18:15 |
| SumitNaiksatam | s3wong: i believe so | 18:15 |
| enikanorov_ | SumitNaiksatam: of course | 18:15 |
| SumitNaiksatam | enikanorov_: ok good we are on the same page | 18:16 |
| banix | Similar to nova flavors I suppose | 18:16 |
| SumitNaiksatam | folks, lets have some structure to the conversation here | 18:16 |
| SumitNaiksatam | i think we are talking over each other | 18:16 |
| SumitNaiksatam | this is a long topic of discussion, so we are not going to resolve things here | 18:16 |
| SumitNaiksatam | we want to get the discussion started and get people thinking so that they can provide feedback | 18:16 |
| SumitNaiksatam | ok so who's next? | 18:17 |
| * pcm_ takes one step back :) | 18:17 | |
| *** Ly100 has joined #openstack-meeting-3 | 18:17 | |
| SumitNaiksatam | pcm_: i was going to say you asked the first question :-) | 18:17 |
| *** MaxV has joined #openstack-meeting-3 | 18:17 | |
| SumitNaiksatam | pcm_: so far good? | 18:17 |
| pcm_ | yes | 18:18 |
| enikanorov_ | so the question I have | 18:18 |
| SumitNaiksatam | ok hemanthravi next | 18:18 |
| enikanorov_ | is about patches that integrate fwaas/vpn/l3 with provider framework | 18:18 |
| SumitNaiksatam | enikanorov_: sorry go ahead | 18:18 |
| SumitNaiksatam | enikanorov_: i don't think there is a plan to integrate those | 18:18 |
| hemanthravi | was asking if flavors allows for a new type of service to be defined | 18:18 |
| enikanorov_ | i think that those patches make sense even if we agree on flavors | 18:18 |
| enikanorov_ | but with the exception | 18:18 |
| SumitNaiksatam | enikanorov_: the service type framework patches are on hold | 18:19 |
| enikanorov_ | that provider should be exposet into the tenant API | 18:19 |
| enikanorov_ | but rather be a read-only attribute | 18:19 |
| SumitNaiksatam | enikanorov_: ok, makes sense to me | 18:19 |
| enikanorov_ | because it seems that we're still going to have mapping between resource and the driver | 18:19 |
| s3wong | enikanorov_: sounds good | 18:19 |
| enikanorov_ | even if we have flavors | 18:19 |
| pcm_ | enikanorov_: So set provider via flavor attriobute and allow showing through provider framework? | 18:20 |
| SumitNaiksatam | enikanorov_: i think if we can explain how the new abstraction (if we call it flavors), incorporates the provider, that will be helpful | 18:20 |
| mandeep | enikanorov_: SumitNaiksatam: There are similar needs in the group policy framework. And they too are creating artifacts for publishing and consuming services and having best match semantics. At appropriate time, should consider that as an alternative as well | 18:20 |
| enikanorov_ | flavor is a scheduling hint where provider is dispatching hint | 18:20 |
| SumitNaiksatam | mandeep: sure | 18:20 |
| SridarK | enikanorov_: could u pls clarify on the read only for tenant - meaning tenant cannot set a provider ? | 18:20 |
| enikanorov_ | SridarK: yes, tenant can't set the provider - that's an idea of flavor framework | 18:20 |
| SridarK | that is fine thanks enikanorov_: | 18:21 |
| enikanorov_ | but we still need to bind resource to a provider, but not manually | 18:21 |
| s3wong | SridaK: one would imagine tenant can select from available options, but not creating one | 18:21 |
| SridarK | s3wong: Yes agreed | 18:21 |
| banix | SumitNaiksatam: Can you elaborate why service type patches are on hold? just not enough time for review? | 18:21 |
| pcm_ | banix: no, pending flavor discussion | 18:22 |
| SumitNaiksatam | banix: ostensibly because we are rethinking the service type framework | 18:22 |
| SumitNaiksatam | enikanorov_: hemanthravi's question was - "was asking if flavors allows for a new type of service to be defined" | 18:22 |
| SumitNaiksatam | hemanthravi: i believe the answer is yes | 18:23 |
| banix | and that is to generalize the framework, provide features such as not exact matches, etc | 18:23 |
| enikanorov_ | not sure i get the question :) | 18:23 |
| mandeep | enikanorov_: At least in the policy framework discussion, it allows for both specific provider, or for it to be satisfied by "best match" | 18:23 |
| hemanthravi | for eg a service other than FW, VPN | 18:23 |
| enikanorov_ | mainly because 'type of service' is a broad term | 18:23 |
| SumitNaiksatam | enikanorov_: so that question is applicable to service chains as well | 18:23 |
| SumitNaiksatam | enikanorov_: what if we want to expose a service chaing via the flavors framework | 18:23 |
| SumitNaiksatam | enikanorov_: this was the earlier plan with STF | 18:24 |
| enikanorov_ | SumitNaiksatam: i think that's where tag representation of capabilities can help | 18:24 |
| SumitNaiksatam | *chain | 18:24 |
| s3wong | SumitNaiksatam: hemanthravi: the available service type in a flavor needs to be submitted via bp, I suppose. Instead of relying on flavor framework to allow everyone to freely add service type | 18:24 |
| mandeep | SumitNaiksatam: This _should_ apply to service chains as well. A service chain is yet another service | 18:24 |
| enikanorov_ | you specify flavor={'type': 'chain_vpn_lbaas'} - something like that | 18:24 |
| SumitNaiksatam | mandeep: thats what i would think | 18:24 |
| enikanorov_ | (primitive example) | 18:24 |
| banix | s3wong: that won't work that nicely for service chains | 18:24 |
| s3wong | banix: true, since those are dynamically created by tenants | 18:25 |
| SumitNaiksatam | enikanorov_: yeah something like that | 18:25 |
| enikanorov_ | also, i'm not sure about ' freely add service type' | 18:25 |
| enikanorov_ | in my understanding 'service type' is something that has code implementation | 18:25 |
| banix | but I see discussion on limiting the capability for having arbitrarily constructed chains | 18:25 |
| enikanorov_ | like now we have service plugins | 18:25 |
| SridarK | SumitNaiksatam: we will need to have a "set" of service drivers for each element in the chain | 18:25 |
| enikanorov_ | so it's not something that admin or tenant defines | 18:25 |
| *** johnthetubaguy has quit IRC | 18:26 | |
| SumitNaiksatam | banix s3wong enikanorov_ so i think the point here is that this deployment specific | 18:26 |
| s3wong | enikanorov_: I guess the question is - should a service chain, defined by tenant, be a "service type"? | 18:26 |
| enikanorov_ | s3wong: i think you're talking about chain implementation | 18:26 |
| SumitNaiksatam | s3wong: the service chain is not necessarily a dynamic construct | 18:26 |
| enikanorov_ | i think tenant can't specify chain template | 18:27 |
| prasadv | enikanorov_: since the framework is matching, it can match the service type to the driver by querying isnt it? | 18:27 |
| *** johnthetubaguy has joined #openstack-meeting-3 | 18:27 | |
| banix | enikanorov: and having a service type of type chain does not make sense? Just wondering if that could be an option | 18:27 |
| SumitNaiksatam | s3wong: the particular deployment/provider has to support the service chain, and it will expose only those that it supports | 18:27 |
| *** johnthetubaguy has quit IRC | 18:27 | |
| enikanorov_ | banix: 'chain' is too abstract. FW_lbaas_chain makes sense | 18:27 |
| enikanorov_ | or other concrete chains | 18:28 |
| SumitNaiksatam | enikanorov_: yes | 18:28 |
| enikanorov_ | but those are static | 18:28 |
| enikanorov_ | that's how i see it | 18:28 |
| SumitNaiksatam | enikanorov_: that has been our approach all along | 18:28 |
| enikanorov_ | static - means we, developers, define them | 18:28 |
| s3wong | SumitNaiksatam: in that case, the provider for such chain that provider can support has multiple drivers? | 18:28 |
| enikanorov_ | SumitNaiksatam: yep | 18:28 |
| SumitNaiksatam | s3wong: could have multiple drivers | 18:28 |
| SumitNaiksatam | s3wong: they will probably be different chains | 18:29 |
| SumitNaiksatam | s3wong: i can see that you are probably seeing an issue with combinatorial explosion | 18:29 |
| SumitNaiksatam | s3wong: however in reality that might not be the case | 18:29 |
| s3wong | SumitNaiksatam: absolutely | 18:29 |
| banix | I may be thinking too broadly for an implementation, but that sounds like a big limitation. But I have seen earlier discussion on this and see the thoughts on this issue. | 18:29 |
| *** shamkut has joined #openstack-meeting-3 | 18:29 | |
| banix | SumitNaiksatam: yes | 18:30 |
| pcm_ | so the chain is specific to the provider right? | 18:30 |
| SumitNaiksatam | pcm_: yes | 18:30 |
| SumitNaiksatam | s3wong banix: so essentially you are expressing the need to chains created by users? | 18:30 |
| SumitNaiksatam | * need to create chains | 18:31 |
| s3wong | SumitNaiksatam: it is extremely limiting is a tenant cannot choose to chain together available services provided by provider | 18:31 |
| s3wong | s/is/if | 18:31 |
| SumitNaiksatam | s3wong: ok | 18:31 |
| SumitNaiksatam | so we are half way into the meeting | 18:31 |
| pcm_ | Would it be the case that the chain would always relate to one provider, or could we cross providers (does that even make sense)? | 18:31 |
| SumitNaiksatam | i think this is a nice segue into the next part of the agenda | 18:31 |
| banix | SumitNaiksatam: Yes, and the ability to compose chains from other services that are defined by the provider | 18:31 |
| *** lpetrut has joined #openstack-meeting-3 | 18:32 | |
| SumitNaiksatam | #topic Service insertion/chaining | 18:32 |
| *** openstack changes topic to "Service insertion/chaining (Meeting topic: Networking Advanced Services)" | 18:32 | |
| s3wong | perfect point to move into the next topic :-) | 18:32 |
| banix | to wrap up the previous section, is it fait o say flavors are a generalized form of service types that we are agreeing on working towsrds? | 18:33 |
| SumitNaiksatam | btw, we are not done with the flavors discussion, but we have started to bleed into the complementary discussion (so thought we could make progress on the agenda :-)) | 18:33 |
| SumitNaiksatam | enikanorov_: please stay with us :-) | 18:33 |
| *** ftcjeff has joined #openstack-meeting-3 | 18:33 | |
| SumitNaiksatam | ok so coming back chaining | 18:33 |
| enikanorov_ | i will, although in read-only mode mostly :) | 18:33 |
| SridarK | SumitNaiksatam: in terms of who defines the chain and who defines the provides in the simpler flavor case - seems we are saying diff things | 18:33 |
| SumitNaiksatam | first an update | 18:33 |
| cgoncalves | SumitNaiksatam: I also share banix's opinion on allowing users to define chains | 18:33 |
| SridarK | *provider | 18:33 |
| *** shamkut has quit IRC | 18:33 | |
| SumitNaiksatam | #link https://blueprints.launchpad.net/neutron/+spec/neutron-services-insertion-chaining-steering | 18:34 |
| s3wong | go ahead SumitNaiksatam | 18:34 |
| SumitNaiksatam | again due to the resource/time crunch we were left to target only a very tiny part of the above blueprint | 18:34 |
| SumitNaiksatam | #link #link https://review.openstack.org/#/c/62599 | 18:35 |
| SumitNaiksatam | unfortunately, even that did not make it in! | 18:35 |
| s3wong | SumitNaiksatam: this is already out for Icehouse, correct? | 18:35 |
| *** sarob__ has quit IRC | 18:35 | |
| SumitNaiksatam | not for lack of effort | 18:35 |
| SumitNaiksatam | s3wong: nope, it was not granted FFE | 18:36 |
| SumitNaiksatam | anyway | 18:36 |
| SumitNaiksatam | so although it was a FWaaS related patch, the idea was to introduce the notion of a service context | 18:36 |
| SumitNaiksatam | service context will aid in service insertion | 18:36 |
| SumitNaiksatam | the service context can be one or a combination of a number of references to other neutron objects | 18:37 |
| SumitNaiksatam | very simple and basic | 18:37 |
| cgoncalves | SumitNaiksatam: would it be possible in the defined blueprint to allow vm instances to be part of a chain? use case: DPI is not supported in openstack as a service; one could create a vm instance with a DPI instance (e.g. ntop) and bind it to a chain FWaaS->VM_DPI->LbaaS | 18:38 |
| SumitNaiksatam | the hope was that all services would implement the service context, and we could subsequently use it to build service chains | 18:38 |
| SumitNaiksatam | cgoncalves: yes | 18:38 |
| SumitNaiksatam | cgoncalves: its agnostic to the service implementation | 18:38 |
| cgoncalves | SumitNaiksatam: awesome. thanks! | 18:39 |
| s3wong | SumitNaiksatam: what is the definition of service context? | 18:39 |
| SumitNaiksatam | s3wong: its in the blueprint ;-) | 18:39 |
| SumitNaiksatam | s3wong: service_context can be used by the user to convey the intent to the backend as to where to anchor the particular service instance | 18:40 |
| banix | Mainly a reference to where a service can be inserted | 18:40 |
| SumitNaiksatam | banix: yeah, much more concise :-) | 18:41 |
| s3wong | banix: I see. thanks. I also just found it in the document :-) | 18:41 |
| SumitNaiksatam | s3wong: make sense? | 18:41 |
| s3wong | SumitNaiksatam: yes | 18:41 |
| SumitNaiksatam | okay | 18:41 |
| SumitNaiksatam | so moving on | 18:41 |
| banix | That seems very logical to me but I think there were concerns wrt backward compability | 18:42 |
| *** safchain has quit IRC | 18:42 | |
| banix | which as far as I can see are not there | 18:42 |
| SumitNaiksatam | banix: actually those were not substantiated | 18:42 |
| SumitNaiksatam | banix: yeah | 18:42 |
| kathmandude | can there be multiple service instances with different contexts? | 18:42 |
| s3wong | SumitNaiksatam: is ports Neutron ports or L4 port number? | 18:42 |
| SumitNaiksatam | banix: that was probably lack of understanding, default semantics can make it backward compatible | 18:42 |
| banix | yeah | 18:42 |
| SumitNaiksatam | s3wong: all neutron constructs, so neutron port | 18:42 |
| SumitNaiksatam | kathmandude: yes | 18:43 |
| SumitNaiksatam | so perhaps these are too many topics for a short meeting | 18:44 |
| banix | So service insertion context allows the insertion to be explicitly defined …. | 18:44 |
| SumitNaiksatam | banix: yes, but as supported by the backend provider | 18:44 |
| banix | that's right | 18:44 |
| SumitNaiksatam | banix: there will be validation, and not all contexts will be valid for a service or deployment | 18:44 |
| SumitNaiksatam | so what i was going to say is I think we have planted enough seeds in this discussion, both on the flavors front and the service insertion/chaining | 18:45 |
| banix | yes | 18:45 |
| SumitNaiksatam | we definitely need more discussion time | 18:45 |
| s3wong | SumitNaiksatam: so how to proceed beyond these seeds? :-) | 18:45 |
| SumitNaiksatam | i want to give time to pcm_ as well for the next topic | 18:45 |
| banix | and probably a timetable for ourselves so we can move things forward | 18:46 |
| SumitNaiksatam | s3wong: yes, lets summarize at the end of the meeting | 18:46 |
| SumitNaiksatam | banix: yes | 18:46 |
| SumitNaiksatam | #topic Vendor plugins for L3 services | 18:46 |
| *** openstack changes topic to "Vendor plugins for L3 services (Meeting topic: Networking Advanced Services)" | 18:46 | |
| SumitNaiksatam | #link http://lists.openstack.org/pipermail/openstack-dev/2014-February/026193.html | 18:46 |
| SumitNaiksatam | pcm_: all yours :-) | 18:46 |
| pcm_ | thanks | 18:46 |
| pcm_ | pretty much was thinking about these topics: | 18:47 |
| pcm_ | 1) how to handle/lcoate vendor config files | 18:47 |
| pcm_ | 2) way to do vendor validation (e.g. validate, commit, apply ~ to precommit/postcommit) | 18:47 |
| pcm_ | 3) How to tell client what vendor capabilities are | 18:48 |
| pcm_ | 4) How to report to plugin status, when there are problems | 18:48 |
| pcm_ | I've seen a bunch of these issues with VPN development and imagine other svcs do to. | 18:48 |
| pcm_ | Should we setup a separate IRC to discuss some ideas on this? | 18:49 |
| * pcm_ primarily wanted to get people thinking about it some | 18:49 | |
| SridarK | pcm_: we also need the flavor discussion to mature to understand what base we are building on | 18:50 |
| pcm_ | SridarK: agreed | 18:50 |
| s3wong | pcm_: agree with SridaK. Seems like a lot of these should be solved by flavors framework | 18:50 |
| *** cnesa has quit IRC | 18:51 | |
| pcm_ | s3wong: not sure how flavors will handle some of the issues like #2 | 18:51 |
| s3wong | pcm_: #1 and #3 should | 18:51 |
| SridarK | s3wong: pcm_'s intent is more to see how vendors adopt a framework | 18:51 |
| pcm_ | s3wong: agree | 18:52 |
| pcm_ | For #2, for example, the plugin for VPN will validate, commit and then call service driver to handle | 18:52 |
| pcm_ | that, unfortunately is too late for vendor to validate and prevent commit. | 18:52 |
| pcm_ | would be nice for a common framework that all services use to allow for this. | 18:53 |
| pcm_ | thinking hooks to pre/post commit actions, like done in ML2/L2 plugins | 18:53 |
| banix | similar to ML2 separation for mechanism drivers? | 18:53 |
| s3wong | pcm_ : plugin/driver has to be involved for #2, no escape for that one | 18:53 |
| mandeep | banix: precisely. It looks like the same problem | 18:54 |
| SridarK | pcm_: if SumitNaiksatam: enikanorov_: are okay too - could this be a part of the flavors discussion at least initially | 18:54 |
| * pcm_ need to read up on ML2 more :) | 18:54 | |
| SumitNaiksatam | SridarK: not sure i got that | 18:55 |
| pcm_ | SridarK: sure. There are likely parts that fit in nicely and some that maybe don't. | 18:55 |
| SumitNaiksatam | SridarK: but we can follow up | 18:55 |
| enikanorov_ | that's an interesting point | 18:55 |
| SumitNaiksatam | pcm_: sorry to cut you short, since only 5 mins, just want to plan for future meetings as well | 18:55 |
| pcm_ | sure np | 18:55 |
| enikanorov_ | basically right now the driver is able to put resource into ERROR state | 18:55 |
| SumitNaiksatam | pcm_: we will continue the discussion in this forum | 18:55 |
| enikanorov_ | that's all it can do | 18:55 |
| SridarK | SumitNaiksatam: since the flavors is also evolving - perhaps we need to get that model settled in first | 18:55 |
| *** jpomero has quit IRC | 18:55 | |
| SumitNaiksatam | SridarK: sure | 18:55 |
| SumitNaiksatam | #topic Summary and planning | 18:56 |
| *** openstack changes topic to "Summary and planning (Meeting topic: Networking Advanced Services)" | 18:56 | |
| s3wong | enikanorov_: seems like we need to extend flavor framework | 18:56 |
| enikanorov_ | s3wong: how do you see it? | 18:56 |
| SumitNaiksatam | so i think there is a lot of discussion needed on a different topics | 18:56 |
| SumitNaiksatam | unfortunately time is short and we have too many meetings | 18:56 |
| SumitNaiksatam | so how does everyone feel about having this is as a biweekly meeting | 18:57 |
| mandeep | And make it 2 hrs ... we need that time | 18:57 |
| pcm_ | SumitNaiksatam: sure, or weekly... | 18:57 |
| enikanorov_ | i'm fine with that | 18:57 |
| SridarK | SumitNaiksatam: From the chaos - with folks jumping over one other (in a good way) in the mtg - only reflects the the intense need to solve this problem :-) | 18:57 |
| mandeep | (just to get to bottom of some of these discussions) | 18:57 |
| enikanorov_ | i'm for weekly, but 1 hour long | 18:57 |
| banix | weekly seems what we need | 18:58 |
| pcm_ | enikanorov_: +1 and just limit topic | 18:58 |
| s3wong | SumitNaiksatam: would be nice to make it NOT immediately before the group-policy meeting | 18:58 |
| SumitNaiksatam | enikanorov_: man deep's suggestion to make to 2 hour but biweekely> | 18:58 |
| prasadv | s3wong: +1 | 18:58 |
| SumitNaiksatam | s3wong: sure | 18:58 |
| enikanorov_ | 2 hrs is exhausting | 18:58 |
| mandeep | OK | 18:58 |
| hemanthravi | +1 weekly, 1hr | 18:58 |
| SumitNaiksatam | if we keep it to only one topic, other topics will be delayed | 18:58 |
| SumitNaiksatam | alright, one hour weekly | 18:59 |
| *** lenrow has joined #openstack-meeting-3 | 18:59 | |
| SumitNaiksatam | we can alternate topics | 18:59 |
| pcm_ | es | 18:59 |
| pcm_ | yes | 18:59 |
| s3wong | move it back to wednesday, perhaps? | 18:59 |
| mandeep | That will work too | 18:59 |
| SridarK | +1 | 18:59 |
| SumitNaiksatam | there are other topics which we did not even touch | 18:59 |
| SumitNaiksatam | ok | 18:59 |
| SumitNaiksatam | many others | 18:59 |
| SumitNaiksatam | regarding day/time? | 18:59 |
| SumitNaiksatam | wednesday? | 18:59 |
| banix | Lets prioritize wrt what we need to get others onboard as well | 19:00 |
| s3wong | SumitNaiksatam: +1 for Wednesday | 19:00 |
| SumitNaiksatam | 17:00 UTC? | 19:00 |
| banix | ok with wednesday | 19:00 |
| SumitNaiksatam | that is 10 AM PDT | 19:01 |
| banix | sounds good to me | 19:01 |
| pcm_ | +1 | 19:01 |
| s3wong | +1 | 19:01 |
| prasadv | +1 | 19:01 |
| SridarK | +1 | 19:01 |
| s3wong | good for enikanorov_? | 19:01 |
| SumitNaiksatam | enikanorov_: is always here :-P | 19:01 |
| enikanorov_ | looks fine | 19:01 |
| SumitNaiksatam | ok done for now - wedenesday 17:00 UTC | 19:02 |
| SumitNaiksatam | we can adjust later | 19:02 |
| banix | time to move to alt | 19:02 |
| SumitNaiksatam | yeah, next meeting is waiting | 19:02 |
| s3wong | Talk to you guys next week! | 19:02 |
| banix | i mean for policy call | 19:02 |
| cgoncalves | banix: indeex :) | 19:02 |
| *** songole has quit IRC | 19:02 | |
| SumitNaiksatam | i had a summary ready, but not time | 19:02 |
| pcm_ | thanks for hosting SumitNaiksatam | 19:02 |
| SumitNaiksatam | no | 19:02 |
| cgoncalves | *indee | 19:02 |
| SumitNaiksatam | ok thanks everyone | 19:02 |
| s3wong | thanks! | 19:02 |
| *** pcm_ has left #openstack-meeting-3 | 19:02 | |
| banix | thank you sumit | 19:02 |
| SumitNaiksatam | will send summary in email | 19:02 |
| *** lenrow__ has joined #openstack-meeting-3 | 19:02 | |
| SridarK | bye | 19:02 |
| SumitNaiksatam | banix: sure | 19:02 |
| *** prasadv has left #openstack-meeting-3 | 19:02 | |
| SumitNaiksatam | #endmeeting | 19:02 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 19:02 | |
| openstack | Meeting ended Thu Mar 13 19:02:48 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:02 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-03-13-18.03.html | 19:02 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-03-13-18.03.txt | 19:02 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-03-13-18.03.log.html | 19:02 |
| *** mandeep has left #openstack-meeting-3 | 19:02 | |
| *** lenrow_ has quit IRC | 19:05 | |
| *** Ly100 has quit IRC | 19:10 | |
| *** SridharRamaswamy has quit IRC | 19:19 | |
| *** mwagner_lap has quit IRC | 19:19 | |
| *** lenrow has quit IRC | 19:22 | |
| *** SridarK has quit IRC | 19:22 | |
| *** sarob has joined #openstack-meeting-3 | 19:27 | |
| *** peristeri has quit IRC | 19:29 | |
| *** kathmandude has left #openstack-meeting-3 | 19:32 | |
| *** devlaps has quit IRC | 19:38 | |
| *** devlaps has joined #openstack-meeting-3 | 19:39 | |
| *** sarob has quit IRC | 19:40 | |
| *** sarob has joined #openstack-meeting-3 | 19:41 | |
| *** sarob has quit IRC | 19:42 | |
| *** devlaps has quit IRC | 19:43 | |
| *** eghobo has quit IRC | 19:45 | |
| *** hemanthravi has quit IRC | 19:47 | |
| *** thinrichs has quit IRC | 19:47 | |
| *** s3wong has quit IRC | 19:49 | |
| *** beyounn has quit IRC | 19:51 | |
| *** jcoufal has joined #openstack-meeting-3 | 19:56 | |
| *** MaxV has quit IRC | 19:58 | |
| *** MaxV has joined #openstack-meeting-3 | 19:59 | |
| *** lblanchard has quit IRC | 20:03 | |
| *** devlaps has joined #openstack-meeting-3 | 20:09 | |
| *** jtomasek has joined #openstack-meeting-3 | 20:13 | |
| *** devlaps has quit IRC | 20:14 | |
| *** julim has quit IRC | 20:15 | |
| *** jcoufal has quit IRC | 20:16 | |
| *** eghobo has joined #openstack-meeting-3 | 20:35 | |
| *** eghobo has quit IRC | 20:40 | |
| *** eghobo has joined #openstack-meeting-3 | 20:44 | |
| *** eghobo has quit IRC | 20:47 | |
| *** eghobo has joined #openstack-meeting-3 | 20:47 | |
| *** cnesa has joined #openstack-meeting-3 | 20:50 | |
| *** sarob has joined #openstack-meeting-3 | 20:55 | |
| *** beyounn has joined #openstack-meeting-3 | 20:59 | |
| *** jthopkin has joined #openstack-meeting-3 | 21:03 | |
| *** lenrow__ has quit IRC | 21:03 | |
| *** lenrow has joined #openstack-meeting-3 | 21:04 | |
| *** devlaps has joined #openstack-meeting-3 | 21:10 | |
| *** devlaps has quit IRC | 21:11 | |
| *** devlaps1 has joined #openstack-meeting-3 | 21:11 | |
| *** cnesa2 has joined #openstack-meeting-3 | 21:15 | |
| *** cnesa has quit IRC | 21:16 | |
| *** safchain has joined #openstack-meeting-3 | 21:20 | |
| *** RajeshMohan has joined #openstack-meeting-3 | 21:20 | |
| *** banix has quit IRC | 21:21 | |
| *** sarob has quit IRC | 21:30 | |
| *** sarob has joined #openstack-meeting-3 | 21:31 | |
| *** markmcclain has quit IRC | 21:31 | |
| *** lpetrut has quit IRC | 21:43 | |
| *** sarob has quit IRC | 21:49 | |
| *** jthopkin has quit IRC | 21:49 | |
| *** sarob has joined #openstack-meeting-3 | 21:51 | |
| *** sarob has quit IRC | 21:55 | |
| *** david-lyle has quit IRC | 21:58 | |
| *** jtomasek has quit IRC | 22:17 | |
| *** eguz has joined #openstack-meeting-3 | 22:40 | |
| *** eghobo has quit IRC | 22:43 | |
| *** wchrisj has quit IRC | 22:46 | |
| *** julim has joined #openstack-meeting-3 | 22:51 | |
| *** sarob has joined #openstack-meeting-3 | 22:54 | |
| *** julim has quit IRC | 22:59 | |
| *** sarob has quit IRC | 23:00 | |
| *** eguz has quit IRC | 23:00 | |
| *** ftcjeff has quit IRC | 23:02 | |
| *** mfer has quit IRC | 23:20 | |
| *** carl_baldwin has quit IRC | 23:29 | |
| *** eghobo has joined #openstack-meeting-3 | 23:34 | |
| *** julim has joined #openstack-meeting-3 | 23:42 | |
| *** markmcclain has joined #openstack-meeting-3 | 23:45 | |
| *** cnesa2 has quit IRC | 23:56 | |
| *** dguitarbite has joined #openstack-meeting-3 | 23:57 | |
| *** sarob has joined #openstack-meeting-3 | 23:57 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!