Wednesday, 2014-05-07

*** michael-yu has joined #openstack-meeting-alt00:04
*** ativelkov_away is now known as ativelkov00:04
*** dtx00ff has joined #openstack-meeting-alt00:06
*** SumitNaiksatam has quit IRC00:08
*** jcooley has quit IRC00:08
*** ativelkov is now known as ativelkov_away00:10
*** tdruiva has quit IRC00:11
*** jcooley has joined #openstack-meeting-alt00:12
*** james_li has quit IRC00:13
*** Sukhdev has joined #openstack-meeting-alt00:14
*** dkehnx has quit IRC00:14
*** dkehnx has joined #openstack-meeting-alt00:14
*** james_li has joined #openstack-meeting-alt00:16
*** rmoe has quit IRC00:19
*** flaper87 is now known as flaper87|afk00:20
*** eankutse has joined #openstack-meeting-alt00:20
*** mattgriffin has quit IRC00:21
*** jcooley has quit IRC00:22
*** jaypipes has joined #openstack-meeting-alt00:23
*** eankutse has quit IRC00:24
*** eankutse has joined #openstack-meeting-alt00:24
*** julienvey has quit IRC00:24
*** samstav has quit IRC00:24
*** saurabhs has quit IRC00:25
*** woodster_ has joined #openstack-meeting-alt00:25
*** chuckC has quit IRC00:25
*** james_li has quit IRC00:26
*** ranjitha has quit IRC00:26
*** richm has quit IRC00:30
*** tchaypo has joined #openstack-meeting-alt00:33
*** rmoe has joined #openstack-meeting-alt00:33
*** SumitNaiksatam has joined #openstack-meeting-alt00:33
*** woodster_ has quit IRC00:34
*** ativelkov_away is now known as ativelkov00:34
*** xarses has quit IRC00:35
*** ativelkov is now known as ativelkov_away00:39
*** SumitNaiksatam has quit IRC00:39
*** ramashri has quit IRC00:41
*** yamahata has joined #openstack-meeting-alt00:42
*** eankutse has quit IRC00:45
*** tdruiva has joined #openstack-meeting-alt00:46
*** yamahata has quit IRC00:55
*** arnaud__ has quit IRC00:57
*** julienvey has joined #openstack-meeting-alt01:01
*** notmyname has quit IRC01:03
*** david-lyle has joined #openstack-meeting-alt01:03
*** ativelkov_away is now known as ativelkov01:04
*** dtx00ff has quit IRC01:04
*** julienvey has quit IRC01:05
*** notmyname has joined #openstack-meeting-alt01:06
*** amcrn has quit IRC01:08
*** ativelkov is now known as ativelkov_away01:10
*** xarses has joined #openstack-meeting-alt01:13
*** SumitNaiksatam has joined #openstack-meeting-alt01:13
*** atiwari has quit IRC01:19
*** gokrokve_ has quit IRC01:21
*** tdruiva_ has joined #openstack-meeting-alt01:25
*** tdruiva has quit IRC01:26
*** MarkAtwood has quit IRC01:29
*** ativelkov_away is now known as ativelkov01:34
*** bill_az has quit IRC01:34
*** mattgriffin has joined #openstack-meeting-alt01:36
*** oomichi has joined #openstack-meeting-alt01:38
*** ativelkov is now known as ativelkov_away01:39
*** banix has joined #openstack-meeting-alt01:40
*** mattgriffin has quit IRC01:42
*** spzala has joined #openstack-meeting-alt01:42
*** nosnos has joined #openstack-meeting-alt01:43
*** spzala has quit IRC01:48
*** sankarshan is now known as sankarshan_away01:48
*** tchaypo has left #openstack-meeting-alt01:49
*** Sukhdev_ has joined #openstack-meeting-alt01:50
*** Sukhdev has quit IRC01:50
*** xuhanp has joined #openstack-meeting-alt01:52
*** jasonb365 has joined #openstack-meeting-alt01:52
*** Sukhdev has joined #openstack-meeting-alt01:52
*** gokrokve has joined #openstack-meeting-alt01:52
*** notmyname has quit IRC01:54
*** notmyname has joined #openstack-meeting-alt01:54
*** vkmc has quit IRC01:55
*** Sukhdev_ has quit IRC01:55
*** Sukhdev has quit IRC01:56
*** zns has joined #openstack-meeting-alt01:56
*** david-lyle has quit IRC01:57
*** julienvey has joined #openstack-meeting-alt02:02
*** baoli has joined #openstack-meeting-alt02:04
*** morganfainberg is now known as morganfainberg_Z02:04
*** ativelkov_away is now known as ativelkov02:04
*** michael-yu has quit IRC02:04
*** julienvey has quit IRC02:07
*** michael-yu has joined #openstack-meeting-alt02:09
*** ativelkov is now known as ativelkov_away02:10
*** mberlin1 has joined #openstack-meeting-alt02:13
*** mberlin has quit IRC02:13
*** zns has quit IRC02:14
*** flwang has quit IRC02:19
*** banix has quit IRC02:27
*** zns has joined #openstack-meeting-alt02:27
*** banix has joined #openstack-meeting-alt02:27
*** baoli has quit IRC02:28
*** markwash has quit IRC02:33
*** IlyaE has quit IRC02:34
*** ativelkov_away is now known as ativelkov02:34
*** sankarshan_away is now known as sankarshan02:37
*** ativelkov is now known as ativelkov_away02:39
*** marun has joined #openstack-meeting-alt02:39
*** gokrokve_ has joined #openstack-meeting-alt02:41
*** IlyaE has joined #openstack-meeting-alt02:43
*** gokrokve has quit IRC02:44
*** akuznetsov has joined #openstack-meeting-alt02:50
*** harlowja is now known as harlowja_away02:50
*** baoli has joined #openstack-meeting-alt02:51
*** flwang has joined #openstack-meeting-alt02:51
*** yamahata has joined #openstack-meeting-alt02:52
*** zhiyan_ is now known as zhiyan02:53
*** resker has joined #openstack-meeting-alt02:56
*** resker has quit IRC02:56
*** harlowja_away has quit IRC02:58
*** esker has quit IRC02:59
*** julienvey has joined #openstack-meeting-alt03:02
*** ramishra has joined #openstack-meeting-alt03:03
*** clarkb has quit IRC03:03
*** flwang has quit IRC03:03
*** clarkb has joined #openstack-meeting-alt03:04
*** ativelkov_away is now known as ativelkov03:04
*** IlyaE has quit IRC03:05
*** flwang has joined #openstack-meeting-alt03:05
*** tdruiva_ has quit IRC03:07
*** julienvey has quit IRC03:07
*** ativelkov is now known as ativelkov_away03:10
*** amotoki has quit IRC03:14
*** zns has quit IRC03:15
*** bltavares|away has quit IRC03:15
*** james_li has joined #openstack-meeting-alt03:16
*** zns has joined #openstack-meeting-alt03:18
*** zz_gondoi is now known as gondoi03:18
*** Sukhdev has joined #openstack-meeting-alt03:21
*** Sukhdev has quit IRC03:21
*** banix has quit IRC03:21
*** Sukhdev has joined #openstack-meeting-alt03:21
*** MarkAtwood has joined #openstack-meeting-alt03:27
*** james_li has quit IRC03:27
*** zns has quit IRC03:28
*** dims has quit IRC03:30
*** chuckC has joined #openstack-meeting-alt03:30
*** marun has quit IRC03:31
*** zns has joined #openstack-meeting-alt03:33
*** gyee has quit IRC03:34
*** coolsvap|afk is now known as coolsvap03:34
*** ativelkov_away is now known as ativelkov03:34
*** michael-yu has joined #openstack-meeting-alt03:38
*** michael-yu has quit IRC03:38
*** ativelkov is now known as ativelkov_away03:39
*** nosnos has quit IRC03:43
*** catohornet has quit IRC03:44
*** marun has joined #openstack-meeting-alt03:55
*** amotoki has joined #openstack-meeting-alt03:56
*** gondoi is now known as zz_gondoi03:59
*** julienvey has joined #openstack-meeting-alt04:03
*** ativelkov_away is now known as ativelkov04:04
*** sankarshan is now known as sankarshan_away04:06
*** james_li has joined #openstack-meeting-alt04:06
*** julienvey has quit IRC04:07
*** baoli has quit IRC04:08
*** akuznetsov has quit IRC04:08
*** james_li_ has joined #openstack-meeting-alt04:08
*** ativelkov is now known as ativelkov_away04:10
*** james_li has quit IRC04:10
*** james_li_ is now known as james_li04:10
*** michael-yu has joined #openstack-meeting-alt04:12
*** tdruiva has joined #openstack-meeting-alt04:14
*** flwang has quit IRC04:14
*** flwang has joined #openstack-meeting-alt04:18
*** caleb_ has quit IRC04:18
*** michael-yu has quit IRC04:21
*** jasonb365 has quit IRC04:24
*** ramishra has quit IRC04:24
*** ramishra has joined #openstack-meeting-alt04:27
*** ramashri has joined #openstack-meeting-alt04:27
*** rbrady has quit IRC04:29
*** yamamoto_ has joined #openstack-meeting-alt04:30
*** ativelkov_away is now known as ativelkov04:34
*** ativelkov is now known as ativelkov_away04:39
*** rbrady has joined #openstack-meeting-alt04:42
*** ramashri has quit IRC04:44
*** catohornet has joined #openstack-meeting-alt04:44
*** akuznetsov has joined #openstack-meeting-alt04:44
*** jasonb365 has joined #openstack-meeting-alt04:46
*** yogeshmehra has joined #openstack-meeting-alt04:49
*** chandan_kumar has joined #openstack-meeting-alt04:50
*** nosnos has joined #openstack-meeting-alt04:51
*** michael-yu has joined #openstack-meeting-alt04:51
*** sankarshan_away is now known as sankarshan04:54
*** arnaud__ has joined #openstack-meeting-alt05:01
*** julienvey has joined #openstack-meeting-alt05:04
*** ativelkov_away is now known as ativelkov05:04
*** julienvey has quit IRC05:08
*** Michalik_ has joined #openstack-meeting-alt05:10
*** ativelkov is now known as ativelkov_away05:10
*** james_li has quit IRC05:17
*** arnaud__ has quit IRC05:19
*** Sukhdev has quit IRC05:21
*** IlyaE has joined #openstack-meeting-alt05:22
*** arnaud__ has joined #openstack-meeting-alt05:24
*** arnaud__ has joined #openstack-meeting-alt05:24
*** IlyaE has quit IRC05:31
*** jcoufal has joined #openstack-meeting-alt05:33
*** ativelkov_away is now known as ativelkov05:34
*** dshulyak_ has joined #openstack-meeting-alt05:37
*** ativelkov is now known as ativelkov_away05:39
*** dshulyak_ has quit IRC05:42
*** igormarnat_ has joined #openstack-meeting-alt05:43
*** yogeshmehra has quit IRC05:45
*** yogeshmehra has joined #openstack-meeting-alt05:46
*** yogeshmehra has quit IRC05:50
*** eghobo has joined #openstack-meeting-alt05:53
*** eghobo has quit IRC05:54
*** eghobo has joined #openstack-meeting-alt05:54
*** yogeshmehra has joined #openstack-meeting-alt05:54
*** dtx00ff has joined #openstack-meeting-alt05:56
*** dtx00ff has quit IRC05:57
*** dtx00ff has joined #openstack-meeting-alt06:01
*** ativelkov_away is now known as ativelkov06:04
*** julienvey has joined #openstack-meeting-alt06:05
*** lukego has joined #openstack-meeting-alt06:09
*** julienvey has quit IRC06:09
*** ativelkov is now known as ativelkov_away06:10
*** SushillKM has joined #openstack-meeting-alt06:13
*** SushillKM has left #openstack-meeting-alt06:13
*** dkehn_ has joined #openstack-meeting-alt06:25
*** dkehnx has quit IRC06:29
*** ativelkov_away is now known as ativelkov06:32
*** zns has quit IRC06:32
*** dtx00ff has quit IRC06:32
*** IlyaE has joined #openstack-meeting-alt06:32
*** igormarnat_ has quit IRC06:36
*** ativelkov is now known as ativelkov_away06:39
*** dtx00ff has joined #openstack-meeting-alt06:40
*** IlyaE has quit IRC06:40
*** _nadya_ has joined #openstack-meeting-alt06:41
*** igormarnat_ has joined #openstack-meeting-alt06:41
*** lukego has quit IRC06:43
*** igormarnat_ has quit IRC06:47
*** _nadya_ has quit IRC06:47
*** _nadya_ has joined #openstack-meeting-alt06:49
*** yamamoto_ has quit IRC06:50
*** matrohon has joined #openstack-meeting-alt06:54
*** ramishra has quit IRC06:57
*** jcoufal has quit IRC07:00
*** ativelkov_away is now known as ativelkov07:04
*** eghobo has quit IRC07:04
*** julienvey has joined #openstack-meeting-alt07:08
*** lsmola has joined #openstack-meeting-alt07:09
*** ativelkov is now known as ativelkov_away07:10
*** lukego has joined #openstack-meeting-alt07:10
*** igormarnat_ has joined #openstack-meeting-alt07:11
*** tnurlygayanov has quit IRC07:11
*** julienvey has quit IRC07:12
*** tnurlygayanov has joined #openstack-meeting-alt07:14
*** tdruiva has quit IRC07:16
*** lsmola2 has joined #openstack-meeting-alt07:17
*** flaper87|afk is now known as flaper8707:18
*** julienvey has joined #openstack-meeting-alt07:18
*** igormarnat_ has quit IRC07:18
*** ramishra has joined #openstack-meeting-alt07:20
*** arnaud__ has quit IRC07:25
*** zhiyan is now known as zhiyan_07:26
*** lsmola2 has quit IRC07:27
*** ativelkov_away is now known as ativelkov07:32
*** ramishra has quit IRC07:33
*** artem_panchenko has joined #openstack-meeting-alt07:33
*** artem_panchenko has left #openstack-meeting-alt07:34
*** igormarnat_ has joined #openstack-meeting-alt07:35
*** jcoufal has joined #openstack-meeting-alt07:37
*** ativelkov is now known as ativelkov_away07:39
*** igormarnat_ has quit IRC07:41
*** igormarnat_ has joined #openstack-meeting-alt07:48
*** michael-yu has quit IRC07:51
*** sergmelikyan has joined #openstack-meeting-alt07:53
*** safchain has joined #openstack-meeting-alt07:54
*** ramishra has joined #openstack-meeting-alt07:54
*** yogeshmehra has quit IRC07:56
*** yogeshmehra has joined #openstack-meeting-alt07:56
*** yogeshme_ has joined #openstack-meeting-alt08:00
*** yogeshmehra has quit IRC08:00
*** ativelkov_away is now known as ativelkov08:04
*** ramishra has quit IRC08:05
*** ativelkov is now known as ativelkov_away08:10
*** nacim has joined #openstack-meeting-alt08:11
*** jasonb365 has quit IRC08:12
*** ramishra has joined #openstack-meeting-alt08:14
*** igormarnat_ has quit IRC08:19
*** derekh_ has joined #openstack-meeting-alt08:20
*** igormarnat_ has joined #openstack-meeting-alt08:23
*** zhangleiqiang has joined #openstack-meeting-alt08:23
*** arnaud__ has joined #openstack-meeting-alt08:26
*** arnaud__ has quit IRC08:30
*** ativelkov_away is now known as ativelkov08:34
*** jamie_h has joined #openstack-meeting-alt08:35
*** dtx00ff has quit IRC08:35
*** dtx00ff has joined #openstack-meeting-alt08:35
*** zhangleiqiang has quit IRC08:36
*** dtx00ff has quit IRC08:40
*** igormarnat_ has quit IRC08:47
*** nacim has quit IRC08:54
*** andreaf has joined #openstack-meeting-alt08:58
*** nacim has joined #openstack-meeting-alt09:07
* iyozhikov is now away: went away...09:09
*** igormarnat_ has joined #openstack-meeting-alt09:15
*** chandan_kumar has quit IRC09:17
*** yogeshme_ has quit IRC09:20
*** igormarnat_ has quit IRC09:20
*** overlayer has joined #openstack-meeting-alt09:23
*** chandan_kumar has joined #openstack-meeting-alt09:23
*** coolsvap is now known as coolsvap|afk09:30
*** xuhanp has quit IRC09:32
*** flwang has quit IRC09:36
*** jgallard has joined #openstack-meeting-alt09:45
*** chandan_kumar has quit IRC09:46
*** dmakogon_ is now known as denis_makogon09:46
*** gokrokve_ has quit IRC09:50
*** gokrokve has joined #openstack-meeting-alt09:50
*** gokrokve has quit IRC09:50
*** _nadya_ has quit IRC09:56
*** coolsvap|afk is now known as coolsvap09:58
*** chandan_kumar has joined #openstack-meeting-alt10:00
*** overlayer has quit IRC10:04
*** ativelkov is now known as ativelkov_away10:05
*** ativelkov_away is now known as ativelkov10:05
*** safchain has quit IRC10:08
*** dims has joined #openstack-meeting-alt10:10
*** dims has quit IRC10:10
*** dims has joined #openstack-meeting-alt10:10
*** ativelkov is now known as ativelkov_away10:10
*** overlayer has joined #openstack-meeting-alt10:11
*** jgallard has quit IRC10:17
*** ativelkov_away is now known as ativelkov10:18
*** ramishra has quit IRC10:20
*** ramishra has joined #openstack-meeting-alt10:20
*** ramishra has quit IRC10:21
*** ramishra has joined #openstack-meeting-alt10:21
*** ramishra has quit IRC10:22
*** igormarnat_ has joined #openstack-meeting-alt10:24
*** gokrokve has joined #openstack-meeting-alt10:38
*** gokrokve has quit IRC10:43
*** yamahata has quit IRC10:43
*** overlayer has quit IRC10:47
*** vkmc has joined #openstack-meeting-alt10:47
*** overlayer has joined #openstack-meeting-alt10:48
*** jjmb has joined #openstack-meeting-alt10:50
*** overlayer has quit IRC10:53
*** overlayer has joined #openstack-meeting-alt10:53
*** coolsvap is now known as coolsvap|afk10:54
*** jcoufal has quit IRC10:54
*** jcoufal has joined #openstack-meeting-alt10:56
*** overlayer_ has joined #openstack-meeting-alt11:00
*** overlayer has quit IRC11:01
*** dims has quit IRC11:11
*** overlayer_ has quit IRC11:13
*** nacim has quit IRC11:16
*** igormarnat_ has quit IRC11:18
*** tdruiva has joined #openstack-meeting-alt11:29
*** igormarnat_ has joined #openstack-meeting-alt11:31
*** tdruiva_ has joined #openstack-meeting-alt11:35
*** tdruiva has quit IRC11:37
*** gokrokve has joined #openstack-meeting-alt11:37
*** gokrokve has quit IRC11:42
*** tdruiva_ has quit IRC11:44
*** sankarshan is now known as sankarshan_away11:46
*** tdruiva has joined #openstack-meeting-alt11:47
*** flaper87 is now known as flaper87|afk11:56
*** flaper87|afk is now known as flaper8711:57
*** amotoki has quit IRC11:59
*** irenab has joined #openstack-meeting-alt12:01
*** overlayer has joined #openstack-meeting-alt12:01
*** shanks has joined #openstack-meeting-alt12:03
*** shanks has quit IRC12:03
*** shanks has joined #openstack-meeting-alt12:03
*** baoli has joined #openstack-meeting-alt12:03
*** eddie_ has quit IRC12:05
*** d0ugal_ has joined #openstack-meeting-alt12:06
*** lukego has quit IRC12:08
*** d0ugal_ has quit IRC12:09
*** lukego has joined #openstack-meeting-alt12:09
*** mwagner_ has quit IRC12:09
*** pdmars has joined #openstack-meeting-alt12:18
*** dkehn_ is now known as dkehnx12:18
*** pdmars has quit IRC12:20
*** dprince has joined #openstack-meeting-alt12:22
*** yamahata has joined #openstack-meeting-alt12:28
*** pdmars has joined #openstack-meeting-alt12:28
*** yamahata has quit IRC12:33
*** tdruiva has quit IRC12:37
*** jdob has joined #openstack-meeting-alt12:37
*** gokrokve has joined #openstack-meeting-alt12:38
*** dprince has quit IRC12:38
*** markvoelker1 has joined #openstack-meeting-alt12:38
*** sankarshan_away is now known as sankarshan12:39
*** woodster_ has joined #openstack-meeting-alt12:39
*** flwang has joined #openstack-meeting-alt12:40
*** gokrokve has quit IRC12:42
*** jjmb has quit IRC12:46
*** beagles has joined #openstack-meeting-alt12:47
*** banix has joined #openstack-meeting-alt12:50
*** nosnos has quit IRC12:53
*** nacim has joined #openstack-meeting-alt12:54
*** jgallard has joined #openstack-meeting-alt12:54
*** nickchase has joined #openstack-meeting-alt12:58
*** baoli has quit IRC12:59
*** baoli has joined #openstack-meeting-alt12:59
*** banix has quit IRC13:00
baoli#startmeeting PCI passthrough13:00
openstackMeeting started Wed May  7 13:00:28 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: PCI passthrough)"13:00
beagleso/13:00
openstackThe meeting name has been set to 'pci_passthrough'13:00
baolihi13:00
irenabhi13:01
johnthetubaguyhi13:01
baoliJohn, welcome13:02
irenabHi John!13:02
* johnthetubaguy waves13:02
-openstackstatus- NOTICE: Zuul is stuck due to earlier networking issues with Gerrit server, work in progress.13:02
*** ChanServ changes topic to "Zuul is stuck due to earlier networking issues with Gerrit server, work in progress."13:02
baoliWhat do you guys want to go over for this last meeting before the summit?13:02
*** sadasu has joined #openstack-meeting-alt13:03
*** eddie_ has joined #openstack-meeting-alt13:03
johnthetubaguyis everything ready for summit session? etherpad all prepared?13:03
irenabI think we need to be sure that all topics we want to discuss are on the etherpad13:03
johnthetubaguyyou got the link?13:04
baoliirenab did a good job on the etherpad13:04
baolihttps://etherpad.openstack.org/p/pci_passthrough_cross_project13:04
irenabDo we want to set a time for meeting before the session? Monday morning or other day during key notes?13:04
sadasubaoli: did you startmeeting?13:05
baolisadasu, yes13:05
irenabI would like to discuss the scope for the nova-spec we are currently blocked with -213:05
sadasutopic hasn't changed for me13:05
irenabsadasu: there was some automatic zuul announcment that messed the topic13:06
sadasuok...got it13:06
johnthetubaguyso on the etherpad… did you want to give a description of the problems you are trying to solve?13:07
*** woodster_ has quit IRC13:07
johnthetubaguyand agree on those13:07
sadasuback to nova pec13:07
johnthetubaguyit seems to dive into the details quite a lot13:07
*** coolsvap|afk is now known as coolsvap13:07
irenabshall we start with naive case were all VM vnics are SRIOV is VM flavor defines so?13:08
johnthetubaguywell, just all nics are SRIOV would do13:08
irenab^if defines so13:08
sadasualso, I think it has been proven that the choice of nic_type sriov and macvtap isn't working13:08
*** julim has joined #openstack-meeting-alt13:08
johnthetubaguythen look at flow between nova and neutron13:08
sadasuthe nova spec comments clearly asks for a level of indirection where we use diff terms to identify vnic_types13:09
irenabsadasu: currentl with pre created neutron port, I can create VMs with both SR-IOV and OVS based vNICs, which is quite cool13:09
johnthetubaguyyeah, but I am not sure we agree the basics yet13:09
*** enikanorov_ has joined #openstack-meeting-alt13:10
irenabjohn: this is works without changing nova apis13:10
baoliJohn, what basics in your mind that we should discuss on?13:11
irenabI think to make some progress, we can srtart with the basic case that per VM all vnics can be either SR-IOV or non SR-IOV13:11
*** ChanServ changes topic to "(Meeting topic: PCI passthrough)"13:11
-openstackstatus- NOTICE: Zuul is processing changes now; some results were lost. Use "recheck bug 1317089" if needed.13:11
johnthetubaguybaoli: I am thinking just the basic SRIOV use case of all nics are SRIOV13:11
johnthetubaguynova and neutron interaction specifying whats going on, etc13:12
johnthetubaguyhow nova picks the correct host with the request network the user wants, etc13:12
baolijohn, in that case, all we need to do is to remove the user CLI change, and add a config to say all nics are SRIOV or not13:13
baoliall the other changes would remain the same.13:13
irenabjohn: agree with baoli, seems that setting it on VM flavor layer can work here13:13
*** tdruiva has joined #openstack-meeting-alt13:13
baoliirenab, I think john is talking all sriov across a cloud13:14
johnthetubaguyyeah13:14
johnthetubaguyacross the whole cloud13:14
johnthetubaguythen lets look at the next options13:14
johnthetubaguywe already have to pick the correct network, as requested by the user, etc13:14
irenabI do not lkie this case so much, too limiting. Why not do it per VM?13:14
baolijohn, like I responded in the comments, even picking up the right network is not specific to SR-IOV13:15
*** abettadapur_ has joined #openstack-meeting-alt13:15
beaglesthe idea.. correct me if I am wrong... is that provides a simplified case in which we can work out the details of nova/neutron coordination, implement the vif driver level details etc, and focus on the user-facing details as an independent aspect13:15
sadasuirenab: agree with you...but lets use this use case to completely figure out the part where Nova picks the correct physical network...13:15
johnthetubaguybaoli: OK, but usually all networks are available everywhere, if you use virtual networking13:15
johnthetubaguybaoli: SRIOV is very much more restrictive13:15
*** zhangleiqiang has joined #openstack-meeting-alt13:16
johnthetubaguybaoli: we can scope that out if we want, assume all networks are everywhere, but that feels wrong13:16
*** ameade has joined #openstack-meeting-alt13:16
sadasujohnthetubaguy: yes because of its dependency on physical network connectivity13:16
baolijohn, so can we assume that all the networks are avaialble on all the hosts?13:17
irenabjohn: except for limited number of VFs, I do not see major limitations compared to virtual networking. For virtual networking, Host should be connected to appropriate physicalnetwork13:17
sadasujohnthe tubaguy: then we are essentially describing the virtual port case13:17
irenabwith ML2 plugin, port won't be bound if host is not connected to physical network13:18
johnthetubaguywell its the limited number of VFs I was worried about, its a consumable port13:18
johnthetubaguyyeah, we have to co to the correct host though, I thought, but anyway, clearly this is not a useful discussion13:18
johnthetubaguylets move to something else13:18
*** eankutse has joined #openstack-meeting-alt13:19
irenabI feel we are stuck till we agree on basic case to cover13:19
johnthetubaguyyeah13:19
johnthetubaguyI am thinking the simple case should be all NICs are SRIOV13:19
irenabshall we start with HPC like cloud => all vnics are SR-IOV?13:19
sadasuI think we are all willing to start with a admin specified setting for vnic_type that applies to the entire cloud13:19
irenabbut still, I think it is not real world case13:20
*** eankutse1 has joined #openstack-meeting-alt13:20
sadasuirenab: agreed...starting point13:20
*** tdruiva has quit IRC13:20
*** eankutse has quit IRC13:20
*** zns has joined #openstack-meeting-alt13:20
johnthetubaguyso I added 4 use cases on the bottom of the etherpad13:21
*** yogeshmehra has joined #openstack-meeting-alt13:21
johnthetubaguydo they look "correct"?13:21
*** zhangleiqiang has quit IRC13:21
irenabjohn: looks ok for me13:24
johnthetubaguy?13:24
sadasudidn't quite get #313:24
johnthetubaguywondering if I missed a case13:24
johnthetubaguysadasu: is that better?13:25
irenabfor #1, if the only mechanism driver in ML2 plugin is SR-IOV, this will be resolved by neutron13:25
baoliJohn, regarding case 2, how do you define slow versue fast?13:25
sadasujohnthetubaguy: what about the case where a VM wants a virtual and Sr-iov port for the same VM13:25
sadasu...diff from the bonded case13:25
irenabsadasu: +113:26
*** yogeshmehra has quit IRC13:26
johnthetubaguysorry, 2 was not clear13:26
johnthetubaguythat is the SRIOV and virtual on the same server13:26
irenabjohn: probaly #3 is not required, it maybe temporary solution till api is converged13:26
johnthetubaguyirenab: I agree, but I wanted to raise it, so we reject it13:27
sadasuabout #3, I think we could potentially end up with lots of flavors...knobs are physical network, # sriov ports, type of sriov ports, # of virtual port13:27
sadasumight be confusing to the user13:28
johnthetubaguysadasu: agreed, its stupid, but we need to discuss it to exclude it13:28
sadasuok....got it :-)13:28
johnthetubaguyit seems like the "obvious" way to do this, till you think about the details13:28
baolijohn, for case 2, if it's one to one mapping, why use another level of indirection?13:28
johnthetubaguybaoli: because the user shouldn't know about the implementation13:29
irenabso the main question is what details we want tenant to be exposed to?13:29
johnthetubaguyand you might want three types13:29
baolithen why not choose the right term in the first place?13:29
johnthetubaguybaoli: I don't get your point?13:29
johnthetubaguywhat term would you prefer?13:30
baoliif it's one to one mapping: slow - virtual, fast - sriov,13:30
*** samstav has joined #openstack-meeting-alt13:30
irenabjohn: maybe you can sync us with your vision for volume type like approach?13:30
johnthetubaguybasically, the user gets to choose between some set of labels for the different types13:31
johnthetubaguythe admin gets to choose what that really means13:31
johnthetubaguyso it could be, virtual, 1Gb SRIOV, 10Gb SRIOV13:31
baolijohn, in our case, the user wants to choose sriov versus non-sriov ports13:31
*** eankutse has joined #openstack-meeting-alt13:31
johnthetubaguybaoli: OK, but the user being so "savvy" shouldn't be the assumed case I think13:32
*** caleb_ has joined #openstack-meeting-alt13:32
baolijohn, like I responded in the spec's comments, 1G versus 10G is not specific to SR-IOV13:32
irenabDo you suggest admin creates nic types defined with some lable exposed to tenant?13:32
johnthetubaguywe spoke before about many other users for that indirection, it seems a shame not to add it13:32
johnthetubaguyirenab: basically, yes13:32
*** eankutse1 has quit IRC13:32
*** mestery has quit IRC13:33
irenabother details that should be used for scheduling is associated by admin but not exposed to the tenant?13:33
johnthetubaguyright13:33
baoliI think that we should consider what we need to solve specifically for SR-IOV networking, not to be confused with some general issues (or functionationlities)13:33
*** zz_gondoi is now known as gondoi13:33
johnthetubaguyso you could have two different vendors of things, all under and single label, if we wanted to do that, without changing the end user API13:33
johnthetubaguybaoli: this API will live for ever once we add it, we have to get that right13:34
baolijohn, agreed on that.13:34
baolijohn, does the admin care about choosing vendors?13:34
*** balajiiyer has joined #openstack-meeting-alt13:35
baoliJohn, or even normal user cares about choosing vendors when using sr-iov technology13:35
irenabbaoli: it may be reasonable if different vendors can be part of the same deployment13:35
baolido we talk about vendors when using non-sriov networking13:35
johnthetubaguywell, its more the ability not to choose that worries me, but I think we are crossed wires here13:35
*** gondoi is now known as zz_gondoi13:35
johnthetubaguylets roll back a little bit13:36
*** jecarey has quit IRC13:36
johnthetubaguydo we agree with the use cases as they are now? (ignoring how we implement them)13:36
johnthetubaguythey seem valid13:36
*** caleb_ has quit IRC13:36
*** balajiiyer has left #openstack-meeting-alt13:36
johnthetubaguyah, wait, I remember13:37
johnthetubaguyits the macvtap vs direct vs virtual13:37
*** overlayer has quit IRC13:37
*** caleb_ has joined #openstack-meeting-alt13:37
johnthetubaguythat is an admin choice I feel13:37
johnthetubaguymacvtap vs direct13:37
johnthetubaguythe user wants "slow" vs "fast", in their view of the world13:38
*** overlayer has joined #openstack-meeting-alt13:38
johnthetubaguyunless they happen to know how hypervisors, work13:38
johnthetubaguyin which case you just change the labels to "SRIOV" vs "Virtual"13:38
*** gokrokve has joined #openstack-meeting-alt13:38
baolijohn, do we assume that all three types can coexist in the same cloud?13:39
irenabjohn: so to start with #2, nic type with single key holding vnic_type will be enough?13:39
irenabbaoli: I think they may coexist in the same VM13:39
johnthetubaguyyeah, same VM13:40
*** dprince has joined #openstack-meeting-alt13:40
johnthetubaguyirenab: yeah, I think vnic_type just being a string passed to Nova, might do the trick13:40
*** tdruiva has joined #openstack-meeting-alt13:40
johnthetubaguyirenab: ideally needs to be scoped, etc, but yeah, thats all13:40
*** sergmelikyan has quit IRC13:40
*** sergmelikyan has joined #openstack-meeting-alt13:41
irenabcase #1 is actually equivalent to monolitic neutron SR-IOV plugin case (pre ML2 plugin)13:41
*** safchain has joined #openstack-meeting-alt13:41
*** krtaylor_ has joined #openstack-meeting-alt13:41
*** krtaylor_ has quit IRC13:42
*** tdruiva has quit IRC13:42
*** krtaylor has quit IRC13:42
irenabjohn: just to understand what you have in mind, do you cuggest new model object "nic type" or vnic_type as parameter of --nic?13:42
irenab^suggest13:42
johnthetubaguyirenab: right, or ML2 configured with a single type13:42
*** flwang has quit IRC13:42
*** gokrokve has quit IRC13:43
johnthetubaguyirenab: I don't know, I think vnic_type param would do the trick13:43
*** Obulpathi has joined #openstack-meeting-alt13:43
johnthetubaguyirenab: I worry more about expressing what the user wants at this point13:43
johnthetubaguyirenab: and making sure we capture the "problem" we want to solve13:43
baolijohn, if we want to add other information such as vendor, port bandwidth, etc, another level of indirection may make sense. However, same thing would apply to non-sriov ports as well.13:44
johnthetubaguybaoli: yes, it probably does, this is just one use of it13:45
baolijohn, if we agree with that, then we should have a common solution for both sriov and non-sriov ports for those13:45
irenabseems to me that currently we have an option to request vnic_type via neutron port passed to nova boot command.13:46
johnthetubaguyyeah, probably, I don't totally get the other use cases13:46
baolithen what's unique to sriov is the number of VFs.13:46
*** thangp has joined #openstack-meeting-alt13:46
*** amytron has joined #openstack-meeting-alt13:46
baoliAnd if we don't care about mis-scheuling, the number doesn't matter13:46
irenabfor proper way to request vnic_type via nova api, we probably need 'nic type'13:47
baoliI mean the limited number of VFs doesn't matter13:47
johnthetubaguyOK...13:49
johnthetubaguyso I added another use case13:49
johnthetubaguyas #313:49
johnthetubaguyI think that relates quite a lot to the ML2 case13:49
johnthetubaguyhow does it look?13:49
*** krtaylor has joined #openstack-meeting-alt13:52
irenabI am not comfortable with admin decides per network what vnic user gets, it may serve as default  if tenant does not specify13:53
baoliI actually don't quite understand 3 & 413:53
johnthetubaguyso #3, as it is now13:54
johnthetubaguyuser picks there networks as they do today13:54
*** mwagner_ has joined #openstack-meeting-alt13:54
johnthetubaguybut admin gets to pick that public network is SRIOV, vs all private networks are implemented using OVS, say13:55
baolijohn, that sounds good to me13:55
sadasuwe have 5 mins, can we quickly decided when to meet during the summit?13:55
sadasuMonday?13:55
beaglesjohnthetubaguy, just spitballing, but you are conceptualizing a progression of functionality (ie. a way we can incrementally implement things) or a use case that will be supported "forever"?13:55
johnthetubaguy#4, user picks between medium.SRIOVnet vs medium.regularNET13:55
beagless/you are/are you/13:55
irenabMonday works for me13:56
johnthetubaguyI fear I would be tied up all Monday13:56
*** betsy has quit IRC13:56
irenabTue during keynotes?13:56
sadasujohnthetubaguy: what would be a good time for you?13:57
sadasuand beagles?13:57
*** kevinconway has joined #openstack-meeting-alt13:57
johnthetubaguysadasu: there probably isn't one I am afraid13:57
*** flwang has joined #openstack-meeting-alt13:57
sadasulunch time?13:58
johnthetubaguybeagles: i was hoping to agree something of the end goal, so we can see how to step towards that13:58
johnthetubaguybeagles: so the hope is for both13:58
beaglesjohnthetubaguy, cool13:58
irenabit would be good to set expectations from the summit session: scope and work items assigment, right?13:58
johnthetubaguyirenab: agreeing the problems we want to solve would be good, so scope yes13:59
johnthetubaguyI really want to see things move forward in Juno, this is the chance really13:59
*** Obulpathi has quit IRC13:59
irenabsadasu: lunch time will work for me13:59
sadasujohnthetubaguy: +113:59
baolijohn, I think that we all share the same goal13:59
*** nickchase has left #openstack-meeting-alt14:00
sadasuI was really hoping to have some whiteboard/unconference type session14:00
irenabsadasu: +114:00
*** igormarnat_ has quit IRC14:00
*** overlayer has quit IRC14:00
irenablet's try to converge on meeting time before the session over ml?14:00
sadasuagreed.14:01
baolisounds good to me14:01
johnthetubaguylooking forward to the session, anyways, will be good to hash this out in person14:01
sadasu+114:01
baoliI guess that we'll see each other in the summit then14:02
irenabsadasu: can you please send out an email?14:02
sadasuok...I am afraid it will just be the usual culprits (3 of us) responding :-)14:02
irenabthanks all! I I need to go, see you in the summit14:03
baolithanks everyone14:03
baoli#endmeeting14:03
*** openstack changes topic to "(Meeting topic: training-manuals)"14:03
openstackMeeting ended Wed May  7 14:03:45 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-05-07-13.00.html14:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-05-07-13.00.txt14:03
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-05-07-13.00.log.html14:03
sadasuthanks for the use cases everyone14:04
*** gokrokve has joined #openstack-meeting-alt14:04
*** igormarnat_ has joined #openstack-meeting-alt14:05
*** markmcclain has joined #openstack-meeting-alt14:05
*** irenab has quit IRC14:06
*** jjmb has joined #openstack-meeting-alt14:06
*** markmcclain1 has joined #openstack-meeting-alt14:08
*** Michalik_ has quit IRC14:10
*** markmcclain has quit IRC14:10
*** sadasu has quit IRC14:10
*** jjmb has quit IRC14:10
*** bnemec has quit IRC14:15
*** bnemec has joined #openstack-meeting-alt14:15
*** shakamunyi has joined #openstack-meeting-alt14:16
*** ativelkov is now known as ativelkov_away14:16
*** ativelkov_away is now known as ativelkov14:17
*** beagles is now known as beagles_brb14:18
*** ativelkov is now known as ativelkov_away14:19
*** ativelkov_away is now known as ativelkov14:20
*** rueb7363 has joined #openstack-meeting-alt14:20
*** esker has joined #openstack-meeting-alt14:21
*** abettadapur_ has quit IRC14:23
*** julienvey has quit IRC14:23
*** ativelkov is now known as ativelkov_away14:25
*** dims has joined #openstack-meeting-alt14:25
*** rueb7363 has quit IRC14:26
*** matrohon has quit IRC14:27
*** rueb7363 has joined #openstack-meeting-alt14:28
*** megan_w|afk is now known as megan_w14:32
*** abettadapur_ has joined #openstack-meeting-alt14:32
*** d0ugal has quit IRC14:34
*** esker has quit IRC14:38
*** zz_gondoi is now known as gondoi14:38
*** mberlin1 has quit IRC14:40
*** iyozhikov is now known as IgorYozhikov14:40
*** abettadapur_ has quit IRC14:43
*** d0ugal has joined #openstack-meeting-alt14:47
*** d0ugal has quit IRC14:47
*** d0ugal has joined #openstack-meeting-alt14:47
*** rueb7363 has quit IRC14:50
*** cjellick has quit IRC14:53
*** mberlin has joined #openstack-meeting-alt14:54
*** xuhanp has joined #openstack-meeting-alt14:54
*** abettadapur_ has joined #openstack-meeting-alt14:55
*** xuhanp has quit IRC14:55
*** caleb_ has quit IRC14:57
*** xuhanp has joined #openstack-meeting-alt14:57
*** Swami has joined #openstack-meeting-alt14:57
*** jecarey has joined #openstack-meeting-alt14:58
*** IlyaE has joined #openstack-meeting-alt14:58
*** cjellick has joined #openstack-meeting-alt14:58
*** oomichi has quit IRC14:59
*** ramishra has joined #openstack-meeting-alt14:59
*** mrsmith has joined #openstack-meeting-alt15:00
Swamihi15:00
mrsmithSwami: howdy15:00
Swamimrsmith: hi15:00
*** ativelkov_away is now known as ativelkov15:00
xuhanphello15:00
Swamixuhanp: hi15:01
*** ativelkov is now known as ativelkov_away15:01
*** ativelkov_away is now known as ativelkov15:01
Swami#startmeeting distributed_virtual_router15:02
openstackMeeting started Wed May  7 15:02:08 2014 UTC and is due to finish in 60 minutes.  The chair is Swami. Information about MeetBot at http://wiki.debian.org/MeetBot.15: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
Swami#topic Agenda15:02
*** openstack changes topic to "Agenda (Meeting topic: distributed_virtual_router)"15:02
Swami1. DVR Update15:02
Swami2. Altanta Summit Planning15:03
SwamiI do have only two topics today for discussion, if you have any other topic that you wanted to discuss please let me know.15:03
Swamixuhanp: Do you have any topic that you wanted to discuss15:04
xuhanpSwami, nope, just want to let you know I replied your question about SQL15:04
xuhanp:D15:04
*** carl_baldwin has joined #openstack-meeting-alt15:04
Swamixuhanp: Yes I got your message, but I did not try it out, I will try it out and let you know.15:04
Swamicarl_baldwin: hi15:05
xuhanpsounds great.15:05
carl_baldwinSwami: hi15:05
Swamixuhanp: are you planning to attend the Atlanta summit15:05
xuhanpSwami, unfortunately I won't15:06
*** pcm_ has joined #openstack-meeting-alt15:06
*** sbalukoff has quit IRC15:06
Swamixuhanp: Just checking. thanks.15:06
xuhanpbut I will try to catch what you guys have discussed15:06
Swami1. DVR Update15:06
*** cjellick has quit IRC15:07
*** pcm_ has quit IRC15:07
SwamiOn the plugin side, we are doing some refactoring and also finishing up the SNAT part.15:07
*** cjellick has joined #openstack-meeting-alt15:07
*** pcm_ has joined #openstack-meeting-alt15:08
*** banix has joined #openstack-meeting-alt15:08
Swamipcm_:hi15:08
Swamibanix; hi15:08
*** rueb7363 has joined #openstack-meeting-alt15:08
banixSwami: hi15:08
SwamiI had one comment that I wanted to address, xuhanp is helping in refining the queries so that we don't have two many queries.15:09
banixSwami: ok15:09
Swamicarl_baldwin: On the plugin side I have also addressed your comments, about run a "for loop" within the sync_data call.15:10
carl_baldwinI’ll take a look at your new patch.15:10
Swamicarl_baldwin: I have not pushed it yet, I will push it today or tomorrow.15:10
carl_baldwinI’ll watch out for it.  Thanks for the heads up.15:11
SwamiI need to add some more code for the SNAT work that I did, so I will push it along with it.15:11
SwamiThat's all I had for the plugin side.15:11
Swamimrsmith: are you there15:11
mrsmithyep15:11
*** beagles_brb is now known as beagles15:11
mrsmithfor l3-agent we are almost done with SNAT15:12
*** pcm_ has quit IRC15:12
Swami#topic L3 Agent15:12
*** openstack changes topic to "L3 Agent (Meeting topic: distributed_virtual_router)"15:12
*** gondoi is now known as zz_gondoi15:13
Swamimrsmith: Good progress15:14
mrsmithyep15:14
mrsmithonce we have basic SNAT done15:14
SwamiAnything else that you wanted to add or wanted to discuss with the community at this time.15:14
mrsmithwe'll have E/W and N/S15:14
mrsmithour next step will be moving the icehouse-GA15:14
SwamiGreat!.15:15
mrsmithand since there were more changes to FIPs there15:15
*** michael-yu has joined #openstack-meeting-alt15:15
mrsmithwe'll have to refactor/integrate a bit agagin15:15
mrsmith*again15:15
*** david-lyle has joined #openstack-meeting-alt15:15
mrsmiththen I'll update the WIP code15:15
SwamiOne other thing that we wanted to make sure after we are done with the E/W and N/S we should also update the "HowTo Wiki".15:15
mrsmithah... true15:16
*** viveknarasimhan has joined #openstack-meeting-alt15:16
viveknarasimhanhi Swami15:16
Swamimrsmith: Thanks for the update15:16
mrsmithnp15:16
Swamiviveknarasimhan: hi15:16
Swami#topic L2 Agent15:16
*** openstack changes topic to "L2 Agent (Meeting topic: distributed_virtual_router)"15:16
SwamiVivek can you provide an update on the L2 Agent15:17
viveknarasimhanyes15:17
viveknarasimhani got the 2nd patch set working15:17
viveknarasimhanand i had problems getting dependencies sorted out15:17
viveknarasimhanCarl helped me to get that done.  Thanks to carl15:17
viveknarasimhantoday i will be pushing the second patchset with15:17
viveknarasimhanmost of the Unit Tests running15:18
viveknarasimhanfurther i worked on few fixes to l2-pop side of ovs agent15:18
viveknarasimhanwhich i need to push upstream as well15:18
Swamiviveknarasimhan: Thanks for the update.15:19
SwamiHave you filed bugs on the l2-pop15:19
*** Murali has joined #openstack-meeting-alt15:19
*** richm has joined #openstack-meeting-alt15:19
Swamiviveknarasimhan: If you have filed those bugs, please go ahead and file the bugs and then push your code.15:20
*** jcoufal has quit IRC15:20
SwamiMurali: hi15:20
MuraliHi Swami15:20
*** shakamunyi has quit IRC15:20
viveknarasimhanhmm.15:21
viveknarasimhani took one bug15:21
viveknarasimhanpatch by Sylvain15:21
Swamiviveknarasimhan: Anything else you want to share.15:21
viveknarasimhanfor the new issue which i have fix, i'll file bug on L2-POp 'tip' code15:21
viveknarasimhanand send it for review15:21
*** woodster_ has joined #openstack-meeting-alt15:21
Swamiviveknarasimhan: You mentioned about the "CLI" command to show all the port-bindings.15:21
viveknarasimhanyes, we can request community here on if that is required15:22
Swamican you elaborate on that to the community,15:22
viveknarasimhanok15:22
SwamiYes, so that we can plan for that.15:22
viveknarasimhanIN dvr . the interfaces of DVR are replicated across multiple nodes.15:22
viveknarasimhanThese replicated dvr interface ports are now stored in a new binding table15:22
viveknarasimhanml2_dvr_port_bindings  inside the ml2 db15:23
viveknarasimhansince given port has only one binding, normal port binding info is shwon already kn port-show command today in Openstack15:23
viveknarasimhanwhat we are planning for is to enhance this 'neutron port-show'15:23
*** _nadya_ has joined #openstack-meeting-alt15:23
*** yamamoto has joined #openstack-meeting-alt15:23
*** shakamunyi has joined #openstack-meeting-alt15:23
viveknarasimhancommand to show the replicated port binding info for DVR interface ports as well15:24
SwamiI think the question to the sub-team, will this be helpfull for the cloud admins or will it be too much of information.15:25
*** atiwari has joined #openstack-meeting-alt15:25
SwamiIt is going to be more number of lines for a single port-show with the additional port-binding.15:25
xuhanpSwami, I think it will be helpful15:26
viveknarasimhanyes correct15:26
viveknarasimhan+1 with xuhanp15:26
scott-millwardHelpful for troubleshooting if nothing else  +115:26
carl_baldwin+115:26
viveknarasimhanas these lines will show which replicated ports are ACTIVE and which are DOWN as well15:26
Swamixuhanp: scott: carl: thanks15:27
Swamiagreed15:27
*** ityaptin has quit IRC15:27
Swamivivek: you can go ahead and implement it after we complete the core functionality15:27
viveknarasimhanok15:27
viveknarasimhanthe next one which i would like to pass forward is that15:28
SwamiWill this be an admin only command or tenant can also see this, what is your proposal15:28
*** kgriffs|afk is now known as kgriffs15:28
viveknarasimhanthe bulk flow adding / removing facility in ovs_lib today is raw15:28
*** james_li has joined #openstack-meeting-alt15:28
viveknarasimhanso when there is a 'race' for two sets of methods to do bulk flow manipulation (methods in ovs_neutron_agent)15:28
viveknarasimhansome flows get missed to be applied (or) deleted15:29
carl_baldwinSwami, I might consider admin only because nothing else in the API reveals to a normal tenant which host a port or VM is hosted on.15:29
scott-millward+1 on Admin only15:29
viveknarasimhan+1 admin15:29
SwamiI was also aligning with "admin" only command.15:29
Swamiagreed15:29
viveknarasimhancontinuing on the earlier two lines15:30
viveknarasimhanso the ovs_lib need to be enhanced to handle bulk manipulation on contextual basis15:30
*** betsy has joined #openstack-meeting-alt15:32
Swamivivek: Yes you can go ahead and file a blueprint spec on this enhancement and we can take it up once we are done with the base core dvr work15:32
viveknarasimhanok15:32
Swamiviveknarasimhan: thanks for the update15:33
Swami#topic L3/DVR scheduler15:33
*** openstack changes topic to "L3/DVR scheduler (Meeting topic: distributed_virtual_router)"15:33
*** james_li has quit IRC15:33
Swami#Murali can you provide an update on the scheduler15:33
Muraliyes Swami15:34
MuraliI am looking at  VRRP scheduler code to leverage. to avoid the duplicate15:34
*** rmoe has quit IRC15:35
SwamiMurali: Yes that was "sylvain" recommendation15:35
Muralii am post the WIP code for snat scheduling15:35
MuraliI may push this week15:35
SwamiMurali: Thanks for the update15:36
Muraliyeah I got comments from sylian15:36
*** emagana has joined #openstack-meeting-alt15:36
MuraliBut we need to yet finish the CLI for SNAT scheduling15:36
Swamimurali: yes got it.15:37
mrsmithmanual scheduling?15:37
Muralino15:37
Muraliits like list_hosting the snat router ....etc15:37
mrsmithk15:38
Swamimurali: got it.15:38
Swami#topic Atlanta summit15:38
*** openstack changes topic to "Atlanta summit (Meeting topic: distributed_virtual_router)"15:38
SwamiFolks next week most of the people will be in Atlanta15:38
SwamiSo we will not be having our regular meeting next week15:39
SwamiWe will continue our sub-team meeting the following week15:39
SwamiI have updated our DVR Etherpad with the topics of interest for discussion, if you feel that you need to add any other topic or item for discussion please feel free to edit the Etherpad.15:40
Swami#link https://etherpad.openstack.org/p/Distributed-Virtual-Router15:40
*** gyee has joined #openstack-meeting-alt15:40
*** ramishra has quit IRC15:41
SwamiFolks our DVR session is on Wednesday at 5.20p.m15:41
viveknarasimhanok15:42
*** Rajeev has joined #openstack-meeting-alt15:42
Swamirajeev: hi15:42
*** esker has joined #openstack-meeting-alt15:42
RajeevSwami: HI15:42
Swami#topic Open Discussion15:42
*** openstack changes topic to "Open Discussion (Meeting topic: distributed_virtual_router)"15:42
*** ramishra has joined #openstack-meeting-alt15:43
SwamiIf you have any other topics or open discussion we can discuss now15:43
*** pcm_ has joined #openstack-meeting-alt15:44
SwamiWe have been constantly pushing the code upstream and trying to address the comments, if there is any delay in addressing the review comments it is because we are in parallel working with N/S features for completion.15:44
Swami#link https://review.openstack.org/#/q/topic:bp/neutron-ovs-dvr,n,z15:45
viveknarasimhanalso we are testing east west with several cases, and so delay incurred on pushing15:45
viveknarasimhansubsequent patch sets upstream15:45
*** zns has quit IRC15:45
SwamiWe value all your comments, so please review the code and provide your feedback that way we can make it ready for the Juno milestone 1.15:45
Swamixunhanp: Do you have anything15:46
Swamicarl: Do you have item for discussion15:46
xuhanpSwami, nope. Thanks for driving this.15:46
Swamiscott, rajeev, mrsmith: any other items for discussion15:46
RajeevSwami: just curious is everyone here attending the Atlanta summit15:46
mrsmithnot I15:47
Swamibanix: pcm_: do you have any other items.15:47
Muralinot I15:47
*** pcm_ has quit IRC15:47
banixno15:47
Swamirajeev: I am attending the sumit.15:47
*** pcm_ has joined #openstack-meeting-alt15:47
xuhanpnot I15:48
SwamiThanks everyone for joining the DVR sub team meeting.15:48
*** eghobo has joined #openstack-meeting-alt15:48
SwamiSee you all the week after next.15:48
RajeevSwami: Thank You15:48
SwamiMeet others at the Atlanta15:48
Swamibye15:49
Swami#endmeeting15:49
viveknarasimhani am attending as well15:49
*** openstack changes topic to "(Meeting topic: training-manuals)"15:49
viveknarasimhanbye15:49
openstackMeeting ended Wed May  7 15:49:12 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-05-07-15.02.html15:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-05-07-15.02.txt15:49
openstackLog:            http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-05-07-15.02.log.html15:49
*** viveknarasimhan has quit IRC15:49
*** Swami has left #openstack-meeting-alt15:50
*** michael-yu has quit IRC15:50
*** s3wong has joined #openstack-meeting-alt15:50
*** Sukhdev has joined #openstack-meeting-alt15:50
*** Murali has quit IRC15:51
*** mrsmith has quit IRC15:51
*** nacim has quit IRC15:52
*** rueb7363 has quit IRC15:53
*** Leonr has joined #openstack-meeting-alt15:53
*** arnaud has joined #openstack-meeting-alt15:54
*** tdruiva has joined #openstack-meeting-alt15:55
*** rmoe has joined #openstack-meeting-alt15:56
*** rkukura has joined #openstack-meeting-alt15:57
*** tdruiva has quit IRC15:58
*** lsmola has quit IRC15:58
*** nlahouti_ has joined #openstack-meeting-alt15:59
*** rcurran has joined #openstack-meeting-alt15:59
*** eankutse has quit IRC15:59
*** matrohon has joined #openstack-meeting-alt15:59
rkukurahi ML2’ers!16:00
HenryGo/16:00
rcurranhi bob16:00
banixhi rkukura, all16:00
emaganahello!16:00
SukhdevHello16:00
yamamotohi16:00
rkukuraseems we’ve got quorum16:01
rkukura#startmeeting networking_ml216:01
openstackMeeting started Wed May  7 16:01:34 2014 UTC and is due to finish in 60 minutes.  The chair is rkukura. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:01
openstackThe meeting name has been set to 'networking_ml2'16:01
rkukura#link https://wiki.openstack.org/wiki/Meetings/ML2#Meeting_May_7.2C_201416:02
rkukura#topic Announcements16:03
*** openstack changes topic to "Announcements (Meeting topic: networking_ml2)"16:03
*** _nadya_ has quit IRC16:03
*** chandan_kumar has quit IRC16:03
*** padkrish has joined #openstack-meeting-alt16:03
rkukuraJuno Summit next week, so no IRC meeting16:03
rkukuraAlso, if you don’t attend the Neutron IRC meetings, you should be aware a mid-cycle sprint meeting is being planned for Juno16:04
rkukuraoptions being considered for date and location are at https://etherpad.openstack.org/p/neutron-juno-mid-cycle-meeting16:04
*** eankutse has joined #openstack-meeting-alt16:05
*** tdruiva has joined #openstack-meeting-alt16:05
rkukuraI think refactoring the neutron core is part of the agenda for this, and ML2 involvement in that would be important16:05
rkukuraAny questions/comments on these announcements, or any other announcements?16:06
*** irenab has joined #openstack-meeting-alt16:06
*** xuhanp has quit IRC16:06
HenryGWill ML2 also be affected by the task-based workflow plans?16:06
rkukuraif not, we’ll move on…16:06
*** ramishra has quit IRC16:07
rkukuraHenryG: good question16:07
rkukuraI haven’t looked at any specifics of that yet. What do you think?16:07
SukhdevHenryG: elaborate, please16:07
HenryGDon't know yet. I plan to attend the task-flow session and see.16:08
*** sadasu has joined #openstack-meeting-alt16:08
SukhdevHenryG: when and where is the session?16:08
rkukuraDepending on the granularity of tasks being addressed, it could potentially be useful for postcommit processing, and maybe for error recovery16:09
*** pcm_ has quit IRC16:09
emaganaSukhdev: I think is Tuesday lead by markmcclain1 but there is not BP yet16:09
*** pcm_ has joined #openstack-meeting-alt16:09
emaganaso it is a mystery right now16:09
HenryGI have not seen a BP for the session yet. The session proposal is http://summit.openstack.org/cfp/details/43316:09
Sukhdev I have been trying to dig it up -16:10
*** ramishra has joined #openstack-meeting-alt16:10
rkukuradefenitely looks relevent to ML2, and could result in significant changes to driver APIs, etc.16:10
*** jmontemayor has joined #openstack-meeting-alt16:10
rkukuraAnything else related to announcements?16:11
HenryGInfo on taskflow here: #link  https://wiki.openstack.org/wiki/TaskFlow16:11
*** jmontemayor has quit IRC16:11
*** andreaf has quit IRC16:11
rkukurathanks HenryG16:12
rkukura#topic Action Items16:12
*** openstack changes topic to "Action Items (Meeting topic: networking_ml2)"16:12
*** jmontemayor has joined #openstack-meeting-alt16:12
rkukurathe only official AI was for me, regarding etherpads for our summit sessions16:12
rkukuraI added one for the ML2 roadmap itself, and several have been added by others16:13
rkukuraWe’ve got 3 sessions that are mainly focused on ML2, each incorporation several session proposals16:13
rkukuraOne question is whether we should try to do a single etherpad per session, vs. etherpads per session proposal?16:14
rkukuraAny thoughts?16:14
emaganarkukura: single one makes easier to follow up action items16:15
asadoughi+1 for etherpads per session proposal16:15
Sukhdevrkukura: earlier we thought about going with one per session - either way is OK16:15
banixeven though the subsessions are related, it may be difficult to bring them into one place. May be multiple leading to sthe session and unifying we get there?16:15
rkukuraWe could certainly start with one etherpad per session, but with a section for each proposal16:16
*** arnaud has quit IRC16:16
*** arunkant has quit IRC16:17
*** julienvey has joined #openstack-meeting-alt16:17
*** zz_gondoi is now known as gondoi16:17
banixrkukura: that would be fine imo16:17
HenryGSounds like a good compromise. At least to get started.16:17
Sukhdevrkukura: I think that is good16:18
rkukuraI think etherpad per session would help foster dicsussion across the entire topic rather than each propsoal separately16:18
banixmakes sense16:18
nlahouti_rkukura: how much details regarding a desing should be added in the etherpad.16:18
rkukuraWould someone like to volunteer to pull together the etherpads for each of the three sessions?16:18
banixI can do it for the modular agent session16:19
rkukuranlahouti_: I think a page worth of bullet points per proposal is about the max16:19
*** mattgriffin has joined #openstack-meeting-alt16:19
rkukurabanix: Thanks!16:19
rkukuraI’m happy to do the ML2 roadmap session16:19
Sukhdevrkukura: we have only two etherpad as of now16:19
*** tdruiva has quit IRC16:20
Sukhdevdo we have the third one created?16:20
rkukurasomeone put together https://etherpad.openstack.org/p/hierarchical_network_topology16:21
*** carl_baldwin_ has joined #openstack-meeting-alt16:21
*** zns has joined #openstack-meeting-alt16:21
rkukuraThis has sections for each of the proposals that went into it16:21
Sukhdevrkukura: thanks for pointing this one - I was missing this…this looks good16:21
rkukurabut we probably should flesh-out each with some bullets to explain the idea, raise issues, etc16:22
*** arnaud has joined #openstack-meeting-alt16:22
padkrishrukkura: Yes, this has the three sessions for Friday16:22
*** woodster__ has joined #openstack-meeting-alt16:22
SukhdevWe need to beef this one up16:22
rkukurawe’ve moved into the next topic...16:22
rkukura#topic ML2 Design Summit Sessions16:23
*** openstack changes topic to "ML2 Design Summit Sessions (Meeting topic: networking_ml2)"16:23
*** carl_baldwin has quit IRC16:23
*** carl_baldwin_ is now known as carl_baldwin16:23
*** sbalukoff has joined #openstack-meeting-alt16:24
*** xuhanp has joined #openstack-meeting-alt16:24
rkukuraThe agenda page has links to the neutron schedule, the 3 scheduled sessions, and the wiki with the etherpads16:24
rkukuraI’d like to see the session descriptions updated to be more clear, etc., and can ask mestery about that16:25
*** woodster_ has quit IRC16:25
rkukuraAre there any ML2 session proposals were supposedly accepted/merged, but don’t have a home on one of these three session?16:25
Sukhdevrkukura: I pointed it to him about one session - he mentioned you need to do it or coordinate with him :-):-)16:26
rkukuraSukhdev: OK, if I can, I’ll try16:26
*** IlyaE has quit IRC16:26
banixrkukura: there was a session approved for inclusion but i dont see it in the list. the session on having a unified mechanism driver for SDN controllers. I do NOT think we need to have this but wanted to get clarification on it.16:27
rkukurabanix: I thiink the intention was to cover that as part of the ML2 roadmap session16:27
*** BrianB_ has joined #openstack-meeting-alt16:27
banixrkukura: yes that was my understanding.16:28
Sukhdevrkukura: ML2 Roadmap description is not very clear - this is what I asked Kyle to fix16:28
rkukurabanix: Lets put the link to the BP/spec on the etherpad for that session, and try to identify any dependencies, and who is working on it16:28
*** ramashri has joined #openstack-meeting-alt16:28
rkukuraSukhdev: OK, I’ll see if I can fix that one, and if not, will work with mestery on it16:29
banixrkukura: i think this is a simple and limitted of a topic that may not need a session; will follow up later.16:29
rkukurabanix: That was the goal for the roadmap session proposal - just to raise awareness of efforts that didn’t need their own sessions16:30
banixrkukura: ok; makes sense.16:30
SukhdevThis is the one for ML2 roadmap - need to beef up https://etherpad.openstack.org/p/ML2_Juno_Roadmap16:31
rkukuraThere were two sessions that we approved that mestery marked as “merging with Isaku's session”16:31
*** xarses has quit IRC16:31
rkukuraDo we know which session that is?16:31
rkukuraThe proposals are http://summit.openstack.org/cfp/details/395 and http://summit.openstack.org/cfp/details/40916:32
banixyeah hold on16:32
rkukuraThese seem agent-related, but I’m not sure if they are in the ML2 agent session, or a different session16:32
banixyes the above sessions were the ones16:33
banixnot in modular agent session16:33
*** IlyaE has joined #openstack-meeting-alt16:34
rkukurabanix: So are these in a separate session?16:34
*** jgallard has quit IRC16:34
yamamotothis one? http://junodesignsummit.sched.org/event/9a0726f0946e4682bc77427afab44116#.U2pgnF7nwoc16:35
*** xuhanp has quit IRC16:35
banixnot sure.16:35
rkukura#action banix to organize single etherpad for Modular L2 Agents session16:35
rkukurayamamoto: Yes, that looks like it. Thanks!16:36
banixyeah yamamoto is right; i think that is the session^^^16:36
rkukura#action rkukura to flesh out single etherpad for ML2 Roadmap session16:36
rkukuraAnd the hierarchical session already has a single etherpad16:37
yamamotoper-proposal etherpads will be removed?16:37
rkukuraSo each session proposer should try to flesh out an outline for discussion at the summit either the appropriate etherpad16:37
*** igormarnat_ has quit IRC16:38
*** pcm_ has quit IRC16:38
rkukurayamamoto: If the assignees could move the per-proposal content to the the single etherpad, I think that the links to those can be removed - any reason not to?16:38
yamamotono reason i can think of.16:39
rkukuraplease try to think about how to get the most value out of these summit sessions16:39
*** gokrokve has quit IRC16:40
banixyeah i think for each session the stake holder need to talk and organize as how to present and direct the discussion16:40
*** julienvey has quit IRC16:40
banixs/holder/holders16:40
*** pcm_ has joined #openstack-meeting-alt16:41
nlahouti_so this would be the main link : https://etherpad.openstack.org/p/ML2_Juno_Roadmap for the ML2 road map.16:41
Sukhdevnlahouti_: that is presently listed under neutron etherpads16:43
padkrishrkukura: some session, e.g. hierarchical networks has three topics...so each topic owner gets around 13 or 14 mins? If every topic owner in a etherpad session brainstorms before, it can be presented by one single person after collecting the ideas16:43
Sukhdevnlahouti_: I will add content to this later today or tomorrow16:43
nlahouti_sukhdev: yes it is under ' ML2 Juno Roadmap'16:43
nlahouti_sukhdev: ok16:44
Sukhdevpadkrish: I think it is a good idea -16:44
rkukurapadkrish: I’m happy for the proposers in each session to figure out how they want to run that session16:44
Sukhdevpadkrish: I was thinking we could get together on Monday or Tuesday in Atlanta and hash it out, thoughts?16:45
*** tdruiva has joined #openstack-meeting-alt16:45
padkrishsukhdev# that's also good...i have proposed a webex session for tomorrow specifically for the hierarchical network session16:45
rkukuraRemember that these are supposed to be more discussion than presentation, so I don’t think having a single presenter is very imporant16:45
*** coolsvap is now known as coolsvap|afk16:46
Sukhdevpadkrish: can you share the webex info?16:46
padkrishsukhdev# sure...16:46
rkukurapadkrish: I was going to look at my calendar regarding the new times - will followup to that email after this meeting16:46
SukhdevI think it is better the subject matter expert presents - rather than just one presenter16:46
padkrishrkukura: Totally agree....i want to have it as a discussion for which we need to brainstorm b4...otherwise, it may become a presentation :)16:47
padkrishrkukura: Sure, thanks...in which case sukhdev, will update with the new timings16:47
rkukuraWould be nice for each session to start with an intro that lists the topics and how they are interelated, has the discussion on the topics, then has a couple minutes at the end to see how things all fit together, get people signed up to do the work, identify dependencies/issues, etc.16:48
Sukhdevpadkrish: my email sukhdev@arista.com16:48
*** dtx00ff has joined #openstack-meeting-alt16:48
padkrish#sukhdev#: Thanks16:48
rkukuraAnything else on the design summit before we move on to bugs, reviews, etc.?16:49
rkukura#topic Bugs16:49
*** openstack changes topic to "Bugs (Meeting topic: networking_ml2)"16:49
rkukura#link https://bugs.launchpad.net/neutron?field.searchtext=ml216:50
rkukuraMy port binding outside transactions but is at the top of the list16:50
rkukuraGot some good review feedback, will hopefully get an update pushed before the summit16:51
rkukuraIs anyone aware of any bugs that need to be dicussed, need assignees, etc?16:51
*** megan_w is now known as megan_w|afk16:51
*** derekh_ has quit IRC16:52
rkukura#topic Spec reviews16:52
*** openstack changes topic to "Spec reviews (Meeting topic: networking_ml2)"16:52
rkukuraI’m way behind on this myself16:53
rkukuraAny spec reviews anyone would like to discuss?16:53
rkukura#topic Code reviews16:54
*** openstack changes topic to "Code reviews (Meeting topic: networking_ml2)"16:54
*** chandan_kumar has joined #openstack-meeting-alt16:54
*** gokrokve has joined #openstack-meeting-alt16:54
nlahouti_we posted couple for ML2 and got comment and reply to the comment but don't know what know what is next?16:54
rkukuranlahouti_: Wondering if it would help to devote good chunk of the ML2 meetings to spec reviews16:55
Sukhdevrkukura: sorry - was pulled into another thing. I put my comment on https://review.openstack.org/#/c/91811/16:55
nlahouti_rkukura: That would help I believe16:55
rkukuraWe can list the ML2-related spec reviews on the agenda, and raise awareness, get reviews signed up, ...16:55
irenabI  have a question related to review https://review.openstack.org/#/c/74464/16:56
*** slagle has quit IRC16:56
rkukurairenab: what’s the question?16:56
irenabthe spec is approved, by patch is still with -2, any advice how to proceed?16:57
rkukurairenab: Have you pinged markmcclain on IRC and/or email?16:57
*** amytron has quit IRC16:57
*** slagle has joined #openstack-meeting-alt16:58
irenabrkukura: meanwile via the patch review only, will follow up with email/irc16:58
rkukuraI think our time focus post-summit needs to be on working through the ML2-related spec reviews16:58
*** harlowja has joined #openstack-meeting-alt16:58
rkukuraand the spec reviewers should then follow through on the code reviews16:58
rkukura#topic Open Discussion16:59
*** openstack changes topic to "Open Discussion (Meeting topic: networking_ml2)"16:59
*** Barker has joined #openstack-meeting-alt16:59
rkukurawe’ve only got a minute16:59
rkukuraanything anyone?16:59
rkukurathanks everyone!16:59
*** denis_makogon has quit IRC16:59
yamamotothanks17:00
rkukura#endmeeting17:00
*** openstack changes topic to "(Meeting topic: training-manuals)"17:00
openstackMeeting ended Wed May  7 17:00:09 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-05-07-16.01.html17:00
banixsee you those who go to the summit in Atlanta!17:00
*** rcurran has quit IRC17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-05-07-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-05-07-16.01.log.html17:00
*** denis_makogon has joined #openstack-meeting-alt17:00
*** denis_makogon has quit IRC17:00
*** denis_makogon has joined #openstack-meeting-alt17:00
rkukurabye17:01
*** rkukura has left #openstack-meeting-alt17:01
*** arnaud has quit IRC17:01
*** denis_makogon has quit IRC17:02
*** BrianB_ has quit IRC17:02
*** nlahouti_ has quit IRC17:02
*** dmakogon_ has joined #openstack-meeting-alt17:02
*** irenab has quit IRC17:05
*** pcm_ has left #openstack-meeting-alt17:05
*** noslzzp is now known as noslzzp_lunch17:05
*** noslzzp_lunch is now known as noslzzp17:05
*** dtx00ff has quit IRC17:07
*** padkrish has quit IRC17:08
*** dtx00ff has joined #openstack-meeting-alt17:08
*** sadasu has quit IRC17:08
*** megan_w|afk is now known as megan_w17:08
*** tdruiva has quit IRC17:08
*** xarses has joined #openstack-meeting-alt17:10
*** safchain has quit IRC17:11
*** s3wong has left #openstack-meeting-alt17:13
*** michael-yu has joined #openstack-meeting-alt17:16
*** saurabhs has joined #openstack-meeting-alt17:17
*** denis_makogon has joined #openstack-meeting-alt17:18
*** balajiiyer1 has joined #openstack-meeting-alt17:20
*** gokrokve has quit IRC17:21
*** zns has quit IRC17:21
*** ramishra has quit IRC17:24
*** michael-yu has quit IRC17:27
*** jmontemayor has quit IRC17:28
*** michael-yu has joined #openstack-meeting-alt17:28
*** IlyaE has quit IRC17:30
*** jcru has joined #openstack-meeting-alt17:30
*** amytron has joined #openstack-meeting-alt17:31
*** jdob has quit IRC17:31
*** jdob_ has joined #openstack-meeting-alt17:31
*** otherwiseguy has quit IRC17:32
*** morganfainberg_Z is now known as morganfainberg17:32
*** jasonb365 has joined #openstack-meeting-alt17:32
*** morganfainberg is now known as needscoffee17:33
*** needscoffee is now known as morganfainberg17:33
*** krtaylor has quit IRC17:33
*** yamamoto has quit IRC17:34
*** TravT has joined #openstack-meeting-alt17:36
*** robertmyers has joined #openstack-meeting-alt17:38
*** NehaV has joined #openstack-meeting-alt17:39
*** jmontemayor has joined #openstack-meeting-alt17:39
*** gokrokve has joined #openstack-meeting-alt17:39
*** chuckC has quit IRC17:43
*** ramashri has quit IRC17:43
*** dshulyak_ has joined #openstack-meeting-alt17:49
*** irenab has joined #openstack-meeting-alt17:49
*** mat-lowery has joined #openstack-meeting-alt17:49
*** Sukhdev has quit IRC17:50
*** zns has joined #openstack-meeting-alt17:51
*** IlyaE has joined #openstack-meeting-alt17:51
*** otherwiseguy has joined #openstack-meeting-alt17:53
*** arnaud has joined #openstack-meeting-alt17:53
*** Barker has quit IRC17:54
*** Barker has joined #openstack-meeting-alt17:55
*** stannie has quit IRC17:55
*** SlickNik has joined #openstack-meeting-alt17:55
*** mestery has joined #openstack-meeting-alt17:57
*** tvoran has joined #openstack-meeting-alt17:58
*** robertmyers has quit IRC17:59
*** yogesh_ has joined #openstack-meeting-alt17:59
*** bmelande has joined #openstack-meeting-alt17:59
SlickNik#startmeeting trove18:00
openstackMeeting started Wed May  7 18:00:07 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
*** jasonb365 has quit IRC18:00
kevinconwayo/18:00
*** jasonb365 has joined #openstack-meeting-alt18:00
glucaso/18:00
amrith\018:00
yogesh_o/18:00
peterstac\o18:00
iccha1o/18:01
abramley0/18:01
mattgriffino/18:01
*** tprado has joined #openstack-meeting-alt18:01
mat-loweryo/18:01
*** robertmyers has joined #openstack-meeting-alt18:01
*** abettadapur_ has quit IRC18:01
*** imsplitbit has joined #openstack-meeting-alt18:01
*** dims has quit IRC18:01
dougshelley66o/18:01
robertmyerso/18:01
cweido/18:01
*** ramashri has joined #openstack-meeting-alt18:01
imsplitbito/18:01
esmute0/18:01
*** mestery_ has joined #openstack-meeting-alt18:01
*** cp16net has joined #openstack-meeting-alt18:01
SlickNikAgenda:18:02
SlickNik#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting18:02
vipulo/18:02
*** esp has joined #openstack-meeting-alt18:02
*** ranjitha has joined #openstack-meeting-alt18:02
SlickNikLast meeting logs:18:02
SlickNik#link http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-04-30-18.02.html18:02
denis_makogono/18:03
*** tildedave_laptop has joined #openstack-meeting-alt18:03
SlickNik#topic How do Gerrit changes get approved?18:03
*** openstack changes topic to "How do Gerrit changes get approved? (Meeting topic: trove)"18:03
cp16net|o|18:03
kevinconway>o<18:03
SlickNikmat-lowery: take it away18:03
espo/18:03
esmutei am curious about this too18:03
esmute:P18:03
mat-loweryGoal: To clarify the Gerrit change approval process used by Trove core (for the benefit of core and non-core).18:03
*** jdob has joined #openstack-meeting-alt18:04
mat-loweryShould I just reproduce the text from the agenda?18:04
*** rueb7363 has joined #openstack-meeting-alt18:04
mat-loweryAll of my arguments are there. :)18:04
SlickNikThat's not necessary.18:04
juiceo/18:04
*** mestery has quit IRC18:04
SlickNikI was giving this a lot of thought this week.18:05
SlickNikAnd a couple of things that made sense to me.18:05
mat-loweryDoes Trove core use a systematic process of reviews and approvals to prevent starvation? Ultimate goal: Reduce time between submittal and merge.18:05
*** ViswaV_ has joined #openstack-meeting-alt18:05
SlickNikIt's good idea to align on a process to prioritize and review changes18:05
*** mestery_ is now known as mestery18:06
SlickNikBut I was looking at the reviewday tool18:06
SlickNik#link  http://status.openstack.org/reviews/18:06
cp16neti'd like to be able to just see the reviews for the projects i care about in that review day tool18:06
*** jdob_ has quit IRC18:06
cp16netinstead of EVERY project18:07
kevinconwayproject:openstack-trove in the search bar?18:07
cp16netdoesnt seem to have a anchor you can use either18:07
vipulI don't think there is a common tool / process that core uses.  It might be good to pick one that we agree to18:07
SlickNikA lot of the top reviews there are actually waiting on changes from the submitter.18:07
mat-lowerycp16net: You can run it locally but it takes forever.18:07
kevinconwayoh… no more search bar18:07
vipulSlickNik: yea it's surprising so many with -1 and -2 show up at the top18:07
cp16netkevinconway: this is an entirely differnt tool for reviews18:07
mat-loweryReviewDay uses a scoring algorithm based on Launchpad bug priority and age of Gerrit change.18:08
amrithreview.openstack.org supports search customization.18:08
vipuli've often used: https://launchpad.net/trove/+milestone/juno-1 as a way to pick higher priority bugs/bps to focus on18:08
amrithmy url is https://review.openstack.org/#/q/-label:CodeReview-2+AND+-label:+Verified-1+AND+status:open+AND+is:watched,n,z18:08
*** xarses has quit IRC18:08
*** SnowDust has joined #openstack-meeting-alt18:08
amriththat gives you just the projects taht you watch18:09
amrithand you can set in your lp profile18:09
iccha1I think it might be good to review some of the review stats at every meeting to see how trove is doing . This is outdated, but if you look at http://russellbryant.net/openstack-stats/trove-reviewers-30.txt, it has some useful metrics like changes abandoned in the last 30 days, or queue growth in last 30 days18:09
SlickNikmat-lowery: Also a lot of reviews on reviewday that haven't yet passed unit-tests.18:10
*** terryw has joined #openstack-meeting-alt18:10
SlickNikDoesn't make sense prioritizing some of those.18:10
*** james_li has joined #openstack-meeting-alt18:10
amrithSlickNik, if you look at the URL I posted, it eliminates anything with a -2 or fails verified18:10
denis_makogonhttp://www.stackalytics.com/report/reviews/trove-group/open18:11
amriththat may be what you want18:11
mat-lowerySlickNik: Understood. I'm not selling ReviewDay but rather a prioritized queue (based on something that makes sense) that every core (and non-core) can/must use.18:11
SlickNikiccha1: Yes, the reviewstats tool hasn't been run since the gerrit upgrade. :(18:11
SlickNikmat-lowery: Got it.18:11
iccha1i like the query amrith , thats something which used in glance too.18:11
SlickNikSo sdague has a couple of good blog articles about this too18:12
amrithAlso for those who want to customize their search, this page is helpful. #link https://review.openstack.org/Documentation/user-search.html18:12
SlickNik#link https://dague.net/2014/04/30/helpful-gerrit-queries-gerrit-2-8-edition/?utm_campaign=OpenStack+Now&utm_source=hs_email&utm_medium=email&utm_content=12695477&_hsenc=p2ANqtz-9twO0GbtB202VDA5wExXeBMIfQwnXdSBfuSj807F74UdfhZwJCsNKrVKI0pi-PqqRJQru8eyayQjntiU8sG1CaO4f1pA&_hsmi=1269547718:12
mat-loweryMy argument for a priority goes like this: If a priority exists, there's no need for "Hey core, please review <change>" which I find inefficient and unfair. It seems that bugging the channel for reviews is OK to some. Why?18:12
*** otherwiseguy has quit IRC18:12
robertmyersmat-lowery: well sometimes it is a blocking bug18:13
SlickNikmat-lowery: I find it okay because of a couple of reasons18:13
robertmyersso we should get eyes on it18:13
mat-loweryrobertmyers: Understood in those circumstances.18:13
mat-loweryBut otherwise, you're cutting the line. :)18:13
imsplitbitis there necessarily a line?18:13
SlickNikRarely do I prioritize a review above all others based on a poke18:14
SlickNikAnd it helps to get a conversation started.18:14
SnowDust:)18:14
* esp visualizes a fight at walmart18:14
juiceI think as a team we would be more efficient with a priority list18:14
juiceright now our focus is like a disco ball rather than a magnifying glass18:14
iccha1if everyone has the same pripirty list, wont the bottom ones be starved?18:14
* amrith thinks about focusing on a disco ball18:15
cp16netyeah i am in agreement we need to be better about it18:15
esmutejuice: as we get more members and more patches, having a process with priority will help18:15
esmute+1 juice18:15
*** morganfainberg has quit IRC18:15
juiceiccha1: the ones at the bottom will not stay there forever18:15
* robertmyers review are on top18:15
SnowDusticcha1 : right18:15
mat-loweryiccha1: If the scoring is is age-influenced, then older (even low priority ones) rise to the top18:15
juicethey will actually move up because we cleared the ones the at the top18:15
*** andreaf_ has joined #openstack-meeting-alt18:15
*** andreaf_ has quit IRC18:16
juiceI think core should decide priority - we can use launchpad to set priority and all work from the same list18:16
esmuteand priority should be last (or way down) if they dont pass jenkins18:16
iccha1+118:16
cp16netthere are some reviews where the bp has not been approved18:16
juiceI don't know if it is feasible to come up with search criteria that will do this for us18:16
*** morganfainberg has joined #openstack-meeting-alt18:16
*** andreaf has joined #openstack-meeting-alt18:16
vipulso the problem with just looking at patch age.. is that there are patches that exist for things that we have disagreement on18:17
juicecp16net: then those reviews should have a low priority18:17
iccha1priorities should be around - first go look at reviews you have already reviewed and folks has posted patchset on18:17
vipulcp16net: +118:17
SlickNikvipul: +118:17
juicein fact we don't need to know the priority for all reviews18:17
esmutevipul, in that case, the core can -2 these patches bringing them down in priortiy18:17
*** dprince has quit IRC18:17
*** morganfainberg has quit IRC18:18
juicewe just need to know which ones are the top priority (e.g. top 5)18:18
juicethe rest are unprioritized18:18
esmutei know some cores -2 patches when they need more clarity and discussions18:18
SlickNikesmute: It's not that easy. The patch might be a good idea, but it might be −1'ed to fix some issues.18:18
SlickNikIn that case a −2 might be a bit harsh18:18
vipulesmute: that could work.. if we ignore -2's and factor in age18:18
vipulobviously there is isn't a simple answer here... needs a longer discussion18:19
vipulwho's going to be in ATL!?18:19
mat-lowerySo the priority queue is liked in general. Just that the scoring isn't as Trove core would like? Is that fair?18:19
dougshelley66so i kind of made the assumption that core would be looking for reviews that are +1 under "V" and had at least 1 +1 under "CR"18:19
vipulsounds like a good place to discuss this18:19
mat-lowerydougshelley66: Thus my argument that -1's should not be left and then the reviewer disappears.18:20
amrithvipul, was question re: ATL targeted at core or all?18:20
*** morganfainberg_Z has joined #openstack-meeting-alt18:20
*** morganfainberg_Z is now known as morganfainberg18:20
mat-loweryThat's the next point: Gerrit etiquette.18:20
vipulanyone who wants to discuss this amrith18:20
amrithI'll be there18:20
amrithin ATL and to discuss this18:20
SlickNikdougshelley66: I know that we look for +1 from Jenkins (i.e. it has to pass the unit tests), but there's no requirement for it having a +1 under CR18:20
*** xarses has joined #openstack-meeting-alt18:20
dougshelley66SlickNik - i wasn't saying that was a requirement, just figured that would be a trigger18:21
*** megan_w is now known as megan_w|afk18:21
mat-loweryTo wrap this item up, is core going to hammer out a scoring algorithm in ATL?18:22
dougshelley66mat-lowery right; how to enforce the policy that you can't -1 and run18:22
SlickNikAnother thing to keep in mind here is that we have some items that are just easy approves: Changes to help strings that make sense, changes to global-requirements, localization changes.18:22
*** abettadapur_ has joined #openstack-meeting-alt18:22
mat-loweryPerhaps number of +1's can bump the item up in score too aka easy approves.18:23
vipul#link https://wiki.openstack.org/wiki/ReviewWorkflowTips18:23
vipullooks like there are a number of tools available to help with this18:24
SlickNikMy personal preference is to approve those sort of changes soon, so that it doesn't affect the size of the review pipeline.18:24
*** jcoufal has joined #openstack-meeting-alt18:24
*** krtaylor has joined #openstack-meeting-alt18:24
mat-loweryI'll check out all of these review tip links but the point, as juice made was to have the queue be presented to you (no work from the reviewer about a query) then work from the top18:25
denis_makogonmat-lowery, we cant enforce contributors to post only one type of marks if patch already has N +1's18:25
cp16netvipul: oh nice18:25
SnowDust   ok then I'll submit my patch with friends bumping it up wid their +1?18:25
cp16netthanks for sharing those tools maybe that can help me18:25
*** jrodom has joined #openstack-meeting-alt18:26
mat-loweryWe're nitpicking a proposed algorithm. My point: At least have an algorithm.18:27
mat-loweryAnd everyone follow it.18:27
*** mestery has quit IRC18:27
mat-loweryI will not be in ATL. Is there some kind of discussion list I should add this to? (And move on to next item.)18:28
dougshelley66given that list of tooling that vipul provided, i assume this is a solved problem? wouldn't every project have the same issue?18:28
esmuteI am in all for having a priority-based process for review like ReviewDay. We can keep making adjustment as we need (ie improve our scoring algorythm etc)18:28
vipuldougshelley66: i don't thnk it's a solved problem.. the tools may help pick reviews based on different criteria.. i am not sure if that's the criteria for us18:29
vipulwe should still discuss what our priority queue is made up of18:29
SlickNikesmute: I hope we don't end up developing a review solution instead of a datastore service :)18:29
vipulSlickNik: weren't you going to propose a 'pod session' to talk about this18:29
SlickNik#action SlickNik to come up with a proposal on how to prioritize reviews to be discussed in ATL, and on IRC.18:29
dougshelley66vipul: ok but i don't konw if i'm clear why all the projects couldn't tackle this issue in the same manner18:30
SlickNikYes, I was.18:30
kevinconwaybut what about review neutrality?18:30
kevinconwayif we allow service providers to create "fast-lanes" for reviews what next?18:30
vipuldougshelley66: good point.. i don't honestly know how other projects do it18:30
*** mestery has joined #openstack-meeting-alt18:31
mat-loweryMay I move on to next point which is to discuss how all of us can keep (high-quality) code moving through the system?18:31
iccha1vipul: we had the same problem in glance18:31
SlickNikvipul: Yes, I'm working on scheduling a pod session to discuss this issue in ATL.18:31
denis_makogonso, can we proceed to next topic?18:31
*** notmyname has quit IRC18:31
SlickNikStay tuned for more info regarding that.18:32
*** notmyname_ has joined #openstack-meeting-alt18:32
SlickNikmat-lowery: go for it.18:32
iccha1SlickNik: mark wash from glance had tried to take some steps with the same18:32
*** notmyname_ is now known as notmyname18:32
mat-loweryas dougshelley66 put it succinctly: you can't -1 and run. Do we all agree? There's an obligation to respond to follow-ups.18:32
*** jasonb365 has quit IRC18:33
amrith+118:33
dougshelley66+218:33
dougshelley66:)18:33
denis_makogonmat-lowery, agreed, -1 without any reason seems invalid18:33
ramashri+118:33
kevinconwaywhat if we have committment issues?18:33
robertmyerskevinconway: lol18:33
espmat-lowery: you can follow up with your reviewers right?18:34
dougshelley66robertmyers: you are just encouraging him :)18:34
mat-lowerydenis_makogon: not without reason. leaving a -1...then the committer disagrees or needs clarification or whatever...and the original reviewer never returns18:34
amytrondougshelley66:  +118:34
juicemat-lowery: what was the next point18:34
robertmyersdougshelley66: agreed18:34
SlickNikIf running comprises not ever responding, then I agree with that sentiment. :)18:35
denis_makogonmat-lowery, in this case, if noone followed same thoughts, -1 can be easily ignored18:35
espmat-lowery: my point from above is that at times if I don’t agree with a -1, I have to follow up with the review to clarify18:36
SlickNikBut this is an async process, so I'd imagine that stuff can come up between when I make a comment and when the other involved party replies.18:36
kevinconwaywhat do you expect from a -1 followup?18:36
SnowDustgood one denis_makogon18:36
kevinconwaypushing up new code get's rid of those18:36
SlickNikSo if it takes me, maybe a day to reply to a comment in gerrit because of this, I think that's acceptable.18:36
espkevinbenton: :) that works too18:36
espsorry ^ kevinconway18:37
mat-lowerykevinconway: I hope you're kidding.18:37
mat-loweryBut I have seen it.18:37
mat-loweryOr what looks like it.18:37
vipulmat-lowery: +1 please dont' just push up a new patch set..18:37
vipulat least reply to the comment18:37
*** jasonb365 has joined #openstack-meeting-alt18:37
vipulit's insane trying to figure out if all previous reviewer comments have been addressed18:37
imsplitbitkevinconway: +1 :)18:37
SnowDustesp: Kevin bent on ?18:37
juicemat-lowery: keeping clean code through the project I think was the next topic18:37
iccha1SlickNik: I think we need metrics, how many reviews done by cores per day, non cores per day, how many patches get abandoned per day and why, etc. The question is are there enough reviews being done first, and then if yes are the right review sbeing looked at18:38
juiceI think we are on a tangent right now18:38
espSnowDust: yeah I didn’t get enough coffee..18:38
kevinconwayi'm not suggesting pushing up new code just to get rid of -1 votes18:38
juice(high-quality) is what you said18:39
kevinconwayi'm just curious why -1 is such a point of contention here18:39
kevinconway-1 is a community member saying "change this i don't like it"18:39
SlickNikbtw, I've seen some behaviour in the new gerrit that doesn't get rid of the −1 even if a new patchset is pushed up.18:39
peterstacI have too18:39
kevinconwaybut -1/+1 don't carry any great weight. you can agree or disagree. core makes the adult decisions18:39
SlickNikSo this might be a moot issue, not that review.o.o has moved to the new gerrit version.18:39
juicekevinconway: no ones is disagreeing with -1 - the disagreement is using a -1 without comments18:39
SlickNiknow*18:39
mat-loweryjuice: My only point by adding high-quality was not to imply fast tracking code for the sake of speed. We can have good reviews and still get things merged.18:39
iccha1i think this conversation is running in too many parallel directions :)18:40
juicemat-lowery: sure we shouldn't sacrifice speed for quality is what you are saying18:40
espiccha1: +118:40
SnowDustesp: +118:41
juicewhoops - other way around in my last comment18:41
kevinconwaySnowDust: -118:41
espI don’t think anyone disagrees with the things being brought up18:41
SlickNikOkay, let me try to give this some definition18:41
amrithall: are we attempting to solve with a broad "policy" that which should be solved by individual interactions when a particular problem occurs? Is this a widely prevalent problem impacting a number of reviews? if yes, I see the point in the policy. If this is a fringe, how about core periodically do some coaching and address that way?18:41
juicego for it slicknik - bring 'er to a close18:41
*** luizfar has joined #openstack-meeting-alt18:41
*** bmelande has quit IRC18:42
SlickNikI don't think anyone disagrees with any of the points mentioned in the Gerrit Ettiquette section.18:42
SlickNik#startvote No leaving -1s and then disappearing. A reviewer that leaves a -1 has an obligation to respond to follow up questions? yes, no18:43
openstackBegin voting on: No leaving -1s and then disappearing. A reviewer that leaves a -1 has an obligation to respond to follow up questions? Valid vote options are yes, no.18:43
openstackVote using '#vote OPTION'. Only your last vote counts.18:43
SlickNik#vote yes18:43
mat-loweryOK. Then if this is just a reminder of the etiquette, I'm happy18:43
amrith#vote yes18:43
kevinconwaywait is this that you have to leave a comment or if you -1 you have to -1 every update?18:43
ramashri#vote yes18:43
dougshelley66#vote yes18:43
mat-lowery#vote yes18:43
SnowDustkevinconway : waiting for an adult decision 4 ur -118:43
vipul#vote yes!18:43
openstackvipul: yes! is not a valid option. Valid options are yes, no.18:43
esp#vote yes18:43
esmute#vote yes18:43
denis_makogon#vote yes18:43
cp16net#vote yes18:43
esmutelol too excited about this one vipul18:43
glucas#vote yes18:43
esmute?18:43
juice#vote yes18:43
SlickNik#endvote18:43
openstackVoted on "No leaving -1s and then disappearing. A reviewer that leaves a -1 has an obligation to respond to follow up questions?" Results are18:43
openstackyes (11): juice, SlickNik, glucas, esp, esmute, amrith, denis_makogon, mat-lowery, cp16net, ramashri, dougshelley6618:44
SlickNikSo just as I thought.18:44
juice:)18:44
cp16neti think this should be obvious and its a silly vote though.18:44
denis_makogonlol, no way )18:44
kevinconway-118:44
SlickNikAre all the other ones similar, or is there a contentious issue?18:44
SlickNikcp16net: Yes, I feel the same way.18:44
esmutecp16net: humans by nature like winning18:44
mat-loweryOK. So the lesson for me is to personally bug the people who are not following etiquette.18:44
iccha1So another point is when we look at stackalytics Core team size: 5 (1.3 per core per day) reviews and Total reviewers: 31 (0.6 per reviewer per day). [http://www.stackalytics.com/report/contribution/trove-group/30] So maybe we need to just do more reviews too?18:44
mat-loweryI tried Gerrit itself. No response.18:44
abramley!sftp18:44
openstackabramley: Error: "sftp" is not a valid command.18:44
SlickNikI'm not going to start a vote on them unless someone feels a dire need to talk about one of those rules.18:44
abramleyOoops - sorry18:45
* amrith wonders why abramley is banging sftp18:45
mat-lowerySlickNik: no need18:45
vipuliccha1: +1 I think that's the main issue18:45
*** esker has quit IRC18:45
vipuliccha1: size of core team and core team cycles spent on reviews18:45
*** dtx00ff has quit IRC18:45
*** james_li has quit IRC18:46
cp16net+118:46
mat-lowerymore reviews off a prioritized list :)18:46
vipuland a lack of a prioritized list :p18:46
SlickNikiccha1: I think you bring up a good point here.18:46
SlickNikiccha1: We need to do a better job of tracking the stats, so that we know when we are slipping or if we need to grow core to cope with the review demand.18:47
*** otherwiseguy has joined #openstack-meeting-alt18:47
juicecinder has similar stats18:47
juiceactually even less18:47
iccha1SlickNik: +1 and bring it up every meeting to keep tabs on the queue18:48
mat-loweryiccha1: +118:48
kevinconwayiccha1: ugh. do we have to read previous meeting minutes into record too?18:48
SlickNik#action SlickNik to look at what stats to monitor for trove review health and include it in the aforementioned "review" proposal18:48
SlickNikI think we've beat this down for now.18:49
cp16neti think thats a good idea to keep everyone in the know18:49
cp16net+118:49
SlickNikI'm going to put something together and will discuss with folks at ATL and on IRC. So stay tuned.18:50
mat-lowerythanks SlickNik18:50
iccha1sounds like a plan!18:50
SlickNikmat-lowery: Thanks for bringing it up!18:50
SlickNik#topic Meetings next week18:50
*** openstack changes topic to "Meetings next week (Meeting topic: trove)"18:50
SlickNikSo a lot of us are going to be in ATL next week for the summit.18:51
denis_makogonyup18:51
*** terryw has quit IRC18:51
*** jamie_h has quit IRC18:51
*** kgriffs is now known as kgriffs|afk18:51
SlickNikSo I'm canceling the two Trove meetings for next week, since there will be a lot going on.18:52
SlickNikWe'll meet again the week after that.18:52
dougshelley66ok18:52
cp16netsounds good18:52
SlickNikI'll send folks reminders on email / IRC.18:52
SlickNikI'll be on IRC on and off during the summit.18:52
cp16neti'll be online all the time18:53
*** esker has joined #openstack-meeting-alt18:53
cp16netdoesnt mean i will respond tho18:53
SlickNikSo if something comes up, feel free to message the trove channel.18:53
SlickNikThat's all I had to say about that. :)18:53
SlickNik#topic Open Discussion18:54
*** openstack changes topic to "Open Discussion (Meeting topic: trove)"18:54
SlickNikAny takers?18:54
amrithSlickNick ... Mid-Cycle Meetup Question18:54
*** _nadya_ has joined #openstack-meeting-alt18:55
SlickNikgo for it18:55
amrithSlickNik, I'm trying to get a list of attendees for the mid-cycle meetup. if you'll be attending, please either drop me a note email or pm.18:55
cp16netword18:55
SlickNikSounds good.18:55
cp16netamrith: is there a date for this?18:55
*** SnowDust has left #openstack-meeting-alt18:55
dougshelley66aug 20-2218:55
amrithyes, let me check. dougshelley66 may know it off top of head18:56
cp16netawesome thanks18:56
amrithyes, he does ;)18:56
cp16netis there a wiki link with more info18:56
cp16net?18:56
amrithlocation: cambridge, MA18:56
amrithno wiki link yet18:56
cp16netok coo18:56
amrithgood point18:56
amrithcp16net, coo to you too ;)18:56
cp16netsomething like we had for the last one would be good18:56
vipulamrith: you might want to do the evite thing hub_cap did18:56
vipulthat way whoever gets approved to go.. can just sign up18:56
cp16net#action amrith make a wiki page for the midcycle meetup18:57
*** NehaV has left #openstack-meeting-alt18:57
amrithcp16net, add one for eventbrite as well18:57
amrith#action that is18:57
*** NehaV has joined #openstack-meeting-alt18:57
*** megan_w|afk is now known as megan_w18:57
amrithSlickNik, ... that's it for me ...18:57
SlickNik#action amrith to set up an eventbrite event for the mid-cycle meetup18:58
amytronamrith:  if you have questions on how we planned the last one, let me know18:58
SlickNik(pro-tip: anyone can do it)18:58
SlickNikSounds good.18:58
SlickNikAnyone else?18:58
amrithamytron, thx. was going to do that.18:58
amytronSlickNik:  i made the PTL do it last time ;)18:58
*** balajiiyer1 has left #openstack-meeting-alt18:58
amytronbut you're right, anyone can do it :)18:58
SlickNikOkay, cool.18:59
SlickNik#endmeeting18:59
*** openstack changes topic to "(Meeting topic: training-manuals)"18:59
openstackMeeting ended Wed May  7 18:59:15 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
juiceslicknik: you really know how to make friends :)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-05-07-18.00.html18:59
cp16netthx18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-05-07-18.00.txt18:59
*** imsplitbit has left #openstack-meeting-alt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-05-07-18.00.log.html18:59
vipuli think the pro-tip was for the 'action' ;)18:59
vipulnot the planning amytron ;D19:00
SlickNikvipul: +1 the pro-tip was for the #action comment19:00
*** eankutse has quit IRC19:00
amytronoh haha :)19:00
*** eankutse1 has joined #openstack-meeting-alt19:00
SlickNiknot for the actual planning.19:00
amytronmy bad, SlickNik19:00
amrithvipul, thx for clarification ;)19:00
vipullol19:00
amrithdidn't realize I could do that19:00
*** tdruiva has joined #openstack-meeting-alt19:00
amrith#action SlickNick to organize mid-cycle meetup19:00
amrith;)19:00
amytronhaha19:00
amrithdamn, recorded minutes ended 1 minute ago ;)19:01
*** mat-lowery has left #openstack-meeting-alt19:01
SlickNiklol, I'll pretend I didn't see that and head back to trove.19:01
*** tdruiva has quit IRC19:01
*** tdruiva has joined #openstack-meeting-alt19:01
*** esp has left #openstack-meeting-alt19:01
SlickNikThanks all!19:02
juicethanks slicknik19:02
*** arnaud__ has joined #openstack-meeting-alt19:02
*** esker has quit IRC19:04
*** SlickNik has left #openstack-meeting-alt19:04
*** robertmyers has left #openstack-meeting-alt19:04
*** megan_w is now known as megan_w|afk19:04
*** irenab has quit IRC19:06
*** cp16net has left #openstack-meeting-alt19:06
*** arnaud__ has quit IRC19:07
*** baoli has quit IRC19:09
*** ranjitha has quit IRC19:09
*** baoli has joined #openstack-meeting-alt19:10
*** megan_w|afk is now known as megan_w19:14
*** megan_w is now known as megan_w|afk19:17
*** esker has joined #openstack-meeting-alt19:17
*** kgriffs|afk is now known as kgriffs19:22
*** tvoran has quit IRC19:22
*** dshulyak_ has quit IRC19:23
*** IlyaE has quit IRC19:25
*** _nadya_ has quit IRC19:27
*** esker has quit IRC19:28
*** tprado has quit IRC19:29
*** IlyaE has joined #openstack-meeting-alt19:30
*** kgriffs is now known as kgriffs|afk19:32
*** megan_w|afk is now known as megan_w19:32
*** amcrn has joined #openstack-meeting-alt19:33
*** andreaf has quit IRC19:34
*** megan_w is now known as megan_w|afk19:35
*** TravT has quit IRC19:40
*** nacim has joined #openstack-meeting-alt19:45
*** chuckC has joined #openstack-meeting-alt19:45
*** TravT has joined #openstack-meeting-alt19:46
*** akuznets_ has joined #openstack-meeting-alt19:47
*** dims has joined #openstack-meeting-alt19:47
*** akuznetsov has quit IRC19:48
*** esker has joined #openstack-meeting-alt19:48
*** ranjitha has joined #openstack-meeting-alt19:51
*** akuznets_ has quit IRC19:53
*** emagana has quit IRC19:58
*** SumitNaiksatam has quit IRC19:59
*** jodom has joined #openstack-meeting-alt20:05
*** jodom has joined #openstack-meeting-alt20:06
*** IlyaE has quit IRC20:06
*** ramashri has quit IRC20:07
*** caleb_ has joined #openstack-meeting-alt20:07
*** ramashri has joined #openstack-meeting-alt20:08
*** jcoufal has quit IRC20:08
*** IlyaE has joined #openstack-meeting-alt20:09
*** jrodom has quit IRC20:10
*** terryw has joined #openstack-meeting-alt20:12
*** esker has quit IRC20:13
*** caleb_ has quit IRC20:14
*** otherwiseguy has quit IRC20:14
*** caleb_ has joined #openstack-meeting-alt20:15
*** esker has joined #openstack-meeting-alt20:16
*** esker has quit IRC20:17
*** SumitNaiksatam has joined #openstack-meeting-alt20:18
*** kgriffs|afk is now known as kgriffs20:22
*** ativelkov is now known as ativelkov_away20:24
*** dtx00ff has joined #openstack-meeting-alt20:26
*** shakamunyi has quit IRC20:27
*** julim has quit IRC20:33
*** betsy has quit IRC20:36
*** spzala has joined #openstack-meeting-alt20:38
*** amcrn has quit IRC20:39
*** mwagner_ has quit IRC20:39
*** baoli has quit IRC20:40
*** Rajeev has quit IRC20:40
*** thangp has quit IRC20:40
*** terryw has quit IRC20:41
*** esker has joined #openstack-meeting-alt20:43
*** tchaypo has joined #openstack-meeting-alt20:44
*** esker has quit IRC20:44
*** jdob has quit IRC20:45
*** esker has joined #openstack-meeting-alt20:47
*** abettadapur_ has quit IRC20:48
*** jodom has quit IRC20:49
*** eankutse1 has quit IRC20:49
*** tdruiva has quit IRC20:50
*** esker has quit IRC20:51
*** esker has joined #openstack-meeting-alt20:51
*** IlyaE has quit IRC20:54
*** caleb_ has quit IRC20:54
*** dtx00ff has quit IRC20:54
*** otherwiseguy has joined #openstack-meeting-alt20:55
*** shakamunyi has joined #openstack-meeting-alt20:56
*** matrohon has quit IRC20:58
*** dtx00ff has joined #openstack-meeting-alt21:02
*** PeterSchwaller has quit IRC21:02
*** arnaud_ has joined #openstack-meeting-alt21:02
*** PeterSchwaller has joined #openstack-meeting-alt21:03
*** caleb_ has joined #openstack-meeting-alt21:04
*** caleb_` has joined #openstack-meeting-alt21:05
*** pdmars has quit IRC21:05
*** jasonb365 has quit IRC21:06
*** Haiying has joined #openstack-meeting-alt21:06
*** arnaud_ has quit IRC21:07
*** shakamunyi has quit IRC21:07
*** caleb_ has quit IRC21:08
*** krtaylor has quit IRC21:08
*** kgriffs is now known as kgriffs|afk21:09
*** jasonb365 has joined #openstack-meeting-alt21:09
*** morganfainberg has quit IRC21:11
*** morganfainberg has joined #openstack-meeting-alt21:11
*** gokrokve_ has joined #openstack-meeting-alt21:11
*** morganfainberg has quit IRC21:13
*** ativelkov_away is now known as ativelkov21:13
*** morganfainberg has joined #openstack-meeting-alt21:13
*** morganfainberg has quit IRC21:14
*** gokrokve has quit IRC21:15
*** esker has quit IRC21:16
*** morganfainberg has joined #openstack-meeting-alt21:17
*** mattgriffin is now known as mattgriffin-clou21:22
*** sballe has quit IRC21:24
*** sballe has joined #openstack-meeting-alt21:25
*** vkmc has quit IRC21:30
*** Barker has quit IRC21:31
*** ameade has quit IRC21:32
*** emagana has joined #openstack-meeting-alt21:33
*** chuckC has quit IRC21:33
*** emagana has quit IRC21:33
*** emagana has joined #openstack-meeting-alt21:34
*** NehaV has quit IRC21:36
*** zns has quit IRC21:36
*** chandan_kumar has quit IRC21:37
*** rand738 has quit IRC21:40
*** rand738 has joined #openstack-meeting-alt21:40
*** eankutse has joined #openstack-meeting-alt21:41
*** eankutse has quit IRC21:41
*** otherwiseguy has quit IRC21:41
*** eankutse has joined #openstack-meeting-alt21:41
*** shakamunyi has joined #openstack-meeting-alt21:41
*** shakayumi has joined #openstack-meeting-alt21:42
*** shakayumi has quit IRC21:42
*** markvoelker has quit IRC21:43
*** otherwiseguy has joined #openstack-meeting-alt21:43
*** michael-yu has quit IRC21:44
*** jmontemayor has quit IRC21:47
*** emagana has quit IRC21:49
*** emagana has joined #openstack-meeting-alt21:52
*** mattgriffin-clou has quit IRC21:53
*** rueb7363 has quit IRC21:56
*** luizfar has quit IRC22:00
*** betsy has joined #openstack-meeting-alt22:01
*** chuckC has joined #openstack-meeting-alt22:02
*** gokrokve_ has quit IRC22:02
*** gokrokve has joined #openstack-meeting-alt22:03
*** megan_w|afk is now known as megan_w22:03
*** esker has joined #openstack-meeting-alt22:03
*** denis_makogon has quit IRC22:05
*** dims_ has joined #openstack-meeting-alt22:05
*** ramashri has quit IRC22:06
*** chuckC has quit IRC22:07
*** dims has quit IRC22:08
*** mattgriffin has joined #openstack-meeting-alt22:10
*** NehaV has joined #openstack-meeting-alt22:12
*** megan_w is now known as megan_w|afk22:12
*** arnaud has quit IRC22:17
*** tdruiva has joined #openstack-meeting-alt22:18
*** jasonb365 has quit IRC22:22
*** gondoi is now known as zz_gondoi22:24
*** otherwiseguy has quit IRC22:25
*** jasonb365 has joined #openstack-meeting-alt22:26
*** Leon has joined #openstack-meeting-alt22:32
*** Leon is now known as Guest508822:32
*** jasonb365 has quit IRC22:35
*** Leonr has quit IRC22:35
*** otherwiseguy has joined #openstack-meeting-alt22:35
*** Guest5088 has quit IRC22:36
*** tdruiva has quit IRC22:38
*** caleb_` has quit IRC22:40
*** michael-yu has joined #openstack-meeting-alt22:41
*** zns has joined #openstack-meeting-alt22:42
*** rwsu has quit IRC22:42
*** gokrokve has quit IRC22:45
*** spzala has quit IRC22:47
*** shakamunyi has quit IRC22:51
*** dims_ has quit IRC22:53
*** ranjitha has quit IRC22:56
*** boris-42 has quit IRC22:57
*** yogesh_ has quit IRC22:57
*** yogesh_ has joined #openstack-meeting-alt22:58
*** boris-42 has joined #openstack-meeting-alt22:58
*** ativelkov is now known as ativelkov_away22:59
*** ativelkov_away is now known as ativelkov22:59
*** david-lyle has quit IRC22:59
*** ativelkov is now known as ativelkov_away22:59
*** ativelkov_away is now known as ativelkov23:00
*** gduan has quit IRC23:00
*** garyduan has joined #openstack-meeting-alt23:01
*** chuckC has joined #openstack-meeting-alt23:01
*** banix has quit IRC23:02
*** yogesh_ has quit IRC23:02
*** ranjitha has joined #openstack-meeting-alt23:03
*** david-ly_ has joined #openstack-meeting-alt23:03
*** mwagner_ has joined #openstack-meeting-alt23:03
*** emagana has quit IRC23:04
*** ativelkov is now known as ativelkov_away23:05
*** dtx00ff has quit IRC23:05
*** dtx00ff has joined #openstack-meeting-alt23:07
*** jcru has quit IRC23:08
*** gokrokve has joined #openstack-meeting-alt23:10
*** kevinconway has quit IRC23:11
*** overlayer has joined #openstack-meeting-alt23:12
*** dtx00ff has quit IRC23:12
*** carl_baldwin has quit IRC23:13
*** overlayer has quit IRC23:14
*** dtx00ff has joined #openstack-meeting-alt23:16
*** atiwari has quit IRC23:17
*** atiwari has joined #openstack-meeting-alt23:18
*** otherwiseguy has quit IRC23:24
*** dims_ has joined #openstack-meeting-alt23:27
*** dims_ has quit IRC23:30
*** dims has joined #openstack-meeting-alt23:30
*** dims has quit IRC23:31
*** ranjitha has quit IRC23:33
*** dims has joined #openstack-meeting-alt23:34
*** flaper87 is now known as flaper87|afk23:34
*** jecarey has quit IRC23:35
*** ranjitha has joined #openstack-meeting-alt23:37
*** dims has quit IRC23:40
*** dims has joined #openstack-meeting-alt23:41
*** IlyaE has joined #openstack-meeting-alt23:42
*** beyounn has joined #openstack-meeting-alt23:43
*** dims has quit IRC23:45
*** tildedave_laptop has left #openstack-meeting-alt23:45
*** dims has joined #openstack-meeting-alt23:46
*** mattgriffin has quit IRC23:47
*** dims has quit IRC23:48
*** dims has joined #openstack-meeting-alt23:48
*** dims has quit IRC23:49
*** dims has joined #openstack-meeting-alt23:50
*** caleb_ has joined #openstack-meeting-alt23:51
*** james_li has joined #openstack-meeting-alt23:52
*** beyounn has quit IRC23:54
*** david-ly_ has quit IRC23:55
*** IlyaE has quit IRC23:56
*** atiwari has quit IRC23:58

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