Wednesday, 2013-12-04

*** alazarev has joined #openstack-meeting-alt00:03
*** rongze has quit IRC00:04
*** gokrokve has quit IRC00:05
*** flaper87 is now known as flaper87|afk00:09
*** amytron has quit IRC00:09
*** boris-42 has quit IRC00:14
*** alazarev has quit IRC00:14
*** nati_ueno has joined #openstack-meeting-alt00:18
*** brents has quit IRC00:19
*** nati_uen_ has quit IRC00:21
*** vipul is now known as vipul-away00:27
*** brents has joined #openstack-meeting-alt00:29
*** sarob has quit IRC00:32
*** nati_ueno has quit IRC00:33
*** sarob has joined #openstack-meeting-alt00:33
*** sarob has quit IRC00:37
*** vipul-away is now known as vipul00:40
*** openstack has joined #openstack-meeting-alt00:46
*** ChanServ sets mode: +o openstack00:46
*** kgriffs is now known as kgriffs_afk00:50
*** sacharya1 has joined #openstack-meeting-alt00:55
*** sarob has joined #openstack-meeting-alt00:55
*** IlyaE has quit IRC00:56
*** sacharya has joined #openstack-meeting-alt00:58
*** sacharya1 has quit IRC00:59
*** aratim has joined #openstack-meeting-alt01:00
*** alazarev has joined #openstack-meeting-alt01:00
*** yogesh has joined #openstack-meeting-alt01:05
*** aratim1 has joined #openstack-meeting-alt01:08
*** gokrokve has joined #openstack-meeting-alt01:09
*** aratim has quit IRC01:10
*** sarob has quit IRC01:11
*** sarob has joined #openstack-meeting-alt01:12
*** sarob has quit IRC01:16
*** brents has quit IRC01:17
*** julim has quit IRC01:22
*** nati_ueno has joined #openstack-meeting-alt01:26
*** yogesh has quit IRC01:29
*** nati_ueno has quit IRC01:32
*** nati_ueno has joined #openstack-meeting-alt01:32
*** noslzzp has joined #openstack-meeting-alt01:32
*** nati_ueno has quit IRC01:33
*** nati_ueno has joined #openstack-meeting-alt01:33
*** nosnos has joined #openstack-meeting-alt01:35
*** nosnos_ has joined #openstack-meeting-alt01:37
*** mozawa has joined #openstack-meeting-alt01:38
*** colinmcnamara has quit IRC01:40
*** colinmcn_ has quit IRC01:40
*** nosnos has quit IRC01:40
*** banix has joined #openstack-meeting-alt01:43
*** alazarev has quit IRC01:50
*** alazarev has joined #openstack-meeting-alt01:51
*** rongze has joined #openstack-meeting-alt02:01
*** rongze has quit IRC02:01
*** rongze has joined #openstack-meeting-alt02:02
*** banix has quit IRC02:04
*** alazarev has quit IRC02:06
*** twoputt_ has quit IRC02:06
*** banix has joined #openstack-meeting-alt02:06
*** twoputt__ has quit IRC02:06
*** tanisdl has quit IRC02:14
*** ruhe has joined #openstack-meeting-alt02:18
*** fungi has quit IRC02:24
*** fungi has joined #openstack-meeting-alt02:26
*** colinmcnamara has joined #openstack-meeting-alt02:31
*** colinmcn_ has joined #openstack-meeting-alt02:31
*** rwsu has quit IRC02:35
*** esker has joined #openstack-meeting-alt02:35
*** rwsu has joined #openstack-meeting-alt02:39
*** MarkAtwood has quit IRC02:49
*** jaypipes has quit IRC02:57
*** ruhe has quit IRC03:01
*** jjmb has joined #openstack-meeting-alt03:09
*** MarkAtwood has joined #openstack-meeting-alt03:12
*** MarkAtwood has quit IRC03:13
*** MarkAtwood has joined #openstack-meeting-alt03:13
*** vipul has quit IRC03:15
*** vipul has joined #openstack-meeting-alt03:16
*** shadower_ has joined #openstack-meeting-alt03:16
*** enikanorov__ has joined #openstack-meeting-alt03:17
*** shadower has quit IRC03:17
*** harlowja has quit IRC03:19
*** enikanorov_ has quit IRC03:20
*** esker has quit IRC03:34
*** rraja has joined #openstack-meeting-alt03:39
*** IlyaE has joined #openstack-meeting-alt03:53
*** morazi has quit IRC03:53
*** amotoki has joined #openstack-meeting-alt03:55
*** betsy has joined #openstack-meeting-alt03:58
*** sergmelikyan has quit IRC04:04
*** nati_ueno has quit IRC04:08
*** rraja has quit IRC04:19
*** MarkAtwood has quit IRC04:23
*** flwang has quit IRC04:33
*** IlyaE has quit IRC04:34
*** banix has quit IRC04:38
*** nosnos has joined #openstack-meeting-alt04:38
*** coolsvap has joined #openstack-meeting-alt04:40
*** nosnos_ has quit IRC04:42
*** banix has joined #openstack-meeting-alt04:44
*** rongze has quit IRC04:45
*** coolsvap has quit IRC04:47
*** noslzzp has quit IRC04:51
*** FallenPegasus has joined #openstack-meeting-alt04:52
*** SergeyLukjanov has joined #openstack-meeting-alt04:56
*** SergeyLukjanov is now known as _SergeyLukjanov04:57
*** _SergeyLukjanov is now known as SergeyLukjanov04:57
*** igormarnat__ has joined #openstack-meeting-alt04:58
*** coolsvap has joined #openstack-meeting-alt05:01
*** venkatesh has joined #openstack-meeting-alt05:11
*** coolsvap has quit IRC05:15
*** rongze has joined #openstack-meeting-alt05:16
*** yjiang5_1 has joined #openstack-meeting-alt05:17
*** venkatesh_ has joined #openstack-meeting-alt05:22
*** stevebaker has quit IRC05:22
*** yjiang5 has quit IRC05:22
*** venkatesh has quit IRC05:22
*** sfineberg has quit IRC05:22
*** ttx has quit IRC05:22
*** ttx has joined #openstack-meeting-alt05:22
*** stevebaker has joined #openstack-meeting-alt05:22
*** ttx has quit IRC05:22
*** ttx has joined #openstack-meeting-alt05:22
*** sfineberg has joined #openstack-meeting-alt05:23
*** yogesh has joined #openstack-meeting-alt05:28
*** rongze has quit IRC05:28
*** amotoki has quit IRC05:30
*** MarkAtwood has joined #openstack-meeting-alt05:36
*** aignatov has joined #openstack-meeting-alt05:36
*** brents has joined #openstack-meeting-alt05:37
*** igormarnat__ has quit IRC05:37
*** FallenPegasus has quit IRC05:38
*** aratim has joined #openstack-meeting-alt05:38
*** igormarnat_ has joined #openstack-meeting-alt05:41
*** aratim1 has joined #openstack-meeting-alt05:44
*** igormarnat_ has quit IRC05:44
*** aratim has quit IRC05:45
*** yogesh has quit IRC05:47
*** yogesh has joined #openstack-meeting-alt05:48
*** flwang has joined #openstack-meeting-alt05:48
*** colinmcnamara has quit IRC05:49
*** colinmcn_ has quit IRC05:49
*** rraja has joined #openstack-meeting-alt05:50
*** yogesh has quit IRC05:52
*** aratim1 has quit IRC05:53
*** aratim has joined #openstack-meeting-alt05:56
*** ashaikh has joined #openstack-meeting-alt05:57
*** rongze has joined #openstack-meeting-alt05:58
*** banix has quit IRC05:59
*** SergeyLukjanov has quit IRC06:04
*** SergeyLukjanov has joined #openstack-meeting-alt06:05
*** yogeshmehra has joined #openstack-meeting-alt06:05
*** aratim has quit IRC06:07
*** SergeyLukjanov has quit IRC06:07
*** aratim has joined #openstack-meeting-alt06:09
*** amcrn has quit IRC06:21
*** aratim1 has joined #openstack-meeting-alt06:26
*** aratim has quit IRC06:26
*** gokrokve has quit IRC06:26
*** rongze has quit IRC06:30
*** rongze has joined #openstack-meeting-alt06:30
*** nosnos has quit IRC06:34
*** nosnos has joined #openstack-meeting-alt06:35
*** sacharya has quit IRC06:35
*** rraja has quit IRC06:36
*** brents has quit IRC06:41
*** jcooley_ has joined #openstack-meeting-alt06:41
*** sarob has joined #openstack-meeting-alt06:42
*** akuznetsov has quit IRC06:44
*** alazarev has joined #openstack-meeting-alt06:44
*** gokrokve has joined #openstack-meeting-alt06:47
*** gokrokve has quit IRC06:48
*** gokrokve has joined #openstack-meeting-alt06:48
*** rraja has joined #openstack-meeting-alt06:49
*** jcooley_ has quit IRC06:51
*** boris-42 has joined #openstack-meeting-alt06:51
*** nati_ueno has joined #openstack-meeting-alt06:52
*** gokrokve has quit IRC06:53
*** SergeyLukjanov has joined #openstack-meeting-alt06:55
*** akuznetsov has joined #openstack-meeting-alt06:58
*** denis_makogon has joined #openstack-meeting-alt06:58
*** alazarev has quit IRC06:59
*** MarkAtwood has quit IRC07:02
*** aratim1 has quit IRC07:05
*** nosnos_ has joined #openstack-meeting-alt07:05
*** nosnos has quit IRC07:08
*** akuznetsov has quit IRC07:08
*** nati_ueno has quit IRC07:10
*** rraja has quit IRC07:21
*** alazarev has joined #openstack-meeting-alt07:23
*** rwsu has quit IRC07:24
*** sarob has quit IRC07:25
*** sarob has joined #openstack-meeting-alt07:25
*** lsmola has joined #openstack-meeting-alt07:26
*** venkatesh_ has quit IRC07:27
*** jtomasek has joined #openstack-meeting-alt07:29
*** sarob has quit IRC07:30
*** yogeshmehra has quit IRC07:33
*** amotoki has joined #openstack-meeting-alt07:33
*** jtomasek has quit IRC07:34
*** jtomasek has joined #openstack-meeting-alt07:37
*** yogeshmehra has joined #openstack-meeting-alt07:38
*** igormarnat_ has joined #openstack-meeting-alt07:47
*** gokrokve has joined #openstack-meeting-alt07:47
*** thouveng has joined #openstack-meeting-alt07:48
*** SergeyLukjanov has quit IRC07:48
*** rwsu has joined #openstack-meeting-alt07:48
*** alazarev has quit IRC07:50
*** gokrokve has quit IRC07:52
*** sarob has joined #openstack-meeting-alt07:56
*** aratim has joined #openstack-meeting-alt07:57
*** arborism has joined #openstack-meeting-alt07:58
*** flaper87|afk is now known as flaper8707:59
*** arborism is now known as amcrn08:00
*** aratim has quit IRC08:01
*** sarob has quit IRC08:18
*** nosnos_ has quit IRC08:19
*** nosnos has joined #openstack-meeting-alt08:19
*** inkerra has quit IRC08:20
*** metabro has quit IRC08:20
*** GheRivero has quit IRC08:22
*** inkerra has joined #openstack-meeting-alt08:22
*** metabro has joined #openstack-meeting-alt08:22
*** ashaikh has quit IRC08:29
*** markwash has quit IRC08:29
*** markmcclain has joined #openstack-meeting-alt08:33
*** SergeyLukjanov has joined #openstack-meeting-alt08:38
*** amcrn has quit IRC08:39
*** venkatesh has joined #openstack-meeting-alt08:39
*** arborism has joined #openstack-meeting-alt08:40
*** boris-42 has quit IRC08:40
*** denis_makogon has quit IRC08:41
*** SergeyLukjanov has quit IRC08:49
*** gokrokve has joined #openstack-meeting-alt08:49
*** aratim has joined #openstack-meeting-alt08:52
*** gokrokve has quit IRC08:53
*** rraja has joined #openstack-meeting-alt08:58
*** jcoufal has joined #openstack-meeting-alt08:58
*** venkatesh has quit IRC09:05
*** amotoki has quit IRC09:08
*** fesp has joined #openstack-meeting-alt09:09
*** funzo has quit IRC09:12
*** flaper87 has quit IRC09:12
*** clarkb has quit IRC09:12
*** fesp is now known as flaper8709:12
*** markmcclain has quit IRC09:13
*** flaper87 has quit IRC09:13
*** flaper87 has joined #openstack-meeting-alt09:13
*** akuznetsov has joined #openstack-meeting-alt09:14
*** derekh has joined #openstack-meeting-alt09:15
*** sarob has joined #openstack-meeting-alt09:17
*** clarkb has joined #openstack-meeting-alt09:19
*** SergeyLukjanov has joined #openstack-meeting-alt09:22
*** mozawa has quit IRC09:25
*** rsblendido has joined #openstack-meeting-alt09:29
*** rossella_s has joined #openstack-meeting-alt09:29
*** dmakogon_ is now known as denis_makogon09:31
*** sarob has quit IRC09:31
*** nadya_ has joined #openstack-meeting-alt09:33
*** duyanhong has joined #openstack-meeting-alt09:34
*** rraja has quit IRC09:38
*** nadya_ has quit IRC09:39
*** jtomasek has quit IRC09:43
*** jtomasek has joined #openstack-meeting-alt09:43
*** duyahong has joined #openstack-meeting-alt09:44
*** duyahong is now known as yahongdu09:45
*** boris-42 has joined #openstack-meeting-alt09:46
yahongdunext meeting is on tomorrow?09:46
*** gokrokve has joined #openstack-meeting-alt09:47
*** colinmcnamara has joined #openstack-meeting-alt09:50
*** colinmcn_ has joined #openstack-meeting-alt09:50
*** gokrokve has quit IRC09:52
*** colinmcn_ has quit IRC09:54
*** colinmcnamara has quit IRC09:54
*** rraja has joined #openstack-meeting-alt09:55
*** sarob has joined #openstack-meeting-alt09:56
*** duyanhong has quit IRC10:02
*** nosnos_ has joined #openstack-meeting-alt10:03
*** yogeshmehra has quit IRC10:06
*** nosnos has quit IRC10:06
*** flwang has quit IRC10:07
*** nadya_ has joined #openstack-meeting-alt10:13
*** nadya_ has quit IRC10:14
*** aratim has quit IRC10:22
*** markmcclain has joined #openstack-meeting-alt10:22
*** aratim has joined #openstack-meeting-alt10:23
*** sarob has quit IRC10:30
*** aignatov has quit IRC10:31
*** markmcclain has quit IRC10:35
*** markmcclain has joined #openstack-meeting-alt10:35
*** nati_ueno has joined #openstack-meeting-alt10:37
*** jog0 has left #openstack-meeting-alt10:38
*** aratim has quit IRC10:39
*** NikitaKonovalov has joined #openstack-meeting-alt10:39
*** nadya_ has joined #openstack-meeting-alt10:41
*** rraja has quit IRC10:46
*** gokrokve has joined #openstack-meeting-alt10:48
*** aignatov has joined #openstack-meeting-alt10:50
*** rongze has quit IRC10:53
*** gokrokve has quit IRC10:53
*** sarob has joined #openstack-meeting-alt10:56
*** nadya_ has quit IRC11:07
*** rongze has joined #openstack-meeting-alt11:11
*** SergeyLukjanov has quit IRC11:12
*** tsufiev has quit IRC11:23
*** sarob has quit IRC11:28
*** SergeyLukjanov has joined #openstack-meeting-alt11:43
*** jergerber has quit IRC11:43
*** nadya_ has joined #openstack-meeting-alt11:45
*** rongze has quit IRC11:45
*** gokrokve has joined #openstack-meeting-alt11:49
*** rongze has joined #openstack-meeting-alt11:51
*** jjmb has quit IRC11:52
*** gokrokve has quit IRC11:53
*** jjmb has joined #openstack-meeting-alt11:54
*** sarob has joined #openstack-meeting-alt11:56
*** jjmb has quit IRC11:58
*** nadya_ has quit IRC12:23
*** denis_makogon is now known as bot-bot12:24
*** sarob has quit IRC12:28
*** ErikB has joined #openstack-meeting-alt12:32
*** enikanorov_ has joined #openstack-meeting-alt12:35
*** flwang has joined #openstack-meeting-alt12:37
*** enikanorov has quit IRC12:38
*** SergeyLukjanov is now known as _SergeyLukjanov12:42
*** _SergeyLukjanov has quit IRC12:42
*** shadower_ is now known as shadower12:43
*** gokrokve has joined #openstack-meeting-alt12:50
*** igormarnat_ has quit IRC12:52
*** jcoufal has quit IRC12:52
*** rraja has joined #openstack-meeting-alt12:53
*** akuznetsov has quit IRC12:53
*** igormarnat_ has joined #openstack-meeting-alt12:53
*** arborism has quit IRC12:54
*** gokrokve has quit IRC12:54
*** akuznetsov has joined #openstack-meeting-alt12:56
*** sarob has joined #openstack-meeting-alt12:56
*** jcoufal has joined #openstack-meeting-alt12:57
*** tedross has joined #openstack-meeting-alt12:57
*** jprovazn has joined #openstack-meeting-alt12:58
*** pdmars has joined #openstack-meeting-alt13:03
*** dprince has joined #openstack-meeting-alt13:03
*** SergeyLukjanov has joined #openstack-meeting-alt13:05
*** nosnos_ has quit IRC13:07
*** nosnos has joined #openstack-meeting-alt13:08
*** NikitaKonovalov has quit IRC13:08
*** yamahata_ has joined #openstack-meeting-alt13:09
*** akuznetsov has quit IRC13:13
*** jdob has joined #openstack-meeting-alt13:14
*** ruhe has joined #openstack-meeting-alt13:15
*** akuznetsov has joined #openstack-meeting-alt13:16
*** aratim has joined #openstack-meeting-alt13:17
*** aratim1 has joined #openstack-meeting-alt13:24
*** aratim has quit IRC13:27
*** aignatov has quit IRC13:27
*** sarob has quit IRC13:29
*** aignatov has joined #openstack-meeting-alt13:31
*** venkatesh has joined #openstack-meeting-alt13:37
*** noslzzp has joined #openstack-meeting-alt13:38
*** venkatesh has quit IRC13:38
*** markmcclain has quit IRC13:38
*** noslzzp has quit IRC13:39
*** noslzzp has joined #openstack-meeting-alt13:39
*** nosnos has quit IRC13:39
*** NikitaKonovalov has joined #openstack-meeting-alt13:40
*** ruhe is now known as ruhe_13:41
*** mozawa has joined #openstack-meeting-alt13:41
*** irenab_ has joined #openstack-meeting-alt13:44
*** igormarnat_ has quit IRC13:44
*** ruhe_ is now known as ruhe13:44
*** aratim has joined #openstack-meeting-alt13:47
*** aratim1 has quit IRC13:47
*** irenab_ has quit IRC13:47
*** irenab has joined #openstack-meeting-alt13:47
*** igormarnat_ has joined #openstack-meeting-alt13:50
*** devkulkarni has joined #openstack-meeting-alt13:50
*** gokrokve has joined #openstack-meeting-alt13:50
*** gokrokve has quit IRC13:55
*** sarob has joined #openstack-meeting-alt13:56
*** sadasu has joined #openstack-meeting-alt13:57
*** aratim has quit IRC13:58
*** ZangMingJie has joined #openstack-meeting-alt14:00
sadasu#startmeeting PCI passthrough14:00
openstackMeeting started Wed Dec  4 14:00:48 2013 UTC and is due to finish in 60 minutes.  The chair is sadasu. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: PCI passthrough)"14:00
openstackThe meeting name has been set to 'pci_passthrough'14:00
*** itzikb has joined #openstack-meeting-alt14:01
*** markmcclain has joined #openstack-meeting-alt14:02
*** baoli has joined #openstack-meeting-alt14:02
*** pcm_ has joined #openstack-meeting-alt14:03
*** SushilKM has joined #openstack-meeting-alt14:03
sadasuIs Yongli there?14:04
*** julim has joined #openstack-meeting-alt14:05
*** rraja has quit IRC14:05
*** skostiuchenko has joined #openstack-meeting-alt14:05
sadasubaoli: are we primarily waiting for Yongli to join?14:06
*** yuyangbj has joined #openstack-meeting-alt14:06
*** skostiuchenko has left #openstack-meeting-alt14:06
baoliyes, waiting for everyone to join14:06
*** tedross has left #openstack-meeting-alt14:06
*** yuyangbj has left #openstack-meeting-alt14:06
irenabbaoli: can you please share the topics for today?14:07
*** yamahata_ has quit IRC14:07
*** yamahata_ has joined #openstack-meeting-alt14:07
*** Brian_ has joined #openstack-meeting-alt14:08
baoli@irenab, I'd like to go over the design with Yongli, that's why I changed the meeting time14:08
sadasuI think the latest entry in the google doc says that Yongli will not be able to attend14:08
baoliwe have email communication, and he said he would join14:10
irenabbaoli: in case Yongli is not going to join in few minutes, may we discuss the neutron related part?14:10
baoliabsolutely. And I also want to discuss port profile14:11
irenabbaoli: great14:11
*** heyongli has joined #openstack-meeting-alt14:11
baoliLooks like Yongli just joined14:12
sadasuHello Yongli!14:12
irenabHi!14:12
heyonglihello14:12
heyonglisorry for later,14:12
sadasu#topic PCI alias14:12
*** openstack changes topic to "PCI alias (Meeting topic: PCI passthrough)"14:12
baoliNot sure if Yunhong would join, it's too early for him14:12
baoliSo let's get started14:12
*** markmcclain has quit IRC14:12
heyonglisummary work of me:  split nova bp, coding in the way14:13
sadasuhow are u splitting nova BP?14:14
*** skostiuchenko has joined #openstack-meeting-alt14:14
irenabheyongli: Can you please share the link to blueprints?14:14
*** rongze has quit IRC14:14
baoliFirst of all,device 'class' or 'feature' auto-discovery. Can we do it?14:15
heyonglisplit the database and API for config to stand alone bp which denpd on pci-extra(sriov support)14:15
heyonglifor now, the featrue auto discovery is hard to push if libvirt can not suppprt it14:15
baoli@heyongli, it doesn't have to depend on libvirt14:16
heyongli@bali, yeah, but if we want to support it from native linux, there is much hard work to solve14:16
baoliCan you describe what it is?14:17
*** rongze has joined #openstack-meeting-alt14:18
heyongliauto discovery plus native linux script is hard push to libvirt of nova i think14:18
baoliWell, if we agree it can/should be done, we can create a new BP and get it done by someone14:19
sadasuheyongli: what support do you need from libvirt to make auto discovery work?14:19
heyonglidevice-type  or the feature auto discovery by libvirt14:20
baoliWell, it doesn't need to use libvirt, right?14:21
baoliAny reason that it has to depend on libvirt to provide it?14:21
heyongli@baoli, yeah, it's possible by another way, but seems not same style code like current: all come from libvit, but there does some code use native linux facility14:22
baoliSo, it can be done with native linux support.14:23
*** SushilKM has quit IRC14:23
baoliShall we vote on that?14:23
itzikb@baoli: What is the linux native way?14:24
heyonglii'm not againt to support it not by libvirt, and if we want, this is will little bigger work, and we should make it as a further work, or the next step14:24
heyonglii mean , in icehouse at least the icehose2, we won't have it14:24
baoli@itzikb, we've discussed that we can use information from /sys/class/net and libvirt to find out the type of a pci device14:25
itzikb@baoli: I thought that I can find the information from libvirt but I was mistaken14:26
baoliSecondly, how to name a pci group. The doc suggested to use the format feature:[name]14:26
heyongliwhy use feature as the key? i think group is straitforward but this is minor14:27
*** stackKid has joined #openstack-meeting-alt14:27
itzikb@baoli: Can you please clarify how do you get the information from /sys/class/net ( or refet to a doc) ?14:27
baoli@itzikb, I don't have it offhand. But let's discuss it offline14:28
heyonglicat /sys/class/net/eth0/address we get :00:1d:7d:d6:f8:f514:28
baoli@heyongli, the idea is that one don't have to provide a group name but use the feautre itself14:28
irenabheyongli: we get from the link the PCI address, right?14:29
heyonglithis is binding to feautre, but this is not nessary , what if you want sub group of a feature, we need group again14:30
heyongli@irenab, address in that dir is a regular file14:30
*** sarob has quit IRC14:30
baoli@heyongli, what do you think how feature auto discovery will be used?14:31
heyongliwe should use group for pure group , and after we finished autodiscorvery the feature, the 'feature' can be another group key through the configuration14:32
heyongliwe don't change anything about group logic in this way14:32
heyongli@baoli, you  guy want use feature as a request spec , are you?14:33
baoli@heyongli, in some cases, a 'group' doesn't have to be specified14:34
baoliDo you want to define predefined features? You said 'group key throught configuration'14:34
heyonglii want the group finnally hold the regular express for address14:34
heyongligroup is the key, and it's value to define the group name, define anythin you want ,this is admin's choice14:35
heyonglifor now, grouping just use key 'vendor' and 'product'14:36
baoliWell, with auto discovery, it makes sense to predefine features.14:36
heyongliyeah, when auto discovery done 'feature' key is ready to use14:36
heyongliin new config option say pci-group-key you define ['feature'], then device group as feature , is this what you want ?14:37
baoli@heyongli, it is in the doc. But we want to know if you agree, or in your mind, how it should be done14:38
heyongligroup  with 'group' key is much flexable, we support 'group' in first version14:39
heyonglithen we do feature auto discovery14:39
heyongliand then you can use the 'feature' as group key without change the code again14:39
*** bill_az has joined #openstack-meeting-alt14:42
heyonglihow do you think about this approach , @baoli14:42
baoli@heyongli, we can do it in a different phase. Can you modify the doc to clearly describe your approach if there is anyt difference from the doc?14:43
*** igormarnat_ has quit IRC14:43
sadasuheyongli: and this becomes part of whitelist specified on each compute node14:43
heyonglithis is make sense for align to the time deadline, and we get flexable way to group, and decouple the grouping itself from feature, this is why i try to persuade you guy do thing in this way14:44
heyongli@sadasu, ok i will update the auto discovery feature part14:44
*** igormarnat__ has joined #openstack-meeting-alt14:45
irenabheyongli: we just need to keep in mind the work that admin should do and try to minimize it14:45
heyongli@sadasu, we want address, then it's local to compute node, but the featue does not must be local14:45
baoli@heyongli, please use a different section to describe your approach.14:45
heyongli@irenab, minimize what? the config size or keep it not local?14:46
heyongli@baoli, sure14:46
baoliOk, let's move on14:46
heyonglithe group method i updated is clear?14:46
irenabheyongly: minimize manual configration operations he need to do14:46
heyongli@irenab, yeah, feature can be global it's good thing14:47
baoli@heyongli, I am not sure how much difference there is14:47
sadasuheyongli: yes. now, with this, what do we need on the controller node?14:48
*** ErikB has quit IRC14:48
*** colinmcnamara has joined #openstack-meeting-alt14:48
*** colinmcn_ has joined #openstack-meeting-alt14:48
heyongli@sadasu, i'm not clear what you mean, define the featue on controller?14:48
sadasuheyongli: is the whitelist on the compute node, the only config file needed now?14:49
heyongli@baoli, group and the feature?  i much prefer make group is general way to group, feature is bind to the property of pci device14:49
heyongli@sadasu, i should check this, but in my picture it should be(not sure)14:50
baoli@heyongli, that's agreed. But we say the group can be denoted as feature:[group]14:50
*** alazarev has joined #openstack-meeting-alt14:51
heyongli@baoli, i don't think so, featue as you desc, it's pci's property not for anything14:51
*** gokrokve has joined #openstack-meeting-alt14:51
irenabheyongli: Do we still need alias definition at Controller and Flavor for SRIOV NIC?14:51
heyongliand 'feature' is the key in the spec, group just a value,14:51
heyongli@irenab, alias is always needed14:52
irenabheyongli: and what about flavor extra_spec?14:52
heyongliif remove alias, pci pass-through is totally re designed .14:53
baoli@heyongli, I suggest that you come up with a doc that describes how it should be done with your approach.14:53
baoli@heyongli, I don't think alias is the key of the current design14:53
heyongli@baoli, i had done in a wiki page14:53
baoliand implemenation14:53
baoli@heyongli, I've read it, but I don't think that it has the details that we need14:54
irenabdo we want to support NIC hot plug case?14:54
heyongli@baoli, if no alias, you need specify a spec with out name14:54
heyongli@baoli, what missed? let me add it14:54
irenabheyongli: how hot plug will be supported with flavor havinged predefined number of requested PCI devices?14:55
heyongli@irenab, what work should be done for hotplug?14:55
baoli@heyongli, please post your wiki url so that everyone else can read it. I actually got it from your comments, but not have it offhand14:55
*** gokrokve has quit IRC14:55
heyongli@baoli, my home access that wiki is buggy i will update it to your google doc14:56
*** sarob has joined #openstack-meeting-alt14:56
*** lblanchard has joined #openstack-meeting-alt14:56
irenabheyongli: once VM is rnning, you want to attach it aditional SRIOV vNIC. I am not sure, but seems that current approach does not allow it14:56
heyongli@irenab, is there support by nova?14:57
*** jtomasek has quit IRC14:57
sadasu@irenab: current approach doesn't support that. Do u need that?14:58
irenabheyongli: Yes. I just want to be sure that nova approach regarding PCI passthrough will enable this use case14:58
*** RobinWang has joined #openstack-meeting-alt14:58
heyongli@irenab, i'm not sure if nova let us do it, i know resize might work but not in a active vm14:58
heyongli@irenab, i don't see a way to do that now, i might be wrong, i just don't know14:59
irenabheyongli: just wanted to see that going with flavor approach won't eliminate the abbility to add NIC15:00
*** yjiang5 has joined #openstack-meeting-alt15:01
*** DennyZhang has joined #openstack-meeting-alt15:01
heyongli@yjiang5, what do you know about hotplug?15:01
irenabseems the meeting time is over. same time next week?15:01
*** IlyaE has joined #openstack-meeting-alt15:01
yjiang5hmm, I remember the meeting is UTC15 in the mail?15:01
heyongli@irenab, sure15:01
sadasu@irenab: You asked for Tuesdays right?15:01
*** jtomasek has joined #openstack-meeting-alt15:02
irenabsadasu: its preferable, but not must15:02
heyonglihttps://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support#tracking_device_allocated_to_alias15:02
heyonglimy design link15:02
sadasu#link https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support#tracking_device_allocated_to_alias15:02
sadasuheyongli: thanks15:02
sadasu#endmeeting15:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:02
openstackMeeting ended Wed Dec  4 15:02:56 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2013/pci_passthrough.2013-12-04-14.00.html15:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2013/pci_passthrough.2013-12-04-14.00.txt15:03
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2013/pci_passthrough.2013-12-04-14.00.log.html15:03
*** jtomasek has quit IRC15:07
*** kgriffs_afk is now known as kgriffs15:07
*** devkulkarni has quit IRC15:09
*** rraja has joined #openstack-meeting-alt15:09
*** markwash has joined #openstack-meeting-alt15:09
*** Swami has joined #openstack-meeting-alt15:10
Swamihi15:11
*** irenab has quit IRC15:11
SwamiRobin wang: ping15:11
*** aignatov has quit IRC15:11
*** colinmcnamara has quit IRC15:11
*** colinmcn_ has quit IRC15:11
*** dteselkin has quit IRC15:11
*** markmcclain has joined #openstack-meeting-alt15:11
RobinWangHi Swami15:12
Swamihi RobinWang15:12
RobinWanglong time no see :)15:12
SwamiJust waiting for you15:12
*** jtomasek has joined #openstack-meeting-alt15:12
Swami#startmeeting Distributed_virtual_router15:12
openstackMeeting started Wed Dec  4 15:12:58 2013 UTC and is due to finish in 60 minutes.  The chair is Swami. Information about MeetBot at http://wiki.debian.org/MeetBot.15:12
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:13
*** openstack changes topic to " (Meeting topic: Distributed_virtual_router)"15:13
openstackThe meeting name has been set to 'distributed_virtual_router'15:13
RobinWangI've just replied your email15:13
*** igormarnat__ has quit IRC15:13
Swami#topic Distributed Virtual Router East-West Discussion15:13
*** openstack changes topic to "Distributed Virtual Router East-West Discussion (Meeting topic: Distributed_virtual_router)"15:13
RobinWangI agree with choosing existing OVS infrastructure as our first step, to accelerate this feature15:14
*** igormarnat__ has joined #openstack-meeting-alt15:14
SwamiRobin: For East West Distributed Router we are planning to move away from the Kernel Module15:14
Swami#agreed15:14
RobinWangI read previous meeting minutes and logs, glad to see that we moved forward far beyond just optimizing East-West Traffic15:15
SwamiRobin:Your prototype that you did for running the performance test includes the OVS infrastructure only is it right?15:16
RobinWangyes, that's right15:16
*** SergeyLukjanov is now known as _SergeyLukjanov15:16
SwamiYes we wanted to consider both options and so we went forward investigating those options15:16
RobinWangwe leveraging ovs, and didn't add extra ovs br15:16
*** _SergeyLukjanov has quit IRC15:16
*** Swami has quit IRC15:16
*** Brian_ has quit IRC15:16
*** baoli has quit IRC15:16
*** itzikb has quit IRC15:16
*** sadasu has quit IRC15:16
*** ywu has quit IRC15:16
RobinWangjust15:17
*** eankutse has joined #openstack-meeting-alt15:17
*** eankutse has quit IRC15:18
*** eankutse has joined #openstack-meeting-alt15:18
*** shivh has joined #openstack-meeting-alt15:18
RobinWangSwami, r u still on line? I saw a quit information15:18
*** Swami has joined #openstack-meeting-alt15:18
Swamihi15:18
SwamiRobinwang; still there, I got disconnected15:19
RobinWanghi15:19
RobinWangI saw the info :)15:19
*** denis_makogon has joined #openstack-meeting-alt15:19
*** heyongli has quit IRC15:19
SwamiSo my question was that, for the prototype that you did, do you have any WIP code that can publish15:19
RobinWangsure15:20
RobinWangthe code is based on Grizzly, just a draft15:21
RobinWangthe mechanism is very simple15:21
SwamiThat's ok,15:21
Swamiwe can go through the code and then refactor the code for the Havana15:21
*** venkatesh has joined #openstack-meeting-alt15:21
SwamiAlso if we need to make any minor changes we can do that15:21
*** venkatesh has quit IRC15:21
RobinWangsure, but I think we might need some non-trivial changes on it15:22
RobinWanghowever, the mechanism is the same15:23
*** shivh has quit IRC15:23
Swamiyes, that's fine, I can review the code and then we can make changes if need15:23
*** alazarev has quit IRC15:23
RobinWangas you pictured in spec doc, there should be a brain to store East-West routing info15:24
SwamiAlso can you capture your design notes in the google doc or on the Wiki page so that we can add more content to it15:24
*** amytron has joined #openstack-meeting-alt15:24
RobinWangto make the POC simple, we didn't put it into l3-agent or some other places15:24
SwamiYes, right now we were thinking of extending the L3 plugin to be the brain15:25
RobinWangthose info is maintained in ovs plugin15:25
RobinWangI think we should figure out where is appropriate to put those data and implementing the logic15:26
SwamiYes you are right, those are L2 parameters, but still we wanted to push it to the L3 plugin and store it15:26
RobinWang#agree15:27
SwamiYes, what you mentioned is also right, that we need to figure out what would be the right place to add those data.15:27
*** esker has joined #openstack-meeting-alt15:28
RobinWangso for the 4 use cases, which one will we address first15:28
*** radix_ has quit IRC15:28
SwamiWe are planning to address East-West first, North-South next and then the services15:28
*** sarob has quit IRC15:28
RobinWangcool15:29
SwamiBecause as soon as we talk about the north south then we also need to include the services in it.15:29
SwamiBut what I am also trying to do is, design for both East-West and North-South and then if the North-South is a low hanging fruit, then implement that as well15:29
RobinWangfor East-West, it is pretty straight forward, we just need to inject flow entry into ovs, to identify those traffic and then manipulate headers to achiieve one-hop thing15:30
*** jcooley_ has joined #openstack-meeting-alt15:30
SwamiYes, you are right15:30
RobinWangfor North-South, how does it work?15:30
SwamiRobin: are you asking for the services how it would work.15:31
RobinWangno, not the co-work between North-South routing and other services(LB/FW/VPN)15:32
RobinWangwhat I wonder is, how we process North-South traffic in DVR15:32
RobinWangthe work flow as I mentioned for East-West above15:33
SwamiYes, I have uploaded a picture in the "North-South" google doc regarding the design of the North South15:33
*** bill_az has quit IRC15:34
SwamiWe were planning to add an additional "External Gateway router" to the tenant's router to do the job. The SNAT will happen on the EG15:34
*** devkulkarni has joined #openstack-meeting-alt15:35
RobinWangI found the pic15:35
Swami#link https://docs.google.com/document/d/1iXMAyVMf42FTahExmGdYNGOBFyeA4e74sAO3pvr_RjA/edit15:35
*** markwash has quit IRC15:35
RobinWangcould you explain how it works15:35
*** markwash has joined #openstack-meeting-alt15:38
*** SushilKM has joined #openstack-meeting-alt15:38
SwamiThis would be the same model that we are planning to use for the East west as well, but without the additional EG. We may or may not have the additional bridge, but in discussion right now.15:38
*** tanisdl has joined #openstack-meeting-alt15:39
*** sacharya has joined #openstack-meeting-alt15:39
*** tanisdl has quit IRC15:39
*** DennyZhang has quit IRC15:40
RobinWangI also see Edouard's review "local ARP responder"15:41
SwamiWhen a tenant is trying to add an external gateway to the router, we will be adding or creating the EG and then the connection between the IR and EG is established with an virtual eth pair. The EG will have an internal private address space in the 169.x.x.x range. Each tenant will have an EG in the compute node15:41
RobinWangis this related to North-South DVR15:41
*** ruhe is now known as ruhe_15:41
*** ashaikh has joined #openstack-meeting-alt15:41
*** stackKid is now known as dingye15:41
SwamiYes Edouard already has a local ARP responder on the OVS, we can utilize it or else we can also add a rule in the OVS to do the arp functionality15:42
*** ruhe_ is now known as ruhe15:42
RobinWang" Each tenant will have an EG in the compute node", does it mean that on each compute node, there's at least one EG?15:43
SwamiYes, you are right.15:44
*** SergeyLukjanov has joined #openstack-meeting-alt15:44
*** jmontemayor has joined #openstack-meeting-alt15:44
RobinWangwhat about the mac of those EG?15:45
SwamiYes, it will also have a unique mac15:45
*** rongze has quit IRC15:46
RobinWangsince they have the same mac, when a North-South traffic comes from the outside world, how to guarantee those packet go to the correct EG on a specific compute node?15:48
*** BrianB_ has joined #openstack-meeting-alt15:48
SwamiRobin:No I did mention that they will have unique mac and unique floating IP on the compute node15:49
*** aignatov has joined #openstack-meeting-alt15:49
RobinWangsorry :)15:49
RobinWangI mis-understood it15:49
RobinWangwith unique mac and FIP, it should work well15:50
Swamiok, I will add more details to that doc15:50
*** asadoughi has joined #openstack-meeting-alt15:50
*** zhiyan has joined #openstack-meeting-alt15:51
Swamialso I am refining the plugin and agent architecture and once it is solid I will update the doc, meanwhile for this week, can you push the code that you have done on the "OVS plugin", I need to take a look at it or else update your doc or wiki with the required information15:51
*** yjiang5 has quit IRC15:52
*** sacharya has quit IRC15:52
*** gokrokve has joined #openstack-meeting-alt15:52
RobinWangOK15:52
*** rkukura has joined #openstack-meeting-alt15:53
Swami#action Swami will update the North South doc with more details on the plugin/agent architecture15:53
Swami#action Robin will push the WIP code for review by the subteam15:53
SwamiRobin does this timeslot works good for you15:54
RobinWangyes15:54
Swamiok, then if you have any questions or concerns, please feel free to send me an email and we can discuss those items in the IRC meeting.15:54
RobinWangSure :)15:55
Swamionce you upload the wip code send me an email, and I can go and review it15:55
*** SushilKM has quit IRC15:55
*** Sukhdev has joined #openstack-meeting-alt15:56
Swamiok, thanks for attending the meeting. We will meet next week.15:56
RobinWangOK, doc may come faster than refining and merging code :)15:56
Swamiany other questions15:56
*** sarob has joined #openstack-meeting-alt15:56
*** rcurran has joined #openstack-meeting-alt15:56
RobinWangSee you15:56
SwamiYes, we can do it together so don't worry we can speed up the process15:57
*** gokrokve has quit IRC15:57
*** aignatov has quit IRC15:57
Swamiok, bye15:57
Swami#endmeeting15:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:57
openstackMeeting ended Wed Dec  4 15:57:29 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
RobinWangI'll think about North-South and discuss with you on email15:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2013/distributed_virtual_router.2013-12-04-15.12.html15:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2013/distributed_virtual_router.2013-12-04-15.12.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2013/distributed_virtual_router.2013-12-04-15.12.log.html15:57
*** matrohon has joined #openstack-meeting-alt15:57
*** aignatov has joined #openstack-meeting-alt15:59
mesteryhi16:00
*** gokrokve has joined #openstack-meeting-alt16:00
matrohonhi16:00
rkukurahi16:00
rcurranhi16:00
mestery#startmeeting networking_ml216:01
openstackMeeting started Wed Dec  4 16:01:02 2013 UTC and is due to finish in 60 minutes.  The chair is mestery. 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
SukhdevHello16:01
asadoughihi16:01
mestery#link https://wiki.openstack.org/wiki/Meetings/ML2 Agenda16:01
mestery#topic Action Items From Last Week16:01
*** openstack changes topic to "Action Items From Last Week (Meeting topic: networking_ml2)"16:01
mesteryFirst item from last week: multi-node devstack gate testing16:02
mesteryI attended the infra meeting last week16:02
mesteryThere is no multi-node gate testing done now.16:02
*** rongze has joined #openstack-meeting-alt16:02
mesterySo, we will be blazing a new path here.16:02
mesteryI will spend some time on this before next week's meeting.16:02
mesteryAny questions?16:02
*** dingye has quit IRC16:03
*** roaet has joined #openstack-meeting-alt16:03
mesteryNext action item is for asomya.16:03
mesteryasomya: Review the TypeDriver patch.16:03
*** asomya has joined #openstack-meeting-alt16:03
*** Swami has left #openstack-meeting-alt16:04
mesteryasomya: hi16:04
asomyahi16:04
mesteryasomya: Did you review the TypeDriver patch?16:04
mesteryWe are reviewing your action item from the last meeting.16:04
asomyaYes, i posted a couple of inline question and a general one explaining my proposal16:04
mesteryasomya: OK, thanks. We can cover this in more detail later, wanted to make sure you had reviewed it.16:05
mestery#topic Development Issues16:05
*** openstack changes topic to "Development Issues (Meeting topic: networking_ml2)"16:05
mesteryrkukura rcurran: Both here?16:05
rkukuraI am16:05
rcurranyup16:05
mesteryrcurran: This is about the VLAN availability during delete_port_postcommit()16:05
mesteryAnd the thread we've had around that.16:05
mesteryWanted to discuss this with the broader team in the meeting.16:06
rkukuraReally the bound_segment being available16:06
mesteryrkukura: Yes16:06
rcurrando you want me to state what i found?16:06
mesteryrcurran: Yes, please do.16:07
rcurranthat is the issue in a nutshell16:07
*** sc68cal has joined #openstack-meeting-alt16:07
rcurrani'm trying to make better use of the pre/postcommit() methods16:07
rcurranfound out that on delete port the unbinding is done before the postcommit16:08
rcurrani need info in postcommit for nexus programming16:08
matrohonwe had the same issue16:08
*** jecarey has joined #openstack-meeting-alt16:08
matrohonfor l2pop16:08
mesterymatrohon: How did you solve this?16:08
rcurrangeneral issue seems to be that if in a create function you call subcreateA,B,C16:08
rcurranthat on deletes the calls should be made in the reverse order C,B,A16:09
*** banix has joined #openstack-meeting-alt16:09
rkukuraI'd argue unbind_segment() should have pre and post commit calls16:09
rcurranjust a thought16:09
mesteryrcurran: +1 to that.16:09
matrohonwe have store locally the data we nedded during pre-commit, and used it during post-commit16:09
mesteryrkukura: Thoughts on the ordering issue rcurren mentioned?16:09
rkukuranot sure I understand why that matters right now - there is only one bound segment belonging to one MechanismDriver16:10
SukhdevI felt the delete methods were ordered wrong - when I worked on it as well16:10
rkukuraI'm OK with reversing the order for deletes relative to creates, but don't see how that relates to the original issue16:10
mesteryConceptually it makes sense to tear things down in the exact reverse order as they were put up.16:10
rcurranit fixes it16:10
rkukurahow does it fix it?16:11
rcurranforgetting about the naming issue for a moment, delete_port_postcommit() is called before the db trans code16:11
rkukuraOh, you mean reversing the pre/post?16:11
rcurrannaming issues aside, yes16:12
rkukurathought you meant calling the list of MDs in the reverse order16:12
rcurrani never liked those names :-)16:12
*** dukhlov_ has quit IRC16:12
rcurranno16:12
rkukuraStill, I think port_unbind() needs to be handled consistently/correctly whether part of delete_port() or otherwise16:13
*** hemanthravi has joined #openstack-meeting-alt16:13
*** lblanchard has quit IRC16:13
rkukuraSo if an MD needs to do something outside a transaction, we need that to work as part of port_unbind()16:13
rcurranyeah, it probably should have a pre/post type style to be in line w/ the other methods16:13
mesteryrkukura rcurran: I agree.16:14
matrohonwhat if the binding was stored in the port context, in orig_context16:15
rkukuraHow about we move the private email discussion to openstack_dev, and try to come to a plan16:15
rcurranok by me16:16
mesteryrkukura: Lets do it.16:16
matrohonrkukura : fine, put me in this discussion16:16
mesteryWho wants this action item?16:16
*** jcoufal has quit IRC16:16
mestery#action rcurran to move this discussion to openstack-dev16:16
rkukuraI can take it16:16
mesteryrcurran: I gave it to you :)16:16
rcurransorry, was looking at something else ... ok16:16
mesteryOK, moving on to the next item on the agenda16:17
rkukuralast email was from rcuran, so I can just reply adding the list16:17
mesteryrkukura: OK, makes sense.16:17
rcurranyes, bob please do16:17
mestery#undo16:17
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x269f890>16:17
rcurrancc matrohon too16:17
mestery#action rkukura to continue discussion on openstack-dev16:17
matrohonrcurran : thanks16:17
mestery#topic Testing16:17
*** openstack changes topic to "Testing (Meeting topic: networking_ml2)"16:17
mesterySo, there are 4 items in this area on the agenda.16:18
mesteryLets start with unit tests, which may be the easiest.16:18
mesteryAt the last meeting, we decided we should possibly add more unit test coverage for ML2.16:18
mesteryDoes anyone want to take this action item and look into this?16:18
rkukurahas anyone checked the coverage?16:18
mesteryI don't think so, no.16:18
mesteryThat would be a good first step.16:18
SukhdevI looked into the port testing16:19
*** markmcclain has quit IRC16:19
Sukhdevand notice that it does not work well for ML2 drivers/context16:19
mesterySukhdev: Unit testing?16:19
mesterySukhdev: Or is that functional/tempest testing?16:19
*** bdpayne has quit IRC16:19
SukhdevOh - my bad - sorry - I was talking about tempest test16:20
rkukuraI'm pretty sure the RPC methods in the server need real unit testing16:20
mesterySukhdev: No worries.16:20
mesteryrkukura: Agreed.16:20
mesteryOK, if no one is volunteering, I'll work offline to find someone to cover this.16:20
mesteryThis being the unit test coverage.16:20
*** rudrarugge has joined #openstack-meeting-alt16:20
mestery#action mestery to find a volunteer to verify and possibly expand ML2 unit test coverage.16:20
*** sarob has quit IRC16:21
mesteryThe next item is multi-node devstack based gate testing.16:21
mesteryWe briefly touched on this earlier. I need to research this more and come up with a plan for this.16:21
rkukuramestery: Can this be combined with the scenarios in the next item?16:21
mesteryrkukura: I think that seems reasonable, yes.16:21
rudraruggehi - is this the policy meeting. sorry joining late16:21
roaetrudrarugge: ml2 subteam meeting16:22
mesteryrudrarugge: Nope, ML2 meeting16:22
rudraruggeok16:22
rkukuraSo multi-node tempest tests run for various config scenarios?16:22
mesteryrkukura: Are you saying the multi-node stuff shoudl just be tempest tests?16:22
mesteryrkukura: I think so, yes.16:22
*** coolsvap has joined #openstack-meeting-alt16:22
mesterySo, I think you're right rkukura, this will cover both items.16:22
rkukuraI'd hope we could reuse as much of what exists as possible16:23
*** baoli has joined #openstack-meeting-alt16:23
mesteryrkukura: Agreed.16:23
mesteryrkukura: But this will require whatever is using tempest to spin up multiple VMs.16:24
mesteryI may need to look at this closer if I'm not understanding something here.16:24
*** sacharya has joined #openstack-meeting-alt16:24
rkukuraI don't know the details, but couldn't something do a multi-node devstack deployment and then run tempest in one of the nodes?16:25
mesteryrkukura: I think that's the idea, yes, but that doesn't exist today. :)16:25
mesteryThe tripleo folks are looking at something similar, according to the infra folks.16:25
SukhdevAre there any tempest tests for multi-node setup - did I miss anything....I did not see any16:25
mesterySo we may be able to combine efforts.16:25
mesterySukhdev: There are none.16:25
mesteryWe need to add those.16:25
rkukuraWouldn't just running the existing tempest tests in a multi-node deployment add significant value?16:26
mesteryrkukura: Yes, I think that's a good start.16:26
Sukhdevrkukura - only if you combine them with nova - otherwise no16:27
rkukuraThen some addition tests could be added to tempest to specifically exercise cross-node interactions16:27
*** bill_az has joined #openstack-meeting-alt16:27
mesteryWait, if you run Tempest against a multi-node openstack, it will be default be using multiple nodes, right?16:27
mesteryAs long as it spins up multiple VMs I guess?16:28
mesteryWhat am I missing here?16:28
rkukuraI was assuming these tempest tests would include nova16:28
Sukhdevthere are nova tests and neutron test - I did not see one invoking other16:28
mesteryThe neutron tests have to spinup VMs for testing, right? They would implicitly be using nova.16:29
Sukhdevwhen you run neutron port test - they have no clue about nova tests - hence, there is no host information - and hence, you can test networks across multi-nodes16:29
rkukuradon't tempest smoke tests involve both nova and neutron?16:29
mesteryI thought they did.16:30
Sukhdevthey do them serially - based upon what i saw16:30
matrohonhttps://github.com/openstack/tempest/blob/master/tempest/scenario/test_network_basic_ops.py16:30
matrohonthis smoke test creat servers and neutron networks16:31
*** markwash_ has joined #openstack-meeting-alt16:31
rkukuramatrohon: right16:31
mesteryYes, exactly, the neutron tests make use of nova implicitly.16:31
*** markwash has quit IRC16:32
*** markwash_ is now known as markwash16:32
rkukuraSukhdev: Of course there are also tempest tests for neutron that don't involve nova16:32
SukhdevI was looking at the API tests16:32
Sukhdevthey do not involve Nova tests16:33
rkukuraso not sure if running all those multi-node adds much, but it shouldn't hurt, and might expose issue16:33
Sukhdevhttps://github.com/openstack/tempest/blob/master/tempest/api/network/test_networks.py16:33
*** aratim has joined #openstack-meeting-alt16:33
mesteryAPI is different than scenario tests, now I understand the gap here Sukhdev.16:34
*** igormarnat__ has quit IRC16:34
*** brents has joined #openstack-meeting-alt16:34
*** igormarnat_ has joined #openstack-meeting-alt16:34
rkukuraso what kind of base multi-node deployment scenario would we start with?16:34
rkukuraMaybe one node for controller/network/tempest and two compute nodes?16:35
mesteryrkukura: I think just running the existing scenario tests against a multi-node ML2 setup would be the best place to start, right?16:35
*** s3wong has joined #openstack-meeting-alt16:35
mesteryrkukura: Yes16:35
matrohonrkukura: fine16:35
*** SushilKM has joined #openstack-meeting-alt16:35
rkukuraThen we could add/modify some test(s) to force VMs onto different compute nodes, right?16:36
matrohonrkukura: yes16:36
mesteryYes, that makes sense.16:36
mesterySo, I think I'll write this up in an etherpad before next week's meeting, does that sound good?16:36
rkukuraAnd could this serve as the template for 3rd party external driver/plugin testing?16:36
mesteryrkukura: Yes, even better!16:36
* mestery likes the slick segway rkukura just did there.16:36
*** rudrarugge has quit IRC16:36
mesteryWhich brings us to our next topic ...16:37
Sukhdevmestery: that is a great idea16:37
matrohonrkukura: great16:37
mesteryVendora based tempest testing for MechanismDrivers16:37
mestery#action mestery to start etherpad for multi-node ML2 tempest testing and share with ML2 subteam16:37
mesterySo, this really applies to more than just ML2, but lets start here.16:37
mesteryAll 3rd party testing requirements are effectively the same.16:38
mesterySo, I was thinking we should share the knowledge on setting this up so everyone doesn't have to reinvent the wheel.16:38
mesteryMakes sense?16:38
Sukhdevexcellent idea16:38
*** aratim1 has joined #openstack-meeting-alt16:38
*** tsimmons has joined #openstack-meeting-alt16:38
mesteryI think the basic idea is this:16:39
mesteryEach 3rd party plugin/MD needs to run the existing Tempest tests when code changes in their plugin or ML2 MD.16:39
mesteryFor this, I think the best way to proceed is to have a Jenkins instance running which reads the gerrit stream and kicks off the tempest tests.16:39
*** aratim has quit IRC16:39
*** Sukhdev_ has joined #openstack-meeting-alt16:39
*** tsimmons has quit IRC16:39
Sukhdev_sorry - my connection dropped - back again16:40
mesterySukhdev_: No worries.16:40
*** tsimmons has joined #openstack-meeting-alt16:40
rkukuramestery: Does this trigger just on merges or also when patches are submitted/approved?16:40
mesteryWhen patches are submitted.16:40
mesteryBecause the 3rd party testing needs to vote +1/-1 as well16:41
rkukurathat's what I hoped16:41
mesteryOK, I can start an etherpad for this as well to combine information.16:41
mesteryI was also thinking perhaps a separate meeting next week would be good for people, maybe over WebEx?16:42
mesteryThoughts?16:42
Sukhdev_So, does there exist anything which we can leverage?16:42
mesterySukhdev_: Yes, there is a jenkins plugin which reads gerrit streams already.16:42
Sukhdev_I started to look into writing my own scripts and realized, it will be a lot of work16:42
rkukuraIs this meeting specifically on multi-node testing and/or 3rd party testing?16:42
mesteryThis is the type of info I hope to share with everyone.16:42
*** Sukhdev has quit IRC16:43
mesteryI think we should combine the two rkukura.16:43
mesteryBecause 3rd party testing will almost certainly need multi-node testing as well.16:43
*** jcooley_ has quit IRC16:43
mestery#action mestery to organize meeting around multi-node tempest testing and 3rd party testing for next week.16:44
rkukuraand is better than or!16:44
mestery:)16:44
mesteryAnything else on testing for now?16:44
ZangMingJieWe are also going to deploy multi-node test, maybe we can share idea16:45
*** tsimmons has quit IRC16:45
rkukurawe didn't really discuss scenarios to test internally16:45
mesteryZangMingJie: Awesome!16:45
mesteryrkukura: Good point, shall we do that now?16:45
rkukurawe should leave some time for the TypeDriver discussion16:47
mesteryGood point, lets move on.16:47
*** yjiang5 has joined #openstack-meeting-alt16:47
mesteryWe can continue the testing scenario discussion on the ML and in the meeting next week.16:47
mestery#topic TypeDriver discussion16:47
*** openstack changes topic to "TypeDriver discussion (Meeting topic: networking_ml2)"16:47
mesteryPer the start of the meeting, asomya has given some comment on ZangMingJie's patch.16:47
mesteryAnyone else have comments?16:48
rkukuraI've started reviewing the current patch16:48
mesteryrkukura: Any high level thoughts at this point?16:48
rkukuraI like the concept, but will have a few issues on the implementation16:49
*** tsimmons has joined #openstack-meeting-alt16:49
rkukuraFrom an API perspective, this really forces the move from provider extension to multiprovider extension16:49
mesteryI think that was what ZangMingJie was intending, right?16:50
mestery#link https://review.openstack.org/#/c/37893/ TypeDriver review16:50
*** NikitaKonovalov has quit IRC16:50
*** bdpayne has joined #openstack-meeting-alt16:50
ZangMingJieYes, I have posted my opinion to openstack-dev list, IMO we should move to multiprovider extension and abondon provider ext16:50
rkukuraDidn't see a thread on this, but will look for it16:51
ZangMingJiehttp://lists.openstack.org/pipermail/openstack-dev/2013-December/021117.html16:52
rkukuraSeems we should be able to maintain provider extension compatibility when only a single segment with then "standard" attributes is involved16:52
mesteryAgreed.16:52
ZangMingJieon API level or neutronclient level ?16:53
*** mugsie has joined #openstack-meeting-alt16:53
rkukuraI'd like to look carefully at how the segment validation/reservation/allocation stuff is handled in the patch - I have a bit of concern there, but need to look closer16:53
rkukuraZangMingJie: I think both, maybe with plan to deprecate provider extension in J?16:53
*** colinmcnamara has joined #openstack-meeting-alt16:54
*** colinmcn_ has joined #openstack-meeting-alt16:54
mesteryrkukura: That's not a bad plan.16:55
*** RobinWang has quit IRC16:55
*** msisk has joined #openstack-meeting-alt16:55
rkukuraMain question is whether we really have consensus on moving away from existing provider extension/model to multi-provider with arbitrary attributes16:55
mesteryrkukura: I'll make a note to mention this during the Neutron team meeting next Monday, sound good?16:56
rkukuraI'd like to get markmcclain and other neutron cores to buy in on this16:56
*** sarob has joined #openstack-meeting-alt16:56
Sukhdev_Can you give a high level summary of this?16:56
rkukuraThe provider extension uses fixes set of attributes (network_type, segmentation_id, phyiscal_network)16:57
*** ashaikh has quit IRC16:57
mesteryrkukura: Added an item for the Neutron team meeting on Monday here: https://wiki.openstack.org/wiki/Network/Meetings#ML2_.28mestery.2Frkukura.2916:58
rkukuraWith multiprovider extension and this patch, TypeDrivers define arbitrary attributes (only network_type is required)16:58
Sukhdev_rkukur: thanks16:58
mesteryOK, lets continue this discussion on the ML and review, we're running short on time.16:58
mestery#topic Open Discussion16:58
*** openstack changes topic to "Open Discussion (Meeting topic: networking_ml2)"16:58
roaetI was attempting to do https://bugs.launchpad.net/neutron/+bug/1196170 and was delayed many time (release, lots of things), and I was wondering if I should continue to rebase over and over again or is it no longer a valid task? If it is a valid task can I get direction/support so that it can be merged (I know it's wishlist, but just wanting to find a conclusion).16:58
mesteryWanted to leave a few minutes for open discussion.16:58
roaet(that wasn't prepared, I swear)16:59
*** SushilKM__ has joined #openstack-meeting-alt16:59
*** colinmcn_ has quit IRC16:59
*** colinmcnamara has quit IRC16:59
sc68caljust posted up my patches for the qos ml2 - I missed the change that removed mox - so it's still WIP16:59
mesteryroaet: I still think is a valid patch to work on.16:59
asadoughii was going to mention progress on ovs-firewall-driver blueprint, basic flows are working on the agent, but not there 100% as i learn more on using openvswitch16:59
mesteryroaet: Please post a new version and rkukura and I will review it in more detail again.17:00
mesterysc68cal: Cool, will check those out!17:00
roaetmestery: thank you. I will ping you both in os-neutron17:00
rkukuraroaet: ok17:00
mesteryasadoughi: Awesome!17:00
*** sarob has quit IRC17:00
*** artom has joined #openstack-meeting-alt17:00
*** colinmcnamara has joined #openstack-meeting-alt17:01
rkukuraasadoughi: Is there a followup meeting scheduled on that?17:01
mesteryOK, we're out of time now.17:01
ZangMingJieovs-firewall-driver is also on our schedule17:01
mesteryLets continue discussions on ML and IRC.17:01
*** aratim has joined #openstack-meeting-alt17:01
mesteryThanks everyone!17:01
roaetthanks17:01
mestery#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
openstackMeeting ended Wed Dec  4 17:01:43 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-12-04-16.01.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-12-04-16.01.txt17:01
*** SushilKM has quit IRC17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-12-04-16.01.log.html17:01
*** CaptTofu has joined #openstack-meeting-alt17:01
matrohonthanks17:01
*** sc68cal has left #openstack-meeting-alt17:01
mugsie#startmeeting designate17:02
openstackMeeting started Wed Dec  4 17:02:03 2013 UTC and is due to finish in 60 minutes.  The chair is mugsie. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: designate)"17:02
*** roaet has left #openstack-meeting-alt17:02
openstackThe meeting name has been set to 'designate'17:02
*** colinmcn_ has joined #openstack-meeting-alt17:02
*** igormarnat__ has joined #openstack-meeting-alt17:02
mugsieis everyone here?17:02
* CaptTofu is here17:02
betsyhere17:02
*** igormarnat_ has quit IRC17:02
msiskhere (sorta -- in a Chef training class)17:03
*** eankutse has quit IRC17:03
*** alazarev has joined #openstack-meeting-alt17:03
*** eankutse has joined #openstack-meeting-alt17:03
*** aratim has quit IRC17:03
*** asomya has quit IRC17:03
*** aratim has joined #openstack-meeting-alt17:03
*** nicole has joined #openstack-meeting-alt17:04
*** aratim1 has quit IRC17:04
mugsiekiall is not around today, so I am going to chair for him17:04
*** nicole is now known as Guest8692417:04
betsyvinod is out today too17:04
*** jmcbride has joined #openstack-meeting-alt17:04
mugsiewe should have a quick one today, not much to talk about17:04
eankutsehere17:04
mugsie#topic Review action items from last week17:04
*** openstack changes topic to "Review action items from last week (Meeting topic: designate)"17:04
mugsieeh, there is none, outstanding, so moving on17:05
*** hemanthravi has quit IRC17:05
*** rcurran has quit IRC17:05
mugsie#topic BP meeting17:05
*** openstack changes topic to "BP meeting (Meeting topic: designate)"17:05
simonmcco/17:05
*** akuznetsov has quit IRC17:05
*** rongze has quit IRC17:05
mugsielooking at what people have filled in, it looks like this time next week is the best time to do the bp meeting17:05
mugsieare people ok with replacing this meeting with that one?17:06
*** shakayumi has joined #openstack-meeting-alt17:06
betsyworks for me17:06
simonmccI'm happy with that17:06
* shakayumi shakayumi == alex b :D17:06
eankutsegood for me17:06
jmcbridedid everyone get you their google hangout accounts?17:06
*** rongze has joined #openstack-meeting-alt17:07
mugsienearly everyone17:07
mugsieI will update the Hangout event, and the launchpad page17:07
shakayumiok17:07
eankutsecool17:07
mugsieif anyone has not sent me the details, my email is graham.hayes@hp.com17:07
*** alazarev has quit IRC17:08
mugsiereemember to submit any blueprints you think should have special attention, so we can read uo in advance17:08
*** yjiang5 has quit IRC17:08
*** zane has joined #openstack-meeting-alt17:08
*** yamahata_ has quit IRC17:08
*** jcooley_ has joined #openstack-meeting-alt17:08
mugsieI think we will go over them all, but there may be ones people want to get into detail with, and we would be better with everyone reading them in advance for that17:08
mugsiesound ok?17:09
tsimmonsCool17:09
eankutsek17:09
shakayumik17:09
betsyagreed17:09
simonmccyep17:09
mugsiecool.17:09
*** SergeyLukjanov is now known as _SergeyLukjanov17:09
mugsie#topic Open Discussion17:09
*** openstack changes topic to "Open Discussion (Meeting topic: designate)"17:09
mugsieanyone have any AOB?17:10
simonmccnothing from me17:10
eankutseAOB?17:10
betsyI'm good17:10
simonmccAny Other Business17:10
eankutse:-)17:10
mugsiecool.17:10
mugsiefastest meeting ever17:10
betsya new record17:11
simonmccschweet17:11
eankutsethx17:11
mugsie#endmeeting17:11
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:11
openstackMeeting ended Wed Dec  4 17:11:19 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-12-04-17.02.html17:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-12-04-17.02.txt17:11
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-12-04-17.02.log.html17:11
*** msisk has left #openstack-meeting-alt17:11
*** igormarnat__ has quit IRC17:11
mugsiethanks everyone17:11
*** radix_ has joined #openstack-meeting-alt17:14
*** jcooley_ has quit IRC17:15
*** BrianB_ has quit IRC17:17
simonmccthanks mugsie17:17
*** jmcbride has quit IRC17:17
*** pcm_ has quit IRC17:19
*** jmcbride has joined #openstack-meeting-alt17:19
*** aratim has quit IRC17:21
*** ruhe is now known as ruhe_17:21
*** ruhe_ is now known as ruhe17:21
*** jmcbride has quit IRC17:22
*** jmcbride has joined #openstack-meeting-alt17:23
*** ashaikh has joined #openstack-meeting-alt17:23
*** eankutse1 has joined #openstack-meeting-alt17:25
*** eankutse1 has quit IRC17:25
*** eankutse1 has joined #openstack-meeting-alt17:26
*** jdob_ has joined #openstack-meeting-alt17:26
*** eankutse has quit IRC17:27
*** jdob has quit IRC17:27
*** jmcbride has quit IRC17:29
*** tsimmons has left #openstack-meeting-alt17:31
*** yogesh has joined #openstack-meeting-alt17:32
*** jmcbride has joined #openstack-meeting-alt17:36
*** jdob_ has quit IRC17:38
*** jdob has joined #openstack-meeting-alt17:38
*** baoli has quit IRC17:39
*** lblanchard has joined #openstack-meeting-alt17:41
*** cweid has joined #openstack-meeting-alt17:45
*** konetzed has joined #openstack-meeting-alt17:46
*** yogesh has quit IRC17:46
*** akuznetsov has joined #openstack-meeting-alt17:50
*** derekh has quit IRC17:50
*** robertmyers has joined #openstack-meeting-alt17:52
*** rossella_s has quit IRC17:52
*** rsblendido has quit IRC17:52
*** datsun_F40PH has joined #openstack-meeting-alt17:53
*** _kpom_ has joined #openstack-meeting-alt17:54
*** SergeyLukjanov has joined #openstack-meeting-alt17:55
*** IlyaE has quit IRC17:56
*** amcrn has joined #openstack-meeting-alt17:57
*** jmcbride has left #openstack-meeting-alt17:58
*** SergeyLukjanov has quit IRC17:58
denis_makogono/17:58
*** demorris has joined #openstack-meeting-alt17:58
*** artom has left #openstack-meeting-alt17:59
datsun_F40PHhello hello trove18:00
denis_makogonola, sir18:00
*** yogesh has joined #openstack-meeting-alt18:00
*** ashestakov_ has joined #openstack-meeting-alt18:00
denis_makogonSIESTA!18:00
esmute\o/18:00
*** jcru has joined #openstack-meeting-alt18:00
amcrno^/18:01
* esmute is giving free hugs whoever is interested18:01
cp16nethola18:01
*** grapex has joined #openstack-meeting-alt18:01
*** imsplitbit has joined #openstack-meeting-alt18:01
imsplitbito/18:01
hub_cap#startmeeting #trove18:01
yogesh5hello18:01
openstackMeeting started Wed Dec  4 18:01:16 2013 UTC and is due to finish in 60 minutes.  The chair is hub_cap. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
yogeshhello18:01
*** openstack changes topic to " (Meeting topic: #trove)"18:01
imsplitbit/o/18:01
ashestakov_o/18:01
openstackThe meeting name has been set to '_trove'18:01
grapexo/18:01
imsplitbit\o\18:01
robertmyerso/18:01
*** NehaV has joined #openstack-meeting-alt18:01
imsplitbit\o/18:01
pdmarso/18:01
amcrn\o18:01
kevinconwayo/18:01
datsun_F40PHo718:01
denis_makogono/18:01
*** SlickNik has joined #openstack-meeting-alt18:01
cp16neto/18:01
isviridovo/18:01
hub_cap#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting18:01
SlickNikhere18:01
cweido/18:02
denis_makogonwhazzap 2 all18:02
hub_cap#topic separate guest agent18:02
*** openstack changes topic to "separate guest agent (Meeting topic: #trove)"18:02
hub_capdenis_makogon: go18:02
imsplitbit))))))))18:02
denis_makogon#link https://github.com/denismakogon/trove-guestagent18:03
juiceo/18:03
denis_makogonlast few days i was working on extracting guestcode into it's own repo18:03
denis_makogonmanually i ran all testcases18:03
hub_capawesome denis_makogon18:03
SlickNikdenis_makogon: nice!18:03
*** akuznetsov has quit IRC18:03
robertmyerslooks good18:03
denis_makogoni mean create/backup/restore/resize18:04
hub_capdenis_makogon: when we really go about creating the guest, we can use a git subtree to keep the history18:04
denis_makogonfor now i've got problems with few tests which are using DB connection18:04
vipulo/18:04
kevinconwayhub_cap: +118:05
*** coolsvap has quit IRC18:05
imsplitbit+1 subtree18:05
cp16net+1.518:05
imsplitbit)))))18:05
datsun_F40PH+1 yeah let's preserve that history18:05
denis_makogonso, question is: do we plan to integrate guestcode ?18:05
grapexhub_cap: Yeah, that history goes back a year and half- let's do the subtree thing.18:05
kevinconwaydenis_makogon: yes, it should be merged with trove repo18:05
SlickNikanother thing denis_makogon. Can you split off the git subtree, rather than have one big initial commit? This preserves git history...18:05
*** Guest86924 has left #openstack-meeting-alt18:06
kevinconwaydenis_makogon: but first separate it, then merge it back in18:06
denis_makogonSlickNik, i would try18:06
hub_capok cool. this brings up an interesting question, if i want to make changes to my guest, and i edit my local code, how does that code get into the instances i provision?18:06
hub_capim worried less about tests, cuz the openstack pypi stuff is set up to handle this, but for day to day devrlopment18:06
*** diakunchikov_ has joined #openstack-meeting-alt18:07
denis_makogonmaybe git clone/pull ?18:07
hub_capdenis_makogon: its necessary18:07
hub_capplz figure out how to do it and use that as the repo18:07
datsun_F40PHi guess you'd have to set up your local repo as the authority18:07
grapexhub_cap: Do you mean when you're developing? Doesn't the rsync trip pull that in? Just point it somewhere else.18:07
grapexSeems like this is yet another thing that will live in /opt/stack18:08
robertmyersadd it to devstack?18:08
hub_capgrapex: fair enough, but the "delivery" part is what hes talking about18:08
grapexand rsync will pull it from there; devstack will clone it if it doesn't exist, and people will make it a shared folder if they're using a VM18:09
kevinconwaydatsun_F40PH: when will vagrant be updated for this?18:09
*** nadya has joined #openstack-meeting-alt18:09
denis_makogongrapex, yes, i was playing with redstack and guest18:09
datsun_F40PHkevinconway: when someone submits a pull request and i feel like merging it18:09
*** nadya is now known as Guest8588618:09
denis_makogon#action denis_makogon: use git subtree for guestcode18:10
*** ashaikh_ has joined #openstack-meeting-alt18:10
*** zhiyan has quit IRC18:10
*** Barker has joined #openstack-meeting-alt18:11
kevinconwaydenis_makogon: it looks like you made changes to agent after moving it out?18:11
*** ashaikh has quit IRC18:11
*** ashaikh_ is now known as ashaikh18:11
*** ruhe has quit IRC18:11
hub_capok so what do we have to make decisions on here?18:11
denis_makogonkevinconway, clean-up18:11
kevinconwaywas it needed to move the agent?18:11
datsun_F40PH+1 that concern18:11
hub_capdo not do any cleanup unless its necessary18:12
kevinconwayit's great to clean it, just make sure to keep the original branch unchanged18:12
denis_makogonkevinconway, i was trying to keep agent code up-to-date wit trove repo18:12
hub_capwe can clean up in a second commit18:12
denis_makogonok, i will revert all my own changes18:12
kevinconwaydenis_makogon: when you do the subtree merge and restore history you can branch off master and re-apply your changes18:12
kevinconwayno big deal18:12
*** shenderov has joined #openstack-meeting-alt18:12
denis_makogonhub_cap, question it that how to keep guest code up-to-date18:12
datsun_F40PHdenis_makogon: don't take matches to it, lean on git to help you maintain your work18:13
denis_makogonok18:13
denis_makogonthanks18:13
hub_capmoving on?18:13
denis_makogonyes18:13
hub_cap#topic configuration parameter deathmatch18:14
*** openstack changes topic to "configuration parameter deathmatch (Meeting topic: #trove)"18:14
hub_capcp16net: denis_makogon go go go18:14
denis_makogon#link https://gist.github.com/denismakogon/778983118:14
cp16netlol18:14
denis_makogoni described all problems with current implementation of parameters configuration18:15
* imsplitbit tosses some rusty hatchets into the ring18:15
datsun_F40PHi'm on team "send the whole file and keep the GA dumb"18:15
denis_makogon#link https://review.openstack.org/#/c/53168/18:15
grapexI like keeping the guest agent dumb too.18:15
hub_capheh denis_makogon next time put this on the meeting agenda so we can view it before hand18:15
denis_makogonsorry18:15
denis_makogonforgot18:15
*** twoputt__ has joined #openstack-meeting-alt18:15
*** twoputt_ has joined #openstack-meeting-alt18:15
denis_makogonguest dumbness defined by database18:16
SlickNik+1 to keeping the guest-agent dumb.18:16
*** shenderov has quit IRC18:17
SlickNikStill reading the gist. Might need clarification on a couple of points.18:17
imsplitbitdenis_makogon: can you explain that?18:17
amcrncan someone clarify what "keep the guest agent dumb" means in terms of action-items as compared to what's in the current review?18:17
cp16netdenis_makogon:   - do not call configuration groups - overrides, it too mysql specific;18:17
amcrni'm not fully groking this gist18:17
grapexamcrn: It means having the server create the full and send it over18:17
hub_capya ir confused a bit18:17
cp16netwhat do you mean?18:17
datsun_F40PHamcrn: the alternate would mean the GA gets to figure out templating and filling in the blanks and locations and such18:17
grapexamcrn: Versus sending over only what to change in db specific terms, and having the guest apply changes to the file18:17
denis_makogongrapex, Amazon RDS doing merging18:18
denis_makogonas i said, only mysql could start with more then one conf file18:18
denis_makogonout of box18:18
imsplitbitnot true18:19
imsplitbitredis can18:19
denis_makogoni've researched18:19
imsplitbitbut I'd love to hear more about servers that cannot18:19
denis_makogonprof ?18:19
cweidredis can use more than one conf file.18:19
imsplitbitit?18:19
amcrngrapex: if it's moved to the server, will it still consult the ga for the source-of-truth, therefore requiring multiple roundtrips?18:19
grapexdenis_makogon: True they do, however they don't support multiple datastores either.18:19
denis_makogonimsplitbit, mongo, cassandra, postgresql18:19
kevinconwayso the payload that comes from the server includes a whole new config or just a partial?18:20
amcrngrapex: i.e. ask the ga what the default values were, then merge the change-set, then push the entire set18:20
denis_makogoni vote for only part18:20
grapexamcrn: Not sure- last I checked, there's no round trip.18:20
hub_capdenis_makogon: postgresql and redis can do a conf.d w/ 1 line in their configs18:20
grapexcp16net: Can you confirm?18:20
amcrnwell now there isn't, but if it's moved from ga to server, what will it be18:21
datsun_F40PHi think just providing a "get the current config" call would suffice18:21
datsun_F40PHlet someone smarter than six lines of awk do the merging work18:21
robertmyersdatsun_F40PH: +118:21
denis_makogondatsun_F40PH, that's the problem, because there could be special config changes to make DB available for any hosts18:22
hub_capno merge18:22
hub_cappush the entire config down18:22
amcrndenis_makogon: details?18:22
datsun_F40PHdenis_makogon: in that case you employ a DBA to make those changes18:22
SlickNikrobertmyers: did you just volunteer yourself? :)18:22
hub_capthere is no need to "merge"18:22
robertmyersSlickNik: sure18:22
vipulare we talking about database config like a my.cnf or guest agent config trove-guestagent.conf18:22
grapexamcrn: The server is assumed to be the source of truth currently.18:22
robertmyersvipul: my.cnf18:22
grapexvipul: my.cnf18:22
SlickNikmy.cnf18:22
vipulk thanks18:22
hub_capMY.CNF18:23
vipul:p18:23
hub_capjust in case u didnt get that vipul18:23
amcrnother than thinning down the guestagent, what is this buying us?18:23
datsun_F40PHthe power to tune18:23
*** dmitryme has joined #openstack-meeting-alt18:23
denis_makogonsuppose, i need to set bind address to eth0 inet addr18:23
grapexamcrn: A better question is what's it costing us?18:23
denis_makogonbut server didn't knew, that guest doing such thing18:24
robertmyersdenis_makogon: why is the guest changing the config?18:24
grapexdenis_makogon: Would you do that via the API?18:24
kevinconwaydenis_makogon: it would be the same process as when the guest first wrote the config18:24
amcrnit must just be me, i'm having a hard time summarizing the positive net benefit of doing this (vs. not doing this)18:24
denis_makogonsimple example https://review.openstack.org/#/c/51884/19/trove/guestagent/datastore/cassandra/manager.py18:24
SlickNikamcrn: you're not alone, I'm trying to think through the exact same thing.18:25
cp16neti'm getting a little lost in this convo18:25
vipulcp16net: +118:26
hub_capok amcrn re-summarize18:26
denis_makogoncurrent design works only with databases which could start with more then one conf file18:26
hub_capif there is no net gain/loss, then we dont change anything until we need it <--- general rule18:26
denis_makogonso you are saying that trove would not work with DBs which cannot do such thing ?18:26
SlickNikamcrn: I think it makes the guest API much simpler.18:26
ashestakov_im agree with dmakogon, will better to send array with K:V parameters through rpc, and render config in manager class18:27
hub_capashestakov_: why is that better?18:27
grapexdenis_makogon: Would it though? It seems like if the db had only one conf file, you could just overwrite that file every time18:27
hub_capi can send a string or a dict.. what is the difference?18:27
grapexUnless the idea is there is some secret stuff on the guest machine you don't want to overwrite18:28
amcrn+1 to grapex's comment, that's where i'm lost18:28
ashestakov_hub_cap: for DBs which dont support multiple configs, manager can render all settings to one file18:28
ashestakov_its more flexible then send renderd configs18:28
robertmyerswhy not just send one file then?18:28
robertmyersthe whole config18:29
ashestakov_or one file..18:29
denis_makogonsuppose trove creates database, why do i need reconfigure it to make it available for r/w operations ?18:29
grapexashestakov_: I disagree, rendered configs could be generated in nearly any way- there's nothing that's unflexible about it except that it replaces the entirety of what's on the guest machine18:29
hub_capexcept then the rendering occurs in the guest and that cost more memory wise, and u need the templates in the guest18:29
amcrnoh, i think i get the gist of what denis_makogon is saying. example: if you have a datastore that doesn't support multiple confs, say you apply some changes with configuration "a". if the user sends in configuration "b" as an update, it's not straightforward to ascertain what the original/virgin/default conf was.18:30
ashestakov_maine point: need to render config depends on manager class, for mysql can has my.cnf and conf.d/my.cnf18:30
amcrnunless the datastore has a operation to say "print-defaults" of course18:30
hub_capamcrn: u can regen the "default" from the config template w/ the updates passed in18:30
datsun_F40PHso then it's up to each impl's GA to figure out what "all the configs" means18:30
grapexamcrn: So when you first do those changes with configuration "a", who or what does that?18:30
vipulthat's part of documentation isn't it?18:30
ashestakov_but for mongo we can have only /etc/mongodb.conf18:30
datsun_F40PHmaybe it's a list of different file locations and their respective contents18:30
kevinconwayashestakov_: why couldn't guest agent just write new config to /etc/mongodb.conf?18:31
cp16netwe have the default conf from rendering the conf again18:31
amcrnhub_cap: today you can't, because only the overrides are stored in the database18:31
hub_capok i think we need to move forward and push this to after the meeting or the ML18:31
imsplitbitI'm wondering if we shouldn't really hash this out more on the ML18:31
imsplitbitit's 12:3018:31
cp16netthats nothing more than whats happening in the create instance18:31
imsplitbitor halfway through the meeting18:31
ashestakov_kevinconway: coz, we have template with common settings and user defined settings18:31
hub_capamcrn: but the config.template is stored in the taskmgr too18:31
amcrnhub_cap: oh yeah, whoops ;)18:31
hub_capso why dont we just regen each config.template + diff'd parameters and send that file down18:32
SlickNikso if all the overrides are in the db, couldn't you just send out a default conf + _all_ overrides to the guest agent.18:32
hub_capsingle file should be ok18:32
SlickNikThat way it gets a + b18:32
hub_capi think SlickNik and i said the same thing18:32
ashestakov_kevinconway: sure we can render all settings in one file, but this should be done for all datastores18:32
amcrnthat approach generally makes sense to me18:32
*** yahongdu has quit IRC18:32
denis_makogonhub_cap, why not to send dict with options and let manager decide how to apply it ?18:32
kevinconwayashestakov_: this seems like only an issue of how to get the new config to the agent. the agent can do what it wants with it.18:33
*** DennyZhang has joined #openstack-meeting-alt18:33
hub_capwhat do they have to decide?18:33
grapexdenis_makogon: In addition to making the guest smart, sending a dict down means you assume that everything will be in some format that will be easy to modify using a dictionary18:33
hub_capif, always, we send down 1 file, what decision is to be made?18:33
grapexSo it's a different assumption18:33
amcrn+1 hub_cap grapex18:33
hub_capok but srsly18:33
grapexIt sounds like we need to keep this more flexible18:33
hub_capmoving on. lets punt to after meeting18:34
SlickNiklet's move on.18:34
imsplitbit+118:34
hub_capgood topic :)18:34
cp16netok18:34
grapexso we should send down a file- but maybe we should allow the guest agent to apply it differently18:34
datsun_F40PHeven if you decide that we'll only send one file we can't stop an intrepid tuner from doing that themselves18:34
imsplitbitdef18:34
*** DennyZhang has quit IRC18:34
datsun_F40PHand then what do we do18:34
kevinconwayhub_cap: can we do ML and not post-meeting?18:34
denis_makogongrapex, that it what i say18:34
imsplitbit+1 ML18:34
amcrn+118:34
konetzed+1 ML18:34
datsun_F40PHbut i guess once you enable root all bets are off anyway18:34
hub_cap++ML18:34
*** DennyZhang has joined #openstack-meeting-alt18:34
imsplitbitthis is a big discussion18:34
hub_cap#topic compat client changes18:34
*** openstack changes topic to "compat client changes (Meeting topic: #trove)"18:34
grapexdatsun_F40PH: Enabling root is like spitting in the face of our precious API!18:34
*** Sukhdev_ has quit IRC18:34
datsun_F40PHgrapex: and yet still allowed18:35
denis_makogonbut i would not prefer to use raw string, vote for dict18:35
hub_capso there was a review that made changes to the compat client for pep18:35
denis_makogon#link https://review.openstack.org/#/c/54900/18:35
*** brents has quit IRC18:35
denis_makogoni've updated review18:35
denis_makogontoday18:35
hub_capwell i dont think weve made a decision on what to do denis_makogon18:36
denis_makogoni took into accout all comments (alph. sort, etc)18:36
hub_capdid u take into account why i -2'd it? :)18:36
hub_capwhich is why we are talking about compat.client ))18:36
hub_capso i -2'd it cuz we said compat.client would not be updated (well i thought so)18:37
hub_capbut grapex has made a great point, that it is used18:37
*** harlowja has joined #openstack-meeting-alt18:37
hub_capits used in all our integration tests18:37
denis_makogonhub_cap, -2 only for discuss18:37
hub_capfor this discussion denis_makogon18:37
grapexI talked to our boss and we'll probably get someone around Rax to update the int tests to use the newer stuff soon, and will also figure out a way to add the XML support into the newer code paths in an OpenStacky way.18:37
denis_makogonyes =)18:37
grapexSometime this month hopefully.18:37
vipulwe still need the compat stuff to be able to do management api stuff18:38
hub_capgrapex: ok cool. vipul good point18:38
denis_makogoni only do PEP8 checks18:38
vipulso until that's sorted out it seems fair to keep it up to date18:38
hub_capim ok w/ altering this since its still in use18:38
SlickNikgood point, vipul18:38
grapexhub_cap vipul: Holy crap, there's no mgmt api stuff in the new CLI?18:38
hub_capaltering = modifying the code18:38
hub_capsince it is still used today18:38
vipulgrapex: you must not use it :p18:38
SlickNikgrapex: yes, that's the case.18:38
grapexvipul: lol18:38
grapexGUILTY18:38
SlickNiklol18:39
hub_capgrapex: not yet.. the v1 code is ther its just not in the cli18:39
robertmyerswho needs management anyway18:39
hub_capso u can still program to it18:39
grapexWell we started using it a few weeks back, but only for non-mgmt stuff18:39
hub_capu just cant $trove blah....18:39
grapexI figured it was general auth related shaningans18:39
*** akuznetsov has joined #openstack-meeting-alt18:39
grapexOk, then we'll try to add that in as well18:39
SlickNikthx grapex.18:40
vipulif that gets sorted out.. we should just nuke the compat code18:40
hub_capvipul: correct18:40
grapexvipul: Agreed18:40
hub_capwe can put it as a branch so that it is still around for someone to use it18:40
*** zane has quit IRC18:40
hub_capand NUKE it18:40
denis_makogonlol18:40
SlickNikvipul / hub_cap ++18:40
robertmyershub_cap: that is what Pypi versions are for18:41
*** zane has joined #openstack-meeting-alt18:41
hub_caprobertmyers: fair enough, we can push one more update (itll tag the code in gh anyway)18:41
robertmyerssure18:41
*** IlyaE has joined #openstack-meeting-alt18:41
hub_capok so, decision is that rax will clean up the mess i made18:41
robertmyershah18:41
esmuteseems fitting to me18:42
datsun_F40PHmore like hub_cap will clean up the mess you made18:42
*** jprovazn has quit IRC18:42
datsun_F40PH>:C18:42
hub_cap #action datsun_F40PH to clean up the mess hub_cap made18:42
datsun_F40PH#undo18:42
grapexhub_cap: Lol18:42
SlickNiklol18:42
hub_capi put a space18:42
hub_capwow i just refershed the wiki and its spinning... not loading18:42
hub_capwhats the next topic?18:43
hub_capah its up18:43
denis_makogonyup18:43
hub_cap#topic granular user privs18:43
*** openstack changes topic to "granular user privs (Meeting topic: #trove)"18:43
hub_capdatsun_F40PH: daz u18:43
datsun_F40PHyes18:43
datsun_F40PHi'd like to do it18:43
denis_makogongo18:43
denis_makogonahead18:43
datsun_F40PHand if nobody argues with my bp i'll do it like i've proposed18:43
hub_caplink it plz18:43
denis_makogon#link https://blueprints.launchpad.net/trove/+spec/user-privilege-control18:43
datsun_F40PHthere you go18:43
* denis_makogon fast as bolt18:44
*** brents has joined #openstack-meeting-alt18:44
datsun_F40PHwell this is a good sign18:44
*** jprovazn has joined #openstack-meeting-alt18:44
vipulso currently the user we create has grant all18:44
vipulwhy couldn't they do this via mysql18:44
datsun_F40PHwhy couldn't they create users or dbs via mysql18:45
denis_makogonvipul, +118:45
vipulfair enough18:45
vipuli caution against re implemetnign more mysql specific things in our api18:45
*** nati_ueno has quit IRC18:45
datsun_F40PHwell this would be buried in mysql for now18:45
*** brents has quit IRC18:45
robertmyersis this not an extrention?18:45
demorrisvipul: who says its MySQL only18:45
denis_makogonbut do we really need such functionality? i mean users, dbs ?18:45
vipulwell i don't mean mysql specific.. i should have said things you can do via the database protocol itself18:46
hub_capdenis_makogon: this is an extension18:46
kevinconwaydid somebody say users?!?18:46
robertmyerskevinconway: shhh18:46
denis_makogoni thought it came from Amazon RDS18:46
imsplitbitoh heck18:46
*** brents has joined #openstack-meeting-alt18:46
datsun_F40PHapparently it's been requested by users of our api at rax and i'd just like to implement it at least for mysql18:46
datsun_F40PHsince, cards on the table, i work at rax18:47
SlickNikSeems to me that it would be different depending on the datastore_type. So seems like a datastore-specific extension.18:47
datsun_F40PHof course it would18:47
datsun_F40PHask redis about users18:47
imsplitbitNO USERS!!!18:47
datsun_F40PHc:18:47
denis_makogonSlickNik, +118:47
imsplitbit:018:47
imsplitbit:)18:47
denis_makogon=[E]18:48
datsun_F40PHso i seek to implement this as a mysql extension primarily18:48
vipuli thought we were a provisioning api -- not a data api -- this is kinda in the middle18:48
hub_capthere is no reason to argue about this18:48
demorrissince this is an extension, I am not sure that we need to have an argument over if it is needed or not18:48
hub_capweve talked about it a billion times18:48
hub_capthis is an extension18:48
hub_capits not a core api18:48
hub_capmoving on18:48
amcrndatsun_F40PH: can you add this enhancement, but limit it to the user/databases extensions vs. adding it in instance-create?18:48
hub_capand kevinconway, no users18:49
denis_makogonagreed with vipul, Data API is for Dynamo/Simple DB18:49
*** gokrokve has quit IRC18:49
datsun_F40PHamcrn: yeah i'm not a fan of the all-in-one instance create personally18:49
amcrnexcellente'18:49
hub_capamcrn: all-in-one instance create will probably not be in v218:49
datsun_F40PHso i'll only be messing with user calls18:49
vipulwe would also need a way of limiting which privileges are 'assignable'18:50
amcrnhub_cap: hooray!18:50
demorristhe goal is not to duplicate the MySQL protocol, I get the arguments about creating a data API18:50
hub_capamcrn: unless someone can do it well, generic, not ugly18:50
hub_cap:)18:50
hub_capok core team18:50
hub_capdo we approve this? im perfectly fine w/ it18:50
demorrisbut for basic functionality around users and databases, there is value in exposing via the API as these are very common tasks when setting up the DB18:50
vipulsure what the heck18:50
hub_capill approve the BP if no one has concerns18:50
datsun_F40PHi welcome discussion and suggestions in the appropriate places18:51
hub_capHAHAHAAHAHAH vipul18:51
amcrnthat's confidence!18:51
demorrisi would rather we debate how to implement it18:51
demorrisbut I feel like most people don't care :)18:51
vipulunfortunately we don't have a good way to turn off extensions18:51
*** eankutse1 has quit IRC18:51
vipulso there's that18:51
hub_capvipul: fix it ;)18:51
datsun_F40PHvipul: we can talk about permission masks18:51
vipuldatsun_F40PH: ok cool18:52
hub_capif u want to turn off all the extensons, just change the path.. likely if u dont want users extension, u wont want root or databases either :P18:52
vipulhub_cap: yea will have to18:52
denis_makogoni could take care of extensions18:52
hub_capyea i totaly agree its crap18:52
vipulhub_cap: we don't want to turn off all18:52
hub_capdenis_makogon: ok thats a good idea. its a big upgrade18:52
hub_capi want to see it done in multiple patchsets though18:52
hub_cap1000 lines of code in 1 patchset is too painful :)18:53
datsun_F40PHso i'll begin to work on this18:53
amcrn+118:53
denis_makogonhub_cap, ok18:53
hub_capdatsun_F40PH: make sure it mirrors the way that nova/cinder/etc do it18:53
hub_capdenis_makogon: ^ ^18:53
hub_capwhoops datsun_F40PH18:53
hub_capok lets move on then?18:53
*** jasonb365 has joined #openstack-meeting-alt18:53
datsun_F40PHhub_cap: i'll consider it but my hands may be tied18:53
hub_capdenis_makogon: there should already be a blueprint fyi18:53
denis_makogoni'll do a bp for that18:53
vipulthanks denis_makogon18:53
hub_capdatsun_F40PH: your stuff will be ok... its not what denis is working on18:54
denis_makogonrefactoring for better pluggability ?18:54
datsun_F40PHsince we have a contract to uphold18:54
denis_makogonthose was mine18:54
datsun_F40PHoh i see now18:54
hub_capok moving on then?18:54
datsun_F40PHplease18:54
denis_makogonyes18:54
hub_cap#topic datastores fast follow18:54
hub_capamcrn: go go go18:54
*** openstack changes topic to "datastores fast follow (Meeting topic: #trove)"18:54
amcrn#link https://blueprints.launchpad.net/trove/+spec/datastore-type-version-followon18:54
amcrngist: there were a couple conversations around some enhancements to the datastores implementation18:55
amcrnthis is an attempt to catalog them18:55
amcrnplease add any additional concerns, comment on existing ones, etc.18:55
vipulamcrn: this is great18:55
grapexvipul: Agreed, good job amcrn.18:56
denis_makogonamcrn, looks very cool18:56
amcrnthanks18:56
cp16netyeah its long there tho18:56
ashestakov_vipul: are you ok with #2?18:56
cp16netside note i think it should be in the wiki :-P18:56
amcrncp16net: i sell cliffnotes for $5 ;)18:56
cp16netdamn you are a business man huh?18:57
cp16net:-P18:57
amcrngotta be on that hussle18:57
hub_capamcrn: he actually sells notes that a homeless dude named cliff writes18:57
cp16nethaha18:57
vipulashestakov_: yep i think that's what we agreed18:57
hub_capyes so someone should really do that work!18:58
ashestakov_vipul: you pushed on me to do this way :)18:58
vipulyea i think we agreed to follow-up on that.. and this looks like the follow-up we need18:58
hub_capok 2 min left... anyone gonna claim that?18:58
denis_makogonso, could we move on ?18:58
amcrnashestakov_: you mentioned last night you'd like to work on these?18:59
denis_makogonhttps://review.openstack.org/59231 - this bad broken code was merged =/18:59
ashestakov_amcrn: yes, but i have some questions about this18:59
hub_capok18:59
*** alazarev has joined #openstack-meeting-alt18:59
hub_cap#action ashestakov_ to do the follow up datastores work19:00
hub_capok gotta end meeting19:00
hub_cap#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
ashestakov_amcrn: #6, as i understood, output should be different depends on who requests19:00
openstackMeeting ended Wed Dec  4 19:00:12 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/_trove/2013/_trove.2013-12-04-18.01.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/_trove/2013/_trove.2013-12-04-18.01.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/_trove/2013/_trove.2013-12-04-18.01.log.html19:00
hub_caplets move to #openstack-trove19:00
*** datsun_F40PH has left #openstack-meeting-alt19:00
*** imsplitbit has left #openstack-meeting-alt19:00
grapexo_ <zzzzz19:01
*** robertmyers has left #openstack-meeting-alt19:01
*** _kpom_ has left #openstack-meeting-alt19:01
*** ashestakov_ has left #openstack-meeting-alt19:02
*** dmitryme has quit IRC19:03
*** hemanthravi has joined #openstack-meeting-alt19:04
*** yahongdu has joined #openstack-meeting-alt19:05
*** aignatov has quit IRC19:06
*** eankutse has joined #openstack-meeting-alt19:07
*** diakunchikov_ has quit IRC19:11
*** Guest85886 has quit IRC19:13
*** mugsie has left #openstack-meeting-alt19:17
*** markwash has quit IRC19:19
*** gokrokve has joined #openstack-meeting-alt19:23
*** SergeyLukjanov has joined #openstack-meeting-alt19:24
*** SergeyLukjanov has quit IRC19:24
*** hemanthravi has quit IRC19:24
*** SergeyLukjanov has joined #openstack-meeting-alt19:25
*** sarob has joined #openstack-meeting-alt19:27
*** nadya_ has joined #openstack-meeting-alt19:31
*** nadya_ has quit IRC19:40
*** dmitryme has joined #openstack-meeting-alt19:41
*** rudrarugge has joined #openstack-meeting-alt19:55
*** eankutse has quit IRC19:56
*** eankutse has joined #openstack-meeting-alt19:56
*** jdob has quit IRC20:00
*** jjmb has joined #openstack-meeting-alt20:03
*** jdob has joined #openstack-meeting-alt20:03
*** boris-42 has quit IRC20:04
*** sadasu has joined #openstack-meeting-alt20:05
*** aignatov has joined #openstack-meeting-alt20:05
*** sarob has quit IRC20:06
*** sarob has joined #openstack-meeting-alt20:06
*** jcru has quit IRC20:06
*** sadasu has quit IRC20:07
*** alazarev has quit IRC20:07
*** demorris has quit IRC20:08
*** derekh has joined #openstack-meeting-alt20:10
*** sarob has quit IRC20:10
*** sarob has joined #openstack-meeting-alt20:12
*** tanisdl has joined #openstack-meeting-alt20:13
*** sarob has quit IRC20:17
*** boris-42 has joined #openstack-meeting-alt20:22
*** alazarev has joined #openstack-meeting-alt20:26
*** jjmb has quit IRC20:26
*** jtomasek has quit IRC20:28
*** SushilKM__ has quit IRC20:34
*** sarob has joined #openstack-meeting-alt20:37
*** sarob_ has joined #openstack-meeting-alt20:38
*** sarob has quit IRC20:39
*** sarob_ has quit IRC20:40
*** sarob has joined #openstack-meeting-alt20:40
*** brents has quit IRC20:41
*** sarob has quit IRC20:45
*** sarob_ has joined #openstack-meeting-alt20:45
*** derekh has quit IRC20:46
*** sarob has joined #openstack-meeting-alt20:47
*** sarob_ has quit IRC20:48
*** brents has joined #openstack-meeting-alt20:49
*** dprince has quit IRC20:50
*** vipul is now known as vipul-away20:51
*** dmitryme has quit IRC20:53
*** alazarev has quit IRC20:53
*** MarkAtwood has joined #openstack-meeting-alt20:55
*** alazarev has joined #openstack-meeting-alt20:58
*** markwash has joined #openstack-meeting-alt20:58
*** tanisdl has quit IRC20:59
*** bdpayne has quit IRC21:00
*** bdpayne has joined #openstack-meeting-alt21:02
*** demorris has joined #openstack-meeting-alt21:03
*** bdpayne_ has joined #openstack-meeting-alt21:05
*** SergeyLukjanov has quit IRC21:05
*** tanisdl has joined #openstack-meeting-alt21:05
*** esker has quit IRC21:06
*** bdpayne has quit IRC21:07
*** harlowja has quit IRC21:09
*** katyafervent has quit IRC21:09
*** ashaikh has quit IRC21:09
*** katyafervent has joined #openstack-meeting-alt21:09
*** harlowja has joined #openstack-meeting-alt21:09
*** DennyZhang has quit IRC21:10
*** ashaikh has joined #openstack-meeting-alt21:11
*** alazarev has quit IRC21:12
*** IlyaE has quit IRC21:14
*** sballe has joined #openstack-meeting-alt21:15
*** noslzzp has quit IRC21:15
*** IlyaE has joined #openstack-meeting-alt21:16
*** denis_makogon has quit IRC21:17
*** jprovazn has quit IRC21:17
*** jjmb has joined #openstack-meeting-alt21:17
*** alazarev has joined #openstack-meeting-alt21:17
*** colinmcnamara has quit IRC21:19
*** colinmcn_ has quit IRC21:19
*** ywu has joined #openstack-meeting-alt21:20
*** radix_ has quit IRC21:20
*** jjmb has quit IRC21:25
*** julim has quit IRC21:25
*** vipul-away is now known as vipul21:25
*** jasonb365 has quit IRC21:30
*** sarob has quit IRC21:39
*** sarob has joined #openstack-meeting-alt21:39
*** jjmb has joined #openstack-meeting-alt21:43
*** sarob has quit IRC21:43
*** lsmola has quit IRC21:47
*** colinmcnamara has joined #openstack-meeting-alt21:48
*** colinmcn_ has joined #openstack-meeting-alt21:48
*** rongze has quit IRC21:49
*** jjmb has quit IRC21:49
*** rudrarugge has quit IRC21:50
*** zane1 has joined #openstack-meeting-alt21:53
*** zane has quit IRC21:53
*** CaptTofu has quit IRC21:53
*** demorris has quit IRC21:55
*** bdpayne_ has quit IRC21:56
*** zane1 has quit IRC21:58
*** harlowja has quit IRC22:02
*** brents has quit IRC22:03
*** pdmars has quit IRC22:05
*** grapex has left #openstack-meeting-alt22:06
*** noslzzp has joined #openstack-meeting-alt22:10
*** shakayumi has quit IRC22:12
*** brents has joined #openstack-meeting-alt22:12
*** lblanchard has quit IRC22:14
*** jdob has quit IRC22:16
*** betsy_ has joined #openstack-meeting-alt22:18
*** eankutse has quit IRC22:19
*** rongze has joined #openstack-meeting-alt22:19
*** betsy has quit IRC22:19
*** betsy_ is now known as betsy22:19
*** eshel has joined #openstack-meeting-alt22:22
*** harlowja has joined #openstack-meeting-alt22:27
*** rongze has quit IRC22:28
*** Barker has quit IRC22:30
*** RajeshMohan has quit IRC22:38
*** RajeshMohan has joined #openstack-meeting-alt22:38
*** rsblendido has joined #openstack-meeting-alt22:49
*** rossella_s has joined #openstack-meeting-alt22:49
*** sarob has joined #openstack-meeting-alt22:50
*** yjiang5_1 has quit IRC22:53
*** sarob has quit IRC22:54
*** rongze has joined #openstack-meeting-alt22:55
*** NehaV has quit IRC22:59
*** rongze has quit IRC23:00
*** sarob has joined #openstack-meeting-alt23:00
*** nati_ueno has joined #openstack-meeting-alt23:01
*** noslzzp has quit IRC23:02
*** noslzzp has joined #openstack-meeting-alt23:04
*** jecarey_ has joined #openstack-meeting-alt23:06
*** jecarey has quit IRC23:07
*** noslzzp has quit IRC23:08
*** alazarev has quit IRC23:08
*** brents has quit IRC23:09
*** aignatov has quit IRC23:09
*** noslzzp has joined #openstack-meeting-alt23:12
*** aignatov has joined #openstack-meeting-alt23:12
*** jecarey_ has quit IRC23:15
*** brents has joined #openstack-meeting-alt23:16
*** vipul is now known as vipul-away23:21
*** yogesh has quit IRC23:23
*** esker has joined #openstack-meeting-alt23:27
*** gokrokve has quit IRC23:27
*** aignatov has quit IRC23:29
*** rsblendido has quit IRC23:29
*** rossella_s has quit IRC23:29
*** banix has quit IRC23:31
*** esker has quit IRC23:32
*** s3wong has quit IRC23:36
*** sacharya has quit IRC23:37
*** vipul-away is now known as vipul23:41
*** alazarev has joined #openstack-meeting-alt23:42
*** mozawa has quit IRC23:45
*** yamahata_ has joined #openstack-meeting-alt23:50
*** bdpayne has joined #openstack-meeting-alt23:51
*** amytron has quit IRC23:52
*** rongze has joined #openstack-meeting-alt23:56
*** rraja has quit IRC23:57

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