Wednesday, 2014-04-09

*** colinmcn_ has joined #openstack-meeting-alt00:01
*** malini has quit IRC00:02
*** malini has joined #openstack-meeting-alt00:03
*** rmoe has quit IRC00:06
*** markmcclain1 has joined #openstack-meeting-alt00:09
*** markmcclain1 has quit IRC00:09
*** noslzzp has joined #openstack-meeting-alt00:09
*** markmcclain1 has joined #openstack-meeting-alt00:09
*** markmcclain has quit IRC00:12
*** michael-yu has quit IRC00:13
*** malini has quit IRC00:17
*** MarkAtwood has quit IRC00:18
*** adrian_otto has left #openstack-meeting-alt00:20
*** Sukhdev has quit IRC00:20
*** rmoe has joined #openstack-meeting-alt00:20
*** Barker has joined #openstack-meeting-alt00:22
*** markmcclain1 has quit IRC00:23
*** michael-yu has joined #openstack-meeting-alt00:24
*** banix has joined #openstack-meeting-alt00:24
*** Hao has joined #openstack-meeting-alt00:25
*** Hao has quit IRC00:29
*** esker has joined #openstack-meeting-alt00:31
*** samstav has quit IRC00:34
*** caleb_ has joined #openstack-meeting-alt00:36
*** andreaf has quit IRC00:37
*** mattgriffin has quit IRC00:40
*** malini has joined #openstack-meeting-alt00:40
*** dansmith has quit IRC00:48
*** ErikB1 has joined #openstack-meeting-alt00:48
*** dansmith has joined #openstack-meeting-alt00:49
*** banix has quit IRC00:49
*** colinmcnamara has quit IRC00:51
*** michael-yu has quit IRC00:52
*** colinmcn_ has quit IRC00:52
*** SumitNaiksatam has quit IRC00:53
*** derekh has quit IRC00:53
*** yamahata has quit IRC00:54
*** SumitNaiksatam has joined #openstack-meeting-alt00:57
*** yamamoto_ has joined #openstack-meeting-alt01:03
*** colinmcnamara has joined #openstack-meeting-alt01:07
*** ErikB1 has quit IRC01:09
*** colinmcnamara has quit IRC01:10
*** SumitNaiksatam has quit IRC01:15
*** Michalik has quit IRC01:17
*** banix has joined #openstack-meeting-alt01:22
*** Michalik has joined #openstack-meeting-alt01:24
*** kevinconway has quit IRC01:26
*** eghobo has quit IRC01:28
*** jjmb has joined #openstack-meeting-alt01:28
*** nosnos has joined #openstack-meeting-alt01:29
*** jjmb1 has joined #openstack-meeting-alt01:31
*** jjmb2 has joined #openstack-meeting-alt01:32
*** richm has quit IRC01:32
*** jjmb has quit IRC01:33
*** mozawa has joined #openstack-meeting-alt01:34
*** jjmb1 has quit IRC01:35
*** mattgriffin has joined #openstack-meeting-alt01:37
*** Barker has quit IRC01:41
*** gokrokve has joined #openstack-meeting-alt01:42
*** walker_ has joined #openstack-meeting-alt01:44
*** walker_ has quit IRC01:44
*** walker_ has joined #openstack-meeting-alt01:45
*** walker_ has quit IRC01:46
*** malini has quit IRC01:50
*** walker_ has joined #openstack-meeting-alt01:54
*** walker_ has quit IRC01:54
*** venkatesh has joined #openstack-meeting-alt01:54
*** walker_ has joined #openstack-meeting-alt01:56
*** MarkAtwood has joined #openstack-meeting-alt01:59
*** ramashri_ has quit IRC02:02
*** caleb_ has quit IRC02:03
*** caleb_ has joined #openstack-meeting-alt02:04
*** walker_ has quit IRC02:04
*** walker_ has joined #openstack-meeting-alt02:05
*** Hao has joined #openstack-meeting-alt02:07
*** esker has quit IRC02:08
*** esker has joined #openstack-meeting-alt02:09
*** mwagner_lap has quit IRC02:10
*** zhiyan is now known as zhiyan_02:11
*** Hao has quit IRC02:11
*** zhiyan_ is now known as zhiyan02:12
*** venkatesh has quit IRC02:16
*** venkatesh has joined #openstack-meeting-alt02:16
*** caleb_ has quit IRC02:19
*** yamahata has joined #openstack-meeting-alt02:22
*** xuhanp has joined #openstack-meeting-alt02:24
*** caleb_ has joined #openstack-meeting-alt02:25
*** julim has quit IRC02:26
*** coolsvap has joined #openstack-meeting-alt02:33
*** colinmcnamara has joined #openstack-meeting-alt02:33
*** demorris has joined #openstack-meeting-alt02:34
*** doug_shelley66 has quit IRC02:34
*** woodster1 has joined #openstack-meeting-alt02:34
*** woodster1 has joined #openstack-meeting-alt02:35
*** Guest98185 is now known as redrobot02:36
*** kevinconway has joined #openstack-meeting-alt02:37
*** banix has quit IRC02:39
*** IlyaE has quit IRC02:43
*** samstav has joined #openstack-meeting-alt02:44
*** gyee has quit IRC02:47
*** bdpayne has quit IRC02:48
*** venkatesh has quit IRC02:50
*** Hao has joined #openstack-meeting-alt02:50
*** arnaud__ has quit IRC02:51
*** Hao has quit IRC02:52
*** yamamoto_ has quit IRC02:52
*** morazi has quit IRC02:54
*** marun has quit IRC02:55
*** malini has joined #openstack-meeting-alt02:57
*** malini has joined #openstack-meeting-alt02:57
*** colinmcnamara has quit IRC02:57
*** ramashri has joined #openstack-meeting-alt02:58
*** banix has joined #openstack-meeting-alt03:00
*** malini has quit IRC03:01
*** harlowja is now known as harlowja_away03:12
*** coolsvap has quit IRC03:12
*** cjellick has quit IRC03:13
*** tedross has joined #openstack-meeting-alt03:17
*** david-lyle has joined #openstack-meeting-alt03:18
*** kevinconway has quit IRC03:19
*** eghobo has joined #openstack-meeting-alt03:19
*** balajiiyer has joined #openstack-meeting-alt03:20
*** balajiiyer has left #openstack-meeting-alt03:21
*** rmoe has quit IRC03:25
*** tedross has quit IRC03:26
*** nosnos has quit IRC03:26
*** coolsvap1 has joined #openstack-meeting-alt03:27
*** coolsvap1 has quit IRC03:27
*** coolsvap has joined #openstack-meeting-alt03:28
*** balajiiyer has joined #openstack-meeting-alt03:29
*** balajiiyer has left #openstack-meeting-alt03:30
*** amcrn has quit IRC03:30
*** samstav has quit IRC03:32
*** rmoe has joined #openstack-meeting-alt03:34
*** yamahata has quit IRC03:35
*** banix has quit IRC03:37
*** jecarey_ has joined #openstack-meeting-alt03:56
*** rpodolyaka1 has joined #openstack-meeting-alt04:04
*** chandan_kumar has joined #openstack-meeting-alt04:04
*** zhiyan is now known as zhiyan_04:06
*** malini has joined #openstack-meeting-alt04:07
*** walker_ has quit IRC04:16
*** nosnos has joined #openstack-meeting-alt04:25
*** saurabhs has left #openstack-meeting-alt04:28
*** SumitNaiksatam has joined #openstack-meeting-alt04:30
*** woodster1 has quit IRC04:31
*** demorris has quit IRC04:32
*** mwagner_lap has joined #openstack-meeting-alt04:39
*** ramashri has quit IRC04:41
*** amytron has joined #openstack-meeting-alt04:56
*** malini has quit IRC04:58
*** HenryG has quit IRC04:59
*** malini has joined #openstack-meeting-alt05:00
*** chandan_kumar has quit IRC05:00
*** akuznetsov has joined #openstack-meeting-alt05:05
*** chandan_kumar has joined #openstack-meeting-alt05:14
*** caleb_ has quit IRC05:15
*** IlyaE has joined #openstack-meeting-alt05:25
*** zhiyan_ is now known as zhiyan05:31
*** gokrokve has quit IRC05:32
*** amytron has quit IRC05:35
*** _nadya_ has joined #openstack-meeting-alt05:44
*** gokrokve_ has joined #openstack-meeting-alt05:44
*** _nadya_ has quit IRC05:46
*** doug_shelley66 has joined #openstack-meeting-alt05:50
*** _nadya_ has joined #openstack-meeting-alt06:04
*** sirushti has quit IRC06:08
*** _sirushti has joined #openstack-meeting-alt06:09
*** _sirushti is now known as sirushti06:09
*** rpodolyaka1 has quit IRC06:14
*** julienvey has joined #openstack-meeting-alt06:16
*** ttrumm has joined #openstack-meeting-alt06:17
*** yamahata has joined #openstack-meeting-alt06:17
*** yamahata__ has joined #openstack-meeting-alt06:18
*** yamahata has quit IRC06:20
*** eghobo has quit IRC06:22
*** yogesh has joined #openstack-meeting-alt06:28
*** rpodolyaka1 has joined #openstack-meeting-alt06:28
*** alex_didenko has joined #openstack-meeting-alt06:28
*** julienvey has quit IRC06:30
*** rpodolyaka1 has quit IRC06:31
*** _nadya_ has quit IRC06:35
*** gokrokve_ has quit IRC06:36
*** _nadya_ has joined #openstack-meeting-alt06:39
*** _nadya_ has quit IRC06:41
*** IlyaE has quit IRC06:48
*** venkatesh has joined #openstack-meeting-alt06:49
*** venkatesh has quit IRC06:51
*** malini has quit IRC06:52
*** jtomasek has joined #openstack-meeting-alt07:02
*** yamahata__ has quit IRC07:03
*** flaper87|afk is now known as flaper8707:06
*** jcoufal has joined #openstack-meeting-alt07:08
*** malini has joined #openstack-meeting-alt07:10
*** nwidell has joined #openstack-meeting-alt07:16
*** yamamoto_ has joined #openstack-meeting-alt07:20
*** ttrumm has quit IRC07:23
*** ttrumm has joined #openstack-meeting-alt07:24
*** jgallard has joined #openstack-meeting-alt07:28
*** coolsvap is now known as coolsvap_away07:30
*** mattgriffin has quit IRC07:32
*** rpodolyaka1 has joined #openstack-meeting-alt07:32
*** gokrokve has joined #openstack-meeting-alt07:36
*** rpodolyaka1 has quit IRC07:36
*** coolsvap_away is now known as coolsvap07:41
*** gokrokve has quit IRC07:41
*** akuznetsov has quit IRC07:46
*** nwidell has quit IRC07:49
*** akuznetsov has joined #openstack-meeting-alt07:52
*** safchain has joined #openstack-meeting-alt08:04
*** nwidell has joined #openstack-meeting-alt08:05
*** nacim has joined #openstack-meeting-alt08:06
*** julienvey has joined #openstack-meeting-alt08:06
*** julienvey has quit IRC08:09
*** julienve_ has joined #openstack-meeting-alt08:10
*** nwidell has joined #openstack-meeting-alt08:12
*** julienve_ has quit IRC08:14
*** d0ugal has quit IRC08:18
*** d0ugal has joined #openstack-meeting-alt08:21
*** d0ugal has quit IRC08:21
*** d0ugal has joined #openstack-meeting-alt08:21
*** doug_shelley66 has quit IRC08:30
*** rpodolyaka1 has joined #openstack-meeting-alt08:32
*** markwash has quit IRC08:35
*** julienvey has joined #openstack-meeting-alt08:35
*** rpodolyaka1 has quit IRC08:36
*** gokrokve has joined #openstack-meeting-alt08:37
*** gokrokve has quit IRC08:42
*** yogesh has quit IRC08:46
*** malini has quit IRC08:46
*** yamahata has joined #openstack-meeting-alt08:47
*** _nadya_ has joined #openstack-meeting-alt08:49
*** chandan_kumar has quit IRC08:49
*** coolsvap is now known as coolsvap|afk08:52
*** yamamoto_ has quit IRC08:55
*** chandan_kumar has joined #openstack-meeting-alt09:03
*** coolsvap|afk is now known as coolsvap09:05
*** overlayer has joined #openstack-meeting-alt09:09
*** david-lyle has quit IRC09:20
*** doug_shelley66 has joined #openstack-meeting-alt09:31
*** gokrokve has joined #openstack-meeting-alt09:38
*** ttrumm has quit IRC09:41
*** gokrokve has quit IRC09:42
*** akuznetsov has quit IRC09:43
*** zhiyan is now known as zhiyan_09:43
*** dmakogon_ is now known as denis_makogon09:44
*** mozawa has quit IRC09:47
*** _nadya_ has quit IRC09:54
*** chandan_kumar_ has joined #openstack-meeting-alt10:03
*** julienvey has quit IRC10:05
*** jgallard has quit IRC10:06
*** chandan_kumar has quit IRC10:06
*** nwidell has quit IRC10:09
*** doug_shelley66 has quit IRC10:10
*** akuznetsov has joined #openstack-meeting-alt10:10
*** ttrumm has joined #openstack-meeting-alt10:12
*** ttrumm has quit IRC10:16
*** ttrumm has joined #openstack-meeting-alt10:17
*** nwidell has joined #openstack-meeting-alt10:18
*** xuhanp has quit IRC10:20
*** rpodolyaka1 has joined #openstack-meeting-alt10:32
*** chandan_kumar_ has quit IRC10:32
*** derekh has joined #openstack-meeting-alt10:32
*** rpodolyaka1 has quit IRC10:36
*** coolsvap is now known as coolsvap|afk10:38
*** gokrokve has joined #openstack-meeting-alt10:39
*** eloib_ has quit IRC10:39
*** gokrokve has quit IRC10:43
*** eanxgeek|log is now known as eanxgeek10:43
*** nwidell has quit IRC10:44
*** dosaboy has quit IRC10:49
*** dosaboy has joined #openstack-meeting-alt10:50
*** vk has quit IRC10:57
*** chandan_kumar_ has joined #openstack-meeting-alt10:58
*** julienvey has joined #openstack-meeting-alt11:06
*** julienvey has quit IRC11:07
*** HenryG has joined #openstack-meeting-alt11:07
*** julienvey has joined #openstack-meeting-alt11:08
*** vk has joined #openstack-meeting-alt11:09
*** julienvey has quit IRC11:12
*** julienvey has joined #openstack-meeting-alt11:22
*** baoli has quit IRC11:25
*** julienvey has quit IRC11:27
*** julienvey has joined #openstack-meeting-alt11:28
*** julim has joined #openstack-meeting-alt11:28
*** ttrumm has quit IRC11:33
*** jaypipes has quit IRC11:33
*** ttrumm has joined #openstack-meeting-alt11:34
*** tsufiev has left #openstack-meeting-alt11:45
*** baoli has joined #openstack-meeting-alt11:53
*** ErikB1 has joined #openstack-meeting-alt11:53
*** coolsvap|afk is now known as coolsvap11:57
*** sballe_ has quit IRC12:01
*** d0ugal_ has joined #openstack-meeting-alt12:04
*** d0ugal has quit IRC12:07
*** zhiyan_ is now known as zhiyan12:10
*** lblanchard has joined #openstack-meeting-alt12:12
*** dprince has joined #openstack-meeting-alt12:13
*** jecarey_ has quit IRC12:14
*** demorris has joined #openstack-meeting-alt12:14
*** tedross has joined #openstack-meeting-alt12:15
*** pdmars has joined #openstack-meeting-alt12:20
*** d0ugal_ is now known as d0ugal12:23
*** aostapenko has joined #openstack-meeting-alt12:26
*** lenrow has joined #openstack-meeting-alt12:28
*** lenrow_ has quit IRC12:31
*** jecarey has joined #openstack-meeting-alt12:33
*** nacim has quit IRC12:37
*** Haiying has joined #openstack-meeting-alt12:37
*** phil_h has joined #openstack-meeting-alt12:39
*** jgallard has joined #openstack-meeting-alt12:39
*** gokrokve has joined #openstack-meeting-alt12:40
*** gokrokve has quit IRC12:45
*** ErikB1 has quit IRC12:45
*** jprovazn has joined #openstack-meeting-alt12:45
*** demorris has quit IRC12:46
*** jdob has joined #openstack-meeting-alt12:50
*** spzala has joined #openstack-meeting-alt12:51
*** markvoelker has quit IRC12:54
*** markvoelker has joined #openstack-meeting-alt12:55
*** nacim has joined #openstack-meeting-alt12:57
*** woodster1 has joined #openstack-meeting-alt13:02
*** woodster1 has quit IRC13:03
*** woodster1 has joined #openstack-meeting-alt13:03
*** sgordon has joined #openstack-meeting-alt13:04
*** mwagner_lap has quit IRC13:06
*** kgriffs|afk is now known as kgriffs13:07
*** sc68cal has quit IRC13:14
*** nosnos has quit IRC13:14
*** tedchang has joined #openstack-meeting-alt13:15
*** eankutse has joined #openstack-meeting-alt13:16
*** thang_ has joined #openstack-meeting-alt13:17
*** eankutse has quit IRC13:17
*** eankutse has joined #openstack-meeting-alt13:17
*** coolsvap is now known as coolsvap|afk13:18
*** coolsvap|afk is now known as coolsvap13:20
*** sc68cal has joined #openstack-meeting-alt13:21
*** coolsvap is now known as coolsvap|afk13:22
*** Hao has joined #openstack-meeting-alt13:22
*** sgordon has left #openstack-meeting-alt13:23
*** ameade has joined #openstack-meeting-alt13:24
*** balajiiyer has joined #openstack-meeting-alt13:27
*** balajiiyer has quit IRC13:27
*** balajiiyer has joined #openstack-meeting-alt13:27
*** kgriffs is now known as kgriffs|afk13:32
*** zz_gondoi is now known as gondoi13:34
*** samstav has joined #openstack-meeting-alt13:35
*** gokrokve has joined #openstack-meeting-alt13:41
*** yamamoto has joined #openstack-meeting-alt13:42
*** Barker has joined #openstack-meeting-alt13:43
*** julim is now known as julim_WFH13:43
*** denis_makogon has quit IRC13:44
*** gokrokve has quit IRC13:45
*** chandan_kumar_ has quit IRC13:46
*** thang_ has quit IRC13:48
*** thang_ has joined #openstack-meeting-alt13:49
*** xuhanp has joined #openstack-meeting-alt13:49
*** Barker has quit IRC13:49
*** andreaf has joined #openstack-meeting-alt13:50
*** zns has joined #openstack-meeting-alt13:53
*** yamahata has quit IRC13:53
*** chandan_kumar_ has joined #openstack-meeting-alt13:53
*** yamamoto has quit IRC13:56
*** jcoufal has quit IRC13:59
*** jcoufal has joined #openstack-meeting-alt14:00
*** Haiying has quit IRC14:04
*** Haiying has joined #openstack-meeting-alt14:04
*** amytron has joined #openstack-meeting-alt14:04
*** gokrokve has joined #openstack-meeting-alt14:06
*** dianefleming has joined #openstack-meeting-alt14:06
*** mattgriffin has joined #openstack-meeting-alt14:08
*** ttrumm has quit IRC14:09
*** demorris has joined #openstack-meeting-alt14:09
*** Haiying has quit IRC14:12
*** Barker has joined #openstack-meeting-alt14:12
*** boh_ricky has quit IRC14:13
*** mozawa has joined #openstack-meeting-alt14:13
*** yamamoto has joined #openstack-meeting-alt14:14
*** walker_ has joined #openstack-meeting-alt14:16
*** kevinconway has joined #openstack-meeting-alt14:17
*** pballand has joined #openstack-meeting-alt14:17
*** kevinconway has quit IRC14:23
*** pballand has quit IRC14:24
*** kevinconway has joined #openstack-meeting-alt14:25
*** saju_m has joined #openstack-meeting-alt14:26
*** gokrokve has quit IRC14:26
*** mwagner_lap has joined #openstack-meeting-alt14:27
*** bill_az has joined #openstack-meeting-alt14:28
*** gokrokve has joined #openstack-meeting-alt14:32
*** bill_az_ has joined #openstack-meeting-alt14:33
*** bill_az has quit IRC14:33
*** katyafervent is now known as katyafervent_awa14:36
*** yamahata has joined #openstack-meeting-alt14:37
*** kgriffs|afk is now known as kgriffs14:37
*** katyafervent_awa is now known as katyafervent14:40
*** caleb_ has joined #openstack-meeting-alt14:44
*** akuznetsov has quit IRC14:44
*** TravT has quit IRC14:46
*** coolsvap|afk is now known as coolsvap14:48
*** caleb_ has quit IRC14:50
*** dianefleming has quit IRC14:52
*** caleb_ has joined #openstack-meeting-alt14:53
*** jprovazn is now known as jprovazn_bbl14:53
*** david-lyle has joined #openstack-meeting-alt14:55
*** Swami has joined #openstack-meeting-alt14:57
*** nikhil__|afk has quit IRC14:57
*** saju_m has quit IRC14:58
*** resker has joined #openstack-meeting-alt14:58
*** Barker has quit IRC14:58
*** carl_baldwin has joined #openstack-meeting-alt14:59
*** vivek has joined #openstack-meeting-alt14:59
Swamicarl: hi14:59
*** vivek is now known as Guest8567815:00
carl_baldwinSwami: hi15:00
*** pcm has joined #openstack-meeting-alt15:00
SwamiGuest85648: hi15:00
xuhanphi15:00
Swamixuhanp: hi15:00
Swamipcm: hi15:00
Swamimrsmith: hi15:01
Swamimrsmith: ping15:01
*** IlyaE has joined #openstack-meeting-alt15:01
*** mrsmith has joined #openstack-meeting-alt15:01
Swami#startmeeting distributed-virtual-router15:01
openstackMeeting started Wed Apr  9 15:01:42 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
Swamimrsmith:hi15:01
*** Barker has joined #openstack-meeting-alt15:01
*** esker has quit IRC15:02
Swami#topic Agenda15:02
*** openstack changes topic to "Agenda (Meeting topic: distributed-virtual-router)"15:02
Swami1. DVR Plugin extension update15:02
Swami2. L2 Agent Update15:02
Swami3. L3 Agent Update15:02
Swami4. Open Discussion15:03
Swami#topic DVR Plugin extension update15:03
*** openstack changes topic to "DVR Plugin extension update (Meeting topic: distributed-virtual-router)"15:03
*** Barker has quit IRC15:03
SwamiAs you all may know the WIP code for the DVR extension is up for review.15:03
*** Guest85678 has quit IRC15:03
SwamiThanks for the early review comments and I have address most of the comments.15:03
SwamiThe latest patch set if patch 515:04
Swamixunahp: I had an issue addressing one of your comments15:04
*** vivekn has joined #openstack-meeting-alt15:04
viveknhi15:04
Swamivivekn: hi15:05
xuhanpSwami, let me know how I can help :-)15:05
*** yamamoto has quit IRC15:05
SwamiThere was the "sqlalchemy Or_" that you mentioned in the review for the L3_db.15:05
*** banix has joined #openstack-meeting-alt15:05
SwamiFor some reason it gives me an error.15:05
SwamiI am not sure if there was any syntax errors.15:06
xuhanpSwami, yes. I saw your reply about it. maybe I need to download your code and experiment a little bit.15:06
Swamiwhen I include the key "device_owner =yyyy". It says that device_owner is unrecognized.15:06
xuhanpok. Let me try that this week and let you know?15:07
*** Barker has joined #openstack-meeting-alt15:07
Swamixuhanp: I will try to do some more investigation on that. In the meanwhile if you can give me a handle on that, it would be great.15:07
xuhanpSwami, sure thing.15:08
SwamiThere was on other topic related to the plugin that I wanted to discuss with the sub-team.15:08
SwamiIs there a cleaner way of accessing the ml2 plugin based port binding information from the l3 Plugin.15:09
SwamiIf anyone have any ideas on this, just ping me.15:10
viveknswami,15:10
Swamivivekn: yes15:10
viveknyou need port binding host_id information?15:10
viveknfor DVR interfaces?15:10
Swamivivekn:yes15:10
*** tedchang has quit IRC15:10
viveknhost_id for dvr interfaces are now stored in an extension table different than port-binding15:11
viveknthat table is called ml2_dvr_port_binding15:11
SwamiIs it still part of the ml2 db.15:11
viveknit is still part of ml2 db only. Let me try to give a cleaner interface through python abstract classes so that you can access that table as well15:12
Swamivivekn: I can chat with you offline on this.15:12
xuhanpSwami and vivekn, will that limit the DVR to only support ML2 plugin?15:12
viveknthe original port-binding table will continue to hold only non-dvr interfaces (liek nova ports, centralized nn ports etc)15:12
Swamivivekn: thanks15:12
viveknfor now we have coded it that way15:12
carl_baldwinAn interface would be good.  Is it something that other plugins could implement down the road?15:12
viveknwhen we post WIP code of L2 for review, we will go through this in more detail15:13
Swamivivekn: thanks15:13
xuhanpthanks15:13
viveknin the current shape no15:13
Swamixuhanp: We are not trying to tie the DVR with the ML2, but there is a dependency on the OVS for the DVR.15:13
viveknis same as the port-binding schema15:13
viveknwith status as an extra collumn15:14
vivekncorrect swami15:14
viveknovs today works with ml2 plugin only15:14
SwamiBut any port addition and port deletion and the corresponding action to those ports are basically handled in the ML2.15:14
SwamiThese are basically to address the OVS rules in the Compute node bridges.15:14
xuhanpSwami, thanks for the information.15:15
Swami#topic L2 Agent15:15
*** openstack changes topic to "L2 Agent (Meeting topic: distributed-virtual-router)"15:15
Swamivivekn: Can you give us an update on the L2 Agent where you are right now.15:15
*** vivekn_ has joined #openstack-meeting-alt15:16
Swamivivekn_: I think your connection is not so good.15:16
vivekn_yes kinda logged out automatically15:17
vivekn_figured out and rejoined :(15:17
Swamivivekn_: can you give an update on the L2 agent before you log off.15:17
vivekn_currently15:17
vivekn_pursuing addressing l2-pop to use15:17
vivekn_extended ml2_dvr_port_bindings table15:17
*** hemanth__ has joined #openstack-meeting-alt15:17
vivekn_to decide whether vm is first on a network in an agent and also a vm is last on the network in a given l2 agent15:18
*** hemanth__ has quit IRC15:18
*** atiwari has joined #openstack-meeting-alt15:18
*** vivekn has quit IRC15:18
vivekn_also started working on gerrit work flow to post WIP code of L2 Agent/Plugin for review on 'master'15:18
Swamivivekn_: thanks for the info.15:19
SwamiWe are looking forward to see the L2 Agent code, so that we might get early feedback.15:19
*** hemanth__ has joined #openstack-meeting-alt15:19
Swamivivekn_: can it be pushed in the next couple of days.15:19
vivekn_yes ,15:19
*** hemanth__ has quit IRC15:20
vivekn_but since travelling15:20
Swamivivekn_: Thanks, that's great.15:20
vivekn_may take 4-5 days15:20
Swamivivekn_: ok, by next week then we should have it posted.15:20
*** akuznetsov has joined #openstack-meeting-alt15:20
Swamivivekn_: hope this helps.15:20
vivekn_yes15:21
Swamivivekn_: Thanks for your time.15:21
Swami#topic L3 Agent15:21
vivekn_welcome15:21
*** openstack changes topic to "L3 Agent (Meeting topic: distributed-virtual-router)"15:21
Swamimrsmith: hi15:21
*** sballe has joined #openstack-meeting-alt15:21
mrsmithhi all15:21
Swamimrsmith: Any updates on the L3 Agent15:22
mrsmithFIP code changes are almost done15:22
*** hemanth__ has joined #openstack-meeting-alt15:22
mrsmithbut since upstream/icehouse has alot of FIP changes15:22
mrsmiththe merge has been delayed15:22
mrsmithand therefore posting for review is delayed15:22
*** zhangleiqiang has joined #openstack-meeting-alt15:22
mrsmithtrying to resolve the merge ASAP15:23
*** nacim has quit IRC15:23
Swamimrsmith: got it.15:23
mrsmithyesterday I got the unit tests passing with DVR changes for l3_agent15:23
mrsmithon icehouse15:23
mrsmithgood progress15:23
Swamimrsmith: Great!!!15:24
*** ramashri has joined #openstack-meeting-alt15:24
*** lenrow has quit IRC15:24
Swamimrsmith: Thanks, please make sure that you push you code as quick as possible to upstream to get the early feedback.15:25
mrsmithunderstood15:25
Swamimrsmith: Thanks for the update15:25
mrsmithnp15:25
*** flaper87 is now known as flaper87|afk15:25
Swami#Open Discussions15:25
SwamiAny open discussions15:26
vivekn_yes15:26
vivekn_i had a chance to read mails from Robert Kukura of l3-team15:26
*** ycombinator has joined #openstack-meeting-alt15:26
Swami#topic Open Discussions15:26
*** openstack changes topic to "Open Discussions (Meeting topic: distributed-virtual-router)"15:26
vivekn_for the external network multiple subnets blueprint15:26
Swamivivekn_: Kukura is part of the ml2 team15:26
vivekn_recent changes have been made for multiple external networks in icehouse15:26
vivekn_which might have impact on DVR15:26
carl_baldwinWhat is that blueprint called?15:27
vivekn_all internet traffic now goes through br-int15:27
vivekn_earlier it went throuh br-ex directly, but not anymore15:27
mrsmiththat would impact DVR15:27
vivekn_and br-ex has flows to strip_vlan (for egress) and insert_vlan(for ingress) packets to internet15:27
*** dianefleming has joined #openstack-meeting-alt15:27
Swamivivekn_: was that the blueprint implemented by Sylvain15:27
vivekn_this is the direction of N-S movement from icehouse15:28
vivekn_they want to eliminate br-ex being tied to ineternal routers15:28
xuhanpvivekn_, do you have the link of the blueprint or the link of the email?15:28
vivekn_yes15:28
vivekn_swami15:28
vivekn_Sylvain fix for multiple external networks changed the paradigm15:28
Swamivivekn_: can you post the blueprint link15:28
vivekn_of how N-S traffic is handled in incehouse15:28
vivekn_i think i have the bug id , i will find blueprint and post it over email15:29
xuhanpvivekn_, thanks15:29
Swamivivekn_: I thought the blueprint that Sylvain posted was related to allowing the L3 agent to handle more than one external networks.15:30
vivekn_here it is15:30
*** overlayer has quit IRC15:30
SwamiI was not sure that it touched the bridges.15:30
*** julienvey has quit IRC15:30
vivekn_one sec15:30
*** Barker has quit IRC15:31
vivekn_couldn't find the right blueprint15:31
Swamicarl: are you aware about this in Icehouse were br-ex is bypassed.15:31
vivekn_https://bugs.launchpad.net/neutron/+bug/130368215:32
*** nacim has joined #openstack-meeting-alt15:32
vivekn_please look at this bug for conversation by robert kukura on the paradigm change15:32
*** resker has quit IRC15:32
vivekn_Sylvain enhancement15:33
vivekn_https://review.openstack.org/#/c/59359/15:33
vivekn_br-ex is not bypassed15:33
vivekn_br-ex will talk to br-int15:33
*** esker has joined #openstack-meeting-alt15:33
vivekn_not to IRs anymore15:33
vivekn_if you need a single external network then old method will continue to work15:33
vivekn_but that will be for backward compatibility fro existing customers15:33
carl_baldwinSwami: I'm not aware.15:33
vivekn_going forward support for external networks is via provider external networks15:34
vivekn_please see Sylvain enhancement posted above for details15:34
Swamivivekn_: We might have to discuss this with Sylvain, he has already commented on the bug that vinod had proposed.15:34
carl_baldwinI've just opened the bug and review linked and will take a look.15:34
vivekn_with a single l3_agent, you can host multiple external networks going forward15:34
vivekn_earlier this was big limitation where you need one instance for l3_agent for every new external network15:35
carl_baldwinI did review the patch early on so my memory of it is beginning to come back.15:35
Swamivivekn_: Can you join the l3-subteam meeting tomorrow, sametime #openstack-meeting-3, and then we can discuss with Sylvain about this provider network scenario with multple external networks15:35
vivekn_sure, i will try to join15:35
Swamivivekn_: thanks.15:36
Swamivivekn_: thanks for bringing up this point.15:36
Swamivivekn_: Can you also send a detailed mail to sylvain and copy me.15:36
vivekn_i will forward the mail that was being discussed between vinod and15:37
vivekn_robert15:37
vivekn_to you , carl, mike and we can take it up from there15:37
Swamivivekn_: thanks vivek.15:37
vivekn_robert's responses are not captured in teh review comments, but he mailed the intent15:37
*** jmontemayor has joined #openstack-meeting-alt15:38
*** Leonr has joined #openstack-meeting-alt15:38
vivekn_i think attending ml2 meetings would help both l2 and l3 people in DVR15:38
*** dianefleming has quit IRC15:38
*** Barker has joined #openstack-meeting-alt15:38
Swamivivekn_: ml2 meeting is just after our meeting today in the same channel. If you are available can you join the meeting and have this discussion with the kukura and mystery.15:39
vivekn_sure15:39
SwamiI will also try to join the ml2 meeting, but may join a bit late.15:39
Swamivivekn_: Thanks15:40
xuhanpSwami, I have another question to bring up if you don't have other topics :-)15:40
Swamixuhanp: go ahead, I was about to ask you.15:40
xuhanpin current design, what happen after one distributed L3 agent on compute node fails?  will the VM on that node still be able to talk to other node or external network?15:40
*** Rajeev has joined #openstack-meeting-alt15:41
xuhanpI mean the compute node is working fine but just the L3 agent fails for some reason.15:41
mrsmithit should get restarted - via /etc/init15:42
mrsmithbut that is part of the interest in DVR - the impact of failure should be smaller15:42
mrsmithlimited to a CN15:42
Swamimrsmith: but the vms that are already provisioned should still be able to communicate.15:42
mrsmithyes - but if the l3_agent fails and does not recover there may be a problem15:43
mrsmithbut it should be better than the NN case15:43
xuhanpSwami, my question is exactly about how to do that?15:43
*** dkehn_ is now known as dkehnx15:43
Swamixuhanp: When an L3 agent fails, the current behaviour should be similar to the current centralized l3 agent behavior.15:44
xuhanpSwami, but we won't provide HA solution for the distributed L3 agent, right?15:45
Swamimrsmith: Is there any other option where when a L3 agent fails, the VMs can continue to pass traffic.15:45
*** zhiyan has quit IRC15:45
mrsmithare we assuming the auto re-start fails as well?15:45
*** sergmelikyan has quit IRC15:46
*** sergmelikyan has joined #openstack-meeting-alt15:46
Swamixuhanp: The HA solution that is currently being proposed for L3 agent should still work, but there may be some difficulties which we have not thought about.15:46
mrsmithsure15:46
xuhanpmrsmith, you mean the auto restart with the help of monitor tool, right?15:46
SwamiWe may have to do some testing. Since we are using the same L3 agent for all the DVR work, L3 vrrp can be used.15:47
mrsmiththe upstart linux functionality15:47
mrsmithfor services15:47
mrsmithwill monitor when a process dies - and auto restart15:47
xuhanpmrsmith, I see.15:47
mrsmithbut if there is a bad bug - the l3_agent may continuously restart15:47
mrsmiththe cloud admin may need to take manual steps15:48
SwamiAny other questions.15:48
xuhanpalso if there are many compute node, say 100, will there be too many l3 agents?15:48
Swamixuhanp: Each compute node will host a l3 agent.15:49
Swamixuhanp: This is minimum requirement.15:49
*** markmcclain has joined #openstack-meeting-alt15:49
*** rmoe has quit IRC15:49
*** colinmcnamara has joined #openstack-meeting-alt15:49
Swamixuhanp: Hope it is clear now.15:49
mrsmithyes - each compute node will host a l3_agent15:49
mrsmithhow many is "too many" ?15:50
SwamiOk, folks we are at the end of the hour.15:50
SwamiSee you all next week.15:50
*** cjellick has joined #openstack-meeting-alt15:50
SwamiThanks everyone for joining the meeting.15:51
xuhanpSwami, ok. Thanks for the explanation. talk to you later15:51
Swami#endmeeting15:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:51
openstackMeeting ended Wed Apr  9 15:51:06 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-04-09-15.01.html15:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-04-09-15.01.txt15:51
openstackLog:            http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-04-09-15.01.log.html15:51
carl_baldwinmrsmith: I don't think there is a too many.  One agent per compute node, however many compute there are.15:51
mrsmithagreed15:51
*** vivekn_ has quit IRC15:51
*** eghobo has joined #openstack-meeting-alt15:52
*** Swami has quit IRC15:53
*** mrsmith has quit IRC15:53
carl_baldwinmrsmith: There may be some some scaling issues to work out but I don't think there is an alternative to working them out.15:53
*** hemanth__ has quit IRC15:53
*** ramashri has joined #openstack-meeting-alt15:55
*** stannie has quit IRC15:58
*** rkukura has joined #openstack-meeting-alt15:58
*** otherwiseguy has joined #openstack-meeting-alt15:59
*** rcurran has joined #openstack-meeting-alt15:59
*** ramashri has quit IRC15:59
*** Sukhdev has joined #openstack-meeting-alt15:59
mesteryhi15:59
rcurranhi15:59
rkukurahi16:00
banixhi there16:00
asadoughihi16:00
mestery#startmeeting networking_ml216:00
openstackMeeting started Wed Apr  9 16:00:08 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
kevinbentonhi16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:00
otherwiseguyhi16:00
openstackThe meeting name has been set to 'networking_ml2'16:00
mestery#link https://wiki.openstack.org/wiki/Meetings/ML2#Meeting_April_9.2C_2014 Agenda16:00
*** sowmini has joined #openstack-meeting-alt16:00
mesteryrcurran: Is asomya around? I emailed him about presenting his TypeDriver work but got no response.16:01
*** nlahouti has joined #openstack-meeting-alt16:01
rcurranno. family issue.16:01
mesteryrcuraan: OK, got it, thanks.16:01
mesterySo, I'd like to spend some time on Juno Design Summit items today, but first I'd like asadoughi to spend some time on his OVS firewall driver16:01
mestery#topic OVS Firewall Driver Update16:01
*** openstack changes topic to "OVS Firewall Driver Update (Meeting topic: networking_ml2)"16:01
Sukhdevhi16:01
mesteryasadoughi: hi16:02
asadoughihi16:02
asadoughiyes, so re-opened the bp and targeted for juno-1 now that ovs 2.1.0 is available and juno is open for development16:02
asadoughishort term goal is to restore all 4 existing patches over the next week16:02
mesteryasadoughi: Great! I've seen those reviews become active lately.16:03
asadoughilong term goal is to have working stateless implementation uploaded to gerrit by summit, (5 weeks)16:03
*** zhiyan has joined #openstack-meeting-alt16:03
banixasadoughi: long term == 5 weeks :)16:03
*** caleb_ has quit IRC16:04
asadoughii had some off-list discussions with vthapar; vthapar will be looking into reflexive learning (stateful) now that ovs data path flow limit is over 200K flows; ultimately, thinking about providing a parallel implementation so the user can decide which driver style will meet their performance constraints (statless vs stateful)16:04
*** irenab has joined #openstack-meeting-alt16:04
asadoughithat is all. questions?16:04
mesteryasadoughi: Very cool!16:04
mesteryasadoughi: Do you happen to have the BP link handy?16:04
asadoughiblueprints.launchpad.net/neutron/+spec/ovs-firewall-driver16:04
mestery#link https://blueprints.launchpad.net/neutron/+spec/ovs-firewall-driver OVS Firewall Driver BP16:05
mesterySo do you think you'll have both stateless and stateful firewall support ready in 5 weeks?16:05
asadoughii doubt it16:06
mestery:)16:06
*** mxu has joined #openstack-meeting-alt16:06
mesteryI recall your email thread on ovs-discuss, and Justin indicated they were integrating linux connection tracking. Any update on that by chance?16:07
*** vthapar has joined #openstack-meeting-alt16:07
asadoughino update on that front16:07
mesteryOK.16:07
asadoughivthapar: you just missed my mention of our previous discussion16:07
mesteryAny other questions for asadoughi around this?16:07
asadoughii'll send another email on the ovs list16:08
*** chandan_kumar_ has quit IRC16:08
*** BrianB_ has joined #openstack-meeting-alt16:08
*** padkrish has joined #openstack-meeting-alt16:09
vthaparI hope to get some results of flow testing with OVS2.1 by next week.16:09
mesteryvthapar: Cool!16:09
*** manishg_ has joined #openstack-meeting-alt16:09
mesteryasadoughi: Thanks for the update!16:09
*** pballand has joined #openstack-meeting-alt16:09
mestery#topic Juno Design Summit16:09
*** openstack changes topic to "Juno Design Summit (Meeting topic: networking_ml2)"16:09
mestery#link https://etherpad.openstack.org/p/juno_ml2_session_ideas Juno Design Summit Etherpad16:09
mesteryI created the above etherpad to track ML2 ideas for the Summit16:09
mesteryI see people have been adding ideas there, thanks!16:09
*** rmoe has joined #openstack-meeting-alt16:10
*** jjmb2 has quit IRC16:10
mesterybanix: I just noticed your idea at the bottom (base mechanism driver for controllers)16:10
mesteryTo be honest, I think that may make sense.16:10
mesteryThe Tail-F driver and the ODL driver are somewhat similar for example.16:11
nlahoutiI also added ML2 MD support for extensions16:11
banixmestery: ok; how do we go about doing this or discussing more?16:11
*** jjmb has joined #openstack-meeting-alt16:12
mesterybanix: I would file a Summit Session for this and we can work it into the agenda.16:12
banixmestery: sounds good. thanks.16:12
mesterynlahouti: Thanks for that! I think that is something we've toyed with for a while now, so trying to resolve that will be good.16:12
rkukuraI listed some ideas I’ve been thinking about for a while16:13
nlahoutimestery: I added more details of changes in summit session link16:13
mesterynlahouti: Thanks!16:14
mesteryrkukura: Thanks for adding all of your info there as well.16:14
rkukuraI suspect some of the ones I listed overlap with others16:14
nlahoutiAlso we need some changes related to VDP support in OVS and if it is okay can we discuss it here ?16:14
mesteryrkukura: Does it make sense to try to merge some ML2 items into a "super-session" again like we did in Hong Kong, giving people 10-15 minutes each?16:14
*** ramashri has joined #openstack-meeting-alt16:15
banixnlahouti, mestery: Yeah I think we have to add this support sooner or later16:15
SukhdevI like some of the ideas and have interest in them - do folks have worked out any details  on these?16:15
rkukuramestery: I think so16:15
mesterynlahouti: OVS changes are not in the domain of OpenStack. Do you mean actually changes to OVS itself?16:15
*** lsmola has quit IRC16:15
rkukuraWe don’t need entire sessions for ideas that are already well understood16:15
mesteryrkukura: Agreed.16:15
*** tedchang has joined #openstack-meeting-alt16:15
nlahoutimestery: I meant OVS neutron agent16:15
mesteryWe should converge on what Juno items we want to work on and try to get them staffed with people by the Summit or soon after.16:15
*** jjmb has quit IRC16:16
mesterynlahouti: OK, then that is applicable here. Is that added to your BP yet? Or do you want to give us a quick summary here?16:16
*** denis_makogon has joined #openstack-meeting-alt16:17
*** gyee has joined #openstack-meeting-alt16:17
nlahoutimestery: it is added to https://blueprints.launchpad.net/neutron/+spec/netron-ml2-mechnism-driver-for-cisco-dfa-support16:17
mesterynlahouti: OK, thanks!16:18
rkukuranlahouti: Does DFA overlap with my “dynamic VLAN segment type for ToR switch” idea?16:18
padkrishmestery: even though it's added under cisco-dfa mechanism driver, it can be used in general for anyone needing VDP support16:18
rkukurawhat does VDP expand to?16:18
mesterypadkrish: It may make sense to split that out into it's own BP so it can be merged separately then.16:18
nlahoutirkukura: I haven't read it yet It could be.16:19
*** woodster1 has left #openstack-meeting-alt16:19
*** ramashri has quit IRC16:19
padkrishrkukura: It stands for VSI discovery protocol and it's a part of QBG IEEE standard16:19
Sukhdevrkukura, nlahouti: It does have similarities -16:19
padkrishmestery: Ok16:19
mesteryAgreed on the similarities16:20
nlahoutisukhdev: is there any BP for that?16:20
*** caleb_ has joined #openstack-meeting-alt16:20
Sukhdevnlahouti: you should look into asoumya work as well - there is similarity there as well16:20
*** richm has joined #openstack-meeting-alt16:20
*** julienvey has joined #openstack-meeting-alt16:21
*** ramashri has joined #openstack-meeting-alt16:21
Sukhdevnlahouti: yes there is mestery provided link in last meeting - do not have handy now, but, can look16:21
padkrishsukhdev: Yes, we discussed with asomya, from what i understood from him, it's different16:21
mesteryrkukura: I think the "dynamic VLAN segment type for ToR switch" idea is going to be something we should do early in Juno, as it will help a lot of these things out.16:21
Sukhdevmestery: +116:22
*** Sam-I-Am has joined #openstack-meeting-alt16:22
banixSukhdev: nlahouti: #link https://blueprints.launchpad.net/neutron/+spec/ml2-type-driver-refactor16:22
mesteryThanks banix!16:23
nlahoutibanix: thx for the link16:23
rkukuramestety: I could writeup a succint BP for it, but if something more aligned with QBG is needed, someone else may want to do it, or help16:23
Sukhdevpadkrish: In that case, perhaps you can highlight the differences ---- all of us do not want to be comming up with diffentent implementations of similar ideas16:23
nlahoutiwe will look into it16:23
*** AndChat|112404 has joined #openstack-meeting-alt16:23
padkrishsukhdev: Yes, i remember looking at this one. Here, they separate the segment allocation to the type driver16:24
*** AndChat-112404 has joined #openstack-meeting-alt16:24
padkrish#sukhdev, mestery: In VDP, it's a protocol which sends the vNIC information to the ToR and the ToR sends the VLAN to be used for that VM.16:24
nlahoutiif there are differences should we have new BP and also wirte up for the desing summint sessison?16:25
*** markwash has joined #openstack-meeting-alt16:25
padkrish#sukhdev: VDP protocol runs in each of the compute nodes.16:25
mesteryIt seems there is some overlap here for sure, we need to figure out how to ensure we make something extensible for all the use cases.16:25
*** andreaf has quit IRC16:26
*** xuhanp has quit IRC16:26
*** pballand has quit IRC16:26
rkukurasounds like we may want a simple framework for this in ML2, where the openvswitch agent MD can use the dynamically assigned VLAN, but a separate driver of some work (maybe the type driver) allocates the VLAN, and this can have a simple neutron-DB-based implementation and one that uses the VDP standard.16:27
padkrishmestery: The work by Arvind has this segment allocation pushed to type drivers. What i see is Type drivers run only in the controller.16:27
Sukhdevmestery: I think I like rkukura's idea of putting together some generic VLAN solution (with some extensions) to cover most of these use cases16:27
*** AndChat|112404 has quit IRC16:27
mesterypadkrish: The similarities with what asomya is doing and VDP is that VLANs are per "host to ToR", if we can make that work we'll be good I think.16:28
banixSukhdev: makes sense16:28
Sukhdevmestery: correct analysis16:28
rkukuraThis definitely is sounding like a good session topic where there are a number of efforts or use cases that require similar support in ML216:28
mesteryAgreed rkukura, I think we should definitely have a session on this.16:29
rkukuraBut I think asomya’s BP covers a more specific topic, so should be a separate session16:29
padkrishmestery: Yes, that part is same. But, my understanding of  asomya's work is, it's like top-down assignment where controller knows the assignment. VDP is more like bottom-up where compute nodes query the TOR for VLAN16:29
Sukhdevrkukura: I have very strong interest in this as well16:29
mesteryWho wants to file this one?16:29
mesteryI can certainly do it.16:30
rkukuraI’ll file one that’s very generic about dynamic VLAN allocation. Others can do more specific proposals, and we can combine16:30
mestery+1 to that rkukura16:31
Sukhdevpadkrish: my understanding of asoumya work is that it is a late binding model - hence, I wanted him to present, so that we can all understand16:31
padkrishrkukura, mestery: Sure, i can give my inputs on the VDP side16:31
padkrishSukhdev: Sure16:31
Sukhdev+ to rkukura as well16:31
*** caleb_ has quit IRC16:31
Sukhdevrkukura; if you like I can help you with that16:32
rkukuracan we get asomya next on the agenda next week?16:32
mesteryrkukura: Yes, I'll work to make sure asomya is here.16:33
padkrishrkukura: Sure, and then we can compare with VDP and its similarities and differences16:34
*** vivekn_ has joined #openstack-meeting-alt16:34
mesteryOK. any other Juno Summit ideas to discuss here?16:34
Sukhdevmestery: we need to short list the ideas soon16:35
*** balajiiyer has quit IRC16:35
mesterySukhdev: Yes, as the filing deadline is April 20th.16:35
*** pballand has joined #openstack-meeting-alt16:35
*** yamahata has quit IRC16:36
*** rudrarugge has joined #openstack-meeting-alt16:36
rkukuraanyone interested in putting together a session on bulk ops?16:36
rkukuraOr on modulat agent?16:36
*** balajiiyer has joined #openstack-meeting-alt16:36
Sukhdevmestery: leaving the Dynamic VLAN idea, we can go through the reaminging list and see what makes sense16:36
rkukuramodular16:36
rkukuraor on ML2 testing?16:36
mesteryrkukura: modular agent has been around for a bit, that's a good one if someone is interested!16:36
rkukurasomeone would need to put some thought into the design and plan16:37
*** noslzzp has quit IRC16:37
*** ramashri has quit IRC16:38
Sukhdevrkukura, mestery: need to understand a bit better as to what you are looking for - then I can see if I can spare some cycles (or join hands with someone)16:38
*** ramashri_ has joined #openstack-meeting-alt16:38
mesteryrkukura: Agreed, but with no less than 3 agents now (OVS, LB and OFAgent), it may make sense to collapse them.16:38
mesterySukhdev: We're talking about merging all 3 of the agents I mentioned ^^^16:38
irenabthere is also MellanoxAgent quite similar to others16:39
*** zhangleiqiang has quit IRC16:39
rkukurabeyond what mesteery just mentioned, drivers within in the agents for things like firewalls or QoS use some generic hooks16:39
irenabI'll check if I can join hands on this topic16:40
mesteryirenab: Thanks, I forgot about that one!16:41
rkukurairenab: right, support for specific SR-IOV cards, various kinds of offloading, etc., might be able to take advantage16:41
irenabI also added point to the etherpad on flexible device naming, not tapXXX16:41
irenabwould be required by SR-IOV HW Switch agent16:42
*** dprince has quit IRC16:42
*** ramashri_ has quit IRC16:42
*** IlyaE has quit IRC16:42
mesteryOK, so it sounds like a modular agent is also a possible topic for Atlanta.16:43
mesteryThere's enough interest here.16:43
Sukhdevmestery: three topics and counting :-)16:43
rkukurajust need a driver for that one16:44
mesterySukhdev: :)16:44
mesteryrkukura: Agreed. Does anyone want to volunteer to drive the modular agent work? It will involve a fair amount of people since it touches 4 agents.16:44
mesteryIf anyone wants to take that one, please reach out to me or rkukura.16:45
mestery#topic Open Discussion16:45
*** openstack changes topic to "Open Discussion (Meeting topic: networking_ml2)"16:45
kevinbentonhttps://review.openstack.org/#/c/85592/16:45
mesteryAnything else this week or should we end a bit early?16:45
kevinbentonhow should i handle this error case16:45
kevinbentonsegment in DB with no network type driver16:45
mesterykevinbenton: That's a good question. This is an end case issue. Did you see enikanorov's comments in the review?16:47
kevinbentonyes, it scanning the whole db on startup an acceptable approach?16:47
kevinbentonis*16:48
rkukurakevinbenton: Maybe the delete should succeed, but the error logged.16:48
*** yamahata has joined #openstack-meeting-alt16:48
mestery+1 to that rkukura16:48
*** overlayer has joined #openstack-meeting-alt16:48
rkukuraIf the type driver doesn’t exist, reclaiming resources isn’t possible, but a DB admin could do that16:48
kevinbentonrkukura: that’s what i was starting to think. if the network_type is gone it sort of implies that there is nothing to clean up16:48
rkukurakevinbenton: right16:49
*** harlowja_away is now known as harlowja16:49
kevinbentonrkukura: so i’ll just log an error and return16:49
*** vinod has joined #openstack-meeting-alt16:49
*** overlayer has quit IRC16:50
mesteryOK, thanks everyone for attending this week!16:51
mesteryWe'll see you all next week, same time and channel.16:51
banixbye16:51
mesteryKeep those Summit ideas flowing!16:51
mestery#endmeeting16:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:51
*** pballand has quit IRC16:51
openstackMeeting ended Wed Apr  9 16:51:28 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-04-09-16.00.html16:51
rkukurabye16:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-04-09-16.00.txt16:51
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-04-09-16.00.log.html16:51
padkrishbye16:51
nlahoutibye16:51
*** balajiiyer has quit IRC16:52
*** pcm has left #openstack-meeting-alt16:52
*** irenab has quit IRC16:53
*** vthapar has quit IRC16:54
*** vivekn_ has quit IRC16:54
*** ramashri has joined #openstack-meeting-alt16:56
*** Hao has quit IRC16:56
*** mugsie has joined #openstack-meeting-alt16:57
*** mxu has quit IRC16:58
*** nlahouti has quit IRC16:58
*** nacim has quit IRC16:59
vinod#startmeeting Designate17:00
openstackMeeting started Wed Apr  9 17:00:24 2014 UTC and is due to finish in 60 minutes.  The chair is vinod. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: Designate)"17:00
openstackThe meeting name has been set to 'designate'17:00
vinodwho's here?17:00
*** Sam-I-Am has left #openstack-meeting-alt17:00
*** tsimmons has joined #openstack-meeting-alt17:00
kiallHeya17:00
mugsieo/17:01
eankutseher17:01
eankutsehere17:01
tsimmonso/17:01
*** gokrokve has quit IRC17:01
vinod#topic Review action items from last week17:01
*** openstack changes topic to "Review action items from last week (Meeting topic: Designate)"17:01
richmhere17:01
vinodBoth the action items were to add agenda action items.  They were done17:01
kiall2x actions for me - Both to put stuff on agenda for today. Done17:01
*** rjrjr_ has joined #openstack-meeting-alt17:01
*** ramashri_ has joined #openstack-meeting-alt17:02
vinod#topic Workshop Meetup - 17:00 UTC via Hangout17:02
*** openstack changes topic to "Workshop Meetup - 17:00 UTC via Hangout (Meeting topic: Designate)"17:02
kiallBTW - Myself and mugsie will have to leave this meeting a little early17:02
vinod#link https://etherpad.openstack.org/p/DesignateAtalantaWorkshop17:02
vinodMugsie what day would the hangout be?17:02
*** ramashri has quit IRC17:02
*** dprince has joined #openstack-meeting-alt17:03
mugsieon monday17:03
mugsienext week17:03
mugsieI just added it there ;)17:03
kiall14th?17:03
mugsieyup17:03
*** amcrn has joined #openstack-meeting-alt17:03
mugsiewas a brain fart on my side17:03
mugsierjrjr_: do you want to stay on after that and talk about our talk?17:03
rjrjr_yes.17:04
rjrjr_what time monday?17:04
*** eanxgeek is now known as eanxgeek|log17:04
mugsie17:00 UTC -> 18:00 UTC17:04
mugsiethen 18:00 on wards for us17:04
vinodso about an hour earlier than now17:04
mugsieno, this time actually17:04
kiallreally? It's 17:00 UTC right now?17:05
mugsiewe are UTC +1 at the moment17:05
*** AndChat-112404 has quit IRC17:05
ekarlsoyo17:05
eankutsethat works for me17:05
rjrjr_where do i find the information about the hangout meetup?17:05
*** SumitNaiksatam has quit IRC17:06
*** ramashri_ has quit IRC17:06
mugsiei will send it on after this meeting17:06
kiallCool :) Graham has everyones's google acct details.. So we'll let him organize the hangout.17:06
*** eanxgeek|log is now known as eanxgeek17:06
*** ramashri has joined #openstack-meeting-alt17:06
kiall#action mugsie to Send out invite etc for Hangout on Mon 14th @ 17:00 UTC17:06
kiallrjrjr_: no details other than "Workshop planning" and https://etherpad.openstack.org/p/DesignateAtalantaWorkshop17:07
rjrjr_okay17:07
vinodanything more on the workshop before we move to the next item?17:07
vinod#topic RRSets APIs - Decision time17:07
*** openstack changes topic to "RRSets APIs - Decision time (Meeting topic: Designate)"17:07
kiallNot from me..17:07
kiall#link https://wiki.openstack.org/wiki/Designate/Blueprints/RecordSets17:07
kiallOkay - So, I added a Proposal #4 (and re-titled the existing proposals)17:07
*** ramashri has quit IRC17:08
kiallCan everyone take 5 mins or so to re-read them?17:08
vinoddoing now17:08
*** rkukura has left #openstack-meeting-alt17:08
*** ramashri has joined #openstack-meeting-alt17:08
*** catohornet has quit IRC17:08
*** nati_ueno has joined #openstack-meeting-alt17:09
*** garyduan has joined #openstack-meeting-alt17:09
*** ramashri has quit IRC17:09
*** derekh has quit IRC17:10
*** ramashri has joined #openstack-meeting-alt17:10
*** catohornet has joined #openstack-meeting-alt17:10
vinodso proposal 4 is essentially the same as what we had before as the design - correct?17:10
eankutseKiall: how different is this from the one proposed last week?17:10
*** ramashri_ has joined #openstack-meeting-alt17:11
kiallvinod / eankutse Proposal 3 and 4 are quite similar, but each proposes a different resource is kept17:11
*** balajiiyer has joined #openstack-meeting-alt17:11
*** ramashri_ has quit IRC17:11
kiallProposal 4 looks very similar to the original V2 spec (i.e. not what got implemented in the end..)17:11
*** ramashri_ has joined #openstack-meeting-alt17:12
rjrjr_were there problems in implementation?17:12
*** vishy has quit IRC17:12
*** yogesh has joined #openstack-meeting-alt17:12
vinodwith proposal 4 - can we also have a PUT which would be completely replace the existing with the new17:12
kialleankutse: So, there was 3 proposals last week, the first 3 on that page are the same as last week, just with a new heading for easier referencing :) Proposal 4 is new since last week, but it what I suggested last week17:12
*** ramashri_ has quit IRC17:13
vinodthe reasoning being that if we have more changes than the modify could be pretty ugly17:13
eankutsek17:13
*** ramashri_ has joined #openstack-meeting-alt17:13
*** vishy has joined #openstack-meeting-alt17:13
mugsievinod: the PATCH would replace the entire resource17:14
kiallall updates in P4 replace the set, with JSONPatch offering support to mutate the set in place where needed17:14
mugsieand the to add, you would use JSON+Patch17:14
mugsieah, kiall just said it17:14
*** ramashri has quit IRC17:14
kiallrjrjr_: yes, there was implementation difficulties - But, we're in a better spot to address those now than we were17:14
*** kgriffs is now known as kgriffs|afk17:15
kiallNow that backend operations are performed within a TX, we can add a new "replace_records" or similar method that replaces the set as a whole in 1 go, in 1 TX17:15
*** ramashri_ has quit IRC17:16
vinodfrom an implementation perspective, kiall were you thinking about having a table for recordsets and another for records similar to now17:16
kiallAnyone still reading BTW?17:16
rjrjr_still here.17:16
richmyes17:16
*** ramashri has joined #openstack-meeting-alt17:16
richmWhat data is associated with a recordset, other than ttl?17:16
kiallrichm: name, type, TTL17:16
kiallpotentially more if/when we add more advanced features17:17
richmof those, what is allowed to be changed?17:17
kiallfor example - GeoIP - RRSet #1 for EU queries, RRSet #2 US17:17
*** nati_uen_ has joined #openstack-meeting-alt17:17
richmok17:17
kiallrichm: ttl, and we could allow name to change.. we just don't currently17:17
kiallvinod: re the tables - I think this BP happens regardless https://wiki.openstack.org/wiki/Designate/Blueprints/Records_Table_Redesign17:18
kialli.e. no matter what is chosen here, records gets split17:18
rjrjr_so, some of the "difficulties" in the code is around creating recordset then record, etc.?  (i also see a bug was found where recordsets are not deleted with records.)  will this help with that?  can some of the central code be simplified?17:18
*** coolsvap is now known as coolsvap|afk17:18
*** yogesh_ has joined #openstack-meeting-alt17:19
kiallrjrjr_: yes, all the central code for records goes away - RecordSets would be the only thing it knows about with P417:19
kiallSo, the DB layer would, inside a TX, create the RRSet entry, then the Nx RR entries .. Should one fail, it aborts the TX and keeps things clean17:20
*** nati_ueno has quit IRC17:20
kiallAnyone still reading BTW?17:20
*** ramashri has quit IRC17:20
vinodi assume you mean reading the proposals - no i am done17:21
rjrjr_okay, my objects last week are being retracted. 8^)  this looks better.17:21
*** SumitNaiksatam has joined #openstack-meeting-alt17:21
rjrjr_objects = objections17:21
kiallvinod: Yea, I mean reading the proposals :)17:21
vinoddecision time or any more questions still lingering in people's minds?17:21
kiallSo .. Say everyone is done reading.. Let's go thought them one by one?17:22
richmok17:22
kiall==== Proposal 117:22
*** rcurran has quit IRC17:22
kiallAnyone have any pros/cons for P1?17:22
*** yogesh has quit IRC17:22
*** tsimmons has quit IRC17:22
kiallPersonally, I dislike the "?modify-rrset" query string, and that without that, a update TTL on a 1 vs 2+ record RRSet behaves differently.17:23
richmFor those folks who actually have to administer DNS - is the concept of managing recordsets separately from records a natual one?  So would it be natural to want to modify the ttl (or other attributes) of a recordset separately from records?17:23
richmnatural17:24
*** chandan_kumar_ has joined #openstack-meeting-alt17:24
rjrjr_in BIND, they just manage records.  recordsets are "background".17:24
richmI also dislike the ?modify-rrset17:24
*** zns has quit IRC17:25
vinodPros - Would be that the users deal with records and not recordsets17:25
kiallrjrjr_: yea, in BIND (and many DNS servers) RRSets are hidden away - But, if your managing a DNS server and don't understand them - chances are your zonefiles are invalid, and BIND is silently serving something different than what you told it to17:25
richmrjrjr_: in BIND, how do you change the ttl in a recordset?17:25
vinodCons - Modifying the recordset is clumsy17:25
kiallvinod: Yep - Agreed on both your Pros/Cons17:26
rjrjr_you change the TTL for all the records.  lowest TTL wins!17:26
richmegads17:26
rjrjr_you asked. 8^)17:26
richmthat seems . . . sub-optimal17:26
kiallrjrjr_: So, to me, that's not right. Since when i fetch a record via the API, and see ttl=30017:26
kiallthen do a DNS query and see ttl=6017:26
*** jgallard has quit IRC17:26
kiallsomething is wrong ;)17:26
*** rmoe has quit IRC17:27
kiallAny other thoughts on P1? Anyone disagree with anything said ^?17:27
vinodNo17:28
kiallOkay .. Moving on ;)17:28
kiall==== Proposal 217:28
vinodThis essentially seeks to mimic BIND's behavior17:29
*** markmcclain has quit IRC17:29
kiallMy last comment from above is really related to this one, as P1 enforces the TTLs are the same, while P2 proposes to use lowest TTL wins behaviour similar to BIND17:29
*** yamamoto has joined #openstack-meeting-alt17:29
*** overlayer has joined #openstack-meeting-alt17:30
kiallAnyone have pro/con's for P2?17:30
rjrjr_pro: it's what most administrators of BIND expect.17:30
*** yamamoto has left #openstack-meeting-alt17:30
*** IlyaE has joined #openstack-meeting-alt17:30
vinodcons: dns behavior might not be consistent with what api shows17:31
kiallrjrjr_: Can't argue with that :) But, for me, the average Designate end-user isn't a DNS admin17:31
*** CaptTofu has joined #openstack-meeting-alt17:32
kiallDesignate should be taking half the DNS admin's job (updating zonefiles), and delegating that to the user who would have been submitting a ticket for that change ..17:32
richmfits with the way IPA works too - if you change the ttl of a record, it actually changes the ttl of the recordset17:32
*** eguz has joined #openstack-meeting-alt17:32
kiallso - IPA doesn't expose RRSets in it's APIs, but internally enforces consistency?17:33
mugsieI would say keeping the API data cnsistant with the end result is requirement17:33
richmkiall: right17:33
*** IlyaE has quit IRC17:33
*** chandan_kumar_ has quit IRC17:34
kiallrichm: so, how would we enforce lowest TTL wins with IPA?17:34
kiallIt sounds like with IPA, latest TTL wins?17:34
richmright17:34
richmenforcing lowest ttl wins would be more difficult17:34
richmwill have to see if ipa can enforce that on the server side17:35
vinodso essentially modifying one record's ttl could modify some other records ttls too17:35
richmright17:35
kiallNew con: We can't easily implement this is a way that is consistent cross different DNS servers17:35
rjrjr_Proposal 5 - Handle TTLs Implicitly - latest TTL wins. 8^)17:35
kiallrjrjr_: lol17:35
*** rmoe has joined #openstack-meeting-alt17:36
kiallOkay .. So, moving on?17:36
*** arnaud has joined #openstack-meeting-alt17:36
*** eghobo has quit IRC17:36
*** safchain has quit IRC17:36
kiallOr anything else before we do?17:36
richmno17:36
*** gokrokve has joined #openstack-meeting-alt17:37
vinod==== Proposal 317:37
kiallOkay17:37
*** zhiyan is now known as zhiyan_17:37
*** vk has quit IRC17:38
vinodthis is mostly similar to proposal 4 except for the terminology and modify17:38
kiallSo .. I can't come up with much in the way of cons for this one to be honest. Essentially, it's RecordSets being called Records, and update being a little different17:38
vinodCons: We talk about recordsets without calling them recordsets - could be more confusing17:39
mugsie+117:39
rjrjr_i like proposal 4 API better ("record" instead of "data", etc.)17:39
richmhow does this correspond with how other DNS servers (other than BIND) are managed?17:39
*** rpodolyaka1 has joined #openstack-meeting-alt17:39
mugsiealso, not sure i like the PUT vs PATCH works either17:39
kiallrichm: RecordSets can be mapped onto any DNS (they have to be!). But, with some DNS servers, we'll have to "explode" the RRSet in a list of Records17:40
kiallBut - Zonetransfers with mDNS should make that just work17:40
*** ijw has joined #openstack-meeting-alt17:41
kiallrjrjr_: I think the "records" vs "data" etc is not really important, it's the concept we're aiming to agree on :)17:41
kiall(not important *right now* ;))17:41
richmI mean - it sounds like this proposal may be difficult for BIND admins to grok - but what about pdns, nsd, etc.?17:41
*** michael-yu has joined #openstack-meeting-alt17:41
rjrjr_i don't think it is difficult, just different.17:41
richmIt seems more natural to me, and aligns better with the DNS specs17:42
kiallP3 and P4 are both likely to cause a double take for DNS admins.. But, DNS Admins are likely not our primary audience17:42
kiallAny other pros/cons on this one?17:44
richmabout PATCH - is it supported everywhere?17:44
kiallYea, it certainly should be17:44
kiallThe bad old days of GET/POST being the only things that worked are gone thanks to APIs :)17:45
kiall(We also use PATCH elsewhere in the v2 API, as do several other OS APIs)17:45
richmok17:45
richmThen it looks like the usage of PUT vs. PATCH is as intended by the HTTP docs17:46
kiallSo - No other comments/pros/cons on P3?17:46
*** kgriffs|afk is now known as kgriffs17:46
*** mfer has joined #openstack-meeting-alt17:46
rjrjr_vote?17:46
kiallrichm: Kinda, PUT is applying PUT's semantics onto a single element within the payload.. But, it's closer than most APIs get to doing it right ;)17:46
kiall==== Proposal 417:47
richmwell, let's just say it makes sense in this context17:47
*** cjellick_ has joined #openstack-meeting-alt17:47
*** chandan_kumar_ has joined #openstack-meeting-alt17:47
kiallOkay - Cons.. We use the word "RecordSets" - this can be scary17:47
*** overlayer has quit IRC17:47
kiallWho has pros/cons on this one?17:47
*** mwagner_lap has quit IRC17:48
*** cjellic__ has joined #openstack-meeting-alt17:48
kiallPros: Maps to the DNS specs - So will fit on any DNS server while keeping data in the API, and in DNS consistent17:48
mugsieI prefer the idea of JSON+PATCH - it shows a good flow of what the modifications are17:48
vinodCons: New concept recordsets.  If we want to add just one record (how many % of the users?) we need to think in terms of recordsets17:48
*** cjellick_ has quit IRC17:49
vinodCons: The zone file does not have recordsets - just records.  But the api has recordsets and not records17:49
eankutseCon: doing away with the concept of Record17:49
mugsietrue, but for most of the users who will have issues, they will be using a CLI / horizon panel17:49
kiallvinod: if your just adding 1 record, then it's a s/record/recordset/ and it should be pretty similar17:49
eankutsenow Record is RecordSet with one member - a little heavy-duty17:49
mugsieeankutse: the concept of record is there, but as a paylod in a recordset17:49
*** glenc has joined #openstack-meeting-alt17:50
*** cjellick has quit IRC17:50
*** cp16net has joined #openstack-meeting-alt17:50
kiallvinod: BIND zone files do have RRSets, implicitly.17:50
mugsieyeah, it is the same info that we would be providing if it was called a record.. and it does align with the RFCs.17:50
*** yogesh_ has quit IRC17:51
kiallPro AND Con: This is the same data model as AWS's Route53. As i said.. Pro AND Con ;)17:51
*** _nadya_ has joined #openstack-meeting-alt17:51
*** yogesh has joined #openstack-meeting-alt17:51
vinodkiall/mugsie: how are you on time?  do you want to start a vote?17:51
kialleankutse: also, most users will be using JClouds, Python bindings, Web Console..17:51
*** IlyaE has joined #openstack-meeting-alt17:52
kiallvinod: Does everyone have a clear #1 in mind?17:52
richmkiall: interesting - do you have a url for the route53 docs?17:52
kiallWe're fine on time17:52
kiall(dont need to leave anymore)17:52
kiallrichm: http://awsdocs.s3.amazonaws.com/Route53/20130401/route53-api-20130401.pdf17:52
kiallRRSet = Resource Record Set BTW, they call them that17:53
*** malini1 has joined #openstack-meeting-alt17:53
kiallhttp://pastie.org/9057085 - example17:54
*** k-pom has joined #openstack-meeting-alt17:54
richmok - thanks17:54
kiallOkay. 5 mins left.. Is anyone ready to vote? Say Yes or No please :)17:55
richmYes17:55
rjrjr_yes17:55
mugsieyes17:55
*** cjellick has joined #openstack-meeting-alt17:55
kiallYes17:55
*** otherwiseguy has quit IRC17:55
vinodyes17:55
*** kgriffs is now known as kgriffs|afk17:55
*** yogesh has quit IRC17:55
eankutseyes17:55
*** hub_cap has joined #openstack-meeting-alt17:55
kiallOk...17:55
kiall#startvote Which RecordSet proposal? P1, P2, P3, P417:56
openstackOnly the meeting chair may start a vote.17:56
kiallgrr.. vinod :)17:56
vinodirc://morgan.freenode.net:6667/#startvote Which RecordSet proposal? P1, P2, P3, P417:56
rjrjr_P417:56
kialllol .. that prefix isn't right ;) Try again?17:56
eankutseP4 with slight reservation17:56
vinod#startvote Which RecordSet proposal? P1, P2, P3, P417:56
openstackBegin voting on: Which RecordSet proposal? Valid vote options are P1, P2, P3, P4.17:56
openstackVote using '#vote OPTION'. Only your last vote counts.17:56
kiallOkay17:56
mugsie#vote P417:56
*** robertmyers has joined #openstack-meeting-alt17:56
kiall#vote P417:56
vinod#vote P417:56
rjrjr_#vote P417:56
eankutse#vote P4 with slight reservation17:57
openstackeankutse: P4 with slight reservation is not a valid option. Valid options are P1, P2, P3, P4.17:57
rjrjr_lol17:57
*** cjellick has quit IRC17:57
mugsie:D17:57
kialleankutse: the bot told you odd ;)17:57
*** cjellick has joined #openstack-meeting-alt17:57
*** SlickNik has joined #openstack-meeting-alt17:57
kiall#showvote17:57
*** cjellic__ has quit IRC17:57
openstackP4 (4): mugsie, rjrjr_, kiall, vinod17:57
eankutse#vote P417:58
kiallSo .. eankutse / richm let?17:58
kiallleft*17:58
richm#vote P417:58
rjrjr_that's everyone.17:58
vinodkiall is there an endvote?17:58
*** eanxgeek is now known as eanxgeek|log17:58
kiallYep #endvote17:58
vinod#endvote17:58
openstackVoted on "Which RecordSet proposal?" Results are17:58
openstackP4 (6): eankutse, vinod, rjrjr_, mugsie, kiall, richm17:58
*** rramirez has joined #openstack-meeting-alt17:58
kiallThat's not what I expected :) I was thinking people were leaning towards P3!17:59
*** julienvey has quit IRC17:59
*** Sukhdev has quit IRC17:59
vinodyou were convincing kiall :-)17:59
kiall#action kiall to put Mini-DNS: Can we rename it to something less provoking, like ZoneTransfer Module? on agenda for next week, again17:59
kiallThat's time :)17:59
*** julienvey has joined #openstack-meeting-alt17:59
vinod#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Wed Apr  9 17:59:43 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
rjrjr_we already resolved it.  jmcbride understood why the name.17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-04-09-17.00.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-04-09-17.00.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-04-09-17.00.log.html17:59
*** esp has joined #openstack-meeting-alt18:00
SlickNikThanks vinod, kiall, et al18:00
*** dshulyak_ has joined #openstack-meeting-alt18:00
*** mugsie has left #openstack-meeting-alt18:00
SlickNik#startmeeting trove18:00
openstackMeeting started Wed Apr  9 18:00:49 2014 UTC and is due to finish in 60 minutes.  The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
cweido/18:00
*** openstack changes topic to " (Meeting topic: trove)"18:00
openstackThe meeting name has been set to 'trove'18:00
*** vinod has left #openstack-meeting-alt18:00
espo/18:00
juiceo/18:01
robertmyerso/18:01
mattgriffino/18:01
*** dougshelley66 has joined #openstack-meeting-alt18:01
pdmarshello18:01
SlickNik#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting18:01
cweidrobertmyers: your name is robotmyers.18:01
cp16neto./18:01
esmute\o/18:01
*** _nadya_ has quit IRC18:01
amrith\\o//18:01
*** grapex has joined #openstack-meeting-alt18:01
k-pom\o18:01
grapexo/18:01
espcweid: lol18:01
kevinconwayo/18:01
dougshelley66o/18:01
robertmyerscweid: correct18:01
mattgriffino/18:01
denis_makogono/18:01
esmuteamrith: that was a stretch :-)18:01
amcrno/18:01
*** glucas has joined #openstack-meeting-alt18:02
amrithesmute: i need a lot of stretching ;)18:02
glucas\o18:02
SlickNikNotes from last meeting:18:02
SlickNik#link http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-04-02-18.01.html18:02
*** eanxgeek|log is now known as eanxgeek18:02
SlickNikLet's get started18:02
SlickNik#topic Refactoring backup/restore strategies18:03
*** openstack changes topic to "Refactoring backup/restore strategies (Meeting topic: trove)"18:03
denis_makogonit's mine18:03
*** lisaclark has left #openstack-meeting-alt18:03
denis_makogonthe point is to collect all strategies in one place18:03
vgnbkro/18:03
*** julienvey has quit IRC18:03
denis_makogonit reduces amount of the confi attributes18:03
denis_makogonand keeps code compact18:03
amrithis this a reaction to a specific bug-fix?18:04
espdemorris: got a link?18:04
espopps18:04
espdenis_makogon: got a link to the bp?18:04
denis_makogon#link https://bugs.launchpad.net/trove/+bug/128768418:04
espthx18:04
robertmyersI'm not sure all impl's should be in the same file18:05
denis_makogonfor future possible refactoring and extracting guest code or etc18:05
amcrnagree with robertmyers18:05
robertmyersit makes sense that they are separate18:05
SlickNikdenis_makogon: Can you give some concrete examples why this is needed, and what it buys us?18:05
SlickNik+1 robertmyers18:05
*** jcru has joined #openstack-meeting-alt18:05
amrith+1 robertmyers18:05
*** rjrjr_ has quit IRC18:05
vipulo/18:05
robertmyerswe should however make it easier to configure18:05
denis_makogonrobertmyers, first of all we don't need to pollute config values each time each datastore add support of some kinds of features18:05
denis_makogonbackup/restore the exact use case18:06
robertmyersdenis_makogon: yes, but consolidating is not the answer18:06
*** saurabhs has joined #openstack-meeting-alt18:06
amcrnthe backup strategy conf parameters should be moved under the datastore subheaders (i.e. [mysql], etc.)18:06
SlickNikdenis_makogon: That would point to needing some sort of lazy loading of config values.18:06
amrithit strikes me that this is a reaction to the review of 7833918:06
robertmyersmaking the config options better, or easier to split up18:06
denis_makogonif we would not store them in one place, we would need to add another one config attr per datastore that reflects the actual place where strategy implemented18:07
*** jasonb365 has joined #openstack-meeting-alt18:07
denis_makogonamcrn, why they should be moved ?18:07
amcrndenis_makogon: your comment above just agreed with me18:07
robertmyerspersonally I think we should tranistion to stevedore for these18:07
kevinconwaywho is steve?18:08
SlickNikrobertmyers: +118:08
grapexkevinconway: It's like Steve Holt I think18:08
robertmyersthat way you could add your own impl with setup.cfg18:08
amcrngrapex: +100 for AD reference18:08
denis_makogonamcrn, i think we need to store all strategies in impl.py files, thats all18:08
*** SnowDust has joined #openstack-meeting-alt18:08
SlickNikrobertmyers: Yes, we need to do some work to transition to installing the guest using setup.cfg before we can do that though.18:08
*** padkrish has quit IRC18:09
amcrnrobertmyers: in lieu of that now, i think we're all agreed it should not be in the same file, and given that, the impl should be defined under each optgroup, no?18:09
robertmyersSlickNik: true18:09
robertmyersamcrn: I think so18:09
*** yogeshmehra has joined #openstack-meeting-alt18:09
SlickNikamcrn: agreed.18:10
denis_makogonso, the the answer is - implement the it another way, just add strategy name space per datastore ?18:10
esmuteThe thing about making the same file is that it would be hard to be shared with other part of the code. I put a patch to move the storage strategy from the guest to trove common so that the TM can use it for deleting/copy backups18:11
esmute#link https://review.openstack.org/#/c/86242/18:11
kevinconwayi understand that the config parameters were moving into datastore specific sections right?18:11
kevinconwayso [mongodb]18:11
SlickNikesmute: I don't think we're moving it into the same file.18:11
denis_makogonkevinconway, i guess yes18:12
robertmyersesmute: we want to split the guest out eventually18:12
robertmyersso less shared code18:12
SlickNikOkay, so that's approaching 15 minutes.18:12
esmuteSlickNik: i thought that was what denis_makogon was proposing18:12
*** NehaV has joined #openstack-meeting-alt18:12
esmuterobertmyers: nice :-)18:12
SlickNikI think we're all agreed that we shouldn't have it all in 1 impl file, and that we should have the config opts per datastore. Eventually move to something like stevedore for loading the strategies.18:13
denis_makogonso, what's the actual answer to this topic ?18:13
cweidSlickNik: +118:14
kevinconwaywhere can we read more on steve dore?18:14
denis_makogonget it18:14
SlickNikdenis_makogon: What's the question?18:14
SlickNikIf there are any other clarifications / questions let's bring it up in the channel.18:14
grapexkevinconway: Your local library!18:14
grapexTo quote an afterschool special18:14
denis_makogoni heard what i want, so we can move on18:15
SlickNik#topic Moving the docs18:15
*** openstack changes topic to "Moving the docs (Meeting topic: trove)"18:15
cweidkevinconway: http://stevedore.readthedocs.org/en/latest/18:15
SlickNikgrapex: yer up18:15
grapexThanks SlickNik18:17
grapexso at the midcycle meetup we talked of moving the docs from the apidocs repo into the trove repo18:17
grapexSo moving this: https://github.com/openstack/database-api to this: https://github.com/openstack/trove18:18
*** caleb_ has joined #openstack-meeting-alt18:18
grapexBasically, we'd take the apidocs directory of the "database-api" repo and move it into the root of Trove18:19
grapexAdditionally, maybe we should kill the "openstack-database-api" directory18:19
grapexhttps://github.com/openstack/database-api/tree/master/openstack-database-api18:19
grapexthere's very little in it18:19
grapexSo I guess my questions are18:19
grapex1. since the midcycle meetup, has anyone decided this is a bad idea18:20
grapexand 2. does removing the openstack-database-api directory seem like a bad idea18:20
*** zns has joined #openstack-meeting-alt18:20
dougshelley66would this info ultimately end up in "openstack-manuals"?18:21
espgrapex: would you leave  openstack-database-api around for a bit during the transition or just link it to the new location?18:21
grapexdougshelley66: Yes18:21
dougshelley66so would that process be owned by Anne G?18:22
grapexesp: We could leave it in the openstack/database-api repo18:22
grapexbut I don't think it's being used18:22
grapexthe last update was 8 months ago18:22
*** yogeshmehra has quit IRC18:22
grapexdougshelley66: I'd email everyone involved in the docs. She heard this plan at the meetup and was ok with the notion.18:22
espgrapex: k18:22
dougshelley66grapex: i presume someone would have to do that conversion?18:23
*** rpodolyaka1 has quit IRC18:23
robertmyers+1 on consolidating docs18:23
grapexdougshelley66: Sure, I can do it.18:23
SlickNikgrapex: ajaeger seems to be the most active committer to that database-api repo. I'd make sure to doublecheck with him as well.18:23
kevinconwayshouldn't every doc get it's own directory?18:23
grapexSlickNik: I have the email ready to send right now to Andreas18:23
dougshelley66grapex: i meant the conversion to the format of the rest of the openstack-manuals content?18:23
grapexdougshelley66: Hmm.. I don't know. My guess is we'll see if moving it interferes with anything the doc team wants to do, and if it does we'll hold off or figure out a better plan18:24
dougshelley66i have no issue with moving it - was just asking the longer term question18:25
*** caleb_ has quit IRC18:25
*** beyounn has joined #openstack-meeting-alt18:25
SlickNikgrapex: I also think it would be a good idea to check with the doc team and figure out if there's a way for them to consume this so that we don't end up having to duplicate this info in 2 places when they need to produce a docbook.18:26
grapexSlickNik: def18:26
*** caleb_ has joined #openstack-meeting-alt18:27
*** yogesh has joined #openstack-meeting-alt18:27
SlickNikSweet, any other comments on this?18:27
SlickNikLet's move on.18:28
SlickNik#topic Design Summit Session Proposals18:28
*** openstack changes topic to "Design Summit Session Proposals (Meeting topic: trove)"18:28
SlickNikThis is everyone. :)18:28
SlickNikPlease get your proposals in for the design summit in ATL.18:29
SlickNik#link http://summit.openstack.org/18:29
amrithdon't everybody step forward at the same time18:29
denis_makogonSlickNik, when the deadline for the submitting ?18:29
mattgriffindenis_makogon, the 20th18:29
denis_makogonmattgriffin, hah, my birthday =)18:30
denis_makogonmattgriffin, thanjs18:30
mattgriffin:)18:30
denis_makogoni have some ideas for the design session related to replication use case B18:30
SlickNikhub_cap, the rest of the cores and I are planning on doing a pass to review these early next week (for scheduling) so please try and get them in by end of this week.18:31
hub_capSlickNik: and i are going to add sessions to address the defecits we have in the integration process18:31
annegentlehey I can circle back on that docs question if you want grapex SlickNik (sorry so late) :)18:32
hub_cap++ w annegentle18:32
SlickNikThat's pretty much all I had for the summit sessions, so yes we can get back to docs. :)18:32
SlickNik#topic Moving the docs18:33
*** openstack changes topic to "Moving the docs (Meeting topic: trove)"18:33
annegentleso I was thinking you'd bring database-api into your trove/doc repo18:33
annegentleAndreas has nice JSON validation tests and so on18:33
grapexannegentle: Me too18:33
annegentlego for it! :)18:33
grapexI think we can merge the tox file and add the new targets to the Trove tox file18:33
annegentlegrapex: cool18:33
grapexannegentle: I'll be sure to email Andreas still18:33
annegentlethat's ideally, really, keep api docs near code18:33
grapexsince he hs def. put in the miles on it right now18:34
grapexannegentle: I agree- it will help us tremendously in keeping them up to date18:34
annegentlenow the install doc I'm still seeking help on, Laurel is working on it, but the apt package isn't available yet, etc. So it's hard to get going18:34
annegentlethe bug is https://bugs.launchpad.net/openstack-manuals/+bug/130458418:34
annegentleif you can offer any notes or suggestions or anything, please put it in that bug.18:35
grapexannegentle: Will do18:35
annegentlesuch as: how to make the VM, what platforms you know it works on, all that good info18:36
annegentlethanks!18:36
grapexannegentle: Thanks Anne!18:37
SlickNiklaurelm: If there specific areas that we can look at to help this along, let us know. I'd be happy to put together some info to fill in places where we might have gaps.18:37
cp16netwhat happened to the that we had some people were working on18:37
SlickNikThanks annegentle!18:37
cp16neti reviewed it but never saw an update on it18:37
SlickNikOh you mean this one cp16net: https://review.openstack.org/#/c/8580318:38
cp16netno...18:38
cp16netthat one is new18:38
cp16netSlickNik: this one https://review.openstack.org/#/c/78608/18:39
laurelmSlickNik: will do18:39
annegentlecp16net: yes that API doc is different from database-api slightly; api-site is a reference listing for end users of the API (think: sdk devs)18:39
*** _nadya_ has joined #openstack-meeting-alt18:39
annegentlecp16net: and as for a manual installation guide, we're looking for a chapter that plugs into somethign like http://docs.openstack.org/havana/install-guide/install/apt/content/18:39
annegentlewhich we work on across four distros18:39
cp16netok18:39
SlickNikAnything else to add here?18:40
annegentlecp16net: are you Craig? Cuz your review of https://review.openstack.org/#/c/78608/ is great -- just need that info for four distros in another location is all18:40
cp16netannegentle: yup18:40
annegentlecp16net: kk thought so :) I'm getting good at this IRC mapping18:41
cp16netthats my -1 ;-P18:41
annegentlecp16net: so that looks really nearly there, laurelm all you have to do is convert it to docbook and get it as a chapter in the openstack-manuals install-guide18:41
*** malini1 has quit IRC18:41
annegentlecp16net: laurelm: I could do a first pass if we want, get it into the community faster18:41
dougshelley66annegentle: that is what we are doing. We went thru that document, clarified some things for laurelm and she is creating the docbook.18:42
annegentleI just hate to do it if laurelm has a head start18:42
cp16netok i dunno who that was that started that review but it was a good start18:42
annegentledougshelley66: ok, great! That's it then18:42
annegentlesorted.18:42
SlickNikdougshelley66 / laurelm: Super; I'm not familiar with the docbook format, but I can help with information / editing once we have something out there.18:43
dougshelley66SlickNik - thx sounds good18:43
*** n0ano has joined #openstack-meeting-alt18:44
SlickNikOkay, we're good with that. Moving on...18:44
annegentledougshelley66: yeah the main thing is get it in the repo for reviews as soon as you can, we'll get it better and better18:44
SlickNik#topic Open Discussion18:44
*** openstack changes topic to "Open Discussion (Meeting topic: trove)"18:44
kevinconwayo/18:44
kevinconwaykey signing18:45
kevinconwaythat is all18:45
cp16neti just did that refresh your keys18:45
SlickNikkevinconway: I signed the key! :)18:45
SlickNikkey(s)18:45
amrithmy key hasn't been signed ;(18:45
amrithonly Justin and Andrew did ;(18:45
kevinconwayamrith: i must have missed yours. will fix that18:46
SlickNikamrith: I could've sworn I signed yours as well (did I forget to push it back up?) I'll double check.18:46
*** kgriffs|afk is now known as kgriffs18:46
kevinconwayso that's four of us that are working on it. what about the other 20?18:47
*** greghaynes has left #openstack-meeting-alt18:47
SlickNiklol kevinconway. The WoT grows slowly.18:47
SlickNikAny other items?18:47
SlickNikbtw kevinconway: https://github.com/dreamhost/stevedore18:48
SlickNikIf there's nothing else, I'm more than happy to end this early.18:48
SlickNikgoing, going....18:48
dougshelley66+118:48
grapexSlickNik: do it, do it, do it...18:48
SlickNik#endmeeting18:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:48
openstackMeeting ended Wed Apr  9 18:48:57 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-04-09-18.00.html18:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-04-09-18.00.txt18:49
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-04-09-18.00.log.html18:49
grapex\o/18:49
SlickNikThanks all.18:49
SlickNiksee you in #openstack-trove18:49
*** jprovazn_bbl has quit IRC18:50
*** SlickNik has left #openstack-meeting-alt18:51
*** esp has left #openstack-meeting-alt18:53
*** CaptTofu has quit IRC18:56
*** yogesh has quit IRC18:58
*** yogesh has joined #openstack-meeting-alt18:58
*** jamie_h has joined #openstack-meeting-alt18:59
*** robertmyers has left #openstack-meeting-alt19:00
*** otherwiseguy has joined #openstack-meeting-alt19:00
mferycombinator are we good to have our meeting in here now?19:00
*** samchoi has joined #openstack-meeting-alt19:00
ycombinatoryes, just waiting on ... there he is19:00
samchoihello19:00
ycombinatorhi19:00
mfer#startmeeting openstack-sdk-php19:01
openstackMeeting started Wed Apr  9 19:01:07 2014 UTC and is due to finish in 60 minutes.  The chair is mfer. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: openstack-sdk-php)"19:01
openstackThe meeting name has been set to 'openstack_sdk_php'19:01
mfer#topic State of repo19:01
*** openstack changes topic to "State of repo (Meeting topic: openstack-sdk-php)"19:01
mferCan everyone state your names and associations if there is one.19:01
mferMatt Farina, HP19:01
jamie_hJamie Hannaford, Rackspace19:01
ycombinatorShaunak Kashyap, Rackspace19:02
samchoiSam Choi, HP19:02
mferThis meeting is to discuss the state of the repo...19:02
glencGlen Campbell, Rackspace19:02
*** yogesh has quit IRC19:03
jamie_hshall we start where we left off?19:03
mferto restate the starting point from earlier....19:03
mfer"We have an SDK that we contributed to stackforge and altered to be OpenStack rather than HP Cloud. We have a larder codebase than we released because we went all in on OpenStack rather than continuing to drive our own. We wanted to make the needed changes for OpenStack before we added service...."19:03
mfer"For example, there are things like multiple api version support that needed to happen."19:03
mferthat's copied and pasted from the earlier meeting19:04
ycombinatoralso: "from a general contributor perspective, wouldn't it be easier to start from an empty repo, though?"19:04
ycombinatorthat was me19:05
*** eanxgeek is now known as eanxgeek|log19:05
ycombinatorand "<jamie_h> yes. no legacy decisions, cleaner code, and it allows members to be included from the very beginning"19:05
ycombinatorand " <mfer> i'm curious to know why? many folks prefer to join into an architecture that's already there so add to it or work on needed tasks."19:05
mferand then we ran out of time19:06
*** pdmars has quit IRC19:06
*** edleafe has joined #openstack-meeting-alt19:06
ycombinatoryup19:06
ycombinatorso I'll put forth my take19:06
ycombinatorto kick us off19:06
samchoisure, would be good to clear up each individual's thoughts as it's unclear. And we can go over pros/cons of each approach as you noted.19:07
*** dshulyak_ has quit IRC19:07
*** chandan_kumar_ has quit IRC19:07
ycombinatorstarting with a set of use cases -> blueprints -> reviews against a blank repo seems like the right way to approach the project19:07
ycombinatoras opposed to modifying existing code19:08
ycombinatorI'd be quite happy if parts of the existing code were "imported" into a blank project as long as a) they matched a blueprint and b) they were reviewed by all of us19:09
mferycombinator fyi, i'm waiting to ask questions until you've let me know your complete thought19:09
ycombinatoryeah - almost done :)19:09
*** k-pom has left #openstack-meeting-alt19:09
ycombinatorright now, I confess it feels like I'm having to learn an existing codebase just to have to revise parts of it19:10
ycombinatorokay, I'll step down with that for Q&A and for someone else to go19:10
*** jtomasek has quit IRC19:11
jamie_hno questions, but i agree with the import idea19:11
mferycombinator starting with a blank repo you need to have a base architecture. where does that fit into your use cases -> blueprints -> reviews picture?19:12
jamie_hmfer what do you mean by "base architecture"?19:12
jamie_has in directory structure?19:12
*** _nadya_ has quit IRC19:12
ycombinatorif my understanding of blueprints are correct, I think thats where it would happen19:12
mferthe software architecture for the codebase. it's more than directories19:12
ycombinatorblueprints + wiki, perhaps19:12
jamie_hthere's a blueprint for the workspace (directory structure). each service's design is discussed separately19:13
ycombinator(someone please feel free to direct me to how architecture type decisions are made in openstack)19:13
mferalso, what we already have started with the use cases -> tickets -> review process internally. how does resetting the codebase to do that over come into account?19:13
*** rand738 has quit IRC19:13
jamie_hbecause forcing people to use an existing codebase, which has not been reviewed by others, does not match the standard review process19:13
mferi do appologize that the current blueprints don't reflect that kind of detail19:13
ycombinatorno need mfer, we are all supposed to bear that burden19:14
edleafeycombinator: Generally blueprint+wiki for each proposed design, followed by discussion in email or IRC19:14
mferif I understand it, most openstack project were contributed projects not reviewed by others. then others came in to be part of the development process19:14
edleafe…or discussion at a Design Summit ;-)19:14
*** jmontemayor has quit IRC19:14
edleafemfer: that was probably only true of Swift19:15
edleafe…since that was already code in production when OpenStack was created19:15
jamie_hi also think we need to make this decision based on the pros and cons, and arrive at a decision best for the project. not based on what other projects did in the past19:15
edleafeNova went through a *lot* of design reviews19:15
edleafejamie_h: Agreed; just letting you in on some history19:16
edleafethat's what us old-timers are good for  ;-)19:16
*** hub_cap has left #openstack-meeting-alt19:16
jamie_hha19:16
mferedleafe so, Nova was contributed to openstack and then went though reviews? Were the reviews during incubation or at other point in time?19:16
*** colinmcnamara has quit IRC19:16
glencThere were a ton of reviews and a lot of revisions in 2011 when it was getting off the ground19:17
edleafeNova was originally the nebula project at NASA - lots of good ideas, but written for a particular use case19:17
edleafee.g., instances were not designed to persist19:17
mferwas it contributed before or after the changes?19:17
edleafeit was used more as a strawman19:17
mferand was it changed or rewritten from scratch?19:17
glenc(I was on the Nova team at that time). The nebula code was pre-existing, but it wasn't nearly ready. My guess is that very little was kept; most was replaced.19:18
edleafemostly written from scratch19:18
*** rand738 has joined #openstack-meeting-alt19:18
edleafeit was too hard to fit into a broader use case that the various parties needed19:18
glencSort of used as a template, but much of it wouldn't scale well.19:18
mferedleafe if it didn't have those issues would so much of it have been rewritten?19:18
edleafemfer: well, that was the point. The issues existed because it was written for a single use case19:19
jamie_hwe have those issues with the current codebase too...19:19
edleafeto make it something that could be the basis of OpenStack Nova, we largely started from scratch19:19
jamie_hit doesn't reflect at all our plans for the transport or service layer, so it really does warrant new code19:20
mfernot exactly, with a minimal amout of work we can change the existing codebase to not have those issues19:20
jamie_hi disagree19:20
*** chandan_kumar_ has joined #openstack-meeting-alt19:20
jamie_hit will require more effort and time than writing fresh code19:20
jamie_hand it will probably cause more bugs in the future than a clean slate19:20
*** rpodolyaka1 has joined #openstack-meeting-alt19:20
jamie_hplus, you'd have to completely rewrite your tests - which is a nightmare for existing projects19:21
edleafeThe general rule is that code talks. If you think something can work, code it and let everyone review it19:21
mferthat's an interesting persepctive. it would likely be more time for you to write the code because you aren't intimately familiar with the existing codebase. i'm already quite familiar with the codebase and coding up the needed changes19:21
samchoijamie_h: so let's discuss the short term road map. https://wiki.openstack.org/wiki/OpenStack-SDK-PHP19:21
samchoiWhich requirement(s) would be difficult to fulfill?19:22
samchoiWith the current repo19:22
mferedleafe we have a plan to get where we'd planned on going with tweaks to the existing codebase to meet the wider needs. things i've discussed with others like Jesse Noller, Dean Troyer and other. we've been coding to go there19:22
mferi'll admit that more of the details could use documentation19:22
mferearlier today I volunteered to do more of that19:22
edleafemfer: OK, sounds good. But yeah, docs would be a huge help19:23
edleafeIf others don't think the current path will get us there, I would encourage them to likewise document a different approach19:24
samchoiFrom the road map, I feel that 3, 7, and 8 are quite trivial requirements so maybe out of the other 5 there are issues you all see?19:24
mferin an email earlier this week I suggested two reasons to start with a fresh repo. 1) There was a technologically superior solution. Something measurable or very obvious that we'd need a clean repo to do. 2) we could get to a release faster while meeting all the requirements.19:24
jamie_hsamchoi Mainly the transport and service layer. If you'd like me to draw up a detailed analysis of what will be particularly difficult to implement, I can do so. but the general point still stands: asking 3 people to rewrite your code will take longer, and considerably more effort, than a fresh start19:24
mferedleafe note, this dicussion isn't around changing the architecture. it's about wiping the codebase and starting from scratch. we are updating the architecture and actively discussing changes.19:25
jamie_hplus the existing codebase is not PSR-2 compliant, there's a reliance on singletons, etc.19:25
samchoithanks for clarifying19:25
edleafemfer: Understood19:26
ycombinatorin general, its going to take anyone not familiar with the existing codebase longer than those who are19:26
jamie_hand inclusivity is one of our most important goals19:26
mferjamie_h there is a task for be PSR-2 and and tool to automate that change.... thanks to fabpot. the singleton left has a blueprint to remove which is fairly straight forward19:26
jamie_hreduce barriers for entry, not raise them19:26
ycombinatorif we wipe clean and start with blueprints first we ensure that there is an shared understanding as we submit reviews19:26
jamie_hmfer these are two, i agree, incidental points. but it's endemic of the wider issue19:26
ycombinatoragain, I think its perfectly okay to "import" existing code so as not to lose existing work - as long as its conforms to agreed-upon blueprints which will give all of us a shared understanding of what to expect from the code19:27
mferjamie_h i've thought a lot about the service layer. i think it's a great idea. i've even mentally worked out how to alter the existing codebase to get things there. i was waiting to see what you'd come up with after our last chat on it.19:27
mferycombinator if we start with a new codebase then no one will be familiar with the codebase19:28
jamie_hi agree completely with what shaunak said: i'm not against any existing piece of code, we can re-import so long as everyone gets a fair say over the design19:28
jamie_hmfer but it puts people on level footing19:28
jamie_hand we can quickly iterate over new designs or re-import existing code19:28
jamie_hbut there needs to be a fair process19:28
mferand how does that help progress the project?19:28
ycombinatormfer: what jamie_h said + we would all be agreeing to designs first, which I think is an important step19:28
mferthe goal is to produce a PHP SDK for end users19:28
samchoiI also don't see how that helps with progress19:28
jamie_hit's important for the community and it will make non-HP workflow faster19:28
mferthat's saying that it's for an HP workflow now19:29
mferand that the current path continues that trend19:29
*** derekh has joined #openstack-meeting-alt19:29
jamie_hall i'm saying is that you're familiar with the codebase and we're not19:29
mferlots of codebases start that way. i've been doing open source a long time. when i approach an existing codebase i always have stuff to learn19:30
mferi'm not sure how that helps move this along at a good pace19:30
edleafemfer: True, but OpenStack is a different beast19:30
jamie_hbut this is not any other codebase. this is our chance to make a great openstack project19:30
mferi agree19:30
jamie_hmfer i guarantee you that with a fresh codebase, i'll be committing every single day and we'll gain rapid pace19:30
edleafeI've had to scrap a bunch of working existing code in order to get a community around the Python SDK19:31
mferedleafe i understand that. i've been spending a lot of time trying to understand the way the community operates19:31
mferand how to work well in it19:31
*** akuznetsov has quit IRC19:31
edleafemfer: yeah, it's not easy. I just want to say "HERE THIS STUFF WORKS! USE IT!", but that wouldn't help in the long run19:32
*** caleb_ has quit IRC19:32
jamie_hi really wouldn't suggest a fresh repo if i didn't think it had a lot of positive advantages (for workflow + community engagement)19:32
*** akuznetsov has joined #openstack-meeting-alt19:32
mferit's more like, here's the stuff, it works well, we have a path to make some changes, and we're actively working to get it out to people19:33
mferjamie_h break that down. how does starting new help the workflow?19:33
mferput aside the community engagement for a moment19:33
*** akuznetsov has quit IRC19:33
glencI think there's a frustration that people aren't able to contribute significantly because they essentially have a learn a new codebase, and one that does not match the target.19:34
jamie_hit speedens up the workflow for every single developer who isn't intimate with the codebase. which, right now, is everybody except HP19:34
samchoiThe story behind the initial code that's in stackforge right now is that mfer and another senior engineer created the initial php sdk. I was brought on board in 2012 to add additional services. It took me 2-3 days to understand the code base without much PHP experience at the time. So I don't think what's in stackforge at the moment is too complex for most.19:34
edleafemfer: I'm approaching it like a new product, but since I've written an SDK before, I know how to avoid lots of the dead ends, and where there be dragons.19:35
mfera fresh codebase would run the problem of everyone having to learn all of it while we discuss the foundation for it.19:35
jamie_hwe're not learning anything with a new codebase. we're creating it.19:35
jamie_hcreating it with an approved process of review19:35
mferwe're all laerning what's being created by others19:35
jamie_hbut that's the nature of a collaborative project19:35
*** SnowDust has quit IRC19:36
jamie_hright now, there's an entire codebase which has not been scrutinised by the openstack community. all i'm saying is that it needs to be.19:36
ycombinatorthis is a community issue: we would feel much more comfortable starting on level ground with everyone else on the project19:36
ycombinatorand right now, thats not the case19:37
mferi've worked on many collaborative projects. i think the difference here is we asked folks to come collaborate with us on where we are going and actively contributing to. the suggestion is to burn down the village so that everyone can work together to architect and build it.19:37
jamie_hthat's your personal choice of metaphor19:37
*** _nadya_ has joined #openstack-meeting-alt19:37
jamie_hopenstack is about full transparency and equality. having a new codebase does that: it opens everything up for review and puts people on a level footing19:38
jamie_hthis is a new, community-driven project: not the continuation of a private codebase.19:38
mferi'll go back to something edleafe said. he noted that code talks. there have been some good ideas for you fine folks. we've gone and coded them.19:38
mferand in understand. you don't want to get involved if it's not coded from scratch19:39
jamie_hthis is not an argument of principle, there are strong arguments at stake here19:39
mferi've not seen how this applies to technical problem in teh codebase that cant' be easily overcome19:39
*** balajiiyer has left #openstack-meeting-alt19:39
mferit seems it's a matter of start clean or you're not going to get started19:40
mferwhich is quite different from the nova disucssion/example earlier19:40
jamie_hthe technical reason is that a fresh slate offer significantly more freedom to implement agreed-upon designs19:40
jamie_hyou're not constrained by legacy (unapproved) decisions19:41
ycombinatorits a matter of making everyone feel equally involved from the start19:41
glencI see the issues are more political than technical. As you said, we can all eventually learn an existing codebase. In the past, companies like Rackspace have gotten trashed for "contributing" a bunch of existing code without involving the community; this is why Solum and the python SDK started off clean, even though we had existing code.19:41
ycombinatorright now, by virtue of there being a pre-existing, not-approved-by-all codebase, we are not all equally involved from the start19:42
glencI suppose we could always go through the existing codebase and submit changes for stuff that doesn't match the desired end state, even to the extent of removing it. That would go through the approval process. Still seems inefficient, but it could work.19:42
jamie_hi don't mind using any of the existing codebase so long as it goes through gerrit first19:43
jamie_hand we all have a say19:43
ycombinatorright, that's my "import" suggestion19:43
jamie_hyeah19:43
mferfor me this isn't political but pragmatic. openstack needs some solid SDKs and we're actively working to produce a PHP one. if there is a more technically sound way to do that or a way to get it out there quicker I'm happy so look at that. This is pragmantic to meet the needs of the end users19:43
*** eanxgeek|log is now known as eanxgeek19:44
samchoiycombinator: jamie_h so that main argument is that you both need to be equally involved from the start, right? After a few weeks, we would have a codebase similar in size to what's in stackforge right now since it's fairly small. Newer contributors may also come along, but it wouldn't be prudent for them to ask us to scrap the codebase without pragmatic reasons.19:44
ycombinatorsamchoi: the difference is that by then we'll have a set of blueprints to go with the codebase19:45
jamie_hit's primarily a political and community issue, which can't really be trumped by the premise that going down the "existing codebase" avenue will save us a few hours19:45
ycombinatorright now we don't have that19:45
mferycombinator we already have a set of blueprints to go with the codebase19:45
samchoijamie_h: considering where the python sdk is at today, probably more than a few hours ;)19:46
jamie_hsamchoi: this is a bigger issue than me and shaunak. it's symbol of a wider need for equality and inclusivity19:46
mfereveryone is equally invited to get involved.19:47
mferthis is different from that19:47
jamie_hnot when half of the code has not been reviewed by others19:47
jamie_hsorry, all of the code19:48
mferothers have not taken the time to review the code. they are welcome to come in, file bugs, use it, etc.19:48
jamie_hbecause the basic premise is flawed: there is extant code in the repo which has not been officially reviewed19:48
mferwhy does the openstack infra team have an explicit way to import code for a new project if that's not something that should be done?19:48
*** caleb_ has joined #openstack-meeting-alt19:49
mferyou point the tool at the existing repo and it pulls it in19:49
*** thang_ has quit IRC19:49
*** chandan_kumar_ has quit IRC19:49
mfersince this is being described as a community process issue, I need to do follow-up from outside this group.19:50
*** caleb_ has quit IRC19:50
mferif it's not been articulated enough please feel free to add more details19:50
edleafemfer: Good idea. Talk to Jesse and Dean about the discussions on these lines we've had on the Python SDK side19:51
*** caleb_ has joined #openstack-meeting-alt19:51
jamie_hso, from my perspective, the follow up strategy needs to be: wipe the codebase and mass import the existing features we want19:52
jamie_hwhich will go through gerrit and be merged back in the library19:52
ycombinatorI'll summarize my thoughts one more time for external follow up19:52
ycombinatorwe have an opportunity to start with designing in the open (using blueprints) and submitting reviews against these blueprints (which could be imports of existing code) to let all contributors have an equal say from the start19:53
*** greghaynes has joined #openstack-meeting-alt19:53
*** d0ugal has quit IRC19:54
jamie_hso mfer and samchoi, where do you stand? are you up for having a try at what shaunak suggested?19:55
mfermy stance is i need to do some external follow-up before i have any further stance19:56
ycombinatorI think that's fair mfer19:57
mferis there anything else?19:57
ycombinatorcould you include us on those follow up conversations as well, please?19:57
samchoithat's fine, will need follow up in any case19:57
jamie_hmfer also, what exactly are you following up?19:57
*** mspreitz has joined #openstack-meeting-alt19:57
jamie_hthe process of importing?19:58
mferycombinator where appropriate i will. some of this is personal mentors and direction in the community type stuff19:58
*** _nadya_ has quit IRC19:58
ycombinatormfer: understood19:58
ycombinatorthanks19:58
mferif not before, next week we'll continue this at the normal meeting time. for meeting things that is19:58
mferemails and side discussions may happen in between.19:58
mfersound good?19:58
jamie_hi had a question above19:58
mferyou mean on what i'm following up on?19:59
jamie_hyeah, i wasn't 100% sure, sorry19:59
mferto understand community processes, history, decision making, project context, etc19:59
mferlots of background on the community angle to this discussion19:59
jamie_hsure, okay. perhaps we could reach out to folks in the openstack community too20:00
*** BillArnold has joined #openstack-meeting-alt20:00
jamie_hso next wednesday is good for everyone?20:00
samchoiBtw, jamie_h ycombinator what are you primary considerations for choosing one approach over another? I can be convinced either way but want to see what everyone's thought process is and their rationale20:00
mferthat's one of the things i'm going to do and have been doing since i released this codebase to the community20:01
*** atiwari has quit IRC20:01
jamie_hawesome, it's definitely an important step before we release any more code20:01
*** david_lyle_ has joined #openstack-meeting-alt20:01
ycombinatorjamie_h I think the wednesday 1530 UTC meeting in openstack-meeting-3 is set for good now20:01
samchoiI think one of the issues is that each individual's criteria for choosing a starting approach is quite different20:02
jamie_hsamchoi: i can follow up over e-mail if you'd like. is that okay with you?20:02
samchoioh certainly, I forgot it's quite late for you20:02
samchoimy apologies jamie_h20:02
jamie_h:)20:02
*** zns has quit IRC20:02
*** otherwiseguy has quit IRC20:03
*** dklyle has joined #openstack-meeting-alt20:03
*** david-lyle has quit IRC20:04
mferthe hour is up. i'm not sure if aother meeting is coming in here.20:04
mferdon't want to step on anyone elses toes atain20:04
mfers/atain/again20:04
mferif there's nothing else I'll end the meeting to respect everyones time20:04
jamie_hsure, i have nothing else20:05
glencok20:05
mfer#endmeeting20:05
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:05
openstackMeeting ended Wed Apr  9 20:05:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-04-09-19.01.html20:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-04-09-19.01.txt20:05
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-04-09-19.01.log.html20:05
*** eanxgeek is now known as eanxgeek|log20:06
*** beyounn has quit IRC20:06
*** caleb_ has quit IRC20:06
*** david_lyle_ has quit IRC20:06
*** eguz has quit IRC20:07
*** eghobo has joined #openstack-meeting-alt20:07
*** tedchang has quit IRC20:08
*** eanxgeek|log is now known as eanxgeek20:08
*** d0ugal has joined #openstack-meeting-alt20:09
*** d0ugal has quit IRC20:09
*** d0ugal has joined #openstack-meeting-alt20:09
*** rpodolyaka1 has quit IRC20:10
*** atiwari has joined #openstack-meeting-alt20:10
*** baoli has quit IRC20:10
*** mwagner_lap has joined #openstack-meeting-alt20:10
*** eanxgeek is now known as eanxgeek|log20:11
*** jcoufal has quit IRC20:13
*** yogesh has joined #openstack-meeting-alt20:13
*** zns has joined #openstack-meeting-alt20:13
*** NehaV1 has joined #openstack-meeting-alt20:14
*** openstackstatus has quit IRC20:15
*** openstackstatus has joined #openstack-meeting-alt20:16
*** NehaV has quit IRC20:17
*** eanxgeek|log is now known as eanxgeek20:17
*** yogesh has quit IRC20:18
*** markmcclain has joined #openstack-meeting-alt20:21
*** noslzzp has joined #openstack-meeting-alt20:27
*** manishg_ has left #openstack-meeting-alt20:29
*** jcoufal has joined #openstack-meeting-alt20:32
*** zns has quit IRC20:32
*** caleb_ has joined #openstack-meeting-alt20:32
*** zns has joined #openstack-meeting-alt20:34
*** harlowja is now known as harlowja_away20:36
*** zns has quit IRC20:36
*** iccha has left #openstack-meeting-alt20:37
*** michael-yu has quit IRC20:37
*** zns has joined #openstack-meeting-alt20:37
*** beyounn has joined #openstack-meeting-alt20:38
*** otherwiseguy has joined #openstack-meeting-alt20:42
*** vk has joined #openstack-meeting-alt20:49
*** cp16net has left #openstack-meeting-alt20:53
*** eanxgeek is now known as eanxgeek|log20:53
*** jdob has quit IRC20:54
*** harlowja_away is now known as harlowja20:55
*** manishg___ has joined #openstack-meeting-alt20:56
*** pdmars has joined #openstack-meeting-alt20:56
*** kevinconway has quit IRC20:57
*** jecarey has quit IRC20:57
*** BillArnold has quit IRC20:57
*** BillArnold has joined #openstack-meeting-alt20:57
*** nati_uen_ has quit IRC20:59
*** manishg___ is now known as manishg20:59
*** colinmcnamara has joined #openstack-meeting-alt21:02
*** dklyle is now known as david-lyle21:03
*** rramirez has quit IRC21:03
*** mspreitz has left #openstack-meeting-alt21:04
*** michael-yu has joined #openstack-meeting-alt21:04
*** zns has quit IRC21:04
*** derekh has quit IRC21:05
*** jecarey has joined #openstack-meeting-alt21:07
*** kevinconway has joined #openstack-meeting-alt21:07
*** rueb7363 has joined #openstack-meeting-alt21:09
*** rueb7363 has quit IRC21:10
*** rueb7363 has joined #openstack-meeting-alt21:10
*** BillArnold has quit IRC21:10
*** rpodolyaka1 has joined #openstack-meeting-alt21:11
*** eghobo has quit IRC21:12
*** kgriffs is now known as kgriffs|afk21:12
*** openstackstatus has quit IRC21:14
*** gokrokve has quit IRC21:14
*** rpodolyaka1 has quit IRC21:15
*** jcoufal has quit IRC21:16
*** eankutse1 has joined #openstack-meeting-alt21:17
*** eankutse1 has quit IRC21:17
*** kgriffs|afk is now known as kgriffs21:19
*** sowmini has quit IRC21:19
*** eankutse has quit IRC21:20
*** zns has joined #openstack-meeting-alt21:20
*** openstackstatus has joined #openstack-meeting-alt21:22
*** SumitNaiksatam has quit IRC21:23
*** lblanchard has quit IRC21:24
*** rudrarugge has quit IRC21:24
*** gokrokve has joined #openstack-meeting-alt21:27
*** walker_ has quit IRC21:27
*** esker has quit IRC21:28
*** ameade has quit IRC21:30
*** Barker has quit IRC21:30
*** mfer has quit IRC21:31
*** nati_ueno has joined #openstack-meeting-alt21:32
*** markmcclain has quit IRC21:39
*** markmcclain has joined #openstack-meeting-alt21:41
*** hemanth_ has quit IRC21:48
*** grapex has quit IRC21:49
*** nati_ueno has quit IRC21:50
*** jjmb has joined #openstack-meeting-alt21:51
*** hemanth has joined #openstack-meeting-alt21:52
*** demorris has quit IRC21:53
*** nati_ueno has joined #openstack-meeting-alt21:53
*** gokrokve has quit IRC21:58
*** caleb_ has quit IRC21:59
*** david-lyle has quit IRC22:02
*** markmcclain has quit IRC22:02
*** carl_baldwin has quit IRC22:03
*** NehaV1 has quit IRC22:03
*** SumitNaiksatam has joined #openstack-meeting-alt22:07
*** rpodolyaka1 has joined #openstack-meeting-alt22:11
*** gokrokve has joined #openstack-meeting-alt22:12
*** denis_makogon has quit IRC22:12
*** kevinbenton has quit IRC22:14
*** jamie_h has quit IRC22:15
*** rpodolyaka1 has quit IRC22:16
*** jasonb365 has quit IRC22:19
*** SumitNaiksatam has quit IRC22:22
*** julienvey has joined #openstack-meeting-alt22:23
*** noslzzp has quit IRC22:27
*** openstack has joined #openstack-meeting-alt22:34
*** ChanServ sets mode: +o openstack22:34
*** mattgriffin has quit IRC22:37
*** tedross has quit IRC22:37
*** rueb7363 has quit IRC22:38
*** jjmb has quit IRC22:38
*** kevinconway has quit IRC22:40
*** Leonr has quit IRC22:46
*** Haiying has joined #openstack-meeting-alt22:47
*** jjmb has joined #openstack-meeting-alt22:51
*** khyati_ has joined #openstack-meeting-alt22:52
*** hemanth has quit IRC22:55
*** hemanth has joined #openstack-meeting-alt22:56
*** jcru has quit IRC22:56
*** vk has quit IRC22:58
*** Sukhdev has joined #openstack-meeting-alt22:59
*** jjmb1 has joined #openstack-meeting-alt23:01
*** nati_ueno has quit IRC23:01
*** hemanth has quit IRC23:01
*** jjmb has quit IRC23:02
*** jjmb1 has quit IRC23:05
*** julienvey has quit IRC23:07
*** banix has quit IRC23:07
*** eankutse has joined #openstack-meeting-alt23:09
*** eankutse has quit IRC23:10
*** eankutse has joined #openstack-meeting-alt23:11
*** otherwiseguy has quit IRC23:21
*** nati_ueno has joined #openstack-meeting-alt23:22
*** gokrokve has quit IRC23:22
*** jjmb has joined #openstack-meeting-alt23:23
*** jjmb has quit IRC23:23
*** jjmb has joined #openstack-meeting-alt23:23
*** walker_ has joined #openstack-meeting-alt23:32
*** walker_ has quit IRC23:39
*** dprince has quit IRC23:41
*** mozawa has quit IRC23:42
*** jjmb has quit IRC23:49
*** Barker has joined #openstack-meeting-alt23:49
*** manishg has quit IRC23:51
*** atiwari has quit IRC23:53
*** jjmb has joined #openstack-meeting-alt23:55

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