Wednesday, 2014-05-21

*** michael-yu has quit IRC00:05
*** MarkAtwood has joined #openstack-meeting-alt00:06
*** michael-yu has joined #openstack-meeting-alt00:07
*** mattgriffin has quit IRC00:09
*** Sukhdev has joined #openstack-meeting-alt00:10
*** jergerber has quit IRC00:11
*** aclark_ has quit IRC00:14
*** sarob has quit IRC00:16
*** nati_uen_ has joined #openstack-meeting-alt00:21
*** MarkAtwood has quit IRC00:23
*** nati_ueno has quit IRC00:24
*** arnaud_ has quit IRC00:26
*** IlyaE has joined #openstack-meeting-alt00:28
*** richm has quit IRC00:32
*** arnaud_ has joined #openstack-meeting-alt00:32
*** michael-yu has quit IRC00:33
*** mattgriffin has joined #openstack-meeting-alt00:37
*** HenryG_ has joined #openstack-meeting-alt00:37
*** HenryG_ has quit IRC00:38
*** jecarey has joined #openstack-meeting-alt00:38
*** eguz has quit IRC00:40
*** eghobo has joined #openstack-meeting-alt00:41
*** mattgrif_ has joined #openstack-meeting-alt00:41
*** mattgriffin has quit IRC00:41
*** rbenali has joined #openstack-meeting-alt00:42
*** rbenali has left #openstack-meeting-alt00:42
*** MarkAtwood has joined #openstack-meeting-alt00:46
*** MarkAtwood has quit IRC00:47
*** ramashri has quit IRC00:50
*** xarses has quit IRC00:50
*** rmoe has quit IRC00:51
*** rand738 has quit IRC00:54
*** rand738 has joined #openstack-meeting-alt00:54
*** tomblank has quit IRC01:04
*** rmoe has joined #openstack-meeting-alt01:12
*** eghobo has quit IRC01:15
*** amytron has joined #openstack-meeting-alt01:15
*** resker has joined #openstack-meeting-alt01:15
*** esker has quit IRC01:18
*** baoli has joined #openstack-meeting-alt01:20
*** amcrn_ has quit IRC01:20
*** tdruiva has joined #openstack-meeting-alt01:20
*** banix has joined #openstack-meeting-alt01:21
*** nati_uen_ has quit IRC01:21
*** jjmb has joined #openstack-meeting-alt01:22
*** amcrn has joined #openstack-meeting-alt01:27
*** nati_ueno has joined #openstack-meeting-alt01:28
*** nati_ueno has quit IRC01:29
*** otherwiseguy has joined #openstack-meeting-alt01:29
*** xarses has joined #openstack-meeting-alt01:30
*** nati_ueno has joined #openstack-meeting-alt01:30
*** Barker has joined #openstack-meeting-alt01:36
*** aurynn has left #openstack-meeting-alt01:38
*** nati_ueno has quit IRC01:38
*** n0ano has quit IRC01:40
*** shakamunyi has quit IRC01:45
*** cjellick_ has joined #openstack-meeting-alt01:46
*** ericgoncz has quit IRC01:46
*** cjellick has quit IRC01:48
*** cjellick_ has quit IRC01:50
*** eankutse1 has joined #openstack-meeting-alt01:51
*** noslzzp has joined #openstack-meeting-alt01:52
*** terryw has joined #openstack-meeting-alt01:53
*** otherwiseguy has quit IRC01:53
*** eankutse has quit IRC01:54
*** eankutse1 has quit IRC01:55
*** shakamunyi has joined #openstack-meeting-alt01:59
*** jjmb has quit IRC02:00
*** terryw has quit IRC02:00
*** Barker has quit IRC02:02
*** Sukhdev has quit IRC02:05
*** shakamunyi has quit IRC02:05
*** markwash has quit IRC02:05
*** otherwiseguy has joined #openstack-meeting-alt02:11
*** baoli has quit IRC02:14
*** sankarshan is now known as sankarshan_away02:18
*** eankutse has joined #openstack-meeting-alt02:21
*** markwash has joined #openstack-meeting-alt02:23
*** chuckC has joined #openstack-meeting-alt02:28
*** eankutse has quit IRC02:29
*** baoli has joined #openstack-meeting-alt02:31
*** amcrn has quit IRC02:35
*** gyee has quit IRC02:36
*** rand738 has quit IRC02:39
*** rand738 has joined #openstack-meeting-alt02:41
*** james_li has joined #openstack-meeting-alt02:44
*** rwsu has quit IRC02:44
*** mberlin has quit IRC02:45
*** balajiiyer has joined #openstack-meeting-alt02:47
*** cjellick has joined #openstack-meeting-alt02:47
*** nelsnelson has quit IRC02:47
*** tomblank has joined #openstack-meeting-alt02:51
*** cjellick has quit IRC02:54
*** james_li has quit IRC02:54
*** baojg has joined #openstack-meeting-alt02:55
*** markwash has quit IRC02:57
*** kenhui has joined #openstack-meeting-alt02:58
*** mberlin has joined #openstack-meeting-alt03:01
*** baojg has quit IRC03:01
*** baojg has joined #openstack-meeting-alt03:02
*** dims_ has joined #openstack-meeting-alt03:03
*** mattgrif_ has quit IRC03:03
*** arnaud_ has quit IRC03:04
*** baoli has quit IRC03:05
*** harlowja is now known as harlowja_away03:05
*** caleb_ has joined #openstack-meeting-alt03:05
*** cjellick has joined #openstack-meeting-alt03:05
*** baojg_ has joined #openstack-meeting-alt03:07
*** rand738 has quit IRC03:08
*** rand738 has joined #openstack-meeting-alt03:08
*** baojg_ has quit IRC03:09
*** baojg has quit IRC03:09
*** baojg has joined #openstack-meeting-alt03:10
*** balajiiyer has quit IRC03:14
*** amytron has quit IRC03:16
*** baojg_ has joined #openstack-meeting-alt03:17
*** mattgriffin has joined #openstack-meeting-alt03:17
*** baojg has quit IRC03:20
*** kenhui has quit IRC03:21
*** vkmc has quit IRC03:25
*** sankarshan_away is now known as sankarshan03:26
*** ramishra has joined #openstack-meeting-alt03:33
*** kenhui has joined #openstack-meeting-alt03:35
*** otherwiseguy has quit IRC03:39
*** banix has quit IRC03:41
*** caleb_ has quit IRC03:44
*** caleb_ has joined #openstack-meeting-alt03:45
*** eghobo has joined #openstack-meeting-alt03:45
*** nosnos has joined #openstack-meeting-alt03:48
*** kenhui1 has joined #openstack-meeting-alt03:50
*** kenhui has quit IRC03:51
*** mattgriffin has quit IRC03:52
*** arnaud_ has joined #openstack-meeting-alt03:59
*** amytron has joined #openstack-meeting-alt04:03
*** jaypipes has joined #openstack-meeting-alt04:11
*** colinmcnamara has joined #openstack-meeting-alt04:15
*** akuznetsov has joined #openstack-meeting-alt04:21
*** Sukhdev has joined #openstack-meeting-alt04:21
*** colinmcnamara has quit IRC04:23
*** dims_ has quit IRC04:29
*** adrian_otto has joined #openstack-meeting-alt04:29
*** morganfainberg is now known as morganfainberg_Z04:42
*** michael-yu has joined #openstack-meeting-alt04:45
*** amytron has quit IRC04:52
*** tomblank has quit IRC04:52
*** baojg has joined #openstack-meeting-alt04:59
*** baojg_ has quit IRC05:00
*** baojg has quit IRC05:00
*** ramishra has quit IRC05:01
*** yogeshmehra has joined #openstack-meeting-alt05:01
*** igor_ has quit IRC05:02
*** kenhui has joined #openstack-meeting-alt05:04
*** igor has joined #openstack-meeting-alt05:06
*** kenhui2 has joined #openstack-meeting-alt05:07
*** kenhui has quit IRC05:07
*** betsy has quit IRC05:07
*** kenhui has joined #openstack-meeting-alt05:07
*** ramishra has joined #openstack-meeting-alt05:08
*** kenhui1 has quit IRC05:08
*** kenhui2 has quit IRC05:11
*** Sukhdev has quit IRC05:13
*** bltavares|away has joined #openstack-meeting-alt05:16
*** bltavares|away is now known as bltavares05:17
*** denis_makogon has joined #openstack-meeting-alt05:20
*** yamamoto_ has joined #openstack-meeting-alt05:21
*** michael-yu has quit IRC05:27
*** kenhui has quit IRC05:27
*** michael-yu has joined #openstack-meeting-alt05:34
*** _nadya_ has joined #openstack-meeting-alt05:46
*** yogeshmehra has quit IRC05:50
*** cjellick has quit IRC05:54
*** cjellick has joined #openstack-meeting-alt05:54
*** jprovazn has joined #openstack-meeting-alt05:55
*** jtomasek has joined #openstack-meeting-alt06:00
*** yogeshmehra has joined #openstack-meeting-alt06:00
*** jtomasek has quit IRC06:05
*** resker has quit IRC06:08
*** esker has joined #openstack-meeting-alt06:08
*** _nadya_ has quit IRC06:08
*** jtomasek has joined #openstack-meeting-alt06:14
*** ttrumm has joined #openstack-meeting-alt06:19
*** _nadya_ has joined #openstack-meeting-alt06:22
*** colinmcnamara has joined #openstack-meeting-alt06:33
*** caleb_` has joined #openstack-meeting-alt06:37
*** caleb_` has quit IRC06:39
*** caleb_ has quit IRC06:40
*** michael-yu has quit IRC06:51
*** ttrumm has quit IRC06:58
*** ttrumm has joined #openstack-meeting-alt06:59
*** adrian_otto has quit IRC07:00
*** flaper87|afk is now known as flaper8707:02
*** artem_panchenko has joined #openstack-meeting-alt07:03
*** artem_panchenko has left #openstack-meeting-alt07:03
*** jcoufal has joined #openstack-meeting-alt07:05
*** tdruiva has quit IRC07:09
*** harlowja_away has quit IRC07:10
*** resker has joined #openstack-meeting-alt07:11
*** eghobo has quit IRC07:12
*** luqas has joined #openstack-meeting-alt07:12
*** _nadya_ has quit IRC07:14
*** esker has quit IRC07:14
*** colinmcnamara has joined #openstack-meeting-alt07:18
*** _nadya_ has joined #openstack-meeting-alt07:25
*** ttrumm has quit IRC07:27
*** ttrumm has joined #openstack-meeting-alt07:28
*** jgallard has joined #openstack-meeting-alt07:31
*** lsmola has quit IRC07:39
*** lsmola has joined #openstack-meeting-alt07:39
*** denis_makogon has quit IRC07:43
*** arnaud_ has quit IRC07:45
*** yogeshmehra has quit IRC07:45
*** jprovazn has quit IRC07:55
*** jprovazn has joined #openstack-meeting-alt08:00
*** jprovazn has quit IRC08:12
*** IlyaE has quit IRC08:12
*** derekh_ has joined #openstack-meeting-alt08:14
*** jprovazn has joined #openstack-meeting-alt08:17
*** nacim has joined #openstack-meeting-alt08:18
*** jamie_h has joined #openstack-meeting-alt08:31
*** safchain has joined #openstack-meeting-alt08:32
*** ramishra has quit IRC08:40
*** ramishra has joined #openstack-meeting-alt08:40
*** annashen has quit IRC08:41
*** isviridov is now known as isviridov|away08:46
*** arnaud_ has joined #openstack-meeting-alt08:47
*** annashen has joined #openstack-meeting-alt08:49
*** arnaud_ has quit IRC08:51
*** aostapenko has left #openstack-meeting-alt09:01
*** andreaf has joined #openstack-meeting-alt09:07
*** jcoufal has quit IRC09:10
*** sankarshan is now known as sankarshan_away09:19
*** denis_makogon has joined #openstack-meeting-alt09:22
*** colinmcnamara has joined #openstack-meeting-alt09:48
*** dguitarbite has joined #openstack-meeting-alt09:50
*** ttrumm has quit IRC09:57
*** mberlin has quit IRC10:10
*** coolsvap|afk is now known as coolsvap10:11
*** jcoufal has joined #openstack-meeting-alt10:15
*** jgallard has quit IRC10:18
*** ttrumm has joined #openstack-meeting-alt10:19
*** _nadya_ has quit IRC10:22
*** yamamoto_ has quit IRC10:24
*** ttrumm has quit IRC10:35
*** jcoufal has quit IRC10:39
*** jcoufal has joined #openstack-meeting-alt10:40
*** nacim has quit IRC10:44
*** colinmcnamara has joined #openstack-meeting-alt10:48
*** dshulyak has quit IRC10:52
*** nacim has joined #openstack-meeting-alt10:58
*** colinmcnamara has joined #openstack-meeting-alt11:03
*** coolsvap is now known as coolsvap|afk11:07
*** coolsvap|afk is now known as coolsvap11:10
*** banix has joined #openstack-meeting-alt11:15
*** nosnos has quit IRC11:16
*** coolsvap is now known as coolsvap|afk11:23
*** mwagner_lap has quit IRC11:33
*** eankutse has joined #openstack-meeting-alt11:35
*** jgallard has joined #openstack-meeting-alt11:37
*** banix has quit IRC11:38
*** ramishra has quit IRC11:38
*** ramishra has joined #openstack-meeting-alt11:39
*** coolsvap|afk is now known as coolsvap11:41
*** jgallard has quit IRC11:46
*** dshulyak has joined #openstack-meeting-alt11:47
*** colinmcnamara has joined #openstack-meeting-alt11:48
*** vkmc has joined #openstack-meeting-alt11:52
*** vkmc has joined #openstack-meeting-alt11:52
*** jjmb has joined #openstack-meeting-alt11:53
*** sankarshan_away is now known as sankarshan11:53
*** baoli has joined #openstack-meeting-alt11:55
*** satish has joined #openstack-meeting-alt11:56
*** coolsvap is now known as coolsvap|afk12:00
*** colinmcnamara has joined #openstack-meeting-alt12:03
*** noslzzp has quit IRC12:06
*** eankutse has quit IRC12:10
*** tomblank has joined #openstack-meeting-alt12:12
*** pdmars has joined #openstack-meeting-alt12:12
*** dguitarbite has quit IRC12:13
*** dguitarbite has joined #openstack-meeting-alt12:14
*** dguitarbite has quit IRC12:14
*** dguitarbite has joined #openstack-meeting-alt12:14
*** luqas has quit IRC12:14
*** pdmars has quit IRC12:17
*** tomblank has quit IRC12:29
*** jdob has joined #openstack-meeting-alt12:31
*** pdmars has joined #openstack-meeting-alt12:32
*** colinmcnamara has joined #openstack-meeting-alt12:33
*** pdmars has quit IRC12:33
*** pdmars has joined #openstack-meeting-alt12:33
*** pdmars has quit IRC12:34
*** denis_makogon has quit IRC12:36
*** denis_makogon has joined #openstack-meeting-alt12:37
*** flaper87 is now known as flaper87|afk12:38
*** pdmars has joined #openstack-meeting-alt12:43
*** HenryG has joined #openstack-meeting-alt12:49
*** tdruiva has joined #openstack-meeting-alt12:49
*** mwagner_lap has joined #openstack-meeting-alt12:50
*** jecarey has quit IRC12:52
*** dprince has joined #openstack-meeting-alt12:56
*** luqas has joined #openstack-meeting-alt12:59
*** resker has quit IRC13:01
*** satish_ has joined #openstack-meeting-alt13:01
*** esker has joined #openstack-meeting-alt13:02
*** mfer has joined #openstack-meeting-alt13:02
*** satish has quit IRC13:03
*** lisa_ has joined #openstack-meeting-alt13:07
*** lisa_ has quit IRC13:15
*** lisa_ has joined #openstack-meeting-alt13:16
*** xuhanp has joined #openstack-meeting-alt13:17
*** jeckersb_gone is now known as jeckersb13:18
*** lisam has joined #openstack-meeting-alt13:19
*** lisa_ has quit IRC13:21
*** _nadya_ has joined #openstack-meeting-alt13:22
*** _nadya_ has quit IRC13:26
*** julim has joined #openstack-meeting-alt13:27
*** eankutse has joined #openstack-meeting-alt13:29
*** satish has joined #openstack-meeting-alt13:30
*** satish_ has quit IRC13:33
*** zz_gondoi is now known as gondoi13:34
*** dhellmann_ is now known as dhellmann13:35
*** eankutse has quit IRC13:37
*** eankutse has joined #openstack-meeting-alt13:37
*** caleb_ has joined #openstack-meeting-alt13:38
*** balajiiyer has joined #openstack-meeting-alt13:40
*** ramishra has quit IRC13:43
*** caleb_ has quit IRC13:43
*** caleb_ has joined #openstack-meeting-alt13:44
*** yamamoto has joined #openstack-meeting-alt13:47
*** dianefleming has joined #openstack-meeting-alt13:50
*** yamamoto has quit IRC13:52
*** AJaeger has joined #openstack-meeting-alt13:53
*** markwash has joined #openstack-meeting-alt13:54
*** _nadya_ has joined #openstack-meeting-alt13:56
*** Barker has joined #openstack-meeting-alt13:56
*** otherwiseguy has joined #openstack-meeting-alt13:59
*** caleb_ has quit IRC14:00
*** caleb_ has joined #openstack-meeting-alt14:02
*** cjellick has quit IRC14:03
*** Obulpathi has joined #openstack-meeting-alt14:03
*** dianefleming has left #openstack-meeting-alt14:03
*** yanndegat has joined #openstack-meeting-alt14:03
*** Sam-I-Am has joined #openstack-meeting-alt14:03
*** terryw has joined #openstack-meeting-alt14:03
*** sld has joined #openstack-meeting-alt14:04
*** dianefleming has joined #openstack-meeting-alt14:04
*** yanndegat_away has quit IRC14:04
*** Obulpathi has quit IRC14:04
*** shaunm has joined #openstack-meeting-alt14:04
*** Obulpathi has joined #openstack-meeting-alt14:05
*** otherwiseguy has quit IRC14:06
*** noslzzp has joined #openstack-meeting-alt14:06
*** Sam-I-Am has left #openstack-meeting-alt14:07
*** yjiang51 has joined #openstack-meeting-alt14:08
*** yanndegat has quit IRC14:08
*** tdruiva has quit IRC14:09
*** amytron has joined #openstack-meeting-alt14:10
*** tdruiva has joined #openstack-meeting-alt14:10
*** rwsu has joined #openstack-meeting-alt14:15
*** balajiiyer has left #openstack-meeting-alt14:17
*** nelsnelson has joined #openstack-meeting-alt14:18
*** _nadya_ has quit IRC14:21
*** _nadya_ has joined #openstack-meeting-alt14:22
*** nelsnelson has quit IRC14:23
*** nelsnelson has joined #openstack-meeting-alt14:23
*** luizfar has joined #openstack-meeting-alt14:24
*** jecarey has joined #openstack-meeting-alt14:29
*** gokrokve has joined #openstack-meeting-alt14:29
*** ramishra has joined #openstack-meeting-alt14:30
*** shakamunyi has joined #openstack-meeting-alt14:31
*** denis_makogon has quit IRC14:32
*** kgriffs|afk is now known as kgriffs14:32
*** jgallard has joined #openstack-meeting-alt14:34
*** cjellick has joined #openstack-meeting-alt14:35
*** cjellick has quit IRC14:35
*** cjellick has joined #openstack-meeting-alt14:36
*** kevinconway has joined #openstack-meeting-alt14:36
*** david-lyle has joined #openstack-meeting-alt14:37
*** yjiang51 has quit IRC14:38
*** markmcclain has joined #openstack-meeting-alt14:40
*** markmcclain has quit IRC14:40
*** markmcclain has joined #openstack-meeting-alt14:40
*** james_li has joined #openstack-meeting-alt14:42
*** tomblank has joined #openstack-meeting-alt14:44
*** jgallard has quit IRC14:45
*** yamahata has joined #openstack-meeting-alt14:46
*** arnaud has joined #openstack-meeting-alt14:49
*** andreaf has quit IRC14:52
*** Swami has joined #openstack-meeting-alt14:52
*** coolsvap|afk is now known as coolsvap14:54
*** AJaeger has left #openstack-meeting-alt14:55
*** carl_baldwin has joined #openstack-meeting-alt14:58
*** isviridov|away is now known as isviridov14:59
*** banix has joined #openstack-meeting-alt14:59
Swami#carl hi15:00
Swamibanix: hi15:00
xuhanphello15:00
Swamixuhanp: hi15:00
banixSwami: hi15:00
*** caleb_ has quit IRC15:00
*** IlyaE has joined #openstack-meeting-alt15:01
Swami#startmeeting distributed_virtual_router15:01
openstackMeeting started Wed May 21 15:01:08 2014 UTC and is due to finish in 60 minutes.  The chair is Swami. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: distributed_virtual_router)"15:01
openstackThe meeting name has been set to 'distributed_virtual_router'15:01
SwamiHi Folks,15:01
Swamihope everyone enjoyed the summit15:01
carl_baldwinSwami: hi15:01
*** betsy has joined #openstack-meeting-alt15:02
*** viveknarasimhan has joined #openstack-meeting-alt15:02
Swamiviveknarasimhan: hi15:02
Swami#topic Agenda15:02
*** openstack changes topic to "Agenda (Meeting topic: distributed_virtual_router)"15:02
*** mrsmith has joined #openstack-meeting-alt15:02
*** asomya has joined #openstack-meeting-alt15:02
Swamimrsmith: hi15:03
Swamibetsy: hi15:03
Swamiasomya: hi15:03
viveknarasimhanhi15:03
SwamiDVR Progress Update15:03
asomyahello15:03
*** devvesa has joined #openstack-meeting-alt15:03
*** pcm_ has joined #openstack-meeting-alt15:03
Swami#topic DVR Progress Update15:03
*** openstack changes topic to "DVR Progress Update (Meeting topic: distributed_virtual_router)"15:03
*** mberlin has joined #openstack-meeting-alt15:03
mrsmithSwami: hi15:03
*** beyounn has joined #openstack-meeting-alt15:04
SwamiLast week we were all in the summit and did not make any progress forward15:04
*** gokrokve has quit IRC15:04
*** gokrokve has joined #openstack-meeting-alt15:04
*** gokrokve has quit IRC15:04
SwamiWe are currently working on fixing a bulk of unit test issues that we are facing with the L3-plugin15:04
*** shaunm has left #openstack-meeting-alt15:04
*** yisun has joined #openstack-meeting-alt15:04
mrsmithSwami: all? :)15:04
SwamiSince it touches almost all the plugins we are addressing the unit test issues that might eat a lot of out time.15:05
mrsmithgood progress was made by some on the icehouse-ga merge15:05
*** beyounn has quit IRC15:05
Swami#topic DVR Extension for L315:05
*** phil_h has joined #openstack-meeting-alt15:05
*** openstack changes topic to "DVR Extension for L3 (Meeting topic: distributed_virtual_router)"15:05
*** nacim has quit IRC15:05
SwamiBased on the summit discussion, I had a chat with Mark McClain and Kyle regarding the DB model design for the DVR15:06
SwamiInstead of creating a separate attribute extension for the "Distributed" flag in "routers" table, we decided to move the "distributed" flag right into the "routers" table and keep this flag to "false" by default.15:07
*** dianefleming has quit IRC15:07
*** TravT has joined #openstack-meeting-alt15:07
SwamiThat way we don't need to maintain this attribute going forward.15:08
SwamiBased on the above mentioned change I will be refactoring the existing code and will be also addressing the Unit test cases for this.15:08
SwamiHope this is not an issue for any of the members here.15:09
Swami#topic L3 Update15:10
*** openstack changes topic to "L3 Update (Meeting topic: distributed_virtual_router)"15:10
Swamimrsmith: any updates15:10
*** gondoi is now known as zz_gondoi15:10
mrsmithjust that we got basic E/W functionality working on icehouse-ga15:10
mrsmithn/s needs more refactoring (again)15:11
*** Barker has quit IRC15:11
*** luizfar has quit IRC15:11
*** zz_gondoi is now known as gondoi15:11
mrsmithand as you say, we have a "debt" of unit tests failures that we need to refactor/fix15:11
*** adrian_otto has joined #openstack-meeting-alt15:11
*** luizfar has joined #openstack-meeting-alt15:11
Swamimrsmith: Thanks for the update15:11
Swami#topic L2 Agent15:12
*** openstack changes topic to "L2 Agent (Meeting topic: distributed_virtual_router)"15:12
*** gokrokve has joined #openstack-meeting-alt15:12
Swamiviveknarasimhan: do you have any updates15:12
viveknarasimhanhyes15:12
viveknarasimhani posted the next patch set for L2 side upstream15:12
viveknarasimhanafter addressing review comments15:12
*** jgallard has joined #openstack-meeting-alt15:13
viveknarasimhanthere are still a few pep8 issues given by tox which i am working on15:13
viveknarasimhanalso i posted fix for l2-pop bug which got review approvals15:13
viveknarasimhanbut vendor CI tests are failing15:13
*** lisam has quit IRC15:13
viveknarasimhani need help from community on what will it take to merge that fix: https://review.openstack.org/#/c/93624/15:13
viveknarasimhanthat fix is mandatory for basic l2-pop (and so for dvr as well)15:14
Swamiviveknarasimhan: It has been already reviewed.15:14
viveknarasimhanyes15:15
SwamiIt should not be an issue to merge this fix into the Juno branch.15:15
viveknarasimhancore reviewer Edgar gave +215:15
SwamiYes vivek, send a mail to Kyle as well and tell him that you are waiting on this patch to be fixed since your work has a dependency.15:16
*** caleb_ has joined #openstack-meeting-alt15:16
viveknarasimhanok i will do15:16
viveknarasimhani sent two mails to maru newby, but didn't get response15:16
viveknarasimhansent a message to him on IRC as well.15:17
*** tomblank has left #openstack-meeting-alt15:17
Swamiviveknarasimhan: Everyone might be settling down after the summit, so wait for another couple of days.15:17
SwamiYou just need two cores approval, please send a message to Kyle and he will request the respective cores to take a look at it.15:17
Swamiviveknarasimhan: thanks for the update.15:18
Swami#topic Services and DVR15:18
*** openstack changes topic to "Services and DVR (Meeting topic: distributed_virtual_router)"15:18
viveknarasimhanok thanks15:18
SwamiFolks there were a couple of questions that came up in the Neutron design session for the DVR regarding the Services15:18
SwamiSo  I would like to start a regular discussion on the services that would be affected by DVR and how to address those issues.15:19
SwamiI have requested the respective Services team members to be part of the DVR team, so that they can provide their feedback and also participate in the addressing the issues.15:19
Swami#topic DVR and LoadBalancer15:20
*** openstack changes topic to "DVR and LoadBalancer (Meeting topic: distributed_virtual_router)"15:20
SwamiI don't think today Loadbalancer service will be impacted by the DVR.15:21
*** apmelton has left #openstack-meeting-alt15:21
SwamiIt should work as expected, but we need to test and validate in a DVR scenario the loadbalancer is working as expected.15:21
Swami#topic DVR and Firewall as a Service15:21
*** openstack changes topic to "DVR and Firewall as a Service (Meeting topic: distributed_virtual_router)"15:21
*** Rajeev has joined #openstack-meeting-alt15:22
*** Barker has joined #openstack-meeting-alt15:22
SwamiThere was some concerns that was raised about the FWaaS and its statefull behavior.15:22
*** zz_paulczar is now known as paulczar15:24
SwamiToday when we router intra VM traffic the packet touches the router only on one side and the other side it does not touch the router. Since the FWaaS is applied in the interface ports of the router, there was some concerns raised. So both the teams should come up with a solution to resolve this issue.15:24
SwamiWe have spoken to "Yi' and he mentioned that he would be joining our team meeting to discuss and taking it forward.15:25
yisunSwami, I’m here15:25
Swamiyisun: hi15:25
viveknarasimhanone second15:25
viveknarasimhanwhen we route the packet in DVR, the source router routes teh packet15:25
carl_baldwinSwami: That is a good and valid concern.  With DVR, each direction of two-way traffic is routed on a different machine.15:26
viveknarasimhanso the fwaas rules must have hit both sides15:26
viveknarasimhanthough each direction is routed on different machines, teh routers on the machines are the same15:26
viveknarasimhanand will hold the same fwaas rules15:26
carl_baldwinviveknarasimhan: The problem is not just that the rules must hit both sides.  The problem is that the state needed for tracking established connections is not there.15:26
viveknarasimhanok15:27
viveknarasimhansince the same router is distributed, the state disperses away onto the 2 routers based on direction of traffc. got it , thanks carl.15:28
yisunI was thinking to force traffic to FW before traffic hits the DVR15:28
SwamiWe had this discussion in the summit and Rajeev mentioned probably it would make sense to apply the firewall rules at the port where it is connected to the br-int.15:28
RajeevOne option is to look at the blueprint that implements security rules in OVS15:29
Swamiyisun: yes that's what I mentioned.15:29
*** glenc_ has quit IRC15:29
RajeevSimilar to security rules, FW can also include a bridge15:29
carl_baldwinyisun: That is a possible solution but negates the advantages of DVR.  Basically, it is saying that DVR and FWaaS are incompatible.  That might be true for some implementations of FWaaS.15:29
*** coolsvap is now known as coolsvap|afk15:30
viveknarasimhanrajeev, won't performance be an issue15:31
*** glenc has quit IRC15:31
viveknarasimhanwith introduction of bridges for fwaas on dvr?15:31
RajeevThe security rules BP folks analysis was no performance impact15:31
*** glenc- is now known as glenc15:31
carl_baldwinRajeev: That solves a different problem.  It doesn’t address the split state issue.15:32
viveknarasimhanthe security rules BP folks said they don't have numbers yet15:32
viveknarasimhanthat donesn't say there is no performance impact15:32
* carl_baldwin has to take off now. Sorry about that. Email or catch him on IRC later.15:32
Swamicarl: thanks15:32
yisunRejeev, that could be complicated when we start to introuduce zone15:33
yisunZone is basically a groupd of ports on the router15:33
RajeevYisun: ports on the same subnet?15:34
yisunIf we create a bridge outside, then we will not be able find right info to apply zone15:34
yisunRajeev, you mean that we can apply zone on subnet directly?15:35
RajeevYisun: will need to understand a bit more about zones,15:35
Swamiyisun: Probably for next it we can plan to address the different approaches for the FwaaS and walk through the Use cases and see how it would work that would be good.15:35
SwamiYisun: can you put together a doc or a wiki for different approaches to solve the state issue with the DVR15:36
SwamiWe can discuss it in the upcoming meetings.15:36
yisunSwami, I don’t think I have thought this through yet, may need more time15:37
RajeevYisun: feel free to get in touch15:37
Swamiyisun: Ok, take your time, this is not required immediately but eventually we need to address this issue.15:37
viveknarasimhanrajeev15:37
viveknarasimhanyi15:37
yisunSwami, yes15:37
Swamiok.15:37
yisunVivek, ya15:38
viveknarasimhansince br-int use of DVR today knows15:38
*** Sukhdev has joined #openstack-meeting-alt15:38
viveknarasimhanif packet is routed or switched,15:38
*** zzelle has joined #openstack-meeting-alt15:38
viveknarasimhanwe can havea the rule redirect traffic to firewall if we detect traffic routed by dvr15:38
viveknarasimhanon both sides (ie., on both ends)15:38
*** krtaylor has quit IRC15:38
yisunVivek, yes, that is what I meant by “force” traffic to FW15:39
SwamiThen dvr should be aware of the FWaaS in all these cases.15:39
viveknarasimhanyes, we can force that15:39
yisunBased on the source MAC I gues15:39
viveknarasimhanwe need to havea  fwaasondvr driver15:39
viveknarasimhanseparate, that will be configured in fwaas section ..15:39
viveknarasimhanin neutron config15:39
Swamiviveknarasimhan: we need to think through all the scenarios.15:40
viveknarasimhanwhat i put over here is service chaining15:40
viveknarasimhandvr routes packets, we detect them, chain such trafic to fwaas..15:40
yisunVivek, correct15:40
Rajeevyes15:40
*** trinaths has joined #openstack-meeting-alt15:40
SwamiOk if you guys have any more thoughts on this, just try to document or put it into the Etherpad and we can discuss in the upcoming meetings.15:40
viveknarasimhanfwaas looks to the traffic and then figures out to drop /forward back to br-int15:40
Rajeevcan also filter on ip addresses15:41
viveknarasimhanwe can filter on l2 header, l3 header15:41
viveknarasimhanl4 headers as well15:41
viveknarasimhanwith OVS 2.1 in plac15:41
yisunvivek and rejeev, let me take this to fwaas team andd discuss about if we should put subnet to zone15:41
viveknarasimhanthanks yi15:41
Rajeevsounds good15:42
Swami#action Yisun to take the FWaaS recommendations to the FWaaS team to work with the DVR15:42
Swami#topic VPNaaS and DVR15:42
*** openstack changes topic to "VPNaaS and DVR (Meeting topic: distributed_virtual_router)"15:42
SwamiWe had a discussion with Nachi on the VPNaaS and its impact on the DVR15:42
*** paulczar is now known as zz_paulczar15:44
RajeevSwami: what is the issue there ?15:44
SwamiBased on the discussion when a VPNaaS is created and associated with the Router, if the router is DVR, based on the service type, if it is a singleton service, then this service namespace should be only created in the Service Node.15:44
*** zz_paulczar is now known as paulczar15:44
*** phil_h has quit IRC15:45
SwamiSince we already have the SNAT service running on the Service Node, this should be accomplished in the Service Node.15:45
Rajeevdoes the VPN allow multiple internal subnets to outside connectivity?15:46
SwamiI don't see any major issues other than refactoring the VPNaaS code to check the router type and based on the router type the scheduler should than decide to start the service in the right node.15:46
Swamiyes it does.15:46
RajeevSo all the subnets attached to a router have access to VPN'ed network ?15:47
SwamiYes15:47
Swami#topic Tempest scenario tests15:47
*** openstack changes topic to "Tempest scenario tests (Meeting topic: distributed_virtual_router)"15:47
pcm_Swami: I thought one could only specify one subnet on near end>15:48
Rajeevit should be then not too difficult to get VPN15:48
RajeevIs there a doc one can point to on VPN?15:48
Swamipcm_: Nachi mentioned that it can support more than one15:49
pcm_Swami: I thought multiple subnets can be specified for the peer end of the connection.15:49
pcm_but not the local end.15:49
Swamipcm_: If you specify multiple subnets on the peer end, then it is equivalent to providing the VPN access to multiple subnets15:50
SwamiI don't see any difference in there.15:50
*** gyee has joined #openstack-meeting-alt15:50
*** igor has quit IRC15:50
pcm_Swami: OK15:50
RajeevSo on the near end it is one subnet only ?15:50
*** igor__ has joined #openstack-meeting-alt15:51
SwamiThe reason for that is that on the "left side" it only accepts one "IP address" for the local ip15:51
SwamiBut you can still have multiple subnets that you can provide access to from the far end.15:51
*** yjiang51 has joined #openstack-meeting-alt15:51
*** yjiang51 has left #openstack-meeting-alt15:51
pcm_Rajeev: When you configure the tunnel, you specify the far end public IP and peer-cidrs.15:51
Rajeevpcm_: sure15:52
SwamiEach of the peer-cidrs is a subnet by itself.15:52
SwamiEither left or right we have a list of "peer-cidrs' or subnets that we will be supporting.15:52
*** nlahouti has joined #openstack-meeting-alt15:53
*** arnaud has quit IRC15:53
*** paulczar has left #openstack-meeting-alt15:53
RajeevSwami: understand the peer-cidrs, what I want to know is can I have 3 local subnets talking to peer through the same VPN?15:53
pcm_Rajeev: Swami: I may be wrong, but I thought it was one to many selection.15:54
*** jgallard has quit IRC15:55
Swamipcm_: when you say "one" to many it is from single cloud site you can connect to multiple branches on the other side15:55
*** eghobo has joined #openstack-meeting-alt15:55
*** coolsvap|afk is now known as coolsvap15:55
*** yamamoto has joined #openstack-meeting-alt15:56
*** IlyaE has quit IRC15:56
Swamirajeev: your question is valid and I will confirm it.15:56
*** arnaud has joined #openstack-meeting-alt15:56
*** derekh_ has quit IRC15:56
pcm_Swami: I mean I thought that you can go from one subnet on this cloud to 1+ subnets on another cloud.15:56
*** gondoi is now known as zz_gondoi15:56
*** rbenali has joined #openstack-meeting-alt15:57
pcm_Did not think you could go from >1 subnet on this cloud to 1+ on the other cloud.15:57
Swamipcm_; rajeev: yes I can confirm it in the next meeting.15:58
*** rkukura has joined #openstack-meeting-alt15:58
*** devvesa has left #openstack-meeting-alt15:58
Swamirajeev: to your point if we only support one subnet on the left, then you don't see any issue with the DVR, am I right.15:58
RajeevSwami: it can be simpler solution then15:59
*** rcurran has joined #openstack-meeting-alt15:59
Swamirajeev: thanks.15:59
*** ericgoncz has joined #openstack-meeting-alt15:59
SwamiWe are at the end of the hour right now.15:59
*** zns has joined #openstack-meeting-alt15:59
RajeevSwami _pcm: thanks for looking into it.15:59
*** phil_h has joined #openstack-meeting-alt15:59
SwamiSorry the services topic took long.15:59
SwamiI also wanted to have some discussion on the Tempest and scenario testing but next week we can take it up.16:00
SukhdevSwami: time for ML2 meeting16:00
*** aostapenko has joined #openstack-meeting-alt16:00
SwamiThanks all16:00
Swami#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed May 21 16:00:55 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-05-21-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-05-21-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-05-21-15.01.log.html16:01
*** caleb_ has quit IRC16:01
*** mrsmith has quit IRC16:01
Swamibye16:01
*** Swami has left #openstack-meeting-alt16:01
*** xuhanp has quit IRC16:01
SukhdevHello ml2'ers16:01
rkukurahi everyone!16:01
trinathsHi all16:01
banixhi16:01
*** mattgriffin has joined #openstack-meeting-alt16:01
zzelleHi all16:01
yamamotohi16:01
Sukhdev#startmeeting networking_ml216:02
openstackMeeting started Wed May 21 16:02:16 2014 UTC and is due to finish in 60 minutes.  The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:02
openstackThe meeting name has been set to 'networking_ml2'16:02
SukhdevHi folks, I will be running the meeting today. Bob is here to help me out16:03
*** StephanB has joined #openstack-meeting-alt16:03
rkukuraBy kind to Sukhdev  ;)16:03
SukhdevAgenda is https://wiki.openstack.org/wiki/Meetings/ML2#Meeting_May_21.2C_201416:03
rkukuras/By/Be16:03
SukhdevYes - listen to rkukura :-)16:03
Sukhdev#info Announcements -16:04
*** caleb_ has joined #openstack-meeting-alt16:04
SukhdevMid-cycle code sprint scheduled July 9-1116:04
Sukhdev#link https://etherpad.openstack.org/p/neutron-juno-mid-cycle-meeting16:05
*** yamahata has quit IRC16:05
SukhdevPlease have a look and sign up - if you can help16:06
*** caleb_` has joined #openstack-meeting-alt16:06
Sukhdevthere is a possibility that the changes may impact ML216:06
rkukuraFocus is on nova parity I think, along with the core refactoring, which could have major implications for ML216:06
Sukhdev#topic - Action Items from last week - none16:06
*** openstack changes topic to "- Action Items from last week - none (Meeting topic: networking_ml2)"16:06
rkukuraSukhdev: I updated the agenda with 2, but they are both done16:07
Sukhdevrkukura: correct - so, be watchful16:07
*** jprovazn is now known as jprovazn_afk16:07
Sukhdev#topic ML2 design summit sessions post-mortem16:07
*** openstack changes topic to "ML2 design summit sessions post-mortem (Meeting topic: networking_ml2)"16:07
*** shivharis has joined #openstack-meeting-alt16:07
*** akuznetsov has quit IRC16:08
*** zz_gondoi is now known as gondoi16:08
*** igordcard has joined #openstack-meeting-alt16:08
SukhdevFour etherpads capture the information - be sure to look through them16:08
SukhdevAny question or issue about the etherpads?16:09
*** richm has joined #openstack-meeting-alt16:09
*** caleb_ has quit IRC16:09
yamamotoare they supposed to be freezed?16:09
rkukuraAny thoughts on overall ML2 sessions? Were they helpful?16:09
*** aostapenko has left #openstack-meeting-alt16:09
yamamotoie no more edits?16:09
banixyamahata_: i don’t think so; please add cooments; you can mark them appropriately16:10
Sukhdevyamamoto: I do not believe they are frozen, feel free to comment16:10
yamamotook16:10
banixyamamoto: ^^^16:10
trinathsdoubt: will ML2 driver synchronization effect the Mechanism driver codebase too16:10
SukhdevPlease update them as you feel appropriate16:10
Sukhdevtrinaths: At this point, I do not think so16:11
shivharisi think the ML2 sessions were very helpful. Folks were eager to know the future directions16:11
*** BrianB_ has joined #openstack-meeting-alt16:11
trinathsokay.. its mentions as a BP in Juno Roadmap16:11
Sukhdevshivharis: I felt the same - but, we were rushed a bit ;-)16:11
*** gokrokve has quit IRC16:11
shivharisone confusion that occcured during the course of the summit regarding16:11
shivharisplugins being a shim layer to ODL like controllers16:12
shivharisI feel it is appropriate for Openstack to be a first class citizen even if16:12
shivharisthere is not controller involved16:12
*** gokrokve has joined #openstack-meeting-alt16:12
Sukhdevshivharis: yea, but, somebody corrected it16:12
shivharisthe LLDP stuff brings about that16:12
nlahoutirkukura: it was helpfull. I wish there was more time and  have session to discuss more details on each topics16:12
shivharisML2 is the appropriate place for making it first class, even without ODL etc.16:13
*** IlyaE has joined #openstack-meeting-alt16:13
shivharisthat all16:13
trinathsI haven't attended the live sessions.. will there be a oppurtunity to see the videos and presentations .. any link for the same..16:13
Sukhdevnlahouti: +1 I felt the same way16:13
*** spzala has joined #openstack-meeting-alt16:14
yamamotomy impression was time/room distribution was not ideal16:14
banixtrinaths: only for thr general conference16:14
rkukuraregarding it being rushed and needing more time for details, how can we improve that?16:14
Sukhdevtrinaths: Design sessions are not recorded16:14
shivharisthe POD talks were very very helpful16:14
banixtrinaths: the general conference sessions were recorded and are on youtube already16:14
Sukhdevrkukura: If we would have gotten an extra session, it would have helped to spread the topics a bit16:15
rkukurashivharis: yes, lots of good progress in the PODs (neutron kind of took over all the tables in the POD room at times)16:15
trinathssukhdev: reg. Design sessions, where can i view ideas/presentations ..16:15
Sukhdevshivharis: Agreed. I loved the idea of Pods - in fact, we used them very effectively for ML2 discussions16:15
banixwith the talk of having coding sessions next time or the one after, i wonder if we lose more slots to regular design sessions16:15
*** xarses has quit IRC16:16
rkukuraSo more session slots would help. Maybe we need to pick fewer proposals too?16:16
banixs/to regular/from regular/16:16
*** manishg has joined #openstack-meeting-alt16:16
SukhdevAny feedback about the PODs?16:16
rkukuraDid the bundling of related proposals into sessions work, or did we need more time to really understand the individual proposals?16:16
asadoughiyes, i'd prefer if we discussed fewer topics at length then many with time constraints16:17
*** rmoe has quit IRC16:17
Sukhdevtrinaths: there is a link which lists all the sessions16:17
*** gokrokve has quit IRC16:17
banixsukhdev: PODs were good; need a better way for scheduling meetings there16:17
asomyaSukhdev: We need more tables for Neutron next time in the POD area :)16:17
rkukuraasomya: +116:17
shivharisrkukura: bundling allowed more 'sessions', but the title of the session did not do justice16:17
trinathsSukhdev: okay.. can you kindly share the link .. please16:17
Sukhdevbanix: correct16:17
asomyarkukura: The bundling worked but the title was a bit misleading16:17
Sukhdevtrinaths: I will look and send - does anyone have access to the link?16:18
shivharisbanix: instead of coding, whiteboarding may help more, your opinion?16:18
asadoughirkukura: 3 proposals in 40 min felt much too tight, no more than 2 in one session next time please16:18
banixtrinaths: https://wiki.openstack.org/wiki/Summit/Juno/Etherpads16:18
rkukuraI think the bundling of the hierarchical networks session worked prerry well, but the information shating happened first in the POD, so we kind of had a plan by the time the session occurred16:18
Sukhdevbanix: Thanks16:18
trinathsbanix: thanks a lot16:19
Sukhdevshivharis: we did good amount of whiteboarding in the pods16:19
rkukuraMaybe its best to present the ideas in the session, then use the POD to collaborate on how they related, etc.16:19
Sukhdevrkukura: great idea...16:19
nlahoutirkukura: I think one way to do is to have people involved in the topic, dedicate their time in the POD area and have discussion.16:19
asomyarkukura: +116:20
shivharissukhdev: yup, that was a great success16:20
banixwith the general conference overlapping only 1 day with the design sessions in Paris we may have a bit more time organizing at the summit before the design sessions16:20
Sukhdevrkukura: communications about the PODs (and scheduling) can be improved in future16:20
rkukuraOne thing I don’t feel we came out of the summit with is a clear sense of what is realistically going to get done during Juno, and the priorities16:20
shivharisIMHO, whiteboarding in PODs, with any number of onlookers/interested folks16:20
rkukuramarun and some others have been suggesting combining code sprints with the summit - maybe this whiteboarding is similar, where groups with a common interest whiteboard a design and start coding16:22
*** igordcard_ has joined #openstack-meeting-alt16:22
SukhdevThis is all great feedback - we should use for next summit16:22
banixalso send feedback to the foundation16:22
*** igordcard has quit IRC16:23
Sukhdevrkukura: yes, whiteboarding, and coding can go hand in hand - if planned correctly16:23
*** ramashri has joined #openstack-meeting-alt16:23
SukhdevOK shall we move on?16:23
nlahoutithat's correct. It has to be planed in advance.16:23
Sukhdev#topic: Bugs16:23
*** openstack changes topic to ": Bugs (Meeting topic: networking_ml2)"16:23
Sukhdevhttps://bugs.launchpad.net/neutron?field.searchtext=ml216:24
shivharissukhdev: i differ on that, sorry, usually coding needs more think time for good code16:24
Sukhdevshivharis: We used the same method during Montreal Tempest coding sprint, and it worked very well16:25
Sukhdevshivharis; We used the white board to discuss the design, agreed to the plan and then divided the work and implemented it16:25
Sukhdevshivharis: In three days we were able to achieve a lot16:25
*** jjmb has quit IRC16:25
shivharissukhdev: ok, i missed that event.16:26
*** betsy_ has joined #openstack-meeting-alt16:26
*** betsy has quit IRC16:26
*** betsy_ is now known as betsy16:26
SukhdevBack to bugs - I see a lot of them accumulating16:26
rkukuraSo how should we as the ML2 subteam ensure we are making good progress squashing the bugs?16:26
*** zns has quit IRC16:26
rkukuraDo we need some triaging within the subteam prior to these meetings?16:27
shivharisfirst tag all bugs as ML216:27
shivharisall => all relevant16:27
Sukhdevshivharis: I believe these are all ML2 bugs16:28
rkukuraDid someone at the summit volunteer to do initial triage/tagging of all neutron bugs?16:28
shivharisdon't know, but i can take ownership of ML2 tagging16:29
SukhdevFirst, we need to ensure they all have an owner16:29
*** sew has left #openstack-meeting-alt16:29
*** garyduan has joined #openstack-meeting-alt16:29
rkukurathey need tag and importance to be set, and if importance is high enough, they need owners16:29
Sukhdevshivharis: cool - thanks…I think they are already tagged, but, if you can scan through them16:30
yamamotoare md-specific bugs expected to be ml2-tagged?16:30
rkukurashivharis: Do you want to try to estimate importance as they show up, even if they are tagged to ml2 by someone else?16:30
yamamotoor is it for ml2 “core” part only?16:30
*** caleb_` has quit IRC16:31
shivharisrkukura: I can, but will need your help to some extent16:31
rkukurayamamoto: We’ve tended to use higher priority/importance for ml2 core than for vendor drivers16:31
Sukhdevyamamoto: yes they should be ml2 tagged16:31
rkukuraSo at these meetings, should we look for owners for medium and above importance bugs needing them?16:32
shivharissuggestion: steps: 1. tag+assign priority 2. search on tags and take ownership. 3. if there are leftovers, assign16:32
*** pballand has joined #openstack-meeting-alt16:33
*** Barker has quit IRC16:33
shivharisrkukura: yes if high priority are left over we should discuss in IRC16:33
Sukhdevshivharis: sounds great…..16:33
*** jmontemayor has joined #openstack-meeting-alt16:33
rkukurashivharis: As “ml2 bug czar”, would you be able to drive the bugs section of the agenda in future meetings, getting owners, making sure high importance stuff is making progress, etc?16:33
Sukhdev#Action: shivharis to scan all the bugs and tag them and prioritize them16:33
shivharisOk, i'll sign up16:34
*** yisun has quit IRC16:34
Sukhdevshivharis: cool - thanks16:34
SukhdevOn to next topic16:34
manishgalso, if some bugs aren't seeing action but are important they can be discussed here in the meeting to make sure some progress is made.16:34
rkukuraOur only high importance bug right now, binding ports in transactions, will be back in review in the next day or so16:35
Sukhdev#topic: Spec Reviews16:35
*** openstack changes topic to ": Spec Reviews (Meeting topic: networking_ml2)"16:35
*** Barker has joined #openstack-meeting-alt16:35
Sukhdevhttps://review.openstack.org/#/q/status:open+project:openstack/neutron-specs,n,z16:35
rkukuraI made an attempt to list all the ML2-related specs in the agenda16:35
*** thinrichs has joined #openstack-meeting-alt16:35
rkukuraThere are 2 that have been merged, 14 in review, and at least one coming16:36
SukhdevI notice two are merged and others are in review16:36
Sukhdevrkukura :-)16:36
banixworking on the spec for sdn-ve mechanism driver; will update and remove workinprogress soon16:36
SukhdevWe, as a team, should review them first before we ask the core reviewers16:37
*** rmoe has joined #openstack-meeting-alt16:37
rkukuraI’d be happy to by the “ml2 spec czar” and keep this organized for each meeting16:37
SukhdevWe should have at least one +1 from our team before we ask the core's16:37
Sukhdevrkukura: that will be awesome!!16:37
rkukuraMaybe even two +1s?16:37
Sukhdevrkukura: agreed16:38
shivharis2 +1s, agreed16:38
*** caleb_ has joined #openstack-meeting-alt16:38
banixSukhdev: well, the specs get submitted to gerrit and there is a chance others may review first16:38
manishgrkukura, Sukhdev - yeah, sounds like good idea for a couple of folks from subteam to first review and then ask core.16:38
rkukuraI’d really appreciate input on whether this is the right set to track - are some not relevant? are some missing?16:38
*** caleb_ has quit IRC16:39
rkukurawe’ve been kicking around the idea of having initial reviews within the subteam to improve scalabiltiy of the entire project - not wasting core reviewer’s time on stuff that isn’t very close to ready16:39
Sukhdevbanix: that is OK if others jump on it first - but, for all ML2 related specs, we should make sure somebody from our sub-team is on it as well16:39
manishgwhere's the list of specs you narrowed down rkukura?16:39
banixSukhdev: makes sense16:40
*** thinrichs has quit IRC16:40
rkukuramaybe next week we can make sure we’ve got at least two subteam reviewers for each spec16:40
banixmanishg: on the agenda16:40
rkukuramanishg: In the meeting agenda16:40
*** arborism has joined #openstack-meeting-alt16:40
shivharisrkukura: +116:41
Sukhdevrkukura: that sounds like a good idea, does everybody agree as well?16:41
yamamotowhat’s an appropriate way to “tag” a spec as ml2-related?16:41
Sukhdevyamamoto: good question - suggestions, ideas?16:41
rkukurayamamoto: I like having “ML2: …” as the first line of the commit message when its focus is on ML216:41
trinathsrkukura:  +116:42
rkukuraBut something like the DVR spec impacts ML2, but isn’t owned by ML2, so won’t do this16:42
*** gokrokve has joined #openstack-meeting-alt16:42
yamamotorkukura: +116:42
zzellemention ML2 in the commit message ?16:43
rkukuraThere should be associated lauchpad BPs that can be tagged I think, right?16:43
zzelleso we can use message:ml2 as gerrit filter  ?16:43
shivharisi think initial bug filer may not be sure where is belongs, so investigating the details can imply ML216:43
rkukuraMaybe we still want to track things from lauchpad, and make sure these have links to the gerrit spec reviews16:43
rkukuraOne comment on some of the summit session etherpads is to “not bury this in ML2”16:44
Sukhdevrkukura: what did they mean or imply?16:44
manishgpossible to have something in commit message like "impacts: ml2; api; etc"16:44
manishgthis was for tagging the specs.  but then we rely on commiter to do the right thing.  same issue with other suggestion about commit message.16:45
trinathsin the subject have ml2-specs: <spec name>16:45
shivharisi am ok with ML2: ... as commit message16:46
rkukuraActually, I don’t see a way to tag BPs in launchpad16:46
manishgtrinaths - this doesn't cover specs that involve ML2 but aren't only ML2.  e.g. DVR.16:46
shivharishow about DVR,ML2: ....16:46
trinathsmanishg: true. I mean it would be simple when we search gerrit for ml2-specs.16:47
*** gokrokve has quit IRC16:47
rkukuraI’ll try to move the list from the agenda into an etherpad that we can use to pull together the links to the spec reviews, the launchpad BPs, and the subteam reviewers assigned to each16:47
manishgwell, DVR will touch of lot of stuff.  so the tag list could be long (if in subject)16:47
Sukhdevrkukura: good idea16:47
manishgrkukura +116:47
yamamotorkukura +116:47
trinathsrkukura +116:48
banixrkukura: that is a good idea16:48
*** esker has quit IRC16:48
shivharis+116:48
manishgmaintain a list of spec elwewhere.  so someone should be paying attention to the specs and if there is ml2 involvment, add that to that list.16:48
rkukuraSukhdev: you can give me a #action for that16:48
*** esker has joined #openstack-meeting-alt16:48
*** kgriffs is now known as kgriffs|afk16:48
Sukhdev#action: rkukura to move all the specs from Action item to an etherpad16:48
rkukuraThis will be the set of specs that touch ML2, not just ones focused on ML216:49
shivharisand add that etherpad link to Agenda16:49
Sukhdevrkukura: thanks16:49
*** esker has quit IRC16:49
rkukuraSukhdev: s/Action/Agenda/16:49
rkukuraTen minutes left16:50
Sukhdev#action: rkukura to move all the specs from Agenda to an ehterpad16:50
Sukhdev#topic: Code Reviews16:50
*** openstack changes topic to ": Code Reviews (Meeting topic: networking_ml2)"16:50
trinathsneed spec reviews for my MD pending from Icehouse.16:50
*** msisk has joined #openstack-meeting-alt16:50
Sukhdevhttps://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z16:51
*** jbratton has joined #openstack-meeting-alt16:51
trinathsi have code too in place for review. need help of the team for review.16:51
Sukhdevtrinaths: yours is in the list, right, we will get on to it16:52
trinathssukhdev: okay..16:52
Sukhdevtrinaths: I will look at it16:52
SukhdevAnything else?16:52
Sukhdev#topic: Open Discussion16:52
*** openstack changes topic to ": Open Discussion (Meeting topic: networking_ml2)"16:52
SukhdevAnything general?16:53
Sukhdevwe have 6 min. left16:53
SukhdevLooks like we have covered most of it :-)16:53
banixI think Sukhdev did a good job chairing the meeting!16:53
rkukurabanix: +116:53
Sukhdevbanix: Thank you…you are so kind16:54
shivharisgreat summit, thanks sukhdev for organizing16:54
trinathsbanix: true said..16:54
trinaths+116:54
*** Kiall has joined #openstack-meeting-alt16:54
SukhdevYou guys are very nice team members - hence, my job was easy - so, the credit goes to you16:54
*** safchain has quit IRC16:54
yamamotowhat’s the next step for modular agent?16:54
trinaths:D16:54
shivharisI need help in becoming a power user of IRC, where to look for a tutorial?16:55
Sukhdevbanix: you want to take that?16:55
banixthere have been a couple of people interested in this work; will send an email this week to get organized before we send an email to ML16:55
manishgyamamoto: modular L2 agent?  is mohammad here?16:55
banixas we were asked to do in the design session16:55
*** vinod2 has joined #openstack-meeting-alt16:55
banixmanishg: yes I am here16:56
rkukurayamamoto: No spec yet, so getting people to work on one or more specs would be the place to start once there is a plan16:56
manishgah, didn't know your irc name!  okay :)16:56
Sukhdev#action: banix to send an email regarding ML2 Modular agent plan and seek interested parties16:56
Sukhdevbanix: I assigned you an action - hope you are OK16:56
banixSukhdev: sounds good16:57
SukhdevAnything else?16:57
SukhdevWe did well - we are right on time16:57
Sukhdev#endmeering networking_ml216:57
shivharisthanks, bye all.16:57
rkukuraThanks Sukhdev, everyone!16:57
trinathsbye all16:57
rkukurabye16:57
yamamotothanks16:57
asomyabye16:58
banixbye16:58
Sukhdev#endmeeting networking_ml216:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:58
openstackMeeting ended Wed May 21 16:58:11 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-05-21-16.02.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-05-21-16.02.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-05-21-16.02.log.html16:58
*** rkukura has left #openstack-meeting-alt16:58
*** rjrjr_ has joined #openstack-meeting-alt16:58
*** trinaths has quit IRC16:58
*** pcm_ has left #openstack-meeting-alt16:58
*** shivharis has quit IRC16:58
*** zzelle has quit IRC16:58
*** asomya has quit IRC16:58
*** hvprash has joined #openstack-meeting-alt16:58
*** igordcard_ has quit IRC16:59
*** SumitNaiksatam has quit IRC16:59
*** igordcard has joined #openstack-meeting-alt16:59
*** balajiiyer1 has joined #openstack-meeting-alt17:00
*** esker has joined #openstack-meeting-alt17:00
Kiall#startmeeting designate17:00
openstackMeeting started Wed May 21 17:00:11 2014 UTC and is due to finish in 60 minutes.  The chair is Kiall. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** bbaby has joined #openstack-meeting-alt17:00
*** openstack changes topic to " (Meeting topic: designate)"17:00
openstackThe meeting name has been set to 'designate'17:00
*** esker has quit IRC17:00
*** balajiiyer1 has left #openstack-meeting-alt17:00
KiallHey guys - Who's about?17:00
*** bbaby has quit IRC17:00
rjrjr_here17:00
vinod2here17:00
eankutsehere17:00
*** jmcbride has joined #openstack-meeting-alt17:00
*** bbaby has joined #openstack-meeting-alt17:00
KiallCool - and I know mugsie will be here in 2 mins17:01
*** mugsie has joined #openstack-meeting-alt17:01
KiallAh.. there he is ;)17:01
mugsieo/17:01
hvprashhi, this is my first meeting and new to the project17:01
bbabyme too.17:01
*** ranjitha has joined #openstack-meeting-alt17:01
KiallSo first off - for those people lurking who were not at the summit, welcome to our new core team member vinod2 :)17:01
eankutsecongrats vinod!17:02
* mugsie tips his hat to vinod2 17:02
jmcbridewelcome hvprash and bbaby!17:02
KiallCool! Great to see new faces getting involved, we're you guys at the summit?17:02
jmcbridecongrats vinod!17:02
*** xarses has joined #openstack-meeting-alt17:02
vinod2Thanks everybody17:02
hvprashthx17:02
betsyhere17:02
hvprashme and bbaby work together in comcast17:02
richmhere17:03
KiallExcellent - I think we met some comcast folks at the summit, but IRC handles often don't map to real life :P17:03
Kiall#topic Incubation / Program Docs17:03
*** openstack changes topic to "Incubation / Program Docs (Meeting topic: designate)"17:03
Kiallmugsie: you're up17:03
mugsiecool - we did a fairly in depth run down at the summit17:04
Kiallhvprash / bbaby - if you're not already aware, agenda is at https://wiki.openstack.org/wiki/Meetings/Designate and is open to everyone to add items to17:04
mugsie#linkhttps://wiki.openstack.org/wiki/Designate/Incubation_Application17:04
mugsie#link https://wiki.openstack.org/wiki/Designate/Incubation_Application17:04
mugsie#link https://wiki.openstack.org/wiki/Designate/Program_Application17:04
*** StephanB has left #openstack-meeting-alt17:04
mugsieI think we are in a good place to get this done by friday17:04
*** rbenali has left #openstack-meeting-alt17:04
mugsiejmcbride: i saw you we editing the program page - we nearly done there?17:05
mugsiewere*17:05
jmcbrideI've sent this around to a couple of folks here at Rackspace…17:05
betsymugsie: awesome17:05
jmcbrideupdating based on feedback from Anne Gentle, Adrian Otto and waiting to hear back from Troy Toman17:05
mugsiecool  - we are going to do a run through in HP later today17:05
jmcbrideand Michael Still17:05
Kialljmcbride: great, mugsie and myself have a meet in about an hour with some of the HP folks we want input from17:06
jmcbridesweet.17:06
Kialljmcbride: anything major?17:06
*** harlowja has joined #openstack-meeting-alt17:06
mugsieI will email you and we can sync up with times to send the email :)17:06
jmcbridenot yet. I was hoping to find a way in the wiki to see my changes.17:06
mugsieyeah, you can17:06
mugsieIf you #link https://wiki.openstack.org/w/index.php?title=Designate/Program_Application&action=history17:07
Kiallhttps://wiki.openstack.org/w/index.php?title=Designate%2FProgram_Application&diff=52977&oldid=5271417:07
*** _nadya_ has quit IRC17:07
*** xarses has quit IRC17:07
jmcbridecool. I'm looking at #link https://wiki.openstack.org/w/index.php?title=Designate/Program_Application&diff=cur&oldid=5292917:07
KiallLooks like pretty minor edits, perfect :017:07
Kiall:)*17:07
jmcbrideFirst thing was Anne asked why not join Networking or Data Processing programs17:08
mugsiecool. we call this item done for the time being? unless anyone else has any major objections17:08
*** manishg has left #openstack-meeting-alt17:08
mugsieah ^17:08
KiallOkay, so jmcbride - do you expect feedback from the remaining people before Friday is out?17:08
shakamunyihello17:08
mugsieyeah, I liked your reasoning why not to17:08
shakamunyihere17:08
Kiallshakamunyi: heya :) New to designate? Welcome17:08
jmcbrideI don't know about Troy and Michael yet, but the doc has been updated to reflect others.17:08
shakamunyicongrats vinod17:08
KiallOkay - Moving on so17:09
jmcbrideSo I added a "Why a new program?" section17:09
jmcbrideThat was the biggest edit.17:09
Kiall#topic Discuss DNSupdate proposal/blueprint17:09
*** openstack changes topic to "Discuss DNSupdate proposal/blueprint (Meeting topic: designate)"17:09
*** kenhui has joined #openstack-meeting-alt17:09
KiallAnyone wanting to take the lead on this one?17:10
shakamunyiKiall this is Alex B17:10
Kiallshakamunyi: Oh .. lol.. what a nickname17:10
shakamunyi:D17:10
shakamunyifew incidents of name clashes with that one :)17:10
Kiallrichm: you able to table about this topic?17:10
richmKiall: yes17:10
richmThe problem is that many DNS administrators already use nsupdate17:11
Kiall#link https://blueprints.launchpad.net/designate/+spec/dnsupdate17:11
richmThey want to be able to use nsupdate with designate17:11
*** rcurran has quit IRC17:11
richmThe bp outlines 3 approaches17:11
richm1) provide a tool called "dnsupdate" which works exactly like nsupdate17:11
*** garyduan has quit IRC17:11
richm2) change the designate client to have an "--nsupdate" mode which makes it work exactly like nsupdate17:12
*** nicole has joined #openstack-meeting-alt17:12
richm3) have mini-DNS work with nsupdate17:12
*** nicole is now known as Guest4991517:12
richmI think 3) would be the most preferable17:12
eankutseCan we start with 3)?17:12
richmyes17:12
*** terryw has quit IRC17:13
eankutseI don't think we should talk directly to miniDNS17:13
eankutseCentral will notify minidns17:13
eankutsewhen updates happens17:13
*** denis_makogon has joined #openstack-meeting-alt17:13
shakamunyithanks richm17:13
*** garyduan has joined #openstack-meeting-alt17:13
eankutseand miniDNS will go from there17:13
KiallSo - I think 3 is the best option, since it allows the real nsupdate utility to speak with us, and any other code supporting the RFC Dynanic DNS17:13
*** nati_ueno has joined #openstack-meeting-alt17:13
KiallBut.. It's also going to be blocked on mDNS17:13
rjrjr_i'm not seeing 3 options in the blueprint, but I like option 3.17:13
richmright - so support for 3) may take some time17:13
eankutseKiall: I was actually proposing the opposite17:13
eankutse:-)17:13
betsyrjrjr_: It’s down at the bottom in the whiteboard section17:14
Kialleankutse: not sure I follow?17:14
shakamunyirjrjr_ it's at the bottom of the whiteboard17:14
mugsieI quite like 3 personally - It was one of the reasons that miniDNS was such a good idea17:14
rjrjr_gotcha!17:14
richmrjrjr_: They are called "Proposal 1, 2, 3" in the bp17:14
KiallProposal 1 seems like a good compromise, and a good way to identify any gaps we might have17:14
eankutseMiniDNS is hidden inside designate17:14
eankutseIt is activated by Central17:14
eankutseSo updates go to central17:15
richmMiniDNS already "talks" to the outside world17:15
eankutseand Central activates (as usual) MiniDNS17:15
Kialleankutse: yes, but once we have all the mDNS code in place, it should be "easy enough" to extend to have a service we can expose to customers that handles dynamic updates17:15
mugsieyeah, that is part of the reason that we have the api separate to cnetral, to allow multiple input APIs17:15
KiallIt may or may not be the same service as mDNS itself, but I'm betting 90% of the code can be reused17:15
*** otherwiseguy has joined #openstack-meeting-alt17:16
eankutseok. Yes. We are talking about the "extended" miniDNS17:16
richmso perhaps mDNS will be split into two parts?17:16
richmmDNS XFR agent17:16
richmand mDNS nsupdate agent17:16
rjrjr_central won't really be central at that point. 8^)17:16
*** SumitNaiksatam has joined #openstack-meeting-alt17:16
Kialleankutse: yea, it would be an extra that would re-use much of the code, but might be different service etc :)17:16
betsyrjrjr_: It’s still authoritative, so why wouldn’t it still be central?17:17
eankutse:-)17:17
KiallAnyway - richm RedHat obv has customers etc asking for this, so, IMO, I'd be happy to see #1 done "today" with with #3 done when mDNS is ready.. #1 will ensure we have all the central requirements etc in place to handle this.17:17
richmKiall: ok, sounds good17:18
shakamunyiKiall: I prefer option 3, option 1 as compromise measure17:18
*** markmcclain has quit IRC17:18
shakamunyiKiall richm: agree17:18
richmok - so two action items for me17:18
vinod2With the current server pools and mdns design, on any modifications, central sends an update to the pool manager, which would send a NOTIFY to the backends.  With proposal 3, we need to think about how to send NOTIFY17:18
*** RaginBajin has joined #openstack-meeting-alt17:18
mugsieshakamunyi: when you say compramise - do you mean short term? or if we can't actually implement 3?17:18
Kiallvinod2: I don't think we do need to change that, as the code for #3 would send the updates to central,a nd the standard logic for NOTIFY's etc would kick in17:19
shakamunyimugsie: short/near term + identify gaps17:19
mugsiecool17:20
KiallBTW folks - for those who don't now .. Alex B / shakamunyi is the HP Cloud DNS dev manage.. jmcbride's counterpart in HP ;)17:20
*** xarses has joined #openstack-meeting-alt17:20
shakamunyiKiall actually I'm at RH17:20
KiallOHH17:20
richma different Alex B17:20
rjrjr_LOL17:20
KiallI though you said Alex B(arclay)17:20
mugsie:D17:20
jmcbridekiall, so you have a new manager?17:20
KiallI was wondering :D17:20
jmcbride;)17:20
richmwe have two Alex B's17:20
shakamunyiKiall sorry - Alex Baretto17:21
shakamunyi:D17:21
KiallMy mistake :D17:21
richmWe have to Alex Bar's17:21
richmtwo17:21
shakamunyiKiall no worries17:21
Kialllol17:21
richmso how do I do the meetingbot #action thing?17:21
vinod2Kiall: So with proposal 3, would there be a separate layer (similar to api) that accepts the nsupdate requests and sends them on to central?17:21
*** kenhui has quit IRC17:21
richmI need to give myself two actions17:21
Kiallrichm: #action <name> <action>17:21
mugsievinod2: yup17:21
vinod2Also with proposals 1 and 2, would the requests go through the current api layer?17:22
*** ranjitha has quit IRC17:22
richm#action richm update dnsupdate blueprint with info from this meeting17:22
*** kenhui has joined #openstack-meeting-alt17:22
*** garyduan has quit IRC17:22
*** gduan has joined #openstack-meeting-alt17:22
richm#action richm add minidns blueprint for nsupdate support17:22
Kiallvinod2: yes - there would, that layer *might* be the same thing we serve mDNS AXFR's from, but might be a different service sharing lots of code17:22
shakamunyivinod2 for mDNS AXFR17:23
jmcbriderecap17:23
*** beyounn_1 has joined #openstack-meeting-alt17:23
*** ranjitha has joined #openstack-meeting-alt17:23
Kiallvinod2: with proposal 1 and 2, the modifications would go through the current API layer I believe17:23
Kiall(after any gaps get closed)17:23
shakamunyiKiall vinod2 correct17:23
*** arnaud has quit IRC17:24
mugsierichm: can you capture ^ in the bp for 1 and 2 ?17:24
richmmugsie: yes17:24
richmanother problem with 1 is that it won't be an exact replacement for nsupdate17:24
richmfor example, doesn't nsupdate allow for constraints?  and tsigkeys?17:24
*** michael-yu has joined #openstack-meeting-alt17:25
shakamunyirichm correct17:25
*** james_li has quit IRC17:25
richmnot sure how we will do that with the v1 or v2 api17:25
rjrjr_also you can "batch" requests with nsupdate17:25
KiallAnyway - To recap as jmcbride suggests - 1) Identify gaps to support the functionality, 2) Close those gaps using the current APIs, 3) Create the dnsupdate util (optional, depending on if mDNS is ready), and 4) support RFC dynamic DNS using mDNS's code (may or may not be a separate service)17:25
RaginBajinI'm sorry, but I can't find the blueprint that you guys are referencing.17:25
KiallRaginBajin: https://blueprints.launchpad.net/designate/+spec/dnsupdate17:25
RaginBajinthx17:25
richmKiall: ok - I will update the blueprint17:26
vinod2Would nsupdate or the equivalent run with admin privileges - so that they can make modifications to any tenant's data?17:26
mugsievinod2: Ideally no17:26
*** igordcard has quit IRC17:26
Kiallvinod2: For #3, It would require the nsupdate call is TSIG signed, so we can identify the end user17:26
Kiallwhich means it has a dep on https://blueprints.launchpad.net/designate/+spec/mdns-designate-scoped-tsig17:27
shakamunyirichm dnsupdate allows for both constraints and tsigkeys (determining the latter through the parsing process)17:27
*** pballand has quit IRC17:27
richmshakamunyi: right, but I'm concerned with how we translate those into something that the designate api can consume17:27
*** kenhui has quit IRC17:28
Kiallrichm: concerned how we translate TSIG keys to user creds?17:28
richmKiall: yes17:28
rjrjr_so, all we are really doing here is creating a new command called nsupdate, but isn't really nsupdate, correct?17:28
richmrjrjr_: correct17:28
rjrjr_doesn't make too much sense to me then. 8^(17:29
Kiallrjrjr_: P1 and P2 do that, P3 uses the real nsupdate17:29
richma new command called "dnsupdate" so as not to conflict with the possibly already installed "nsupdate"17:29
*** kenhui has joined #openstack-meeting-alt17:29
KiallP1 would be considered a stop-gap while #3 is blocked17:29
KiallAnd, if RH have people asking and dev time to work on it, I don't see a reason to reject the P1 stopgap while P3 is blokced17:29
Kiallblocked*17:30
*** BrianB_ has quit IRC17:30
KiallBuilding P1 will without a doubt make doing P3 easier, as gaps are closed in the API/Central layers17:30
*** esker has joined #openstack-meeting-alt17:31
shakamunyirjrjr_ dnsupdate just provides simplified command for nsupdate17:31
rjrjr_what new functionality are we adding besides a different command line tool that does what designate command line tool does?17:31
shakamunyiKiall agree. I'm committed to that P1 stopgap17:32
Kiallrjrjr_: well, it's not so much about having another tool, it's about compatibility with the standard (outside of designate) CLIs for managing DNS17:32
*** akuznetsov has joined #openstack-meeting-alt17:32
rjrjr_so, the new dnsupate tool will be a shell like nsupdate is?17:33
richmrjrjr_: a DNS admin who prefers to use nsupdate and has a lot of process/scripts built around using nsupdate will be reluctant to rewrite everything to use the designate command line tool17:33
*** yogeshmehra has joined #openstack-meeting-alt17:33
Kiallrjrjr_: yes, ideally a 100% compatible re-implementation17:33
*** eguz has joined #openstack-meeting-alt17:33
richmrjrjr_: yes - the goal is that it is a drop-in replacement17:33
KiallAt least for the features it implements anyway17:33
richmjust sed -e s/nsupdate/dnsupdate/g17:33
rjrjr_okay.17:33
shakamunyirjrjr_ and doing that with in an easy to use + script manner with some niceties (such as automatically creating PTRs for a given A or AAAA record)17:34
RaginBajinbut I guess anything written outside of the nsupdate tool is then kinda screwed right. (i.e. perl, etc)17:34
richmso shakamunyi is also proposing some additional features that dnsupdate will have that nsupdate does not have17:34
KiallOr telling your DHCP server that nsupdate is at /usr/bin/*d*nsupdate etc17:34
*** ramishra has quit IRC17:34
richmRaginBajin: not sure what you mean17:35
KiallRaginBajin: correct, Proposal 3, which we agree is the long term goal, solves working with code that doesn't shell out to nsupdate17:35
shakamunyirichm all entirely ease-of-use17:35
richmyou mean, if someone has written something in Net::DNS?17:35
RaginBajinrichm yeah exactly17:35
richmright, proposal 317:35
KiallWith P3 implemented, Net:DNS, dnspython, etc etc will all "just work" with Designate for updates etc17:35
RaginBajinkiall: gotcha17:35
*** emagana has joined #openstack-meeting-alt17:36
KiallOkay - I think we have consensus. shakamunyi / richm .. can we start by just identifying the gaps that will need to be fixed in API/Central - Once we have that we have a better idea of the work involved17:37
*** eghobo has quit IRC17:37
mugsie+117:37
richmagreed17:37
eankutse+117:37
*** betsy_ has joined #openstack-meeting-alt17:37
rjrjr_+117:37
KiallOkay - Let's move on so :)17:37
Kiall#topic Server pool deployment question for multi-region/DC name servers17:37
*** openstack changes topic to "Server pool deployment question for multi-region/DC name servers (Meeting topic: designate)"17:37
KiallI'm not sure who added this item?17:37
*** Sukhdev has quit IRC17:38
mugsiejmcbride: i think?17:38
KiallLooks like it was jmcbride - Anyone free to discuss?17:38
*** betsy has quit IRC17:38
shakamunyiKiall agree17:38
shakamunyiKiall agreed17:38
jmcbrideyes, that was me, sorry guys17:38
jmcbrideso I brought along a friend17:38
*** IlyaE has quit IRC17:38
Kialllol - sorry for what exactly? ;)17:38
jbrattonthis goes back to what we started discussing at the summit about having multiple minidns servers with their own pools17:39
jbrattonso we need to define pools of pools for lack of a better way of saying it17:39
jbrattonand I don't care how it is implemented.. config files.. api.. etc.17:39
KiallOkay, so this was related to ensuring that DNS servers in Region A do AXFR's from, and get NOTIFY's from, Region A mDNS servers?17:40
jbrattonbut each minidns needs to know who to send notifies to, and who to accept zone transfers from17:40
jbrattonyeah17:40
*** ramishra has joined #openstack-meeting-alt17:40
jbrattonwe don't want a full mesh where every minidns is notifying every nameserver17:40
Kiall++17:40
*** betsy has joined #openstack-meeting-alt17:40
jbrattonso I was thinking it could go in the api since that is where we define the nameservers at17:40
eankutse+217:41
jbrattonbut that is just my thought.. you all are welcome to implement it however17:41
mugsieyeah - so we define affinity to minidns installations at the servers level>17:41
eankutsejust like masters today have a list of slaves to send to17:41
mugsie?*17:41
KiallOkay, So, did anyone come up with a good way to handle this? My initial thought is around tagging mDNS servers (via a config option) and then tagging (via the API) the actual DNS servers with a matching attribute17:41
eankutseI think a config file for miniDNS to read upon startup17:41
eankutsewill be one way to go17:41
*** ViswaV has joined #openstack-meeting-alt17:41
mugsieyeh, my initlal though was that it was another attrib on the hosts that we defined in the servers call17:41
KiallSo.. an mDNS server with a tag of "region-a" would notify all servers with the "region-a" tag17:42
*** betsy_ has quit IRC17:42
richmp17:42
mugsiewhich maps to a tag / something on a mDNS agent17:42
*** jprovazn_afk has quit IRC17:42
KiallBut - that only solves NOTIFY's I think.. We still need to create the zone at the real DNS server with the correct list of mDNS's to AXFR from17:42
eankutsemugsie: what is mDNS agen?17:43
mugsieyeah, hense tagging the servers/hosts themselves as well17:43
mugsieeankutse: agent - i cnat type17:43
KiallMaybe mDNS will, not unlike nova-compute, registers itself on startup as being part of a tag/region etc?17:43
*** gokrokve has joined #openstack-meeting-alt17:43
Kialleankutse: mini-dns - just shorter ;)17:43
eankutseI just wanted to clarify the "agent"17:43
eankutseis that the service? or another thing?17:44
*** kenhui has quit IRC17:44
mugsiea runnign instance of mDNS17:44
eankutsek17:44
*** luqas has quit IRC17:44
*** xarses has quit IRC17:44
RaginBajinand this would be use to handle load basically right17:45
jbrattonI envision multiple mdns agents for scale17:45
jbrattonto handle multiple geographic locations17:45
mugsieRaginBajin: and to ensure a dns server in london doesnt AFXR from austin, when there is a mDNS server in london17:46
KiallSo .. "designate-mdns" upon boot registers itself, like nova-compute does, with it's tag, and we "tag" servers in the pools API, we can then have knowledge of all the components involved, and make smart decisions around who to NOTIFY and where to AXFR.17:46
Kiall(summarized my idea ^)17:46
mugsieKiall: yup17:46
mugsiei think that works17:46
rjrjr_makes sense.17:46
RaginBajinmugsie: ok that's what I thought.. I've heard the term mdns before but not as mini-dns, so I wanted to be sure.17:46
mugsiejbratton: does that look like what you were thinking?17:46
jbrattonyeah, that makes perfect sense17:47
mugsiecool17:47
jbrattonwe don't add/remove nameservers very often.. so how it is setup.. that can be as static or dynamic as needed17:47
*** gokrokve has quit IRC17:47
vinod2is there already a blueprint to track this?17:48
KiallThe other option - which removes the "registers itself" bit, it just to have an API resource that lists out all the mDNS servers with there tags.. Simpler, but when things like dynamically booting a pool for a customer comes along, the registration piece can be reused to handle that17:48
Kiallvinod2: No, this came out of the discussions in Atlanta.. But it was unsolved at the time17:48
KiallDoorbell - BRB17:49
eankutseI can open a blueprint for this17:49
KiallThanks eankutse17:49
RaginBajinIs designate being the system to initiate the AXFR's or NOTIFY or are we giving that to processes like BIND. Trying to get my head around this, sorry for the questions.17:50
eankutse#action eankutse open blueprint for regionalized mdns servers17:50
mugsieRaginBajin: it is Designate17:50
KiallRaginBajin: Sure, so.. BIND/PowerDNS etc will be the "real DNS servers" (as it is today)17:50
shakamunyiKiall mDNS tagging makes sense to me17:50
KiallWe'll also have this mini-DNS service, that BIND/PowerDNS/etc/etc do AXFR's from17:50
rjrjr_Designate will.  the mdns (mini-dns) is going to be a simplified DNS server for transfers initially.17:50
Kiallmini-DNS (or mDNS) will sent NOTIFY's to BIND/PowerDNS/etc, and BIND/PowerDNS/etc will perform an AXFR against mDNS17:51
*** jjmb has joined #openstack-meeting-alt17:51
*** jjmb has quit IRC17:52
Kiall#action eankutse to file blueprint around region-aware handing of NOTIFY's and AXFR's17:52
*** jjmb has joined #openstack-meeting-alt17:52
KiallOnce that's up, we can figure out the details17:52
KiallBut.. I think we have a general direction to go with tag's (which may be the wrong word, but we'll figure that out when we have more than 5 mins left in the meet)17:53
*** emagana has quit IRC17:53
shakamunyiKiall agree, think "tags" or (insert name here) is a start17:53
Kiall#action kiall to re-add "Server pool deployment question for multi-region/DC name servers" to agenda one the BP is drafted17:53
*** ramishra has quit IRC17:53
*** sarob has joined #openstack-meeting-alt17:53
*** emagana has joined #openstack-meeting-alt17:53
KiallOkay .. Moving on, unless there are any other comments on this one? :)17:53
betsyNot from me. It all sounds good17:54
Kiall#topic Open Discussion17:54
mugsie+117:54
*** openstack changes topic to "Open Discussion (Meeting topic: designate)"17:54
*** IlyaE has joined #openstack-meeting-alt17:54
hvprashso for us newcomers, is this is the official developer documenation we should be referring - http://designate.readthedocs.org/en/latest/devstack.html ? any suggestions, tips to get started?17:54
KiallOkay - Open discussion, anything off-agenda today?17:54
Kiallhvprash: I have a ticket filed for me to update those docs, there slightly outdated17:54
Kiallhttps://github.com/moniker-dns/devstack.git was moved to https://github.com/stackforge/designate/tree/master/contrib/devstack17:54
hvprashlooks like not much has changed and is a good reference to start with ?17:55
*** grapex has joined #openstack-meeting-alt17:55
KiallYea, it's just a "plugin" rather than fork of DevStack now17:55
rjrjr_are we going to provide support for Keystone v3 domains?  have we been approached about this yet? http://www.florentflament.com/blog/setting-keystone-v3-domains.html17:56
*** nati_uen_ has joined #openstack-meeting-alt17:56
*** cp16net has joined #openstack-meeting-alt17:56
*** nati_uen_ has quit IRC17:56
RaginBajinI do have a question, if someone wanted to write a driver for say a particular service, is there any starting point to look at17:56
Kiallrjrjr_: I've been approached internally by HP Keystone folks, but haven't had much time to dig in yet17:56
KiallRaginBajin: when you say service, you mean something like a 3rd party hosted DNS?17:56
*** adrian_otto1 has joined #openstack-meeting-alt17:56
*** xarses has joined #openstack-meeting-alt17:56
Kiallor just a different DNS server?17:56
RaginBajinkiall:  Yes a 3rd party hosted DNS17:57
KiallInside of this folder https://github.com/stackforge/designate/tree/master/designate/backend17:57
*** arborism is now known as amcrn17:57
Kiallyou'll see all the backends, one of them is a driver for DynECT (i.e DynDns)17:57
RaginBajinkiall: Perfect. Thanks17:57
eankutseI am startiing work on designate-mdns service. Hope to have basic initial submission in the next few days: https://blueprints.launchpad.net/designate/+spec/mdns-core-mdns-service17:57
denis_makogonRaginBajin, do not forget about integration testing inside 3d party CI for any new driver17:57
*** baoli has quit IRC17:58
*** adrian_otto has quit IRC17:58
*** nati_uen_ has joined #openstack-meeting-alt17:58
Kialleankutse: excellent :)17:58
*** SlickNik has joined #openstack-meeting-alt17:58
*** amrith is now known as not-arborism17:58
KiallRaginBajin: questions etc, drop by #openstack-dns and people are usually there17:58
Kiall2 mins left - Any other topics before we call it a day?17:59
*** nati_ueno has quit IRC17:59
betsyJust FYI, I’ll be working on the database schema redesign for recordsets and records17:59
*** michael-yu has quit IRC17:59
*** not-arborism is now known as amrith17:59
KiallOkay, if there's nothing else we're at time :)17:59
KiallThanks all17:59
Kiall#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Wed May 21 17:59:53 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-05-21-17.00.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-05-21-17.00.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-05-21-17.00.log.html17:59
*** RaginBajin has left #openstack-meeting-alt18:00
*** jcru has joined #openstack-meeting-alt18:00
shakamunyithanks Kiall18:00
SlickNikThanks Kiall.18:00
SlickNikOn the dot :018:00
*** markmcclain has joined #openstack-meeting-alt18:00
SlickNik:)18:00
KiallSlickNik: ;)18:00
hvprashThanks18:00
*** bbaby has quit IRC18:00
*** jbratton has left #openstack-meeting-alt18:00
*** michael-yu has joined #openstack-meeting-alt18:00
*** hvprash has quit IRC18:00
*** msisk has quit IRC18:01
*** saurabhs has joined #openstack-meeting-alt18:01
*** vinod2 has left #openstack-meeting-alt18:01
SlickNik#startmeeting trove18:01
openstackMeeting started Wed May 21 18:01:17 2014 UTC and is due to finish in 60 minutes.  The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
*** mugsie has left #openstack-meeting-alt18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: trove)"18:01
openstackThe meeting name has been set to 'trove'18:01
denis_makogono/18:01
iccha1o/18:01
mattgriffino/18:01
*** jmcbride has quit IRC18:01
kevinconwayo/18:01
*** imsplitbit has joined #openstack-meeting-alt18:01
imsplitbito/18:01
vipulo/18:01
pdmarso/18:01
amcrno/18:01
peterstac\o18:01
amytrono/18:01
amrith\0/18:01
grapex~o~18:01
*** robertmyers has joined #openstack-meeting-alt18:01
vgnbkro/18:01
Barkero/18:02
*** pballand has joined #openstack-meeting-alt18:02
*** mat-lowery has joined #openstack-meeting-alt18:02
cp16neto/18:02
robertmyerso/18:02
mat-loweryo/18:02
peoplemergeo/18:02
cp16netgrapex: is doing the wave18:02
SlickNik#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting#Agenda_for_May_2118:02
amcrnpop and lock18:02
glucaso/18:02
*** pballand has quit IRC18:02
grapexcp16net: I hope your PSA involves a cartoon mascot singing about logging safety.18:03
dougshelley66o/18:03
*** esp has joined #openstack-meeting-alt18:03
SlickNik#topic Informational PSA on Openstack Logging Standards18:03
*** openstack changes topic to "Informational PSA on Openstack Logging Standards (Meeting topic: trove)"18:03
*** simon_chang has joined #openstack-meeting-alt18:03
espo/18:03
SlickNikcp16net: all yours18:03
*** rjrjr_ has quit IRC18:03
*** kenhui has joined #openstack-meeting-alt18:03
cp16net#link http://media0.giphy.com/media/Zjh1dptLNm5Qk/200_s.gif18:03
cp16net#link https://wiki.openstack.org/wiki/LoggingStandards18:03
cp16netso there was a review for removing the translations for debug messages18:04
vipulthe image also seems to go well with the topic ;)18:04
grapexcp16net: I was about to say please add an underscore to that picture so we can localize it18:04
cp16neti was not aware of this link so i thought i would share so we can all be on the same page18:04
grapexbut thanks to that other link I now know that isn't how we roll in Trove. Thanks cp16net!18:04
*** betsy has quit IRC18:05
*** baoli has joined #openstack-meeting-alt18:05
cp16netbut this also leads to us making sure we make log messages at the right level18:05
cp16netcurrently *almost* everything is in debug18:05
iccha1+118:05
denis_makogon++18:05
cp16netand this is not helpful for operations to turn down logging18:06
vipulyea without debug turned on.. you're SOL18:06
denis_makogonagreed, we need more INFO level logging18:06
cp16neti think getting some input from people running this in a prod env would help a ton18:06
iccha1also the note on running other libraries at different log levels is useful note for deployments18:06
cp16netso i think the action here is to audit out logging levels throughout trove18:06
*** NehaV has joined #openstack-meeting-alt18:07
denis_makogonsound reasonable18:07
vipul+1 we should be looking at this during reviews as well18:07
cp16net#action make a bug to audit logging levels throughout trove code code with deployers18:07
grapexI like this policy much better than the "put underscores in front of every string ever" policy18:08
cp16net#agree vipul18:08
denis_makogongrapex, +118:08
amcrnand if someone is planning on helping out with this, please be holistic vs. pushing a couple dozen reviews, fixing it file by file :)18:08
*** coolsvap is now known as coolsvap|afk18:08
*** zuqiang has joined #openstack-meeting-alt18:08
*** zuqiang has quit IRC18:08
kevinconwaythere goes my strategy of one commit per log line18:08
cp16netamcrn: i think either way would be fine as long as its not considered done after the first review18:08
denis_makogonamcrn, agreed, hard to review a 2k lines patch with only one type of change18:08
dougshelley66seems like we should break it up logically?18:09
cp16netbecause you might not know what the guest agent logging should be for c*18:09
denis_makogondougshelley66, file by file18:09
kevinconwaycp16net: but we use a python guest agent?18:09
SlickNik#action cp16net make a bug to audit logging levels throughout trove code code with input from deployers18:09
denis_makogondougshelley66, or per package18:09
vipuldenis_makogon: no please don't do file by file18:09
cp16netamcrn: but i agree to make sure it includes at least the whole module of changes18:09
SlickNikcp16net: add your name to the #action line. :)18:09
amcrni think my comma was misplaced, i was against file by file :D18:09
cp16netgotcha thanks :)18:10
*** james_li has joined #openstack-meeting-alt18:10
vipulthose commas18:10
dougshelley66i was referring to some reasonable grouping that could be split across multiple devs?18:10
cp16netgotcha18:10
denis_makogonamcrn, get it =)18:10
cp16netdougshelley66: sure18:10
*** SnowDust has joined #openstack-meeting-alt18:10
kevinconwaycan we get the implementors of datastores to fix their guest logs?18:10
denis_makogonbut first we need policy18:10
cp16netok any othe questions18:10
*** jmcbride has joined #openstack-meeting-alt18:10
cp16neti'm done18:10
*** jasonb365 has joined #openstack-meeting-alt18:11
*** arnaud has joined #openstack-meeting-alt18:11
denis_makogonkevinconway, first implement postgresql then convince us to re-write our code =))18:11
amcrnhashtag rekt18:11
kevinconwaydenis_makogon: sick burn18:11
*** Guest49915 has left #openstack-meeting-alt18:11
SlickNikSo guys, while I think this is important. I don't think it's a high-pri item.18:11
*** jmcbride has quit IRC18:11
*** jmcbride has joined #openstack-meeting-alt18:12
cp16netSlickNik: i agree its a low at most18:12
SlickNikIf you're interested in helping out with it, I'd suggest you touch base with cp16net rather than submit a competing patch.18:12
denis_makogonyeah, i agree18:12
*** rueben has joined #openstack-meeting-alt18:12
SlickNikOkay, 'nuff said.18:12
cp16netok18:12
SlickNik#topic Follow up on ATL discussion on Code Reviews18:12
*** openstack changes topic to "Follow up on ATL discussion on Code Reviews (Meeting topic: trove)"18:12
SlickNik#link https://etherpad.openstack.org/p/trove-review-juno18:12
SlickNikSo at ATL we decided to use a custom dashboard to focus our review efforts.18:13
vipulhere's another one that we tried to take notes in during the session, but etherpad was a flake: https://etherpad.openstack.org/p/juno-trove-reviews18:13
denis_makogon#link bit.do/trove-reviews18:14
SlickNikThis dashboard is at: http://bit.do/trove-reviews18:14
SlickNikA couple of you mentioned that this doesn't capture reviews from the client and integration projects.18:14
cp16netSlickNik: you can include the other ones as well18:15
SlickNikSo I created another that does at: http://bit.do/all-trove-reviews18:15
SlickNik#link http://bit.do/all-trove-reviews18:15
denis_makogonSlickNik, amazing =)18:15
vipulnice18:15
iccha1sweet!18:15
grapexSlickNik: really great stuff!18:15
amcrn<3 SlickNik18:15
grapexSomeone at Rax just pointed this out, so quick reminder that you need to be signed in first for the link to work.18:16
SlickNikAlso wanted to touch upon a couple of other issues that came up.18:16
cp16netnice18:16
mat-loweryThis is great SlickNik. Can you elaborate on the meaning of "No Negative Feedback"?18:17
SlickNikI'm still looking into the beginning of meeting stats, so I'll keep you posted on that18:17
mat-lowery(Or I could read the query.)18:17
denis_makogonmat-lowery, has no -1 for now18:17
SlickNikmat-lowery: Passed unit tests, passed integration tests, and no −1 from other reviewers.18:17
imsplitbitso I see a fundamental problem here, if I may, metadata is no where on here18:17
mat-loweryIf I remember correctly, I was told that core does look at -1s. This seems to contradict that.18:18
vipuldoes it have a -1? imsplitbit18:18
grapexAlso... let's talk about it18:18
denis_makogonimsplitbit, is is abandoned due to hang timeout?18:18
grapexI think core should in general look at more stuff18:18
denis_makogon*is it18:18
imsplitbitand that's because Auston asked to hold the client changes until the server piece is reviews18:18
imsplitbitreviewed18:18
grapexbut looking at -1 explicitly is a little silly- its like saying "we must be better at looking at the lowest priority items."18:18
denis_makogoni would say that we need another section "Abandoned due to time expiration"18:19
imsplitbitand the server will fail jenkins until client patch is merged18:19
grapeximsplitbit: That seems like a good case for making blueprints the starting point of where core looks.18:19
SnowDustmat-lowery: +118:19
SlickNikimsplitbit: And why isn't the server piece in here?18:19
imsplitbitbecause jenkins -1 it18:19
SlickNikbecause of a −1 dependency on the client?18:19
imsplitbitcause tests fail due to the client not having metadata support in it18:19
vipulyea this is the fun of having a cross dependency :D18:20
grapexSo I think this is a good start, but we probably won't be able to go off a filter alone18:20
imsplitbitso I just wanted to point that out18:20
grapexI think we should look at this and at the blueprints18:20
imsplitbitthis dashboard is nice but that is a rather large flaw for any new features18:20
mat-lowerygrapex: good start. can't be the only list18:20
grapexif there's a -1'd pull request in Gerrit that is part of a blueprint which is low priority that hasn't been well-discussed, I'm personally ok if Core looks at that dead-last / not-at-all18:20
* grapex runs for cover18:21
SlickNikThis comes back to our core-standup. We'll have to discuss bps that don't show up because of cross dependencies like this separately.18:21
imsplitbit*unless* we merge client code first which is scary since changes made on the reviews for server code could necesitate a change in the client18:21
*** _nadya_ has joined #openstack-meeting-alt18:21
cp16netmake sure we know where bp stands18:21
imsplitbitkk I just wanted to point this out18:21
SlickNikI'm still need to work something out here with the other core folks - so stay tuned for info regarding this.18:21
imsplitbitRax is looking to use metadata asap so I get asked about it daily18:22
SlickNikimsplitbit: Historically we've had to merge client code first so that we can make sure that tests pass.18:22
SlickNikimsplitbit: Issue duly noted. Will figure out what the best way to handle such cases is.18:23
grapexSlickNik: I don't see that changing unless we move to writing Tempest tests in the Trove repo with the copy/pasta client18:23
SlickNikgrapex: same here.18:23
SlickNikokay moving on to another point that came up.18:23
SlickNikThe 2 +2 reviews needed for approval.18:24
SlickNikSo I talked to multiple folks, and this is definitely a cross OpenStack thing.18:24
SlickNik#link https://wiki.openstack.org/wiki/GerritJenkinsGit#Reviewing_a_Change18:25
SlickNik"When a review has two +2 reviews and one of the core team believes it is ready to be merged, he or she should leave a +1 vote in the "Approved" category."18:25
vipulso it's just a practice, but not enforced by gerrit?18:25
iccha1yes18:26
*** emagana has quit IRC18:26
*** IlyaE has quit IRC18:26
SlickNikvipul: yes18:26
vipulok, sounds good18:26
*** _nadya_ has quit IRC18:26
esmutedoesnt the core who gave the 2nd +2 also does a +1 approved?18:26
*** IlyaE has joined #openstack-meeting-alt18:26
iccha1all cores have +1 approved at any time18:26
denis_makogonesmute, it seems - 3d one18:26
iccha1its when they choose to use it18:26
SlickNikAlso IMHO, it's a good thing. We've caught issues in the past during a second review.18:26
SlickNikSo I suggest keeping it exactly like it is today.18:26
SlickNikAnd not changing this.18:26
esmuteso does that mean we need 3 cores to get a patch merged?18:27
iccha12nd core can approve it18:27
vipuljust 2 cores18:27
SlickNikesmute: Nope, the second +2 also does an approve.18:27
SlickNikso 2 cores.18:27
denis_makogonso, basically, nothing changed18:27
vipulI think it's been working.. let's just keep doing it the way we have18:27
esmuteahh ok.. so this is just to ensure that the core who gave the second +2 also gives a +1 when approving18:28
*** viveknarasimhan has quit IRC18:28
*** dguitarbite has quit IRC18:28
SlickNikesmute: This is a follow up to the conversation some folks had in ATL where they wanted to move to a system that required only 1 core approval.18:28
SlickNikesmute: And I'm clarifying that we're NOT moving to that. :)18:28
cp16netsounds good18:28
esmuteok.. thanks for the clarification SlickNik18:29
*** baoli has quit IRC18:29
*** nati_uen_ has quit IRC18:29
SlickNikOkay, that's pretty much all I had on the follow up.18:29
vipulSlickNik: when is the core standup?18:29
esmuteare you guys doing a hangout?18:30
SlickNikvipul: haven't gotten around to figuring that out just yet. Working on a doodle. Expect a link in your inbox sometime today. :)18:30
vipulok18:30
*** jmcbride has left #openstack-meeting-alt18:30
SlickNikAny other questions?18:30
grapexvipul: I vote for not during my lunch18:30
amcrni vote for grapex's lunch hour18:30
vipulgrapex: how about your yoga hour18:30
cp16netfail18:30
grapexAs a former resident of the third most obese city in America I think us Texans have given up enough of our most precious resource... food.18:31
amcrn;D18:31
esmutegrapex: where did you move to?18:31
SlickNik#topic Open Discussion18:31
*** openstack changes topic to "Open Discussion (Meeting topic: trove)"18:31
*** hub_cap has joined #openstack-meeting-alt18:31
vipuli thought amcrn had something18:31
denis_makogonSlickNik, we missed last section18:31
SlickNikoops, let me refresh18:31
amrithI'll wait on amcrn18:31
SlickNikmy mistake18:31
denis_makogonSlickNik, Clustering python-troveclient Interface18:31
amcrni snuck it in last minute due to the sparse agenda, apologies18:32
grapexFrom San Antonio to Austin. Here all the hip food is in trucks so over-eaters have to run after it.18:32
SlickNik#topic Clustering python-troveclient Interface18:32
*** openstack changes topic to "Clustering python-troveclient Interface (Meeting topic: trove)"18:32
SlickNikamcrn: apologies. the floor is yours.18:32
amcrnso, with the clustering spec ironed out, i was looking into the python-troveclient and quickly found out that modeling heterogenous instances is a tad awkward18:32
amcrn#link https://gist.github.com/amcrn/c4ae2210e9d9864c21fd18:33
denis_makogonyeah, looks pretty huge =)18:33
amcrnso, two questions: does anyone have a better option for the heterogenous case?18:33
amcrndenis_makogon: that's mostly formatting to deal with gist.github.com's weird text-wrap18:34
amcrnand the other question is under the "Thoughts" subheader18:34
*** igor__ has quit IRC18:34
denis_makogonamcrn, can we table it for at least 1-2 day to think about that ?18:34
vipulso nova does something pretty weird with the block-device-mapping argument18:34
grapexamcrn: So is there any other client that can take basically a "vaargs" for some series of values?18:34
hub_capamcrn: i think the other projects just punt on complex stuff in the client18:34
hub_capat least in the cli portion18:34
*** nati_ueno has joined #openstack-meeting-alt18:35
vipulit's not quite json, but an ordered list of thing colon-delimited18:35
vipulhttp://docs.openstack.org/trunk/openstack-ops/content/attach_block_storage.html18:35
amcrnhub_cap: how does something like horizon then make use of that then? raw http request?18:35
SlickNikamcrn: I know the neutron-cli does something similar. They use key=value pairs as args though.18:35
*** igor_ has joined #openstack-meeting-alt18:35
amcrnvipul: nice, thanks for the reference18:35
amcrngrapex: we already take json for configuration-group parameter updates18:35
grapexamcrn: I think I'm kind of ok with the JSON approach18:36
grapexbut it isn't consistent18:36
grapexit seems like a heterogenous cluster is sort of a power user thing though18:36
denis_makogoni guess for now it's a pretty good way to describe complex shell request ( vipul's link )18:36
hub_capamcrn: make it work _in_ the client, not in the cli18:37
hub_capdoes that make sense?18:37
peterstacwhat about allowing the same option to be specified multiple times?18:37
amcrnhub_cap: ah, thanks for the clarification18:37
kevinconwaywe could do something goofy like a bunch of delimeted strings18:37
vipulit's a bit difficult to expect someone to write json in a terminal.. so i would be ok with something like nova18:37
kevinconway--sizes="1,2,3,4"18:37
peterstaci.e.  --flavor=1 --flavor=2 etc.18:37
*** rand738 has quit IRC18:37
cp16netyeah just not in the shell is what hub_cap is saying18:37
amcrnok, so shell assumes homogenous, and if you want heterogenous we can tap into the client18:37
hub_capim ok w that for now18:38
denis_makogonanother question, about volumes18:38
grapexvipul: my issue with the colon delimited list is it still switches from the format typical to the CLI to something different18:38
peterstackevinconway: I thought of that, but it would turn numerics into strings ...18:38
amcrnand whether that's colon delim'd, or json, or whatever, we can hash that out over the coming days18:38
denis_makogondo volume size is required by the default ?18:38
amcrndenis_makogon: the cli claims it isn't, but it is afaik18:38
grapexif it's different JSON seems easier to get right than making it a colon / fabric style approach we'd semi-invent for this.18:38
vipulgrapex: sure.. maybe we need to look at more examples like that to see if there is a precedent..18:38
grapexvipul: +118:39
amcrncool, i'll draw up more examples and drop it in the official channel18:39
denis_makogonamcrn, thanks18:39
SlickNikamcrn: I'm good with making this (heterogenous) work in the client, and punting on the cli till later.18:39
grapexamcrn: Good point18:39
cp16net#agreed18:39
iccha1+118:39
amcrndefinitely all agreed on the cli vs. client thing, thanks guys18:39
hub_capyou might be able to make a subparser for --instance --flavor 1 --blah18:39
SlickNikI think it might be a useful ML question as well.18:39
hub_capand --instance --flavor 2 --blah18:39
kevinconwayhub_cap: yeah that's going to be a super messy subparser i think18:40
* hub_cap is not sure how it works, but think github18:40
hub_caperr git cmd line18:40
SlickNikokay, let's move on.18:40
SlickNikThanks amcrn18:40
kevinconwayi guess you could grab nargs=? and pipe that into another parser18:40
SlickNik#topic Open Discussion18:40
*** openstack changes topic to "Open Discussion (Meeting topic: trove)"18:40
amrith\0/18:40
grapex-1 to a subparser vs just using JSON. I think everyone would be more ok with JSON than having to own something else. :/18:40
SlickNikamrith: go for it.18:40
hub_capamrith: wants to discuss a stickfigure18:41
SnowDustanyone reviewing "vertica datastore" patch ?18:41
amrithTrove Mid-Cycle meetup is going to be on August 20, 21, 22 in Boston/Cambridge.18:41
SnowDustwe need reviews ...!!!18:41
denis_makogonSnowDust, me18:41
amrithIf you are going to attend, please register at18:41
amrithhttps://trove-midcycle-meetup-2014.eventbrite.com18:41
amrithThere are three questions you have to answer (in addition to basic information such as name, email, and telephone number).18:41
amrithWe're working on a location and once we have a better idea on the number of registrations, I will have details like hotels and if required a block reservation.18:41
amrithFinally, if you are arriving on the 19th, please consider coming in a bit early. We're trying to arrange an evening openstack event with the local openstack group. Details to follow.18:41
SnowDustdenis_makogon : thanks ..18:41
*** Youcef_ has joined #openstack-meeting-alt18:41
vipulSnowDust: i'll look later today18:41
kevinconwayamrith: are you organizing a key-signing party?18:41
SnowDustvipul : thx !18:41
kevinconwayi hear those go really well18:41
iccha1thanks for setting it up amrith18:41
amcrnkevinconway: lol18:42
denis_makogonamrith, cool, Cambridge =)18:42
yogeshmehraSlickNik: If you could also give the review comments...You had few in mind, right?18:42
SnowDustamrith: not interested ? :)18:42
yogeshmehrawill help us move faster18:42
amrithkevinconway, I will think about it (very hard)18:42
amrithiccha1, thanks.18:42
cp16netlol18:42
SlickNikyogeshmehra / SnowDust: Yes, will do it today.18:42
SnowDustcp16net : not interested ?18:42
amrithSnowDust, not interested in what?18:42
yogeshmehraawesome....thanks much18:42
* cp16net confused18:43
SnowDustreviews .. on "vertica datastore" patch18:43
amrithkey signing party? no, very interested. I hear that kevinconway is organizing one.18:43
amrithoh, vertica review.18:43
denis_makogoncp16net,  amrith, i guess in reviewing vertica patch18:43
cp16netthats fine its on the list18:43
amrithwill do that later today18:43
*** gokrokve has joined #openstack-meeting-alt18:43
cp16netmy comment was not to you18:43
amrithhave been stuck with a bunch of "stuff" after being on the road for two weeks18:43
amrithSlickNik, I'm done.18:43
SlickNikamrith thanks!18:44
denis_makogoni've got one question18:44
denis_makogoncan i ask for it ?18:44
SlickNikdenis_makogon: sure18:44
SlickNikgo for it.18:44
denis_makogonWhat about troveclient CLI style ?18:44
denis_makogonsince we plan to have cluster-create18:44
cp16netplz elaborate18:44
denis_makogoncp16net, we have now "trove create" call for instances18:45
mattgriffinamrith, details will be added to https://wiki.openstack.org/wiki/Trove/JunoCycleMeetup ?18:45
denis_makogoncp16net, i guest we should move to "trove instance-create"18:45
denis_makogoncp16net, heat as the example18:45
vipuldenis_makogon: +118:45
denis_makogonthey have "heat list" which is going to be deprecated and they have "heat stack-list"18:46
vipulwe might have to support both for a while.. but at least we should introduce instance-create18:46
dougshelley66wasn't there some discussion about trying to move away from the term "instance"? or has that ship sailed?18:46
grapexvipul: Then we can change it to "instance create"18:46
denis_makogonvipul, yes, they will point out to same API call, but will have different signature for awhile18:46
*** betsy has joined #openstack-meeting-alt18:46
cp16netwe need to be mindful of when we can depricate such a thing...18:46
grapexand then after that, back to just "create"... and the cycle will be complete. :)18:46
* cp16net doesnt know the answer to that18:47
cp16netgrapex: lolz back to the beginning?18:47
denis_makogongrapex, we can't use "instance create", it should contain dash18:47
vipulit's a cli.. not an API.. not sure what the 'rules' are18:47
denis_makogoni meant "-"18:47
cp16netvipul: yea18:47
kevinconwaywe need to make sure we don't break the client too18:47
grapexvipul: I thought the rules were "do whatever Nova did"18:47
amcrnas long as the client is versioned, which is fairly trivial, we should be able to do what we want18:47
denis_makogonkevinconway, we wouldn't18:47
kevinconwayso if you mean add an instance-create that mirrors trove create then sure18:47
*** gokrokve has quit IRC18:47
*** Youcef_ is now known as Youcef18:47
denis_makogonkevinconway, yes, that's what i was asking for18:48
vipulgrapex: isn't that what we do anyway18:48
SlickNikbtw, the clis are on a continuous release cycle and don't follow OS milestones.18:48
*** michael-yu has quit IRC18:48
iccha1therehttps://etherpad.openstack.org/p/juno-cross-project-consistency-across-rest-apis18:48
SlickNikSo we have some more leeway with changing them as we see fit.18:48
iccha1i mean https://etherpad.openstack.org/p/juno-cross-project-consistency-across-rest-apis is a good etherpad from the summit18:48
iccha1on cross api consistency18:48
cp16netwhat benifit do we really get from changing the cli18:48
vipulthat's a long etherpad18:48
grapexcp16net: +118:49
denis_makogoncp16net, generic format18:49
cp16netits not generic enough?18:49
cp16netit does what it has to do18:49
denis_makogoncp16net, this questions are came from python-openstackclient and python-openstacksdk18:49
*** ViswaV has quit IRC18:49
cp16netits no the client binding you are talking about18:49
grapexI would rather we have it as it once was than the way we have it now, but I don't really care. I can't imagine anyone who uses it does either beyond some fleeting sense of annoyance it doesn't use their personally preferred convention18:49
cp16netits just the shell cmds which work and i dont really see a reason to change them again18:49
SlickNikafaik, the API is the word set in stone. We have freedom to change the clis as we see fit.18:50
denis_makogoni'm not saying that we should do that, i just wondering what cores are other contributors feeling about that ?18:50
SlickNikBut yes, we probably should look at moving  "trove create" to "trove instance-create" once we have clustering.18:51
vipulthe shell commands are important though.. since 'trove create' seems like the first step thing to do, you're misleading the user into creating a single instance18:51
SlickNikvipul: agreed.18:52
denis_makogonsounds good18:52
amcrnso as a part of the python-troveclient drop, "create" should be moved to "instance-create" ?18:52
denis_makogoni guess this change should land right after/before clustering18:52
denis_makogonamcrn, yes18:52
vipulor at least add 'instance-create' if we want to support both for a while amcrn18:52
amcrni'd say right after, that way clustering can land without impacting existing usecases18:52
kevinconwayi think we have to keep "create" or we version the client18:52
SlickNikamcrn: can we make it a different dependent patchset?18:52
denis_makogonvipul, ++18:52
amcrnSlickNik: sure.18:53
denis_makogonSlickNik, seems like yes18:53
hub_capwhy not leave create = instance-create and add a cluster-create18:53
hub_capsince in the beginning instance was kinda our "primary" resource18:53
grapexhub_cap: +118:53
hub_capand we can fix it in a v218:53
cp16neti'm personally not in favor of changing the cli to object-create18:53
vipulhub_cap: because we have two top level things..18:54
hub_capbut it gives us a way to not muck up the expected behaviro in a _already in trusty tahr system_18:54
denis_makogonhub_cap,  /instance      /clusters18:54
* hub_cap 's parrot squaks18:54
hub_capi get that guys18:54
grapexI mean I think if we wanted to have "blah-create" we should have kept it as "instance create", where we got CLI and suggestions when we tried "instance" without create. It seemed so much easier to reason about back then.18:54
hub_capbut we also have an _expected behavior_18:54
hub_capso we rev the client before we rev the api (odd)18:54
hub_capor ew add cluster-create18:54
grapexI thought one big reason was so we could have a plain "create" echoing the Nova CLI's "boot" command18:54
* hub_cap votes on the easier and more expected one18:55
vipulgrapex: but nova's boot command is all there is .. there is no other type of server you would boot18:55
cp16neti'd be ok adding cluster-create to work differently18:55
vipulwe have two types of 'instances' you can 'boot'18:55
cp16netthat makes sense18:55
kevinconwayvipul: marshmallows18:55
*** krtaylor has joined #openstack-meeting-alt18:55
denis_makogonhub_cap, let me ask nova cores and cinder core what they think about their CLI style18:55
hub_capbut we have an expected behavior too vipul18:56
*** jcoufal has quit IRC18:56
peterstacvipul: +1 and potentially more down the road18:56
vipulsure, which is why i'm saying support both.. add a deprecated warming18:56
hub_capdenis_makogon: what would that accoomplish? im not sure what u mean by that18:56
SlickNikI'm good with supporting both and adding a deprecation warning.18:56
hub_capso yer saying just symlink instance-create to create?18:56
vipulyes18:56
denis_makogonhub_cap, common CLI style across all projects18:56
* hub_cap shrugs why not18:56
amcrni'm ok with that18:56
*** _nadya_ has joined #openstack-meeting-alt18:56
hub_capdenis_makogon: im not sure its needed, looks like we have consensus18:56
*** jcoufal has joined #openstack-meeting-alt18:56
denis_makogonok18:57
*** shakamunyi has quit IRC18:57
*** RaginBaj_ has joined #openstack-meeting-alt18:57
SlickNikOkay, anything else?18:57
denis_makogonif it'll work for all of us then i'm fine with that18:57
* cp16net looks at the otherside of the room18:57
robertmyers#vote no client18:57
grapexrobertmyers: +118:57
robertmyerscurl for all18:57
grapexLet's just wait for the OpenStack SDK18:57
SlickNiklol @ robertmyers18:57
amcrn+118:57
amcrnlol18:57
SlickNik#endmeeting18:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:57
openstackMeeting ended Wed May 21 18:57:53 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-05-21-18.01.html18:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-05-21-18.01.txt18:57
grapexWe'll just copy the client into the Trove repo so people quit bugging us18:57
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-05-21-18.01.log.html18:57
*** RaginBaj_ has quit IRC18:57
SlickNikThanks all!18:58
grapexit won't be a test dep and everything will be happy. :)18:58
cp16netthanks SlickNik18:58
iccha1thanks SlickNik18:58
grapexThanks SlickNik!18:58
*** RaginBaj_ has joined #openstack-meeting-alt18:58
*** mat-lowery has left #openstack-meeting-alt18:59
*** Barker has quit IRC19:01
*** kgriffs|afk is now known as kgriffs19:02
*** betsy has quit IRC19:03
*** harlowja is now known as harlowja_away19:04
*** nati_ueno has quit IRC19:04
*** betsy has joined #openstack-meeting-alt19:05
*** nati_ueno has joined #openstack-meeting-alt19:05
*** zns has joined #openstack-meeting-alt19:06
*** IlyaE has quit IRC19:07
*** kenhui has quit IRC19:07
*** IlyaE has joined #openstack-meeting-alt19:07
*** kenhui has joined #openstack-meeting-alt19:07
*** betsy has quit IRC19:09
*** dims has joined #openstack-meeting-alt19:09
*** betsy has joined #openstack-meeting-alt19:10
*** ramishra has joined #openstack-meeting-alt19:13
*** nati_ueno has quit IRC19:13
*** sarob has quit IRC19:13
*** adrian_otto1 is now known as adrian_otto19:14
*** IlyaE has quit IRC19:17
*** arnaud has quit IRC19:17
*** kenhui has quit IRC19:20
*** Barker has joined #openstack-meeting-alt19:21
*** kenhui has joined #openstack-meeting-alt19:22
*** ramishra has quit IRC19:22
*** harlowja_away is now known as harlowja19:27
*** ranjitha has quit IRC19:31
*** NehaV has quit IRC19:32
*** NehaV has joined #openstack-meeting-alt19:32
*** IlyaE has joined #openstack-meeting-alt19:33
*** arnaud has joined #openstack-meeting-alt19:33
*** arnaud has quit IRC19:33
*** arnaud has joined #openstack-meeting-alt19:37
*** SnowDust has quit IRC19:38
*** satish_ has joined #openstack-meeting-alt19:38
*** satish has quit IRC19:41
*** nikhil|afk is now known as nikhil__19:41
*** jcru has left #openstack-meeting-alt19:42
*** gokrokve has joined #openstack-meeting-alt19:43
*** gokrokve_ has joined #openstack-meeting-alt19:45
*** eguz has quit IRC19:47
*** eghobo has joined #openstack-meeting-alt19:47
*** gokrokve has quit IRC19:48
*** kenhui has quit IRC19:48
*** dprince has quit IRC19:49
*** hub_cap has left #openstack-meeting-alt19:49
*** gokrokve_ has quit IRC19:50
*** IlyaE has quit IRC19:50
*** esker has quit IRC19:50
*** Sukhdev has joined #openstack-meeting-alt19:51
*** eddie_ has quit IRC19:53
*** satish has joined #openstack-meeting-alt19:56
*** eddie_ has joined #openstack-meeting-alt19:57
*** satish_ has quit IRC19:57
*** lsmola2 has joined #openstack-meeting-alt20:01
*** cp16net has left #openstack-meeting-alt20:04
*** xarses has quit IRC20:05
*** _nadya_ has quit IRC20:06
*** satish_ has joined #openstack-meeting-alt20:06
*** arnaud has quit IRC20:07
*** rueben has quit IRC20:09
*** satish has quit IRC20:10
*** rueben has joined #openstack-meeting-alt20:10
*** ramishra has joined #openstack-meeting-alt20:14
*** jeblair has joined #openstack-meeting-alt20:16
*** betsy has quit IRC20:17
*** jrist_ has joined #openstack-meeting-alt20:19
*** simon_chang has quit IRC20:19
*** james_li has quit IRC20:21
*** xarses has joined #openstack-meeting-alt20:21
*** jrist has quit IRC20:21
*** jrist_ is now known as jrist20:21
*** arnaud has joined #openstack-meeting-alt20:23
*** ccrouch has left #openstack-meeting-alt20:23
*** james_li has joined #openstack-meeting-alt20:23
*** arnaud has quit IRC20:26
*** eankutse has quit IRC20:27
*** ranjitha has joined #openstack-meeting-alt20:27
*** arnaud has joined #openstack-meeting-alt20:29
*** Rajeev has quit IRC20:29
*** zns has quit IRC20:29
*** arnaud has quit IRC20:30
*** satish has joined #openstack-meeting-alt20:30
*** arnaud has joined #openstack-meeting-alt20:30
*** IlyaE has joined #openstack-meeting-alt20:31
*** arnaud has quit IRC20:31
*** arnaud has joined #openstack-meeting-alt20:31
*** baoli has joined #openstack-meeting-alt20:32
*** satish_ has quit IRC20:32
*** markwash_ has joined #openstack-meeting-alt20:33
*** markwash has quit IRC20:34
*** caleb_ has joined #openstack-meeting-alt20:34
*** markwash has joined #openstack-meeting-alt20:34
*** colinmcnamara has joined #openstack-meeting-alt20:35
*** ramishra has quit IRC20:35
*** zns has joined #openstack-meeting-alt20:35
*** zns has quit IRC20:35
*** zns has joined #openstack-meeting-alt20:36
*** _nadya_ has joined #openstack-meeting-alt20:36
*** markwash_ has quit IRC20:37
*** jjmb has quit IRC20:42
*** gokrokve has joined #openstack-meeting-alt20:43
*** jjmb has joined #openstack-meeting-alt20:43
*** michael-yu has joined #openstack-meeting-alt20:43
*** gokrokve has quit IRC20:48
*** phil_h has quit IRC20:51
*** SumitNaiksatam has quit IRC20:52
*** zns has quit IRC20:57
*** chuckC has quit IRC20:57
*** jmontemayor_ has joined #openstack-meeting-alt21:03
*** zns has joined #openstack-meeting-alt21:03
*** jmontemayor_ has quit IRC21:03
*** ranjitha has quit IRC21:04
*** jmontemayor_ has joined #openstack-meeting-alt21:04
*** gokrokve has joined #openstack-meeting-alt21:04
*** michael-yu has quit IRC21:05
*** colinmcnamara has quit IRC21:05
*** ranjitha has joined #openstack-meeting-alt21:05
*** jmontemayor has quit IRC21:05
*** michael-yu has joined #openstack-meeting-alt21:06
*** jasonb365 has quit IRC21:07
*** jasonb365_ has joined #openstack-meeting-alt21:07
*** arnaud has quit IRC21:07
*** sarob has joined #openstack-meeting-alt21:07
*** otherwiseguy has quit IRC21:07
*** jeckersb is now known as jeckersb_gone21:07
*** jdob has quit IRC21:07
*** arnaud has joined #openstack-meeting-alt21:09
*** amcrn_ has joined #openstack-meeting-alt21:10
*** otherwiseguy has joined #openstack-meeting-alt21:10
*** pdmars has quit IRC21:11
*** arnaud has quit IRC21:11
*** arnaud has joined #openstack-meeting-alt21:11
*** arnaud has quit IRC21:11
*** balajiiyer has joined #openstack-meeting-alt21:12
*** arnaud has joined #openstack-meeting-alt21:12
*** baoli has quit IRC21:12
*** arnaud has quit IRC21:13
*** balajiiyer has quit IRC21:13
*** baoli has joined #openstack-meeting-alt21:13
*** amcrn has quit IRC21:13
*** nati_ueno has joined #openstack-meeting-alt21:13
*** rueben has quit IRC21:14
*** xarses has quit IRC21:15
*** lsmola2 has quit IRC21:15
*** mfer has quit IRC21:18
*** arnaud has joined #openstack-meeting-alt21:18
*** arnaud has quit IRC21:19
*** jcoufal has quit IRC21:21
*** betsy has joined #openstack-meeting-alt21:25
*** nati_ueno has quit IRC21:26
*** nati_ueno has joined #openstack-meeting-alt21:26
*** rueben has joined #openstack-meeting-alt21:27
*** xarses has joined #openstack-meeting-alt21:27
*** chuckC has joined #openstack-meeting-alt21:28
*** rueben has quit IRC21:28
*** denis_makogon has quit IRC21:29
*** jmontemayor_ has quit IRC21:30
*** julim has quit IRC21:32
*** IlyaE has quit IRC21:33
*** balajiiyer1 has joined #openstack-meeting-alt21:34
*** IlyaE has joined #openstack-meeting-alt21:34
*** rueben has joined #openstack-meeting-alt21:35
*** jmontemayor has joined #openstack-meeting-alt21:36
*** caleb_ has quit IRC21:36
*** ericgoncz has quit IRC21:37
*** balajiiyer1 has left #openstack-meeting-alt21:39
*** IlyaE has quit IRC21:41
*** andreaf has joined #openstack-meeting-alt21:41
*** jamie_h has quit IRC21:42
*** kenhui has joined #openstack-meeting-alt21:44
*** SumitNaiksatam has joined #openstack-meeting-alt21:47
*** mwagner_lap has quit IRC21:47
*** SumitNaiksatam has quit IRC21:49
*** ericgoncz has joined #openstack-meeting-alt21:51
*** satish has quit IRC21:51
*** Sukhdev has quit IRC21:51
*** _nadya_ has quit IRC21:52
*** yogeshmehra has quit IRC21:55
*** yogeshmehra has joined #openstack-meeting-alt21:56
*** yogeshme_ has joined #openstack-meeting-alt21:57
*** yogeshmehra has quit IRC21:57
*** luizfar has quit IRC21:58
*** esp has left #openstack-meeting-alt22:01
*** Barker has quit IRC22:01
*** zns has quit IRC22:01
*** yogeshme_ has quit IRC22:02
*** yogeshmehra has joined #openstack-meeting-alt22:02
*** kgriffs is now known as kgriffs|afk22:03
*** yogeshmehra has quit IRC22:04
*** ericgoncz has quit IRC22:05
*** yogeshmehra has joined #openstack-meeting-alt22:05
*** krtaylor has quit IRC22:05
*** carl_baldwin has quit IRC22:09
*** NehaV has quit IRC22:09
*** yogeshmehra has quit IRC22:09
*** shanks has quit IRC22:10
*** spzala has quit IRC22:10
*** SumitNaiksatam has joined #openstack-meeting-alt22:12
*** gokrokve has quit IRC22:12
*** SumitNaiksatam has quit IRC22:12
*** shanks has joined #openstack-meeting-alt22:13
*** robertmyers has quit IRC22:13
*** gondoi is now known as zz_gondoi22:14
*** dims has quit IRC22:18
*** _nadya_ has joined #openstack-meeting-alt22:19
*** yamahata has joined #openstack-meeting-alt22:19
*** sarob has quit IRC22:20
*** sarob has joined #openstack-meeting-alt22:21
*** sarob_ has joined #openstack-meeting-alt22:22
*** Obulpathi has quit IRC22:22
*** markmcclain has quit IRC22:22
*** markmcclain has joined #openstack-meeting-alt22:23
*** eankutse has joined #openstack-meeting-alt22:23
*** rueben has quit IRC22:24
*** sarob has quit IRC22:25
*** rueben has joined #openstack-meeting-alt22:25
*** sarob_ has quit IRC22:26
*** eankutse has quit IRC22:26
*** eankutse has joined #openstack-meeting-alt22:26
*** laurelm has quit IRC22:28
*** troytoman has joined #openstack-meeting-alt22:28
*** amytron has quit IRC22:29
*** chuckC has quit IRC22:29
*** jmontemayor has quit IRC22:29
*** james_li has quit IRC22:29
*** _nadya__ has joined #openstack-meeting-alt22:30
*** laurelm has joined #openstack-meeting-alt22:30
*** colinmcnamara has joined #openstack-meeting-alt22:31
*** sanek11 has joined #openstack-meeting-alt22:31
*** Adri2000_ has joined #openstack-meeting-alt22:31
*** Adri2000_ has quit IRC22:31
*** Adri2000_ has joined #openstack-meeting-alt22:31
*** cgoncalv1s has joined #openstack-meeting-alt22:31
*** zns has joined #openstack-meeting-alt22:32
*** SumitNaiksatam has joined #openstack-meeting-alt22:32
*** rueben_ has joined #openstack-meeting-alt22:32
*** rueben_ has quit IRC22:33
*** Youcef_ has joined #openstack-meeting-alt22:33
*** radix has quit IRC22:33
*** notmyname_ has joined #openstack-meeting-alt22:33
*** james_li has joined #openstack-meeting-alt22:33
*** troytoman_ has quit IRC22:33
*** radix has joined #openstack-meeting-alt22:33
*** notmyname has quit IRC22:33
*** notmyname_ is now known as notmyname22:34
*** cyli_ has joined #openstack-meeting-alt22:34
*** kgriffs|afk has quit IRC22:34
*** igor__ has joined #openstack-meeting-alt22:34
*** johnthetubaguy_ has joined #openstack-meeting-alt22:34
*** kgriffs|afk has joined #openstack-meeting-alt22:36
*** rueben has quit IRC22:36
*** kgriffs|afk is now known as kgriffs22:36
*** amcrn_ has quit IRC22:36
*** jasonb365_ has quit IRC22:36
*** dansmith_ has joined #openstack-meeting-alt22:37
*** Adri2000 has quit IRC22:38
*** _nadya_ has quit IRC22:38
*** johnthetubaguy has quit IRC22:38
*** cyli has quit IRC22:38
*** agordeev has quit IRC22:38
*** anteaya has quit IRC22:38
*** cgoncalves has quit IRC22:38
*** Youcef has quit IRC22:38
*** dansmith has quit IRC22:38
*** igor_ has quit IRC22:38
*** johnthetubaguy_ is now known as johnthetubaguy22:38
*** dansmith_ is now known as dansmith22:38
*** colinmcnamara has quit IRC22:39
*** cyli_ is now known as cyli22:40
*** kenhui has quit IRC22:40
*** gokrokve has joined #openstack-meeting-alt22:43
*** tdruiva_ has joined #openstack-meeting-alt22:44
*** imsplitb1t has joined #openstack-meeting-alt22:47
*** tdruiva has quit IRC22:47
*** gokrokve has quit IRC22:47
*** IlyaE has joined #openstack-meeting-alt22:48
*** saurabhs has quit IRC22:49
*** akuznetsov has quit IRC22:49
*** richm has quit IRC22:49
*** nelsnelson has quit IRC22:49
*** rwsu has quit IRC22:49
*** isviridov has quit IRC22:49
*** hgedikli_ has joined #openstack-meeting-alt22:50
*** mattgriffin has quit IRC22:50
*** michael-yu has quit IRC22:53
*** otherwiseguy has quit IRC22:53
*** hgedikli has quit IRC22:54
*** matrohon has quit IRC22:54
*** eankutse has quit IRC22:56
*** anteaya has joined #openstack-meeting-alt22:56
*** michael-yu has joined #openstack-meeting-alt22:57
*** eguz has joined #openstack-meeting-alt22:59
*** eguz has quit IRC22:59
*** imsplitbit has quit IRC22:59
*** vkmc has quit IRC22:59
*** otherwiseguy has joined #openstack-meeting-alt23:00
*** banix has quit IRC23:01
*** eghobo has quit IRC23:02
*** ranjitha has quit IRC23:02
*** baoli has quit IRC23:06
*** nosnos has joined #openstack-meeting-alt23:10
*** richm has joined #openstack-meeting-alt23:11
*** jecarey has quit IRC23:11
*** saurabhs has joined #openstack-meeting-alt23:11
*** rwsu has joined #openstack-meeting-alt23:12
*** akuznetsov has joined #openstack-meeting-alt23:13
*** nelsnelson has joined #openstack-meeting-alt23:13
*** isviridov has joined #openstack-meeting-alt23:13
*** mwagner_lap has joined #openstack-meeting-alt23:14
*** markwash has quit IRC23:15
*** kevinconway has quit IRC23:15
*** terryw has joined #openstack-meeting-alt23:18
*** otherwiseguy has quit IRC23:21
*** andreaf has quit IRC23:22
*** chuckC has joined #openstack-meeting-alt23:23
*** terryw has quit IRC23:25
*** david-lyle has quit IRC23:26
*** zns has quit IRC23:26
*** yamahata has quit IRC23:29
*** nati_ueno has quit IRC23:30
*** harlowja has quit IRC23:33
*** harlowja_ has joined #openstack-meeting-alt23:33
*** mencito has joined #openstack-meeting-alt23:34
*** james_li has quit IRC23:35
*** james_li has joined #openstack-meeting-alt23:37
*** mencito_ has joined #openstack-meeting-alt23:40
*** mencito has quit IRC23:41
*** james_li has quit IRC23:41
*** morganfainberg_Z is now known as morganfainberg23:42
*** grapex has quit IRC23:42
*** gokrokve has joined #openstack-meeting-alt23:44
*** gokrokve has quit IRC23:49
*** nati_ueno has joined #openstack-meeting-alt23:50
*** chuckC has quit IRC23:52

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!