Wednesday, 2014-01-08

*** sarob_ has quit IRC00:04
*** amytron has quit IRC00:05
*** sarob has joined #openstack-meeting-alt00:05
*** funzo has joined #openstack-meeting-alt00:05
*** sarob has quit IRC00:09
*** gokrokve has quit IRC00:13
*** esker has joined #openstack-meeting-alt00:13
*** kevinconway has quit IRC00:14
*** sballe has quit IRC00:15
*** sballe has joined #openstack-meeting-alt00:15
*** pballand has quit IRC00:16
*** eharney has quit IRC00:19
*** markwash_ has joined #openstack-meeting-alt00:20
*** ruhe is now known as _ruhe00:21
*** markwash has quit IRC00:21
*** markwash_ is now known as markwash00:21
*** haleyb has quit IRC00:23
*** banix has quit IRC00:23
*** yamahata has joined #openstack-meeting-alt00:26
*** yidclare1 has quit IRC00:27
*** _cjones_ has joined #openstack-meeting-alt00:29
*** haleyb has joined #openstack-meeting-alt00:35
*** SergeyLukjanov is now known as _SergeyLukjanov00:37
*** sacharya has joined #openstack-meeting-alt00:39
*** sacharya has quit IRC00:40
*** yamahata has quit IRC00:40
*** haleyb has quit IRC00:40
*** haleyb has joined #openstack-meeting-alt00:44
*** AlanClark has quit IRC00:44
*** haleyb has quit IRC00:48
*** nosnos has joined #openstack-meeting-alt00:53
*** haleyb has joined #openstack-meeting-alt00:57
*** funzo has quit IRC00:57
*** funzo has joined #openstack-meeting-alt00:58
*** devanand1 is now known as devananda01:02
*** funzo has quit IRC01:02
*** gokrokve has joined #openstack-meeting-alt01:03
*** haleyb has quit IRC01:03
*** markwash has quit IRC01:04
*** haleyb has joined #openstack-meeting-alt01:05
*** haleyb has quit IRC01:10
*** haleyb has joined #openstack-meeting-alt01:11
*** colinmcnamara has quit IRC01:14
*** funzo has joined #openstack-meeting-alt01:14
*** haleyb has quit IRC01:16
*** mozawa has joined #openstack-meeting-alt01:19
*** bdpayne has quit IRC01:22
*** haleyb has joined #openstack-meeting-alt01:23
*** bdpayne has joined #openstack-meeting-alt01:25
*** yidclare has joined #openstack-meeting-alt01:27
*** resker has joined #openstack-meeting-alt01:31
*** yidclare has quit IRC01:32
*** ashaikh has joined #openstack-meeting-alt01:32
*** esker has quit IRC01:33
*** funzo has quit IRC01:35
*** yamahata has joined #openstack-meeting-alt01:42
*** nosnos has quit IRC01:43
*** xuhanp has joined #openstack-meeting-alt01:43
*** nosnos has joined #openstack-meeting-alt01:44
*** haleyb has quit IRC01:49
*** haleyb has joined #openstack-meeting-alt01:52
*** gokrokve has quit IRC01:54
*** funzo has joined #openstack-meeting-alt01:58
*** IlyaE has quit IRC02:11
*** ijw has quit IRC02:12
*** funzo has quit IRC02:14
*** funzo has joined #openstack-meeting-alt02:17
*** funzo has quit IRC02:21
*** BBG_Stephen has quit IRC02:21
*** funzo has joined #openstack-meeting-alt02:21
*** haleyb has quit IRC02:22
*** nati_ueno has quit IRC02:23
*** haleyb has joined #openstack-meeting-alt02:25
*** haleyb has quit IRC02:31
*** resker has quit IRC02:32
*** markmcclain has quit IRC02:33
*** haleyb has joined #openstack-meeting-alt02:35
*** amytron has joined #openstack-meeting-alt02:41
*** balajiiyer has joined #openstack-meeting-alt02:43
*** nosnos has quit IRC02:43
*** colinmcnamara has joined #openstack-meeting-alt02:43
*** coolsvap has quit IRC02:43
*** haleyb has quit IRC02:47
*** dhellmann has quit IRC02:55
*** eankutse has joined #openstack-meeting-alt02:57
*** haleyb has joined #openstack-meeting-alt03:05
*** funzo has quit IRC03:11
*** funzo has joined #openstack-meeting-alt03:11
*** IlyaE has joined #openstack-meeting-alt03:12
*** funzo has quit IRC03:16
*** haleyb has quit IRC03:22
*** haleyb has joined #openstack-meeting-alt03:35
*** haleyb has quit IRC03:40
*** funzo has joined #openstack-meeting-alt03:41
*** haleyb has joined #openstack-meeting-alt03:42
*** funzo has quit IRC03:43
*** funzo_ has joined #openstack-meeting-alt03:43
*** fungi has quit IRC03:44
*** funzo_ has quit IRC03:47
*** vipul is now known as vipul-away03:48
*** doug_shelley66 has quit IRC03:50
*** harlowja is now known as harlowja_away03:52
*** vipul-away is now known as vipul03:52
*** fungi has joined #openstack-meeting-alt03:52
*** amcrn has quit IRC03:56
*** coolsvap has joined #openstack-meeting-alt04:00
*** IlyaE has quit IRC04:05
*** IlyaE has joined #openstack-meeting-alt04:12
*** gokrokve has joined #openstack-meeting-alt04:12
*** haleyb has quit IRC04:12
*** haleyb has joined #openstack-meeting-alt04:16
*** colinmcnamara has quit IRC04:19
*** sbalukoff has joined #openstack-meeting-alt04:25
*** pballand has joined #openstack-meeting-alt04:26
*** eshel has joined #openstack-meeting-alt04:31
*** IlyaE has quit IRC04:35
*** funzo has joined #openstack-meeting-alt04:44
*** eankutse has quit IRC04:45
*** funzo has quit IRC04:48
*** esker has joined #openstack-meeting-alt04:48
*** IlyaE has joined #openstack-meeting-alt04:50
*** IlyaE has quit IRC04:50
*** flwang has quit IRC04:56
*** flwang has joined #openstack-meeting-alt04:56
*** gokrokve has quit IRC04:58
*** IlyaE has joined #openstack-meeting-alt04:58
*** flwang has quit IRC04:58
*** IlyaE has quit IRC04:59
*** IlyaE has joined #openstack-meeting-alt05:00
*** chandankumar has joined #openstack-meeting-alt05:00
*** dhellmann has joined #openstack-meeting-alt05:04
*** doug_shelley66 has joined #openstack-meeting-alt05:18
*** IlyaE has quit IRC05:21
*** sballe_ has joined #openstack-meeting-alt05:23
*** sballe has quit IRC05:26
*** balajiiyer has quit IRC05:27
*** dhellmann has quit IRC05:31
*** bdpayne has quit IRC05:39
*** dhellmann has joined #openstack-meeting-alt05:42
*** flwang has joined #openstack-meeting-alt05:44
*** banix has joined #openstack-meeting-alt05:44
*** funzo has joined #openstack-meeting-alt05:44
*** IlyaE has joined #openstack-meeting-alt05:48
*** funzo has quit IRC05:49
*** IlyaE has quit IRC05:51
*** banix has quit IRC06:00
*** obondarev_ has joined #openstack-meeting-alt06:12
*** sbalukoff has quit IRC06:13
*** sc68cal has quit IRC06:14
*** sc68cal has joined #openstack-meeting-alt06:19
*** IlyaE has joined #openstack-meeting-alt06:21
*** funzo has joined #openstack-meeting-alt06:45
*** funzo has quit IRC06:50
*** IlyaE has quit IRC06:56
*** SergeyLukjanov has joined #openstack-meeting-alt07:05
*** ashaikh has quit IRC07:12
*** IlyaE has joined #openstack-meeting-alt07:18
*** jcoufal has joined #openstack-meeting-alt07:20
*** IlyaE has quit IRC07:21
*** ashaikh has joined #openstack-meeting-alt07:24
*** ashaikh has quit IRC07:29
*** markwash has joined #openstack-meeting-alt07:35
*** funzo has joined #openstack-meeting-alt07:46
*** funzo has quit IRC07:51
*** markvoelker1 has quit IRC07:54
*** markwash has quit IRC08:04
*** nadya_ has joined #openstack-meeting-alt08:10
*** coolsvap has quit IRC08:12
*** coolsvap has joined #openstack-meeting-alt08:12
*** jtomasek has joined #openstack-meeting-alt08:13
*** jtomasek has quit IRC08:20
*** jtomasek has joined #openstack-meeting-alt08:21
*** nadya_ has quit IRC08:25
*** coolsvap has quit IRC08:28
*** ikhudoshyn has joined #openstack-meeting-alt08:28
*** coolsvap has joined #openstack-meeting-alt08:30
*** sbalukoff has joined #openstack-meeting-alt08:31
*** sbalukoff has quit IRC08:35
*** flaper87|afk is now known as flaper8708:40
*** SergeyLukjanov is now known as _SergeyLukjanov08:44
*** _SergeyLukjanov has quit IRC08:44
*** funzo has joined #openstack-meeting-alt08:47
*** sbalukoff has joined #openstack-meeting-alt08:48
*** funzo has quit IRC08:51
*** SergeyLukjanov has joined #openstack-meeting-alt08:59
*** safchain has joined #openstack-meeting-alt08:59
*** nadya_ has joined #openstack-meeting-alt09:03
*** derekh has joined #openstack-meeting-alt09:11
*** nadya_ has quit IRC09:19
*** nadya_ has joined #openstack-meeting-alt09:21
*** markwash has joined #openstack-meeting-alt09:23
*** konetzed has quit IRC09:29
*** konetzed has joined #openstack-meeting-alt09:30
*** nadya_ has quit IRC09:33
*** yamahata has quit IRC09:34
*** funzo has joined #openstack-meeting-alt09:47
*** jjmb has quit IRC09:52
*** funzo has quit IRC09:52
*** flwang has quit IRC09:52
*** nadya_ has joined #openstack-meeting-alt10:01
*** xuhanp has quit IRC10:10
*** SergeyLukjanov has quit IRC10:17
*** nadya_ has quit IRC10:18
*** SergeyLukjanov has joined #openstack-meeting-alt10:22
*** SergeyLukjanov has quit IRC10:23
*** nadya_ has joined #openstack-meeting-alt10:28
*** nadya_ has quit IRC10:34
*** nadya_ has joined #openstack-meeting-alt10:35
*** jtomasek has quit IRC10:39
*** jtomasek has joined #openstack-meeting-alt10:39
*** mozawa has quit IRC10:40
*** nadya_ has quit IRC10:45
*** funzo has joined #openstack-meeting-alt10:48
*** yamahata has joined #openstack-meeting-alt10:53
*** funzo has quit IRC10:53
*** SergeyLukjanov has joined #openstack-meeting-alt10:58
*** jtomasek has quit IRC11:05
*** jtomasek has joined #openstack-meeting-alt11:06
*** yportnova has left #openstack-meeting-alt11:10
*** funzo has joined #openstack-meeting-alt11:49
*** funzo has quit IRC11:54
*** irenab__ has joined #openstack-meeting-alt11:56
*** amrith has joined #openstack-meeting-alt12:07
*** esker has quit IRC12:14
*** slagle_ is now known as slagle12:20
*** funzo has joined #openstack-meeting-alt12:23
*** jtomasek has quit IRC12:40
*** jtomasek has joined #openstack-meeting-alt12:44
*** laurelm has joined #openstack-meeting-alt12:44
*** sballe_ has quit IRC12:45
*** sballe_ has joined #openstack-meeting-alt12:45
*** coolsvap has quit IRC12:47
*** baoli has joined #openstack-meeting-alt12:57
*** heyongli has joined #openstack-meeting-alt12:57
baoliHi Yongli12:57
heyonglihello12:58
irenab__hi13:00
heyongliJohn will join us today13:00
irenab__baoli, heyongli: Did you have a chance to look at neutron doc?13:00
*** johnthetubaguy has joined #openstack-meeting-alt13:01
baoliIrenab, yes13:01
heyonglii read, but not totally finish13:01
johnthetubaguyhi, sorry I am late13:02
irenab__I want to see if it neutron part can be pushed in parallel13:02
baoliit looks good to me. I just need to spend a little more time. One comment for now is that vendor_id and product_id may be useful to the vendor plugin, I think13:02
heyonglimost of part can be parallel , i think13:02
baoliAgreed13:03
irenab__maybe tomorrow we can discuss  the neutron details13:03
irenab__but since John is here, lets talk about nova parts?13:03
heyonglisure13:03
irenab__baoli: I think you should start meeting to get logs13:04
baoliIt would be great if John can join us13:04
johnthetubaguywell I am kinda interested in the nova <-> quantum bits too13:04
baoli#startmeeting PCI passthrough13:04
openstackMeeting started Wed Jan  8 13:04:42 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:04
*** openstack changes topic to " (Meeting topic: PCI passthrough)"13:04
openstackThe meeting name has been set to 'pci_passthrough'13:04
johnthetubaguyhi, do we have a rough agenda for today?13:05
baoliHi John13:05
baoliI posted this on the wiki yesterday:https://wiki.openstack.org/wiki/Meetings/Passthrough13:05
*** sballe_ has quit IRC13:06
irenab__baoli: how do you suggest to proceed?13:06
baoliYesterday, we were discussing predefined PCI groups. Yongli doesn't seem to like the idea13:06
*** BrianB_ has joined #openstack-meeting-alt13:06
baoliLet's continue from what we have left yesterday13:06
johnthetubaguybaoli: got it, thanks13:06
*** sadasu has joined #openstack-meeting-alt13:07
ttxbaoli: will the meeting change back to Tuesdays once agreement is reached ? I haven't updated the meeting calendar given it's very temporary...13:07
baolittx, yes.13:07
ttxok, let's skip the calendar update then :)13:07
*** amrith has quit IRC13:07
baoliwe will be doing daily meetings for this week.13:08
baoliexcept for Friday/Saturday13:08
johnthetubaguybaoli: I can't promise to make all those, but lets see how it goes13:08
johnthetubaguyHave a agreed the list of use cases we want to support yet?13:09
johnthetubaguylike a short term list (for Icehouse) and longer term aims too?13:09
baolijohn, we didn't go through those cases yet. But stuck on the first part13:09
johnthetubaguyI thought use cases would be the first part, which bit are we stuck on?13:10
baoliBut I guess that we should go through them first?13:10
*** noslzzp has joined #openstack-meeting-alt13:10
*** pdmars has joined #openstack-meeting-alt13:10
irenab__baoli: there is a list of use cases you put on wiki13:10
baoliShall we start from use cases today, then?13:11
irenab__I just miss there one more case for  mixed VIFs, both sriov and vnic for same VM13:11
baoli#topic use cases13:11
*** openstack changes topic to "use cases (Meeting topic: PCI passthrough)"13:11
heyonglii think john mean the use case in the blueprint of nova.13:11
baoli#irenab, yes, I should put that in13:11
johnthetubaguyheyongli: I think we probably want both, but lets start with this wiki first13:11
heyonglisure13:12
baoli#topic SRIOV-based cloud13:12
*** openstack changes topic to "SRIOV-based cloud (Meeting topic: PCI passthrough)"13:12
baoliAny thoughts on this?13:12
johnthetubaguyCan we start with GPU passthrough?13:12
johnthetubaguyjust to keep things simple13:13
baoliOk13:13
johnthetubaguyhow do we want that to look?13:13
johnthetubaguynova boot —flavor bigGPU13:13
johnthetubaguynova boot —flavor smallGPU_4GBRAM_2_vCPUs13:14
baoliJohn, our discussion so far is based on PCI groups13:14
heyongligroups is almost identical  to pci-flavor13:14
johnthetubaguyI think there will be more agreement if we work from what the user wants, then look how to deliver that13:14
johnthetubaguyi.e. agree the problem we are solving, then look how to implement13:15
johnthetubaguythen apply that to networking13:15
irenab__johnthetubaguy: I think we mostly talked on PCI for networking, and this is quite different from GPU case13:15
baoli#agreed13:15
*** xuhanp has joined #openstack-meeting-alt13:15
johnthetubaguyI agree its different, but we need the object model to work for both right?13:16
baoliWhen we have been working on this for a while, and certainly we would think about it from user's point of view13:16
baoliAlso taking into account what existing API we have in nova/neutron13:16
irenab__johnthetubaguy: not sure it will e the same from request point of view13:16
irenab__I have strong objection to elaborate in flavor request for SRIOV NICs13:17
baoliJohn, in any case, a PCI group/pci flavor can be used in the nova server flavor13:17
irenab__which is fine for Device passthrough case13:17
johnthetubaguyyes, and I think I agree, but I would just like to see both SRIOV and GPU side by side13:17
johnthetubaguyif we agree how to setup GPU, for example, it should be very similar for SRIOV, agreed the user bit is probably different13:18
irenab__I think GPU case should be mostly as today, with extra_spec for PCI device13:18
irenab__the proposal is to change the terminology from pci_alias to pci_group13:19
heyongliirena: no , i think the alias is diffrent , we can drop but not  the same thing with group13:20
johnthetubaguyOK, can we recap what we have in the code today, if only for my benefit?13:20
johnthetubaguythen agree how GPU looks in the new(er) world?13:20
baoliYongli, can you go ahead to describe that for John?13:20
heyongliwe have now is : alias: define how you chose the device13:20
heyongliserver flavor:  use alias request your device13:21
heyongliwhite list:  select device from a host, pick which can be assign to VMs13:21
baoliJust want to add that the extra_specs/whitelist is based on PCI device's vender_id and product_id13:22
johnthetubaguyand how do the while list and alias relate again?13:22
baoliby vendor_id and product_id13:22
*** matrohon has quit IRC13:22
heyonglialias is chose device from the available pool13:22
johnthetubaguyhow does the device id come into things? only via whitelist?13:23
heyongliwhitelist chose device from all on a specific host13:23
johnthetubaguyOk, so if I want a flavor that says pick either GPUv3 and GPUv4, can I do that?13:24
heyonglialias support this13:24
heyonglidefine a alias,  say the GPUv3 or GPUv413:24
johnthetubaguyOK, so alias is a list of possible vendor_ids and product_ids?13:25
heyongliyeah13:25
johnthetubaguydoes it include device ids?13:25
heyongliwhat id do you mean?13:25
johnthetubaguythe PCI device id, where does that come into the model?13:25
heyonglino alias not include the device id ( the DB main key)13:26
*** jjmb has joined #openstack-meeting-alt13:26
johnthetubaguyso where does the device id come from? it gets seletected our of the whitelist on the device when attaching it to the VM?13:26
baoliJohn, by id, do you mean PCI slot?13:26
johnthetubaguypossibly13:26
heyonglithat infomation store in the pci device model13:27
johnthetubaguyI think I mean address, sorry13:27
heyonglialias should not include the address13:28
baolidomain:bus:slot:func13:28
johnthetubaguyright, thats the thing13:28
heyongliwhitelist doe not also, but i added alread in current  patch i released13:28
johnthetubaguyis that in the whitelist?13:28
johnthetubaguyah, OK13:28
heyongliand support the * and [1-5]13:28
johnthetubaguyso the big step between GPU and SRIOV is groups different addresses?13:29
johnthetubaguygrouping^13:29
baoliyes, they belong to different groups13:29
johnthetubaguyso that should go in the alias now? for SRIOV?13:29
*** banix has joined #openstack-meeting-alt13:30
heyonglialias don't need the address13:30
irenab__Do we talk about SRIOV for networking or general?13:30
heyongliadd the group to alias  is sufficent13:30
johnthetubaguyOK, so we are adding an extra thing called group?13:30
heyonglithis is also in my patches released13:30
johnthetubaguythat deals with grouping addresses?13:30
heyongliyeah13:30
johnthetubaguywhy is this not just part of alias, that is just a grouping right?13:30
heyongliyeah, just in group13:31
heyonglialias is global13:31
johnthetubaguy(sorry lots of dumb questions, but I just don't think I get where you are coming from now)13:31
johnthetubaguyso group is going to be local to each server?13:31
heyonglishould not say, i want the devicd had bdf is a:b:c, this is meanless13:31
baoliPCI group is global13:31
heyonglikind of local , like pci vendor13:32
*** eharney has joined #openstack-meeting-alt13:32
heyongliif we keep alias as it, this is local13:32
heyongliif we kill alias, this is going to global13:32
baoliYongli, alias is defined on the controller node13:32
heyongliyeah13:32
johnthetubaguyhmm, but its a local thing that gets referenced in a global concept (flavor)13:32
johnthetubaguyI think this is where it gets very confusing13:32
*** mozawa has joined #openstack-meeting-alt13:32
heyonglikind of  confusing, might have a better solution13:33
johnthetubaguySo, from my outsider view, this seems:13:33
heyonglibut , group is very like the vender id13:33
johnthetubaguya) roughly complete, but (b) a bit confusing ( c) re-inventing groupings we already have in other bits of nova13:34
heyongliwe can say vendor id is global, cause it's alloced by pci world13:34
johnthetubaguyI think we can agree on this though...13:34
johnthetubaguyPCI device has: vendor_id, product_id, address13:35
johnthetubaguyand we want to group them13:35
baoliwell, vendor_id is a hardware specific thing13:35
*** banix has quit IRC13:35
johnthetubaguytypes of GPU (don't care about address), types of VIF (do care about specific groups of addresses)13:35
johnthetubaguyby default we should not expose any of these devices, unless we configure nova to allow such a device on a particular host to be exposed13:36
heyongliVIF should not care the address, i think, they just need partion by address, am right ?13:36
johnthetubaguywell, they a grouped by an address range right?13:36
*** dprince has joined #openstack-meeting-alt13:36
heyongliyeah, think13:36
irenab__john: it maybe  PF13:37
irenab__parent of all Virtual Functions13:37
johnthetubaguyah, OK, so we have virtual functions from a specific address too?13:37
johnthetubaguyor is function just part of the address?13:37
baoliJoin, in SRIOV, we have PF and VF13:38
baoliPF: physical function, VF: vritual function, The function is part of the address13:38
johnthetubaguythats cool, just checking we are still grouping by address13:38
irenab__Virtual Function is a PCI device of SRIOV NIC that has Parent Function representing the SRIOV NIC itself13:38
johnthetubaguythats all cool, just trying to work out what we are grouping13:39
baoliA PCI group is a collection of PCI devices that share the same functions or belong to the same subsystem in a cloud.13:39
irenab__actually what we need for basic networking case is grouping by network connectivity13:40
baoliIrenab, that's what I mean by subsystem13:40
johnthetubaguyOK, so we need someway to link the address to the neutron network-uuid?13:41
baoliin the case of SRIOV, new --nic options will achieve that13:41
irenab__john: yes, but wee need to make sure that VM is scheduled on appropriate Host13:42
johnthetubaguywell, I am not sure it always can, the user doesn't know which host that request will land on right? it just hints to some mappings13:42
heyongli+113:42
johnthetubaguyanyways, I think we are moving foward here13:42
baoli pci group is a logical abstraction13:43
irenab__john: its an idea. Based on the VM boot request it should be scheduled on the Host that is capable to provide SRIOV nics and connect to correct physical network13:43
baoliit doesn't care where it lands, but as long as it's using a device in a particular pci group13:43
heyongliagree13:44
johnthetubaguyright, so what is the user requesting here13:44
johnthetubaguythe neutron network, and the type of connection?13:45
johnthetubaguyso passthrough, or virtual, and also which type of passthrough, 1Gb or 10Gb, etc?13:45
baolia  neutron network with a NIC that is in a particular PCI group13:45
irenab__on wiki:     nova boot --flavor m1.large --image <image_id>                     --nic net-id=<net-id>,vnic-type=macvtap,pci-group=<group-name> <vm-name>13:45
johnthetubaguyI am trying to ignore our terms here, and thing of the user13:45
johnthetubaguythink^13:45
baoliJohn, 1Gb or 10 GB is a qos thing13:46
baoliIt's not related to what we are discussing here. But conceptually, you can have a PCI group with 1GB nics13:46
johnthetubaguydepends, it could be different cards right?13:46
irenab__john: on --nic there is waht we think is needed13:46
heyonglito deal with  1G, 10G thing, add the pci device_id to alias is a good solution13:47
heyonglii think13:47
baoliAGain, you can use PCI groups to group NICs that are on different kind of cards13:48
heyonglialso work13:48
johnthetubaguyOK13:48
johnthetubaguyI have written up what I think we said here:13:48
johnthetubaguyhttps://wiki.openstack.org/wiki/Meetings/Passthrough#Definitions13:48
johnthetubaguyDo we all agree with those statements?13:48
*** doug_shelley66 has quit IRC13:49
johnthetubaguysorry, I missed a bit, please refresh13:49
johnthetubaguyextra bullet on SRIOV13:49
heyonglii post my +113:50
irenab__john: I think the last SRIOV bullet is not accurate.13:50
johnthetubaguyirenab__: yeah, I don't like it, what is a better statement?13:50
irenab__Its not specific to neutron network , its specific to provider_network that many neutron networks can be defined for13:51
baoliJohn, can we go throught the original post and see if they make sense?13:51
johnthetubaguyOK, so it could be specific to a group of netron networks?13:51
irenab__john: yes13:51
johnthetubaguyirenab__: awesome, got you, thanks13:52
*** lblanchard has joined #openstack-meeting-alt13:52
*** rossella_s has joined #openstack-meeting-alt13:52
johnthetubaguyirenab__: can you check my update please, is that better?13:53
*** rsblendido has joined #openstack-meeting-alt13:53
johnthetubaguybaoli: we can do that next, I just wanted to agree some basics of what we have, and what we need13:53
baoliok13:54
irenab__john: its OK. Not sure what you mean by specific configuration13:54
johnthetubaguyI was meaning neutron might specify settings like VLAN id13:54
irenab__john: correct13:55
johnthetubaguycool, thanks, let me add an e.g.13:55
johnthetubaguyso I guess in basic cases we pass the full nic though13:55
johnthetubaguyand its straight to the provider network13:56
irenab__each device can be configured differently, but the common part is that it has same network connectivity (to the same Fabric)13:56
johnthetubaguybut if we have virtual devices, we can do some fun stuff13:56
johnthetubaguyright13:56
irenab__john: with full NIC passthrough , I think there is nothing for neutron to do13:57
johnthetubaguyirenab__: yeah, it probably gives the guest IP addresses, and things, but yes, there is little connection info I guess13:57
irenab__In full passthrough it can be only configured from inside the VM13:58
baoliserver flavor can still be used for generic PCI passthrought13:58
irenab__at least for cases I need, we talk only of SRIOV VFs13:58
johnthetubaguyI don't get why that is, neutron DHCP can still setup, if its given the mac address?13:58
*** esker has joined #openstack-meeting-alt13:59
irenab__jogh: agree. I mean that you need VM to actually do something to get the config, like send DHCP request13:59
heyonglithey might mean pass through regular PCI13:59
johnthetubaguyirenab__: ah, yep, sorry, thats true13:59
johnthetubaguycool, so I think we can agree the GPU passthrough case then...14:00
johnthetubaguyuser requests a flavor extra specs *imply* which possible PCI devices can be connected14:00
heyonglistill base on alias, right ?14:00
irenab__john: would you be available tomorrow for this meeting to dig into SRIOV net details?14:00
johnthetubaguyI am leaving that out for now.. we can add that later14:00
johnthetubaguywhat time is tomorrow?14:01
baolisame time14:01
johnthetubaguy13.00 UTC?14:01
*** jdob has joined #openstack-meeting-alt14:01
johnthetubaguythat should be OK14:01
baoliYes14:01
irenab__great. thanks14:01
baoliDo we want to end this meeting now?14:01
johnthetubaguywe might have to soon14:01
johnthetubaguyI can do another 10 mins14:02
irenab__I can too14:02
baolicool14:02
heyonglifine14:02
irenab__Do we want to start SRIOV NIC case?14:03
*** yamahata has quit IRC14:03
johnthetubaguywell, just thinking about doing a statement like14:03
johnthetubaguyuser requests a flavor extra specs *imply* which possible PCI devices can be connected14:03
johnthetubaguyas in thats the GPU case14:03
johnthetubaguywhat do we say for the SRIOV case?14:03
irenab__I think flavor extra spec is not god solution for networking case14:04
irenab__good^14:04
baolia VM needs NICs from one or more PCI groups14:04
johnthetubaguyuser requests neutron nics, on specific neutron networks, but connected in a specific way (i.e. high speed SRIOV vs virtual)14:04
johnthetubaguydoe that make sense?14:05
johnthetubaguydoes^14:05
irenab__and VM can be attached to different virtual networks14:05
*** nadya_ has joined #openstack-meeting-alt14:05
irenab__and iterface can be attached/detached later on14:05
irenab__interface^14:05
baoliI should say, A VM needs NICs on some networks from some PCI groups14:05
johnthetubaguysome of the nics may be virtual, some may be passthrough, and some might be a different type of passthrough14:05
baoliyes14:06
irenab__john: correct14:06
johnthetubaguyI am trying to exclude any of the admin terms in the user description14:06
johnthetubaguyso we have a clear vision we can agree on, thats all14:06
baoli#agreed14:06
irenab__john: vision yes, implementation details - no14:06
johnthetubaguyOK, I updated the wiki page14:07
johnthetubaguyhttps://wiki.openstack.org/wiki/Meetings/Passthrough#The_user_view_of_requesting_things14:07
johnthetubaguydo we agree on that?14:07
irenab__john: yes14:07
johnthetubaguysorry to take up the whole meeting on this, but really happy to get a set of aims we all agree on now14:08
baoli#agreed14:08
johnthetubaguysweet14:08
*** bcrochet|bbl is now known as bcrochet14:08
heyongli+114:08
johnthetubaguyso I think the question now, is how do we get the admin to set this up and configure it14:08
johnthetubaguyand what do we call everything14:08
irenab__agree14:09
johnthetubaguythat sounds like something for tomorrow, but maybe spend 5 mins discussing one point...14:09
baoli#agreed14:09
irenab__ok14:09
johnthetubaguyat the summit we raised an issue with the current config14:09
irenab__john: can you recap14:09
johnthetubaguybasically we are trying to keep more of the config as API driven, to stop the need for reloading nova.conf, etc, and general ease of configuration14:10
johnthetubaguynow clearly not everything should be an API14:10
*** eankutse has joined #openstack-meeting-alt14:10
johnthetubaguyalso, in other sessions, we have pushed back on ideas that introduce new groups that are already covered by existing generic groupings (i.e. use host aggregates, don't just add a new grouping)14:11
baoliJohn, we have discussed configuration versus API for the past couple of meetings. Would you be able to look at the logs? I can send you the logs14:11
johnthetubaguyyeah, if you can mail me the lots that would be awesome, or are then on the usual web address?14:11
johnthetubaguydid we have nova-core review any outcomes of that yet?14:11
irenab__john: we try to define auto-discovery of PCI device in order to minimize items needed for config14:11
johnthetubaguyright that sounds good14:11
johnthetubaguyI should read up on those lots14:12
johnthetubaguylogs14:12
baoliA couple of them are in the daily logs, but not in the meeting logs14:12
johnthetubaguyah...14:12
baoliI need to find a way to link them back here. I'll try to do that14:12
irenab__baoli: I think its better you send it, since there was meeting name change and one meeting without starting...14:12
johnthetubaguycool, we should probably end this meeting, then add those pointers to the wiki page?14:13
baoliI'll send them again.14:13
baoliSure14:13
johnthetubaguycool, could we just add it to that meeting wiki page?14:13
johnthetubaguycool14:13
irenab__thanks, I think the meeting was productive. see you tomorrow14:13
baoliI'll do both. See you guys tomorrow14:13
heyonglithanks,baoli14:13
johnthetubaguyso to be upfront, I think we can do the whole grouping with host aggregates and an API to list all pci devices14:14
johnthetubaguybut yep, lets chat tomorrow!14:14
baoli#endmeeting14:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:14
openstackMeeting ended Wed Jan  8 14:14:21 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-08-13.04.html14:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-08-13.04.txt14:14
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-08-13.04.log.html14:14
*** heyongli has quit IRC14:17
*** noslzzp has quit IRC14:18
*** ijw has joined #openstack-meeting-alt14:18
*** irenab__ has quit IRC14:21
*** colinmcnamara has joined #openstack-meeting-alt14:22
*** matrohon has joined #openstack-meeting-alt14:22
*** eankutse has quit IRC14:23
*** colinmcnamara has quit IRC14:23
*** eankutse has joined #openstack-meeting-alt14:23
*** amrith has joined #openstack-meeting-alt14:24
*** amytron has quit IRC14:32
*** nadya_ has quit IRC14:34
*** doug_shelley66 has joined #openstack-meeting-alt14:36
*** colinmcnamara has joined #openstack-meeting-alt14:36
*** matty_dubs|gone is now known as matty_dubs14:37
*** amotoki has joined #openstack-meeting-alt14:37
*** tomblank has joined #openstack-meeting-alt14:37
*** rsblendido has quit IRC14:40
*** rossella_s has quit IRC14:40
*** lblanchard has quit IRC14:40
*** jjmb has quit IRC14:40
*** konetzed has quit IRC14:40
*** balajiiyer has joined #openstack-meeting-alt14:40
*** flwang has joined #openstack-meeting-alt14:41
*** rossella_s has joined #openstack-meeting-alt14:42
*** rsblendido has joined #openstack-meeting-alt14:42
*** lblanchard has joined #openstack-meeting-alt14:42
*** jjmb has joined #openstack-meeting-alt14:42
*** konetzed has joined #openstack-meeting-alt14:42
*** rossella_s has quit IRC14:49
*** colinmcnamara has quit IRC14:51
*** colinmcnamara has joined #openstack-meeting-alt14:53
*** csaba|afk is now known as csaba14:57
*** amrith has quit IRC15:01
*** Swami has joined #openstack-meeting-alt15:01
Swamihi15:01
*** amrith has joined #openstack-meeting-alt15:02
Swamisafchain ping15:02
Swamijames ping15:02
Swamirobin wong ping15:02
Swamihemanth ravi ping15:02
Swamienikanorov ping15:03
enikanorovhey15:03
Swamihi enikanorov15:03
enikanorovhi15:03
SwamiThis is will be our regular meeting slot where we discuss the distributed virtual router alias multihost15:04
Swami#startmeeting Distributed virtual router15:04
openstackMeeting started Wed Jan  8 15:04:44 2014 UTC and is due to finish in 60 minutes.  The chair is Swami. Information about MeetBot at http://wiki.debian.org/MeetBot.15:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: Distributed virtual router)"15:04
openstackThe meeting name has been set to 'distributed_virtual_router'15:04
enikanorovgood. I don't have to say much this time, so I'll be a silent listener. unless something related to lbaas arises15:05
safchainSwami, hi15:05
Swamisafchain: hi15:05
Swamisafchain: I missed you in the conference call last week. Where you not able to dial.15:05
safchainunfortunately yes15:06
*** Barker has joined #openstack-meeting-alt15:06
Swamisafchain: did you get a chance to go over the google doc15:06
safchainSwami, not since two weeks15:07
Swamienikanorov: did you get a chance to go through the google doc.15:07
enikanorovSwami: not yet15:07
Swamisafchain: ok, thanks, if you have any questions please let me know.15:07
safchainSwami, sure15:08
*** shivh has joined #openstack-meeting-alt15:08
safchainSwami, great to see call flows15:08
Swamienikanorov: Since you are here, I have a basic question related to services such as Lbaas. On how it should operate in a distributed Router mode.15:09
Swamisafchain: thanks15:09
safchainSwami, have you change something in the global design ?15:09
Swamienikanorov: What is your thought on centralizing the services versus distributed.15:09
*** rwsu has joined #openstack-meeting-alt15:09
*** pnavarro has joined #openstack-meeting-alt15:10
enikanorovSwami: that's a good question. Currently we don't have loadbalancers that operate as routers themselves, so vip is always on the tenant network15:10
Swamisafchain: what do you mean by global design. I don't think we have changed anything .15:10
enikanorovso if i understand correctly, virtual router stuff would affect association of the floating ip and the vip port15:10
Swamienikanorov: Yes you are right, I am not familiar with the LBass as you are.15:11
safchainsafchain, I mean the design of the solution, type of routers, routing, etc15:11
safchainSwami, ^15:11
enikanorovif talking about routed-mode loadbalancers things could be different, but we have not analyzed it yet, since we doesn't have such solution.15:11
Swamisafchain: nothing has changed from our original design, but we have added more content and description.15:11
enikanorovin fact we have one (which is nicira's or VMWare NSX), but it relies on the nicira edge router, so I'm not sure distributed routers are applicable there15:12
*** rsblendido has quit IRC15:12
*** rossella_s has joined #openstack-meeting-alt15:13
*** rsblendido has joined #openstack-meeting-alt15:13
Swamienikanorov: in the current LBaas service model, will the lbaas service be affected when we distribute the routers, because in this case each compute node will be having an external gateway and a related floating ip., where do you intend to have the lbaas service.15:13
Swamisafchain: Did you have any details on your proposal for the north-south.15:13
*** bill_az has joined #openstack-meeting-alt15:14
enikanorovfloating ip is a nat from gateway to the port on tenant network, in fact lbaas is even unaware of that15:14
Swamienikanorov: Yes in our design we don't have a concept of edge router, yes it makes our life easier when we a tenant has an edge router.15:14
safchainSwami, no, only the document linked on the bottom of yours15:15
enikanorovso for existing lbaas providers it doesn't matter how floating ips are maintained, because it is out of lbaas control15:15
Swamisafchain: Yes it only had the picture but no other information, that's why I was curious to know if you had any other solution.15:15
Swamienikanorov: When we have external network connectivity from each and every compute node in a multihost scenario, where will the lbaas run15:16
safchainSwami, other than yours and mine, no, I could had some details to my document15:17
*** julim has joined #openstack-meeting-alt15:17
enikanorovthat totally depends on lbaas provider. existing haproxy lbaas provider choses one of the hosts where lbaas agent runs15:17
enikanorovand starts haproxy there15:17
*** colinmcnamara has quit IRC15:17
enikanorovSwami: another providers may use VMs to bring up the balancer15:18
*** betsy has joined #openstack-meeting-alt15:18
Swamienikanorov: In the google doc, I have a picture at the end describing the services, you can take a look at it.15:19
enikanorovlet me do it right now15:19
Swamilink https://docs.google.com/document/d/1iXMAyVMf42FTahExmGdYNGOBFyeA4e74sAO3pvr_RjA/edit15:20
safchainSwami, I think one difference between the two designs is the API/CLI changes and of course  all the routing things15:20
*** sadasu has quit IRC15:21
Swamisafchain: Yes I since we are also considering the east-west we have that in place. the reason for adding the new EGA command is to utilize only single ip address in the compute nodes, otherwise each EGA will consume one IP address. How are you handling it?15:22
shivhcan one maintain a single routed ip address for the distributed virtual router? Do we have to have one IP address per host?15:23
Swamishivh: hi15:24
*** ttx has quit IRC15:25
*** ttx has joined #openstack-meeting-alt15:25
*** ttx has quit IRC15:25
*** ttx has joined #openstack-meeting-alt15:25
shivhhi, interesting work you are doing. I was trying to see if we can use vip concepts here as well.15:25
safchainSwami, for north-south, the traffic goes through the "classical"  l3 agent, only compute node having floating ip are directly connected to external network15:25
Swamishivh: We do have only one single routed ip address for all the routers that we have for distributed routers. But for external connectivity, if you enable a Gateway on each and every node, then each node will have a public ip address.15:25
shivhgot it. my question is answered. thx.15:26
*** amytron has joined #openstack-meeting-alt15:27
*** dprince has quit IRC15:27
Swamisafchain: When you say it uses the classical l3 agent, for normal external connectivity to the public network, does the tenat still use the gateway in the network node.15:28
safchainSwami, only if the tenant doesn't use any floating ip15:29
Swamisafchain: ok, if the tenant uses floating ip for a particular VM, then how do you route the traffic.15:30
safchainSwami, if the tenant use one floating ip, the floating ip is scheduled on the compute node15:30
safchainSwami, what do you mean by "route the traffic"  ? north-south or east-west ?15:31
Swamisafchain: I meant north-south.15:31
*** markmcclain has joined #openstack-meeting-alt15:31
Swamisafchain: for the floating ip case, the traffic will get out from the compute node and all other VM traffic will then move through the network node external net. ( am I right).15:32
safchainSwami, no only this vm will use the floating ip15:33
safchainSwami, all others will use the current l315:33
*** flwang has quit IRC15:33
Swamisafchain: ok thanks.15:33
Swamienikanorov: did you get a chance to look at the doc.15:33
enikanorovlooking at it right now.15:34
Swamienikanorov; thanks.15:34
Swamisafchain: The only issue that we see in our current model is how to tie the services network with the distributed network?15:35
*** flwang has joined #openstack-meeting-alt15:36
safchainSwami, which services, fwaas, lbaas ?15:36
enikanorovSwami: i need to think about the scheme. at first glance it doesn't seem different from single router at which loadbalancer works (if we had such insertion mode for lb)15:36
*** xuhanp has quit IRC15:37
Swamisafchain: I was talking about the VPNaaS and LbaaS15:37
Swamienikanorov: thanks, think through that and I will chat with this week.15:38
enikanorovSwami: we'll have an lbaas meeting tomorrow at 14 utc on #openstack-meeting15:38
enikanorovi'll try to raise the discussion on this15:38
Swamienikanorov: Ok I will try to join, it is too early, but will try.15:39
enikanorovok. i don't think it's required, probably such discussion is a bit premature since there are no plans to introduce routed lb for icehouse15:39
enikanorovbut I'll let folks know about the bp and your design doc15:40
Swamisafchain: I need to discuss the next steps. So if you have any concerns or questions on the doc, please send me your thoughts or ideas or proposals.15:40
safchainSwami, yes of course and I will update my doc15:40
*** BrianB_ has quit IRC15:40
Swamisafchain: Also if you want to talk to me and understand more on the design we can have a session.15:40
Swamienikanorov: Thanks for your help.15:41
safchainSwami, sure, I will update the doc, I after I will ping you to discuss about it15:41
enikanorovno prob15:41
Swamiok, thanks15:41
Swamifolks I need to drop off early today.15:41
safchainSwami, ok no prob15:42
SwamiSo I will end the discussion and if anything is required please, send me an email. Folks also don't wait for the meeting and if you have any questions feel free to send me.15:42
SwamiThanks for joining.15:42
shivhThanks for organizing.15:42
Swami#info Next week I am planning to have a global design discussion.15:43
*** flwang has quit IRC15:43
safchainSwami, thanks for the meeting15:43
*** tomblank1 has joined #openstack-meeting-alt15:43
SwamiThank you all.15:43
Swami#endmeeting15:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:43
openstackMeeting ended Wed Jan  8 15:43:41 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-01-08-15.04.html15:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-01-08-15.04.txt15:43
openstackLog:            http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-01-08-15.04.log.html15:43
*** Swami has left #openstack-meeting-alt15:44
*** akuznetsov has quit IRC15:44
*** tomblank has quit IRC15:44
*** coolsvap has joined #openstack-meeting-alt15:47
*** sballe has joined #openstack-meeting-alt15:51
*** sballe has quit IRC15:52
*** chandankumar has quit IRC15:53
*** chandankumar_ has joined #openstack-meeting-alt15:53
*** chandankumar__ has joined #openstack-meeting-alt15:55
*** kevinconway has joined #openstack-meeting-alt15:55
*** jecarey has joined #openstack-meeting-alt15:56
*** akuznetsov has joined #openstack-meeting-alt15:56
*** rcurran has joined #openstack-meeting-alt15:57
*** chandankumar_ has quit IRC15:57
*** rkukura has joined #openstack-meeting-alt15:58
asadoughihi16:00
*** xuhanp has joined #openstack-meeting-alt16:01
rkukurahi16:01
mesteryhi16:01
shivhhi all16:01
matrohonhi16:01
*** Sukhdev has joined #openstack-meeting-alt16:01
*** BrianB_ has joined #openstack-meeting-alt16:01
mestery#startmeeting networking_ml216:02
openstackMeeting started Wed Jan  8 16:02:02 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:02
openstackThe meeting name has been set to 'networking_ml2'16:02
mestery#link https://wiki.openstack.org/wiki/Meetings/ML2 Agenda16:02
mesterySo, welcome back from the holidays everyone!16:02
mesteryWe've got an agenda heavily focused on bugs and Binding Management today.16:02
mesteryBut first, lets cover action items from the previous meeting 3 weeks ago.16:03
mestery#topic Action Items16:03
*** openstack changes topic to "Action Items (Meeting topic: networking_ml2)"16:03
mesteryasadoughi: Thanks for sending out UT coverage!16:03
mestery#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/022649.html ML2 Unit Test Coverage16:03
asadoughimestery: no problem.16:03
asadoughithe most useful one to look at now, i think, is the sorted and filtered output http://paste.openstack.org/show/55375/16:03
mestery#link http://paste.openstack.org/show/55375/ Sorted and filtered ML2 UT Coverage16:04
asadoughiso, at the bottom, you'll see what's lacking the most line coverage16:04
mesteryThanks asadoughi!16:04
*** dprince has joined #openstack-meeting-alt16:04
mesteryasadoughi: Would you mind filing a bug (or bugs) to track the things we need to add coverage for?16:04
rkukura+116:04
asadoughimestery: a bug per row in the file?16:05
asadoughimestery: threshold?16:05
mesteryThat would be a large number of bugs, but would allow for splitting things up quite well :)16:05
mesteryrkukura: Thoughts on bug per row?16:05
rkukurashould be possible to look over the files and see if the lines not covered should be, or if they are code that really should never execute16:06
*** amrith has quit IRC16:06
*** pcm_ has joined #openstack-meeting-alt16:06
rcurrani was planning on fixing all drivers/cisco under one bug16:06
mesteryrcurran: Thanks! Is there a bug for that? If not, please file one.16:07
asadoughiok, i can aggregate the ones like that16:07
asadoughiinto one bug16:07
mesteryasadoughi: Thanks!16:07
rcurrani thought i did. if not then i'll create one16:07
*** ozstacker has quit IRC16:07
mestery#action rcurran to verify if a bug exists for Cisco ML2 UT coverage16:07
mestery#action asadoughi to verify UT coverage and file bugs for appropriate areas16:07
mesteryOK, lets move on now.16:07
*** ozstacker has joined #openstack-meeting-alt16:08
rkukuraif the issues with the type drivers are similar, you could aggregate those16:08
mestery#topic Binding Management16:08
*** openstack changes topic to "Binding Management (Meeting topic: networking_ml2)"16:08
asadoughiok, sounds good16:08
*** yamahata has joined #openstack-meeting-alt16:08
mesterySo, rkukura and I were chatting about this yesterday.16:08
mesteryWe have some issues around the binding which we wanted to discuss here.16:08
mesteryrkukura: Thanks for adding some items to the agenda there. :)16:08
Sukhdevcan I ask a question?16:09
rkukuraSukhdev: you just did!16:10
mestery:)16:10
*** gokrokve has joined #openstack-meeting-alt16:10
*** xuhanp has left #openstack-meeting-alt16:10
*** amrith has joined #openstack-meeting-alt16:10
*** ashaikh has joined #openstack-meeting-alt16:10
Sukhdevha ha - funny!!16:11
rkukuraPlease, don't hesitate to speak!16:11
Sukhdevwhat is the acceptable level of coverage?16:11
mesteryFor UT?16:12
Sukhdevyes16:12
rkukuraSukhdev: Not sure about others, but my view is that meaningful code should be 100% covered, but some error handling code is acceptable to not cover.16:12
mestery+1 ^^^^16:12
rkukuraAlso, things like abstract methods in base classes don't need coverage (not sure if they get reported)16:13
mesteryThanks for answering that rkukura.16:13
mesteryNow, lets get back to binding management.16:14
*** xuhanp has joined #openstack-meeting-alt16:14
mesteryLets discuss "Original vs. Bound Segment" now.16:14
mestery#link https://review.openstack.org/#/c/62380/ WIP around "Original vs. Bound Segment"16:14
matrohonthis was just a patch to illustarte my words16:15
matrohonduring the mail discussion16:15
mesterymatrohon: OK, thanks, I think it moves in the right direction :)16:15
matrohonit has to be improved and tested16:15
*** banix has joined #openstack-meeting-alt16:16
* mestery nods.16:16
*** eankutse has quit IRC16:16
*** eankutse has joined #openstack-meeting-alt16:16
rkukuraIs the basic idea to make PortContext.original_bound_segment available to MDs in port_update_precommit and port_update_postcommit?16:17
rcurranand the delete_port_pre/postcommit()?16:17
matrohonrkukura: yes16:17
*** amrith has quit IRC16:17
*** IlyaE has joined #openstack-meeting-alt16:18
rkukurarcurran: I guess if the unbind is implicit and part of the delete, then it makes sense for this to be visible in the delete calls16:18
rcurranthat's what i was thinking16:19
rkukuraI think that would mean that the unbind occurred before the delete transaction, but maybe it should be occuring as part of the transaction (i.e. not happen if the delete TX rolls back)16:19
rkukuraSo this gets to the heart of the original issue - how does unbind relate to port_delete?16:20
*** nadya_ has joined #openstack-meeting-alt16:20
rcurrani have these same questions. i used matrohon's bug (instead of emails) to get these conversations going16:20
mesteryDoesn't unbind have to happen BEFORE a delete?16:21
rkukuramestery: If it does happen before delete, I think it needs to be port_update from the view of the MDs.16:21
mesteryrkukura: That makes sense. But would the case be for having it happen AFTER the delete? To me, that doesn't make sense.16:22
*** xuhanp has quit IRC16:22
rkukuraIn that case, the client does port_delete, the drivers all see port_update for the unbind with bound_segment none and old value in orignal_unbound_segment, and then the drivers all see port_delete with none in both bound_segment and original_bound_segment16:22
*** SergeyLukjanov has quit IRC16:23
rkukuraI think the other option is that is is part of the delete itself16:23
mesteryThat makes sense as well I think.16:23
rkukuraBut that means that if the delete TX rolls back, the unbind never happened.16:24
rcurranright, that's where we left off before the break :-), i could rewrite the cisco nexus md to work to that design16:24
mesteryrcurran: So you're on board with this approach then?16:24
rkukuraDo we have any strong arguments for/against either of the two approaches (explcit or implicit)?16:25
*** jjmb has quit IRC16:25
rkukurarcurran: Not sure which approach you are referring to16:25
rcurranyour comment from 11:2216:26
rkukuraI don't have timestamps16:26
mesterySo explicit.16:26
rcurranright now i "unbind/delete" cisco nexus md resources on delete_port16:26
shivhI am seeing 2 approches in the above convesation: 1. unbind as part of delete 2. delete can happen only for unbound ports16:26
shivhI see #2 to be simple.16:26
matrohonthe first approach looks better to me, MD could react at bindings update16:26
rcurrani can change to update_port_pre/postcommit() as long as i have access to the bound segment info (and know that it's unbinding)16:27
matrohonbut I don't see any use cases yet :)16:27
*** jecarey has quit IRC16:27
rkukuraI'm a bit concerned about two separate TXs from one API call16:28
rkukuraIf we do the unbind first, with its own port_update_precommit and port_update_postcommit, then do the port_delete_precommit and have to roll back, we've left a mess16:29
*** Barker has quit IRC16:29
mesteryrkukura: So making it implicit is easier from a DB perspective then?16:29
rkukuraI think I'm leaning towards implicit, where the unbind is part of the delete TX, and MDs only see port_delete_[pre|post]_commit16:30
*** tomblank has joined #openstack-meeting-alt16:30
mesterySo then as long as we have hte original bound segment available, will that satisfy your requirements rcurran?16:31
*** jecarey has joined #openstack-meeting-alt16:31
*** esker has quit IRC16:31
shivhI like #1 approach for its elegance. Does holding the transaction for that long going to affect perf.16:31
*** tomblank1 has quit IRC16:31
rcurranthat would be my question ... just need accessing to the original_bound_segment on delete_port_pre/postcommit()16:31
rkukuraSo then the question is whether the unbind_port call on the bound MD happens before the delete_port_precommit calls on all MDs, or after them but before the delete_port_postcommit calls16:32
rkukurashivh: I think we'd make sure no postcommit calls happen during the TX, and MDs would only make remote calls in the postcommit calls16:32
mesteryI don't understand how we can delete a port before unbinding it, pre or post. I think we need to unbind before we delete it.16:34
rkukuramestery: I guess the unbind happens as part of the delete TX, but the MD handles it in the port_delete_postcommit call after that TX.16:35
shivhrkukura: worth discussing?: splitting the api and let the app decide to make sure it is unbound before sending delete.16:35
rkukuraRight now the bind_port() and unbind_port() calls happen inside transactions.16:36
rkukuraI think our current calling of bind_port() inside the TX is a problem because the MD may need to make a remote call to see if it can bind that port.16:36
rcurranwhich is why, today, delete_port_precommit() has access to the bound_segment, but delete_port_postcommit does not16:37
matrohonrkukura : agrre16:37
mesteryrkukura: I agree with that.16:37
mesteryOK, so lets circle back here and make sure everyone agrees what we've talked about.16:39
rkukurarcurran: We absolutely need to make sure all MDs see which segment has been unbound in a postcommit call, whether that is port_delete_postcommit or port_update_postcommit16:39
mesteryrkukura: Care to summarize?16:39
rcurranrkukura: agreed16:40
rkukuraWhat I just said to rcurran is the original issue, but we also need to look at the bind_port() TX issue, and come up with an overall solution16:40
rkukuraI would be willing to look at how to move bind_port() out of the TX this week, and propose a patch or at least explain the options in email before Monday16:41
rcurrangreat16:41
mesteryrkukura: That would be awesome! Consider it yours.16:41
matrohonwhen an MD is responsible for the binding it need to ask its external device during the pre call, to be able to wright the decision of the extrernal to the DB, no?16:41
mestery#action rkukura Look at moving bind_port() out of the TX and send email or a WIP patch to discuss.16:42
mesterymatrohon: I think so, yes. That has to happen outside the TX for obvious reasons.16:42
*** ametts has left #openstack-meeting-alt16:42
rkukuramatrohon: right16:42
rkukuraI'll look at all the things that can trigger binding, unbinding, and rebinding, and see if we can handle those with a minimal number of transactions.16:43
mesteryThanks rkukura.16:44
mesteryIs there anything else to discuss with regards to binding now?16:44
rkukuraA port_update that changes the host_id is probably the interesting case - not clear if the bind_port on the MD(s) should happen before the port_update_precommit calls16:45
*** doude_ has joined #openstack-meeting-alt16:45
mesteryI'm not clear on that one either, but some MDs will again need to make remote calls in that case.16:45
rkukuramaybe the interaction with the MD for bind_port needs two phases, one to check and one to finalize16:46
*** alagalah has joined #openstack-meeting-alt16:46
mesteryI think that makes sense rkukura.16:46
rkukuraShould we move this to email or #openstack-neutron?16:46
matrohonsalv-orlando had some issues with binding too, did he talk to you?16:46
matrohonrkukura : it's a good idea16:47
rkukuramatrohon: Is this the issue that marun has also been raising about the agent liveness and this not being a realtime system?16:47
rcurrani prefer email to keep this discussion going16:48
*** sballe has joined #openstack-meeting-alt16:48
rkukurarcurran: OK, I will send an email with a proposal or set of options ASAP16:48
rcurranthanks16:48
*** alagalah has quit IRC16:49
matrohonrkukura : https://bugs.launchpad.net/neutron/+bug/125389616:49
*** amrith has joined #openstack-meeting-alt16:49
*** gokrokve has quit IRC16:50
matrohonrkukura : https://bugs.launchpad.net/neutron/+bug/1253896/comments/3016:50
*** gokrokve has joined #openstack-meeting-alt16:50
*** matty_dubs is now known as matty_dubs|lunch16:51
rkukuramatrohon: thanks16:51
*** nadya_ has quit IRC16:51
mesteryOK, rkukura will continue this discussion on the ML now.16:52
mesteryWe have 8 minutes left.16:52
mesteryI wanted to cover one more thing and leave open discussion.16:52
mestery#topic Bugs16:52
*** openstack changes topic to "Bugs (Meeting topic: networking_ml2)"16:52
mesteryI listed some bugs in the agenda.16:52
mesteryPlease have a look at those, it would be good to try to review those ones this week.16:52
*** mozawa has quit IRC16:52
mesteryIf there are other ML2 related bugs not there, please add them to that agenda or ping rkukura or myself for core reviews.16:53
mestery#topic Open Discussion16:53
*** openstack changes topic to "Open Discussion (Meeting topic: networking_ml2)"16:53
shivhmestery, rkukura: need your review cycles for https://review.openstack.org/#/c/6012916:53
*** nadya_ has joined #openstack-meeting-alt16:53
mesteryshivh: Will definitely take a peek at this one!16:53
rkukuraLets not drop the ball on the TypeDriver refactoring that opens up the set of provider attributes16:53
shivhthanks. need to progress for tempest with this...16:53
rkukurashivh: I'll look at that16:54
shivhrkukura, mestery: thanks16:54
*** gokrokve has quit IRC16:55
mesteryrkukura: Good call! Do you have that link handy by any chance?16:55
asadoughire:blueprint ovs-firewall-driver, status update: continuing to make progress on existing reviews and working on items that will further agent before getting to the "meat" of the firewall16:55
*** markmcclain has quit IRC16:55
mesteryasadoughi: Thanks for the update!16:55
doude_What about the sumit discussion https://docs.google.com/document/d/1ZHb2zzPmkSOpM6PR8M9sx2SJOJPHblaP5eVXHr5zOFg/edit ?16:56
rkukuraHas anyone been tracking the SRIOV / PCI-passthru work from an ML2 perspective?16:56
*** tsimmons has joined #openstack-meeting-alt16:56
doude_RPC handling in ML2 for Type and Mechanism Drivers16:56
*** jmcbride has joined #openstack-meeting-alt16:56
rkukuradoude_: Do we have a BP for this?16:56
*** jmcbride has quit IRC16:56
mesteryrkukura: Regarding PCI-passthru, I've been in touch with ijw and some Cisco folks working on that.16:56
mesteryrkukura: We should attend their meeting next week on IRC and bring that up perhaps.16:56
rkukuramestery: +116:57
* ijw wavs16:57
doude_I don't find bp for that, I don't remember who initiate it16:57
*** pcm_ has left #openstack-meeting-alt16:57
* mestery has now unleashed ijw with 3 minutes left in this ML2 meeting.16:57
doude_the gdocs is owned by Arvind Somya16:57
mesteryI think asomya did that Google Doc if I'm not mistaken.16:57
mesterydoude_: I'll ping asomya on that one and see where he's at with it, there is no BP right now.16:57
*** mugsie has joined #openstack-meeting-alt16:57
ijwSo yes - we know in theory what we want to do in the plugin but I don't know we have the skillset to write one.  Happy to discuss with anyone who's interested.16:57
mestery#action mestery to ping asomya around https://docs.google.com/document/d/1ZHb2zzPmkSOpM6PR8M9sx2SJOJPHblaP5eVXHr5zOFg/edit16:58
*** esker has joined #openstack-meeting-alt16:58
asadoughiijw: who is we and what are you takling about?16:58
mesteryijw: rkukura and I will join the passthrough meeting next week and bring up ML2 issues there.16:58
ijwPCI group - me, baoli, irenab, heyongli16:58
asadoughiijw: nevermind16:58
doude_mestery: ok, thanks. I plan to do some work in ML2 which need to use thaht16:58
rkukuraijw: I'll try to catch up on the PCI email thread beforehand16:59
mesteryOK, we're reaching the end of time now everyone.16:59
ijwNext passthrough meeting is tomorrow 1300CET #openstack-meeting-alt, I think16:59
mesteryLets continue discussions on ML or in-channel.16:59
rkukuraijw: thanks!16:59
mesteryAnd we'll see you all next week, same IRC-time, same IRC-channel. :)16:59
mestery#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
*** _cjones_ has left #openstack-meeting-alt16:59
openstackMeeting ended Wed Jan  8 16:59:44 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-01-08-16.02.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-01-08-16.02.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-01-08-16.02.log.html16:59
*** rcurran has quit IRC17:00
kiall#startmeeting designate17:00
openstackMeeting started Wed Jan  8 17:00:07 2014 UTC and is due to finish in 60 minutes.  The chair is kiall. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: designate)"17:00
openstackThe meeting name has been set to 'designate'17:00
*** esker has quit IRC17:00
ijwrkukura: it's fairly nonspecific with respect to ml2 at the moment, but you could check https://docs.google.com/document/d/1svN89UXKbFoka0EF6MFUP6OwdNvhY4OkdjEZN-rD-0Q/edit# (that is very explicitly my take on how to do it and not by any stretch the agreed approach)17:00
kiallHey guys17:00
*** SergeyLukjanov has joined #openstack-meeting-alt17:00
*** vinod has joined #openstack-meeting-alt17:00
*** csaba is now known as csaba|afk17:00
kiallHappy new year etc etc :) Who do have around today?17:00
*** jmcbride has joined #openstack-meeting-alt17:00
vinodhere17:00
eankutsehappy new year! :-)17:00
rkukuraijw: Thanks17:00
mugsieo/17:00
tsimmonsHey guys17:00
*** chandankumar__ has quit IRC17:00
betsyhere17:01
*** sacharya has joined #openstack-meeting-alt17:01
kiallSo - Lets dive right in then..17:01
kiallFirst topic was from jmcbride17:01
kiall#topic esignate mini-summit is January 27 to 2917:01
*** openstack changes topic to "esignate mini-summit is January 27 to 29 (Meeting topic: designate)"17:01
kiall#topic Designate mini-summit is January 27 to 2917:01
*** openstack changes topic to "Designate mini-summit is January 27 to 29 (Meeting topic: designate)"17:01
*** artom has joined #openstack-meeting-alt17:01
artomo/17:02
eankutselet's skip for now17:02
kialleankutse: oh, joe AFK?17:02
*** esker has joined #openstack-meeting-alt17:02
eankutseyes17:02
kiallOkay - We'll leave that to next week then17:02
tsimmonsoh wait17:02
* kiall waits17:02
kiall:)17:02
tsimmonsI think he's typing :P17:02
*** rjrjr has joined #openstack-meeting-alt17:03
jmcbrideI'm here guys17:03
kiallCool :)17:03
*** sarob has joined #openstack-meeting-alt17:03
kiallOkay - So, we need to start thinking about the agenda for the face to face meet in Austin at the end of Janurary17:03
*** sarob has quit IRC17:04
kiallFrom my point of view, I want to get as much input about what you guys want rather than myself or graham putting the agenda together!17:04
*** imsplitbit has joined #openstack-meeting-alt17:04
jmcbrideyes, we started brainstorming some topics, here is what I have:17:04
imsplitbito/17:04
*** rkukura has left #openstack-meeting-alt17:04
*** sarob has joined #openstack-meeting-alt17:04
jmcbride1. Some team building17:04
jmcbride2. Figure out server pools17:04
*** imsplitbit has left #openstack-meeting-alt17:04
jmcbride3. Find ways to improve our development process (in particular, breaking down work and adding to transparency on progress)17:05
jmcbride4. Blueprint review17:06
jmcbride5. code code code!17:06
jmcbride6. v2 breakdown and finish17:06
jmcbrideThoughts?17:07
mugsielooks good17:07
kiallOkay, I reckon we'll fill up the two a half days with that lot - I think #3 is probably the most important from my point of view17:07
rjrjragreed17:07
eankutselooking good17:08
rjrjrwhat dates in january?17:08
jmcbridekiall: agreed17:08
tsimmonsJanuary 27 to 2917:08
kiallrjrjr: Jan 27th through 29th17:08
kiallI'll be flying to Austin on the .. umm.. 26th or so, and heading to Seattle on the afternoon of the 29th17:09
*** sarob has quit IRC17:09
mugsieas will I17:09
*** sarob has joined #openstack-meeting-alt17:09
rjrjrsorry, was the austin face to face info published somewhere?  been out of it for a few weeks...17:10
*** datsun180b has joined #openstack-meeting-alt17:10
kiallrjrjr: jmcbride has organized it17:10
rjrjrk17:10
jmcbriderjrjr: it hasn't been published yet - we mostly just worked it out towards the end of the year 2013 via IRC and other discussions.17:11
*** sarob has quit IRC17:11
*** sarob has joined #openstack-meeting-alt17:11
kiallOkay - So, I'll spend some time over the next week trying to take ^ list, and put together some more detail on what to discuss for each.17:11
jmcbridekiall: if you'd like, I can draft a target agenda to fill out the days and run it by you and everyone17:12
*** jcoufal has quit IRC17:12
kiall#action kiall put together an agendawiki page based on ^, fill with as much detail as possible.17:12
kialljmcbride: ah - great :)17:12
kiallI'll leave it to you so17:12
kiallLets come back to this next week once that page is up then..17:12
*** sarob has quit IRC17:12
kiall#topic Filtering Blueprint17:12
*** openstack changes topic to "Filtering Blueprint (Meeting topic: designate)"17:13
eankutseyes17:13
eankutseBased on discussions with Kiall17:13
kiallThis one is from eankutse, the BP looks great.. I do have a few comments though17:13
eankutseI put together a blueprint for Filtering (Search) feature17:13
kiall#link https://wiki.openstack.org/wiki/Designate/Blueprints/Filtering_API17:13
eankutsehttps://blueprints.launchpad.net/designate/+spec/filtering17:13
eankutsehttps://wiki.openstack.org/wiki/Designate/Blueprints/Filtering_API17:13
eankutseI need some feedback when you all get some time17:13
eankutseto look at it17:14
eankutsein the next couple of days17:14
eankutse:-)17:14
kiallSure - I've given it a look over, and have some feedback.. Not sure if anyone else has yet though ;)17:14
*** sarob has joined #openstack-meeting-alt17:14
eankutsecool17:14
kiallThe first thing that stood out for me was the /zones/ipaddresses endpoint17:14
eankutseyea...17:14
kiallI'm not sure I totally agree, as it's a special case for IPs versus a generic method.. e.g. What about CNAME values etc?17:15
eankutsethose might be on recordset17:15
kiallI think a better option might be to have a /records endpoint in addition to /zones/{id}/records17:15
*** sarob has quit IRC17:15
*** shivh has quit IRC17:16
kiallThat endpoint wouldn't be filtered by zone, so a /records?filter=bla would get the same results17:16
kiallThoughts?17:16
eankutsethe goal being that we can have a privleged user filter across all zones17:16
eankutsebelonging to all tenants17:17
kiallYea, and "normal" users would have access to /records too, but filtered to just their tenant17:17
*** sarob has joined #openstack-meeting-alt17:17
eankutsethat should work17:17
eankutseThx. I'll modify17:17
kiallThe thing I don't like about that, is the duplication .. And I know mugsie will call me up on that ;)17:17
*** markwash has quit IRC17:18
eankutsemugsie: what do you think?17:18
mugsieyeah, I personaly disagree with the spearate endpoints17:18
*** yamahata has quit IRC17:18
mugsiefor me personally, I like the logical sub reasource style API17:18
artomGet rid of /zones/{id}/records entirely?17:19
*** markwash has joined #openstack-meeting-alt17:19
mugsiei know that then causes problens for searching across things.. so i am not sure how we do that17:19
artomLeave just /records, behaving as described by kiall and eankutse above...17:19
kiallartom: no, that's the duplication part.. /zones/{id}/records would stay, but /zones/{id}/records/{id} would probably move to /records/{id}17:19
mugsiewhich is the bit i dont like17:20
artomAh, right.17:20
*** tanisdl has joined #openstack-meeting-alt17:20
kialland /zones/{id}/records would essentially be an alias for /records?zone_id={id}17:20
mugsieyou should be able to walk the tree of resources17:20
rjrjrkiall, i like that.17:20
mugsiehowever, it does mean urls in the future wont be as clear17:21
eankutsemugsie: I see your argument for "ReSTfulness" here17:21
eankutseand opaqueness17:21
mugsieeg /zones/<id>/records/<id>/recordsets/ is obvoiusly recordsets in the record<id> in zone <id>17:21
*** sarob has quit IRC17:22
mugsieinstead of /recordsets?record=<id>17:22
mugsiepersonally, url query params should be used for small changes, not filtering sub resources17:23
*** sballe has quit IRC17:23
mugsie(imo)17:23
*** sballe has joined #openstack-meeting-alt17:24
kiallI personally think having a top level /records and /recordsets is the better choice, it's not perfect, but not awful either..17:24
kiallanyone else have strong opinions either way?17:24
*** pballand has quit IRC17:24
rjrjrwhat is the other option to filter across zones?17:24
rjrjri just see /records allowing that.17:25
kiallmugsie: BTW, so what would you suggest as the alternative to filter accross all records17:25
kialle.g. as an admin trying to locate records without knowing which zone/rrset it's in?17:25
mugsiepeople like Jira etc generally use a /search end point, that can allow freeform searching17:25
artom"search" is hardly a resource ;)17:26
mugsieand then the search doesnt have to be tied to a particular type of resource either17:26
artomBut I can see that working...17:26
*** bdpayne has joined #openstack-meeting-alt17:26
tsimmonsI could see a /records endpoint just for admins to do operations on random records, but then for individual tenants keeping the zone/id/records/id as well.17:26
artomIt makes a single "weird" endpoint, as opposed to them being all over the place.17:26
mugsiethey can walk the responce, and use the self links to do operations on the results17:26
kiallA generic search endpoint that can match against anything? records/zones/rrsets/tsig keys?17:27
*** IlyaE has quit IRC17:27
mugsieyeah, depending on what you have access to17:27
artomPerhaps /search/{resource_type}?17:27
tsimmonsOr you could have search/zones, etc17:27
kiallI'm not sure I'd want to try and make that work without bringing in something like ElasticSearch/Lucene/etc.. Which I really don't think is an option17:27
betsyI like that idea17:27
rjrjrso, /search/records?  why not just /records then?17:27
kialltsimmons: is /search/records not the same thing really as /records ?17:28
mugsieno17:28
artomBecause /search/zones, /search/keys etc17:28
*** Sukhdev has quit IRC17:28
*** nadya_ has quit IRC17:28
tsimmonsPretty much, but you generlize all search in /search17:28
mugsieit allows us to keep the decent urls, and and can allow us to create predefined searches etc in the furture17:28
kiallAlso - Bear in mind that, I'm not aware of any OpenStack API that offers true "Search" (as against simple filtering) .. I'm not sure that's a convention we should break17:29
*** hub_cap is now known as carnac17:29
*** jtomasek has quit IRC17:29
*** jmcbride1 has joined #openstack-meeting-alt17:29
tsimmonsIf you can't have records without zones it seems a little odd to have an endpoint for all of them. But I can understand the need to just view all records.17:29
tsimmonsProbably shouldn't break convention though...17:29
*** msisk has joined #openstack-meeting-alt17:30
*** carnac is now known as hub_cap17:30
mugsienot many other projects have true sub resources though17:30
kialltsimmons: yea, I personally think having the duplication (i.e. /records and /zones/../records) is the best choice from a not amazing set of choices.17:30
*** jmcbride has quit IRC17:30
tsimmonsIf /records were admin-only I don't really have a problem with it. As long as zones/id/records/id stays.17:30
kiallmugsie: true, our data is naturally tree structured17:31
kialltsimmons: I could agree with that ..17:31
tsimmonsIt seems a little cleaner to keep every search under one space to me though.17:31
mugsiehow do you do this style of search in nuetron for example? say an admin trying to find all floating IPs17:31
mugsie?17:31
kiallGET /floating_ips?all_tenants=117:31
jmcbride1Surely we are not the only project with this problem, do we have examples from other projects to pull from?17:31
mugsieyou could have /search?resource=blah - and then the rest of the filter17:32
mugsieand make the resource arg mandatory for the time being17:32
mugsieand if we decide to ever have a true search, we can do it wioth breaking things17:32
mugsiewithout*17:32
kialljmcbride1: I've not seen anything similar in other projects, but it's been a while since I looked.17:33
*** pballand has joined #openstack-meeting-alt17:33
*** SushilKM has joined #openstack-meeting-alt17:33
kiallHumm.. So.. I really dislike /search?resource=blah17:34
mugsiewhy?17:34
*** nadya_ has joined #openstack-meeting-alt17:34
mugsieits a filter ;)17:34
tsimmonsI'm more of a fan of /search/resource?name=blah personally.17:35
eankutseSo, in the interest of getting to other agenda items for today, should we think through these option for a while and pick up in IRC?17:35
kiallAnyway - tsimmons's suggestion of making the admin-only, and thus subject to change, is a good one..17:35
mugsieeankutse: good plan17:35
tsimmons^agree17:35
mugsiepeople can dump comments on the wiki?17:35
eankutseyes17:35
rjrjryes17:35
kiallWe can pick almost anything now and get the meat of the implementation done.. Without worrying too much about the what the final URL structure will be17:35
betsygood idea17:35
tsimmonsWe can look over the other projects and see if there's anything similar.17:36
kiallOkay - Anyone with strong opinions, let's leave them on the wiki at the bottom of the BP17:36
kiallAnyone else have other comments on that BP? That was the only real thing that caught my eye17:37
tsimmonsThat's here https://wiki.openstack.org/wiki/Designate/Blueprints/Filtering_API it was hashtag linked earlier.17:37
eankutseKiall: that was a big/important one. Thx all17:37
eankutse:-)17:37
kiallOkay - Moving on so :) Next was from vinod ..17:38
kiall#topic APIs for managing TLDs17:38
*** openstack changes topic to "APIs for managing TLDs (Meeting topic: designate)"17:38
vinodI had some comments/questions on the change and wanted to bring them up17:38
vinodThe TLDs are stored in the central storage.  They are not sent to the backend.17:38
vinodBy default now there are no TLDs.  Should designate be prepopulating the database with some default TLD values.  If so any suggestions on where this should go?17:39
*** obondarev_ has quit IRC17:39
*** jmcbride has joined #openstack-meeting-alt17:39
kiallWell, I guess the choice is between 1) Defaulting to the IANA list, 2) Defaulting empty, and treating that as "anything is allowed", 3) Defaulting empty, and treating that as "nothing is allowed"17:40
*** AlanClark has joined #openstack-meeting-alt17:40
tsimmonsI don't know how extensive the IANA list is, but number 1 seems the best option to me if it doesn't impede anything.17:41
vinodCurrently the behavior is (3)Defaulting empty, and treating that as "nothing is allowed"17:41
kiallI would be fine with either #1 or #2, but wouldn't want to see #3 - The less pain to get things setup, the better17:41
*** IlyaE has joined #openstack-meeting-alt17:41
mugsiei like 117:41
betsytsimmons:agree17:41
kialltsimmons: the disadvantage to using the IANA list is, it changes when new TLDs are launched17:41
kiallWhich is happening a hell of a lot more now that it used it17:41
kiallI'm not sure that's really that big of an issue though, every few months, sync the default list up17:42
mugsietrue17:42
tsimmonsEh, if there was a generally comprehensive list that was default and then could be updated easily with the new list, that wouldn't be too bad right? Basically you just want to get the big ones.17:42
tsimmonsYeah.17:42
*** IlyaE has quit IRC17:43
eankutse1) sounds good to me since it is the "equivalent" of reading from the config file17:43
kiallThe IANA and Mozilla Public Suffix lists probably cover well over 90%17:43
mugsieany issue with licences for them?17:43
mugsieif not, I say we use them..17:43
*** jmcbride1 has quit IRC17:43
jmcbrideWhat if option #2 was targetted for now, with a future blueprint to add the pull from the IANA/mozilla lists and sync with them?17:44
kialljmcbride: yea, we do want to support people who don't care if the TLDs are valid etc.. So, that's probably a pretty good option.17:44
kiallAlso - designate-manage could have a command added to download the lists and sync17:45
kiallmugsie: re licences, 99.9% sure they are both fine to use17:45
tsimmonsa designate-manage command would be snazzy.17:45
kiallWe already include them as *.sample today, and I checked that last time17:45
*** glucas has joined #openstack-meeting-alt17:46
vinodkiall: With this change I am removing the lists17:46
*** amcrn has joined #openstack-meeting-alt17:46
kiallvinod: yea, I meant I had checked the licences before when we first included the lists :)17:46
*** harlowja_away is now known as harlowja17:46
ekarlsoello :p17:47
kiallSo - Anyone think there's a better option than #2? Default empty, accept anything17:47
ekarlsoran late :)17:47
vinodThat looks like a good option - with the current bp I will make option (2) as the default17:47
mugsiecool17:47
kiallgreat :) vinod, did you have anything else on that BP to discuss?17:48
*** seanGossard has joined #openstack-meeting-alt17:48
abramley:q17:48
vinodI will add another bp to get the information in the lists into the api17:48
*** colinmcnamara has joined #openstack-meeting-alt17:48
kiallvinod: okay :) Lets move on so.17:49
kiallNext item was from betsy / vinod ...17:49
kiall#topic Case-sensitivity in Domain Names17:49
*** openstack changes topic to "Case-sensitivity in Domain Names (Meeting topic: designate)"17:49
kiallNot really sure what this one is about :D17:49
vinodAlso to make it clear - if the tld db is empty then the behavior is to allow everything and if there is something in the tld db then start enforcing the rules17:49
mugsievinod: yup17:49
vinodOn the topic of case sensitivity17:49
vinodWe have a vagrant implementation where we see that we can create domains with different cases - e.g. hp.com and HP.com can both be created17:50
vinods/implementation/installation17:50
*** matty_dubs|lunch is now known as matty_dubs17:50
kiallThat shouldn't happen - ever.17:50
vinodOn another installation we do not see this behavior17:50
betsyThat's what we were thinking17:50
betsyDid something change recently?17:51
kiallI would imagine the DB is set as case sensitive?17:51
*** nati_ueno has joined #openstack-meeting-alt17:51
eankutsethe storage, huh?17:51
kiallOr the unique index is somehow missing17:52
kiallI mean, a mysql table can be configured to either case sensitive, or in-sensitive. I don't believe we specify a default while creating the tables17:52
vinodIs the db set as case sensitive in one of the config files?17:52
betsyAh. That must be it.17:52
*** esp has joined #openstack-meeting-alt17:53
eankutsesince there is no designate specific logic for this17:53
betsyWe're using sqlite with the vagrant set up17:53
eankutseI think you are right on17:53
kiallHumm17:53
eankutsemust be the db17:53
*** robertmyers has joined #openstack-meeting-alt17:53
kiallMigration #21 might be the cause17:53
*** _ruhe is now known as ruhe17:53
kiall#action Check into migration #21 and case sensitivity17:54
kiallRunning out of time, So I'll check into that after the meet17:54
eankutsewhat does migration #21 do?17:54
*** jimbobhickville has joined #openstack-meeting-alt17:54
kiallSet's the character set to UTF8, rather than accepting the database default.17:54
*** DennyZhang has joined #openstack-meeting-alt17:54
eankutsethx17:54
kiallBut - We might have needed to use utf8_general_ci there instead17:54
kiallOkay - 5 mins to go.17:55
kiall#topic Open Discussion17:55
*** openstack changes topic to "Open Discussion (Meeting topic: designate)"17:55
kiallSo - I have an off-agenda item..17:55
kiallI'd like to propose mugsie for "core", he's pretty consistently doing good reviews etc.. so I reckon it's a good fit17:56
kiallFollowing openstack tradition, that gets put to a vote.17:56
*** esp has left #openstack-meeting-alt17:56
kiallThoughts?17:56
*** gokrokve has joined #openstack-meeting-alt17:56
jmcbrideHow many core members should we target?17:56
jmcbrideAnd who is a core member today?17:57
betsyI second mugsie as a core member17:57
kiallI don't think there's a "good" number,17:57
artomDoes there have to be a target? As long as the person knows the project, does good reviews and is willing to put in the time/energy...17:57
kialltoday it's myself, betsy, and from back in the day, ekarlso17:57
*** krtaylor has quit IRC17:58
eankutseI second mugsie17:58
tsimmons+1 for mugsie17:58
artomThe more core the merrier, means patches get in faster ;)17:58
jmcbrideartom: agreed.17:58
jmcbrideWe definitely need more than 2…17:59
vinod+1 for mugsie17:59
kiallOkay - Anyone disagree?17:59
jmcbride+1 for mugsie17:59
ekarlsoI think we need someone *outside* of HP son as well :p17:59
kiallWith about 30 seconds to go, and nobody voting against ..17:59
ekarlso+1 mugsie17:59
rjrjragreed.  +117:59
kiallekarlso: betsy is outside HP17:59
ekarlsokiall: she's core ?17:59
ekarlsocoolio17:59
ekarlsothen I'm silenced :)17:59
kialland, anyone is free to propose anyone..17:59
kiallOkay then - Congrats mugsie18:00
tsimmonsWoot18:00
jmcbridewoot!18:00
*** jcru has joined #openstack-meeting-alt18:00
mugsie\o/18:00
kialland - we're eating into trove's time now :)18:00
tsimmons#link http://robhirschfeld.com/2014/01/06/openstack-defcore/ may be of general interest. Whenever you have a chance.18:00
*** esp has joined #openstack-meeting-alt18:00
jmcbrideOne quick topic note: Designate Meetup - We need a communication plan for including the community (e.g. setup a "summit" page with details, sign-up info, remote participation info). I can do that18:00
mugsiejmcbride: cool, there is a meeting section in the blueprints page18:01
kialljmcbride: Let's move to #openstack-dns before we take all of troves time :)18:01
kiall#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Wed Jan  8 18:01:28 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
hub_cap:)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-01-08-17.00.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-01-08-17.00.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-01-08-17.00.log.html18:01
hub_capthx kiall18:01
hub_cap#startmeeting trove18:01
*** arnaud__ has joined #openstack-meeting-alt18:01
*** msisk has left #openstack-meeting-alt18:01
openstackMeeting started Wed Jan  8 18:01:39 2014 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
esmuteo/18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** arnaud___ has joined #openstack-meeting-alt18:01
*** openstack changes topic to " (Meeting topic: trove)"18:01
openstackThe meeting name has been set to 'trove'18:01
denis_makogono/18:01
kiallhub_cap would probably beat me if I didn't end it soon ;)18:01
amcrno/18:01
pdmarso/18:01
*** SlickNik has joined #openstack-meeting-alt18:01
*** mugsie has left #openstack-meeting-alt18:01
espo/18:01
*** artom has left #openstack-meeting-alt18:02
*** tsimmons has left #openstack-meeting-alt18:02
kevinconwayo18:02
hub_capkiall: not me!18:02
robertmyerso/18:02
SlickNikhey18:02
*** imsplitbit has joined #openstack-meeting-alt18:02
amytrono/18:02
*** vinod has left #openstack-meeting-alt18:02
hub_capfirst meeting of the year!!18:02
imsplitbito/18:02
imsplitbito\18:02
imsplitbito/18:02
datsun180bo18:02
denis_makogono|18:02
esmuteHappy 2014 folks!18:02
hub_cap#topic https://wiki.openstack.org/wiki/Meetings/TroveMeeting18:02
*** openstack changes topic to "https://wiki.openstack.org/wiki/Meetings/TroveMeeting (Meeting topic: trove)"18:02
denis_makogonthnks18:02
*** kanzaros has joined #openstack-meeting-alt18:02
datsun180bthat is yet to be evaluated18:02
cp16net\o18:03
imsplitbityay the world survived another year!18:03
hub_caplol datsun180b18:03
vipulo/18:03
*** bcrochet has quit IRC18:03
hub_capok so this isint on the list but id like to welcome amcrn to core!18:03
imsplitbityeah welcome18:03
cp16netwoot18:03
datsun180bmore like amcoren18:03
hub_caphis first task, update russellb 's scripts to show hes in core!18:03
esmutecongrats amcrn!18:03
amcrnthanks :)18:03
jimbobhickvillelooking forward to all the −2s… I mean +2s18:03
imsplitbitdatsun180b: that was hub_cap quality18:03
hub_capdatsun180b: geesus thats my caliber of jokes18:03
datsun180bwell someone's got to do your job18:04
hub_capdatsun180b: good call, 2x bad jokes are way better than 1x18:04
hub_capok so lets get to the real first topic18:04
SlickNikheh, welcome onboard amcrn.18:04
*** mat-lowery_ has joined #openstack-meeting-alt18:04
*** dl has joined #openstack-meeting-alt18:05
hub_cap#topic introduce parelastic18:05
*** openstack changes topic to "introduce parelastic (Meeting topic: trove)"18:05
hub_cap#link www.parelastic.com18:05
*** dl is now known as Guest2199518:05
*** bcrochet has joined #openstack-meeting-alt18:05
cp16netanyone from parelastic here?18:05
hub_capparelastic is a group w/ some mysql, linux, coding rockstars that is coming in to help us wiht, well ill let them talk about it. But im happy to have them joining the fold!!18:05
*** pballand has quit IRC18:05
amrithyes, several of s18:05
doug_shelley66hi18:05
parstac_petehi there18:06
hub_capwelcome doug_shelley66 amrith and co18:06
SlickNikhey guys!18:06
seanGossardyo18:06
esmuteNICE18:06
vgnbkr_1Hi.18:06
cp16netnice welcome :)18:06
vipulcool! more trovesters18:06
amcrnhola18:06
glucaso/18:06
laurelmhello18:06
kanzaroshowdy18:06
jimbobhickvillewow, lots of 'em.  welcome18:06
hub_capwe just doubled in size!! this is great stuff!!18:06
imsplitbitok wait! are we trovians? trovesters?18:06
denis_makogonwelcome18:06
doug_shelley66We are looking forward to getting involved in the Trove community and working with all of you18:06
imsplitbitcan we have a one hour meeting to decide this?18:06
imsplitbit:)18:06
vipulimsplitbit: +118:06
vipuli'd like clarity as well18:06
jimbobhickvilletrovenites18:06
imsplitbityeah see18:06
*** colinmcnamara has quit IRC18:06
SlickNikimsplitbit: take your pick18:06
imsplitbitwe need clarity on this18:07
denis_makogontrovers18:07
hub_capive been chatting w/ doug_shelley66 and amrith for a bit about comign aboard18:07
hub_caplol you guys if u read this channel it loks like u want clarity about parelastic18:07
hub_capnot the choice betwen trovester and trovian or whatever18:07
imsplitbitSlickNik: this is python, there should be one and only one way18:07
jimbobhickvilletrovellian18:07
imsplitbitha!18:07
imsplitbitsorry about that18:07
*** NehaV has joined #openstack-meeting-alt18:07
* imsplitbit is totally at fault for that18:07
hub_capso lets skip the trovester stuff and let doug_shelley66 intro the team :)18:08
imsplitbitI gues18:08
amrith+1 :)18:08
imsplitbitlol18:08
denis_makogonimsplitbit, let them speak18:08
vipulyea imsplitbit18:08
doug_shelley66hi there - so we have been working on DBaaS for a few years now and are very interested Trove and its direction18:08
doug_shelley66so onto the team18:08
*** safchain has quit IRC18:08
doug_shelley66We are located between Toronto, Ontario and Cambridge MA18:09
*** Barker has joined #openstack-meeting-alt18:09
doug_shelley66I'm the head of development and will be the Internal Dev Lead18:09
esmuteWoo... fellow ONtarian here18:09
*** k-pom has joined #openstack-meeting-alt18:09
doug_shelley66ah, from where?18:09
esmuteOttawa.18:09
esmuteThat's Canada's capital for those who dont know :-)18:10
imsplitbit...18:10
denis_makogonlol18:10
doug_shelley66say hi to Steve for me18:10
doug_shelley66so i know most of the team said HI at the beginning of this but why don't each of just indicate your name and location18:10
esmuteIm Steve. but sure.. will do18:10
hub_capeveryone is steve!18:10
jimbobhickvilleare you a steve or a stew?18:11
*** bcrochet has quit IRC18:11
hub_capso doug_shelley66 what do you guys intend on working on?18:11
*** ViswaV has joined #openstack-meeting-alt18:11
denis_makogondoug_shelley66, so, what the difference between Amazon RDS and parelastic ? What kind of features do you have ?18:11
doug_shelley66let me answer hub_cap first18:11
doug_shelley66after some discussions with hub_cap we are interested in getting involved with the Clustering and Replication projects18:12
imsplitbitsweet, we need the help18:12
*** bcrochet has joined #openstack-meeting-alt18:13
*** cweid has joined #openstack-meeting-alt18:13
imsplitbitso far it's me18:13
cweido/18:13
imsplitbitso I'm happy18:13
denis_makogonimsplitbit, and me (from heat side)18:13
doug_shelley66at it's core ParElastic is a parallel database18:13
hub_caphorray for working on clustering and replication. there is a lot of owrk that will go into that18:13
doug_shelley66which can actually cause multiple RDS instances to look like one18:13
vipulis it more of a front end? or a different engine underneath?18:14
doug_shelley66we didn't implement a storage engine - it is using stock mysql18:14
doug_shelley66(or RDS)18:14
denis_makogondoug_shelley66, so no NoSQL ?18:15
robertmyersdouble negative18:15
*** SushilKM has quit IRC18:15
doug_shelley66no not NoSQL18:15
doug_shelley66:)18:15
doug_shelley66we are SQL at the front end18:16
*** IlyaE has joined #openstack-meeting-alt18:16
vipuldoug_shelley66: do you run parelastic in a separate instance than the mysql ?18:16
*** Ankur has joined #openstack-meeting-alt18:16
doug_shelley66that is one possible configuration18:16
*** bcrochet has quit IRC18:16
amcrndoug_shelley66: i've read the basic whitepaper, is there another one that details how the data distribution works? the introductory whitepaper states that administrative rules handle it, but i'd be interested in knowing more.18:17
*** ViswaV has quit IRC18:17
*** sarob has joined #openstack-meeting-alt18:17
*** sarob has quit IRC18:17
hub_capyes it seems like trove will have some of that logic as well amcrn  :)18:17
*** jasonb365 has joined #openstack-meeting-alt18:18
*** sarob has joined #openstack-meeting-alt18:18
amcrn(by "basic whitepaper", i'm referring to https://s3.amazonaws.com/ParElastic/ParElastic_White+Paper.pdf, so there's no confusion)18:18
*** sarob has quit IRC18:18
*** bcrochet has joined #openstack-meeting-alt18:18
*** ViswaV has joined #openstack-meeting-alt18:19
doug_shelley66amrcn - maybe we could setup a separate discussion - i don't want to side track this meeting too much?18:19
hub_cap++18:19
denis_makogon++18:19
amcrnno problem18:19
SlickNikThat sounds like a good idea.18:19
hub_capi think thats a fair introduction18:19
*** jmontemayor has joined #openstack-meeting-alt18:19
hub_capparelastic team, feel free to start chatting in #openstack-trove with us w/ any questions18:19
*** jmcbride has quit IRC18:19
hub_capwelcome!18:20
*** sarob has joined #openstack-meeting-alt18:20
doug_shelley66Thanks - that would be great - as we are spinning up we certainly have questions18:20
seanGossardgood to be here, thanks!18:20
hub_capwoo!18:20
hub_capok movin on18:20
hub_cap#topic mid cycle meetup18:20
*** openstack changes topic to "mid cycle meetup (Meeting topic: trove)"18:21
hub_cap#link https://wiki.openstack.org/wiki/Trove/IcehouseCycleMeetup18:21
amytrondoug_shelley66:  are you and your team going to the meetup?18:21
datsun180bugh, i'm not going downtown18:21
datsun180bit's so far away18:21
denis_makogonlol18:21
hub_capim excited about this one. other teams are doing it and i think itll be pretty nice to get together18:21
hub_caplol datsun180b :)18:21
imsplitbithub_cap: +118:21
robertmyersdatsun180b: nice18:21
*** SushilKM has joined #openstack-meeting-alt18:21
*** michayu has joined #openstack-meeting-alt18:22
denis_makogonsorry, but our team is not able to come due to several reasons18:22
doug_shelley66amytron - yes we will be sending a contingent18:22
*** mpolanco has joined #openstack-meeting-alt18:22
imsplitbitawe man18:22
hub_cap#link https://etherpad.openstack.org/p/TroveMidCycleMeetup18:22
hub_capdenis_makogon: :(18:22
hub_capdenis_makogon: we will find a way to get you involved, maybe a google hangout?18:23
hub_capill work w/ you denis_makogon to make sure u can be there in some form, we might have to experiment a bit18:23
*** michayu is now known as michael-yu18:23
denis_makogonhub_cap, thanks18:23
* datsun180b googles "diy telepresence robot"18:23
SlickNikDefinitely will figure out a way to involve folks who won't be able to travel.18:23
hub_capplz propose sessions to the etherpad18:24
cp16netlol18:24
imsplitbithttp://www.hizook.com/files/users/3/Texai_Robot_BigBangTheory_6.jpg18:24
*** ViswaV has quit IRC18:24
*** yogesh has joined #openstack-meeting-alt18:24
hub_caphah ok that means its time to move on :)18:25
imsplitbityep18:25
hub_capalso, if u know u are going, and havent signed up yet, plz do now18:25
hub_capor soon18:25
*** sarob has quit IRC18:25
hub_capit helps w/ our headcount for things like lunch, u do want lunch, right?18:26
hub_caphttps://troveicehousemeetup.eventbrite.com/18:26
jimbobhickvillelunch++18:26
hub_cap#link https://troveicehousemeetup.eventbrite.com/18:26
cweidI expect 2 lunches18:26
*** sarob has joined #openstack-meeting-alt18:26
kevinconwayhub_cap: i'm sold18:26
hub_capcweid: in 3 days? deal!18:26
vipulwill special meal requests be fulfilled18:26
SlickNiklol18:26
hub_capvipul: yup, all meals will contain chicken18:26
vipulor do i have to start eating meat now18:26
hub_capvipul: :)18:26
jimbobhickvilleI request caviar-encrusted puffer fish for my lunch18:26
hub_capi know we have special requests to fufill, we will have glueten free, vegetarian, i assume (right amytron ??)18:27
datsun180bwhat kind of food can't you get from a truck in downtown austin in the middle of the week18:27
esmutewill Rax be hosting a party too?18:27
amrithYes please. I'm flexitarian (I'll eat steak if you don't have vegan options).18:27
vipulesmute: ++18:28
hub_capNICE18:28
vipulthose Rax parties are awesome18:28
imsplitbitI'm with you vipul I need a kosher gluten free lactose free vegetarian meal18:28
amytronyes, i think we should provide vegetarian options. we can poll the participants after everyone registers18:28
cweidWe also will serve plastic pellets.18:28
hub_capamytron: is our socialist expert, she will be making plans on drinkups18:28
*** ViswaV has joined #openstack-meeting-alt18:28
amytronwow, well. this is awkward18:29
amytron:)18:29
hub_capHAAHAHAHAH18:29
hub_capwe will likely be doing some drinkups in some form or fashion :)18:29
cweid- likely18:29
imsplitbitsocialist or not18:29
jimbobhickvillewill there be special drink requests?18:29
doug_shelley66ok, i'm in18:29
hub_capjimbobhickville: as long as the special request is a beer, yes18:30
cweidWhisky/18:30
datsun180bcan my special request be that you honor nobody else's special request18:30
denis_makogoncweid, Irish bomb18:30
*** sarob has quit IRC18:31
cweidcweid: This sounds good.18:31
hub_capheh nice :)18:31
*** sarob has joined #openstack-meeting-alt18:31
cweidoops18:31
hub_capcweid: cweid you pulled a hub_cap18:31
cweiddenis_makogon: this sounds good18:31
hub_capok movin on!18:31
cweidhub_cap: hub_cap we are twins.18:31
hub_capto the less fun topic18:31
hub_capcweid: dibs on davito18:32
imsplitbitoh jees here it comes18:32
cweidUsers...18:32
*** jrodom has joined #openstack-meeting-alt18:32
hub_cap#topic too many open reviews18:32
*** openstack changes topic to "too many open reviews (Meeting topic: trove)"18:32
hub_caplol no not users18:32
hub_capcp16net: plz link those18:32
cp16net#link http://www.russellbryant.net/openstack-stats/trove-openreviews.html18:32
cp16net#link https://review.openstack.org/#/mine/important/18:32
*** sarob has quit IRC18:32
SlickNik I'm going to have a chunk of time to work through a bunch of them today.18:33
hub_capso we have a lot of reviews, this is partually due to the end of year, partially due to the core team size and partially due to the core team *participation*18:33
SlickNikAnd by going to have, I mean I've tried to put aside. :)18:33
vipuli accept some of the blame... haven't been active as i'd like to be on those18:33
*** sarob has joined #openstack-meeting-alt18:34
cp16netsorry to be a party pooper but just wanted to bring it up since i've seen so many reviews ~7018:34
hub_capyes cp16net18:35
vipulcp16net: it's a fair point.. we havn't been doing our job18:35
amcrnif some eyes could hit the configuration-groups review and the datastore-manager to versions review in particular, that'd be great18:35
hub_capyes we really need to focus. im going to be putting my support behind all the datastore sint he next few days18:35
cp16netok i'll step off the soap box18:35
*** sarob has quit IRC18:35
*** eankutse has quit IRC18:36
esmutenot just core reviews. Non-core can also provide valuable reviews which can speed things up (not saying that I do :-))18:36
*** sarob has joined #openstack-meeting-alt18:36
hub_capwe need to merge the _large_ patches too, yes amcrn config groups and datastores18:36
SlickNikamcrn: will take a look.18:36
cp16netesmute: i agree18:36
*** Ankur has quit IRC18:36
denis_makogonesmute, true stroy18:36
denis_makogon*story18:36
hub_capok so, we totally know this is an issue, and i will be harping on it18:37
hub_capas a community, please, look at the stats18:37
hub_capif you see core members not doing their jobs, call them out :)18:37
denis_makogonstats != reality18:37
hub_capit will help keep us in check18:37
* imsplitbit ducks18:38
jimbobhickvillestats measure reality?18:38
hub_capdenis_makogon: not sur ewhat u mean18:38
hub_capthe stats reflect the work each person does on reviewing18:38
hub_capif you see a core member w/o a lot of reviews talk to them18:38
hub_capcuz they arent doing their job18:38
hub_capso18:38
hub_capstats = reality18:38
denis_makogonhub_cap, if you mean review/contribution stats18:38
*** derekh has quit IRC18:38
cweidreturn true18:38
hub_capi mean the reviews yes18:38
imsplitbitthat would be stats == reality18:39
hub_capimsplitbit: shaddup18:39
*** rnirmal has joined #openstack-meeting-alt18:39
kevinconwayimsplitbit: unless javascript then stats === reality18:39
cp16net≠≠18:39
denis_makogonwe haven't seen grapex for awhile18:39
hub_capdenis_makogon: grapex is on vacation :)18:39
denis_makogonhub_cap, makes sense18:39
cp16netyup18:40
*** sarob has quit IRC18:40
hub_capill be screaming at core daily18:40
datsun180bresult = new ComparisonFactory.create(ComparisonFactory.equals)().compare(stats, reality);18:40
*** sarob has joined #openstack-meeting-alt18:40
*** Ankur has joined #openstack-meeting-alt18:40
hub_caplol18:40
hub_capok so i welcome ideas for makign this better18:41
hub_cap#topic tempest integration18:42
*** openstack changes topic to "tempest integration (Meeting topic: trove)"18:42
denis_makogoni like the idea of putting link to Russels site (open reviews section) in Open Discussion18:42
denis_makogonit would be some sort of reminder18:42
*** krtaylor has joined #openstack-meeting-alt18:43
SlickNikOkay, so I've submitted patches to devstack-gate, and openstack-infra config to enable us to run tempest on devstack-gate.18:43
hub_capif u want to re-add it weekly denis_makogon im fine w/ that (i might forget)18:43
denis_makogonSlickNik, could you share the links ?18:43
SlickNikYeah, hang on.18:44
denis_makogonk18:44
hub_cap#link https://review.openstack.org/#/c/65065/18:44
hub_cap#link https://review.openstack.org/#/c/64913/18:44
hub_cap#link https://review.openstack.org/#/c/65040/18:44
SlickNik#link https://review.openstack.org/#/c/65065/18:44
hub_cap:)18:44
hub_capBEEEEEET U18:44
SlickNikthanks hub_cap18:44
hub_capnpnp18:44
*** sarob has quit IRC18:45
SlickNikAlso, I'm still working on cleaning up the guestagent elements and the job to build the image.18:45
SlickNikBut this will allow us to get started writing Tempest tests that test the API and parts of the taskmanager, at least.18:45
denis_makogonso, do we plan to deprecate -integration ?18:46
SlickNikUntil that piece is in place.18:46
SlickNikdenis_makogon: eventually the integration tests parts of it, at least.18:46
SlickNikI imagine it'll stick around until we have enough coverage in tempest.18:47
denis_makogoni think we need pure plan for tests coverage18:47
denis_makogonand we could split tasks between guys who works w/ tempest18:48
SlickNikI'd love help with writing tests for tempest.18:49
SlickNikI know some of you already started looking at it.18:49
SlickNikdenis_makogon: can you explain what you mean by "pure plan"?18:49
denis_makogoni know that my teammate is working on list- operation18:49
denis_makogonwhen we would have merged infra and devstack patches we would need to cover ReST API part18:50
denis_makogonso we have not so many tests which involves rest18:51
denis_makogonwe could give those tests to SnowDust, as variant18:51
kevinconwaydenis_makogon: are you talking about some kind of acceptance test that only uses api?18:51
denis_makogoni mean that we need to split whole tests into separate independent groups and share them between everyone who is interested in it18:52
hub_caplets work on delegatging outisde this meeting18:52
denis_makogonk18:52
hub_capand give some time for open discussion18:52
SlickNikPerhaps what's needed is to meet up regarding it and to talk about who's working on which pieces.18:52
hub_cap++18:53
SlickNikI can look into setting some time up for that.18:53
hub_cap#topic open discussion18:53
*** openstack changes topic to "open discussion (Meeting topic: trove)"18:53
hub_capGO GOGOGOGO18:53
datsun180b#topic airline food: what's the deal18:53
SlickNik#action SlickNik to organize some time to meet up and talk about who's working on what for the tempest tests.18:53
hub_capdatsun180b: depends on the airline, when i fly i get a great eggs benedict w/ bacon instead and a spicy hollindaise18:54
hub_capoh wait thats airport food18:55
hub_capnot airline food18:55
*** dprince_ has joined #openstack-meeting-alt18:55
* SlickNik want's to know what airline hub_cap flies18:55
hub_capeheh i just meant the air_port_18:55
vipulimsplitbit: Do you have enough to push up reviews for the replication pieces you've been working on?18:55
SlickNikah, makes more sense.18:55
*** dprince has quit IRC18:55
vipulairport ramen18:55
*** Ankur has quit IRC18:55
imsplitbitvipul not yet but I have 40% on metadata I'll be submitting soon18:55
esphub_cap: that sounds delicious18:55
imsplitbitthe replication will be fast follow18:55
imsplitbitjust api18:55
imsplitbitno impl18:55
hub_capAIRPORT RAMEN vipul18:55
vipulimsplitbit: Ok - we would like to help out with some of that, so whenever you have it we can look at it18:56
imsplitbitno problem18:56
hub_capif nothign else, push it to a fork :)18:56
imsplitbitparelastic seems to want to help with that too18:56
imsplitbitso we should be able to knock it out18:56
imsplitbitquick18:56
denis_makogonSlickNik, could you write ML about sub-meeting (topic - tempest and trove) ?18:57
SlickNikdenis_makogon: will do.18:57
doug_shelley66imsplitbit - maybe we can connect up and see what we can help with18:57
imsplitbitdoug_shelley66: definitely18:58
imsplitbitI would also like to host a meeting at the meetup in austin18:58
imsplitbitvery little presentation but lots of collaboration18:58
hub_cap++18:59
hub_cap:)18:59
denis_makogonlets meet in Europe18:59
denis_makogonsuppose, Paris ?18:59
hub_capdenis_makogon: i agree!!!18:59
denis_makogonMadrid18:59
cp16net+118:59
kevinconwaydenis_makogon: paris, texas18:59
robertmyers+118:59
cp16net:-P18:59
denis_makogonMoscow18:59
pdmarsdenis_makogon: yes18:59
kevinconwaydenis_makogon: or odessa, texas18:59
denis_makogonLondon18:59
doug_shelley66how about Sochi in a few weeks18:59
hub_capparis is the next one (after atlanta)18:59
denis_makogonat Baker Street 221B18:59
hub_caplol18:59
hub_capits 1119:00
imsplitbitgood talk guys19:00
hub_cap#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Wed Jan  8 19:00:05 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-01-08-18.01.html19:00
imsplitbitI'm out19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-01-08-18.01.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-01-08-18.01.log.html19:00
*** imsplitbit has left #openstack-meeting-alt19:00
*** venkatesh has joined #openstack-meeting-alt19:00
*** jimbobhickville has left #openstack-meeting-alt19:00
*** esp has left #openstack-meeting-alt19:00
*** Duane has joined #openstack-meeting-alt19:01
SlickNikThanks all19:01
cweidbyeeeee happy new year19:01
*** robertmyers has left #openstack-meeting-alt19:01
*** ankur-bansal has joined #openstack-meeting-alt19:03
*** markmcclain has joined #openstack-meeting-alt19:03
*** pcm_ has joined #openstack-meeting-alt19:04
*** Guest21995 has quit IRC19:05
*** joel_c has left #openstack-meeting-alt19:07
*** ankur-bansal has quit IRC19:07
*** songole has joined #openstack-meeting-alt19:09
*** songole has left #openstack-meeting-alt19:10
*** esker has quit IRC19:12
*** jrodom has quit IRC19:13
*** pcm_ has left #openstack-meeting-alt19:14
*** yidclare has joined #openstack-meeting-alt19:14
*** SlickNik has left #openstack-meeting-alt19:15
*** eharney has quit IRC19:15
*** datsun180b has quit IRC19:16
*** datsun180b has joined #openstack-meeting-alt19:17
*** ruhe is now known as _ruhe19:21
*** yidclare has left #openstack-meeting-alt19:23
*** Duane has quit IRC19:25
*** tedross has joined #openstack-meeting-alt19:25
*** Duane has joined #openstack-meeting-alt19:25
*** johnthetubaguy has quit IRC19:26
*** Duane has quit IRC19:30
*** datsun180b has left #openstack-meeting-alt19:30
*** tedross has left #openstack-meeting-alt19:31
*** Duane has joined #openstack-meeting-alt19:32
*** rossella_s has quit IRC19:33
*** nadya_ has quit IRC19:34
*** DennyZhang has quit IRC19:34
*** sarob has joined #openstack-meeting-alt19:34
*** rsblendido has quit IRC19:35
*** jmcbride has joined #openstack-meeting-alt19:36
*** Duane has quit IRC19:37
*** jmcbride has left #openstack-meeting-alt19:37
*** Duane has joined #openstack-meeting-alt19:38
*** Duane_ has joined #openstack-meeting-alt19:42
*** Duane has quit IRC19:43
*** Duane has joined #openstack-meeting-alt19:46
*** Duane_ has quit IRC19:47
*** venkatesh has quit IRC19:49
*** eankutse has joined #openstack-meeting-alt19:50
*** eharney has joined #openstack-meeting-alt19:52
*** baoli has quit IRC19:53
*** sarob has quit IRC19:53
*** sarob has joined #openstack-meeting-alt19:54
*** mpolanco has quit IRC19:56
*** sarob has quit IRC19:57
*** Duane has quit IRC19:58
*** doug_shelley66 has quit IRC19:58
*** lblanchard has quit IRC20:01
*** rpothier has joined #openstack-meeting-alt20:01
*** vipul is now known as vipul-away20:02
*** vipul-away is now known as vipul20:02
*** Duane_ has joined #openstack-meeting-alt20:02
*** rpothier has left #openstack-meeting-alt20:02
*** lblanchard has joined #openstack-meeting-alt20:03
*** safchain has joined #openstack-meeting-alt20:13
*** safchain has quit IRC20:13
*** _ruhe is now known as ruhe20:14
*** vipul is now known as vipul-away20:17
*** mat-lowery_ has quit IRC20:25
*** mat-lowery_ has joined #openstack-meeting-alt20:26
*** IlyaE has quit IRC20:34
*** SushilKM has quit IRC20:36
*** vipul-away is now known as vipul20:36
*** jdob has quit IRC20:39
*** sarob has joined #openstack-meeting-alt20:41
*** jdob has joined #openstack-meeting-alt20:42
*** ViswaV has quit IRC20:43
*** mat-lowery_ is now known as mat-lowery20:44
*** IlyaE has joined #openstack-meeting-alt20:47
*** ViswaV has joined #openstack-meeting-alt20:53
*** ViswaV has quit IRC20:54
*** betsy has quit IRC20:54
*** ViswaV has joined #openstack-meeting-alt20:55
*** ViswaV has quit IRC20:55
*** ViswaV has joined #openstack-meeting-alt20:55
*** ViswaV has quit IRC20:56
*** ViswaVutharkar has joined #openstack-meeting-alt20:56
*** sarob has quit IRC20:59
*** arnaud__ has quit IRC20:59
*** arnaud___ has quit IRC20:59
*** sarob has joined #openstack-meeting-alt21:00
*** lblanchard has quit IRC21:00
*** tomblank has quit IRC21:01
*** sarob_ has joined #openstack-meeting-alt21:01
*** tomblank has joined #openstack-meeting-alt21:01
*** lblanchard has joined #openstack-meeting-alt21:01
*** sarob has quit IRC21:04
*** ViswaVutharkar has quit IRC21:04
*** ViswaV has joined #openstack-meeting-alt21:05
*** sarob_ has quit IRC21:07
*** sarob has joined #openstack-meeting-alt21:07
*** krtaylor has quit IRC21:11
*** sarob has quit IRC21:12
*** michael-yu has left #openstack-meeting-alt21:17
*** amrith has quit IRC21:19
*** balajiiyer has quit IRC21:20
*** jjmb has joined #openstack-meeting-alt21:23
*** Duane has joined #openstack-meeting-alt21:24
*** jjmb1 has joined #openstack-meeting-alt21:25
*** Duane_ has quit IRC21:27
*** david-lyle has quit IRC21:27
*** jjmb has quit IRC21:28
*** david-lyle has joined #openstack-meeting-alt21:28
*** bcrochet is now known as bcrochet|bbl21:29
*** eankutse has quit IRC21:31
*** eankutse has joined #openstack-meeting-alt21:31
*** SergeyLukjanov_ has joined #openstack-meeting-alt21:34
*** SergeyLukjanov has quit IRC21:35
*** dprince_ has quit IRC21:40
*** jdob has quit IRC21:42
*** jdob has joined #openstack-meeting-alt21:43
*** pnavarro has quit IRC21:44
*** AlanClark has quit IRC21:44
*** jjmb1 has quit IRC21:52
*** arnaud__ has joined #openstack-meeting-alt21:57
*** IlyaE has quit IRC21:57
*** arnaud___ has joined #openstack-meeting-alt21:57
*** balajiiyer has joined #openstack-meeting-alt21:57
*** balajiiyer has quit IRC21:58
*** balajiiyer has joined #openstack-meeting-alt21:58
*** IlyaE has joined #openstack-meeting-alt22:03
*** arnaud___ has quit IRC22:04
*** arnaud__ has quit IRC22:04
*** matty_dubs is now known as matty_dubs|gone22:05
*** lblanchard has quit IRC22:06
*** tomblank has quit IRC22:06
*** sarob has joined #openstack-meeting-alt22:08
*** jdob has quit IRC22:08
*** arnaud__ has joined #openstack-meeting-alt22:08
*** SergeyLukjanov_ has quit IRC22:08
*** arnaud___ has joined #openstack-meeting-alt22:08
*** SergeyLukjanov has joined #openstack-meeting-alt22:10
*** doug_shelley66 has joined #openstack-meeting-alt22:15
*** krtaylor has joined #openstack-meeting-alt22:16
*** rwsu has quit IRC22:22
*** jecarey has quit IRC22:23
*** pdmars has quit IRC22:23
*** eankutse has quit IRC22:24
*** alazarev has joined #openstack-meeting-alt22:26
*** sarob has quit IRC22:26
*** rwsu has joined #openstack-meeting-alt22:30
*** flaper87 is now known as flaper87|afk22:32
*** sarob has joined #openstack-meeting-alt22:33
*** sarob has quit IRC22:36
*** markwash has quit IRC22:36
*** sarob has joined #openstack-meeting-alt22:37
*** sarob_ has joined #openstack-meeting-alt22:38
*** sarob_ has quit IRC22:38
*** alazarev has quit IRC22:38
*** markwash has joined #openstack-meeting-alt22:38
*** sarob_ has joined #openstack-meeting-alt22:39
*** IlyaE has quit IRC22:40
*** sarob has quit IRC22:41
*** amrith has joined #openstack-meeting-alt22:43
*** amytron has quit IRC22:45
*** sarob_ has quit IRC22:46
*** amytron has joined #openstack-meeting-alt22:47
*** Duane has quit IRC22:47
*** SergeyLukjanov_ has joined #openstack-meeting-alt22:47
*** SergeyLukjanov_ has quit IRC22:47
*** SergeyLukjanov has quit IRC22:48
*** SergeyLukjanov_ has joined #openstack-meeting-alt22:48
*** Duane has joined #openstack-meeting-alt22:48
*** SergeyLukjanov_ has quit IRC22:48
*** csaba|afk is now known as csaba22:50
*** Duane has quit IRC22:52
*** sarob has joined #openstack-meeting-alt22:55
*** jcru has quit IRC22:55
*** jecarey has joined #openstack-meeting-alt22:56
*** rnirmal has quit IRC22:58
*** NehaV has quit IRC23:01
*** pdmars has joined #openstack-meeting-alt23:02
*** sarob has quit IRC23:02
*** sarob has joined #openstack-meeting-alt23:03
*** sarob_ has joined #openstack-meeting-alt23:04
*** kevinconway has quit IRC23:06
*** NehaV has joined #openstack-meeting-alt23:06
*** NehaV has quit IRC23:07
*** sarob has quit IRC23:07
*** eharney has quit IRC23:10
*** Barker has quit IRC23:11
*** amrith has quit IRC23:15
*** csaba is now known as csaba|afk23:21
*** sarob_ has quit IRC23:21
*** sarob has joined #openstack-meeting-alt23:22
*** BrianB_ has quit IRC23:22
*** yogesh has quit IRC23:22
*** yogesh has joined #openstack-meeting-alt23:23
*** Duane has joined #openstack-meeting-alt23:24
*** sarob has quit IRC23:26
*** Duane has quit IRC23:27
*** yogesh has quit IRC23:27
*** ViswaV has quit IRC23:34
*** kebray_ has joined #openstack-meeting-alt23:36
*** ruhe is now known as _ruhe23:41
*** balajiiyer1 has joined #openstack-meeting-alt23:41
*** mpolanco has joined #openstack-meeting-alt23:42
*** balajiiyer has quit IRC23:42
*** sarob has joined #openstack-meeting-alt23:44
*** jasonb365 has quit IRC23:44
*** gokrokve has quit IRC23:45
*** gokrokve has joined #openstack-meeting-alt23:46
*** bill_az has quit IRC23:46
*** seanGossard has quit IRC23:46
*** mpolanco has quit IRC23:47
*** ashaikh has quit IRC23:50
*** gokrokve has quit IRC23:50
*** sacharya has quit IRC23:53
*** balajiiyer1 has quit IRC23:54
*** mat-lowery has quit IRC23:57
*** balajiiyer1 has joined #openstack-meeting-alt23:59

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