*** dboik has joined #openstack-meeting-3 | 00:01 | |
*** rockyg has quit IRC | 00:02 | |
*** dboik has quit IRC | 00:05 | |
*** yamahata has joined #openstack-meeting-3 | 00:10 | |
*** cjellick has quit IRC | 00:14 | |
*** otherwiseguy has quit IRC | 00:19 | |
*** terryw has joined #openstack-meeting-3 | 00:19 | |
*** cjellick has joined #openstack-meeting-3 | 00:19 | |
*** openstackstatus has quit IRC | 00:23 | |
*** ivar-lazzaro has quit IRC | 00:23 | |
*** openstackstatus has joined #openstack-meeting-3 | 00:24 | |
*** ChanServ sets mode: +v openstackstatus | 00:24 | |
*** cjellick has quit IRC | 00:24 | |
*** mfer has joined #openstack-meeting-3 | 00:27 | |
*** arosen has quit IRC | 00:28 | |
*** dboik has joined #openstack-meeting-3 | 00:36 | |
*** shwetaap has joined #openstack-meeting-3 | 00:38 | |
*** mfer has quit IRC | 00:42 | |
*** markmcclain has quit IRC | 00:43 | |
*** terryw has quit IRC | 00:44 | |
*** bpokorny_ has quit IRC | 00:44 | |
*** otherwiseguy has joined #openstack-meeting-3 | 00:45 | |
*** markmcclain has joined #openstack-meeting-3 | 00:53 | |
*** terryw has joined #openstack-meeting-3 | 00:54 | |
*** otherwiseguy has quit IRC | 00:54 | |
*** salv-orlando has quit IRC | 00:55 | |
*** jacalcat has joined #openstack-meeting-3 | 01:06 | |
*** s3wong has quit IRC | 01:07 | |
*** jacalcat has left #openstack-meeting-3 | 01:11 | |
*** alexsyip has quit IRC | 01:13 | |
*** shwetaap has quit IRC | 01:29 | |
*** stanzgy has joined #openstack-meeting-3 | 01:31 | |
*** otherwiseguy has joined #openstack-meeting-3 | 01:38 | |
*** terryw has quit IRC | 01:38 | |
*** jacalcat has joined #openstack-meeting-3 | 01:40 | |
*** jacalcat has left #openstack-meeting-3 | 01:46 | |
*** shwetaap has joined #openstack-meeting-3 | 01:47 | |
*** otherwiseguy has quit IRC | 01:49 | |
*** otherwiseguy has joined #openstack-meeting-3 | 01:49 | |
*** david-lyle has joined #openstack-meeting-3 | 01:50 | |
*** markmcclain has quit IRC | 01:55 | |
*** Longgeek has joined #openstack-meeting-3 | 02:26 | |
*** julim has quit IRC | 02:27 | |
*** lhcheng has quit IRC | 02:28 | |
*** lhcheng has joined #openstack-meeting-3 | 02:28 | |
*** lhcheng has quit IRC | 02:34 | |
*** hurgleburgler has joined #openstack-meeting-3 | 02:41 | |
*** coolsvap|afk is now known as coolsvap | 02:55 | |
*** armax has quit IRC | 03:03 | |
*** carl_baldwin has joined #openstack-meeting-3 | 03:05 | |
*** armax has joined #openstack-meeting-3 | 03:07 | |
*** jacalcat has joined #openstack-meeting-3 | 03:08 | |
*** jacalcat has left #openstack-meeting-3 | 03:13 | |
*** carl_baldwin has quit IRC | 03:19 | |
*** chuckC_ has joined #openstack-meeting-3 | 03:27 | |
*** coolsvap is now known as coolsvap|afk | 03:37 | |
*** coolsvap|afk is now known as coolsvap | 03:45 | |
*** shwetaap has quit IRC | 03:51 | |
*** hurgleburgler has quit IRC | 03:53 | |
*** armax has quit IRC | 03:59 | |
*** shwetaap has joined #openstack-meeting-3 | 04:06 | |
*** hurgleburgler has joined #openstack-meeting-3 | 04:30 | |
*** amotoki has joined #openstack-meeting-3 | 04:34 | |
*** carl_baldwin has joined #openstack-meeting-3 | 04:38 | |
*** shwetaap has quit IRC | 04:43 | |
*** shwetaap has joined #openstack-meeting-3 | 04:43 | |
*** pettori has joined #openstack-meeting-3 | 04:52 | |
*** shwetaap has quit IRC | 04:57 | |
*** pettori has quit IRC | 05:05 | |
*** carl_baldwin has quit IRC | 05:07 | |
*** hurgleburgler has quit IRC | 05:09 | |
*** david-lyle has quit IRC | 05:10 | |
*** lhcheng has joined #openstack-meeting-3 | 05:18 | |
*** lhcheng has quit IRC | 05:21 | |
*** lhcheng has joined #openstack-meeting-3 | 05:21 | |
*** jcoufal has joined #openstack-meeting-3 | 05:22 | |
*** david-lyle has joined #openstack-meeting-3 | 05:27 | |
*** yamahata has quit IRC | 05:51 | |
*** yamahata has joined #openstack-meeting-3 | 05:52 | |
*** coolsvap is now known as coolsvap|afk | 06:00 | |
*** coolsvap|afk is now known as coolsvap | 06:12 | |
*** pkoniszewski has joined #openstack-meeting-3 | 06:13 | |
*** mrunge has joined #openstack-meeting-3 | 06:13 | |
*** mrunge has quit IRC | 06:39 | |
*** lhcheng has quit IRC | 06:40 | |
*** mrunge has joined #openstack-meeting-3 | 06:47 | |
*** MaxV has joined #openstack-meeting-3 | 06:49 | |
*** MaxV has quit IRC | 06:55 | |
*** k4n0 has joined #openstack-meeting-3 | 06:56 | |
*** flaper87|afk is now known as flaper87 | 06:58 | |
*** k4n0 has quit IRC | 07:02 | |
*** matrohon has joined #openstack-meeting-3 | 07:06 | |
*** ttrifonov_zZzz is now known as ttrifonov | 07:12 | |
*** k4n0 has joined #openstack-meeting-3 | 07:15 | |
*** ttrifonov is now known as ttrifonov_zZzz | 07:16 | |
*** ttrifonov_zZzz is now known as ttrifonov | 07:17 | |
*** mrunge has quit IRC | 07:21 | |
*** mrunge has joined #openstack-meeting-3 | 07:29 | |
*** k4n0 has quit IRC | 07:42 | |
*** MaxV has joined #openstack-meeting-3 | 07:44 | |
*** MaxV has quit IRC | 07:49 | |
*** SumitNaiksatam has quit IRC | 07:50 | |
*** SumitNaiksatam has joined #openstack-meeting-3 | 07:50 | |
*** k4n0 has joined #openstack-meeting-3 | 07:55 | |
*** dboik has quit IRC | 08:00 | |
*** safchain has joined #openstack-meeting-3 | 08:00 | |
*** sunrenjie6 has quit IRC | 08:04 | |
*** sunrenjie has joined #openstack-meeting-3 | 08:05 | |
*** yamamoto has quit IRC | 08:08 | |
*** sunrenjie has quit IRC | 08:10 | |
*** salv-orlando has joined #openstack-meeting-3 | 08:11 | |
*** ttrifonov is now known as ttrifonov_zZzz | 08:13 | |
*** ttrifonov_zZzz is now known as ttrifonov | 08:15 | |
*** ttrifonov is now known as ttrifonov_zZzz | 08:16 | |
*** sunrenjie has joined #openstack-meeting-3 | 08:16 | |
*** ttrifonov_zZzz is now known as ttrifonov | 08:17 | |
*** ttrifonov is now known as ttrifonov_zZzz | 08:18 | |
*** ttrifonov_zZzz is now known as ttrifonov | 08:20 | |
*** MaxV has joined #openstack-meeting-3 | 08:20 | |
*** david-lyle has quit IRC | 08:35 | |
*** zz_johnthetubagu is now known as johnthetubaguy | 09:17 | |
*** sunrenjie has quit IRC | 09:29 | |
*** coolsvap is now known as coolsvap|afk | 09:56 | |
*** otherwiseguy has quit IRC | 09:59 | |
*** yamahata has quit IRC | 10:19 | |
*** ttrifonov is now known as ttrifonov_zZzz | 10:20 | |
*** ttrifonov_zZzz is now known as ttrifonov | 10:22 | |
*** scheuran has joined #openstack-meeting-3 | 10:38 | |
*** stanzgy has quit IRC | 10:52 | |
*** igordcard has joined #openstack-meeting-3 | 10:53 | |
*** MaxV has quit IRC | 11:12 | |
*** MaxV has joined #openstack-meeting-3 | 11:12 | |
*** MaxV has quit IRC | 11:17 | |
*** MaxV has joined #openstack-meeting-3 | 11:27 | |
*** amotoki_ has joined #openstack-meeting-3 | 11:34 | |
*** amotoki_ has quit IRC | 11:34 | |
*** otherwiseguy has joined #openstack-meeting-3 | 11:38 | |
*** otherwiseguy has quit IRC | 11:43 | |
*** julim has joined #openstack-meeting-3 | 11:45 | |
*** amotoki has quit IRC | 11:45 | |
*** coolsvap|afk is now known as coolsvap | 11:46 | |
*** sarob has quit IRC | 11:46 | |
*** flaviof_zzz has quit IRC | 11:50 | |
*** bradjones has quit IRC | 11:59 | |
*** coolsvap is now known as coolsvap|afk | 12:01 | |
*** markmcclain has joined #openstack-meeting-3 | 12:15 | |
*** sarob has joined #openstack-meeting-3 | 12:20 | |
*** flaviof_zzz has joined #openstack-meeting-3 | 12:22 | |
*** bradjones has joined #openstack-meeting-3 | 12:26 | |
*** salv-orlando has quit IRC | 12:27 | |
*** otherwiseguy has joined #openstack-meeting-3 | 12:32 | |
*** otherwiseguy has quit IRC | 12:37 | |
*** sigmavirus24_awa is now known as sigmavirus24 | 12:49 | |
*** amotoki has joined #openstack-meeting-3 | 13:01 | |
*** flaviof_zzz is now known as flaviof | 13:03 | |
*** jaypipes has joined #openstack-meeting-3 | 13:12 | |
*** zz_jgrimm is now known as jgrimm | 13:13 | |
*** shwetaap has joined #openstack-meeting-3 | 13:16 | |
*** otherwiseguy has joined #openstack-meeting-3 | 13:26 | |
*** peristeri has joined #openstack-meeting-3 | 13:26 | |
*** otherwiseguy has quit IRC | 13:31 | |
*** markmcclain has quit IRC | 13:33 | |
*** thangp has joined #openstack-meeting-3 | 13:38 | |
*** julim has quit IRC | 13:47 | |
*** otherwiseguy has joined #openstack-meeting-3 | 13:52 | |
*** dboik has joined #openstack-meeting-3 | 13:59 | |
*** jgrimm is now known as zz_jgrimm | 13:59 | |
*** salv-orlando has joined #openstack-meeting-3 | 14:10 | |
*** pkoniszewski has quit IRC | 14:11 | |
*** dt_os has joined #openstack-meeting-3 | 14:13 | |
*** otherwiseguy has quit IRC | 14:16 | |
*** mwagner_lap has joined #openstack-meeting-3 | 14:19 | |
*** dboik has quit IRC | 14:30 | |
*** dboik has joined #openstack-meeting-3 | 14:30 | |
*** dt_os has quit IRC | 14:32 | |
*** hurgleburgler has joined #openstack-meeting-3 | 14:33 | |
*** carl_baldwin has joined #openstack-meeting-3 | 14:38 | |
*** markmcclain has joined #openstack-meeting-3 | 14:41 | |
*** markmcclain has quit IRC | 14:41 | |
*** k4n0 has quit IRC | 14:42 | |
*** pkoniszewski has joined #openstack-meeting-3 | 14:42 | |
*** markmcclain has joined #openstack-meeting-3 | 14:43 | |
*** zz_jgrimm is now known as jgrimm | 14:46 | |
*** otherwiseguy has joined #openstack-meeting-3 | 14:47 | |
*** jschwarz has joined #openstack-meeting-3 | 14:51 | |
*** markmcclain has quit IRC | 14:53 | |
*** gholler has joined #openstack-meeting-3 | 14:57 | |
*** gholler_ has joined #openstack-meeting-3 | 14:57 | |
*** devvesa has joined #openstack-meeting-3 | 14:58 | |
*** yamahata has joined #openstack-meeting-3 | 14:58 | |
*** seizadi has joined #openstack-meeting-3 | 14:59 | |
*** johnbelamaric has joined #openstack-meeting-3 | 15:00 | |
carl_baldwin | hi all | 15:01 |
---|---|---|
jschwarz | hi carl :) | 15:01 |
carl_baldwin | jschwarz: hi | 15:01 |
ChuckC | o/ | 15:01 |
jschwarz | added an item to the agenda in case you didn't see it ;p | 15:01 |
*** pcm__ has joined #openstack-meeting-3 | 15:01 | |
carl_baldwin | jschwarz: I did see it. | 15:01 |
carl_baldwin | thanks | 15:02 |
devvesa | hi | 15:02 |
carl_baldwin | #startmeeting neutron_l3 | 15:02 |
openstack | Meeting started Thu Oct 9 15:02:14 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:02 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:02 |
*** openstack changes topic to " (Meeting topic: neutron_l3)" | 15:02 | |
openstack | The meeting name has been set to 'neutron_l3' | 15:02 |
carl_baldwin | #topic Announcements | 15:02 |
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)" | 15:02 | |
carl_baldwin | I don’t think I have any announcements except that Juno RC2 is being work on, I believe. | 15:03 |
carl_baldwin | Any announcements? | 15:04 |
carl_baldwin | #topic Bugs | 15:04 |
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)" | 15:04 | |
*** tidwellr has joined #openstack-meeting-3 | 15:04 | |
carl_baldwin | I did follow up with more triage since the last meeting. That was my action item. | 15:04 |
carl_baldwin | I haven’t seen any concerning bugs pop up since then. | 15:05 |
carl_baldwin | Are there any bugs that need to be brought up? | 15:05 |
matrohon | hi! I need one more core review on this : https://review.openstack.org/#/c/116924/ | 15:05 |
matrohon | I'd like it to merge in juno :) | 15:06 |
carl_baldwin | matrohon: I’ll add it to my queue. | 15:06 |
carl_baldwin | matrohon: Is it tagged for juno potential? | 15:07 |
matrohon | carl_baldwin : yes it is tagged. thanks | 15:07 |
carl_baldwin | ok | 15:07 |
*** mfer has joined #openstack-meeting-3 | 15:07 | |
*** Rajeev has joined #openstack-meeting-3 | 15:07 | |
carl_baldwin | Any other bugs? | 15:08 |
carl_baldwin | #topic l3-high-availability | 15:08 |
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)" | 15:08 | |
carl_baldwin | safchain: amuller: ping | 15:08 |
carl_baldwin | Anything new here to report or discuss? | 15:08 |
jschwarz | a muller is out o PTO (holiday, i'm no supposed to be here either ;p) | 15:08 |
safchain | hi | 15:09 |
safchain | nothing special this week | 15:09 |
carl_baldwin | safchain: Thanks. Feel free to ping me if you need something. | 15:09 |
jschwarz | I would like to discuss the ns_name issue as it relates to the HA functional tests | 15:09 |
safchain | carl_baldwin, thx | 15:09 |
jschwarz | #link https://review.openstack.org/#/c/123434/2/neutron/agent/l3_agent.py | 15:10 |
carl_baldwin | jschwarz: almost there. | 15:10 |
jschwarz | sorry then :) | 15:10 |
carl_baldwin | #topic bgp-dynamic-routing | 15:10 |
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)" | 15:10 | |
carl_baldwin | devvesa: ping | 15:10 |
devvesa | carl_baldwin: hi | 15:10 |
carl_baldwin | devvesa: good discussions this week. Any progress on the bp? | 15:11 |
devvesa | been busy this morning. I'm considering your idea about promoting ips or networks to advertise them | 15:11 |
devvesa | also I think that modeling the edge router is not needed since it is not useful for your use case | 15:12 |
carl_baldwin | devvesa: One request. Could you link that testing page that you gave me a link to to the L3 subteam page in the bgp-dynamic-routing section? | 15:12 |
devvesa | sure. | 15:12 |
devvesa | #link https://wiki.openstack.org/wiki/Neutron/DynamicRouting/TestingDynamicRouting | 15:13 |
devvesa | oh, now I've read 'to the subteam page' :) | 15:13 |
devvesa | I'll do | 15:13 |
carl_baldwin | devvesa: The modelling change that I thought was most important was that advertised routes associate with routers. Any more thoughts on that? | 15:13 |
carl_baldwin | #action devvesa will link dynamic routing testing page to subteam page. | 15:14 |
devvesa | to me the advertised routes should be associated to the routing instance, which is the instance that is 'deployed' in the dr_agent | 15:15 |
devvesa | but we can discuss it more in the spec | 15:15 |
*** salv-orlando has quit IRC | 15:15 | |
carl_baldwin | devvesa: Let me think about that a little more. Maybe I don’t fully understand the scope of the RoutingInstance object. I’ll review the spec again. | 15:16 |
*** jacalcat has joined #openstack-meeting-3 | 15:16 | |
carl_baldwin | It still seems natural to associate with the router because the router is what will be handling the route and it has the next hop for the route as a property of the router (its public address). | 15:17 |
carl_baldwin | devvesa: Thanks for your work on this. | 15:17 |
carl_baldwin | #topic L3 Agent Refactoring | 15:17 |
*** openstack changes topic to "L3 Agent Refactoring (Meeting topic: neutron_l3)" | 15:17 | |
carl_baldwin | jschwarz: hi | 15:17 |
jschwarz | carl_baldwin, hi | 15:18 |
jschwarz | would be happy if you'd have a look at the link i posted above | 15:18 |
carl_baldwin | Sorry to have ruffled some feathers here. It seems we have two conflicting efforts going on with the L3 agent. | 15:18 |
jschwarz | https://review.openstack.org/#/c/123434/2/neutron/agent/l3_agent.py | 15:18 |
jschwarz | that's quite alright, and I do realise your intentions on this. I realise the current state isn't the best one | 15:19 |
jschwarz | the earlier patchset I linked contains what I believe you're looking for | 15:19 |
* carl_baldwin is looking at the link | 15:19 | |
*** amotoki has quit IRC | 15:20 | |
carl_baldwin | jschwarz: I think the property is fine. I can leave that in. | 15:20 |
jschwarz | very well then | 15:20 |
carl_baldwin | I also see the motivation for _get_router_info from the test you linked. However, this doesn’t feel quite right. | 15:20 |
carl_baldwin | Could this work as a static factory method on the RouterInfo class? | 15:21 |
jschwarz | You mean, a RounterInfo.create() function which returns what we need? | 15:21 |
*** julim has joined #openstack-meeting-3 | 15:22 | |
carl_baldwin | jschwarz: Yes, something like that. | 15:22 |
carl_baldwin | It doesn’t make sense where it is now to me. | 15:22 |
jschwarz | This will be problematic since in the functional tests we also change the RouterInfo we create (we override it with a TestRouterInfo, adding the cfg.CONF.host argument) | 15:22 |
jschwarz | So a factory function in the RouterInfo namespace will require also overriding functions that create the RouterInfo in the test agent | 15:23 |
jschwarz | #link https://review.openstack.org/#/c/117994/15/neutron/tests/agents/l3_agent.py | 15:23 |
jschwarz | :( | 15:24 |
carl_baldwin | That test does override it now. so, it is not a new requirement. The question is how it overrides it, right? | 15:25 |
jschwarz | Right. But I think it's better to override a _get_router_info over overriding (and refactoring) _router_added (iirc) | 15:25 |
carl_baldwin | I have not had the chance to look through the test yet. I’ll do so today. | 15:25 |
jschwarz | I'm happy to schedule a sit-down with you on this subject on Monday once we both get a chance to think about this again, if you want :) | 15:26 |
carl_baldwin | I’ll abandon the reverts that I have up and try to propose something that will meet both our needs. | 15:26 |
jschwarz | carl_baldwin, sounds good. | 15:26 |
carl_baldwin | #action carl_baldwin will abondon reverts and find a better proposal. | 15:27 |
jschwarz | carl_baldwin, I'll be happy if you let me write that patch since the functional tests patch depends on the solution we'll implement | 15:27 |
carl_baldwin | jschwarz: I’ll be in touch. | 15:27 |
jschwarz | sounds great | 15:27 |
jschwarz | thanks | 15:27 |
*** Swami has joined #openstack-meeting-3 | 15:27 | |
carl_baldwin | jschwarz: we still have a fundamental problem now in that we have two efforts going on that will be very difficult to coordinate. | 15:28 |
Swami | hi | 15:28 |
carl_baldwin | Swami: hi | 15:28 |
jschwarz | carl_baldwin, I agree, so we better work on this together | 15:29 |
jschwarz | carl_baldwin, the functional tests patch is ready for core review since the smaller patches are all merged - maybe we can consider having the refactoring effort also include the functional tests | 15:29 |
carl_baldwin | I will post a spec for the refactoring I plan soon (hopefully today) | 15:30 |
*** corvus is now known as jeblair | 15:30 | |
carl_baldwin | jschwarz: I will review the tests patch. Is it just the one patch? | 15:30 |
jschwarz | yep :) the rest are merged | 15:31 |
carl_baldwin | jschwarz: Thanks. | 15:31 |
yamahata | hi, I'm also interested in l3 agent refactoring. | 15:31 |
jschwarz | the integration tests are well in the work (will discuss this later) but that's a ways off IMO | 15:31 |
carl_baldwin | jschwarz: do you plan more work beyond this patch in the near future? | 15:31 |
carl_baldwin | yamahata: I will add you to the review of the spec. | 15:31 |
yamahata | carl_baldwin: can you explain the plan roughly? | 15:31 |
carl_baldwin | yamahata: It will be better to wait for the spec. I will try to get it up today. | 15:32 |
yamahata | carl_baldwin: got it | 15:32 |
jschwarz | the integration tests' first test is planned to be about the HA (since amuller is working closely on this with me and Maru) | 15:32 |
matrohon | carl_baldwin : interested too :) | 15:32 |
jschwarz | but first the framework has to go through, and a spec, etc... and those aren't up yet | 15:32 |
*** BrianB_ has joined #openstack-meeting-3 | 15:33 | |
jschwarz | carl_baldwin, you can see the current needs of the integration tests here: https://review.openstack.org/#/c/123000/5/neutron/tests/agents/l3_agent.py | 15:33 |
jschwarz | basically, more functions from the original L3 code needs overriding | 15:33 |
jschwarz | that said, it's a long way off | 15:33 |
*** johnbelamaric has quit IRC | 15:34 | |
*** cjellick has joined #openstack-meeting-3 | 15:34 | |
carl_baldwin | jschwarz: I will get more familiar with this work. | 15:34 |
carl_baldwin | Thanks. | 15:34 |
*** johnbelamaric has joined #openstack-meeting-3 | 15:34 | |
carl_baldwin | #topic neutron-ovs-dvr | 15:35 |
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)" | 15:35 | |
jschwarz | Thank you. i'll make sure I add you as a reviewer on all relevant patches and will try to keep this forum involved in the future :) | 15:35 |
carl_baldwin | jschwarz: That will be great, thanks. | 15:35 |
carl_baldwin | Swami: hi | 15:35 |
Swami | hi | 15:36 |
carl_baldwin | I’m sorry that I missed most of the meeting yesterday. I had a one-time conflict. | 15:36 |
Swami | no problems | 15:36 |
carl_baldwin | Anything to report or discuss? | 15:36 |
Swami | regarding DVR there are couple of items that we need to discuss | 15:36 |
Swami | There are two bugs right now, one with respect DB lockwait timeout and the other is triggered because of the DB lockwait timeout | 15:37 |
Swami | DB DuplicateError for Snat binding. | 15:37 |
Swami | I have posted patches for both these bugs. | 15:38 |
Swami | #link https://review.openstack.org/#/c/126793/ | 15:38 |
Swami | patch for the DB Duplicate Error. | 15:38 |
*** pkoniszewski has quit IRC | 15:38 | |
carl_baldwin | Swami: Is it ready for review? Do you need input on it? | 15:39 |
Swami | This patch again introduces the "hints" in the scheduler, since we have a timing issue with respect to Gateway clear and interface-delete, we need to prevent the snat_scheduler being called when there is router_interface-delete, so I am using the hints. | 15:39 |
Swami | Take a look at it and let me know. | 15:39 |
Swami | I have still address couple of unit tests on this patch, but I want you to take a look at it. | 15:40 |
carl_baldwin | Swami: I will. | 15:40 |
Swami | s/have/have to | 15:40 |
carl_baldwin | I have been meaning to get to it. | 15:40 |
Swami | Also on the DB lockwait timeout issue, there is patch out there | 15:40 |
carl_baldwin | #action carl_baldwin will review https://review.openstack.org/#/c/126793/ | 15:41 |
Swami | #lin https://review.openstack.org/#/c/127129/ | 15:41 |
Swami | #link https://review.openstack.org/#/c/127129/ | 15:41 |
Swami | This patch also needs your attention. | 15:41 |
carl_baldwin | #action carl_baldwin will review https://review.openstack.org/#/c/127129/ | 15:42 |
*** scheuran has quit IRC | 15:42 | |
carl_baldwin | Swami: I have had these on my list to look at. I will bump them up to the top. | 15:42 |
* carl_baldwin wonders where the time goes | 15:42 | |
*** stevelle has left #openstack-meeting-3 | 15:42 | |
Swami | Also I have posted a WIP patch for the VPN with DVR. | 15:42 |
carl_baldwin | Swami: Thank you for the links. | 15:42 |
Swami | #link https://review.openstack.org/#/c/127133/ | 15:42 |
Swami | Last week we had an action item to create a Wiki to start adding notes for the HA and DVR with Service node. | 15:43 |
Swami | #link https://wiki.openstack.org/wiki/Neutron/DVR/ServiceNode-HA | 15:43 |
carl_baldwin | Swami: A new one I have not seen yet. | 15:43 |
Swami | carl_baldwin: yes this is a new one, since armando abandoned the VPN patch that prevents someone from configuring the VPN for DVR, I started working on this patch. | 15:44 |
Swami | Now with DVR the IPsec reference implementation should work. | 15:44 |
carl_baldwin | Swami: that will be good. | 15:45 |
Swami | carl_baldwin: I will work on the "Migration comments" that you made and try to push a patch. | 15:45 |
carl_baldwin | Thanks for the HA/DVR wiki page link too. That will be an important improvement. | 15:45 |
Swami | That's all I have from the DVR side. | 15:45 |
carl_baldwin | Swami: How many of you are there? ;) | 15:45 |
Swami | Also rajeev is back from vacation and I will ask him to take a look at the IPv6. | 15:46 |
carl_baldwin | Swami: Thanks for the report. | 15:46 |
*** johnbelamaric has quit IRC | 15:46 | |
Swami | Right now it's only me and rajeev just joined me today. | 15:46 |
*** johnbelamaric has joined #openstack-meeting-3 | 15:46 | |
* carl_baldwin was just kidding | 15:47 | |
carl_baldwin | Swami: Great work. Thanks. | 15:47 |
carl_baldwin | #topic Open Discussion | 15:47 |
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)" | 15:47 | |
carl_baldwin | I think that is all I wanted to cover today. | 15:47 |
carl_baldwin | Anything else? | 15:47 |
Swami | I am done, nothing else. | 15:47 |
jschwarz | Surprisingly, none from me :) | 15:47 |
pcm__ | is there a link with an overview of the plans for refactorings? | 15:47 |
* pcm__ trying to catch up | 15:48 | |
carl_baldwin | pcm__: Not yet, I’m hoping to get a spec up today. If not today then tomorrow. | 15:48 |
carl_baldwin | #action carl_baldwin will put up a spec detailing l3 agent refactoring goals. | 15:48 |
pcm__ | carl_baldwin: cool. Interested in that effort as well | 15:48 |
jschwarz | will be happy if you could also add me as a reviewer for that | 15:48 |
carl_baldwin | jschwarz: I will. | 15:48 |
pcm__ | me too | 15:48 |
matrohon | carl_baldwin : I wonder if you plan to resubmit pluggable-ext-net in kilo | 15:48 |
carl_baldwin | pcm__: Will add you too. | 15:48 |
*** otherwiseguy has quit IRC | 15:48 | |
matrohon | https://review.openstack.org/#/c/88619/5/specs/juno/pluggable-ext-net.rst | 15:49 |
carl_baldwin | matrohon: Yes, I do. That is important work for me and I will resubmit it soon. It will benefit greatly from some refactoring. | 15:49 |
matrohon | carl_baldwin : good to know thanks | 15:49 |
matrohon | is there anybody around still interested in BGPVPN? | 15:50 |
matrohon | https://review.openstack.org/#/c/93329/ | 15:50 |
*** johnbelamaric has quit IRC | 15:51 | |
carl_baldwin | matrohon: devvesa mentioned a possible pod session or something at the conference. | 15:51 |
Swami | yes I will be interested in BGPVPN | 15:51 |
devvesa | matrohon: yes, I would like to reserve a pod during the summit to talk about BGP and BGPVPN | 15:51 |
carl_baldwin | devvesa: loop in Swami and matrohon for that discussion. | 15:52 |
matrohon | carl_baldwin, devvesa, Swami : great, there is a natural overlap devvesa work | 15:52 |
matrohon | pods are exclusively on friday? | 15:53 |
devvesa | no | 15:53 |
devvesa | I think there will be pods available all the design session days | 15:54 |
devvesa | however, even the design sessions are not defined yet (at least in the sched site) | 15:54 |
Swami | If we don't want to miss the design session then we can book the pod on friday to have our discussion | 15:54 |
devvesa | Ok. I'll reserve on friday | 15:55 |
matrohon | fine, one of the main contributor on BGP stuff in our team will attend the summit only untill thurday mornig | 15:55 |
matrohon | friday won't match with his planning :( | 15:55 |
devvesa | ouch | 15:55 |
carl_baldwin | Let’s wait a bit for the rest of the schedule to come out. We’ll have a better idea of when we can fit it in. | 15:56 |
*** markmcclain has joined #openstack-meeting-3 | 15:56 | |
matrohon | there is no design session wednesday pm for neutron | 15:56 |
matrohon | for the moment | 15:56 |
matrohon | if i do remember well :) | 15:56 |
devvesa | Yes, let's wait. I'll ping all of you via IRC before reserve the pod and see your availability , ok? | 15:57 |
matrohon | http://kilodesignsummit.sched.org/overview/type/neutron#.VDawUps7vmE | 15:57 |
matrohon | devvesa : fine | 15:57 |
carl_baldwin | devvesa: Okay. | 15:57 |
*** markmcclain1 has joined #openstack-meeting-3 | 15:58 | |
carl_baldwin | Thanks everyone. I’m looking forward to Kilo and the summit. | 15:59 |
carl_baldwin | #endmeeting | 15:59 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:59 | |
openstack | Meeting ended Thu Oct 9 15:59:15 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:59 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-10-09-15.02.html | 15:59 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-10-09-15.02.txt | 15:59 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-10-09-15.02.log.html | 15:59 |
devvesa | bye! | 15:59 |
jschwarz | bye guys :) | 15:59 |
*** lhcheng has joined #openstack-meeting-3 | 16:00 | |
jschwarz | carl_baldwin, I'll be off for the rest of the week so i'll try to catch you on monday and see if we can work something out :) | 16:00 |
jschwarz | have a nice weekend guys | 16:00 |
*** markmcclain has quit IRC | 16:00 | |
pcm__ | bye | 16:00 |
carl_baldwin | jschwarz: okay | 16:00 |
carl_baldwin | Thanks | 16:00 |
*** pcm__ has left #openstack-meeting-3 | 16:00 | |
*** jschwarz has quit IRC | 16:00 | |
carl_baldwin | Have a great weekend | 16:00 |
*** otherwiseguy has joined #openstack-meeting-3 | 16:02 | |
*** markmcclain1 has quit IRC | 16:03 | |
*** johnbelamaric has joined #openstack-meeting-3 | 16:03 | |
*** armax has joined #openstack-meeting-3 | 16:03 | |
*** markmcclain has joined #openstack-meeting-3 | 16:04 | |
*** devvesa has quit IRC | 16:04 | |
*** johnbelamaric has quit IRC | 16:06 | |
*** johnbelamaric_ has joined #openstack-meeting-3 | 16:06 | |
*** yamahata has quit IRC | 16:06 | |
*** safchain has quit IRC | 16:07 | |
*** lhcheng has quit IRC | 16:08 | |
*** lhcheng has joined #openstack-meeting-3 | 16:09 | |
*** carl_baldwin has quit IRC | 16:11 | |
*** SridarK has quit IRC | 16:12 | |
*** matrohon has quit IRC | 16:12 | |
*** lhcheng has quit IRC | 16:13 | |
*** cbader has joined #openstack-meeting-3 | 16:15 | |
*** igordcard has quit IRC | 16:16 | |
*** robcresswell has joined #openstack-meeting-3 | 16:22 | |
*** MaxV has quit IRC | 16:24 | |
*** johnbelamaric_ has quit IRC | 16:24 | |
*** johnbelamaric_ has joined #openstack-meeting-3 | 16:25 | |
*** robcresswell has left #openstack-meeting-3 | 16:25 | |
*** johnbelamaric_ has quit IRC | 16:26 | |
*** david-lyle has joined #openstack-meeting-3 | 16:26 | |
*** peristeri has quit IRC | 16:30 | |
*** peristeri has joined #openstack-meeting-3 | 16:32 | |
*** otherwiseguy has quit IRC | 16:35 | |
*** peristeri has quit IRC | 16:40 | |
*** peristeri has joined #openstack-meeting-3 | 16:40 | |
*** pettori has joined #openstack-meeting-3 | 16:42 | |
*** igordcard has joined #openstack-meeting-3 | 16:45 | |
*** bradjones has quit IRC | 16:46 | |
*** s3wong has joined #openstack-meeting-3 | 16:47 | |
*** carl_baldwin has joined #openstack-meeting-3 | 16:51 | |
*** johnthetubaguy is now known as zz_johnthetubagu | 16:52 | |
*** sigmavirus24 has left #openstack-meeting-3 | 16:57 | |
*** Youcef has joined #openstack-meeting-3 | 17:04 | |
*** salv-orlando has joined #openstack-meeting-3 | 17:08 | |
*** alexpilotti has joined #openstack-meeting-3 | 17:23 | |
*** lhcheng has joined #openstack-meeting-3 | 17:34 | |
*** jcoufal has quit IRC | 17:35 | |
*** peristeri has quit IRC | 17:40 | |
*** ivar-lazzaro has joined #openstack-meeting-3 | 17:40 | |
*** SumitNaiksatam has quit IRC | 17:40 | |
*** seizadi has quit IRC | 17:42 | |
*** peristeri has joined #openstack-meeting-3 | 17:45 | |
*** otherwiseguy has joined #openstack-meeting-3 | 17:46 | |
*** lhcheng has quit IRC | 17:49 | |
*** lhcheng has joined #openstack-meeting-3 | 17:49 | |
*** peristeri has quit IRC | 17:51 | |
*** mrunge has quit IRC | 17:51 | |
*** lhcheng has quit IRC | 17:54 | |
*** gholler_ has quit IRC | 17:55 | |
*** gholler has quit IRC | 17:55 | |
*** sigmavirus24 has joined #openstack-meeting-3 | 17:56 | |
*** jacalcat has left #openstack-meeting-3 | 17:56 | |
*** glebo has joined #openstack-meeting-3 | 17:58 | |
*** rkukura has joined #openstack-meeting-3 | 17:59 | |
*** SumitNaiksatam has joined #openstack-meeting-3 | 18:00 | |
SumitNaiksatam | hi | 18:00 |
rkukura | hi | 18:00 |
ivar-lazzaro | hi | 18:01 |
s3wong | hello | 18:01 |
SumitNaiksatam | rkukura: ivar-lazzaro s3wong: hi | 18:01 |
glebo | yo | 18:01 |
*** yyywu has joined #openstack-meeting-3 | 18:01 | |
SumitNaiksatam | lets get started | 18:01 |
SumitNaiksatam | glebo: hi | 18:01 |
*** shakamunyi has joined #openstack-meeting-3 | 18:01 | |
*** shakamunyi has quit IRC | 18:01 | |
SumitNaiksatam | #startmeeting networking_policy | 18:01 |
openstack | Meeting started Thu Oct 9 18:01:54 2014 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:01 |
*** openstack changes topic to " (Meeting topic: networking_policy)" | 18:01 | |
openstack | The meeting name has been set to 'networking_policy' | 18:01 |
SumitNaiksatam | #info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy | 18:02 |
SumitNaiksatam | #chairs s3wong ivar-lazzaro rkukura | 18:02 |
SumitNaiksatam | just in case i lose connectivity | 18:02 |
SumitNaiksatam | #topic Patches in review | 18:03 |
*** openstack changes topic to "Patches in review (Meeting topic: networking_policy)" | 18:03 | |
SumitNaiksatam | #link #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy+branch:master,n,z | 18:03 |
SumitNaiksatam | the above are the server side patches which we are focussing on for now | 18:03 |
SumitNaiksatam | the good news is that we got some patches merged over the last few days | 18:04 |
SumitNaiksatam | thanks to all the reviewers! | 18:04 |
s3wong | implicit driver is next in the chain | 18:04 |
SumitNaiksatam | s3wong: yes, thanks for the reviews | 18:04 |
SumitNaiksatam | the GBP redirect to service chain patches have also been pushed | 18:05 |
*** hemanthravi has joined #openstack-meeting-3 | 18:05 | |
SumitNaiksatam | i notice that multiple patches are in review | 18:05 |
SumitNaiksatam | the spec is also in review, so we need to get the spec reviewed, approved, merged first | 18:05 |
SumitNaiksatam | hemanthravi: good timing ;-( | 18:05 |
SumitNaiksatam | oopps i meant ;-) | 18:05 |
hemanthravi | hi | 18:06 |
hemanthravi | :) | 18:06 |
*** nbouthors has joined #openstack-meeting-3 | 18:06 | |
SumitNaiksatam | so taking a step back…how is the stackforge process coming along, in terms of pusing patches for reviews, and reveiwing? | 18:06 |
SumitNaiksatam | anyone face any issues, or things we need to change? | 18:06 |
SumitNaiksatam | we are following the standard openstack process (so its not new) | 18:07 |
SumitNaiksatam | hopefully we can get out of the long-chain-of-dependencies mode pretty soon | 18:07 |
SumitNaiksatam | and not have to spent the rest of lives rebasing! ;-) | 18:08 |
hemanthravi | will resume reviews from my side | 18:08 |
SumitNaiksatam | hemanthravi: thanks | 18:08 |
SumitNaiksatam | lets tackle the service chain spec review as a separate topic, i forgot to add it to the agenda | 18:08 |
SumitNaiksatam | ivar-lazzaro: rkukura: anything else we need to discuss in terms of the patches that are in review? (we will discuss DB schema and resource mapping driver refactoring separately) | 18:09 |
rkukura | nothing I can think of | 18:09 |
SumitNaiksatam | rkukura: okay | 18:09 |
ivar-lazzaro | SumitNaiksatam: nope | 18:10 |
SumitNaiksatam | btw, i forgot to mention, Ronak mentioned that he cannot make it to the meeting today, and i believe banix is still off work | 18:10 |
SumitNaiksatam | ivar-lazzaro: okay | 18:10 |
SumitNaiksatam | #topic GBP DB | 18:10 |
*** openstack changes topic to "GBP DB (Meeting topic: networking_policy)" | 18:10 | |
glebo | Sumit: "meeting today" = this meeting, or some other meetup? | 18:11 |
SumitNaiksatam | glebo: ah, i meant this meeting | 18:11 |
glebo | sumit: ack | 18:11 |
glebo | thx | 18:11 |
SumitNaiksatam | ivar-lazzaro: so you posted the separate schema patch? | 18:11 |
SumitNaiksatam | #link https://review.openstack.org/#/c/126383/ | 18:12 |
ivar-lazzaro | SumitNaiksatam: yes, as it was mentioned in the ML discussion there are roughly two ways of addressing this | 18:12 |
SumitNaiksatam | ivar-lazzaro: okay | 18:12 |
SumitNaiksatam | ivar-lazzaro: so we for Juno we have decided to go with a separate DB so as not to break neutron migrations? | 18:12 |
ivar-lazzaro | SumitNaiksatam: Different Schema Different Chain (DSDC) or Same Schema Different Chain (SSDC) | 18:12 |
SumitNaiksatam | ivar-lazzaro: :-) | 18:13 |
ivar-lazzaro | SumitNaiksatam: we definitively know that we need to have a different chain | 18:13 |
rkukura | I thought we prefered a separate chain in the same DB? | 18:13 |
ivar-lazzaro | SumitNaiksatam: My patch proposes a different schema approach (the other is trivial) | 18:13 |
rkukura | SSDC | 18:13 |
rkukura | any downside to the trivial option? | 18:14 |
rkukura | creating a separate DB means extra work for deployment tools, etc. | 18:14 |
ivar-lazzaro | rkukura: yes, we still risk that packagers could have some problems with that | 18:14 |
ivar-lazzaro | rkukura: because we are touching a core project DB | 18:14 |
ivar-lazzaro | rkukura: even though we are only adding tables | 18:15 |
ivar-lazzaro | rkukura: the separate schema approach is the safest, no turnarounds whatsoever | 18:15 |
rkukura | We are building a service plugin right now, and we have foriegn keys on the existing core tables, so this just seems like the easier/safer option to me. | 18:15 |
SumitNaiksatam | ivar-lazzaro: you mean the risk is with SSDC? | 18:15 |
ivar-lazzaro | SumitNaiksatam: yeah that's the risk with same schema | 18:15 |
rkukura | A separate schema seems to mean more DB connections from the server, possibility of some DB’s not supporting it, and deployment tools needing to create extra DBs and configure their URLs into neutron.conf. | 18:16 |
ivar-lazzaro | rkukura: DBMSs are made so there's no actual difference from a schema to another... it's just namespacing | 18:16 |
ivar-lazzaro | rkukura: so there are no performance issues in having a different schema | 18:16 |
rkukura | ivar-lazzaro: According to the guy from Red Hat who maintains sqlalchemy, that is the case for mysql, but not necessarily for other DBs | 18:17 |
ivar-lazzaro | rkukura: why do we need new deployment tools? our migration will do the trick | 18:17 |
*** carl_baldwin has quit IRC | 18:17 | |
rkukura | puppet scripts need to create the new DBs, set their owners, put their URLs in neutron’s conf file, ... | 18:17 |
ivar-lazzaro | rkukura: I would say that being safe on the packaging perspective is our top priority... Maybe we can verify that the implementation works with other DBMS | 18:17 |
rkukura | SSDC is much safer from a packaging perspective | 18:18 |
ivar-lazzaro | rkukura: yeah and that happens for any Stackforge Project | 18:18 |
ivar-lazzaro | rkukura: In my experience with RH, adding tables to the existing Neutron DB is actually a problem (backport of apic driver) | 18:19 |
rkukura | This stackforge project is a service plugin that may eventually become part of neuton - I don’t see why we want to add complexity that is not needed. | 18:19 |
ivar-lazzaro | rkukura: if for some reason they add a gbp_endpoint table in Kilo, the migration will fail when you upgrade | 18:19 |
SumitNaiksatam | rkukura: agreed, but it seems that some of the discussions around packaging have indicated that adding tables to the same neutron schema raises eyebrows with the distro folks | 18:19 |
rkukura | The backport issue is due to the single linked list chain of migtrations, right? | 18:19 |
ivar-lazzaro | rkukura: right, but I want to make sure that the separate chain is enough | 18:20 |
ivar-lazzaro | rkukura: I have no preference whatsoever, I just want to make sure our stuff can be packaged and used by people | 18:20 |
ivar-lazzaro | rkukura: so the approach that maximizes this wins for me | 18:20 |
rkukura | Adding a separate DB requires much more code change and support in the deployment tools. I don’t see why we aren’t just going with the simple solution. | 18:20 |
ivar-lazzaro | rkukura: I'm aiming for the safest, not the simpliest | 18:21 |
rkukura | ivar-lazzaro: Do you have examples of how adding a new chain of migrations in the same DB might cause difficulty for deployment tools? | 18:21 |
ivar-lazzaro | rkukura: yes, let's say that in Kilo someone adds a table with the same name as ours | 18:22 |
ivar-lazzaro | rkukura: (even us if we get merged) | 18:22 |
rkukura | Are you 100% sure that managing multiple DB connections in the same neutron process works correctly with greenthreads and all that? | 18:22 |
ivar-lazzaro | rkukura: then the migration Juno -> Kilo will fail because of duplication of tables | 18:22 |
rkukura | ivar-lazzaro: If someone adds a table containing the string “gbp”, I will -2 it | 18:22 |
ivar-lazzaro | rkukura: what if we add it when we merge into neutron? | 18:23 |
SumitNaiksatam | rkukura: ;-) | 18:23 |
ivar-lazzaro | rkukura: I understand we need to take some more time validating that the approach scales and works with as many DBMS as possible | 18:23 |
SumitNaiksatam | rkukura: if we can get an assurance from the distro folks that adding tables to the neutron schema is fine, i think we can go the SSDC route, however i think they have been apprehensive to this point | 18:24 |
ivar-lazzaro | rkukura: but imho it's worth the effort if we are then 100% sure that packagers won't complain | 18:24 |
rkukura | ivar-lazzaro: If we add it, we’ll need to think about what works best for our existing users. Maybe making the upgrade migration check if the tables already exist would solve it. | 18:24 |
ivar-lazzaro | rkukura: that requires a core change in Neutron (even alembic maybe) | 18:24 |
*** peristeri has joined #openstack-meeting-3 | 18:24 | |
rkukura | I think packagers will have more work to do if there are additional DBs to create and configure. | 18:24 |
ivar-lazzaro | SumitNaiksatam: +1, if we make sure that it's ok with them, I'm all for it | 18:25 |
rkukura | ivar-lazzaro: Are you sure a migration cannot be written to check if the table exists? | 18:25 |
SumitNaiksatam | ivar-lazzaro: also, i recall that there was something about there being only a single DB revision table that was causing issues? | 18:25 |
ivar-lazzaro | rkukura: I guess you can do that in the migration file | 18:26 |
ivar-lazzaro | SumitNaiksatam: that is easy to solve, you just add a new versioning table | 18:26 |
*** garyduan has joined #openstack-meeting-3 | 18:26 | |
ivar-lazzaro | rkukura SumitNaiksatam: do we agree that we can go with SSDC if distro guys bless the approach? | 18:27 |
rkukura | Note that I did add a -1 and a comment with my view on this to https://review.openstack.org/#/c/126383/. Thats where we should be having this discussion. | 18:27 |
rkukura | ivar-lazzaro: I’m convinced either will work - just want to figure out which is best from various points of view | 18:28 |
*** cathy_ has joined #openstack-meeting-3 | 18:28 | |
glebo | rkukura: newbie question here: you say "existing users" how many of these do we think we have for GBP? | 18:28 |
ivar-lazzaro | rkukura: actually if we were 100% sure that distro guys are ok I would just go with SSDC | 18:28 |
ivar-lazzaro | rkukura: in fact, it's simpler code and more intuitive approach | 18:29 |
ivar-lazzaro | rkukura: but packaging has the top priority for me | 18:29 |
rkukura | glebo: If and when we get to the point of merging GBP into neutron, I think it will be largely because we’ve got existing users of our stackforge implementation. | 18:29 |
*** pettori has quit IRC | 18:30 | |
SumitNaiksatam | rkukura: ivar-lazzaro: okay lets try to close on this by tomorrow (by checking with the distro/packagin folks) | 18:30 |
*** LouisF has joined #openstack-meeting-3 | 18:30 | |
rkukura | ivar-lazzaro: I’ve also got concerns about whether DSDC works with postgresql, db2, etc. | 18:30 |
ivar-lazzaro | SumitNaiksatam: I don't know many of them :) who can follow up? Maybe we should ask guidance to Ihar | 18:30 |
ivar-lazzaro | rkukura: that has to be validated indeed | 18:31 |
glebo | rkukura: and how many are there today? | 18:31 |
SumitNaiksatam | ivar-lazzaro: yes, i thought we were already talking to him | 18:31 |
rkukura | ivar-lazzaro: no data that it doesn’t, just the sqlalchemy maintain’s advice that DBs differ in this | 18:31 |
ivar-lazzaro | rkukura: I hope it's not that hard | 18:31 |
*** pettori has joined #openstack-meeting-3 | 18:31 | |
SumitNaiksatam | anyone else have thoughts or opinions on this? | 18:32 |
rkukura | glebo: We don’t have enough functionality merged to the stackforge repos yet for their to be any existing users, but hopefully soon ;) | 18:32 |
rkukura | seems like following up with the sqlalchemy maintainer and maybe someone familiar with the puppet scripts would make sense. | 18:33 |
glebo | rkukura: indeed. So, if current user count is low, then maybe user impact is not germaine at this point? | 18:33 |
SumitNaiksatam | glebo: i think rkukura’s point is that we expect users to adopt this once we have this in stackforge | 18:34 |
rkukura | glebo: agreed that we aren’t talking about current users as of today. I think we were talking about at the end of kilo or in the L cycle. | 18:34 |
SumitNaiksatam | glebo: and the expect them keep using this, regardless of where GBP ends up | 18:34 |
SumitNaiksatam | glebo: so our approach needs to be non-disruptive for them (or at least we have to try) | 18:34 |
cathy_ | rkukura: SumitNaiksatam: I have a related question to glebo's quesiton. Currently GBP is developed in Stackforge. Are we still targeting GBP for the Openstack K release? | 18:35 |
SumitNaiksatam | glebo: but your point well taken as well, i guess we need to weigh the pros and cons | 18:35 |
SumitNaiksatam | cathy_: GBP is definitely targeted for K release as well | 18:35 |
glebo | rkukura SumitNaiksatam: so the impact is more from the perspective of the existing OS users who would merge GBP to their existing Neutron deployments, more so than for stackforge GBP users? | 18:35 |
SumitNaiksatam | cathy_: what will be its eventual home is not clear at this point | 18:36 |
rkukura | cathy_: I’m not very hopeful of GBP getting merged into neutron during kilo, but I do expect our repos to be used with kilo. | 18:36 |
SumitNaiksatam | cathy_: for Juno its being release via stackforge | 18:36 |
SumitNaiksatam | *released | 18:36 |
SumitNaiksatam | glebo: at the moment existing users == stackforge GBP users :-) | 18:37 |
SumitNaiksatam | cathy_: did that answer your question? | 18:37 |
rkukura | This brings up the issue of branching within our stackforge repos. At some point, I think we’ll need a branch that tracks stable-juno and another branch that tracks master. | 18:37 |
cathy_ | Is it widely known to users that they can use GBP in Stackforge ? | 18:37 |
SumitNaiksatam | rkukura: yes good point | 18:37 |
glebo | rkukura: +1, sadly so. The priorities for Kilo have been stated VERY clearly by the TC: Neutron stability and closing gap for the eventual deprecation of Nova-networking. Not clear to me that anything outside of those stated goals will get much air time in Kilo | 18:37 |
ivar-lazzaro | rkukura: +1 | 18:37 |
SumitNaiksatam | #action SumitNaiksatam to explore branching for stackforge projects | 18:38 |
cathy_ | SumitNaiksatam: yes. thanks for your answer. | 18:38 |
rkukura | cathy_: our plan is to get the stackforge repos into a useable state before the kilo summit, and do our best their to raise awareness | 18:38 |
s3wong | glebo: I think that was the primary reason for GBP not able to land in Juno as well | 18:38 |
LouisF | SumitNaiksatam: what are plans for gbp meetings at the summit? | 18:39 |
glebo | s3wong: ack. And, depending on progress toward that goal, may be used again in L | 18:39 |
SumitNaiksatam | cathy_: this has been discussed in ML, any reason to believe that users are still not aware of this? | 18:39 |
s3wong | SumitNaiksatam: rkukura: in terms of advertising this during the K-Summit... other than our conference presentation, is there anything else? I mean, do we have a booth? :-) | 18:39 |
SumitNaiksatam | LouisF: yes we will defintiely be meeting | 18:39 |
LouisF | SumitNaiksatam: any sessions on gbp? | 18:40 |
glebo | we're off on a few tangents. Did we yet close the SSDC vs DSDC topic? | 18:40 |
SumitNaiksatam | glebo: good point | 18:40 |
SumitNaiksatam | LouisF: lets circle back to this in the open discussion | 18:40 |
SumitNaiksatam | glebo: we will close on SSDC versus DSDC by tomorrow based on distro/packagers input | 18:41 |
s3wong | glebo: I believe the conclusion there is if same schema is OK with release and packaging folks, we will go with SSDC --- that is my understanding so far | 18:41 |
SumitNaiksatam | #action ivar-lazzaro to send update to ML based on decision by tomorrow | 18:41 |
glebo | s3wong SumitNaiksatam: wfm | 18:41 |
SumitNaiksatam | #topic Resource Mapping driver refactoring proposal | 18:42 |
*** openstack changes topic to "Resource Mapping driver refactoring proposal (Meeting topic: networking_policy)" | 18:42 | |
glebo | s3wong SumitNaiksatam: thx for clarifying | 18:42 |
SumitNaiksatam | ivar-lazzaro: another item for you ;-) | 18:42 |
ivar-lazzaro | SumitNaiksatam: yeee | 18:42 |
SumitNaiksatam | ivar-lazzaro: i believe you have posted a LP BP for this | 18:42 |
ivar-lazzaro | SumitNaiksatam: So I proposed a BP | 18:42 |
SumitNaiksatam | #link https://blueprints.launchpad.net/group-based-policy/+spec/mapping-extension-refactor | 18:42 |
ivar-lazzaro | SumitNaiksatam: #link https://blueprints.launchpad.net/group-based-policy/+spec/mapping-extension-refactor | 18:42 |
ivar-lazzaro | yeah that one | 18:43 |
SumitNaiksatam | ivar-lazzaro: thanks, but i beat you ;-P | 18:43 |
ivar-lazzaro | SumitNaiksatam: ;) | 18:43 |
SumitNaiksatam | ivar-lazzaro: so we will wait for the more detailed spec | 18:43 |
SumitNaiksatam | ivar-lazzaro: in the meanwhile can you please quickly summarize in which direction you are going? | 18:43 |
ivar-lazzaro | sure | 18:43 |
*** carl_baldwin has joined #openstack-meeting-3 | 18:43 | |
rkukura | ivar-lazzaro: This is more radical than I expected - are you suggesting dropping the other mapping attributes, or just moving them to a different extension? | 18:43 |
SumitNaiksatam | ivar-lazzaro: i think the vendor drivers will be interested in knowing about this | 18:43 |
ivar-lazzaro | rkukura: the main extension should be PT->Port | 18:44 |
ivar-lazzaro | rkukura: everything else can be implicit, or different extension | 18:44 |
ivar-lazzaro | So the rationale behind the proposal is that we want to expose a common mapping API | 18:44 |
rkukura | ivar-lazzaro: I was considering including that part in a base-mapping extension in https://blueprints.launchpad.net/group-based-policy/+spec/gbp-extension-drivers | 18:44 |
ivar-lazzaro | that user knows is the common denominator between mapping drivers | 18:44 |
SumitNaiksatam | so ivar-lazzaro are you proposing to remove all other mapping? | 18:45 |
rkukura | ivar-lazzaro: I think this does kind of make sense, especially if policy drivers can have corresponding extension drivers that expose their specific mapping attributes | 18:45 |
ivar-lazzaro | The extension we have now is complex and set a very big constraint on how drivers should map the GBP model | 18:45 |
ivar-lazzaro | Also, showing constructs like Network/Subnet/Router may be not very useful, especially in write mode | 18:46 |
rkukura | But I’m a bit concerned that this kind of blocks any possibility of GBP supporting multiple policy drivers simultaneously in the future. | 18:46 |
ivar-lazzaro | So my proposal is that our main GBP mapping extension (common one) is PT->Port RO | 18:47 |
ivar-lazzaro | this is needed by Nova | 18:47 |
SumitNaiksatam | ivar-lazzaro: but to create the port you need all the other mapping as well, right? | 18:47 |
ivar-lazzaro | and gives the drivers the capability to do whatever mapping they want implicitly, or using extension for explicit mapping as per rkukura proposal | 18:47 |
rkukura | ivar-lazzaro: I think you and I are agreeing pulliing PT->port into a base-mapping extension makes sense. Others? | 18:47 |
* s3wong already confused by PT --- forgot that EP is now policy target... | 18:47 | |
ivar-lazzaro | s3wong: :) | 18:48 |
ivar-lazzaro | SumitNaiksatam: you do, but don't confuse DB with API | 18:48 |
ivar-lazzaro | SumitNaiksatam: you can do whatever you want in the backend without exposing it to the outside world | 18:48 |
rkukura | ivar-lazzaro: I thought your proposal was going to be more around factoring out code from resource_mapping driver that other drivers can use. | 18:48 |
ivar-lazzaro | SumitNaiksatam: and I don't see any compelling need to expose those constructs (besides port) | 18:48 |
SumitNaiksatam | ivar-lazzaro: rkukura: i think you folks have thought about this more than i have, so i need to see the spec or the patch | 18:48 |
SumitNaiksatam | rkukura: that was my initial understanding as well | 18:49 |
ivar-lazzaro | rkukura: that is a direct consequence. We converge in a common mapping extension (used by the reference implementation) and then we add extensions | 18:49 |
SumitNaiksatam | rkukura: seems like we are leapfroggin :-) | 18:49 |
s3wong | rkukura: agreed... that was the item we talked about during the hackathon: which is factoring out implicit driver for EP/EPG/L2P/L3P for a common piece where other policy drivers can use | 18:49 |
ivar-lazzaro | s3wong: that is a different item, that's about our code architecture per se | 18:50 |
ivar-lazzaro | s3wong: what I'm bringing up here is about the minimal API we need to set as GBP "standard" | 18:50 |
rkukura | s3wong: The implicit_policy driver is already totally separate from any specific mapping, so it should be useable with any policy driver. | 18:50 |
ivar-lazzaro | This will help users moving from a driver to another without issues (or even using them together) | 18:50 |
*** bpokorny has joined #openstack-meeting-3 | 18:51 | |
s3wong | ivar-lazzaro: I see --- so you are thinking of making anything other than EP/EPG to be non-mandatory... | 18:51 |
ivar-lazzaro | rkukura: s3wong: the implicit policy driver is fine | 18:51 |
ivar-lazzaro | s3wong: only EP -> Port will be standard | 18:51 |
ivar-lazzaro | s3wong: any other mapping will be decided by the driver itself | 18:51 |
s3wong | ivar-lazzaro: not even EPG, huh? I guess you don't want to always map it to a subnet | 18:51 |
rkukura | Is there a need for an additional BP covering refactoring the resource_mapping driver code, such as the functions to create ports, subnets, networks, etc., into a class that any driver can inherit or compose? | 18:51 |
ivar-lazzaro | s3wong: abstracting is the whole point of GBP in fact ;) | 18:51 |
ivar-lazzaro | rkukura: yes, that is also useful, but we can discuss that separately | 18:52 |
SumitNaiksatam | rkukura: sure, however we need to optimize on the available time as well | 18:52 |
rkukura | So this discussion is on the API. | 18:52 |
ivar-lazzaro | What I'm saying is... Is there a compelling need for exposing the full mapping? | 18:52 |
ivar-lazzaro | If not, we should do the simpler 5% effort solution which covers 90% of use cases | 18:53 |
s3wong | ivar-lazzaro: but that does have an impact on the mapping DB, right? | 18:53 |
rkukura | I’d think that, given the port, a user could navigate to the subnet and network, right? | 18:53 |
ivar-lazzaro | rkukura: correct | 18:53 |
SumitNaiksatam | rkukura: ivar-lazzaro agree | 18:53 |
ivar-lazzaro | rkukura: so if we exclude the "write" capabilities, we don't have any need for exposing a more complex model which constraints future drivers | 18:54 |
SumitNaiksatam | ivar-lazzaro: i guess you are trying to move away from forcing the users of the current mapping extension to do the mapping to routers, subnets, etc. | 18:54 |
rkukura | the PT->port mapping is clearly read-only, right? | 18:54 |
SumitNaiksatam | ivar-lazzaro: and only limit to ports | 18:54 |
ivar-lazzaro | My feeling is that nobody will even even need mapping extensions in a first place! unless they want to provide Write capabilities | 18:54 |
ivar-lazzaro | rkukura: correct | 18:55 |
SumitNaiksatam | ivar-lazzaro: if i recollect one of the original goals was to provide both neutron and GBP APIs concurrently | 18:55 |
SumitNaiksatam | ivar-lazzaro: i am not sure if that holds true, we should check on that | 18:55 |
rkukura | I see little risk in splitting the existing mapping extension into a base-mapping extension that just covers PT->port, and a resource-mapping extension that exposes the rest of the attributes. | 18:55 |
SumitNaiksatam | ivar-lazzaro: okay we need some more offline discussion on this | 18:55 |
s3wong | ivar-lazzaro: it is an interesting take on the idea that some part of mapping driver can be used by other policy-driver; when we set off with mapping driver, it was meant to be a reference implementation | 18:55 |
SumitNaiksatam | we have 5 minutes remaining | 18:55 |
ivar-lazzaro | s3wong: the mapping DB right now is what the main plugin inherits from... And that shouldn't be the case! So a refactor there is needed as well | 18:55 |
SumitNaiksatam | lets circle back to the earlier topic | 18:55 |
SumitNaiksatam | #topic Open Discussion | 18:56 |
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)" | 18:56 | |
SumitNaiksatam | LouisF: you asked about GBP session in the Paris summit | 18:56 |
ivar-lazzaro | s3wong: but that's a problem we have anyway if we want to give drivers the ability to map their own stuff without writing a new Plugin | 18:56 |
rkukura | ivar-lazzaro: My BP will move the build in mapping extension to an extension driver. | 18:56 |
s3wong | ivar-lazzaro: and of course now you are taking it to the extreme where you assume most vendor policy-driver will be using some parts of mapping driver | 18:56 |
LouisF | SumitNaiksatam: yes | 18:56 |
ivar-lazzaro | rkukura: nice! So our combined effort will solve this problem and give a much nicer API | 18:56 |
SumitNaiksatam | so we have a conference session/presentation: #link https://openstacksummitnovember2014paris.sched.org/event/3381db355f042c612c11960a588e31de | 18:57 |
rkukura | ivar-lazzaro: I kind of agree, but we do need to get the rest of the team thinking about this, which I think we’ve accomplished | 18:57 |
ivar-lazzaro | s3wong: No that's the whole point, vendor drivers will most certainly only need PT->Port mapping | 18:57 |
SumitNaiksatam | LouisF: was your question targeted at a desgin summit session? | 18:57 |
ivar-lazzaro | s3wong: and that's all we have to give them | 18:57 |
s3wong | ivar-lazzaro: rkukura: I agree that if the intent is to let 3rd party policy driver to leverage mapping driver, the ML2 like framework thing rkukura proposes seems like a good step | 18:57 |
LouisF | both | 18:57 |
SumitNaiksatam | ivar-lazzaro: rkukura s3wong: can we continue the discussion after the meeting, we have changed the topic | 18:57 |
ivar-lazzaro | s3wong: with this proposal I'm in fact enhancing the flexibility of future drivers | 18:57 |
SumitNaiksatam | LouisF: so as far the design summit session is concerned, that is not decided yet | 18:58 |
SumitNaiksatam | LouisF: the wishlist for Neutron looks like this: #link https://etherpad.openstack.org/p/kilo-neutron-summit-topics | 18:58 |
SumitNaiksatam | LouisF: we have also requested a session for GBP in the “other projects” track but we are not sure we will get that | 18:58 |
s3wong | SumitNaiksatam: and my understanding is ... even the pods are very limited in time-sharing in this summit | 18:58 |
SumitNaiksatam | s3wong: okay | 18:59 |
s3wong | SumitNaiksatam: I heard somewhere (from mestery, I believe) that Neutron pods will only be available on Friday? | 18:59 |
SumitNaiksatam | LouisF: short of anything else, i propose that we will at least have an uncoference session | 18:59 |
SumitNaiksatam | s3wong: yes the schedule seems to suggest that | 18:59 |
SumitNaiksatam | *unconference | 18:59 |
LouisF | SumitNaiksatam: thx | 18:59 |
SumitNaiksatam | LouisF: and of course open to other suggestions/ideas | 19:00 |
s3wong | Most likely, we need to grab a room somewhere that isn't pod/Neutron related, and meet at a mutual time there | 19:00 |
SumitNaiksatam | anyone else have any other thoughts on these logistics? | 19:00 |
SumitNaiksatam | s3wong: yes | 19:00 |
SumitNaiksatam | and this is going to be the case for a lot of other features/new projects | 19:00 |
glebo | ivar-lazzaro s3wong rkukura: a summary of where you all converged on the mapping topic would be great, either here or in subsequent room | 19:00 |
SumitNaiksatam | since the agenad is heavily oversubscribed | 19:00 |
rkukura | s3wong: We need to check on that. My understanding was the pods were available all week, but most of friday was dedicated to informal discussions rather than scheduled sessions | 19:00 |
SumitNaiksatam | glebo: yes, this will be posted to the ML | 19:01 |
ivar-lazzaro | glebo: I'll propose a spec very soon and we can continue the discussion there | 19:01 |
s3wong | rkukura: OK? because if not, that would be even worse than the good old unconference days | 19:01 |
SumitNaiksatam | #action ivar-lazzaro rkukura to send update to ML on #link https://blueprints.launchpad.net/group-based-policy/+spec/mapping-extension-refactor and #link https://blueprints.launchpad.net/group-based-policy/+spec/gbp-extension-drivers | 19:01 |
rkukura | glebo: And I’ll be posting the spec for https://blueprints.launchpad.net/group-based-policy/+spec/gbp-extension-drivers | 19:02 |
s3wong | rkukura: but it seems like there are some dedicated "cross-projects" stuff over the first few days for the pod area? | 19:02 |
SumitNaiksatam | okay we are a couple of minutes over | 19:02 |
SumitNaiksatam | anything else that anyone wants to urgently bring up? | 19:02 |
*** bpokorny_ has joined #openstack-meeting-3 | 19:02 | |
s3wong | SumitNaiksatam: we should start working on the presentation via email? | 19:02 |
s3wong | SumitNaiksatam: now that banix will likely not join us... | 19:03 |
SumitNaiksatam | s3wong: yes, i have an AI to add the policy summit slides to mandeep’s earlier slides | 19:03 |
SumitNaiksatam | #action SumitNaiksatam to update presentation slides | 19:03 |
s3wong | SumitNaiksatam: OK | 19:03 |
SumitNaiksatam | s3wong: thanks for the reminder! | 19:03 |
SumitNaiksatam | alright, lets call it a wrap (we can continue the discussion in #openstack-gbp) | 19:04 |
SumitNaiksatam | thanks all for joining | 19:04 |
SumitNaiksatam | bye | 19:04 |
SumitNaiksatam | #endmeeting | 19:04 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 19:04 | |
openstack | Meeting ended Thu Oct 9 19:04:30 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:04 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-10-09-18.01.html | 19:04 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-10-09-18.01.txt | 19:04 |
openstack | Log: http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-10-09-18.01.log.html | 19:04 |
ivar-lazzaro | bye | 19:04 |
rkukura | bye | 19:04 |
s3wong | bye (lunch-time) | 19:04 |
*** bpokorny has quit IRC | 19:05 | |
*** glebo has left #openstack-meeting-3 | 19:07 | |
*** mwagner_lap has quit IRC | 19:08 | |
*** BrianB_ has quit IRC | 19:09 | |
*** jcoufal has joined #openstack-meeting-3 | 19:10 | |
*** LouisF has quit IRC | 19:12 | |
*** lhcheng has joined #openstack-meeting-3 | 19:15 | |
*** jacalcat has joined #openstack-meeting-3 | 19:18 | |
*** carl_baldwin has quit IRC | 19:19 | |
*** hemanthravi has quit IRC | 19:21 | |
*** cbader has quit IRC | 19:22 | |
*** seizadi has joined #openstack-meeting-3 | 19:25 | |
*** carl_baldwin has joined #openstack-meeting-3 | 19:26 | |
*** hemanthravi has joined #openstack-meeting-3 | 19:30 | |
*** jacalcat has left #openstack-meeting-3 | 19:41 | |
*** david-lyle is now known as david-lyle_afk | 19:47 | |
*** yyywu has quit IRC | 19:47 | |
*** lhcheng has quit IRC | 19:48 | |
*** lhcheng has joined #openstack-meeting-3 | 19:48 | |
*** seizadi has quit IRC | 19:51 | |
*** pettori has quit IRC | 19:52 | |
*** MaxV has joined #openstack-meeting-3 | 19:53 | |
*** lhcheng has quit IRC | 19:53 | |
*** sigmavirus24 has left #openstack-meeting-3 | 19:54 | |
*** ivar-laz_ has joined #openstack-meeting-3 | 19:55 | |
*** Longgeek has quit IRC | 19:55 | |
*** ivar-lazzaro has quit IRC | 19:57 | |
*** hemanthravi has quit IRC | 20:05 | |
*** jcoufal has quit IRC | 20:13 | |
*** ivar-laz_ has quit IRC | 20:15 | |
*** jacalcat has joined #openstack-meeting-3 | 20:22 | |
*** matrohon has joined #openstack-meeting-3 | 20:25 | |
*** lhcheng has joined #openstack-meeting-3 | 20:26 | |
*** pettori has joined #openstack-meeting-3 | 20:30 | |
*** otherwiseguy has quit IRC | 20:34 | |
*** alexpilotti has quit IRC | 20:35 | |
*** lhcheng has quit IRC | 20:38 | |
*** lhcheng has joined #openstack-meeting-3 | 20:38 | |
*** lhcheng has quit IRC | 20:43 | |
*** david-lyle_afk is now known as david-lyle | 20:53 | |
*** seizadi has joined #openstack-meeting-3 | 20:54 | |
*** jcoufal has joined #openstack-meeting-3 | 20:58 | |
*** alexsyip has joined #openstack-meeting-3 | 20:58 | |
*** carl_baldwin has quit IRC | 21:02 | |
*** jacalcat has left #openstack-meeting-3 | 21:02 | |
*** otherwiseguy has joined #openstack-meeting-3 | 21:04 | |
*** julim has quit IRC | 21:04 | |
*** markmcclain has quit IRC | 21:05 | |
*** jacalcat1 has joined #openstack-meeting-3 | 21:06 | |
*** bpokorny has joined #openstack-meeting-3 | 21:07 | |
*** bpokorny_ has quit IRC | 21:09 | |
*** carl_baldwin has joined #openstack-meeting-3 | 21:11 | |
*** ttrifonov is now known as ttrifonov_zZzz | 21:13 | |
*** ivar-lazzaro has joined #openstack-meeting-3 | 21:14 | |
*** HenryG has quit IRC | 21:14 | |
*** jgrimm is now known as zz_jgrimm | 21:17 | |
*** lhcheng has joined #openstack-meeting-3 | 21:20 | |
*** jcoufal has quit IRC | 21:29 | |
*** mfer has quit IRC | 21:32 | |
*** matrohon has quit IRC | 21:33 | |
*** lhcheng has quit IRC | 21:36 | |
*** lhcheng has joined #openstack-meeting-3 | 21:36 | |
*** dboik has quit IRC | 21:40 | |
*** lhcheng has quit IRC | 21:41 | |
*** jacalcat1 has left #openstack-meeting-3 | 21:41 | |
*** pettori has quit IRC | 21:44 | |
*** otherwiseguy has quit IRC | 21:49 | |
*** Swami has quit IRC | 22:04 | |
*** bpokorny_ has joined #openstack-meeting-3 | 22:04 | |
*** jacalcat has joined #openstack-meeting-3 | 22:04 | |
*** cathy_ has quit IRC | 22:05 | |
*** jacalcat has left #openstack-meeting-3 | 22:05 | |
*** bpokorny has quit IRC | 22:07 | |
*** Sukhdev has joined #openstack-meeting-3 | 22:09 | |
*** dboik has joined #openstack-meeting-3 | 22:25 | |
*** MaxV has quit IRC | 22:38 | |
*** peristeri has quit IRC | 22:39 | |
*** shwetaap has quit IRC | 22:40 | |
*** shwetaap has joined #openstack-meeting-3 | 22:41 | |
*** Rajeev has quit IRC | 22:41 | |
*** shwetaap has quit IRC | 22:45 | |
*** ttrifonov_zZzz is now known as ttrifonov | 22:57 | |
*** thangp has quit IRC | 22:58 | |
*** HenryG has joined #openstack-meeting-3 | 23:07 | |
*** MaxV has joined #openstack-meeting-3 | 23:09 | |
*** MaxV has quit IRC | 23:13 | |
*** igordcard has quit IRC | 23:16 | |
*** bpokorny has joined #openstack-meeting-3 | 23:22 | |
*** bpokorny_ has quit IRC | 23:24 | |
*** flaper87 is now known as flaper87|afk | 23:25 | |
*** bpokorny_ has joined #openstack-meeting-3 | 23:31 | |
*** bpokorny has quit IRC | 23:34 | |
*** hurgleburgler has quit IRC | 23:36 | |
*** david-lyle has quit IRC | 23:40 | |
*** zz_jgrimm is now known as jgrimm | 23:43 | |
*** carl_baldwin has quit IRC | 23:46 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!