Wednesday, 2014-04-16

*** pdmars has quit IRC00:00
*** sarob has quit IRC00:01
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"00:02
*** atiwari has quit IRC00:04
*** demorris has quit IRC00:10
*** drupalmonkey has quit IRC00:13
*** spzala has joined #openstack-meeting-alt00:18
*** noslzzp has joined #openstack-meeting-alt00:18
*** rmoe has quit IRC00:20
*** Barker has joined #openstack-meeting-alt00:20
*** SumitNaiksatam has quit IRC00:23
*** MarkAtwood has joined #openstack-meeting-alt00:33
*** rmoe has joined #openstack-meeting-alt00:37
*** eguz has quit IRC00:45
*** baoli has joined #openstack-meeting-alt00:53
*** spzala has quit IRC01:01
*** gyee has quit IRC01:03
*** Barker has quit IRC01:09
*** michael-yu has quit IRC01:09
*** mozawa has joined #openstack-meeting-alt01:13
*** rueb7363 has joined #openstack-meeting-alt01:20
*** nati_uen_ has quit IRC01:20
*** marun has quit IRC01:29
*** david-lyle has joined #openstack-meeting-alt01:36
*** amcrn has quit IRC01:39
*** arnaud has quit IRC01:40
*** xuhanp has joined #openstack-meeting-alt01:41
*** julienvey has joined #openstack-meeting-alt01:46
*** cjellick has quit IRC01:50
*** julienvey has quit IRC01:51
*** david-lyle has quit IRC02:03
*** richm has quit IRC02:10
*** flwang has quit IRC02:10
*** eankutse has quit IRC02:15
*** sbalukoff has quit IRC02:19
*** rueb7363 has quit IRC02:28
*** rueb7363 has joined #openstack-meeting-alt02:28
*** noslzzp has quit IRC02:33
*** eankutse has joined #openstack-meeting-alt02:33
*** coolsvap|afk is now known as coolsvap02:35
*** harlowja is now known as harlowja_away02:35
*** julienvey has joined #openstack-meeting-alt02:45
*** noslzzp has joined #openstack-meeting-alt02:50
*** julienvey has quit IRC02:50
*** colinmcnamara has joined #openstack-meeting-alt02:51
*** colinmcnamara has quit IRC03:01
*** sarob has joined #openstack-meeting-alt03:01
*** zhiyan_ is now known as zhiyan03:01
*** demorris has joined #openstack-meeting-alt03:05
*** sarob has quit IRC03:06
*** sergmelikyan has quit IRC03:10
*** sergmelikyan has joined #openstack-meeting-alt03:13
*** ramishra has joined #openstack-meeting-alt03:23
*** beyounn has quit IRC03:23
*** noslzzp has quit IRC03:25
*** Sukhdev has joined #openstack-meeting-alt03:30
*** jecarey has quit IRC03:32
*** SumitNaiksatam has joined #openstack-meeting-alt03:33
*** demorris has quit IRC03:34
*** yamamoto_ has joined #openstack-meeting-alt03:35
*** nosnos has quit IRC03:35
*** eankutse has quit IRC03:42
*** rueb7363 has quit IRC03:43
*** julienvey has joined #openstack-meeting-alt03:46
*** rueb7363 has joined #openstack-meeting-alt03:48
*** julienvey has quit IRC03:51
*** jjmb has joined #openstack-meeting-alt03:53
*** jjmb1 has joined #openstack-meeting-alt03:56
*** jjmb has quit IRC03:58
*** sarob has joined #openstack-meeting-alt04:02
*** IlyaE has quit IRC04:03
*** rpodolyaka1 has joined #openstack-meeting-alt04:05
*** sarob has quit IRC04:07
*** IlyaE has joined #openstack-meeting-alt04:17
*** sergmelikyan has quit IRC04:21
*** sergmelikyan has joined #openstack-meeting-alt04:23
*** nosnos has joined #openstack-meeting-alt04:25
*** saju_m has joined #openstack-meeting-alt04:27
*** saju_m has quit IRC04:27
*** coolsvap is now known as coolsvap|afk04:35
*** julienvey has joined #openstack-meeting-alt04:47
*** rueb7363 has quit IRC04:48
*** julienvey has quit IRC04:52
*** coolsvap|afk is now known as coolsvap04:52
*** Sukhdev has quit IRC04:57
*** sunrenjie6 has joined #openstack-meeting-alt04:57
*** sarob has joined #openstack-meeting-alt05:03
*** oomichi has joined #openstack-meeting-alt05:06
*** oomichi has left #openstack-meeting-alt05:07
*** IlyaE has quit IRC05:07
*** sarob has quit IRC05:08
*** rpodolyaka1 has quit IRC05:29
*** chandan_kumar has joined #openstack-meeting-alt05:31
*** julienvey has joined #openstack-meeting-alt05:51
*** IlyaE has joined #openstack-meeting-alt05:54
*** HenryG_ has joined #openstack-meeting-alt05:54
*** jcoufal has joined #openstack-meeting-alt05:55
*** julienvey has quit IRC05:55
*** lblanchard has joined #openstack-meeting-alt05:55
*** HenryG has quit IRC05:57
*** sdague has quit IRC05:58
*** sarob has joined #openstack-meeting-alt06:04
*** sdague has joined #openstack-meeting-alt06:05
*** sarob has quit IRC06:08
*** denis_makogon has joined #openstack-meeting-alt06:09
*** lblanchard has quit IRC06:11
*** slagle has quit IRC06:12
*** slagle has joined #openstack-meeting-alt06:13
*** safchain has joined #openstack-meeting-alt06:15
*** alex_didenko has joined #openstack-meeting-alt06:17
*** _nadya_ has joined #openstack-meeting-alt06:22
*** rpodolyaka1 has joined #openstack-meeting-alt06:23
*** rpodolyaka1 has quit IRC06:36
*** jcoufal has quit IRC06:38
*** _nadya_ has quit IRC06:44
*** eankutse has joined #openstack-meeting-alt06:47
*** _nadya_ has joined #openstack-meeting-alt06:49
*** eankutse has quit IRC06:51
*** IlyaE has quit IRC06:55
*** ttrumm has joined #openstack-meeting-alt07:00
*** chandan_kumar has quit IRC07:02
*** jcoufal has joined #openstack-meeting-alt07:02
*** flaper87|afk is now known as flaper8707:04
*** _nadya_ has quit IRC07:04
*** sarob has joined #openstack-meeting-alt07:05
*** slagun has quit IRC07:07
*** chandan_kumar has joined #openstack-meeting-alt07:08
*** sarob has quit IRC07:10
*** beyounn has joined #openstack-meeting-alt07:13
*** matrohon has joined #openstack-meeting-alt07:36
*** ryanpetrello has quit IRC07:40
*** nacim has joined #openstack-meeting-alt07:43
*** ryanpetrello has joined #openstack-meeting-alt07:44
*** akuznets_ has quit IRC07:53
*** jtomasek has joined #openstack-meeting-alt07:59
*** akuznetsov has joined #openstack-meeting-alt08:00
*** sarob has joined #openstack-meeting-alt08:06
*** ryanpetrello has quit IRC08:09
*** sarob has quit IRC08:11
*** ryanpetrello has joined #openstack-meeting-alt08:11
*** derekh has joined #openstack-meeting-alt08:12
*** beyounn has quit IRC08:22
*** jgallard has joined #openstack-meeting-alt08:24
*** denis_makogon has quit IRC08:25
*** jgallard has quit IRC08:28
*** andreaf has joined #openstack-meeting-alt08:28
*** jgallard has joined #openstack-meeting-alt08:28
*** dshulyak has joined #openstack-meeting-alt08:34
*** eghobo has joined #openstack-meeting-alt08:51
*** SushillKM has joined #openstack-meeting-alt08:51
*** SushillKM has left #openstack-meeting-alt08:51
*** chandan_kumar has quit IRC09:06
*** ramishra has quit IRC09:06
*** ramishra has joined #openstack-meeting-alt09:07
*** sarob has joined #openstack-meeting-alt09:07
*** ramishra has quit IRC09:08
*** sarob has quit IRC09:12
*** overlayer has joined #openstack-meeting-alt09:13
*** flwang has joined #openstack-meeting-alt09:13
*** chandan_kumar has joined #openstack-meeting-alt09:19
*** flwang has quit IRC09:19
*** persia has quit IRC09:25
*** chandan_kumar has quit IRC09:26
*** chandan_kumar has joined #openstack-meeting-alt09:26
*** ttrumm has quit IRC09:28
*** persia has joined #openstack-meeting-alt09:28
*** ttrumm has joined #openstack-meeting-alt09:28
*** persia is now known as Guest9004309:29
*** Guest90043 has quit IRC09:29
*** Guest90043 has joined #openstack-meeting-alt09:29
*** Guest90043 is now known as persia09:29
*** jgallard has quit IRC09:58
*** mozawa has quit IRC10:02
*** nosnos has quit IRC10:07
*** sarob has joined #openstack-meeting-alt10:08
*** nosnos has joined #openstack-meeting-alt10:12
*** sarob has quit IRC10:13
*** dmakogon_ is now known as denis_makogon10:14
*** demorris has joined #openstack-meeting-alt10:16
*** eghobo has quit IRC10:21
*** eanxgeek|log is now known as eanxgeek10:31
*** xuhanp has quit IRC10:33
*** mestery_ has joined #openstack-meeting-alt10:33
*** eankutse has joined #openstack-meeting-alt10:34
*** nosnos has quit IRC10:34
*** nosnos has joined #openstack-meeting-alt10:35
*** mestery has quit IRC10:36
*** sunrenjie6 has quit IRC10:37
*** nosnos has quit IRC10:39
*** overlayer has quit IRC10:46
*** demorris has quit IRC10:48
*** yamamoto_ has left #openstack-meeting-alt10:51
*** nosnos has joined #openstack-meeting-alt11:06
*** sarob has joined #openstack-meeting-alt11:09
*** baoli has quit IRC11:12
*** sarob has quit IRC11:15
*** coolsvap is now known as coolsvap|afk11:15
*** Haiying has joined #openstack-meeting-alt11:19
*** yamamoto has joined #openstack-meeting-alt11:21
*** yamamoto has left #openstack-meeting-alt11:21
*** ttrumm has quit IRC11:28
*** zhangleiqiang has joined #openstack-meeting-alt11:44
*** Haiying has quit IRC11:49
*** sreshetnyak has joined #openstack-meeting-alt11:49
*** baoli has joined #openstack-meeting-alt11:54
*** Haiying has joined #openstack-meeting-alt11:58
*** eankutse has quit IRC12:01
*** dprince has joined #openstack-meeting-alt12:06
*** akuznetsov has quit IRC12:09
*** akuznets_ has joined #openstack-meeting-alt12:09
*** sarob has joined #openstack-meeting-alt12:10
*** sarob has quit IRC12:15
*** nosnos has quit IRC12:17
*** _nadya_ has joined #openstack-meeting-alt12:34
*** jdob has joined #openstack-meeting-alt12:38
*** slagle has quit IRC12:39
*** overlayer has joined #openstack-meeting-alt12:39
*** slagle has joined #openstack-meeting-alt12:40
*** akuznets_ has quit IRC12:43
*** akuznetsov has joined #openstack-meeting-alt12:43
*** HenryG_ has quit IRC12:44
*** Haiying has quit IRC12:45
*** pdmars has joined #openstack-meeting-alt12:52
*** _nadya_ has quit IRC12:53
*** jjmb1 has quit IRC12:56
*** Barker has joined #openstack-meeting-alt12:57
*** mfer has joined #openstack-meeting-alt12:58
*** pdmars has quit IRC12:58
*** demorris has joined #openstack-meeting-alt12:59
*** pdmars has joined #openstack-meeting-alt13:03
*** spzala has joined #openstack-meeting-alt13:07
*** HenryG has joined #openstack-meeting-alt13:08
*** Obulpathi has joined #openstack-meeting-alt13:10
*** Obulpathi has quit IRC13:10
*** Obulpathi has joined #openstack-meeting-alt13:11
*** sarob has joined #openstack-meeting-alt13:11
*** sarob has quit IRC13:16
*** zhangleiqiang has quit IRC13:18
*** rmoe has quit IRC13:19
*** eankutse has joined #openstack-meeting-alt13:22
*** mestery_ is now known as mestery13:22
*** rmoe has joined #openstack-meeting-alt13:24
*** ramishra has joined #openstack-meeting-alt13:27
*** zz_gondoi is now known as gondoi13:31
*** gondoi is now known as zz_gondoi13:31
*** amotoki has quit IRC13:32
*** MarkAtwood has quit IRC13:34
*** mattgrif_ has joined #openstack-meeting-alt13:34
*** samstav has joined #openstack-meeting-alt13:34
*** jecarey has joined #openstack-meeting-alt13:35
*** zz_gondoi is now known as gondoi13:35
*** malini_afk is now known as malini13:38
*** eankutse1 has joined #openstack-meeting-alt13:42
*** eankutse has quit IRC13:43
*** balajiiyer has joined #openstack-meeting-alt13:45
*** gondoi is now known as zz_gondoi13:45
*** flwang has joined #openstack-meeting-alt13:48
*** jgallard has joined #openstack-meeting-alt13:49
*** xuhanp has joined #openstack-meeting-alt13:51
*** zz_gondoi is now known as gondoi13:51
*** ameade has joined #openstack-meeting-alt13:52
*** jprovazn has joined #openstack-meeting-alt13:53
*** mattgrif_ has quit IRC13:58
*** julienvey has joined #openstack-meeting-alt13:59
*** spzala has quit IRC14:00
*** spzala has joined #openstack-meeting-alt14:01
*** drupalmonkey has joined #openstack-meeting-alt14:02
*** mozawa has joined #openstack-meeting-alt14:03
*** mozawa has quit IRC14:04
*** spzala has quit IRC14:04
*** sarob has joined #openstack-meeting-alt14:12
*** sarob has quit IRC14:17
*** zns has joined #openstack-meeting-alt14:22
*** kevinconway has joined #openstack-meeting-alt14:26
*** overlayer has quit IRC14:29
*** julienvey has quit IRC14:31
*** MarkAtwood has joined #openstack-meeting-alt14:41
*** mwagner_lap has quit IRC14:47
*** Leonr has joined #openstack-meeting-alt14:49
*** akuznetsov has quit IRC14:49
*** jmontemayor has joined #openstack-meeting-alt14:50
*** coolsvap|afk is now known as coolsvap14:51
*** rmoe has quit IRC14:54
*** carl_baldwin has joined #openstack-meeting-alt14:54
*** carl_baldwin has quit IRC14:55
*** carl_baldwin has joined #openstack-meeting-alt14:55
*** vthapar has joined #openstack-meeting-alt14:57
*** Swami has joined #openstack-meeting-alt14:59
Swamihi all15:00
*** asomya has joined #openstack-meeting-alt15:00
xuhanphello15:00
carl_baldwinSwami: all: hi15:00
Swamixuhanp: hi15:00
Swamicarl: hi15:00
*** mrsmith has joined #openstack-meeting-alt15:00
*** akuznetsov has joined #openstack-meeting-alt15:00
Swamimrsmith: hi15:01
*** Rajeev has joined #openstack-meeting-alt15:01
*** eankutse1 has quit IRC15:01
*** vthapar has left #openstack-meeting-alt15:01
Swamirajeev: hi15:02
*** rossella_s has joined #openstack-meeting-alt15:02
Rajeevswami Hi15:02
Swami#startmeeting distributed_virtual_router15:02
openstackMeeting started Wed Apr 16 15:02:29 2014 UTC and is due to finish in 60 minutes.  The chair is Swami. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: distributed_virtual_router)"15:02
openstackThe meeting name has been set to 'distributed_virtual_router'15:02
mrsmithswami: hi15:02
Swami#topic Agenda15:02
*** openstack changes topic to "Agenda (Meeting topic: distributed_virtual_router)"15:02
Swami1. DVR Progress15:02
*** pcm__ has joined #openstack-meeting-alt15:03
Swami2. Gerrit review update15:03
Swami3. L3 Agent Update15:03
*** IlyaE has joined #openstack-meeting-alt15:03
Swami4. L2 Agent Update15:03
Swami5. L3 Driver update15:03
*** asomya has quit IRC15:03
Swami#topic DVR Progress15:03
*** openstack changes topic to "DVR Progress (Meeting topic: distributed_virtual_router)"15:03
SwamiDVR work is in Progress. East-West is done. We are almost done with the FIP work.15:04
*** eankutse has joined #openstack-meeting-alt15:04
RajeevSwami: time permitting, suggest poll for topics of interest at summit15:05
SwamiFIP work not complete yet.15:05
Swamirajeev: thanks15:05
*** julienvey has joined #openstack-meeting-alt15:05
SwamiSNAT work will be taken once we finish the FIP work.15:05
*** atiwari has joined #openstack-meeting-alt15:06
SwamiLast week we gave an update to the Neutron PTL on the DVR Progress to align with the Juno milestones15:06
SwamiThe target is to push all the code before the summit to the gerrit for review.15:07
SwamiOur target will be Juno milestone 115:07
SwamiWe wanted to have some testable code in there by Juno milestone 1, so that enough testing will be done to test for stability.15:08
SwamiAlso the discussion that I had with the PTL includes redefining the test infrastructure to have multinode setup to accomodate the DVR test.15:08
SwamiHope this helps.15:09
*** balajiiyer has left #openstack-meeting-alt15:09
Swami#topic Gerrit review update15:09
*** openstack changes topic to "Gerrit review update (Meeting topic: distributed_virtual_router)"15:09
SwamiThe Plugin code and the L2 Agent code is now in gerrit for review.15:09
Swami#link https://review.openstack.org/8422315:10
SwamiL2 Agent code15:10
Swami#link https://review.openstack.org/8773015:10
SwamiThanks for the early review comments on the patch posted.15:11
SwamiStill there are couple of more patches that we will be pushing in the next week.15:11
SwamiL3 Scheduler code, L3 Agent code and L3 Drivers.15:11
carl_baldwinSwami: I find this link to be useful to watch all of the commits:15:12
Swami#topic L3 Agent15:12
carl_baldwin#link https://review.openstack.org/#/q/topic:bp/neutron-ovs-dvr,n,z15:12
*** openstack changes topic to "L3 Agent (Meeting topic: distributed_virtual_router)"15:12
Swamicarl: thanks for posting the link15:13
*** shivharis has joined #openstack-meeting-alt15:13
Swamimrsmith: can you give an update on the L3 agent15:13
*** sarob has joined #openstack-meeting-alt15:13
*** jprovazn is now known as jprovazn_afk15:13
mrsmithSwami: yes15:13
mrsmithinitial merge to icehouse-2 is done15:14
mrsmithI am trying to cleanup/resolve the FIP conflicts15:14
mrsmithI may end up pushing a subset of the functionality for review15:14
mrsmithjust for clarity15:14
mrsmithbut I should be able to push something by next wed15:14
mrsmiththe refactoring/changes occuring in the FIP area has resulted in more changes for DVR15:15
*** hemanth has joined #openstack-meeting-alt15:15
Swamimrsmith: Thanks for your update.15:15
mrsmithnp15:16
Swamivivek:ping15:16
Swami#topic L3 Drivers15:16
*** openstack changes topic to "L3 Drivers (Meeting topic: distributed_virtual_router)"15:16
SwamiRajeev where are we with respect to the drivers15:16
Swamiis rajeev in here.15:17
Swamidid we lose him15:17
mrsmithhmm.. he was there15:17
Rajeevswami: all our changes are in the L-3 agent itself15:17
Swamithat's fine.15:17
Swamirajeev: here he is.15:18
mrsmithRajeev: including the change to ip_lib.py?15:18
mrsmithwant me to push that as well?15:18
*** sarob has quit IRC15:18
Rajeevthere are a few pieces in ip_lib that I will push it in15:18
Rajeevduring this week15:19
Swamirajeev: mrsmith: thanks15:19
Swamisounds good.15:19
Swami#topic FIP Gateway issue15:19
*** openstack changes topic to "FIP Gateway issue (Meeting topic: distributed_virtual_router)"15:19
SwamiThere was one question that came up in our discussion regarding the FIP behavior today in openstack neutron.15:20
SwamiSo we need the community opinion on this before we proceed.15:20
*** kgriffs|afk is now known as kgriffs15:21
SwamiToday in a Centralized router mode, when a FIP is assigned to a VM, any incoming traffic from an External Network uses the FIP IP as the destination IP and the traffic flows to the VM.15:21
SwamiWhen the VM responds to the request the traffic also passes through the FIP.15:21
SwamiBut for any normal traffic that initiates from the VM, it uses the default gateway configured in the VM and the traffic flows through the SNAT.15:23
SwamiWhen we implement the North-South in a distributed DVR, the Floating IP will not be on the same node as the SNAT and so how do we want this behavior to be.15:23
carl_baldwinSwami, for a VM with an associated floating ip that should not be true.15:23
*** spzala has joined #openstack-meeting-alt15:23
Rajeevswami: I agree with Carl, same opinion15:24
carl_baldwinOutgoing traffic will always prefer the tip as source ip and not default SNAT address.15:24
carl_baldwins/tip/fip/15:24
Swamicarl: rajeev: Yesterday I heard this from our internal folks. I can re-confirm this.15:24
Rajeevwhen FIP in place, rules don't allow default SNATing15:25
SwamiI am not sure if murali or vivek is in this meeting.15:25
Rajeevswami: np, we can take it offline.15:25
Swamirajeev: carl: thanks for the update.15:25
carl_baldwinI'm pretty confident that the iptables rules in the router are structured to alway s source traffic from a fip when associated.15:26
carl_baldwinLet me know if you need more technical clarification for your follow-up.15:26
SwamiOk, so the agreement here is whatever is the behavior today in Openstack we will follow the same model.15:26
carl_baldwinAgreed.  Any other behavior is a bug.15:27
SwamiIrrespective of centralized or distributed for the FIP>15:27
*** shivharis has quit IRC15:27
carl_baldwinRight.15:27
SwamiIf I have more information on this "bug", then I will bring it up in the next meeting.15:27
*** cjellick has joined #openstack-meeting-alt15:28
haleybyes, i would agree with carl, fip is preferred15:28
Swamihaleyb: Thanks for confirming it brian.15:29
*** Rajeev has quit IRC15:29
Swami#topic DVR HowTo wiki15:30
*** openstack changes topic to "DVR HowTo wiki (Meeting topic: distributed_virtual_router)"15:30
SwamiFor the Neutron Documentation team to get started we are planning to include a "DVR HowTo", so that it would be helpful for the folks who are testing and as well as for the documentation folks.15:31
SwamiSo we will be updating the DVR HowTo wiki on more information.15:31
*** viveknarasimhan has joined #openstack-meeting-alt15:31
Swami#link https://wiki.openstack.org/wiki/Neutron/DVR/HowTo15:32
*** amotoki has joined #openstack-meeting-alt15:32
*** yamamoto has joined #openstack-meeting-alt15:32
SwamiThis is just a template and we will add more content as we progress.15:32
xuhanpSwami, that will be really helpful for us to test it too!15:32
Swamixuhanp: Yes this is to enable testers.15:32
Swamiviveknarashimhan: hi15:33
Swami#topic L2 Agent Update15:33
*** openstack changes topic to "L2 Agent Update (Meeting topic: distributed_virtual_router)"15:33
Swamivivek: are you there.15:34
viveknarasimhanhi15:34
viveknarasimhani am there15:34
Swamiviveknarasimhan: can you provide an update for the L2 agent15:35
viveknarasimhani posted the L2 Agent/ML2 plugin WIP code for review15:35
*** jgallard has quit IRC15:36
*** Murali has joined #openstack-meeting-alt15:36
viveknarasimhani have been getting review comments from lot of folks15:36
viveknarasimhani will be starting to address them one-by-one from today15:36
viveknarasimhanThe port-binding changes are done and i am running various type of use-cases on it15:36
viveknarasimhanlike DVR hosted + Non DVR hosted VM type of cases to make sure old behaviour didn't brek15:37
*** Rajeev has joined #openstack-meeting-alt15:37
viveknarasimhani have a question though15:37
*** pcm_ has joined #openstack-meeting-alt15:37
viveknarasimhani we link the patches say L3 Extension patch is linked with my L2 patch put for review15:37
viveknarasimhanif i do git pull --rebase, then will I be required to address conflicts i nthe L3 Extension patch also?15:38
viveknarasimhanso the question is: when patches are linked, how is git pull --rebase handled , before we repost for review15:38
*** eankutse1 has joined #openstack-meeting-alt15:39
*** Sukhdev has joined #openstack-meeting-alt15:39
*** ramishra has quit IRC15:39
Swamiviveknarasimhan: no I am not an expert in this area.15:39
*** rmoe has joined #openstack-meeting-alt15:39
SwamiI can check offline and let you know.15:39
amotokiviveknarasimhan: which patch?15:39
*** eankutse has quit IRC15:40
Swamiamotoki: Viveknarasimhan has a dependency of the L3 extension patch that we posted for review.15:40
amotokiSwami: I just check the exact one. I am looking for it in the review list...15:41
*** andreaf has quit IRC15:41
SwamiSo he is asking how to post patches that have dependencies for review and if the dependent source tree has any conflicts, how to resolve it.15:41
viveknarasimhanthis patch: https://review.openstack.org/8773015:41
*** andreaf has joined #openstack-meeting-alt15:41
viveknarasimhanthe above patch is the L2 side changes and this dependes on L3 side changes also posted by Swami earlier15:41
amotokiI got it. I think if there is no direct dependency you can post without dependency (if there is a note in the commit message).15:42
Swamiamotoki: There are the two patches15:42
Swami#link https://review.openstack.org/#/q/topic:bp/neutron-ovs-dvr,n,z15:42
*** asomya has joined #openstack-meeting-alt15:43
amotokiyes i know. perhaps you are talking about how to manage the dependency.15:43
Swamiamotoki: Thanks for your help.15:43
Swamiviveknarasimhan: We can take it offline and resolve this issue.15:43
amotokiif you have a question, i can help anytime.15:43
*** trinaths has joined #openstack-meeting-alt15:43
viveknarasimhani will mail you amotoki15:44
Swamiamotoki: Thanks for your help again.15:44
viveknarasimhani will also CC mestery on the same question.  Thanks for your help amotoki.15:44
Swami#topic FIP/SNAT question.15:44
*** openstack changes topic to "FIP/SNAT question. (Meeting topic: distributed_virtual_router)"15:44
SwamiThere was another question that we had with the FIP/SNAT.15:44
SwamiToday in the distributed model, we will be having SNAT and FIP running on two different nodes.15:45
*** chandan_kumar has quit IRC15:46
SwamiWhen an admin removes the "SNAT" binding from an agent, then should FIP still continue to work?? this is the question15:46
SwamiAny suggestions?15:48
RajeevSwami: FIP and SNAT are independent15:48
Rajeevso should continue to work15:49
mesteryI can help with the patch dependency issue as well.15:49
Swamirajeev: Yes thanks for your input.15:49
RajeevAn external gateway has to be set for the router15:49
xuhanpSwami, what do you mean by "remove the binding"?15:49
mrsmithbut don't we require the external-gateway-set?15:49
* pcm__ On dependency: https://wiki.openstack.org/wiki/Gerrit_Workflow#Add_dependency15:49
mrsmithfor FIP?15:49
RajeevThereafter both SNAT and FIP can be there15:49
*** vthapar has joined #openstack-meeting-alt15:49
SwamiEven though FIP and SNAT are different mrsmith mentioned there is some dependency and so we wanted to get broader consensus on this before we proceed.15:50
RajeevFrom an agent perspective, it can handle SNAT in addition to FIP depending on what it's .ini says15:50
*** mwagner_lap has joined #openstack-meeting-alt15:51
Muraliin this case in FIP namespace what is gatway IP?15:51
mrsmithseems awkward to me to require ext-gw-set, but then allow it to be cleared15:51
Swamixuhanp: We are proposing an admin level command to remove and add SNAT from an agent.15:51
mrsmithfor FIPs15:51
Swamixuhanp: That is what I mentioned as binding to the agent.15:51
xuhanpSwami, you mean choose another agent to take the SNAT role node?15:51
Swamixuhanp: Yes, before you move, you first remove the binding from the current SNAT agent.15:52
xuhanpSwami, thanks for the clarification15:52
Swamimestery: Thanks for your help.15:53
*** zhangleiqiang has joined #openstack-meeting-alt15:53
*** _nadya_ has joined #openstack-meeting-alt15:53
SwamiSo what i am hearing is in the distributed model, SNAT behavior should not affect the FIP.15:53
*** AndroUser2 has joined #openstack-meeting-alt15:53
Swamior vise versa.15:54
*** vkmc has joined #openstack-meeting-alt15:54
Swamimrsmith: Do you have any suggestions on this or do you want to discuss this more next week.15:54
*** vkmc has quit IRC15:54
*** vkmc has joined #openstack-meeting-alt15:54
*** cjellick has quit IRC15:55
carl_baldwinI'll admit I don't completely understand what the dependency between FIP and default SNAT might be.15:55
mrsmithit is possible to do, and I guess a "good" feature to be able to move SNAT while FIPs are running15:55
SwamiOk, let us talk about this topic more indepth in the next meeting.15:55
mrsmithsure15:55
*** cjellick has joined #openstack-meeting-alt15:56
mrsmiththe only dependency is in the current code15:56
mrsmithmore to refactor15:56
carl_baldwinSo, an implementation level dependency.15:56
mrsmithyes15:56
SwamiWe only have a couple of more minutes.15:56
*** rcurran has joined #openstack-meeting-alt15:56
Swami#topic General discussion15:56
*** openstack changes topic to "General discussion (Meeting topic: distributed_virtual_router)"15:56
carl_baldwinI see.  I think we can work that out.  I've done some work with this as well.15:56
SwamiDoes anyone have any other topic to discuss.15:56
mrsmithcarl: sounds good15:56
SwamiI knew that rajeev brought up some summit design discussion topic.15:57
RajeevFor the summit, we want to poll audience on future for DVR15:57
*** nlaouti has joined #openstack-meeting-alt15:57
SwamiRajeev, we do have signed up for a "DVR update".15:57
*** rkukura has joined #openstack-meeting-alt15:58
SwamiIn order to achieve partiy with Nova, we also need to complete the Distributed DHCP.15:58
RajeevGreat15:58
*** _nadya_ has quit IRC15:58
*** AndroUser2 has quit IRC15:58
*** pcm_ has quit IRC15:58
SwamiThis is one of the major topic that came up last week when I discussed DVR with Mark McClain.15:58
viveknarasimhanI just started off15:58
viveknarasimhanwith the Distributed DHCP document15:58
SwamiSo the immediate need is "refactor' the L3 Agent/L2 Agent code and also to support Distributed DHCP.15:59
viveknarasimhani will whet that with you Swami and then we can proceed from that point15:59
SwamiOk we are almost at the end of the hour15:59
SwamiThanks all for joining this meeting.15:59
*** banix has joined #openstack-meeting-alt15:59
SwamiKeep up the momentum.16:00
*** viveknarasimhan has quit IRC16:00
Swamibye16:00
Swami#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Apr 16 16:00:13 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-04-16-15.02.html16:00
mrsmithbye16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-04-16-15.02.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-04-16-15.02.log.html16:00
*** mrsmith has quit IRC16:00
rkukuraml2’ers here?16:00
banixhi there16:00
nlaoutihi16:00
rkukurahi banix!16:00
amotokihi16:00
yamamotohi16:00
trinathshi rkukura16:00
mesteryo/16:01
trinathshi mestery16:01
mesterytrinaths: Howdy!16:01
trinathsmestery: :)16:01
rkukuraSukhdev: you around?16:01
SukhdevHello16:01
*** marun has joined #openstack-meeting-alt16:01
rkukuralets get started!16:02
*** persia has quit IRC16:02
rkukura#startmeeting networking_ml216:02
openstackMeeting started Wed Apr 16 16:02:15 2014 UTC and is due to finish in 60 minutes.  The chair is rkukura. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:02
openstackThe meeting name has been set to 'networking_ml2'16:02
*** persia has joined #openstack-meeting-alt16:02
*** colinmcnamara has joined #openstack-meeting-alt16:02
*** persia has quit IRC16:02
*** persia has joined #openstack-meeting-alt16:02
rkukura#topic Announcements16:02
*** openstack changes topic to "Announcements (Meeting topic: networking_ml2)"16:02
*** emaganap has joined #openstack-meeting-alt16:02
*** eghobo has joined #openstack-meeting-alt16:03
rkukuracongrats to mestery on being elected PTL!16:03
mesteryThanks rkukura!16:03
banixcongrats! :)16:03
amotokicongrats mestery.16:03
*** Swami has left #openstack-meeting-alt16:03
emaganaprkukura: +116:03
Sukhdevmestery: Huge contratulations!!!16:03
rkukurasince that is more than a full time job, Sukhdev has volunteered to take over as a co-chair of our sub-team16:04
rkukurathanks Sukhdev!16:04
mesteryThanks Sukhdev for volunteering!16:04
SukhdevMy pleasure!!16:04
*** padkrish has joined #openstack-meeting-alt16:04
banixcool! :)16:04
rkukuraSo the co-chair role is mainly to facilitate these weekly meetings and report sub-team status at the neutron IRC meeting16:04
*** Murali has quit IRC16:05
*** jmontemayor has quit IRC16:05
*** richm has joined #openstack-meeting-alt16:05
trinathsmestery: congratulations16:05
*** Barker has quit IRC16:06
rkukuraHopefully at least one of us will be available each Wednesday, but others could certainly step in if needed16:06
*** ramishra has joined #openstack-meeting-alt16:06
*** Barker has joined #openstack-meeting-alt16:06
rkukuraIts everyone’s job to review code, blueprints, and docs related to ML216:07
rkukuraany other announcements?16:07
rkukuraI don’t see any action items recorded from last week16:07
nlaoutithe was some VDP discussion last week can we discuss it now16:08
rkukura#topic TypeDriver Refactoring16:08
*** openstack changes topic to "TypeDriver Refactoring (Meeting topic: networking_ml2)"16:08
*** sadasu has joined #openstack-meeting-alt16:08
*** Sourabh has joined #openstack-meeting-alt16:08
trinathscan we start submitting the BPs into the review system (the new process)16:08
rkukuraI don’t see asomya here, so we may have to push this off again16:08
rkukuratrinaths: Definitely!16:08
Sukhdevrkukura: I thought mestery was going to arrange Asomya to come and present16:09
rkukurashould have mentioned that in annountments16:09
asomyarkukura: I''m here16:09
nlaoutiwe just open new BP https://blueprints.launchpad.net/neutron/+spec/vdp-network-overlay16:09
rkukuraasomya: great!16:09
nlaoutito address the > 4k seg and changes in ovs_neutron agent16:09
asomyaI've managed to refit ML2 and almost all type drivers, had to take a two week break due to some personal stuff but i'm confident i'll be able to push at least a WIP this week or next by the latest16:09
rkukuranlaouti: lets cover that under the design summit sessions section of the agenda16:10
nlaoutiIt has it16:10
rkukuraasomya: Are you planning to submit a summit session on this?16:10
nlaoutipaddu can give the link16:10
padkrish#rkukura# Here the link for that http://summit.openstack.org/cfp/details/31416:10
asomyaWeren't you rolling all these into one ML2 session?16:10
asomyaI can do a quick demo16:11
asomyadon't think i have anough material for a dedicated session :)16:11
rkukuraOK, lets include that in a catch-all session that I’ll file16:11
*** colinmcnamara has quit IRC16:11
*** jgallard has joined #openstack-meeting-alt16:11
rkukuraDoes this work effect the way providernet and/or multiprovidernet extensions are used with ML2?16:12
Sukhdevasomya: it is on the same lines that you presented in HongKong?16:12
*** pcm_ has joined #openstack-meeting-alt16:12
asomyasukhdev: Yes it's the same BP16:12
*** demorris has quit IRC16:13
rkukuraOK, I’ll inlcude the link the the existing BP in the catch-all session proposal16:13
*** bdpayne has joined #openstack-meeting-alt16:13
padkrish#asomya#: Last week there was a talk about dynamic VLAN allocations. Is there a BP for that?16:13
rkukuraMy understanding is that all BPs will need to go through a review/acceptence process in the new neutron-specs repo.16:13
Sukhdevasomya: you had a specific use case padkrish has a specific use case rkukura had proposed last week that we come up with a generic mechanism in ML2 to deal with this16:14
*** betsy has joined #openstack-meeting-alt16:14
*** sarob has joined #openstack-meeting-alt16:14
asomyaSukhdev: Padkrish: Yes that's my goal after the architecture changes to author a custom vlan type driver. We can sync up and see if we can make it generic enough to be reusable16:14
rkukurapadkrish: I’m going to propose a session and BP on a base mechanism for dynamic VLAN assignment, and I think the stuff you and nlaouti are talking about would build on that16:14
nlaoutidoes it mean the costum vlan type driver can support more that 4k segment?16:15
rkukuraAny other questions for asomya right now re. type driver refactoring?16:15
Sukhdevrkukura, padkrish, asomya: we should coordinate this work16:15
asomyanlaouti: Yeah, that's the goal16:15
nlaoutiasomya: that's good16:16
padkrish#sukhdev# Sure, how can we do that? Thru the dev mailing list?16:16
asomyaRkukura: Is the custom driver part of the ML2 catchall session? or we can have an unconference session16:16
amotokiI have another use case. point-to-point link between VM vnics (without mac learning), though it seems orthogonal to the exsting type drivers.16:16
SourabhI have a question - N1k plugin has an extension called network profile - it allows specifying custom segment ranges and segment types for a network - can we do this with your refactoring?16:16
Sukhdevpadkrish: can we kick off discussion on ML and then if the need be, we can arrange a meeting16:16
rkukuraLets cover the dynamic VLAN stuff in the design summit session agenda topic in a bit16:17
mesteryasomya: I think they killed the unconference slots this year.16:17
rkukura#topic ovs-firewall-driver update16:17
*** openstack changes topic to "ovs-firewall-driver update (Meeting topic: networking_ml2)"16:17
*** zhiyan is now known as zhiyan_16:17
asadoughihi16:17
rkukuraasadoughi: any update for us?16:17
*** jmontemayor has joined #openstack-meeting-alt16:18
rkukuraWe didn’t cover that last week, did we?16:18
asadoughiso still working on restoring existing patches, vthapar is out on vacation this week16:18
*** akuznets_ has joined #openstack-meeting-alt16:18
asadoughistill attempting to have a working impl by summit but my short term schedule hasn't been as open as i expected16:18
rkukuraasadoughi: Are you submitting a session proposal for this?16:19
*** BrianB_ has joined #openstack-meeting-alt16:19
asadoughithat's all. i have feedback on one of the patches i restored that i need to get to already.16:19
asadoughirkukura: yes, already submitted16:19
vthaparone small update from me, I've shared some of my prototype reflexive learning code with my test team and once they have resources available will be testing out OVS2.1's 200k flow space.16:19
*** sarob has quit IRC16:19
asadoughivthapar: coo16:19
asadoughil16:19
mesteryvthapar: Cool, that sounds pretty awesome!16:19
vthaparI had one question regarding use of openvswitch...16:20
*** IlyaE has quit IRC16:20
vthaparis the planned future direction to reduce no. of bridges in use?16:20
mesteryvthapar: You mean collapse from br-int/br-tun/br-ex to a single bridge?16:20
rkukuraLike every other BP for juno, we’ll need to get an updated BP for ovs-firewall-driver through the spec review process16:20
asadoughivthapar: i haven't heard number of bridges being a constraint16:21
mesteryvthapar: I would be in favor of patches which moved the OVS agent in that direction.16:21
*** akuznetsov has quit IRC16:21
mesteryvthapar: OpenDaylight uses a single bridge, for example.16:21
asadoughirkukura: filed and approved during icehouse so i'd prefer to not resubmit16:21
vthaparI was coming from a different direction, as in using multiple bridges based on functionality16:21
vthaparI had discussed with asadoughi, using separate ovs bridge for security groups, say br-sec.16:21
banixmestery: SDN-VE also uses a single bridge16:21
mesteryvthapar: Ah, interesting choice. So, isolate the features per-bridge?16:21
rkukuramestery can clarify, but my understanding is all BPs for juno need to go through the new process16:21
vthaparyes, I am working on a blueprint for the same, just need to do some prototyping and make sure it holds up.16:22
mesteryYes, the way the new BP process works is that features which missed the previous release need to be re-approved for Juno now.16:22
mesteryvthapar: Very cool!16:22
asadoughimestery: ok16:22
mesteryasadoughi: If you have other questions around that, please let me know. This is a new process, so I'm happy to help.16:22
vthaparthink of it like a service chaining model, but for core neutron services.16:22
asadoughiso should i stop coding and refile bp? can't do all things at once16:23
vthaparasadoughi, I can help with bp.16:23
mesteryasadoughi: Hopefully you can simply migrate your existing BP over to the new neutron-specs repository with minimal effort.16:23
*** xuhanp has quit IRC16:23
rkukuramestery: I’m still not totally clear if we want the BPs in neutron-specs prior to the summit, if WIPs make sense for this, or if google docs are OK until the ideas get sociallized and teams formed at the summit16:23
mesteryasadoughi: Please keep coding, I expect your BP to not be too contentious since it was already approved for Icehouse.16:23
mesteryrkukura: I think we should be pushing specs to neutron-specs, and before the summit is perfectly fine.16:24
amotokimestery: who have responsibilities to review blueprints? nova team assigns two folks from nova-drivers to review BPs.16:24
mesteryrkukura: I don't think each BP needs a summit session.16:24
asadoughiok, i'll at least push a WIP by next week to neutron specs gerrit16:24
mesteryamotoki: Anyone can review them, neutron-cores can +2/+A the BPs.16:24
amotokiokay.16:24
mesteryamotoki: For larger BPs, it may be good to assign neutron cores as reviewers of the resulting code as well. What do you think?16:24
amotokimestery: agree. it is a good idea.16:25
rkukuragetting some of these existing BPs through the process quickly would be a good way to get the ball rolling with the new process16:25
mesteryrkukura: +1 to that idea.16:25
mesteryI think asadoughi's BP is a good example of something we can approve quickly once it hits neutron-specs. :)16:25
rkukuraanythign else on ovs-firewall-driver before we move on to the design summit session ideas?16:26
asadoughinada from me.16:26
vthaparI had question on using br-sec for SGs...16:26
vthapardoes it sound like a good idea or direction we want to be heading in? feature based bridges?16:27
banixvthapar: what is the advantage of having such an architecture?16:27
*** manishg has joined #openstack-meeting-alt16:28
vthaparit provides isolation of flwos thsu making it easy to troubleshoot.16:28
amotokiI think The advantage is that it makes easier to manage flow rules.16:28
rkukuravthapar: And does traversing patch ports between bridges add overhead to the kernel datapath?16:28
vthaparrkukura: that is the open question right, which I need to prototype and get test results of.16:28
vthaparright now.16:28
vthaparthe sort of work I am doing, I am using a service VM which host these bridges, not on host OS.16:29
vthaparso, it allows me possibility of providing a scaleout model.16:29
vthapare.g. if you have a few tenants but lots of SG rules, your SG flows maybe too high and will benefit from being separate instance.16:30
vthaparanother reason was that OVS2.0 only supports 2k flows in kernel space, I was avoiding that problem by having SG flows in separate bridge running in its own service VM, thus its own kernel.16:30
banixso there will be for example a sec related bridge on each data path? meaning multiple such bridges if there are multiple network interfaces on a host?16:30
*** IlyaE has joined #openstack-meeting-alt16:30
yamamotopatch ports do not add overhead to the datapath afaik16:30
mesteryvthapar: I think the idea is worth exploring. Once you vet it a bit more, let us know how it looks.16:31
vthaparnot really, br-sec would need to sit where br-int sits today.16:31
*** ramishra has quit IRC16:31
vthaparmestery: I Am working on BP, not published yet coz want to do some testing and get some concrete numbers.16:31
mesteryvthapar: Cool! It may be worth filing a summit session for this, or collapsing it into asadoughi's ovs-firewall session16:32
vthaparthe use case I have at my workspace kid of necessiates such an approach but I believe it will benefit all.16:32
rkukuramestery: I was thinking the same thing16:32
amotokivthapar: br-sec sounds good to me for ovs-firewall-driver as we can separate a logic from the exsiting ovs-agent.16:32
vthaparhow should I go about it? file a bp first?16:32
mesteryamotoki: +116:32
asadoughihow long's a summit session anyway? ovs-firewall-driver might not even take up the full time as-is.16:33
mesteryvthapar: Yes, a BP is a good start, and then discussing as part of asadoughi's session in Atlanta woudl also be good!16:33
mestery40 minutes asadoughi16:33
rkukura#topic Design summit session proposals16:33
*** openstack changes topic to "Design summit session proposals (Meeting topic: networking_ml2)"16:33
mesterySo, combining them would be good16:33
*** demorris has joined #openstack-meeting-alt16:33
vthaparok. will work on getting BP up before that so all get some context.16:33
rkukuradeadline for submitting proposals is Sunday, 4/2016:33
mesteryvthapar: Great!16:33
mesteryYes, please file early!16:33
amotokiasadoughi: if it does need full time, you can add a comment in session proposal.16:33
mesteryWe're already over our allotted 20 spots.16:34
mesterySo we may converge a few sessions.16:34
amotoki *if does *not* need16:34
*** zhiyan_ is now known as zhiyan16:34
asadoughiah, 40 minutes, i was thinking 1 hour.16:34
vthapar20 deadline might be bit difficult for me.16:34
rkukurasession proposals don’t need to be very detailed16:35
vthaparam on vacation [sort of] with intermittent access.16:35
vthaparaha, will do that.16:35
banixvthapar: thats deadline for session proposals16:35
rkukuraWe’ve been collecting ideas for session proposals to be filed at https://etherpad.openstack.org/p/juno_ml2_session_ideas16:35
vthapargot it.16:35
*** baoli has quit IRC16:35
*** baoli has joined #openstack-meeting-alt16:36
rkukurawould be great if people that have filed proposals for ML2 could add link to proposal under “already filed ideas”, and move up any useful text from below16:36
Sukhdevmestery, rkukura: Is there a limit on number of sessions for ML2 specific work?16:37
rkukuraSukhdev and I will get the proposal on re-synchronization filed this week16:37
nlaouti I have a question, is there  BP or work done on supporting mechanism driver RPC on the ovs neutron agent side16:37
rkukuraLets discuss the dynamic VLAN stuff for a moment16:38
mesterySukhdev: No limit, other than practicial. If we can collapse ML2 sessions into 2 sessions, that might be ideal.16:38
amotokiIs RPC stuff related to VLAN stuff? i am not sure.16:38
emaganapmestery: +1 that is a good idea16:38
rkukuraI think that having the mechanism driver handle the get_device_details RPC will be needed for dynamic VLAN, at least on certain use cases16:39
amotokii see.16:39
Sukhdevmestery: may be tight, but, we'll try :-)16:39
*** redrobot has left #openstack-meeting-alt16:39
amotokiI have an idea to refactor RPC callbacks in all neutron plugins. The current mixin apporach prevents each RPC API from evolving separately.16:39
nlaoutiNot really.16:39
amotokiit is not directly related to ML2 but i can cover it.16:39
nlaoutiamotoki: in some cases MD may need to send info to ovs agent16:39
amotokinlaouti: yes. i understand the need.16:40
*** trinaths has quit IRC16:40
amotokisome driever need to receive RPC too.16:40
rkukuraI’m thinking that the bound MD should be responsible for handling get_device_details, and maybe it should defer to the segment’s type driver in most cases16:40
nlaoutiamotoki: thats correct16:40
nlaoutiamotoki: l2_pop implemeted one which is being used by l2_pop16:41
*** drupalmonkey has left #openstack-meeting-alt16:41
asadoughibanix: +1 for modular agent discussion. ovs_neutron_agent is bloating as-is.16:41
rkukuraAdding new RPCs in drivers is kind of related to having extensions supported by drivers, isn’t it?16:41
*** zhiyan is now known as zhiyan_16:41
amotokiit is sometimes related to having new extensions, but it is not always.16:41
nlaoutirkukura: that could be one of the cases16:42
rkukuraSo I plan to file a session proposal on just very basic changes to ML2 to allow the bound MD to dynamically assign VLAN tags16:42
nlaoutirkukura: as part of my work on Mechanism driver, I needed to have RPC on ovs_agent for the MD.16:42
rkukuraI think separate session proposals for VDP and such make sense, and mestery can combine these into one session16:43
*** jcoufal has quit IRC16:43
rkukuranlaouti: Are you saying you need the MD to make and RPC call to the agent?16:43
nlaoutirkukura: For now I create RPC  bases on some config option on ml2_conf.ini on ovs agent and on server side16:43
nlaoutirkukura: yes16:44
banixamotoki: is there a blueprint for your work on unifying  RPC callbacks16:44
amotokiI will register it tomorrow.16:44
amotokiI don't think it need a session proposal.16:45
rkukuranlaouti, amotoki: Seems the extensibility of the REST and RPC interfaces could be covered together in one session, or maybe as part of the catch all session16:45
amotokirkukura: sounds good.16:46
*** cp16net has joined #openstack-meeting-alt16:46
nlaoutirkukura: sounds good16:46
rkukuraAre there items on the etherpad (or not yet on it) that need volunteers to submit proposals?16:46
*** gokrokve has joined #openstack-meeting-alt16:47
rkukuraDoes anyone want to look into the bulk operations?16:47
rkukuraAny other session topics to discuss?16:49
*** zhangleiqiang has quit IRC16:49
amotokire bulk operation, it is very different between agent case and sdn controller case, so I could not cover both cases so far.16:49
*** noslzzp has joined #openstack-meeting-alt16:49
*** cp16net has quit IRC16:50
rkukuraamotoki: Basic question I have on bulk operations is whether the ML2 plugin should handle them as separate operations, each with precommit followed by postcommit16:51
rkukuraof if all precommits should happen in one transaction16:51
*** harlowja_away is now known as harlowja16:51
rkukuraof it the drivers should have a bulk_precommit and bulk_postcommit method16:51
rkukuras/of it/or if/16:51
Sukhdevrkukura: Do you have a use case in mind?16:52
rkukuraSukhdev: Not really, just want to make sure we aren’t calling controllers/devices from inside transactions16:52
amotokimy initial thought is to commit all requests in one (bulk_)precommits and then bulk_postcommit. it seems easier to rollback.16:53
Sukhdevrkukura: I can think of this being useful in the re-sync process16:53
amotokiperhaps same as your thought.16:53
*** pcm_ has quit IRC16:53
rkukuraSukhdev: interesting16:53
rkukuraDo we need anything related completing the deprecation of the monolithic plugins?16:54
asadoughimonolothic plugins maybe not, but monolithic agents.. i'm curious in general how we would go about refactoring (e.g. RPC, agent) when there are active feature implementations ongoing; obviously with nova-network parity being a priority, that will make it more difficult.16:55
rkukuraWe’ve got a migration tool now, and I guess we’ll be removing code in juno, and maybe moving the L2 agents (or refactoring them as drivers in a modular agent)16:55
*** vinod has joined #openstack-meeting-alt16:55
*** msisk has joined #openstack-meeting-alt16:55
mesteryasadoughi: That's a good point. nova-network parity is priority #1 for Juno, so we can't slow that down at all. :)16:56
rkukura#topic Open Discussion16:57
*** openstack changes topic to "Open Discussion (Meeting topic: networking_ml2)"16:57
rkukuraWe’ve got a couple minutes left - anything else?16:57
asadoughimestery: yeah, and nova-parity patches are making agent more monolothic!16:57
*** amcrn has joined #openstack-meeting-alt16:57
*** rpodolyaka1 has joined #openstack-meeting-alt16:57
asadoughibanix: thoughts?16:58
banixasadoughi: do you have any particular patch in mind or in general?16:58
amotokiDo we use ML2 with OVS or ML2 with linuxbridge for nova-parity? It may be one topic in the summit. OVS with hybrid have a performance issue.16:58
*** rjrjr has joined #openstack-meeting-alt16:58
*** wendar has quit IRC16:59
asadoughibanix: is https://review.openstack.org/#/c/87730/ nova-parity or related, i think saw something about distributed dhcp in the dvr meeting prior adding on to this16:59
mesteryamotoki: Maybe I should file a summit session on deprecation plans for LB and OVS, and we can cover that there.16:59
mesteryNot sure if needs a full session or not.16:59
mesteryMaybe in a broader "juno plans" session16:59
rkukuraamotoki: Hopefully the ovs-firewall-driver will eliminate the hybrid bridge16:59
*** jmcbride has joined #openstack-meeting-alt16:59
asadoughiamotoki: everyone could switch ovs non-hybrid if ovs-firewall-driver is implemented? :)16:59
*** mugsie has joined #openstack-meeting-alt17:00
*** tsimmons has joined #openstack-meeting-alt17:00
vthaparis firewall driver only reason for using linux-bridge today?17:00
rkukurawe are out of time17:00
rkukuraOK, lets get the summit session proposals in, and start working on writing and reviewing BPs!17:00
amotokimestery: sounds good. we need to clarify all nova-parity plans.17:00
banixasadoughi: thanks will look into this patch in partiular and this issue in general17:00
rkukura#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
mesterythanks rkukura!17:00
openstackMeeting ended Wed Apr 16 17:00:38 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-04-16-16.02.html17:00
amotokithanks.17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-04-16-16.02.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-04-16-16.02.log.html17:00
rkukurathanks everyone!17:00
Sukhdevbye17:00
mesteryamotoki: Yes, I have a plan started, I'll share it with the team soon. I need to present it to the TC next Teusday17:01
asadoughivthapar: yeah, lb for security groups on iptables17:01
kiall#startmeeting Designate17:01
openstackMeeting started Wed Apr 16 17:01:14 2014 UTC and is due to finish in 60 minutes.  The chair is kiall. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: Designate)"17:01
openstackThe meeting name has been set to 'designate'17:01
*** rcurran has quit IRC17:01
*** asomya has quit IRC17:01
kiallHeya - who's about? :)17:01
mugsieo/17:01
*** wendar has joined #openstack-meeting-alt17:01
vinodhere17:01
jmcbridehowdy17:01
tsimmonso/17:01
*** rkukura has left #openstack-meeting-alt17:01
*** nlaouti has left #openstack-meeting-alt17:01
rjrjrhere17:01
*** vthapar has quit IRC17:02
*** julienvey has quit IRC17:02
kiall#topic Review action items from last week17:02
*** openstack changes topic to "Review action items from last week (Meeting topic: Designate)"17:02
*** derekh has quit IRC17:02
richmhere17:02
kiall2 items - 1 I was told was one after I added it, and other was to organize the hangout. So.. Both done.17:02
betsyo/17:02
*** pcm__ has left #openstack-meeting-alt17:02
kiall#topic DNSpy update17:03
*** openstack changes topic to "DNSpy update (Meeting topic: Designate)"17:03
kiallI missed who added this item? :)17:03
*** sadasu has quit IRC17:03
*** nacim has quit IRC17:03
vinodJoe added this17:03
jmcbrideI added this17:03
jmcbrideUnfortunately emmanuel is not here at the moment, as he has the best detail.17:03
*** padkrish has left #openstack-meeting-alt17:03
vinodBut from what he mentioned, notify works well with DNS Pythin17:04
jmcbrideI know he is working through it and having some success… hasn't hit any major issues.17:04
kialljmcbride: ah, will he be here before the end of the meet? If so, Let's come back to it/17:04
vinodNo not today17:04
jmcbrideno, but my thought was mostly around what we want to do with dnspy and the diy17:04
vinodAXFR works as a client he needs to checkout as a server17:04
kiallvinod: Okay..17:05
jmcbrideI think he will be done soon and I thought I'd bring it up so we have what we need on diy to make a decision17:05
betsykiall: How’s the DIY coming?17:05
kiallbetsy: exactly as it was a few months ago - I'm confident it's relatively easy to implement, I think it's a *slightly* better option, but am open to both DIY and DNSpy17:06
jmcbrideI would imagine the two could probably be swapped out without to much impact.17:06
kiallYou might have noticed the # of reviews from me has jumped over the last week, finally managing to organize time etc :)17:07
betsyI know. I’m impressed17:07
vinodespecially with the late nighters like yesterday :-)17:07
kialljmcbride: yea, swapping one for the other should actually be easy enough17:08
jmcbrideOK, I think we can probably move on.  The main takeaway I think is the DNSpy might be an option to go with initially for mDNS then swap out later in the event we are not ready to address DIY yet.17:08
kiallAnyway - I'm personally open to both routes, I do think DIY is going to give us more control - but that's very much "It'll be useful at some point in the future" thing17:08
kialljmcbride: yea, essentially the same as my thinking :)17:09
jmcbridesweet17:09
*** jgallard has quit IRC17:09
*** safchain has quit IRC17:10
kiallOnce the next BP (also the next topic) is implemented, we should be pretty close to being able to actually implement these choices17:10
*** amcrn has quit IRC17:10
kiallSo - Anything else on this topic before we move on?17:10
vinodNo17:10
kiall#topic Clarify details mdns-structured-rdata17:10
*** openstack changes topic to "Clarify details mdns-structured-rdata (Meeting topic: Designate)"17:10
vinod#link https://wiki.openstack.org/wiki/Designate/Blueprints/MiniDNS#Update_the_Record_object_to_make_available_the_structured.2C_as_well_as_textual_representations_of_the_records.27s_RData17:10
*** akuznets_ has quit IRC17:11
vinodI wanted to clarify my understanding before I get started on this.17:11
vinodCurrently designate/objects has an object for record. This object (designate.objects.Record) would provide from_text, to_text methods. designate.objects.base would provide a from_dict, to_dict methods. The various types of records supported ("A", "AAAA", "CNAME", "MX", "SRV", "TXT", "SPF", "NS", "PTR", "SSHFP") would each have a separate type that inherit from designate.objects.Record. Storage's get_record, find_record and find_records would be ab17:11
*** eghobo has quit IRC17:11
*** MarkAtwood has quit IRC17:11
*** eghobo has joined #openstack-meeting-alt17:11
*** nicole has joined #openstack-meeting-alt17:12
*** denis_makogon_ has joined #openstack-meeting-alt17:12
*** denis_makogon has quit IRC17:13
*** denis_makogon_ is now known as denis_makogon17:13
*** dmakogon_ has joined #openstack-meeting-alt17:13
*** beyounn has joined #openstack-meeting-alt17:13
kiallvinod: Sorry, misundersood the first time a wrote a totally wrong comment.. Typing again ;)17:13
*** demorris has quit IRC17:14
*** MarkAtwood has joined #openstack-meeting-alt17:15
kiallSo - Yes, for e.g. "MXRecord" would inherit from Record, it would provide (to|from)_text methods (for the API), and in the next BP, (to|from)_dnpy methods17:15
kiallStorage's methods would then be updated to accept/return the appropriate object, rather than the generic "Record" class17:16
vinodok.  the next part of my question17:16
vinodFor storage's create_record, update_record to take in one of these record types (rather than a dict that as it is currently) and be able to create/update it, we would need to modify either the central and/or api layer to supply one of the record types rather than a dict. Should this be done as another blueprint?17:16
*** tsimmons has quit IRC17:16
kiallEventually, we should end up in a place where we can go recordset = storage.get_recordset(12345) ; recordset.to_dnspy(), which that would then be pushed out over the wire in response to queries etc17:17
*** tsimmons has joined #openstack-meeting-alt17:17
kiallvinod: I actually consider that a bug in the o.m switchover, previous to the o.m migration, our own objects 100% passed over the wire to the API layer17:17
*** noslzzp has quit IRC17:18
kiallSo .. I do think that bug needs to be fixed so we can avoid unnecessary dict<-->object conversions where there not needed17:18
kiallI was actually looking at it about an hour ago, but haven't found the cause yet17:19
betsykiall: o.m switchover?17:19
*** Sourabh has quit IRC17:19
mugsieoslo.messageing17:19
betsyOK. I thought it was oslo something, but couldn’t think what the m was for17:19
kiallThe switch from the depreciated oslo-incubator "rpc" stuff to the replacement oslo.messaging lib17:19
kiallSorry - should have explained :)17:20
*** david-lyle has joined #openstack-meeting-alt17:20
*** tsimmons has quit IRC17:20
betsynp17:20
vinodok kiall i will let you fix that bug - since you have more knowledge there17:20
kiallSure :)17:21
*** Sukhdev has quit IRC17:21
kiallOkay .. So, vinod - I assume this means you're going to take that BP?17:22
vinodyes17:22
kiallCool - I'll get that bug sorted as soon as I can - Hopefully today.17:23
vinodalso wanted to check - is Graham doing the api validation for the various record types?17:23
*** amotoki has quit IRC17:23
*** michael-yu has joined #openstack-meeting-alt17:23
mugsievinod: not at the moment - just the current objects - but when that BP merges, I can update17:24
vinodasking since kiall mentioned something to this effect yesterday17:24
kiallmugsie was adding validation pieces to your objects stuff, which would let us centralize the validations into something that can be used by both the API and Central and mDNS etc17:24
kialli.e. anything based on those objects could then be validated, including the RRType specific objects17:24
mugsieyeah, it would just be updating schemas17:25
kiallOkay - Anything else on this topic before we move onto Open Discussion? (Short agenda today)17:25
vinodEverything clarified17:26
*** IlyaE has quit IRC17:26
kiall#topic Open Discussion17:27
*** openstack changes topic to "Open Discussion (Meeting topic: Designate)"17:27
kiallAny other topics today? :)17:27
jmcbrideDesign time at the summit17:27
kiallAh yes - I saw that got scheduled, but I cant see when it was scheduled for!17:28
kiallmugsie: did you get an email or anything?17:28
jmcbrideMugsie started on this topic and he and I have been looking into finding more time to review blueprints, etc.17:28
mugsiekiall: nope, nothing17:28
mugsieI assume I will get an email from Beth at some point17:28
jmcbrideMugsie: what was the name of the program/event you submitted it under?17:29
mugsieDesign Summit17:29
jmcbrideOK.  Another option for time is https://www.openstack.org/blog/2014/03/call-for-proposals-open-source-openstack-summit/17:29
mugsieyeah17:29
mugsieI would say we go for it17:29
*** Obulpathi has quit IRC17:29
jmcbride"it’s an opportunity for these projects to hold small design summits with their community members."17:29
jmcbrideThe more time available, the better.  I'll go ahead and submit.17:30
kiallIt sounds like that's the same thing you did mugsie?17:30
mugsienope, its a new side track17:30
mugsienot part of the design summit17:30
mugsiewe got offical design summit time17:30
mugsieand this would be extra time -its a full 1/2 day sesion17:30
jmcbrideHow much time did you secure?17:31
mugsieI can work wit jmcbride to put in an application for the new side session17:31
mugsieI don't know - I have never been to a design summit17:31
*** _nadya_ has joined #openstack-meeting-alt17:31
mugsiekiall: any idea how long thre design sessions go on for>17:31
mugsie?*17:31
kiallmugsie: there all different lengths from memory17:31
mugsieIsay we go for it - the more exposure the better17:32
mugsieI say*17:32
*** kgriffs is now known as kgriffs|afk17:32
kiallsummit.openstack.org/cfp/details/196 says "Scheduled"... I'm assuming that means there's a schedule *somewhere*17:32
mugsieyeah - but I don't think it is public yet17:32
mugsiethey said they would let us know by friday17:32
jmcbrideOK, lets go for it. Can we assume the usual suspects from HP, RedHat, eBay and Rackspace will make it?17:32
mugsieme anyway17:32
richmyes17:33
kialljmcbride: yep, definitely17:33
mugsiejmcbride: you free after this? we can put it in this evening if possible17:34
jmcbride#action Joe Work with mugsie to get an application in for https://www.openstack.org/blog/2014/03/call-for-proposals-open-source-openstack-summit/17:34
*** cp16net has joined #openstack-meeting-alt17:34
mugsiecool17:34
jmcbrideyes, I'm free17:34
*** david-lyle has quit IRC17:35
*** yogesh has joined #openstack-meeting-alt17:36
mugsieanythign else?17:36
betsyI’m good17:36
kiallNot from me, I'm already semi-distracted right now (dragged into another conversation as I'm apparently the only person who can still login to the server.. heh)17:36
betsy:)17:37
vinodnothing from me17:37
kiallCool, Okay.. vinod I'll ping you once I've figured out the bug :)17:38
kiallThanks all :) See you in #openstack-dns ....17:38
kiall#endmeeting17:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:38
openstackMeeting ended Wed Apr 16 17:38:41 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-04-16-17.01.html17:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-04-16-17.01.txt17:38
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-04-16-17.01.log.html17:38
*** vinod has left #openstack-meeting-alt17:39
*** amcrn has joined #openstack-meeting-alt17:44
*** sarob has joined #openstack-meeting-alt17:45
*** cweidenkeller has joined #openstack-meeting-alt17:45
*** _nadya_ has quit IRC17:45
*** Obulpathi has joined #openstack-meeting-alt17:45
*** demorris has joined #openstack-meeting-alt17:48
*** k-pom has joined #openstack-meeting-alt17:51
*** michael-yu has quit IRC17:52
*** michael-yu has joined #openstack-meeting-alt17:53
*** markmcclain has joined #openstack-meeting-alt17:54
*** amrith is now known as notamrcn17:54
*** arnaud has joined #openstack-meeting-alt17:55
*** SlickNik has joined #openstack-meeting-alt17:55
*** markmcclain1 has joined #openstack-meeting-alt17:56
*** baoli has quit IRC17:56
*** d0ugal has quit IRC17:56
*** gokrokve has quit IRC17:57
*** baoli has joined #openstack-meeting-alt17:57
*** hub_cap has joined #openstack-meeting-alt17:58
*** yamamoto has quit IRC17:58
*** markmcclain has quit IRC17:59
*** notamrcn is now known as amrith17:59
*** mat-lowery has joined #openstack-meeting-alt17:59
*** jprovazn_afk is now known as jprovazn18:00
SlickNik#startmeeting trove18:00
openstackMeeting started Wed Apr 16 18:00:20 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
*** openstack changes topic to " (Meeting topic: trove)"18:00
openstackThe meeting name has been set to 'trove'18:00
*** eguz has joined #openstack-meeting-alt18:00
*** esp has joined #openstack-meeting-alt18:00
denis_makogono/18:00
SlickNik#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting#Agenda_for_the_weekly_meeting_Apr.1618:00
*** spzala has quit IRC18:00
amcrno/18:00
*** _shalkh has joined #openstack-meeting-alt18:00
esp\o18:00
*** grapex has joined #openstack-meeting-alt18:00
kevinconway7o718:01
SlickNikprevious meeting minutes:18:01
grapexo818:01
SlickNik#link http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-04-09-18.00.html18:01
cp16netholla o]18:01
pdmarso/18:01
vipul\o18:01
SlickNikWe have a quorum. Let's get started.18:01
SlickNik#topic Discuss the expectations of an agenda item for the weekly meeting18:01
*** openstack changes topic to "Discuss the expectations of an agenda item for the weekly meeting (Meeting topic: trove)"18:01
amcrnalright, this is me18:02
*** spzala has joined #openstack-meeting-alt18:02
amcrnLately, agenda items have been extremely terse (usually just a link).18:02
cweidenkellerG/18:02
amcrnWe’d like to try and make this meeting more focused by keeping it very goal-oriented.18:02
*** kgriffs|afk is now known as kgriffs18:02
amcrnThis means agenda items should have a clearly defined objective.18:02
amcrnGood: Review #xxxxx has comments on foobar.py from multiple folks and there seems to be no consensus on how to solve problem ‘y’. Let’s quickly rehash the merits of both approaches in 2-5 minutes and call for a vote. Goal: choose an approach and move forward on implementation.18:02
k-pom\o\18:02
amcrnBad: Discuss blueprint ‘xyz’18:02
amcrnBad: Revisit blueprint ‘abc’ that we talked about last week to get answers on remaining disagreements.18:02
*** jcru has joined #openstack-meeting-alt18:02
amcrn(Note: the last example is bad because the remaining disagreements should be clearly articulated, with each point of view represented and summarized).18:02
*** robertmyers has joined #openstack-meeting-alt18:02
*** imsplitbit has joined #openstack-meeting-alt18:02
amcrnAt the conclusion of an agenda item, a summary of key conclusions, action items, and points of accountability should be noted.18:02
robertmyerso/18:02
glucaso/18:03
*** sarob has quit IRC18:03
amcrnIt’s likely that we’ll want to introduce time-boxing per agenda item in the future, but we think this is a good start. Any questions?18:03
imsplitbito/18:03
*** amytron has joined #openstack-meeting-alt18:03
*** sarob has joined #openstack-meeting-alt18:03
grapexamcrn: So, each agenda item requires a more refined synopsis, and a time limit?18:03
kevinconwayamcrn: who's responsibility is it to summarize the item minutes?18:03
grapexAs well as a clear goal.18:03
annasheno18:03
amcrnkevinconway: the purpose who added it to the agenda18:04
amcrnthe person*18:04
*** eghobo has quit IRC18:04
amcrngrapex: synopsis plus well defined goal18:04
espamcrn: sounds like a good start18:04
amrithamcrn, agreed. one suggestion (given that this is irc) is that we allow the leader of an agenda item to talk and hold only one conversation going if possible18:04
amrithsuch as with this conversation now18:04
amrithyou proposed something18:04
amrithand you got a couple of replies18:04
amrithbut they were all directed at you18:05
kevinconwayi feel like this could have an impact on our useful side conversations that take place during long agent item talks18:05
amrithand it is possible/effective18:05
*** sbalukoff has joined #openstack-meeting-alt18:05
dougshelley66o/18:05
*** khyati has joined #openstack-meeting-alt18:05
*** shivamshukla has joined #openstack-meeting-alt18:05
grapexkevinconway: That is a sad18:05
grapexamcrn: I like this idea. SlickNik, do you think we should vote on it now?18:05
yogesho/18:05
amrithamcrn: you agree wity my idea or not18:06
vgnbkro/18:06
amcrnamrith: not sure i understand your suggestion18:06
SlickNikamcrn / grapex: I like this too.18:06
amrithamcrn: often we have many conversations going in parallel18:06
SlickNikWhat's the course of action when a "bad" agenda item makes its way on to the agenda?18:06
kevinconwaygrapex: so hang on, if you're going to vote on a process should we get it codified into a by-law?18:06
amrithand it is confusing18:06
amrithso along with the idea of a clearly defined agenda item18:06
amrithI was proposing that we have some structure in the conversation18:07
amrithand end with a decision/conclusion18:07
amcrnwe can play police a bit more and stop tangential conversations from over-running the channel18:07
*** sarob has quit IRC18:07
amrithamcrn: ok, makes sense18:07
amcrnand to your last point: [11:02:59]  <amcrn> At the conclusion of an agenda item, a summary of key conclusions, action items, and points of accountability should be noted.18:07
amcrnSlickNik: I vote it goes to the bottom of the list18:08
amrithamcrn: I agree18:08
amcrnSlickNik: but we can take a peek and ping people on Monday/Tuesday giving some guidance on how items can be framed/boxed better.18:08
vipulthe wiki page gets overwritten though18:08
kevinconwayamrith: are you suggesting http://www.robertsrules.org/?18:08
* robertmyers does18:08
*** ramishra has joined #openstack-meeting-alt18:09
SlickNikamcrn: +1 on the guidance piece.18:09
SlickNikOkay, I think pretty much all of us think this is a good idea.18:09
denis_makogonagreed18:09
SlickNikTo grapex's call for a vote: +118:10
dougshelley66+1 and the same "rules" should be carried over to the Monday BP meeting18:10
amcrn+118:10
grapex+118:10
amrith+118:10
esp+118:10
denis_makogon+118:10
vipul+118:10
cweidenkeller+118:10
kevinconwaycan i get a summary of this before vote?18:10
k-pom+118:10
imsplitbit+3418:10
amcrnkevinconway: i'll do so and put it on the wiki18:10
yogesh+118:10
kevinconwayso what is everyone voting on?18:10
vipullol18:10
kevinconwayi got lost in the side convos18:11
imsplitbitvoting18:11
pdmars+118:11
denis_makogonkevinconway, voting for the vote18:11
amcrnmoving on18:11
SlickNikOkay, let's move on.18:11
SlickNik#topic Datastore and Datastore Version Concat in Trove Horizon Dashboard18:11
grapexSlickNik: Maybe you should post these new rules on the top of the agenda wiki page so people see them before they add anything18:11
*** openstack changes topic to "Datastore and Datastore Version Concat in Trove Horizon Dashboard (Meeting topic: trove)"18:11
amcrngrapex: i'll take care of that, good idea18:11
SlickNikgrapex +1. amcrn: thanks18:11
amcrnmichael-yu: you're up18:12
michael-yuSo, this topic is the Horizon patch for supporting multiple data stores.18:12
michael-yuFor the proposed behavior, see the commit message:18:12
michael-yuhttps://review.openstack.org/#/c/75269/18:12
*** NehaV has joined #openstack-meeting-alt18:12
michael-yuThere is an underlying question is whether we should have 2 drop downs in Launch Instance18:12
michael-yuone for datastore type, the other for datastore-version18:12
michael-yuor just one drop down that concats the two18:13
denis_makogonmichael-yu, i read all coments and came in to the conclusion, that dashboard should have two dependent choise box18:13
*** ramishra has quit IRC18:13
michael-yudenis_makogon: ok18:13
robertmyersmichael-yu: I fine with two if you must18:13
robertmyersi'm a +018:14
*** nicole has quit IRC18:14
vipuli tend to agree with robertmyers on this one.. although we're represented it as two separate fields in the DB.. most deployers will make this an easy concat when they set it up18:14
robertmyersBut possibly the ui should handle it18:14
robertmyerswith angular :)18:14
denis_makogonso, can we move on ?18:15
amrithrobertmyers, were those your review comments? looks like you weren't in favor?18:15
amcrndenis_makogon: no, because the goal hasn't been met18:15
denis_makogoni guess we agreed that two dropdowns are totally fine18:15
robertmyersamrith: yes those are mine18:15
amcrndoes anyone else in the room have an opinion?18:15
amrithrobertmyers, thx18:16
robertmyerslike I said I don't love it18:16
robertmyersbut I wont stand in the way18:16
amcrnbecause i find robertmyers point somewhat intriguing, because it almost suggests they should haven't been two fields in the first place.18:16
vgnbkrIf going with two, could the database type default to "mysql" and the version to the latest version for the selected type?18:16
amcrnshouldn't*18:16
robertmyersamcrn: yes18:16
robertmyersit is silly18:16
amrithamcrn typed the words faster than I could18:16
SlickNikI have a slight preference for 1, because it's one less click, and one less control.18:16
amcrnrobertmyers: where were you when i was the only one voting for single field against a barrage of others :P18:17
robertmyersaustin18:17
robertmyers:)18:17
amcrnlol18:17
amrithrobertmyers, amcrn ... other than the aesthetics can you see a downside to two boxes?18:17
amritharen't they linked?18:17
michael-yuyes, they are linked18:17
kevinconwayi don't see how the number of db columns defines the interface18:17
vipulwell the UI doesn't necessarily have to reflect how data is stored18:17
denis_makogonvipul, agreed18:17
vipulkevinconway: +118:18
abramleyWe may just end up with the 2nd box just containing a single entry for all database18:18
abramley... e..g MySQL -> 5.5 only18:18
*** jprovazn has quit IRC18:18
yogeshabramley: good point18:18
amcrnwith devstack right now, the result would be "mysql-mysql-5.5"18:18
robertmyerswell, what we really want is people to pick the version18:18
*** gokrokve has joined #openstack-meeting-alt18:18
vipulwhy don't we go with one less drop-down and if this really becomes an issue.. we can revisit by changing the UI18:18
robertmyersvipul: +118:18
robertmyersthat is my point18:18
amrithI like vipul's idea (also robert, amcrn)18:18
amrith+1 on that18:19
abramley+1 for a single dropdown with a merged datastore and version18:19
*** walker__ has joined #openstack-meeting-alt18:19
amcrnvipul: i'll agree if as a follow-up we can have a blueprint discussing the termination of datastore-type permanently from the api in a version 218:19
amcrnbecause it's caused nothing but headaches18:19
denis_makogonif that's the case, i'm fine too18:19
vipulamcrn: so expose just a version?18:19
yogeshvipul: +1 for a single dropdown18:19
*** emaganap has quit IRC18:19
amcrnvipul: one field, "mysql-5.5" vs "mysql" and "5.5"18:20
amcrnbecause as of now, datastore-type is an overglorified piece of metadata that's acting as a first class element18:20
*** emagana has joined #openstack-meeting-alt18:20
vipulI suppsoe that would work.. everything is tied to the datastore_version..18:20
SlickNikamcrn: I like it, but that's a conversation for another day.18:20
amcrnagreed, tangential. i'll take up an action item to summarize my thoughts on that and bring it up another time in a blueprint.18:21
amcrnvote time?18:21
SlickNikamcrn: goal met for this agenda item?18:21
amcrn(for single dropdown vs. multi)18:21
*** flwang has quit IRC18:21
amrithamcrn, single dropdown +118:21
espI’m not very familiar with the look and feel of the horizon project atm.  are there existing screens that show multiple drop downs?18:21
amcrni think we're all ok with single18:21
denis_makogonagreed18:21
espI can withdraw my ? if we are ready to vote18:21
*** nicole has joined #openstack-meeting-alt18:22
*** SnowDust has joined #openstack-meeting-alt18:22
amcrnany voters for double?18:22
amcrnif not, we can move on18:22
abramley-1 double18:22
SlickNikesp: I believe you can talk to them for guidance, but ultimately it's for the team to decide.18:22
SlickNiksingle +118:22
espSlickNik: k, I’m gonna sit out of this vote :)18:22
grapexsingle +118:22
yogeshsingle +118:23
glucassingle +118:23
michael-yuthat's fine with me. single that is.18:23
michael-yuone question though:18:23
hub_capat the end of the day, u wont have 80 different active mysql-5.X18:23
amrith(amrith, married)18:23
hub_capso single ++18:23
hub_capamrith: lol u cant vote for two18:23
cp16netabstain18:23
mattgriffinsingle +118:23
cweidenkellersingle +118:23
robertmyerssingle +118:23
denis_makogonsingle +118:23
vipulsingle18:23
*** sarob has joined #openstack-meeting-alt18:23
*** eanxgeek is now known as eanxgeek|log18:24
amcrnthis is like Kim Jung-Un's re-election results: 100% yes18:24
*** _shalkh has quit IRC18:24
amcrnalright, let's move on18:24
*** _shalini_kh has joined #openstack-meeting-alt18:24
esplol18:24
hub_capamcrn: hahahaha18:24
SlickNikamcrn: thanks.18:24
denis_makogonamcrn, like Putin elections18:24
dougshelley66amcrn i could vote against it if it makes you feel better18:24
grapexamcrn: Hey let's not get into divisive political topics here.18:24
amcrndougshelley66: lol18:24
grapexamcrn: I heard the other day on North Korea media they were contributing 99% of the code for the latest OpenStack releases.18:25
SlickNik#topic Perform integration testing for the heat based instances18:25
*** openstack changes topic to "Perform integration testing for the heat based instances (Meeting topic: trove)"18:25
*** mugsie has left #openstack-meeting-alt18:25
shivamshuklayes this is basically to test heat based instance workflow18:25
shivamshuklathere is a patch for this https://review.openstack.org/#/c/66499/18:25
dougshelley66grapex: i didn't realize all you guys liven in North Korea18:25
vipulgrapex: haha18:25
*** balajiiyer has joined #openstack-meeting-alt18:25
espgrapex: that explains a lot :)18:26
shivamshuklaso for this we needed to change config values of trove-taskmanager.conf18:26
denis_makogoni've got question to core about heat based flow18:26
*** coolsvap is now known as coolsvap|afk18:26
shivamshuklaand a reastart of service18:26
vipulso the issue I had with this patch is how we are expecting that the taskmanager be restarted18:26
*** eanxgeek|log is now known as eanxgeek18:26
vipulthat makes this test worthless if we ever expect to run it against a remote system18:26
grapexvipul: +118:27
denis_makogonvipul, i think for heat based testing we would need third-party CI18:27
vipuli do think we need to figure out ways to excercise both code paths though18:27
grapexshivamshukla: Also, since these tests seem to create a new instance, I think they should go into a new file rather than being added to instances.py18:27
shivamshuklaso my question is how can we do that other then this way18:27
_shalini_khSo the idea is if we dont restart the service then it wont read use-heat true.18:27
vipul_shalini_kh: right, but if the taskmanager was not on the same machine as the tests.. then you couldn't do that anyway18:28
robertmyersvipul: +118:28
denis_makogon+1 to 3d party CI for heat based provisioning18:28
_shalini_khHow will we change configuration without restarting..?18:28
*** balajiiyer has left #openstack-meeting-alt18:28
grapexAnother question is do we want to make testing heat it's own unique tests, or change the test config so it makes the existing tests use heat?18:28
denis_makogongrapex, i guess we still need to restart taskmanager18:29
grapexBecause if we modify the existing tests to work with Heat if the config is different, then it's a matter of setting up Trove to use Heat, then telling the test configs you want to test it that way18:29
yogeshdenis_makogon: what 3rd party CI, do we have it getting used elsewhere...18:29
grapexAlthough maybe it's easier to make these new tests18:29
vipulgrapex: That would be ideal -- how do we get both code paths tested in a single Gate18:30
*** spzala has quit IRC18:30
SlickNikgrapex: +118:30
grapexvipul: So maybe this idea of restarting taskmanager should be allowed but tweakable via the test config-18:30
*** spzala has joined #openstack-meeting-alt18:30
yogeshvipul: can we have a new heat gate?18:30
grapexSo this may be a bit confusing, but imagine the heat tests are introduced as new tests18:30
grapexwith the same groups as the existing instance create tests18:31
SlickNikI think we have a good chunk of our test suite that we'd want to run using this new ("heat" enabled) config.18:31
*** nicole1 has joined #openstack-meeting-alt18:31
SnowDust+1 together for heat gate18:31
grapexSo the tests work the same, but at that point it runs both sets of tests. In the VM, it restarts task manager18:31
vipulyogesh: yea, you could.. it would increase the overall time..18:31
grapexbut if you want to test remote, you basically disable one of those sets as well as the taskmanager restart18:31
denis_makogongrapex, only provisioning tests can work with heat based trove, nothing else18:31
yogeshvipul: at the cost of some time, a better abstraction18:32
denis_makogongrapex, no resizes, no security groups18:32
SlickNikyogesh: Yes, but there are some holes in heat (esp. regarding resize) that we would have to fix before all our tests would run in that gate as it.18:32
denis_makogonSlickNik, there are plans in heat to cover all cases required by Trove18:32
*** nicole has quit IRC18:32
yogeshSlickNik: it can be incremental18:32
denis_makogonSlickNik, i've got several BP already approved in heat space18:32
denis_makogonSlickNik, security groups update, volume resize18:33
yogeshdenis_makogon: pointers to BPs please...18:33
SlickNikyogesh: But then you'd have to maintain more, different test code for the different workflow.18:33
denis_makogonyogesh, they already asssigned to my college18:33
SnowDustSlickNik heat gate answers no heat tests vs some tests18:33
vipulgrapex: I could live with that.. so there would be a test.conf flag that says.. run non-remote tests.. and this one that restarts would fall into that category18:33
*** spzala has quit IRC18:33
grapexvipul: Yeah. If there's two sets of tests, and you want to just run one- I think we'd have to disable one of the sets of tests.18:34
grapexThat gets tricky. But I'm sure there's a better way I could think of with a bit more time. That way in the public we're able to test both.18:34
vipulso to make this happen sooner.. (heat gate would be a bigger effort) .. we can do what's in the patch, provided they provide a way via cfg to turn off the test shivamshukla18:34
grapexNow- in the distant past, when Reddwarf was a fork, we had a test that would restart nova after changing the configs18:35
grapex*nobody liked it*18:35
vipuli really want to see that heat works.. and the sooner we can get it into the default gate the better18:35
denis_makogonvipul, but we need to think about heat gate18:35
grapexso we'd need to be careful, since if we do that wrong it could cause problems18:35
vipuldenis_makogon: wanna help set it up?18:35
grapexvipul: I agree- right now we have no idea how well heat is working.18:35
vipulwe need more testing resources denis_makogon18:35
yogeshgrapex: it is working smooth18:35
denis_makogonvipul, first we need to refactor code to extract heat provisioning into it's own manager for taskamanager18:35
denis_makogonvipul, and than setup the another gate18:36
SnowDustvipul we can set it up if required18:36
SnowDustand commit testing resources from our side18:36
vipulSnowDust: i mean compute resources SnowDust18:36
SlickNikSnowDust: It's not just about testing resources. You'd need compute capacity as well.18:37
SnowDust;)18:37
vipulalthough that's not a huge issue18:37
*** akuznetsov has joined #openstack-meeting-alt18:37
SnowDusthmm18:37
grapexMaybe we should wait for datastore capabilities to make it easier to change the configs related to Heat18:37
grapexBecause if we have to have test code that's mucking with a config file we will all be less happy18:37
denis_makogonvipul, for now i agree with test.conf, but in the nearest future, we should think about it's own gate18:38
grapexbut if there's an API for capabilities we could call, and then restart it, it will be much easier.18:38
vipulgrapex: yea we can revise the test when that's in18:38
SlickNikAs much as I'd like to spend time on a separate heat gate, I can live with having some _heat_ testing using the flag approach grapex and vipul mentioned earlier.18:38
SnowDustbut I am also open to discuss a conf setting to turn testing switch between heat non heat18:38
grapexvipul: True- maybe we should wait though18:38
denis_makogongrapex, how does the capabilities can help testing heat code ?18:38
shivamshuklabut how come changing test.conf will create instance using heat as it will only read from taskmanager.conf18:39
vipulso let's jsut do this.. fix the test to honor a flag.. get this in, at least continues to prove that we don't break heat18:39
*** SnowDust has left #openstack-meeting-alt18:39
SlickNiklong term, we'd probably want a separate gate running in parallel using the infra/ci test resources.18:39
denis_makogonSlickNik, ++18:39
*** michael-yu has quit IRC18:40
*** vkmc has quit IRC18:40
yogeshAwesome...agreed18:40
SlickNikvipul: +118:40
*** michael-yu has joined #openstack-meeting-alt18:40
yogesh+118:40
*** _nadya_ has joined #openstack-meeting-alt18:41
shivamshuklaok so we will need a flag for non remote for which we need to disable our test18:41
grapexvipul: so by honor a flag, you just mean we could turn off the "restarr taskmanager" bit, right?18:41
grapexI think I agree with were we've ended up on this18:41
vipulgrapex: yes.. or like shivamshukla says..18:41
*** SnowDust has joined #openstack-meeting-alt18:41
grapex+118:41
SlickNikCool, I think we've got a path forward on this.18:41
SlickNikLet's move on.18:41
SlickNik#topic Neutron Support, SecGroup Management, and Networking18:42
*** openstack changes topic to "Neutron Support, SecGroup Management, and Networking (Meeting topic: trove)"18:42
*** marun has quit IRC18:42
denis_makogonannashen, suppose you here =)18:42
denis_makogonlet me talk first18:42
SlickNikdenis_makogon: sure, you can go first.18:42
denis_makogonat the previous BP meeting we talked about supporting neutron and nova-network18:43
denis_makogoni proposed to make it switchable via config18:43
SlickNikI have some questions regarding this, but will wait until you finish.18:43
denis_makogonBP didn't got approved, yet18:43
denis_makogonso, implementation will cover Base interface and nova-network implementation18:43
SlickNikSo is this just "Please look at BP and approve"?18:44
denis_makogonno18:44
*** kgriffs is now known as kgriffs|afk18:44
denis_makogonnot at all18:44
denis_makogoni'd like to hear thoughts of community over this18:44
amrithdenis_makogon, I'm unsure what you are asking18:44
kevinconwayso the only thing that i was uncertain of in the BPs is that neutron support is mutex with nova-network and there's no way to enable neutron in an existing deploy18:45
grapexSo, this topic has three blueprints, so I'm a bit confused as to the aspect we're discussing18:45
denis_makogoni'm asking community to say if it has suggestions or concerns, if not, i guess BP can be approved18:45
denis_makogon#link https://blueprints.launchpad.net/trove/+spec/network-manager-spec18:45
SlickNikSo, frankly I'm confused as to why there are 3 separate BPs on this.18:46
denis_makogonSlickNik, one for refactoring current code, and implementing nova-network driver18:46
grapexdenis_makogon: I don't see it that way18:46
denis_makogonother for neutron18:46
robertmyersThat seems like it could all be one18:46
grapexone of these looks like creating a network manager for the existing trove functionality18:46
*** jprovazn has joined #openstack-meeting-alt18:47
denis_makogongrapex, that's mine18:47
grapexThe one from Anna Shen, "Secgroup management via neutron vs nova-network", is about using neutron in addition to nova-network18:47
grapexso it looks like there's some overlap18:47
SlickNikWhy would you need a separate BP to "refactor" code with the sole goal of achieving what another BP already aims to achieve?18:47
grapexthen there's another one from Anna called "Neutron Support for Trove" that's about adding the two networks to each Trove instance which is related to what Juice discussed a few weeks back18:47
denis_makogonSlickNik, we decided to split them18:47
denis_makogondifferent tasks18:48
robertmyerswe don't need two BP for tasks18:48
SlickNikYou can have different tasks as part of the same BP. That's what "partially-implements" is for.18:48
grapexSo I'm guessing "Neutron Support for Trove" should not be a part of today's discussion as it seems less like the two other ones18:48
denis_makogongrapex, i think annashen 's BP about using neutron instead of nova-network18:48
vipulgrapex: Yea i think that's a separate thing that could land after this refactoring/manager implemetatin18:49
denis_makogonvipul, yes, that's what i'm saying18:49
vipuldenis_makogon: i'm talking about the one Juice discussed18:49
grapexdenis_makogon: Well these look very similar: https://blueprints.launchpad.net/trove/+spec/secgroup-mgmt-via-neutron and https://blueprints.launchpad.net/trove/+spec/network-manager-spec18:49
SlickNikdenis_makogon: https://blueprints.launchpad.net/trove/+spec/secgroup-mgmt-via-neutron needs the refactoring to happen to implement it, yes?18:49
*** chandan_kumar has joined #openstack-meeting-alt18:49
*** rand738 has quit IRC18:49
kevinconwayok, my concern is with the neutron BPs18:49
annashen#link https://blueprints.launchpad.net/trove/+spec/neutron-support18:50
denis_makogongrapex, they cannot be similar18:50
*** SnowDust has quit IRC18:50
denis_makogongrapex, i'm not aiming to implement new API for SGs18:50
*** pcm__ has joined #openstack-meeting-alt18:50
*** pcm__ has left #openstack-meeting-alt18:51
vipulannashen: https://blueprints.launchpad.net/trove/+spec/secgroup-mgmt-via-neutron and https://blueprints.launchpad.net/trove/+spec/neutron-support are the same18:51
vipulshould be the same18:51
kevinconwayso before we rush to integrate a bunch of neutron code, what's with the disclaimer that no-one with an existin trove deploy can use the features?18:51
grapexdenis_makogon: Maybe I'm misreading this but the one from Ana says "use neutron to do the security group stuff" with comments by you saying "let's make a manager base class to switch between neutron and nova-volume"18:51
*** rand738 has joined #openstack-meeting-alt18:51
denis_makogongrapex, my goal is to refactor actual code to have an ability to switch from nova-network to neutron harmlessly18:51
grapexdenis_makogon: Then yours is about making a network manager to switch between neutron and nova-network18:51
*** nicole1 has quit IRC18:51
vipulkevinconway: I don't know if there is a good way for both to co-exist in hte underlying infrastructure anyway18:51
*** jjmb has joined #openstack-meeting-alt18:51
*** pcm__ has joined #openstack-meeting-alt18:51
grapexfor the record I prefer denis's blueprint here- I think we should make an interface so we can use nova-network or neutron18:51
*** pcm__ has left #openstack-meeting-alt18:51
vipuli don't think you can have a Nova deployment with both kevinconway18:52
dougshelley66this may be a mild tangent - but could someone state what the current support (or lack therof) for neutron is in trove today?18:52
grapexdougshelley66: we're not using neutron today.18:52
kevinconwayvipul: not necessarily both, but there is _no_ migration path for an existing deploy18:52
annashenvipul, i was thinking there might be more complicated scenarios for sec group so i created another one18:52
vipulkevinconway: that's a infrastructure migration issue really..18:52
amrithdougshelley66, what denis_makogon told me yesterday is that there is NO support today18:52
grapexNow it also seems like denis_makogon's blueprint came after annashen's18:52
*** russellb has quit IRC18:53
dougshelley66so shouldn't we understand what the issue(s) are and have one BP to address them?18:53
kevinconwayvipul: is there a precedence in OS showing migrations from network to neutron?18:53
vipulkevinconway: i don't think there is a good way to do it :) -- what i've seen really is set up a new cloud with neutron, migrate workloads18:53
grapexkevinconway: I think we can worry about migrations as a later step, especially if we allow either nova-network or neutron to work going forward18:53
denis_makogongrapex, mine BP comes first because without any refactoring it would be hard to use neutron based network attributes management over existing code18:54
vipulwhich is why not many have movd onto neutron18:54
kevinconwayno, i agree we should have support for neutron. i think it's a bad idea to have _zero_ plan to upgrade exiting troves to use it18:54
*** _shalini_kh has quit IRC18:54
*** Rajeev has quit IRC18:54
kevinconwaywhat other feature have we implemented where the upgrade strategy was "start over"?18:54
grapexSlickNik and core: I guess the question is which of these two blueprints do we want to keep?18:55
vipulkevinconway: i don't see how that is a Trove responsibility... esmute is implementing cross-region restore.. and that could be used by Trove users to switch to a new infrastructure18:55
*** russellb has joined #openstack-meeting-alt18:55
denis_makogongrapex, good question, i suppose18:55
amrithdenis_makogon, annashen it sounds like there are some questions being asked here. (a) there are two tasks and three blueprints. is there a reason for this? (b) is there a requirement to switch back and forth from neutron to nova? would someone use that? and (c) what are the issues involved in switching to neutron from nova.18:55
grapexkevinconway: I think there *will* be an upgrade strategy later. Though vipul is right, that may be the responsibility for Neutron and not necessarily us18:55
kevinconwaylet me rephrase my conerns: I think upgrade/migration documentation for this feature should be a pre-req to completion18:55
amrithSlickNik and core: I'd equally direct my questions above to y'all (or is that all'o'y'all)18:56
denis_makogonamrith, we would npt switch to neutron once nova-network will be deprecated18:56
annashenamrith, trove currently support nova-network, by introducing neutron, we do not want nova-network going away immedidately18:56
SlickNikamrith: There isn't a requirement to switch back and forth.18:57
*** balajiiyer has joined #openstack-meeting-alt18:57
amrithSlickNik, I misread denis_makogon' earlier comment.18:57
SlickNikamrith: At some point, neutron becomes the preferred way of doing networking in your OpenStack cloud.18:57
grapexSlickNik: It's time for you to exercise your PTL POWARS. One blueprint must live... and one shall die!18:57
amrithI agree18:57
vipulwe need a way to pick which backend Nova or Nuetron.. that's it.  We also need to implement the Neutron backend18:57
grapexThat's my take anyway18:57
denis_makogonamrith, nova-network should be deprecated at the end of the Juno, i suppose, so as nova-network driver also would be marked as deprecated18:58
yogeshdenis_makogon: annashen: a side question, do we plan to cover its flow through heat, in the alternate heat-enabled path...18:58
vipuland let's get rid of these BPs!18:58
SlickNikamrith: And we need to be able to run trove on an OpenStack Cloud that is running neutron, instead of nova-networking.18:58
denis_makogonyogesh, someday - yes18:58
SlickNikamrith: Those are all the requirements I see for this for now.18:58
amrithso the questions that remain are these, why 3 bp's, and what are the issues in moving to neutron; would that migration be someone elses responsibility18:58
annashenright, please vote, go or no go18:58
amrithSlickNik, looks like we are saying same thing; thx18:58
dougshelley66wouldn't it make sense for someone to draft a BP that outlines the requirements first?18:59
denis_makogonas for me i see two tasks at now18:59
SlickNikSo here's my view on the current BP issue.18:59
vipuldougshelley66: yet another BP!18:59
*** andreaf has quit IRC18:59
SlickNikLet's have 1 BP for supporting neutron.18:59
dougshelley66clearly none of the existing BPs has enumerated the requiremetns18:59
dougshelley66which is why we are having this discussion18:59
denis_makogonSlickNik, agreed19:00
yogeshdiugshelley66: +1, i think THE bp should be elaborated19:00
*** balajiiyer1 has joined #openstack-meeting-alt19:00
imsplitbitI'm exhausted19:00
SlickNikAnd in it detail all the gaps that we currently have that need to be filled.19:00
dougshelley66SlickNik +119:00
annashenslicknick +119:00
SlickNikMultiple folks can work against that 1 BP, if needed.19:00
vipulSlickNik: pick 1 BP.. and have annashen and denis_makogon just fill it in completely19:00
yogeshSlickNik +119:00
grapexSlickNik: I'm ok with that- as long as we keep in nova-network functionality19:00
amrithSlickNik, +119:00
hub_capso annashen was schedule to work on this19:01
grapexSlickNik: Just want to confirm that is also part of the plan.19:01
hub_caplets let her do the work, but make sure it supports both use cases19:01
amrithgrapex +1, I was given this assurance at last meeting19:01
SlickNikLet's use this one: https://blueprints.launchpad.net/trove/+spec/neutron-support19:01
denis_makogonhub_cap, annashen will take neutron support19:01
SlickNikSince it most resembles what I'm talking about.19:01
vipulhub_cap: +1 we can do that.. there isn't that much work here19:01
*** gondoi is now known as zz_gondoi19:01
hub_capright vipul19:01
hub_capits not a ton of work19:01
hub_capsplitting it will take more time19:01
hub_capdenis_makogon: can work on something else since annashen had proposed it initially19:01
hub_capdenis_makogon: couldve told anna to mod her bp instead of creating a nother19:02
*** balajiiyer has quit IRC19:02
grapexhub_cap: +119:02
SlickNikIf we need to do any refactoring as a result of what we need to achieve to fix these gaps, we can use the same bp, and "partially implements".19:02
hub_captimes up19:02
hub_capend it SlickNik19:02
vipulhub_cap: +10019:02
SlickNikhub_cap: +119:02
SlickNik#endmeeting19:02
denis_makogonhub_cap, first i proposed, but didn't saw any response/changes over 2-3 weeks, i suppose19:02
*** jmcbride has quit IRC19:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:02
openstackMeeting ended Wed Apr 16 19:02:51 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-04-16-18.00.html19:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-04-16-18.00.txt19:02
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-04-16-18.00.log.html19:02
SlickNikThanks all.19:02
*** imsplitbit has left #openstack-meeting-alt19:03
*** demorris has quit IRC19:03
amrithbye all!19:03
*** robertmyers has left #openstack-meeting-alt19:03
*** k-pom has left #openstack-meeting-alt19:03
*** shivamshukla has left #openstack-meeting-alt19:03
*** eankutse has joined #openstack-meeting-alt19:04
*** rpodolyaka1 has quit IRC19:05
*** eankutse1 has quit IRC19:06
*** colinmcnamara has joined #openstack-meeting-alt19:07
*** rjrjr has quit IRC19:08
*** ramishra has joined #openstack-meeting-alt19:09
*** SlickNik has left #openstack-meeting-alt19:10
*** jmcbride has joined #openstack-meeting-alt19:10
*** mat-lowery has left #openstack-meeting-alt19:10
*** nati_ueno has joined #openstack-meeting-alt19:10
*** BrianB_ has quit IRC19:10
*** esp has left #openstack-meeting-alt19:11
*** demorris has joined #openstack-meeting-alt19:11
*** dprince has quit IRC19:11
*** eankutse has quit IRC19:11
*** eankutse has joined #openstack-meeting-alt19:12
*** ramishra has quit IRC19:14
*** jdob_ has joined #openstack-meeting-alt19:15
*** nati_ueno has quit IRC19:20
*** yamahata_ has quit IRC19:21
*** nati_ueno has joined #openstack-meeting-alt19:21
*** rpodolyaka1 has joined #openstack-meeting-alt19:21
*** jecarey_ has joined #openstack-meeting-alt19:28
*** michael-yu has quit IRC19:30
*** chandan_kumar has quit IRC19:30
*** michael-yu has joined #openstack-meeting-alt19:32
*** jecarey has quit IRC19:32
*** nati_uen_ has joined #openstack-meeting-alt19:32
*** nati_ueno has quit IRC19:33
*** _nadya_ has quit IRC19:34
*** nati_uen_ has quit IRC19:35
*** malini is now known as malini_afk19:38
*** mattgriffin is now known as mattgriffin-afk19:40
*** mattgriffin-afk has quit IRC19:41
*** jmcbride has quit IRC19:42
*** dkehn_ has joined #openstack-meeting-alt19:43
*** eankutse has quit IRC19:44
*** eankutse has joined #openstack-meeting-alt19:44
*** dkehn has quit IRC19:46
*** dkehn_ has quit IRC19:46
*** amcrn_ has joined #openstack-meeting-alt19:46
*** dkehnx has quit IRC19:46
*** dkehn_ has joined #openstack-meeting-alt19:46
*** amcrn has quit IRC19:47
*** dkehn has joined #openstack-meeting-alt19:48
*** eanxgeek is now known as eanxgeek|log19:48
*** sarob has quit IRC19:48
*** amcrn_ is now known as amcrn19:48
*** spzala has joined #openstack-meeting-alt19:50
*** zns has quit IRC19:53
*** msisk has left #openstack-meeting-alt19:53
*** chandan_kumar has joined #openstack-meeting-alt19:56
*** jmcbride has joined #openstack-meeting-alt19:57
*** akuznetsov has quit IRC19:57
*** IlyaE has joined #openstack-meeting-alt19:58
*** NehaV1 has joined #openstack-meeting-alt19:59
*** jmcbride has quit IRC19:59
*** jprovazn has quit IRC19:59
*** colinmcnamara has quit IRC19:59
*** jdob_ has quit IRC19:59
*** NehaV has quit IRC20:00
*** demorris has quit IRC20:02
*** Barker has quit IRC20:02
*** eankutse1 has joined #openstack-meeting-alt20:02
*** eankutse has quit IRC20:03
*** khyati_ has joined #openstack-meeting-alt20:03
*** khyati has quit IRC20:04
*** esp has joined #openstack-meeting-alt20:06
*** Barker has joined #openstack-meeting-alt20:07
*** Sukhdev has joined #openstack-meeting-alt20:08
*** rpodolyaka1 has quit IRC20:09
*** ramishra has joined #openstack-meeting-alt20:10
*** sarob has joined #openstack-meeting-alt20:10
*** Barker has quit IRC20:12
*** nicole has joined #openstack-meeting-alt20:12
*** nicole has quit IRC20:13
*** Barker has joined #openstack-meeting-alt20:14
*** zns has joined #openstack-meeting-alt20:14
*** ramishra has quit IRC20:14
*** sarob has quit IRC20:15
*** david-lyle has joined #openstack-meeting-alt20:16
*** esp has left #openstack-meeting-alt20:16
*** emagana has quit IRC20:17
*** NehaV1 has quit IRC20:19
*** jomara has quit IRC20:19
*** NehaV has joined #openstack-meeting-alt20:19
*** baoli has quit IRC20:20
*** sarob has joined #openstack-meeting-alt20:20
*** jomara has joined #openstack-meeting-alt20:20
*** gyee has joined #openstack-meeting-alt20:21
*** eankutse1 has quit IRC20:23
*** eankutse has joined #openstack-meeting-alt20:23
*** mattgriffin has joined #openstack-meeting-alt20:24
*** mattgriffin has quit IRC20:29
*** ameade has quit IRC20:29
*** eankutse has quit IRC20:36
*** eankutse has joined #openstack-meeting-alt20:36
*** michael-yu has quit IRC20:39
*** manishg has left #openstack-meeting-alt20:42
*** gokrokve has quit IRC20:42
*** jomara has quit IRC20:44
*** jomara has joined #openstack-meeting-alt20:45
*** michael-yu has joined #openstack-meeting-alt20:47
*** mattgriffin has joined #openstack-meeting-alt20:48
*** eguz has quit IRC20:49
*** eghobo has joined #openstack-meeting-alt20:50
*** balajiiyer1 has quit IRC20:55
*** jdob has quit IRC20:55
*** Obulpathi has quit IRC20:57
*** jmcbride has joined #openstack-meeting-alt20:59
*** baoli has joined #openstack-meeting-alt21:00
*** gokrokve has joined #openstack-meeting-alt21:02
*** kgriffs|afk is now known as kgriffs21:03
*** kgriffs is now known as kgriffs|afk21:04
*** jmontemayor has quit IRC21:07
*** mfer has quit IRC21:07
*** balajiiyer has joined #openstack-meeting-alt21:08
*** rpodolyaka1 has joined #openstack-meeting-alt21:10
*** sarob has quit IRC21:11
*** sarob has joined #openstack-meeting-alt21:11
*** amytron_ has joined #openstack-meeting-alt21:14
*** rpodolyaka1 has quit IRC21:14
*** amytron has quit IRC21:14
*** amytron_ is now known as amytron21:14
*** sarob has quit IRC21:15
*** betsy_ has joined #openstack-meeting-alt21:23
*** kevinconway has quit IRC21:23
*** balajiiyer has quit IRC21:23
*** sarob has joined #openstack-meeting-alt21:24
*** jcoufal has joined #openstack-meeting-alt21:24
*** denis_makogon has quit IRC21:24
*** betsy has quit IRC21:24
*** betsy_ is now known as betsy21:24
*** sarob_ has joined #openstack-meeting-alt21:27
*** grapex has quit IRC21:28
*** sarob_ has quit IRC21:28
*** pdmars has quit IRC21:28
*** sarob_ has joined #openstack-meeting-alt21:29
*** sarob has quit IRC21:29
*** eguz has joined #openstack-meeting-alt21:29
*** sarob has joined #openstack-meeting-alt21:31
*** zns has quit IRC21:31
*** sarob has quit IRC21:32
*** sarob_ has quit IRC21:33
*** eghobo has quit IRC21:34
*** jmcbride has quit IRC21:35
*** betsy has quit IRC21:36
*** Obulpathi has joined #openstack-meeting-alt21:36
*** Barker has quit IRC21:38
*** mwagner_lap has quit IRC21:38
*** NehaV has quit IRC21:39
*** jcru has quit IRC21:52
*** betsy has joined #openstack-meeting-alt21:56
*** demorris has joined #openstack-meeting-alt21:56
*** carl_baldwin has quit IRC21:57
*** manishg has joined #openstack-meeting-alt22:00
*** jecarey_ has quit IRC22:02
*** demorris has quit IRC22:02
*** betsy has quit IRC22:05
*** amytron has quit IRC22:06
*** Sukhdev has quit IRC22:08
*** rpodolyaka1 has joined #openstack-meeting-alt22:10
*** michael-yu has quit IRC22:13
*** sarob has joined #openstack-meeting-alt22:13
*** jecarey_ has joined #openstack-meeting-alt22:14
*** rpodolyaka1 has quit IRC22:15
*** NehaV has joined #openstack-meeting-alt22:15
*** zns has joined #openstack-meeting-alt22:16
*** banix has quit IRC22:23
*** enikanorov has quit IRC22:27
*** enikanorov has joined #openstack-meeting-alt22:27
*** Obulpathi has quit IRC22:27
*** swat30 has quit IRC22:29
*** swat30 has joined #openstack-meeting-alt22:29
*** jtomasek has quit IRC22:30
*** NehaV has quit IRC22:31
*** sarob has quit IRC22:34
*** sarob has joined #openstack-meeting-alt22:35
*** jcoufal has quit IRC22:36
*** arnaud has quit IRC22:36
*** arnaud has joined #openstack-meeting-alt22:37
*** sarob has quit IRC22:39
*** yogesh has quit IRC22:40
*** Leonr has quit IRC22:41
*** mattgriffin has quit IRC22:41
*** Haiying has joined #openstack-meeting-alt22:42
*** IlyaE has quit IRC22:44
*** zns has quit IRC22:46
*** zns has joined #openstack-meeting-alt22:51
*** manishg has quit IRC22:51
*** walker__ has quit IRC22:54
*** ccrouch has quit IRC22:59
*** ccrouch has joined #openstack-meeting-alt23:00
*** sarob has joined #openstack-meeting-alt23:01
*** sarob has quit IRC23:01
*** david-lyle has quit IRC23:01
*** sarob has joined #openstack-meeting-alt23:01
*** atiwari has quit IRC23:03
*** IlyaE has joined #openstack-meeting-alt23:06
*** michael-yu has joined #openstack-meeting-alt23:13
*** eankutse1 has joined #openstack-meeting-alt23:14
*** eankutse has quit IRC23:14
*** bgorski has joined #openstack-meeting-alt23:16
*** gokrokve has quit IRC23:23
*** flaper87 is now known as flaper87|afk23:25
*** MarkAtwood has quit IRC23:25
*** zns has quit IRC23:32
*** jmcbride has joined #openstack-meeting-alt23:36
*** chandan_kumar has quit IRC23:37
*** mattgriffin has joined #openstack-meeting-alt23:37
*** Obulpathi has joined #openstack-meeting-alt23:40
*** jmcbride has quit IRC23:41
*** Obulpathi has quit IRC23:45
*** manishg has joined #openstack-meeting-alt23:47
*** manishg___ has joined #openstack-meeting-alt23:50
*** lblanchard has joined #openstack-meeting-alt23:52
*** ramishra has joined #openstack-meeting-alt23:52
*** manishg has quit IRC23:52
*** manishg___ is now known as manishg23:52
*** Obulpathi has joined #openstack-meeting-alt23:55
*** ramishra has quit IRC23:56
*** zaneb has joined #openstack-meeting-alt23:58
*** wirehead_ has joined #openstack-meeting-alt23:58
*** lblanchard has quit IRC23:59

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