Wednesday, 2014-01-22

*** lblanchard has joined #openstack-meeting-alt00:02
*** flwang has quit IRC00:02
*** pdmars has quit IRC00:02
*** vipul-away is now known as vipul00:02
*** gokrokve has quit IRC00:04
*** gokrokve has joined #openstack-meeting-alt00:04
*** sarob has joined #openstack-meeting-alt00:07
*** michael-yu has quit IRC00:09
*** gokrokve has quit IRC00:09
*** sarob has quit IRC00:10
*** sarob has joined #openstack-meeting-alt00:11
*** pballand has quit IRC00:12
*** DennyZhang has joined #openstack-meeting-alt00:14
*** sarob has quit IRC00:15
*** flwang has joined #openstack-meeting-alt00:20
*** vipul is now known as vipul-away00:21
*** balajiiyer has joined #openstack-meeting-alt00:21
*** sarob has joined #openstack-meeting-alt00:27
*** esker has joined #openstack-meeting-alt00:27
*** amcrn has joined #openstack-meeting-alt00:28
*** lblanchard has quit IRC00:40
*** lblanchard has joined #openstack-meeting-alt00:42
*** flaper87 is now known as flaper87|afk00:42
*** kebray_ has quit IRC00:45
*** lblanchard has quit IRC00:53
*** IlyaE has joined #openstack-meeting-alt00:53
*** amcrn has quit IRC01:04
*** DennyZhang has quit IRC01:09
*** Barker has joined #openstack-meeting-alt01:11
*** mestery has quit IRC01:18
*** harlowja has joined #openstack-meeting-alt01:33
*** nosnos has joined #openstack-meeting-alt01:35
*** malini_afk is now known as malini01:43
*** sankarshan_away is now known as sankarshan01:45
*** kebray_ has joined #openstack-meeting-alt01:46
*** michael-yu has joined #openstack-meeting-alt01:47
*** michael-yu has quit IRC01:54
*** IlyaE has quit IRC02:01
*** sarob has quit IRC02:08
*** sarob has joined #openstack-meeting-alt02:08
*** michael-yu has joined #openstack-meeting-alt02:10
*** sarob has quit IRC02:13
*** kebray_ has quit IRC02:19
*** markwash has quit IRC02:25
*** coolsvap_away has quit IRC02:33
*** michael-yu has quit IRC02:33
*** yamahata has quit IRC02:42
*** malini is now known as malini_afk02:51
*** colinmcnamara has quit IRC02:51
*** colinmcnamara has joined #openstack-meeting-alt03:05
*** colinmcnamara has quit IRC03:10
*** michael-yu has joined #openstack-meeting-alt03:17
*** vipul-away is now known as vipul03:17
*** michael-yu has quit IRC03:18
*** colinmcnamara has joined #openstack-meeting-alt03:20
*** jecarey has joined #openstack-meeting-alt03:24
*** rnirmal has joined #openstack-meeting-alt03:26
*** mattgriffin has quit IRC03:30
*** banix has joined #openstack-meeting-alt03:31
*** mattgriffin has joined #openstack-meeting-alt03:32
*** doug_shelley66 has quit IRC03:39
*** michael-yu has joined #openstack-meeting-alt03:42
*** michael-yu has quit IRC03:42
*** mattgriffin has quit IRC03:44
*** michael-yu has joined #openstack-meeting-alt03:44
*** mattgriffin has joined #openstack-meeting-alt03:46
*** harlowja is now known as harlowja_away03:54
*** gokrokve has joined #openstack-meeting-alt03:55
*** colinmcnamara has quit IRC03:56
*** colinmcnamara has joined #openstack-meeting-alt03:57
*** colinmcnamara has quit IRC04:02
*** michael-yu has quit IRC04:07
*** coolsvap has joined #openstack-meeting-alt04:08
*** mattgriffin has quit IRC04:15
*** akuznetsov has joined #openstack-meeting-alt04:25
*** michael-yu has joined #openstack-meeting-alt04:25
*** rnirmal has quit IRC04:26
*** michael-yu has quit IRC04:28
*** colinmcnamara has joined #openstack-meeting-alt04:28
*** gokrokve has quit IRC04:28
*** mattgriffin has joined #openstack-meeting-alt04:28
*** gokrokve has joined #openstack-meeting-alt04:29
*** balajiiyer has quit IRC04:31
*** colinmcnamara has quit IRC04:33
*** DennyZhang has joined #openstack-meeting-alt04:37
*** adrian_otto has joined #openstack-meeting-alt04:37
*** vipul is now known as vipul-away04:40
*** jecarey has quit IRC04:41
*** vipul-away is now known as vipul04:44
*** gokrokve has quit IRC04:53
*** colinmcnamara has joined #openstack-meeting-alt04:58
*** DinaBelova_ is now known as DinaBelova04:58
*** michael-yu has joined #openstack-meeting-alt05:02
*** colinmcnamara has quit IRC05:03
*** Barker has quit IRC05:06
*** chandankumar_ has joined #openstack-meeting-alt05:08
*** yamahata has joined #openstack-meeting-alt05:13
*** vipul is now known as vipul-away05:15
*** sarob has joined #openstack-meeting-alt05:15
*** tanisdl has quit IRC05:17
*** coolsvap is now known as coolsvap_away05:23
*** gokrokve has joined #openstack-meeting-alt05:25
*** vipul-away is now known as vipul05:32
*** adrian_otto has left #openstack-meeting-alt05:35
*** eankutse has joined #openstack-meeting-alt05:35
*** flwang has quit IRC05:36
*** arnaud__ has quit IRC05:36
*** arnaud has quit IRC05:37
*** vipul is now known as vipul-away05:47
*** eankutse has quit IRC05:54
*** eankutse has joined #openstack-meeting-alt05:54
*** colinmcnamara has joined #openstack-meeting-alt05:59
*** flwang has joined #openstack-meeting-alt05:59
*** IlyaE has joined #openstack-meeting-alt06:02
*** colinmcnamara has quit IRC06:03
*** DinaBelova is now known as DinaBelova_06:04
*** vipul-away is now known as vipul06:10
*** IlyaE has quit IRC06:10
*** SushilKM has joined #openstack-meeting-alt06:11
*** aignatov_ is now known as aignatov06:17
*** coolsvap_away is now known as coolsvap06:19
*** doug_shelley66 has joined #openstack-meeting-alt06:21
*** IlyaE has joined #openstack-meeting-alt06:26
*** mattgriffin has quit IRC06:30
*** sarob has quit IRC06:30
*** sarob has joined #openstack-meeting-alt06:31
*** SushilKM has quit IRC06:31
*** eankutse1 has joined #openstack-meeting-alt06:31
*** banix has quit IRC06:32
*** sankarshan is now known as sankarshan_away06:32
*** IlyaE has quit IRC06:32
*** eankutse has quit IRC06:34
*** sarob has quit IRC06:35
*** eankutse1 has quit IRC06:36
*** csaba|afk is now known as csaba06:39
*** NikitaKonovalov_ is now known as NikitaKonovalov06:41
*** nosnos_ has joined #openstack-meeting-alt06:43
*** nosnos has quit IRC06:43
*** DennyZhang has quit IRC06:44
*** NikitaKonovalov is now known as NikitaKonovalov_06:50
*** SushilKM has joined #openstack-meeting-alt06:50
*** SushilKM has quit IRC06:54
*** xuhanp has joined #openstack-meeting-alt06:56
*** dguitarbite has joined #openstack-meeting-alt06:57
*** SushilKM has joined #openstack-meeting-alt06:58
*** sarob has joined #openstack-meeting-alt07:01
*** nadya__ has joined #openstack-meeting-alt07:05
*** sarob has quit IRC07:09
*** SushilKM has quit IRC07:10
*** michael-yu has quit IRC07:10
*** michael-yu has joined #openstack-meeting-alt07:12
*** sarob has joined #openstack-meeting-alt07:17
*** NikitaKonovalov_ is now known as NikitaKonovalov07:18
*** sarob_ has joined #openstack-meeting-alt07:19
*** aignatov is now known as aignatov_07:20
*** SushilKM has joined #openstack-meeting-alt07:20
*** vipul is now known as vipul-away07:21
*** sarob has quit IRC07:21
*** jjmb has quit IRC07:22
*** sarob_ has quit IRC07:23
*** vipul-away is now known as vipul07:25
*** michael-yu has quit IRC07:35
*** yamahata has quit IRC07:38
*** csaba is now known as csaba|afk07:44
*** vipul is now known as vipul-away07:45
*** obondarev_ has joined #openstack-meeting-alt07:53
*** vipul-away is now known as vipul07:54
*** aignatov_ is now known as aignatov07:54
*** yogesh has joined #openstack-meeting-alt08:00
*** flaper87|afk is now known as flaper8708:03
*** aignatov is now known as aignatov_08:06
*** SushilKM has quit IRC08:08
*** jcoufal has joined #openstack-meeting-alt08:13
*** SushilKM has joined #openstack-meeting-alt08:14
*** DinaBelova_ is now known as DinaBelova08:15
*** sarob has joined #openstack-meeting-alt08:17
*** sarob has quit IRC08:22
*** SergeyLukjanov_ is now known as SergeyLukjanov08:23
*** luqas has joined #openstack-meeting-alt08:23
*** michael-yu has joined #openstack-meeting-alt08:24
*** jtomasek has joined #openstack-meeting-alt08:26
*** michael-yu has quit IRC08:35
*** dguitarbite has quit IRC08:44
*** dguitarbite has joined #openstack-meeting-alt08:45
*** luqas has quit IRC08:55
*** colinmcnamara has joined #openstack-meeting-alt09:01
*** safchain has joined #openstack-meeting-alt09:02
*** derekh has joined #openstack-meeting-alt09:03
*** colinmcnamara has quit IRC09:05
*** aignatov_ is now known as aignatov09:10
*** sarob has joined #openstack-meeting-alt09:17
*** derekh has quit IRC09:18
*** sarob has quit IRC09:22
*** venkatesh has joined #openstack-meeting-alt09:25
*** venkatesh has quit IRC09:26
*** luqas has joined #openstack-meeting-alt09:27
*** SergeyLukjanov is now known as SergeyLukjanov_a09:27
*** dosaboy_ is now known as dosaboy09:28
*** SergeyLukjanov_a is now known as SergeyLukjanov_09:28
*** aignatov is now known as aignatov_09:34
*** dosaboy has quit IRC09:36
*** aignatov_ is now known as aignatov09:37
*** dosaboy has joined #openstack-meeting-alt09:38
*** matrohon has quit IRC09:40
*** matrohon has joined #openstack-meeting-alt09:40
*** SergeyLukjanov_ is now known as SergeyLukjanov09:40
*** flwang has quit IRC09:47
*** SergeyLukjanov is now known as SergeyLukjanov_09:47
*** NikitaKonovalov is now known as NikitaKonovalov_09:47
*** aignatov is now known as aignatov_09:49
*** xuhanp has quit IRC09:52
*** johnthetubaguy has joined #openstack-meeting-alt09:52
*** aignatov_ is now known as aignatov09:53
*** DinaBelova is now known as DinaBelova_09:58
*** SushilKM has quit IRC10:02
*** boris-42 has quit IRC10:02
*** SushilKM has joined #openstack-meeting-alt10:02
*** boris-42 has joined #openstack-meeting-alt10:04
*** SushilKM has quit IRC10:07
*** SushilKM has joined #openstack-meeting-alt10:08
*** akuznetsov has quit IRC10:12
*** akuznetsov has joined #openstack-meeting-alt10:13
*** sarob has joined #openstack-meeting-alt10:13
*** sarob_ has joined #openstack-meeting-alt10:17
*** yogesh has quit IRC10:18
*** sarob has quit IRC10:18
*** SushilKM has quit IRC10:19
*** sarob_ has quit IRC10:22
*** xuhanp has joined #openstack-meeting-alt10:25
*** xuhanp has quit IRC10:26
*** flwang has joined #openstack-meeting-alt10:31
*** jesusaurus has quit IRC10:35
*** derekh has joined #openstack-meeting-alt10:35
*** jesusaurus has joined #openstack-meeting-alt10:37
*** gokrokve has quit IRC11:11
*** sarob has joined #openstack-meeting-alt11:17
*** sarob has quit IRC11:22
*** aignatov is now known as aignatov_11:26
*** shanks has joined #openstack-meeting-alt11:28
*** yogesh has joined #openstack-meeting-alt11:28
*** derekh has quit IRC11:29
*** yogesh has quit IRC11:33
*** nadya__ has quit IRC11:33
*** aignatov_ is now known as aignatov11:50
*** boris-42 has quit IRC11:53
*** boris-42 has joined #openstack-meeting-alt11:56
*** colinmcnamara has joined #openstack-meeting-alt12:03
*** gokrokve has joined #openstack-meeting-alt12:06
*** colinmcnamara has quit IRC12:08
*** gokrokve has quit IRC12:12
*** sergmelikyan has quit IRC12:12
*** safchain has quit IRC12:13
*** jcoufal has quit IRC12:14
*** jcoufal has joined #openstack-meeting-alt12:15
*** sarob has joined #openstack-meeting-alt12:17
*** sarob has quit IRC12:22
*** aignatov is now known as aignatov_12:26
*** julim has joined #openstack-meeting-alt12:32
*** jjmb has joined #openstack-meeting-alt12:38
*** jjmb has quit IRC12:38
*** sgordon has joined #openstack-meeting-alt12:40
*** doug_shelley66 has quit IRC12:43
*** irenab has joined #openstack-meeting-alt12:55
*** gokrokve has joined #openstack-meeting-alt13:01
*** baoli has joined #openstack-meeting-alt13:01
baoli#startmeeting pci passthrough13:02
openstackMeeting started Wed Jan 22 13:02:17 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: pci passthrough)"13:02
openstackThe meeting name has been set to 'pci_passthrough'13:02
*** sadasu has joined #openstack-meeting-alt13:02
*** rkukura has joined #openstack-meeting-alt13:02
*** coolsvap has quit IRC13:03
irenabhi13:03
baoliHi13:03
sadasuHello!13:03
irenabbaoli: following you email, I suggested to cover SRIOV related this week13:04
baoliIrenab, I agree13:05
irenabAs for heyongli BP , I reviewed, no major  issues13:05
ijwyo13:05
irenabJust do not like the way it deals with netowrking for now....13:05
baoliWhat's exactly the plan B you mentioned13:06
irenabBut it least it adds some support13:06
ijwthe one I suggested?13:06
*** pdmars has joined #openstack-meeting-alt13:06
*** pdmars has quit IRC13:06
*** gokrokve has quit IRC13:06
irenabyes, what Ian menat by neutron eawre scheduler13:06
irenab^aware13:06
*** pdmars has joined #openstack-meeting-alt13:07
baoliHow is it exactly defined?13:07
*** luqas has quit IRC13:08
sadasuI had one question regarding the bp wiki13:08
irenabsadasu: I think heyongli is not here13:08
*** BrianB_ has joined #openstack-meeting-alt13:09
sadasuok...maybe ijw can answer13:09
ijwbaoli: the problem is that we need to decide in advance of starting a VM which specific network cards can be used to attach to the networks it wants13:09
irenabbaoli: you can see Ian's suggestion at #link: https://docs.google.com/document/d/1vadqmurlnlvZ5bv3BlUbFeXRS_wh-dsgi5plSjimWjU/edit?pli=1#13:09
sadasupci-flavor can be specified as part of nova flavor create and as part of --nic option13:09
*** heyongli has joined #openstack-meeting-alt13:09
ijwbaoli: the solution is for nova-api to ask Neutron what the requirements are and hand it to the scheduler13:09
sadasuignoring the exact syntax for now13:09
heyonglisorry my home network un-stable today13:10
sadasuhave we thought of the case where pci-flavors can be specified both places?13:10
sadasuI don't see it in the doc13:10
ijwAnd according to rkukura, there's a similar requirement for provider networks, so I think in practice a lot of that solution would be done by them and we could piggyback on it, but I also think it's Juno territory13:10
irenabsadasu: as far as I understood, it is there13:10
sadasunova flavor-key m1.small set pci_passthrough:pci_flavor= '1:bigGPU'13:11
ijwsadasu: yes - the ones in the nova flavor are non-Neutron passthrough devices which are simply attached (even if they're NICs).  The ones in Neutron are attached by vif plugging.13:11
sadasunova boot mytest --flavor m1.tiny --image=cirros-0.3.1-x86_64-uec --nic net-id=network_X pci_flavor= '1:phyX_NIC;'13:11
*** aignatov_ is now known as aignatov13:11
ijwAnd we have to combine all the PCI device requirements before we try to scheule.13:11
irenabheyongli: Can you please address my comments on wiki?13:12
sadasuijw: I understand that since I have been following this discussion...I think it should be made very clear and explicit in the doc13:12
heyongliwhich one? irenab?13:12
ijwsadasu: Ok, that seems sensible13:12
sadasualso, admin should be careful while creating a pci-flavor that is a mixture of networking and non-networking devices13:13
irenabheyongli: can we quickly go over all of them13:13
ijwThe document could do with a work-over for formatting, too, it's hard to read because the formatting's patchy13:13
heyongliirenab: ok13:13
ijwI was going to do that if I found time but I haven't managed it yet13:13
heyongliijw: i had to do it tomorrow13:14
irenabheyongli: just look for irenab on wiki page13:14
ijwI suggest anyone else who has 5 minutes to spare picks a section13:14
irenabfirst on pci_information format, do you agree?13:14
heyongliformat or name?13:14
ijwThe idea of pci_information as I understood it is that you could supply the config item more than once rather than having a list of matches13:14
ijwBut we should choose one, clearly that's not defined well enough13:15
irenabheyongli: both format and name13:15
irenabyou have '=>' there13:15
heyongliirenab: sure, if this kind of problem or typo, i think you can modify it directly.13:16
irenabheyongli: thanks13:16
heyonglifor name, i don't have the good idea.13:17
irenabheyongli: another Question on pci_flavor_attrs. Is it single defintion?13:17
heyongliit can be multi ,if we want it to be.13:17
*** sarob has joined #openstack-meeting-alt13:17
irenabshould it be defined per PCI flavor or not?13:18
heyonglithis should be identical in all cloud machine, is it a problem?13:18
heyongliirenab: no , i don't thinks so, any concern?13:18
irenabno, I just not sure I understand the usage and what should  be defined there by cloud admin13:18
baoliwell, I imagine it would. What if you want to add a new attribute in order to do some new stuff?13:19
irenabAs I understood, its the list of properties to filter the PCI devices by scheduler, right?13:19
baoliThen the question becomes why would you like to define pci flavors on the fly if the attribute is static?13:20
ijwI think it should be (a) single and (b) comma separated13:20
*** amotoki has joined #openstack-meeting-alt13:20
heyongliirenab, not filter , it's the scheduler orgnized the stats pool, i think .13:20
ijwa, b, c for example13:20
ijwbaoli: flavors can be defined on the fly but we need to validate the attributes they use, I think13:20
irenabheyongli: but eventually the device will be picked by mataching all attrs?13:21
heyonglilist is a json structure, like all other definition,13:21
ijwYou still have quite a lot of flexibility in what flavors you make even if the attrs are the same13:21
baoliwhy attr is static?13:21
ijwBecause pci_stats are created based on it, really, and you could invalidate flavors if you change it13:21
ijwWe discussed this before and I think the conclusion is that yes, it could be something you could change, but if we wanted to do that we could add it later13:22
heyongliijw: yeah, there could be some improvement maybe, but have no idea yet.13:22
*** sarob has quit IRC13:22
ijwBut if we have lots of lines of the form:13:22
ijwpci_information=[{match}, {attrs}]13:22
ijwThat's not awful13:22
ijwAnd the lines are short enough to be readable - long config items don't wrap well, I think13:22
heyongliijw: don't we talk abou the  pci_flavor_attrs?13:23
*** vkmc has joined #openstack-meeting-alt13:23
*** vkmc has joined #openstack-meeting-alt13:23
baoliwould compute node read it as well so that it can validate the attr in the list?13:23
irenabat least I do13:23
ijwheyongli: sorry, I'm talking about both at once ;)13:23
ijwpci_flavor_attrs=a, b, c I think13:23
ijwspaces ignored13:23
irenabso attrs in pci_info can be from the (a,b,c) only13:24
irenab?13:24
ijwbaoli: compute node uses it, yes - not to validate, but to group the pci_stats it's returning13:24
ijwirenab: yes13:24
heyongliijw: this lead the to code need to be parse it, but if use [], you don't do anything.13:24
baoliijw, I mean to validate the attr that's used in the pci information list?13:24
ijwheyongli: string.split will do it for commas, so I think that's 2 lines of code for a slightly nicer format13:25
ijwbaoli: In pci_information you can specify things outside the pci_flavor_list13:25
ijwOr are you saying we should check they're all present13:25
ijw?13:25
heyongliijw: i'm fine with it. but someone will jump in suggest the [] i think, i accept it , and let's move on13:25
baoliso attrs used in the pci information could be anything?13:26
irenabbaoli: as long as defined on Controller13:26
irenabfor pci_flavor_attr13:26
*** sankarshan_away is now known as sankarshan13:26
heyonglibaoli: i think this is the start of configration, it's no method to verify it, except the format13:26
ijwbaoli: yes13:27
ijwirenab: no13:27
ijwirenab: You can put what you like in there, they don't have to be in the flavor_attrs - but the ones that aren't can only be used for information, not for scheduling13:28
baoliijw, ok. got it13:28
*** doug_shelley66 has joined #openstack-meeting-alt13:28
irenabijw: can you please define the pci_flavor_attr, I am confused13:28
irenabijw: got it13:28
ijwOK13:28
ijwHaven't caught up with John yet - he did a driveby on the google document, I replied to his comment but haven't seen a response.  The mailing list message also had no response when I checked an hour ago.13:29
baoliHow does the flavor definition get conveyed to all the compute nodes?13:30
ijwI see where he's coming from with his points about host aggregate but I think he's basically suggesting that we use host aggregates in place of the whole system, both pci_information and flavors13:30
heyongliijw: john remove his name from this blue print, he is busy on other thing, and we kill his time too much13:30
ijwheyongli: ok13:30
ijwI'm going for beer with him next week, I'll have a conversation then13:30
heyongliijw: so cool13:30
ijwIndeed ;)13:30
ijwOne week, three countries, no sleep ;)13:31
heyongliijw: thank you do so much for this .13:31
ijwNah - this is not work, this is beer because I happen to be in the area ;)13:31
ijwAlso, beer13:31
heyonglii update the pci  attr to a, b, c13:32
irenabso, are we OK with this BP?13:32
baoliSetting aside the beer, How does the flavor definition get conveyed to all the compute nodes?13:32
irenabCan we move to baoli's list for the rest?13:32
ijwbaoli: don't you touch my pint!13:32
ijwbaoli: That's actually a good question13:32
baoliit's early morning, and I have to work. No beer13:33
ijwbaoli: I think there are two options.  Either a compute node requests it when it comes up and doesn't start sending pci_stats till it has it, or the control node casts it occasionally13:33
heyonglisorry , i don't under stand the question13:33
baoliwell, you can define it on the fly13:33
ijwYes, that's why an update after cast might be a better option13:34
irenabijw: can you repeat the question?13:34
ijwI mean, even if you can't change it via the API, you can stop the control server, change it and restart, so we have to be flexible13:34
ijwirenab: baoli asked how we get the pci flavor attrs to the compute hosts so that they can send pci_stats in the right format13:35
sadasuso at startup time of compute and controller nodes and right after update via CLI?13:35
*** derekh has joined #openstack-meeting-alt13:35
baoliijw, restarting is an interesting proposation13:35
ijwbaoli: indeed - if you restart the compute it needs to find out the information, which is either a need for a call or a periodic broadcast; if you restart the control node you have to send the information, which can be a cast13:36
ijwIf the two are out of sync then the compute node would send the wrong info and the control node would have to drop it13:36
sadasunot sure if periodic broadcast is a good idea13:37
baoliWell, it doesn't sound good to me if restarting needs to be done for a change of flavor, doesn't it13:37
heyongliijw: compute not sent the flavor i think, but use wrong specs.13:37
ijwbaoli: No - this is only if you decide to change the list of attributes (in the config, at the moment)13:37
ijwflavors would be fine for dynamic update, the compute node doesn't need to know what they are13:37
sadasubaoli: that may not be the reason for a restart, but before a flavor definition update has been sent to all compute nodes, it is possible that the controller is restarted13:38
*** luqas has joined #openstack-meeting-alt13:38
baoliijw, why? are you sending stats based on flavor definition?13:38
ijwbaoli: no - as you say13:38
heyonglibaoli: i don't think so.13:38
irenabon flavor_attrs I think13:38
heyonglistats construct base on the attr list,13:38
ijwYou're sending pci stats (and instance start requests) using pci attrs, that's the only way control and compute communicate13:38
baoliCan you explain how the stats get calculated?13:39
ekarlsojust 7win 37813:39
ijwBut they do have to agree on the list of attributes they're using (pci_flavor_attrs)13:39
*** jdob has joined #openstack-meeting-alt13:39
baoliAgain, can you explain how the stats get calculated?13:40
baoliby a compute node?13:40
ijwbaoli: I have devices (1, 2) and (1, 4) for (vendor, product) - if the attrs list is 'vendor' I would get {vendor: 1, count: 2} and if it's vendor, product I would get {vendor:1, device: 2, count:1} and {vendor:1, device:4, count:1}13:40
ijwMake sense?13:40
baolihow do you know it's by vendor or (vendor, product_id)?13:41
ijwpci_flavor_attrs' value13:41
ijwAs received from the control node13:41
ijw... somehow, which is where we started the discussion13:41
ijwMake sense?13:42
baoliI must have missed something13:42
baoliNot yet.13:42
baoliyou said the attribute list is one item?13:43
baolisorry. You define an attribute list as (a,b,c, ....)?13:43
ijwNo, a comma separated list13:44
ijwof multiple attributes13:44
baoliAm I using a comma in there?13:44
ijwbaoli: I mean 'no, it's not one item'13:44
ijwI'll try to be clea13:44
ijwr13:44
baoliso is it (a1, a2, a3)?13:44
baolifor example?13:44
ijwI meant that I think pci_flavor_attrs should appear just once in the config, not repeatedly; that it should have a value like 'a,b,c' because the JSON format '["a","b","c"]' is a bit unnecessary for a list of simple items; and that the programmatic value would be a list of strings.13:45
baolithat's fine13:45
baoliI don't care about the format, actually13:46
ijwYeah, we went all over the shop in that discussion but those are the three things I meant to say13:46
baolihow stats get calculated based on ["a", "b", "c"]?13:47
heyonglibaoli: let me show you13:47
ijwAs above - we bucket based on unique combinations of value, so there would be one stats row for each unique combination of a, b, c attribute values13:47
heyongliif device had [a, b], it should in the [a,b ] pool13:47
heyonglii f  device had [a, b,c ], it in the [a,b,c] pool13:47
heyongliif only device had only a, it's in the [a,] pool13:48
ijwUm, no13:48
baolioh, guys, come on13:48
heyongliacctually, it's [a, none , none ] pool13:48
ijwnot at all13:48
*** banix has joined #openstack-meeting-alt13:48
ijwLook - so the attributes will be ones that the pci devices have.  device, product, things in extra info, so on13:48
heyonglithere should have no overlap, and what is it in you mind, intresting.13:49
ijwAbsences in any of them would be None13:49
heyongliijw: cool, i agree13:49
ijwBut the bucket is unique combinations of those attributes' values in the pci device list on the compute node13:49
heyonglii said [a], is [a, none none]13:49
*** akuznetsov has quit IRC13:49
ijwWe do an operation like the SQL statement SELECT $pci_flavor_attrs, count(*) from pci_devices GROUP BY $pci_flavor_attrs13:50
ijwWhich means that, for each unique value combo we get a count of devices with that combo13:50
ijwheyongli: yeah, I think I agree with what you mean but I don't think your explanation was at all clear ;)13:50
ijwSo for pci_flavor_attrs='device,vendor'13:51
*** tnurlygayanov_ has joined #openstack-meeting-alt13:51
heyongliijw: may be , i'm not good at it like you, really,13:51
ijwTake a list of PCI devices13:51
*** tnurlygayanov has quit IRC13:51
ijwTurn it into a list of [device-value,vendor-value] one for each device13:51
ijwCount unique combinations13:51
heyongliijw: in compute node we don't need sql the db to calulate this13:51
ijwReturn the combination and count to the control node13:51
baoliijw, you need [device], [vendor], [device, vendor], right?13:52
ijwheyongli: yes - I'm not suggesting we use SQL, it's just I can express the transformation unambiguously with one line of SQL13:52
heyongliijw: in this way, the device will belong to multi pool, this had  problem.13:52
ijwbaoli: nope - in the schedulers, flavors match more than one of those buckets13:52
baoliijw, I'm really lost here.13:52
ijwSo if I have a flavor that says 'vendor: 1' and I have pci_flavor_attrs of 'device,vendor'13:53
heyonglijiw: if a flavor request [a, b] you maybe allocate it from pool [a,b,c] this will lead to use up the device but stats say compute node had it13:53
ijwThen in the scheduler I have pci_stats for each device,vendor combination13:53
baoliyou must have thought it through. But I would recommend documenting this in a well specified algorithm. Becasue this is critical13:53
ijwI check each pci_stats row that has vendor=1, ignoring the device13:53
ijwAnd find a free device13:54
*** yamahata has joined #openstack-meeting-alt13:55
baoliThere seems to be a big disconnect in this regard. So it must be clearly specified in the doc.13:55
*** jecarey has joined #openstack-meeting-alt13:55
heyongliijw: this will lead to this: one device in multi pool(bucks,) this is not good.  i suggest:  if device match [vendor=1, product=5,...], it count only in the most longer mach pool.13:55
heyonglibaoli: agree13:56
ijwheyongli: One device will never be in multiple pools13:56
ijwheyongli: There is no short-match set of pools13:56
heyongliijw: so , that's good for me13:56
*** aignatov is now known as aignatov_13:57
ijwA pool is always tagged by a full set of pci_flavor_attrs.  The scheduler works out partial matches, so the complexity isn't passed on to the compute nodes13:57
baoliOk, time's almost up now.13:57
ijwSo hopefully that's clear13:57
*** mestery has joined #openstack-meeting-alt13:57
baoliWe'll start SRIOV tomorrow13:57
heyongliijw: i only request the stats calculate algorithm had this feature(longer match), any thing other is fine to me.13:57
ijwbaoli: I'll see about that algorithm, but I guarantee it will horrify - it's definitely a long search in the worst case13:57
baoliijw, I dont' like anything that's horrific.13:58
ijwheyongli: I think you and I agree what the stats will be - just put a patch up and I'll review13:58
heyonglii update  the the doc base on this request.13:58
*** banix has quit IRC13:58
heyongliijw: sure, i had the patch, and sent, that's fit our goal, i think.13:59
ijwbaoli: It's slow in the worst case, which the admin has an option to set up.  It has to be because we allow such general flavor conditions, because people want them.  We minimise the data it operates on to ensure it's not going to be too slow in practice, but the algorithm as code does have to do retries as it finds a match so it will look suspiciously like lots of nested loops13:59
ijwIt will have a comment explaining that when we come to write it13:59
baoliijw, my concern is how it works because I haven't seen a complete description on this yet.13:59
heyongliijw: this fine, stats report base on one compute node, there is no so many device13:59
ijwbaoli: I certainly wrote a fairly complete one, but if you'll take it on trust that it will work quite honestly I would sooner write the algorithm as code14:00
heyonglibaoli: much like the current implementation, i think.14:00
baoliAnd as far as I'm concerned, it's nasty and unnecessarily complicated. I'm not sure we are going in the right direction any more14:00
*** colinmcnamara has joined #openstack-meeting-alt14:00
ijw(which I can do once heyongli's patch is up so I can work off of it)14:00
*** nadya__ has joined #openstack-meeting-alt14:00
baoli#endmeeting14:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:01
openstackMeeting ended Wed Jan 22 14:01:07 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-22-13.02.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-22-13.02.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-22-13.02.log.html14:01
*** heyongli has quit IRC14:01
ijwNot trying to be awkward, just trying to save time.  Sounds like heyongli will have something by next week at the latest and we have a quiet period while I2 is sorted out where we can get our patches all lined up14:01
*** dprince has joined #openstack-meeting-alt14:01
*** gokrokve has joined #openstack-meeting-alt14:02
*** akuznetsov has joined #openstack-meeting-alt14:04
*** yamahata has quit IRC14:05
*** colinmcnamara has quit IRC14:05
*** boris-42 has quit IRC14:06
*** gokrokve has quit IRC14:06
*** colinmcnamara has joined #openstack-meeting-alt14:07
*** aignatov_ is now known as aignatov14:09
*** boris-42 has joined #openstack-meeting-alt14:10
*** lblanchard has joined #openstack-meeting-alt14:11
*** eankutse has joined #openstack-meeting-alt14:17
*** sarob has joined #openstack-meeting-alt14:17
*** eankutse has quit IRC14:19
*** eankutse has joined #openstack-meeting-alt14:19
*** coolsvap has joined #openstack-meeting-alt14:22
*** sarob has quit IRC14:22
*** banix has joined #openstack-meeting-alt14:23
*** SushilKM has joined #openstack-meeting-alt14:23
*** mattgriffin has joined #openstack-meeting-alt14:27
*** SushilKM has quit IRC14:27
*** jaypipes has quit IRC14:27
*** jaypipes has joined #openstack-meeting-alt14:28
*** SushilKM has joined #openstack-meeting-alt14:28
*** eankutse has quit IRC14:30
*** eankutse has joined #openstack-meeting-alt14:30
*** betsy has joined #openstack-meeting-alt14:30
*** SushilKM has quit IRC14:33
*** xuhanp has joined #openstack-meeting-alt14:34
*** safchain has joined #openstack-meeting-alt14:35
*** esker has quit IRC14:39
*** esker has joined #openstack-meeting-alt14:40
*** SushilKM has joined #openstack-meeting-alt14:44
*** esker has quit IRC14:45
*** amytron has joined #openstack-meeting-alt14:47
*** kevinconway has joined #openstack-meeting-alt14:48
*** balajiiyer has joined #openstack-meeting-alt14:51
*** baoli has quit IRC14:54
*** SushilKM has quit IRC14:54
*** abccba has joined #openstack-meeting-alt14:56
*** nosnos_ has quit IRC14:57
*** Swami has joined #openstack-meeting-alt15:02
Swamihi15:02
Swamisafchain ping15:02
*** gokrokve has joined #openstack-meeting-alt15:03
Swamijamie ping15:03
safchainSwami, Hi15:03
Swamisafchain: hi15:03
Swami#startmeeting distributed_virtual_router15:03
openstackMeeting started Wed Jan 22 15:03:59 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
*** AlanClark has joined #openstack-meeting-alt15:04
Swamitopic: Changes in our API15:04
Swami#topic: Changes in our API15:05
*** openstack changes topic to ": Changes in our API (Meeting topic: distributed_virtual_router)"15:05
Swamisafchain: We are currently planning to move away from the user command that would create the EGA's15:06
safchainSwami, did you update the gdoc ?15:06
SwamiSo we would be using the existing router-gateway-set and router-gateway-clear command to provision the EGA in the compute Nodes.15:06
Swamisafchain: I have not, but  I will update it today.15:07
*** eankutse has quit IRC15:07
Swamisafchain: But in this model, each compute node will be using either single EGA or a multiple EGA per tenant based on the global config.15:07
*** gokrokve has quit IRC15:08
safchainok, I will check the gdoc15:08
*** gokrokve has joined #openstack-meeting-alt15:09
Swamisafchain: But still we can't get rid of the "--distributed" arg for the "router" object and that is the only way in our model we can distinguish between a centralized and distributed router.15:10
*** balajiiyer has left #openstack-meeting-alt15:11
*** rnirmal has joined #openstack-meeting-alt15:11
safchainSwami, ok15:12
Swamisafchain: I heard that you were busy with the tempest work and made lot more progress.15:13
safchainSwami, Yes a lot, and also work and the HA BP15:14
*** Barker has joined #openstack-meeting-alt15:14
Swamisafchain: Is your HA targeted for the Icehouse 3 milestone.15:14
safchainSwami, yes15:14
Swamisafchain: Did you get a chance to go over the "Provider router" blueprint15:15
SwamiJamie ping15:15
safchainsafchain, not yet15:15
safchainSwami, I have to15:15
Swamisafchain: thanks, once you go over it let me know and we can discuss.15:15
SwamiI still see that there should be some router attribute that should say that the services can run in that router or not.15:16
*** sarob has joined #openstack-meeting-alt15:17
*** irenab has quit IRC15:18
Swamisafchain: On monday I attended the service vm meeting and I also brought up this issue with sumit and other folks.15:18
safchainSwami, ok, I will have a look to the log15:19
Swamisafchain: I am planning to push a WIP code by icehouse 3.15:19
safchainSwami, great15:19
Swamiat least for the East-West part, we may not be ready with the north-south by that time.15:20
Swamilet us see how it goes.15:20
Swamisafchain: Are there anyone right now working on the L3-consolidation15:20
Swamisafchain: Which subteam is working on the L3-consolidation.15:21
safchainSwami, I don't know15:21
*** sarob has quit IRC15:22
*** dhellmann is now known as dhellmann_15:22
*** malini_afk is now known as malini15:22
Swamisafchain: I had a question with respect to the "shared" flag in the external net object15:23
SwamiWhat is the functionality of the "shared' flag. I tried setting both False and true and in both cases I can see that all tenants can access the external net if created by an admin.15:23
SwamiThe only difference I see is "if shared=true", the subnet associated with the external net is visible to the tenant. I am not sure what is the use case for it.15:24
*** SheenaG has left #openstack-meeting-alt15:25
*** DinaBelova_ is now known as DinaBelova15:25
Swamisafchain: any thoughts on that topic15:27
safchainSwami, no I have to check that also15:28
safchainSwami, I did the same test as you15:29
Swamisafchain: Thanks hope we are on the same boat.15:29
*** sankarshan is now known as sankarshan_away15:29
Swamisafchain: I did see there was a blueprint out there to fix this during havana, but this was untargetted at the end.15:29
safchainSwami, sorry for the lag, bit busy today15:30
Swamisafchain: That's fine, no worries.15:30
safchainSwami, do you have the link of this BP15:30
Swamiany way I will have to stop by 7.40a.m15:30
SwamiYes, I will paste it right now.15:30
Swami#link https://wiki.openstack.org/wiki/Neutron/sharing-model-for-external-networks15:31
safchainSwami, thx15:31
*** eankutse has joined #openstack-meeting-alt15:32
*** SergeyLukjanov_ is now known as SergeyLukjanov15:33
Swamisafchain: Do you have any other topics to discuss15:34
safchainSwami, not today, I will check your gdoc with the modifications to be sure to understand of the API15:36
Swamisafchain: Ok, if you don't have any topic to discuss, we can end the meeting.15:36
SwamiI have a hard stop at 7.40p.m15:36
Swamisafchain: Thanks for the joining the meeting.15:36
SwamiI will update the doc and send you an email.15:37
Swamiuntil then bye15:37
safchainSwami, yes I will ping you if I will have questions, don't hesitate to ping me as well15:37
safchainSwami, thx for the meeting15:37
Swamisafchain: Ok, thanks .15:37
Swamibye15:37
safchainbye15:37
Swami#endmeeting15:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:37
openstackMeeting ended Wed Jan 22 15:37:47 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-01-22-15.03.html15:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-01-22-15.03.txt15:37
openstackLog:            http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-01-22-15.03.log.html15:37
*** Swami has quit IRC15:38
*** sankarshan_away is now known as sankarshan15:40
*** luqas has quit IRC15:41
*** xuhanp has quit IRC15:42
*** jmontemayor has joined #openstack-meeting-alt15:43
*** jmontemayor has quit IRC15:45
*** Phil|2 has joined #openstack-meeting-alt15:45
*** jmontemayor has joined #openstack-meeting-alt15:46
*** PeterSchwaller has joined #openstack-meeting-alt15:46
*** nadya__ has quit IRC15:47
*** akuznetsov has quit IRC15:47
*** aignatov is now known as aignatov_15:49
*** luqas has joined #openstack-meeting-alt15:50
*** eankutse1 has joined #openstack-meeting-alt15:54
*** akuznetsov has joined #openstack-meeting-alt15:55
*** eankutse has quit IRC15:57
*** chandankumar_ has quit IRC15:58
*** rcurran has joined #openstack-meeting-alt15:59
mesteryhi15:59
banixHello15:59
mesteryrkukura: ping15:59
mesterybanix: hi16:00
mesteryrkukura: Per our convo, I can run the meeting if you want, cancelled appointment due to weather here. :)16:00
*** hemanthravi has joined #openstack-meeting-alt16:00
rcurranhi16:00
mestery#startmeeting networking_ml216:00
openstackMeeting started Wed Jan 22 16:00:46 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:00
openstackThe meeting name has been set to 'networking_ml2'16:00
*** ativelkov has left #openstack-meeting-alt16:00
mesteryrcurran: Hey there!16:00
mestery#link https://wiki.openstack.org/wiki/Meetings/ML2 Agenda16:01
mesteryWe have what appears at first glance to be a large agenda today, but I think this may be a short meeting, so lets see.16:01
mestery#Action Item Review16:01
mestery#topic Action Item Review16:01
*** openstack changes topic to "Action Item Review (Meeting topic: networking_ml2)"16:01
*** chadlung_ has joined #openstack-meeting-alt16:01
*** chandankumar_ has joined #openstack-meeting-alt16:01
mesteryasomya: Here?16:01
*** sballe has joined #openstack-meeting-alt16:02
*** esker has joined #openstack-meeting-alt16:02
rkukurahi16:02
mesteryrkukura: Welcome!16:02
*** SushilKM has joined #openstack-meeting-alt16:02
mesterySo, I don't think asomya is here.16:02
mesteryHe had an action item to revive and work with zang on the TypeDrver refactoring.16:02
mesteryI'll ping asomya offline to see where that is at.16:02
mestery#topic Port Binding Conclusions16:02
*** openstack changes topic to "Port Binding Conclusions (Meeting topic: networking_ml2)"16:03
*** asadoughi has joined #openstack-meeting-alt16:03
mesteryrkukura: We segway into the next agenda item around port binding :)16:03
*** SushilKM has left #openstack-meeting-alt16:03
*** chadlung_ has quit IRC16:03
rkukuraSure16:03
mesteryrkukura: You had an action item to send an email to the list with details16:03
mesteryBut we can continue the discussion here as well16:03
*** asomya has joined #openstack-meeting-alt16:03
*** chadlung has joined #openstack-meeting-alt16:03
rkukuraWe covered the details at some length here last week. I've done some further thinking, and it still mostly seems to make sense.16:04
* mestery nods in agreement.16:04
*** DennyZhang has joined #openstack-meeting-alt16:04
rkukuraI will send a summary to the list soon, but have been focusing on the stuff needed for vif_security and for sriov right now16:04
mesteryrkukura: Great!16:05
rkukuraBasically, just need to make sure we are OK with no global ordering of bind_port() and unbind_port() calls across threads and processes16:05
mestery#action rkukura to send summary around ML2 binding to the list.16:05
*** gokrokve has quit IRC16:05
rkukuraI've got some more detail on which attributes for current and original binding are valid in what calls for each API action16:06
rkukuraSo I'll summarize this in the email before getting started coding.16:07
mesteryCool, thanks rkukura.16:07
mesteryAny questions on binding from anyone?16:07
*** SergeyLukjanov is now known as SergeyLukjanov_a16:07
mestery#topic ovs-firewall-driver update16:08
*** openstack changes topic to "ovs-firewall-driver update (Meeting topic: networking_ml2)"16:08
mesteryasadoughi: Here?16:08
rkukuraNote the some other binding-related changes will be coming from the sriov pci-passthru work16:08
*** SergeyLukjanov_a is now known as SergeyLukjanov_16:08
asadoughimestery: hi16:08
sadasurkukura: still very much in the works so didn't bring it up earlier16:08
mesteryasadoughi: Any updates you wanted to share here regarding ovs-firewall and ML2?16:09
asadoughipatches laying the foundation for the actual firewall driver are pending review https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/ovs-firewall-driver,n,z16:09
rkukurasadasu: I've been going thru irenab's proposal, which I think will be discussed at tomorrow's pci-passthru meeting16:09
mestery#info ovs-firewall-driver foundation patches out for review: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/ovs-firewall-driver,n,z16:09
asadoughiactual firewall driver implementation is still in prototype phase, working on seeing what parts i can delegate out to the interested parties, related blueprints16:10
mesteryasadoughi: Will make a note for the team to review these.16:10
sadasurkukura: yes, thanks for taking a look16:10
mesteryasadoughi: OK, thanks for the update!16:10
asadoughismall general concern: still targetting icehouse-3, but don't know where neutron will be (e.g. current testing/gate issues)16:11
asadoughimestery: that's all16:11
mesteryasadoughi: Yes, agreed. This could slip to Juno or something.16:11
mesteryasadoughi: Thanks!16:11
mestery#topic New MechanismDrivers16:12
*** openstack changes topic to "New MechanismDrivers (Meeting topic: networking_ml2)"16:12
mesterySo, there is a large amount of new MDs proposed and in various states.16:13
mesteryPlease see the meeting page for links to reviews and BPs16:13
mesteryrkukura and I were talking yesterday, and we think it would be great for someone from each of these to participate in weekly ML2 meetings.16:13
mesteryEspecially to ensure everyone is aware of things like the port binding changes coming down the pipeline.16:13
mesteryI'll send a note to openstack-dev with this request as well.16:13
*** kebray_ has joined #openstack-meeting-alt16:14
mesteryIn the meantime, reviews of the new MDs with reviews out would be appreciated by their owners.16:14
rkukuraalso to discuss any plugin changes made by or needed by the news drivers16:14
mesteryYes, thanks for bringing that up rkukura.16:14
*** amotoki has quit IRC16:14
mestery#topic Open Discussion16:15
*** openstack changes topic to "Open Discussion (Meeting topic: networking_ml2)"16:15
rkukurawe still have some time, but not much, to make plugin changes that would simplify the drivers, etc.16:15
* mestery nods in agreement with rkukura16:15
*** jcoufal has quit IRC16:16
* mestery was right about this meeting going short I guess. :016:16
mesteryAnything else anyone wants to bring up?16:16
banixJust a side question: Should we have tests which make sure the plugin deals with rollbacks when a mechanism driver post-* operation fails; I have a patch to deal with such failures after update operations.16:16
rkukuraThere are number of ml2 fixes in review, some approved and some not, that we should keep an eye on16:16
asadoughiso, do we need more hands on deck for ml2 and the gate?16:16
*** Barker has quit IRC16:16
*** jmontemayor has quit IRC16:17
mesterybanix: That is a good idea.16:17
rkukurabanix: Do you have a link?16:17
*** eankutse has joined #openstack-meeting-alt16:17
mesteryasadoughi: More hands on deck for the gate is always a good thing. And of course, specific ML2 issues we should be looking at.16:17
*** BrianB__ has joined #openstack-meeting-alt16:18
asadoughimestery: any directions with that regard, i haven't been following all the activity16:18
banixrkukura; no, haven't submitted the patch as I am still trying to figure out how to add the test code. I have been testing it manually right now.16:18
mesteryasadoughi: I think the best advice I can give is to hop on #openstack-neutron and ask for status updates there.16:18
mesteryThe most current info is in-channel, as the gate tends to ebb and flow very fast, making IRC the best for current status.16:19
* rkukura is not sure the gate does anything very fast16:19
*** aignatov_ is now known as aignatov16:19
*** eankutse1 has quit IRC16:20
*** _ruhe is now known as ruhe16:20
*** denis_makogon has quit IRC16:20
rkukurabut /me agrees with mestery16:20
banixIt is not that things are slow, they do not get through….16:20
mesteryrkukura: :P16:20
*** abccba has quit IRC16:20
asadoughiyeah, how bad is the situation? it seems most are reacting like it's another day in the park, but some are more critical of it?16:21
asadoughii.e. should new code stop getting reviewed, produced until gate is fixed?16:22
mesteryasadoughi: My understanding is it's pretty bad, the gate needs attention on those bugs affecting it.16:22
rkukuraI think approvals are blocked at least until i-2 is cut16:23
*** xuhanp has joined #openstack-meeting-alt16:23
* mestery nods in agreement.16:24
asadoughihmm, ok, i'll continue discussion in #openstack-neutron later16:24
mesteryI think it's best if people have cycles to jump into #openstack-neutron and see where help is needed.16:24
mesteryasadoughi: Cool, thanks!16:24
mesteryOK, thanks everyone!16:24
mesteryWe'll chat again next week!16:24
mestery#endmeeting16:24
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:24
openstackMeeting ended Wed Jan 22 16:24:46 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:24
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-01-22-16.00.html16:24
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-01-22-16.00.txt16:24
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-01-22-16.00.log.html16:24
rkukurabye16:24
*** rcurran has quit IRC16:24
*** xuhanp has quit IRC16:25
*** denis_makogon has joined #openstack-meeting-alt16:25
*** nadya__ has joined #openstack-meeting-alt16:26
*** SergeyLukjanov_ is now known as SergeyLukjanov16:28
*** asomya has quit IRC16:29
*** sadasu has quit IRC16:29
*** aclark_ has joined #openstack-meeting-alt16:31
*** banix has quit IRC16:31
*** nadya__ has quit IRC16:32
*** venkatesh has joined #openstack-meeting-alt16:32
*** jomara_ has quit IRC16:33
*** bcrochet has quit IRC16:33
*** jmontemayor has joined #openstack-meeting-alt16:34
*** Barker has joined #openstack-meeting-alt16:34
*** jmontemayor has quit IRC16:34
*** AlanClark has quit IRC16:34
*** nadya__ has joined #openstack-meeting-alt16:35
*** jmontemayor has joined #openstack-meeting-alt16:35
*** malini has left #openstack-meeting-alt16:37
*** aignatov is now known as aignatov_16:42
*** ViswaV has joined #openstack-meeting-alt16:43
*** lblanchard1 has joined #openstack-meeting-alt16:44
*** lblanchard has quit IRC16:44
*** jomara has joined #openstack-meeting-alt16:45
*** bcrochet has joined #openstack-meeting-alt16:45
*** rkukura has quit IRC16:45
*** hemanthravi has quit IRC16:45
*** rkukura has joined #openstack-meeting-alt16:46
*** funzo has quit IRC16:47
*** funzo has joined #openstack-meeting-alt16:47
*** pballand has joined #openstack-meeting-alt16:47
*** michael-yu has joined #openstack-meeting-alt16:49
*** dguitarbite has quit IRC16:49
*** michael-yu has quit IRC16:50
*** bdpayne has joined #openstack-meeting-alt16:51
*** bcrochet has quit IRC16:53
*** colinmcnamara has quit IRC16:54
*** jomara has quit IRC16:55
*** mugsie has joined #openstack-meeting-alt16:55
*** rakhmerov has joined #openstack-meeting-alt16:55
*** vinod1 has joined #openstack-meeting-alt16:56
*** msisk has joined #openstack-meeting-alt16:57
*** banix has joined #openstack-meeting-alt16:58
*** sankarshan is now known as sankarshan_away16:58
*** Leonr has joined #openstack-meeting-alt16:59
*** resker has joined #openstack-meeting-alt17:00
kiall#startmeeting designate17:00
openstackMeeting started Wed Jan 22 17:00:16 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
*** artom has joined #openstack-meeting-alt17:00
artomo/17:00
kiallHey all - Who's about today?17:00
vinod1here17:00
betsyo/17:00
mugsieo/17:00
kiallCool :)17:00
eankutsehere17:00
*** jmcbride has joined #openstack-meeting-alt17:00
jmcbrideGood day folks!17:01
*** tanisdl has joined #openstack-meeting-alt17:01
kiallSo - We have no pre-prepared agenda for today, With the mini-summit so close, I've been full steam ahead on some internal work. Trying to complete a good chunk of it before travelling17:01
mugsiesame ^17:02
kiall#topic Review action items from last week17:02
*** openstack changes topic to "Review action items from last week (Meeting topic: designate)"17:02
*** rjrjr_ has joined #openstack-meeting-alt17:02
*** esker has quit IRC17:02
kiallso, we had 1 item from last .. "send email to Openstack mailing list"17:02
*** lblanchard has joined #openstack-meeting-alt17:02
kiallthat was re the mini-summit17:02
*** zane has joined #openstack-meeting-alt17:02
kialljmcbride sent that during the week17:03
kiall#link http://lists.openstack.org/pipermail/openstack-dev/2014-January/024862.html17:03
mugsieany extra interest form that jmcbride ?17:03
kialljmcbride: did you get any response privately? or via eventbrite?17:03
jmcbrideso, mostly Redhat folks are now trickling in17:04
*** rnirmal has quit IRC17:04
*** vkmc has quit IRC17:04
artomI said I'd attend via Hangouts...17:04
*** lblanchard2 has joined #openstack-meeting-alt17:04
jmcbridebut otherwise, I have not seen anything17:04
artomNot sure how that will work out...17:04
jmcbrideI'll check our current registration17:04
kiallartom: we'll be as inclusive as possible :)17:05
jmcbrideI have 10 folks registered.17:05
jmcbride1 red hatter has confirmed but not registered17:05
*** pballand has quit IRC17:05
jmcbride2 are TBD in person attendance.17:05
*** lblanchard1 has quit IRC17:06
kiallCool - So 10-13 in person?17:06
*** bcrochet has joined #openstack-meeting-alt17:06
jmcbride14 if you include me.17:06
kiallCool :) This should be fun!17:06
betsyI'm looking forward to it17:06
mugsieyup17:06
jmcbrideyep.  I'm hoping to get some tasty austin lunch staples too, so keep your fingers crossed.17:07
kiallI also see you've updated the agenda you wrote up17:07
kiall#link https://etherpad.openstack.org/p/DesignateAustinWorkshop2014-0117:07
jmcbrideYes, I was hoping to get feedback from you guys17:07
*** pballand has joined #openstack-meeting-alt17:07
kiallLooks good, I think on the morning of day 1 we can fill in the "Design sessions" topics, based on "Review Icehouse progress and start blueprint review"17:07
*** lblanchard has quit IRC17:08
jmcbridekiall: agreed17:08
kiall#action kiall find 2 hours to write mini-dns spec ahead of time -_-17:08
kiallI'm still on the fence over ^ - hence this would be a great time to discuss it ;)17:08
jmcbridekiall: that would be great - or at least refine it in your head and we can do a bit of whiteboarding17:08
jmcbridekiall: we also have some feedback for you on it17:09
artomkiall, actually, about that... you want to discuss that now?17:09
ekarlsohey folks17:09
kiallmyself and mugsie have had a few pub conversations about it, generally refining more each time, but I'm not sure I'm in a great position to articulate it correctly yet17:09
jmcbridekiall: I'm adding it to the agenda to specifically address17:10
kiallThe act of writing it down should help get the final pieces cleared up17:10
*** jomara_ has joined #openstack-meeting-alt17:10
kiallCool - Thanks Joe17:10
*** SergeyLukjanov is now known as SergeyLukjanov_17:10
jmcbride"The design sessions priorities" section is where you can add more topics you would like to address outside of icehouse17:11
kiallSo, other than HP and RAX folks, are there any other folks here today that will be there in person? or hangouts?17:11
jmcbrideIf we have time left over, we can simply start at the top of all known blueprints and prioritize/discusss17:12
rjrjr_i'll be on via hangout17:12
jmcbrideArtom will also be on hangout17:12
*** richm has joined #openstack-meeting-alt17:12
*** michael-yu has joined #openstack-meeting-alt17:12
kiallrjrjr_: Great :) So, we'll have a few via hangouts.17:12
artomIf you go out for food/beers, I'll bring my laptop to a local Irish pub ;)17:13
jmcbrideRackspace will also have our DNS operations lead in person (Jason Bratton).17:13
ekarlsoI own't be there :p, hangout though !17:13
kialljmcbride: "If we have time left over," <-- you mean today, or in person?17:13
jmcbrideekarlso, can you register so I know to expect you?17:13
jmcbrideekarlso: in person during workshop17:13
jmcbride^kiall: in person during workshop17:13
jmcbrideI'm not sure I want to take you guys to an irish pub in Austin17:14
jmcbrideYour expectations will be TOO high!17:14
kialljmcbride: perfect :) The last week, myself / mugsie / ekarlso's heads has been been in Ops mode rather than Dev mode ;)17:14
mugsiejmcbride: I learnt a long time ago about irish pubs abroad :)17:15
kiallYea - There always .. Interesting places ;)17:15
*** bcrochet has quit IRC17:15
artomHey, having been in Scotland (not the same, I know) and here in Montreal... We're doing quite OK here :)17:15
jmcbridenice, well, I'll try and find an Austin favorite that measure up...17:15
*** jomara_ has quit IRC17:15
kiallrjrjr_ / artom - Whats your TZ difference to Austin? And - Are they any topics you have a particular interest it?17:16
kiall(To try and schedule those conversations for your working hours!)17:16
artomI'm EST, so +117:16
artomReverse DNS for me, mostly17:16
artomPossible better BIND support17:16
rjrjr_MST17:16
artomIt'll depend on what I get fed in my backlog and what gets decided, if anything17:17
*** rnirmal has joined #openstack-meeting-alt17:17
*** michael-yu has quit IRC17:18
jmcbrideSweet, so you guys will be an hour in both directions timezone wise.  Will the proposed times be cool?17:18
*** vgnbkr_1 has quit IRC17:18
kiallOkay - rjrjr_ - could you add any topics (even if there listed on the page) that you're interested in to the bottom of https://etherpad.openstack.org/p/DesignateAustinWorkshop2014-0117:18
rjrjr_yes17:18
kiallartom: feel free to update what I put down for you ;)17:18
*** SergeyLukjanov_ is now known as SergeyLukjanov17:18
kiallThanks!17:19
vinod1richm:  Are there any topics that you would be interested in?17:19
artomkiall, sure, I'll keep that info fresh.17:19
jmcbriderichm - welcome, do you know if you will be able to make it (at least via hangout)17:19
*** jomara_ has joined #openstack-meeting-alt17:20
jmcbrideartom & rjrjr_ - can you send me your google usernames?17:20
*** rakhmerov has quit IRC17:21
kiallLet's take that as a yes ;) Otherwise mugsie has them17:21
rjrjr_rjrjr@cox,net17:21
rjrjr_yes17:21
jmcbrideOne other note about next week priorities, a dev from our Load Balancer team will also be attending (his name is jorge). He has some ideas about "global load balancing".17:22
kiallWorth mentioning - next weeks Wednesday IRC meeting will obviously be cancelled, as we'll have just wrapped up the few days in person .. Just making sure that's clear :)17:23
*** bcrochet has joined #openstack-meeting-alt17:23
*** aclark_ has quit IRC17:23
kialljmcbride: excellent :)17:23
*** chandankumar_ has quit IRC17:24
kiallAnyway - So, Since we have no pre-prepared agenda today, if anyone has anything to bring up, or that they want to discuss, jump in at any time please :)17:24
*** jmontemayor has quit IRC17:24
artomWell, re mini-dns...17:24
*** colinmcnamara has joined #openstack-meeting-alt17:24
*** tanisdl has quit IRC17:24
artomOr you want to save that for the workshop?17:25
kiallbetsy: you're Blacklisted Domains review, is that ready to look over? Last time i looked, you had left a comment saying "not ready yet" :)17:25
betsyI've got some changes that I'll submit today and that should be it17:25
betsySorry, but I've been ill17:25
kiallartom: I think we need to get that written up, it's a complex idea with lots of tradeoffs.. And I know I personally still haven't quite got the idea clear in my head17:26
*** tanisdl has joined #openstack-meeting-alt17:26
kiallbetsy: unacceptable ;)17:26
betsy:)17:26
kiallNo worries - I just didn't want it to sit there ready for review for ages without getting looked at ;)17:26
kiallOkay - Well, If nobody has anything else, we can call it a day?17:27
*** Barker has quit IRC17:27
jmcbrideyep, have a great week, see ya'll in Austin!17:27
kialljmcbride: BTW17:28
eankutsesee you17:28
artomkiall, well, I just have... an "alternative"?17:28
*** SergeyLukjanov is now known as SergeyLukjanov_17:28
artomNot comments about the idea itself.17:28
*** vkmc has joined #openstack-meeting-alt17:28
*** vkmc has quit IRC17:28
*** vkmc has joined #openstack-meeting-alt17:28
kialljmcbride: Myself and mugsie be in Austin on Sunday, and staying in the Radission .. Just FYI17:28
kiallartom: an alternative?17:29
*** jmontemayor has joined #openstack-meeting-alt17:29
artomWell, instead of implementing mini-dns, the same effect can be achieved by mandating the multi backend with a PowerDNS master.17:29
jmcbridekiall: sweet, I emailed all attendees my contact info.  I might be able to slip away for dinner/drinks Sunday, so let me know.17:29
*** chandankumar_ has joined #openstack-meeting-alt17:29
kialljmcbride: depends how tried we are ;) Land at like 6am or something.17:30
*** yamahata has joined #openstack-meeting-alt17:31
kiallartom: That's certainly an option, but has some drawbacks in terms of the potential phase 2 features..17:31
kiallInbound AXFR, RFC / nsupdate Dynamic DNS, anything that modifies the content of the zone, would be really really awkward to fit into that model17:31
*** Barker has joined #openstack-meeting-alt17:32
artomDo we need to allow zone modification by means other than the API?17:32
*** pballand has quit IRC17:32
kiallI think we do, and I know rjrjr_ would agree ;) one of the pieces he discussed in the past was accepting RFC / nsupdate dynamic DNS updates17:33
eankutseartom: we should not rule out use of nsupdate17:33
mugsieafik redhat openshift needs it as well17:33
jmcbridekiall/artom: regarding mini-DNS, I think it sounds feasible, but I think it will only work for use cases in which either zone transfers or dynamic dns protocol is supported.17:33
kiallRedHat I'm sure are interested in that too - OpenShift / Origin requires a a RFC style dynamic DNS server17:33
artomAnd so mini-dns would implement said RFC-style server?17:34
artomAnd reflect any changes it receives via not-API in Designate's state?17:34
kialljmcbride: absolutely - this would never be a target of end user queries - that would be an epic failure waiting to happen IMHO ;)17:34
kiallartom: yea, so, RFC dynamic DNS is actually quite simple to impelement (with the exception of transactional / atomic commits of whole changeset - but that's another topic to solve independently)17:35
jmcbridekiall: agreed. My comment was targetted at how to get zone data transferred from master to slaves.17:35
kiallWhen I say simple - I mean, simple once you have the other pieces in place17:36
jmcbridekiall: I think we will benefit from that 2 hour homework assignment you gave yourself…17:36
kialljmcbride: and lots of RFC reading ;)17:37
*** DennyZhang has quit IRC17:37
jmcbridekiall: before bed is the best time for that17:37
kiallYou'll never get past the first sentence that way17:37
*** Duane_ has joined #openstack-meeting-alt17:38
rjrjr_our mini-dns also needs to respond to refresh requests from slaves17:38
kiallartom: Anyway - I know I see huge advantages by being able to alter the data we have via the standard DNS mechanisms, I think supporting that is key if we go with the "mini-dns" suggestion , or the enforce powerdns alternative route you suggested17:38
*** kalebpomeroy has joined #openstack-meeting-alt17:38
eankutseKiall: regarding RFC's that you plan to read17:39
eankutsecan you tell us which ones you plan to look at?17:39
kialleankutse: I meant you guys ;) I've read them all17:39
eankutseI am interested as well17:39
eankutse:-)17:39
eankutsesleep reading RFC's?17:39
kiallrfc1034, rfc1035, rfc2181 are some the main ones17:40
eankutsecool17:40
artomkiall, was just throwing the alternative out there. It seemed like mini-dns was reimplementing existing stuff for benefits that were unclear to me. But if we want storage <-> backend "bidirection" communications, I don't think we have the choice...17:40
kiall2136 is nsupdate / RFC style dynamic DNS17:40
artomUnless we start doing funky stuff like polling the PowerDNS db to import changes into storage...17:41
kiallEhh - And I'm sure theres 100 others that aren't coming to mind right now17:41
eankutseThat's a good start17:41
eankutsethere'll be references from those to others17:41
kiallartom: Well, powerDNS supports custom backends, lua based from memory, but we enter pretty dangerous territory there with ever becoming core OpenStack ;)17:42
artomThat's a whole other level of meta right there...17:42
kiallAnd - Choosing PowerDNS as a core piece, as much as I like that idea, would likely be a roadblock for us over time as people have their favourite17:42
artom"We put a backend in your backend so you can DNS while you DNS" ;)17:42
*** markwash has joined #openstack-meeting-alt17:43
kiallartom: hah :) Yep17:43
*** venkatesh has quit IRC17:43
jmcbrideWe should have a blueprint for the idea of supporting bidirectional updates (e.g. using dynamic DNS to update zones).17:43
kialloh eankutse .. rfc2845 would be another core piece.. providing a method of identification of users making queries etc to this17:44
jmcbridehttp://i.imgur.com/kQ7DHB4.jpg17:45
kialllol17:45
artomjmcbride, I didn't think anyone would actually do that :D17:45
artomBravo.17:45
*** luqas has quit IRC17:45
*** hub_cap has joined #openstack-meeting-alt17:45
kiallartom: CloudFlare was (is?) based on PowerDNS and a custom backend for it ;)17:46
kiallOkay - Well, I think it's time to wrap this up and call it a day :)17:46
eankutseKiall: thx. Keep them coming :-)17:46
kiallhub_cap got here, so .. everyone leave please.17:46
kiall;)17:46
hub_capYEA BOI17:46
*** julienvey has left #openstack-meeting-alt17:46
hub_caphi kiall ;) i totally saw a half past / half 30 thing on tv the other day17:46
artomHey, we got 15 more minutes officially, I intend to fill every last second with more memes :D17:46
kiallOkay - Thanks all :) Cya next week !17:47
betsycya17:47
kiall#endmeeting17:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:47
openstackMeeting ended Wed Jan 22 17:47:18 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-01-22-17.00.html17:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-01-22-17.00.txt17:47
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-01-22-17.00.log.html17:47
kiallhub_cap: seriously? still going on about that!17:47
*** rjrjr_ has quit IRC17:48
*** jcru has joined #openstack-meeting-alt17:48
*** grapex has joined #openstack-meeting-alt17:48
*** mugsie has left #openstack-meeting-alt17:48
jmcbridehub_cap: And here is my last comment for the day http://i.imgur.com/LmcRGPW.jpg17:49
*** jimbobhickville1 has joined #openstack-meeting-alt17:50
*** cp16net has joined #openstack-meeting-alt17:50
*** ashestakov has joined #openstack-meeting-alt17:50
*** rakhmerov has joined #openstack-meeting-alt17:51
*** DennyZhang has joined #openstack-meeting-alt17:55
hub_capkiall: hey!17:57
hub_caplol jmcbride ;)17:57
*** vinod1 has left #openstack-meeting-alt17:57
kiallhub_cap: hows things? Too cold to work on the porch in the boxers these days? ;)17:58
*** SlickNik has joined #openstack-meeting-alt17:58
hub_capmost def. its like 50s17:58
hub_capim in the back bedroom office17:58
*** jmontemayor has quit IRC17:58
SlickNikhello there17:58
*** zane has quit IRC17:59
kiallhub_cap: it's colder here ;) 44 according to google17:59
*** jmontemayor has joined #openstack-meeting-alt17:59
hub_capF/C?17:59
*** vgnbkr_1 has joined #openstack-meeting-alt18:00
hub_cap#startmeeting trove18:00
*** imsplitbit has joined #openstack-meeting-alt18:00
openstackMeeting started Wed Jan 22 18:00:23 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:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: trove)"18:00
ashestakovhi all18:00
openstackThe meeting name has been set to 'trove'18:00
imsplitbito/18:00
SlickNikhere18:00
kiallhub_cap: Ireland has never seen 44C ;)18:00
kevinconwayo/18:00
* kiall gets out of the way18:00
glucaso/18:00
*** esp has joined #openstack-meeting-alt18:01
*** safchain has quit IRC18:01
grapexo/18:01
espo/18:01
abramleyo/18:01
*** seanGossard has joined #openstack-meeting-alt18:01
*** datsun180b has joined #openstack-meeting-alt18:01
*** robertmyers has joined #openstack-meeting-alt18:01
robertmyerso/18:01
hub_capok so lets get this party started18:01
kanzaroso/18:01
cweido/18:01
*** mat-lowe_ has joined #openstack-meeting-alt18:01
datsun180bis the party over here18:01
hub_cap#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting18:01
cp16neto/18:01
hub_capaye datsun180b18:01
esmuteo/18:02
datsun180bthat is a serious query, my party locator is malfunctioning18:02
hub_capLOL18:02
hub_capok so this is another small meeting heh18:02
imsplitbitno datsun180b the party is over there18:02
*** garyduan has joined #openstack-meeting-alt18:02
hub_capso, lets get on w/ the first item (im switchign the agenda)18:02
hub_cap#topic kill tha xmls18:03
*** openstack changes topic to "kill tha xmls (Meeting topic: trove)"18:03
SlickNik+118:03
* grapex screams in terror!18:03
hub_capso, the TC has said that its a-ok to remove from future apis18:03
SlickNiklol@grapex18:03
jimbobhickville1rip that sucka out18:03
hub_capand told trove that we can/should remove before our first integrated release18:03
*** arnaud has joined #openstack-meeting-alt18:03
mattgriffino/18:03
*** arnaud__ has joined #openstack-meeting-alt18:03
*** amrith has joined #openstack-meeting-alt18:04
esmutegrapex: i thought you'd be relieved18:04
*** mpolanco has joined #openstack-meeting-alt18:04
grapexhub_cap: How long does that give us again?18:04
hub_capok so we are going to have to let this sit for about a month i think18:04
hub_capitll be beore feature freezer18:04
hub_caplol18:04
hub_capfreeze18:04
SlickNik#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule18:05
SlickNikfor all your release date needs.18:05
grapexI'm down for removing it- but we think maybe one or even two people at Rax use it now, so its a bit tricky.18:05
hub_capbut id like to give any company who is removing this time to call peoples :)18:05
grapexhub_cap: Cool18:05
*** saurabhs has joined #openstack-meeting-alt18:06
*** pballand has joined #openstack-meeting-alt18:06
hub_capso we have no problems w/ this then?18:06
datsun180bburn xml to the ground18:07
datsun180bsalt the earth18:07
hub_capotehr than making sure we give companies time to tell that guy 2003 called and wants their xml back?18:07
datsun180bleave a sign18:07
hub_capdatsun180b: nice touch, leaving a sign18:07
kevinconwaydatsun180b: are you saying xml is the salt of the earth?18:07
hub_capoh geez18:07
hub_capkevinconway: startrd, lets move18:07
SlickNiklol18:07
hub_cap#topic conductor message sync strategies18:08
*** openstack changes topic to "conductor message sync strategies (Meeting topic: trove)"18:08
datsun180byes hello18:08
datsun180bso tim noticed before our holiday conductor introduced a potential problem18:08
*** NehaV has joined #openstack-meeting-alt18:08
datsun180bthat is, syncing statuses of instances and backups is no longer a database update, but a message-in-a-bottle rpc cast, so we could find ourselves with an instance in one state18:09
datsun180bbut conductor might be bogged down and so the db would be out of date18:09
*** demorris has joined #openstack-meeting-alt18:09
datsun180band if messages can get to conductor out of order, things can get even worse, so what we need to do is make sure that conductor makes its updates in the right order, especially in the face of multiple conductor workers18:10
datsun180bi've got a pull request that's halfway there, a sent_at field compared to the updated field of the tables, but i can do one better because the guest and host's timekeeping could skew and cause problems still18:10
datsun180bhub_cap suggested that i ask nova's conductor peeps for their sync strategy, but otherwise i'd add a table that only conductor uses, to pair (instance, message) -> timestamp from guest18:11
datsun180bis this thing on?18:11
SlickNikYup, good call on this grapex/datsun180b.18:11
hub_capwe are listening18:11
SlickNikyup, listening18:11
hub_capbasically yer saying good stuff18:11
datsun180bokay recap: 1. i add a new table only conductor uses18:11
hub_capso only cweid will argue w u18:12
kevinconwayyes, listening18:12
*** yogesh has joined #openstack-meeting-alt18:12
datsun180b2. chances are this is old territory long since covered by nova and they have a better idea18:12
vipulafaik nova is async when it sends host updates18:12
*** jmcbride has quit IRC18:12
datsun180bi don't think making a guest agent wait until conductor confirms status updates is the right way to go, though18:13
hub_capyes vipul but how does it handle the potential race between a customer call and a guest update :)18:13
*** mat-lowe_ is now known as mat-lowery18:13
hub_capbut datsun180b will hit us up w/ a review and/or updates from the nova crew18:14
vipulhub_cap: Yea, that's an issue, but we may want to consider handling it at the guest..18:14
datsun180bporque no los dos?18:14
vipulthe guest doesn't look at its own state18:14
hub_capvipul: yea i want to make sure we solve that in some way, and datsun180b has a handle on it18:14
datsun180bi think the best we can do is ask the guest what time it thinks it is every time it sends a message18:14
kevinconwaydatsun180b: +118:15
datsun180band for conductor to keep a ledger to at least keep each instance's story straight, at least self-consistent18:15
*** michael-yu has joined #openstack-meeting-alt18:15
vipuldatsun180b: cool that'll solve the out of order issue18:15
*** michael-yu has quit IRC18:16
datsun180bokay, so #action datsun go add a conductor sent_at table and #action datsun go talk to nova about conductor ?18:16
*** michael-yu has joined #openstack-meeting-alt18:16
*** derekh has quit IRC18:16
vipulsounds good datsun180b18:17
hub_capdatsun180b: u gotta start w/ #action18:17
datsun180b#action datsun180b add sent_at table for conductor to sync messages from guests18:17
SlickNiksounds good to me.18:17
*** gokrokve has joined #openstack-meeting-alt18:17
hub_capmoving on18:17
datsun180b#action datsun180b talk to nova team about their conductor sync strategy18:17
hub_cap#topic tempest work18:18
*** openstack changes topic to "tempest work (Meeting topic: trove)"18:18
datsun180bthank you all18:18
SlickNikThe couple of devstack-gate reviews that I had are taking a while to get merged.18:18
SlickNikI haven't been bothering the CI team too much about it, since they're crazy busy dealing with zuul/gate issues at the moment.18:19
hub_capso SlickNik, do you anticipate working on the image caching stuff next?18:19
SlickNikHopefully that'll change once i2 gets cut.18:19
kevinconwayso by looking at that etherpad, the next step for tempest trove is to write some API acceptance tests. is that correct?18:19
SlickNikYes, kevinconway. That is correct.18:20
SlickNikRight now, to test it out, you can pull the devstack-gate changes from gerrit.18:20
*** SergeyLukjanov_ is now known as SergeyLukjanov18:21
kevinconwaywill we be able to run the acceptance tests against different data stores as a part of tempest?18:21
vipulThe guest related tests can't go in until the image stuff is figured out.. is that correct?18:21
grapexWas any Trove specific code for Tempest written during the time I dropped off the Earth?18:21
SlickNikkevinconway: Eventually. We're starting of with just mysql, but the end goal is to port all of what is in trove-integration to Tempest.18:21
*** rumale has joined #openstack-meeting-alt18:22
grapexWe could use Fake Mode while we wrote more tests.18:22
grapexThat way we could write tests even if the image stuff isn't set up yet.18:22
SlickNikhub_cap: Yes, I'm working on the image caching work in parallel.18:22
hub_capSlickNik: id prefer to see the initial goal to be make devstac/tempest do what trove-integration does now18:22
hub_capcool SlickNik18:22
grapexIf we use Fake Mode, there's no reason we couldn't try porting some of the more complex test cases right away.18:23
*** rakhmerov has quit IRC18:23
SlickNikgrapex: I started writing a couple of 'service' pieces for trove for the flavors API. I'll push a patch set up within the next couple of days.18:24
vipuldoes Tempest have a fake mode? or is it focused purely on end to end18:24
grapexvipul: If it can hit various environments that shouldn't matter.18:24
grapexWe can start a fake mode daemon and hit that18:24
SlickNikvipul: Looking at other components, it seems like it's entirely end-to-end.18:24
kevinconwaywhere can i read more about tempest? i feel like there's something i don't understand18:24
hub_capkevinconway: wiki.o.o/Tempest would be my guess18:25
SlickNikgrapex: In order to do that we'd have to be able to enable a fake mode demon in devstack, I think. Might be something worth looking into.18:25
SlickNikkevinconway: hang on a sec.18:26
*** rakhmerov has joined #openstack-meeting-alt18:26
SlickNik#link http://docs.openstack.org/developer/tempest/18:26
hub_caplets start w/ real mode tests :)18:26
grapexSlickNik: I think it would be worth it. In fact, it wouldn't be a bad idea to test via Fake Mode in CI- there's plenty of stuff the daemonized version can find that the version we run in Tox can't quite see.18:26
*** nadya__ has quit IRC18:26
hub_capthen lets try to find a way to capitalize on the "fakes" that sdague talked about in our summit talk18:26
kevinconwaybut to clarify, our plan is to rewrite all of our tests using tempest?18:26
grapexhub_cap: I think we should do them in parallel. That way we can know things aren't inflexible.18:26
hub_capheh, im not sure SlickNik has the bandwidth for that ;)18:27
grapexhub_cap: I think that was an idea and not existing work.18:27
SlickNikhub_cap / grapex: Yeah my approach was to start with the real mode, and add the fake mode later once we have built some social capital with the tempest folks.18:27
*** bdpayne has quit IRC18:28
SlickNikThere might be some initial push back, since this (fake mode) is different from what a other OS teams are doing.18:28
grapexSlickNik: Ok, you have to start somewhere. However in my experience fake mode is working now with the int tests that run with Tox on each check in, and it'll be easier to write the tests that way since the feedback will be so quick.18:28
grapexSlickNik: Ok- maybe just consider it as a tool you can use while writing tests.18:29
SlickNikgrapex: I hear you. Let's look at that once we have some set of real mode tests (even if it's some basic ones).18:29
hub_capgrapex: i suspect that might be much work w/ tempest internals to get that all working18:29
*** Duane_ has quit IRC18:29
*** Duane_ has joined #openstack-meeting-alt18:30
SlickNikgrapex: I feel it's a worthwhile exercise to do things the tempest way (initially at least) so that we can learn some of the ropes as well, since it does have some new ways of dealing with things.18:30
*** NehaV has left #openstack-meeting-alt18:30
grapexhub_cap: I hope not- my understanding is it can run against any environment.18:31
*** NehaV has joined #openstack-meeting-alt18:31
grapexBut you guys are probably right in that it would be easier to start with real.18:31
SlickNikAnyhow, some of you wanted to start looking into some of these tests as well (denis, and some other globallogic and mirantis folks)18:32
*** tanisdl has quit IRC18:32
*** zane has joined #openstack-meeting-alt18:32
hub_capso we done w/ this topic?18:32
SlickNikSo I've just put up a quick etherpad to indicate what pieces each of us might be working on.18:32
*** harlowja_away is now known as harlowja18:32
*** artom has left #openstack-meeting-alt18:32
grapexOk, let's start with real. I just want us to try to stay open minded. I'd hate it if the "canonical" Trove tests became something I couldn't run or play around with unless I had a fleet of servers at my finger tips.18:32
SlickNikSo feel free to update if you're starting to look at a piece.18:33
SlickNik#link https://etherpad.openstack.org/p/trove-tempest-items18:33
hub_capgrapex: right now itll be no more than the current tests18:33
SlickNikAlso feel free to ping me in openstack-trove if you have any questions regarding any of this.18:34
hub_capok so movin on18:34
SlickNikAnd with that I'm good to move on.18:34
grapexOk.18:34
*** nadya__ has joined #openstack-meeting-alt18:34
grapexThanks SlickNik!18:34
SlickNikanytime, np.18:34
*** Duane_ has quit IRC18:35
hub_cap#topic datastore mgmt api18:35
*** openstack changes topic to "datastore mgmt api (Meeting topic: trove)"18:35
hub_capashestakov: tag18:35
*** nadya__ has quit IRC18:35
ashestakovi want propose mgmt API spec for datastores18:36
ashestakovto move create/update datastores/versions from trove-manage to API18:36
ashestakovthis is my gist https://gist.github.com/andreyshestakov/855793518:37
ashestakovpls look18:37
*** julienvey_ has joined #openstack-meeting-alt18:38
jimbobhickville1I guess I don't have enough context to know why you would want to do that18:38
hub_capok anything else to that ashestakov ?18:38
*** noslzzp has quit IRC18:38
robertmyersashestakov: should those urls be /mgmt/blah18:38
espashestakov: so this api would allow manipulating the datastore on a guest instance without tearing down the instance?18:39
hub_cap+1 robertmyers18:39
*** noslzzp has joined #openstack-meeting-alt18:39
SlickNikesp: more like the datastores in the db, I would think.18:39
*** ruhe is now known as _ruhe18:39
ashestakovesp: no guest instance, just create/update18:39
SlickNikto updated the datastore instances in the models.18:39
SlickNik+1 on /mgmt (robertmyers' suggestion)18:40
ashestakovi saw same impl for configuration-groups18:40
espk, I think I get it18:40
ashestakovwithout /mgmt18:40
*** eankutse has quit IRC18:40
robertmyersconfigurations is for the user18:40
robertmyersnot an admin18:41
robertmyersonly admins will create datastores18:41
ashestakovok, just /mgmt/datastores/... ?18:41
jimbobhickville1isn't /mgmt stuff only supposed to be exposed via trove-manage or did I misunderstand that?18:41
robertmyersyes18:41
hub_capjimbobhickville1: naw18:41
robertmyersjimbobhickville1: well, no18:41
hub_capu can expose via the cli too18:41
vipuli think mgmt stuff should be in trove cli18:41
hub_capyes18:42
hub_cap"initial setup" stuff should be in trove-manage18:42
vipuli think amcrn was working on that last time we met18:42
jimbobhickville1ok, cool, that's timely advice since I was about to do the wrong thing18:42
hub_capand "tweaking" stuff (like adding a datstore) shoudl be in the mgmt api18:42
*** michael-yu has left #openstack-meeting-alt18:43
SlickNikanything else to add, ashestakov?18:44
ashestakovany comments except /mgmt ?18:44
ashestakovshould troveclient has commands for mgmt api?18:44
robertmyersashestakov: yes, it use to18:45
ashestakovi didnt see any mgmt commands in troveclient18:45
*** michael-yu has joined #openstack-meeting-alt18:45
ashestakovonly in trove-mgmt-cli while ago18:45
hub_capashestakov: i removed them cuz our mgmt api is mostly busted18:45
*** Ranjitha has joined #openstack-meeting-alt18:45
hub_capand had few if any tests added18:45
datsun180bthanks for the vote of confidence, technical leadership!18:46
hub_caphahahaahah18:46
SlickNikashestakov: maybe lines 36-37 should be:18:46
SlickNikCreate version18:46
SlickNikPOST /datastores/{id}/versions18:46
ashestakovSlickNik: why /versions?18:47
kevinconwaySlickNik: i agree18:47
SlickNikreally a nitpick, but it seems like you'd want your URI to indicate that it was a create operation on a version.18:48
*** tanisdl has joined #openstack-meeting-alt18:48
SlickNika POST to /datastores/{id} could be for any operation really, and you'd have to peek into the body to see that it was a version create.18:48
ashestakov /datastores/id already means versions, like in GET18:48
kevinconwayGET /datastores/<id> should give you the data store18:49
kevinconwaywhy would it give you versions instead?18:49
*** tanisdl has quit IRC18:49
ashestakovoops18:50
*** jprovazn has joined #openstack-meeting-alt18:50
ashestakovok, i agree vit /versions18:50
ashestakovany other comments? i have one more point to discuss18:51
SlickNikOkay, thanks.18:51
*** jcoufal has joined #openstack-meeting-alt18:52
SlickNikI think we're good.18:52
ashestakovcool18:52
SlickNikLet's speed things up a bit to leave some time for open discussion.18:53
SlickNikSo go ashestakov.18:53
hub_cap++18:53
*** zane has left #openstack-meeting-alt18:53
hub_capmoving on18:53
hub_cap#topic Datastore versions migrations/upgrades18:53
*** openstack changes topic to "Datastore versions migrations/upgrades (Meeting topic: trove)"18:53
ashestakovlets look here https://gist.github.com/andreyshestakov/855930918:53
kevinconwayoh no18:53
kevinconwaybig topic for 7 minutes18:53
ashestakovthis is API for migrations18:53
ashestakovthis is base on approach suggested by amcrn https://gist.github.com/amcrn/dfd493200fcdfdb61a2318:54
kevinconwayhow are we separating upgrades from migrations?18:54
*** julim has quit IRC18:54
vipulwe should probably tackle upgrades first?18:55
kevinconwayare we defining upgrades to be in place and migrations require a new instance?18:55
SlickNikvipul: agreed18:55
ashestakovNote: Chose the term migration over upgrade because the latter indirectly suggests that downgrades (ex: from 5.6 to 5.5) and/or datastore transitions (ex: from MySQL to Postgres) are not possible.18:55
vipulthat's what my understanding was kevinconway18:55
jimbobhickville1I want to migrate from mysql to redis, go!18:56
SlickNikashestakov: I don't know if migration is the right term. It implies it's not in place.18:56
kevinconwayjimbobhickville1: i think that would be possible with this api if you define a migration manager18:56
jimbobhickville1are we going to then have to have some way to define possible migration paths so a customer can know what's a valid path or not?18:57
SlickNikalthough, now that I think of it, it doesn't necessarily have to be (it's just used that way in OS, so it's loaded).18:57
*** julim has joined #openstack-meeting-alt18:57
*** sarob has joined #openstack-meeting-alt18:57
*** DinaBelova is now known as DinaBelova_18:57
*** sarob has quit IRC18:58
kevinconwayjimbobhickville1: yes, with ashestakov's api you would define valid migration paths18:58
jimbobhickville1cool18:58
kevinconway#link https://gist.github.com/andreyshestakov/855930918:58
kevinconwaythat's the gist he posted18:58
jimbobhickville1I should probably read that then18:58
kevinconwayashestakov: yeah i think you need to ML this topic18:59
hub_cap+118:59
kevinconwayi'm sure you'll get lots of advice18:59
SlickNikI think we might need more time to read/digest this.18:59
SlickNikSo +1 for ML18:59
hub_capthis is big18:59
kevinconwaylets hope migrations isn't the next users18:59
ashestakovok, ill answer in ML18:59
hub_capok so no open discussion19:00
hub_cap#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Wed Jan 22 19:00:09 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-22-18.00.html19:00
*** nati_ueno has joined #openstack-meeting-alt19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-01-22-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-01-22-18.00.log.html19:00
*** imsplitbit has left #openstack-meeting-alt19:00
datsun180bkevinconway: i might like to migrate my users from one datastore type to another19:00
hub_capgoto trove for open discussion19:00
*** datsun180b has left #openstack-meeting-alt19:00
SlickNikokay, thanks all!19:00
*** robertmyers has left #openstack-meeting-alt19:00
*** nwidell has joined #openstack-meeting-alt19:01
*** _ruhe is now known as ruhe19:01
*** ashestakov has left #openstack-meeting-alt19:01
*** rakhmerov has quit IRC19:03
*** amrith has quit IRC19:03
*** mpolanco has left #openstack-meeting-alt19:03
*** sarob has joined #openstack-meeting-alt19:03
*** colinmcnamara has quit IRC19:04
*** NehaV has quit IRC19:05
*** NehaV has joined #openstack-meeting-alt19:05
*** julienvey_ has quit IRC19:06
*** rakhmerov has joined #openstack-meeting-alt19:07
*** jmontemayor has quit IRC19:08
*** jmontemayor_ has joined #openstack-meeting-alt19:08
*** jmontemayor_ has quit IRC19:08
*** jmontemayor has joined #openstack-meeting-alt19:09
*** rakhmerov has quit IRC19:10
*** jmontemayor has quit IRC19:10
*** jimbobhickville1 has left #openstack-meeting-alt19:13
*** jmontemayor has joined #openstack-meeting-alt19:14
*** banix has quit IRC19:15
*** nadya__ has joined #openstack-meeting-alt19:16
*** vipul is now known as vipul-away19:17
*** nwidell has quit IRC19:18
*** esp has left #openstack-meeting-alt19:18
*** banix has joined #openstack-meeting-alt19:18
*** nwidell has joined #openstack-meeting-alt19:19
*** eankutse has joined #openstack-meeting-alt19:20
*** jprovazn has quit IRC19:22
*** vipul-away is now known as vipul19:23
*** johnthetubaguy has quit IRC19:28
*** jmcbride has joined #openstack-meeting-alt19:29
*** pballand has quit IRC19:30
*** nadya__ has quit IRC19:30
*** jmcbride has quit IRC19:31
*** jmcbride has joined #openstack-meeting-alt19:31
*** cp16net has left #openstack-meeting-alt19:34
*** pballand has joined #openstack-meeting-alt19:35
*** sarob has quit IRC19:38
*** sarob has joined #openstack-meeting-alt19:38
*** jcoufal has quit IRC19:41
*** sarob has quit IRC19:43
*** julienvey_ has joined #openstack-meeting-alt19:46
*** nwidell has quit IRC19:47
*** julienvey_ has quit IRC19:48
*** nwidell has joined #openstack-meeting-alt19:50
*** tanisdl has joined #openstack-meeting-alt19:51
*** DennyZha` has joined #openstack-meeting-alt19:54
*** SlickNik has left #openstack-meeting-alt19:55
*** msisk has left #openstack-meeting-alt19:55
*** DennyZhang has quit IRC19:56
*** NikitaKonovalov_ is now known as NikitaKonovalov19:57
*** DennyZha` has quit IRC20:00
*** obondarev_ has quit IRC20:02
*** mat-lowery has quit IRC20:03
*** Duane_ has joined #openstack-meeting-alt20:03
*** DinaBelova_ is now known as DinaBelova20:04
*** jmcbride has quit IRC20:05
*** MarkAtwood has joined #openstack-meeting-alt20:05
*** yamahata has quit IRC20:05
*** jmcbride has joined #openstack-meeting-alt20:11
*** derekh has joined #openstack-meeting-alt20:11
*** vipul is now known as vipul-away20:19
*** vipul-away is now known as vipul20:19
*** safchain has joined #openstack-meeting-alt20:20
*** safchain has quit IRC20:20
*** kalebpomeroy has left #openstack-meeting-alt20:20
*** jmcbride1 has joined #openstack-meeting-alt20:23
*** jmcbride has quit IRC20:23
*** nwidell has quit IRC20:24
*** SergeyLukjanov is now known as SergeyLukjanov_20:28
*** sarob has joined #openstack-meeting-alt20:30
*** Duane_ has quit IRC20:30
*** Duane_ has joined #openstack-meeting-alt20:30
*** akuznetsov has quit IRC20:31
*** sarob has quit IRC20:31
*** jmcbride1 has left #openstack-meeting-alt20:31
*** kebray_ has quit IRC20:34
*** vipul is now known as vipul-away20:34
*** Duane_ has quit IRC20:35
*** Duane_ has joined #openstack-meeting-alt20:36
*** BrianB__ has quit IRC20:36
*** BrianB_ has quit IRC20:37
*** DinaBelova is now known as DinaBelova_20:37
*** NikitaKonovalov is now known as NikitaKonovalov_20:42
*** jecarey has quit IRC20:44
*** rumale has quit IRC20:44
*** ijw has quit IRC20:46
*** NikitaKonovalov_ is now known as NikitaKonovalov20:47
*** julienvey_ has joined #openstack-meeting-alt20:48
*** kebray_ has joined #openstack-meeting-alt20:49
*** sarob has joined #openstack-meeting-alt20:50
*** vipul-away is now known as vipul20:51
*** SergeyLukjanov_ is now known as SergeyLukjanov20:51
*** demorris has quit IRC20:53
*** Duane_ has quit IRC20:54
*** demorris has joined #openstack-meeting-alt20:54
*** julienvey_ has quit IRC20:54
*** julienvey__ has joined #openstack-meeting-alt20:54
*** Duane_ has joined #openstack-meeting-alt20:54
*** Duane__ has joined #openstack-meeting-alt20:55
*** sarob has quit IRC20:55
*** NikitaKonovalov is now known as NikitaKonovalov_20:57
*** Duane_ has quit IRC20:58
*** DennyZhang has joined #openstack-meeting-alt20:59
*** sarob has joined #openstack-meeting-alt20:59
*** SergeyLukjanov is now known as SergeyLukjanov_21:02
*** ViswaV has quit IRC21:02
*** jmontemayor has quit IRC21:04
*** Barker has quit IRC21:04
*** demorris has quit IRC21:06
*** Duane_ has joined #openstack-meeting-alt21:06
*** DennyZhang has quit IRC21:06
*** saurabhs has quit IRC21:06
*** DennyZhang has joined #openstack-meeting-alt21:07
*** saurabhs has joined #openstack-meeting-alt21:07
*** DennyZhang has quit IRC21:08
*** DennyZhang has joined #openstack-meeting-alt21:08
*** jmontemayor has joined #openstack-meeting-alt21:09
*** Duane__ has quit IRC21:09
*** ijw has joined #openstack-meeting-alt21:11
*** vkmc has quit IRC21:11
*** kebray_ has quit IRC21:12
*** ijw has quit IRC21:17
*** ijw has joined #openstack-meeting-alt21:17
*** dprince has quit IRC21:19
*** demorris has joined #openstack-meeting-alt21:22
*** lblanchard2 has quit IRC21:22
*** ruhe is now known as _ruhe21:23
*** lblanchard has joined #openstack-meeting-alt21:25
*** Barker has joined #openstack-meeting-alt21:31
*** Duane__ has joined #openstack-meeting-alt21:32
*** jecarey has joined #openstack-meeting-alt21:32
*** DennyZhang has quit IRC21:34
*** DennyZhang has joined #openstack-meeting-alt21:35
*** Duane_ has quit IRC21:36
*** DennyZhang has quit IRC21:45
*** DennyZhang has joined #openstack-meeting-alt21:46
*** Duane_ has joined #openstack-meeting-alt21:48
*** rakhmerov has joined #openstack-meeting-alt21:49
*** sarob has quit IRC21:50
*** sarob has joined #openstack-meeting-alt21:50
*** NehaV has quit IRC21:50
*** Duane__ has quit IRC21:51
*** ViswaV has joined #openstack-meeting-alt21:51
*** ViswaV has quit IRC21:53
*** DennyZhang has quit IRC21:53
*** ViswaV has joined #openstack-meeting-alt21:53
*** DennyZhang has joined #openstack-meeting-alt21:53
*** DennyZhang has quit IRC21:54
*** DennyZhang has joined #openstack-meeting-alt21:54
*** sarob has quit IRC21:55
*** doug_shelley66 has quit IRC22:01
*** derekh has quit IRC22:03
*** david-lyle has quit IRC22:06
*** david-lyle has joined #openstack-meeting-alt22:06
*** sarob has joined #openstack-meeting-alt22:07
*** seanGossard has quit IRC22:09
*** Duane__ has joined #openstack-meeting-alt22:09
*** garyduan has quit IRC22:11
*** DennyZhang has quit IRC22:11
*** garyduan has joined #openstack-meeting-alt22:12
*** Duane_ has quit IRC22:13
*** sarob has quit IRC22:18
*** lblanchard has quit IRC22:26
*** jdob has quit IRC22:27
*** julienvey__ has quit IRC22:28
*** sarob has joined #openstack-meeting-alt22:29
*** Duane_ has joined #openstack-meeting-alt22:30
*** nadya__ has joined #openstack-meeting-alt22:31
*** jergerber has joined #openstack-meeting-alt22:31
*** Duane__ has quit IRC22:34
*** Barker has quit IRC22:35
*** nadya__ has quit IRC22:35
*** NehaV has joined #openstack-meeting-alt22:42
*** Duane__ has joined #openstack-meeting-alt22:42
*** doug_shelley66 has joined #openstack-meeting-alt22:45
*** Duane_ has quit IRC22:46
*** resker has quit IRC22:46
*** demorris has quit IRC22:52
*** Duane__ has quit IRC22:54
*** Duane_ has joined #openstack-meeting-alt22:54
*** jtomasek has quit IRC22:55
*** NehaV has quit IRC22:58
*** Duane_ has quit IRC22:58
*** kevinconway has quit IRC23:05
*** eankutse has quit IRC23:07
*** saurabhs has quit IRC23:12
*** Barker has joined #openstack-meeting-alt23:13
*** tanisdl has quit IRC23:14
*** jmontemayor has quit IRC23:14
*** MarkAtwood has quit IRC23:16
*** Barker has quit IRC23:18
*** jcru has quit IRC23:20
*** Barker has joined #openstack-meeting-alt23:20
*** amytron has quit IRC23:20
*** yogesh has quit IRC23:20
*** sballe has quit IRC23:22
*** sballe has joined #openstack-meeting-alt23:22
*** jergerber has quit IRC23:24
*** sarob has quit IRC23:25
*** sarob has joined #openstack-meeting-alt23:25
*** sarob has quit IRC23:29
*** saurabhs has joined #openstack-meeting-alt23:30
*** sballe_ has joined #openstack-meeting-alt23:34
*** sballe has quit IRC23:35
*** amcrn has joined #openstack-meeting-alt23:41
*** Leonr has quit IRC23:42
*** sarob has joined #openstack-meeting-alt23:43
*** tanisdl has joined #openstack-meeting-alt23:48

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