Thursday, 2015-10-15

*** harshs has joined #openstack-meeting-400:00
*** pmesserli has quit IRC00:00
*** banix has quit IRC00:00
*** banix_ is now known as banix00:00
*** smillward has quit IRC00:05
*** Piet has joined #openstack-meeting-400:17
*** SimonChung has quit IRC00:19
*** yamamoto has quit IRC00:21
*** yamamoto has joined #openstack-meeting-400:22
*** Sukhdev has quit IRC00:34
*** May-meimei has quit IRC00:34
*** wojdev_ has joined #openstack-meeting-400:37
*** wojdev has quit IRC00:37
*** wojdev_ is now known as wojdev00:37
*** Sukhdev has joined #openstack-meeting-400:38
*** SumitNaiksatam has joined #openstack-meeting-400:40
*** SumitNaiksatam has quit IRC00:40
*** bharathm has quit IRC00:44
*** julim has quit IRC00:45
*** bharathm has joined #openstack-meeting-400:47
*** banix has quit IRC00:51
*** banix has joined #openstack-meeting-400:52
*** Swami has quit IRC01:00
*** bharathm has quit IRC01:00
*** IlyaG has quit IRC01:03
*** bharathm has joined #openstack-meeting-401:03
*** woodard has joined #openstack-meeting-401:10
*** mestery has quit IRC01:18
*** Brian_shang has quit IRC01:20
*** Brian_shang has joined #openstack-meeting-401:20
*** bharathm has quit IRC01:20
*** SimonChung has joined #openstack-meeting-401:23
*** woodard has quit IRC01:23
*** IlyaG has joined #openstack-meeting-401:25
*** stanchan has joined #openstack-meeting-401:26
*** SimonChung1 has joined #openstack-meeting-401:26
*** SimonChung has quit IRC01:29
*** MarkAtwood has quit IRC01:31
*** wojdev has quit IRC01:33
*** FallenPegasus has quit IRC01:36
*** Brian_shang has quit IRC01:50
*** Brian_shang has joined #openstack-meeting-401:50
*** s3wong has quit IRC01:55
*** baoli has joined #openstack-meeting-401:56
*** mfedosin_ has quit IRC02:03
*** baoli has quit IRC02:13
*** sdake has joined #openstack-meeting-402:17
*** yamahata has quit IRC02:21
*** yamamoto has quit IRC02:31
*** harshs has quit IRC02:33
*** banix has quit IRC02:34
*** VW has joined #openstack-meeting-402:39
*** vivek-ebay has quit IRC02:50
*** KunalGandhi has quit IRC02:50
*** Brian_shang has quit IRC02:51
*** VW has quit IRC02:51
*** VW has joined #openstack-meeting-402:51
*** Brian_shang has joined #openstack-meeting-402:51
*** cloudtrainme has quit IRC03:02
*** sdake has quit IRC03:07
*** grakiss has joined #openstack-meeting-403:12
*** yamamoto has joined #openstack-meeting-403:15
*** itisha has joined #openstack-meeting-403:16
*** DericHorn-HP has quit IRC03:16
*** dims_ has quit IRC03:18
*** Sukhdev has quit IRC03:22
*** Sukhdev has joined #openstack-meeting-403:22
*** VW has quit IRC03:25
*** VW has joined #openstack-meeting-403:25
*** puranamr has joined #openstack-meeting-403:26
*** VW has quit IRC03:30
*** xuhan has joined #openstack-meeting-403:40
*** SimonChung1 has quit IRC03:51
*** SimonChung has joined #openstack-meeting-403:53
*** puranamr has quit IRC03:58
*** Sukhdev has quit IRC03:58
*** puranamr has joined #openstack-meeting-403:58
*** IlyaG has quit IRC03:59
*** IlyaG has joined #openstack-meeting-404:00
*** puranamr has quit IRC04:00
*** puranamr has joined #openstack-meeting-404:02
*** IlyaG has quit IRC04:04
*** puranamr has quit IRC04:05
*** puranamr has joined #openstack-meeting-404:06
*** DericHorn-HP has joined #openstack-meeting-404:06
*** puranamr has quit IRC04:08
*** DericHorn-HP has quit IRC04:11
*** puranamr has joined #openstack-meeting-404:12
*** SimonChung1 has joined #openstack-meeting-404:15
*** SimonChung has quit IRC04:18
*** puranamr has quit IRC04:18
*** dims has joined #openstack-meeting-404:18
*** puranamr has joined #openstack-meeting-404:19
*** bharathm has joined #openstack-meeting-404:21
*** puranamr has quit IRC04:22
*** puranamr has joined #openstack-meeting-404:23
*** dims has quit IRC04:24
*** bharathm has quit IRC04:25
*** lakshmiS has joined #openstack-meeting-404:28
*** puranamr has quit IRC04:30
*** puranamr has joined #openstack-meeting-404:32
*** puranamr has quit IRC04:34
*** puranamr_ has joined #openstack-meeting-404:34
*** puranamr_ has quit IRC04:39
*** puranamr has joined #openstack-meeting-404:41
*** lakshmiS_ has joined #openstack-meeting-404:52
*** Sukhdev has joined #openstack-meeting-404:54
*** lakshmiS has quit IRC04:55
*** amotoki has quit IRC04:57
*** amotoki_ has joined #openstack-meeting-404:57
*** DericHorn-HP has joined #openstack-meeting-405:12
*** jpekkari has joined #openstack-meeting-405:14
*** puranamr has quit IRC05:16
*** harshs has joined #openstack-meeting-405:20
*** dims has joined #openstack-meeting-405:21
*** zehicle has quit IRC05:22
*** dims has quit IRC05:26
*** FallenPegasus has joined #openstack-meeting-405:29
*** tfukushima has joined #openstack-meeting-405:29
*** xuhan has quit IRC05:30
*** IlyaG has joined #openstack-meeting-405:31
*** IlyaG has quit IRC05:35
*** nkrinner has joined #openstack-meeting-405:35
*** harshs_ has joined #openstack-meeting-405:41
*** harshs has quit IRC05:43
*** harshs_ is now known as harshs05:43
*** lazy_prince has joined #openstack-meeting-405:44
*** puranamr has joined #openstack-meeting-405:48
*** puranamr has quit IRC05:49
*** puranamr has joined #openstack-meeting-405:51
*** harshs has quit IRC05:59
*** harshs has joined #openstack-meeting-406:00
*** wojdev has joined #openstack-meeting-406:10
*** Sukhdev has quit IRC06:19
*** Sukhdev has joined #openstack-meeting-406:19
*** wojdev has quit IRC06:21
*** dims has joined #openstack-meeting-406:22
*** puranamr has quit IRC06:26
*** dims has quit IRC06:27
*** numans has joined #openstack-meeting-406:30
*** amotoki has joined #openstack-meeting-406:32
*** amotoki has quit IRC06:32
*** wojdev has joined #openstack-meeting-406:34
*** armax has quit IRC06:44
*** Sukhdev has quit IRC06:56
*** matrohon has joined #openstack-meeting-407:08
*** belmoreira has joined #openstack-meeting-407:10
*** harshs has quit IRC07:15
*** akwasnie has joined #openstack-meeting-407:18
*** evgenyf has joined #openstack-meeting-407:22
*** lakshmiS has joined #openstack-meeting-407:30
*** wojdev has quit IRC07:31
*** lakshmiS_ has quit IRC07:32
*** KunalGandhi has joined #openstack-meeting-407:40
*** itisha has quit IRC07:41
*** FallenPegasus has quit IRC07:42
*** KunalGan_ has joined #openstack-meeting-407:45
*** KunalGandhi has quit IRC07:46
*** lakshmiS has quit IRC07:50
*** feisky has joined #openstack-meeting-407:53
*** amotoki_ has quit IRC07:55
*** amotoki has joined #openstack-meeting-408:06
*** KunalGan_ has quit IRC08:11
*** xuhan has joined #openstack-meeting-408:23
*** grakiss has quit IRC08:24
*** dims has joined #openstack-meeting-408:25
*** dims has quit IRC08:30
*** mfedosin_ has joined #openstack-meeting-408:32
*** nihilifer_mobile has quit IRC08:36
*** pbourke has joined #openstack-meeting-408:39
*** amotoki has quit IRC08:43
*** stanchan has quit IRC08:49
*** amotoki has joined #openstack-meeting-408:53
*** wojdev has joined #openstack-meeting-408:59
*** subscope has joined #openstack-meeting-408:59
*** amotoki has quit IRC09:03
*** mfedosin_ has quit IRC09:09
*** wojdev has quit IRC09:12
*** dims has joined #openstack-meeting-409:27
*** dims has quit IRC09:32
*** wojdev has joined #openstack-meeting-409:33
*** VW has joined #openstack-meeting-409:34
*** _degorenko is now known as degorenko09:45
*** evgenyf has quit IRC09:48
*** dims has joined #openstack-meeting-409:51
*** tfukushima has quit IRC09:54
*** wojdev has quit IRC10:02
*** VW has quit IRC10:09
*** VW has joined #openstack-meeting-410:09
*** subscope has quit IRC10:16
*** lakshmiS has joined #openstack-meeting-410:17
*** evgenyf has joined #openstack-meeting-410:34
*** feisky has quit IRC10:45
*** numans has quit IRC10:53
*** subscope has joined #openstack-meeting-410:56
*** numans has joined #openstack-meeting-411:06
*** lakshmiS has quit IRC11:37
*** Brian_shang has quit IRC11:47
*** dzamboni has joined #openstack-meeting-411:48
*** xuhan1 has joined #openstack-meeting-411:50
*** xuhan has quit IRC11:52
*** xuhan1 is now known as xuhan11:52
*** baoli has joined #openstack-meeting-411:55
*** klamath has joined #openstack-meeting-411:57
*** baoli has quit IRC11:58
*** numans has quit IRC12:01
*** baoli has joined #openstack-meeting-412:03
*** baoli has quit IRC12:04
*** sambetts has quit IRC12:04
*** irenab has quit IRC12:04
*** irenab has joined #openstack-meeting-412:05
*** sambetts has joined #openstack-meeting-412:06
*** yamamoto has quit IRC12:08
*** markvoelker has joined #openstack-meeting-412:08
*** baoli has joined #openstack-meeting-412:08
*** baoli has quit IRC12:08
*** baoli has joined #openstack-meeting-412:09
*** xuhan has quit IRC12:09
*** numans has joined #openstack-meeting-412:14
*** bradjones has joined #openstack-meeting-412:16
*** bradjones has quit IRC12:16
*** bradjones has joined #openstack-meeting-412:16
*** amotoki has joined #openstack-meeting-412:26
*** zehicle has joined #openstack-meeting-412:30
*** puranamr has joined #openstack-meeting-412:33
*** VW has quit IRC12:35
*** VW has joined #openstack-meeting-412:36
*** woodard has joined #openstack-meeting-412:37
*** woodard has quit IRC12:37
*** woodard has joined #openstack-meeting-412:38
*** puranamr has quit IRC12:43
*** mestery has joined #openstack-meeting-412:45
*** puranamr has joined #openstack-meeting-412:45
*** Brian_shang has joined #openstack-meeting-412:48
*** VW has quit IRC12:52
*** VW has joined #openstack-meeting-412:52
*** Brian_shang has quit IRC12:52
*** yamamoto has joined #openstack-meeting-412:54
*** amotoki has quit IRC13:00
*** mestery has quit IRC13:00
*** mestery has joined #openstack-meeting-413:01
*** Brian_shang has joined #openstack-meeting-413:03
*** Brian_shang has quit IRC13:04
*** pmesserli has joined #openstack-meeting-413:05
*** Brian_shang has joined #openstack-meeting-413:05
*** cloudtrainme has joined #openstack-meeting-413:06
*** Brian_shang has quit IRC13:07
*** julim has joined #openstack-meeting-413:10
*** cloudtrainme has quit IRC13:10
*** amotoki has joined #openstack-meeting-413:12
*** Brian_shang has joined #openstack-meeting-413:12
*** lakshmiS has joined #openstack-meeting-413:13
*** Brian_shang has quit IRC13:16
*** Brian_shang has joined #openstack-meeting-413:19
*** woodard has quit IRC13:19
*** Piet has quit IRC13:20
*** woodard has joined #openstack-meeting-413:26
*** puranamr has quit IRC13:27
*** puranamr has joined #openstack-meeting-413:32
*** yamamoto has quit IRC13:34
*** julim has quit IRC13:35
*** inteq has quit IRC13:35
*** barrett1 has joined #openstack-meeting-413:36
*** daneyon_ has quit IRC13:37
*** dane_leblanc has joined #openstack-meeting-413:41
*** abhishekk has joined #openstack-meeting-413:42
*** jpekkari has quit IRC13:46
*** Brian_shang has quit IRC13:47
*** kairat has joined #openstack-meeting-413:49
*** jwagner_away is now known as jwagner13:49
*** Brian_shang has joined #openstack-meeting-413:50
*** bunting has joined #openstack-meeting-413:51
*** yamamoto has joined #openstack-meeting-413:51
*** jpekkari has joined #openstack-meeting-413:52
*** DericHorn-HP has quit IRC13:56
*** Brian_shang has quit IRC13:57
*** Brian_shang has joined #openstack-meeting-413:57
*** VanL has joined #openstack-meeting-413:57
*** jmckind has joined #openstack-meeting-413:58
*** sigmavirus24_awa is now known as sigmavirus2413:58
*** FallenPegasus has joined #openstack-meeting-414:00
kairato/14:01
flaper87Courtesy meeting reminder: ativelkov, cpallares, flaper87, flwang1, hemanthm, ivasilevskaya, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, 14:01
flaper87Courtesy meeting reminder: Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, ajayaa, GB21, bpoulos, harshs, abhishekk, bunting, dshakhray, wxy, dhellmann, kairat14:01
flaper87#startmeeting Glance14:01
openstackMeeting started Thu Oct 15 14:01:39 2015 UTC and is due to finish in 60 minutes.  The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
mfedosino/14:01
*** openstack changes topic to " (Meeting topic: Glance)"14:01
openstackThe meeting name has been set to 'glance'14:01
rosmaitao/14:01
kairato/14:01
abhishekk0/14:01
flaper87hey folks! welcome :)14:01
kragnizo/14:01
nikhilo/14:01
*** mclaren has joined #openstack-meeting-414:02
flaper87awesome, we have quorum. I believe jokke_ is around too!14:02
flaper87let's get started14:02
flaper87#topic Agenda14:02
*** openstack changes topic to "Agenda (Meeting topic: Glance)"14:02
flaper87#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:02
flaper87as usual, our agenda is there and we have some interesting topics to discuss14:02
flaper87#topic Artifacts updates14:02
*** openstack changes topic to "Artifacts updates (Meeting topic: Glance)"14:03
flaper87ativelkov: nikhil mfedosin14:03
flaper87news?14:03
mfedosinhi there!14:03
nikhilhi14:03
mfedosinAlex wrote a big message14:03
buntingo/14:03
mfedosin[openstack-dev] [app-catalog] [glance] [murano] Data Assets API for App Catalog14:03
sigmavirus24o/14:03
flaper87the email w.r.t the app catalog ?14:03
flaper87ah yeah14:03
flaper87planning to get to it tomorrow14:03
mfedosinI haven't read it yet, but it's about next implementation of Glance v3 API14:04
flaper87ok, I'll read it carefully and I'd like to encourage everyone to do that14:04
mfedosinflaper87, we're waiting for your response on that matter14:04
flaper87sure thing14:05
mfedosinflaper87, everyone is welcome in the discussion :)14:05
mfedosinthanks14:05
flaper87I'd love to hear others opinions there. I think it's important14:05
flaper87ok, moving on14:05
flaper87#topic Drivers updates14:06
*** openstack changes topic to "Drivers updates (Meeting topic: Glance)"14:06
flaper87We discussed a, hopefully, improvement for proposing small specs. These specs have been refered to as lite specs for a while and we didn't have a good way to manage them. In the hope of keeping the user's process simple, we've discussed using LP whislist bugs as lite specs and to implement a small process for it.14:06
flaper87The discussion happened here:14:06
flaper87#link http://eavesdrop.openstack.org/meetings/glance_drivers/2015/glance_drivers.2015-10-13-14.01.log.html14:06
flaper87and I've started to document the process here:14:06
flaper87#link https://review.openstack.org/#/c/234653/14:06
flaper87The document needs some work and jokke_ has stated he doesn't like the idea at all, very clearly. (at least he did it in lowercase :P)14:06
flaper87I'd like to encourage everyone to go through the logs and the proposal. It'd be great to get some further feedback on the process.14:06
flaper87Personally, I believe this is worth a try and it's definitely something we can revert or move away from if it doesn't work out.14:06
flaper87I think it'd be healthy to keep this discussion on that review but, if there are questions already, we can take some time now14:07
flaper87The meeting logs are not very long and the docs could use more eyeballs14:07
flaper87:)14:07
flaper87concerns? Shall we move on to the next update ?14:08
flaper87:D14:08
buntingWhat will we do with the current bugs marked wishlist?14:08
nikhilIt doesn't hurt to try a beta14:08
flaper87bunting: those will be triaged14:08
nikhilmeaning lets pick some potential lite-specs and see how people give feedback14:08
flaper87yup, that's the goal14:08
abhishekk++14:08
nikhiland then document the process 2-3 weeks after the summit14:08
flaper87if it doesn't work, we can move to something else14:09
jokke_o/14:09
nikhilor mention in the doc that we are trying14:09
nikhilI will comment14:09
flaper87nikhil: ++14:09
flaper87I did mention it's being introdued in Mitaka14:09
flaper87introduced14:09
jokke_I think it's gonna be really messy14:10
jokke_but my comments are mainly on that doc change14:10
*** VanL has quit IRC14:10
flaper87ok14:10
flaper87lets move on14:10
flaper87#topic release updates14:10
*** openstack changes topic to "release updates (Meeting topic: Glance)"14:10
flaper87jokke_: floor is yours14:11
jokke_So Glance got nice and shiny "11.0.0" Liberty tag just 35min ago14:11
rosmaitayay14:11
flaper87w00000h0000014:11
jokke_Thanks everyone and big hand to nikhil for being on the wheel14:11
jokke_also stable/kilo point release was tagged earlier this week14:12
*** gchamoul has quit IRC14:12
flaper87w000h00000014:12
*** coolsvap has quit IRC14:12
*** cloudtrainme has joined #openstack-meeting-414:12
*** cloudtrainme has quit IRC14:12
flaper87speaking about stable: glanceclient stable/juno gate works now14:12
jokke_thanks for the help keeping our stable together as well for all the bugfixes and backporters!14:12
jokke_flaper87: gr8!!!14:12
nikhilflaper87: yeah, there were some inconsistencies in stable/juno for client14:12
nikhiland the project mark for py3 support was partial so, mostly incorrect14:13
flaper87back to green now, which is good now that juno will soon reach EOL14:13
* flaper87 hates EOL'ing versions that don't have a working gate14:13
jokke_yeah ... I'll try to have a look if there is something critical we should backport for that before closure14:13
nikhilanyone are you aware of the deprecation dates for juno?14:14
flaper87it's likely going to be decided at the summit14:14
nikhilyeah, I don't remember the official deprecation dates14:14
nikhilI see14:14
jokke_nikhil: Iirc in 3months time or so ... the support for Juno was promised 15months14:14
flaper87yeah, but there have been changes (or at least there were in YVR)14:14
nikhilgotcha, thanks jokke_. but that's still a few months down ..14:14
*** banix has joined #openstack-meeting-414:14
*** coolsvap has joined #openstack-meeting-414:14
jokke_yeah we've had hope to keep bit overlap14:15
flaper87there's an email thread about this, I should look it up14:15
jokke_that's it from release front14:15
flaper87ok, moving on if there's nothing else on this topic14:15
flaper87good14:15
flaper87#topic cross-project liaisons14:15
*** openstack changes topic to "cross-project liaisons (Meeting topic: Glance)"14:15
flaper87#link https://wiki.openstack.org/wiki/CrossProjectLiaisons14:15
flaper87There are a couple of things here:14:16
flaper871) We need to update that wiki page, namely, we need volunteers for the several liaison roles.14:16
flaper87I'll be pinging folks that are listed there to make sure they still have time for it14:16
mfedosinI can be Glance<->Documentation liason, btw :)14:16
flaper87BUT!if you want to volunteer for something, please, let me know. Even if there's someone listed there14:17
flaper87mfedosin: awesome14:17
mfedosinsince I work with Olena14:17
flaper87#info mfedosin wants to volunteer for the glance->docs liaison role14:17
jokke_I'm happy to keep the Stable14:17
rosmaitai think i already am cross-doc liason14:17
mclarenI'll volunteer for security14:17
flaper87w000h000014:17
flaper87many volunteers14:17
flaper87keep it coming14:17
flaper87we need one more14:17
nikhilsecurity for me too if there's room14:18
mfedosinrosmaita, ah, okay. you are already there14:18
nikhilnova<->glance needs update and I think flaper87 is the the POC ?14:18
flaper87we need someone that can help attending the cross-project meetings that may/may not disappear in the future14:18
rosmaitamfedosin: let's talk at the summit14:18
flaper87nikhil: yeah14:18
nikhilflaper87: I was gunna suggest that14:18
*** pbourke has left #openstack-meeting-414:19
flaper87I would attend those but they happen in a really bad time for me and I'd love to have some help there14:19
nikhil planning to help with CPL meetings in Mitaka.14:19
flaper87I know nikhil has attended some and <3 for that14:19
jokke_flaper87: I can also share the workload on the release front if needed. Have been doing it (maybe too much) already ;)14:19
mfedosinrosmaita, sure! frankly speaking I don't want to get another responsibility :)14:19
flaper87jokke_: sweet, would love to work with you on that14:19
*** Brian_shang has quit IRC14:20
*** dzamboni has quit IRC14:20
flaper87nikhil: mind if to take the CPL meetings one instead of security (or with security)14:20
flaper87:D14:20
nikhilI can do infra+qa if there's no spot on secuity14:20
*** jwagner is now known as jwagner_away14:20
nikhilflaper87: sure, I figured. the second one should be PTL14:20
*** gchamoul has joined #openstack-meeting-414:20
nikhiltrying to find a big difference between infra and qa atm14:21
*** puranamr has quit IRC14:21
nikhilflaper87: so, what's the difference between CPL and inter project liaisons?14:21
flaper87nikhil: you mean the CPL should be just for PTLs? I guess that's how it was presented but it's really hard for me to attend. I've participated in some but can't do them all14:22
nikhilflaper87: is that just CPL meetings liaisons14:22
nikhil?14:22
flaper87nikhil: yeah14:22
jokke_Anyone knows who Nate Ziemann is? :P14:22
nikhilI do14:22
nikhilwork with me14:22
flaper87we'll clarify a lot during the summit14:22
flaper87since there'll be a session on this14:22
jokke_Seems to be our Product Working Group liaison, but never heard of him ... just wondering if he has put his name on wrong line14:22
flaper87Ok, thanks everyone for volunteering, I'll add you to the wiki if you're not there already14:22
nikhilflaper87: I don't mind attending CPL meetings as I do that for awareness anyways..14:22
flaper87we need to move on, many other topics to go through14:23
flaper87nikhil: ++ lets talk offline14:23
flaper87thanks, btw!14:23
nikhiljokke_: he's prod mgr at IBM and active at the group there. I've had a chat with him in Liberty. He put his name them I sup..14:23
*** dzamboni has joined #openstack-meeting-414:23
flaper87#topic Trusts in glance (mfedosin, kairat) https://review.openstack.org/#/c/233601/214:23
*** openstack changes topic to "Trusts in glance (mfedosin, kairat) https://review.openstack.org/#/c/233601/2 (Meeting topic: Glance)"14:23
*** dzamboni has quit IRC14:23
mfedosinhey!14:23
*** banix has quit IRC14:24
mfedosinjust wanted to inform you that we started trusts implementation in Glance14:24
*** VanL has joined #openstack-meeting-414:24
kairatI would call it PoC at this stage)14:24
*** jpekkari has quit IRC14:24
mfedosinhere's the basic code https://review.openstack.org/#/c/233601/14:25
flaper87that's awesome14:25
jokke_++14:25
flaper87#link Trusts in glance (mfedosin, kairat) https://review.openstack.org/#/c/233601/214:25
flaper87ops14:25
flaper87#undo14:25
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x9fe70d0>14:25
flaper87#link https://review.openstack.org/#/c/233601/14:25
*** jwagner_away is now known as jwagner14:25
*** wojdev has joined #openstack-meeting-414:25
mfedosinand we're going to insert it in appropriate places in glance14:25
nikhildo we have a spec for this?14:26
flaper87mfedosin: do you have an ETA?14:26
mfedosinexactly in image uploading v1 and v214:26
flaper87nikhil: there's one14:26
mfedosinnikhil yes14:26
nikhilI am trying to get a sense of what the scope is14:26
kairatflaper87, need to be updated14:26
kairatflaper87, I am going to update it tommorow14:26
jokke_#link https://review.openstack.org/#/c/229878/14:26
nikhilgot it, thanks!14:26
jokke_^^ the spec14:26
nikhil:)14:26
mfedosinkairat, yes please :)14:26
mfedosinthe problem was - how to pass trust into glance_store14:27
flaper87please, keep the spec updated as we're in the process of digging into those14:27
mfedosinbecause there is no keystoneclient dependency there14:27
mclarenmfedosin: looking forward to chatting about this at the summit14:27
flaper87would it be worth it having a session on this?14:27
flaper87there are free slots14:27
jokke_there is session proposed14:27
*** banix has joined #openstack-meeting-414:27
flaper87where?14:27
flaper87did I miss it?14:28
jokke_on the etherpad14:28
mfedosinbut today after a discussion with Flavio we decided to add it as optional dependency to Swift backend14:28
*** lakshmiS_ has joined #openstack-meeting-414:28
nikhilflaper87: late addition14:28
jokke_deep blue just above x-proj14:28
flaper87was that recently added?14:28
mfedosinflaper87, I added it14:28
flaper87ahhh14:28
flaper87ok, I'm not crazy then14:28
flaper87I mean...14:28
mfedosinyesterday, I suppose14:28
flaper87I am... but yeah14:28
*** FallenPegasus has quit IRC14:28
flaper87mfedosin: sounds great, I'll add it to the schedule14:29
mfedosinwithout trust we can't use multitenant swift driver14:29
mfedosinbecause it's unsecure14:29
mfedosin(see my latest cve)14:29
flaper87awesome!14:29
nikhilmfedosin: are you planning to add that as an optional way to authN?14:29
mfedosinso we should implement them asap I think14:29
flaper87mclaren: it'd be great to get your review on the spec for this work14:29
mclarenyup, I'm on it14:30
flaper87mclaren: awesome, thank you14:30
flaper87mfedosin: anything else?14:30
nikhilbecause, with swift we still don't have a way upstream for operators to move away from bad old locations and prevent them from keeping swift auth v1.14:30
mfedosinnikhil, I'm not sure right now, but yeah - we can reathenticate with trust to get new token14:30
nikhilok, let's discuss this on spec.14:31
nikhilthanks.14:31
mfedosinwe can discuss it on the summit14:31
flaper87++ on spec14:31
flaper87moving on14:31
flaper87#topic Approach for location management policies (kairat)  https://review.openstack.org/#/c/233687/14:31
*** openstack changes topic to "Approach for location management policies (kairat)  https://review.openstack.org/#/c/233687/ (Meeting topic: Glance)"14:31
mfedosinif you interested than put your name in the etherpad14:31
*** lakshmiS has quit IRC14:32
kairatSo I created a spec that changes the policy approach for get_image_location14:32
kairatNow i see that light-spec should be different (will change it soon)14:32
flaper87kairat: if you wrote the spec already, don't change it14:33
kairatThe change proposes just exclude location info from server response when policy doesn't allow it14:33
flaper87it's there, we can review that14:33
kairatflaper87, ok14:33
*** banix has quit IRC14:33
kairatI would like to have some feedback on it14:33
nikhilkairat: hmm, are we not using show direct url config option?14:33
kairatPreviously(in v2), we prohibited image-show, image-list of policy doesn't allow us14:34
kairatnikhil, when it is true then policy should manage this14:34
kairatIMO14:34
jokke_yes we have config option for that and we support the policy limitations for to whom it's exposed14:34
*** DericHorn-HP has joined #openstack-meeting-414:34
flaper87mmh, if we're adding policies, I wonder if we still need the config_option14:34
kairatAdditionally, i found a bug https://review.openstack.org/#/c/233687/14:34
flaper87I'll comment on the spec14:34
mclarenshow direct url is off by default I think14:34
jokke_mclaren: was just battling around this quite a bit so might be able to give bit more light there14:35
nikhilmay be we need it for v1 flaper8714:35
mclaren(If I'm thinking of the right thing)14:35
mclarenI can try14:35
flaper87nikhil: oh, good point. I'll have to check14:35
mclarenby default show multiple locations is off14:35
kairatbut when it is true then get_image_location is useless right now14:36
mclarenif you switch it on and then restrict the get_locations policy then lots of things don't work properly14:36
kairatbecause image-show image-list is also forbidden14:36
kairatmclaren, +114:36
mclarenIt's bad, but hopefully a corner case14:36
flaper87mclaren: ++14:36
jokke_there is bug open for that14:36
mclarenyou have to switch on two incompatible non-default things14:36
nikhilyes14:36
nikhilhopefully policies would be able to handle v1 too14:37
kairatAlso I noticed that we cannot add/delete location is show_multiple is off14:37
nikhilthen we can deprecate it14:37
flaper87nikhil: that's my hope14:37
mclarenand showing image locations is very brave IMHO :-)14:37
bunting++14:37
flaper87deprecating the option would be ideal so we can just use policies14:37
nikhilwell people want to do that mclaren14:37
nikhillike ironic14:37
*** dzamboni has joined #openstack-meeting-414:38
flaper87not everyone runs a public cloud14:38
* nikhil nods14:38
jokke_and I'm a lot against feature adds on v1 ... if it hasn't been needed so far, we probably won't need it at the corner of deprecation either14:38
mfedosinmclaren, do you mean showing direct urls?14:38
mclarenshowing the location string14:38
kairatmfedosin, and this also, I heard Ceph also need this14:38
nikhil'locations' is terrible14:39
kairat*this=location_utl14:39
mclarenyeah, cinder probably do stoo14:39
nikhilit can be a confusion hell14:39
mclarentoo14:39
flaper87ok, we need to move on. Sorry for limiting the time on the topic14:39
flaper87lets follow-up on the spec14:39
kairatok14:39
nikhilit should be a complete spec14:39
nikhilnot a lite one14:39
flaper87kairat: thanks for the heads up and for putting the spec together14:39
flaper87nikhil: agreed14:39
nikhilbut thanks kairat for already proposing a review14:39
flaper87#topic Skip next week's meeting (flaper87)14:39
*** openstack changes topic to "Skip next week's meeting (flaper87) (Meeting topic: Glance)"14:40
flaper87I'd like to propose skipping next week's meeting14:40
nikhil#vote yes14:40
flaper87:P14:40
nikhil:P14:40
kairat)14:40
jokke_I don't mind if the plane has wifi :P14:40
flaper87unless someone screams in 3 ... 2... 1... I'll agree this14:40
rosmaita#vote yes14:40
jokke_an hour of travel time burned some way ;)14:40
flaper87:P14:40
mclaren#vote yes14:40
flaper87just pay for the full wifi plan and you're good14:41
flaper87#agreed Skip next week's meeting October 22nd14:41
jokke_flaper87: _if_ it exists14:41
mfedosinI don't care, but skipping something is always a pleasure14:41
flaper87jokke_: man, don't get me started on airplane wifis14:41
flaper87:D14:41
jokke_:D14:41
*** dims has quit IRC14:41
flaper87moving on14:41
flaper87#topic Summit agenda (flaper87) http://mitakadesignsummit.sched.org/overview/type/glance14:42
*** openstack changes topic to "Summit agenda (flaper87) http://mitakadesignsummit.sched.org/overview/type/glance (Meeting topic: Glance)"14:42
flaper87well, that's the agenda!14:42
jokke_19min and a lot in the agenda still14:42
flaper87I'll add trusts to it14:42
flaper87I created a schedule for the summit based on the topics that were added in the proposals etherpad:14:42
flaper87#link https://etherpad.openstack.org/p/mitaka-glance-summit-topics14:42
*** dims has joined #openstack-meeting-414:42
flaper87At the top of that etherpad, I added the agenda for the summit and, as you probably noticed already, we have 2 free slots. jokke_ mentioned that we could take some time to do a heads up on DefCore in one of our working sessions. I think it'd be useful for the team but I'd also like to encourage everyone to join the cross-project session on this topic:14:42
flaper87#link http://mitakadesignsummit.sched.org/event/402c14d0efed29d1abd21b51f678576214:42
flaper87Anyhow, the link to our schedule is:14:42
flaper87#link http://mitakadesignsummit.sched.org/type/glance#.Vh-J4s-1RZI14:42
flaper87If you have another proposal OR if you have some conflicts in the current schedule, please, let me know and I'll do my best to make you happy.14:42
flaper87we now have just 1 free slot (trusts took one)14:42
mclarenAre we looking for topics to fill some of the free slots?14:42
flaper87The free slot could be used to talk about defcore, interop and glance14:43
mclarenI'm not sure, but we could potentially talk about image formats?14:43
flaper87if there are other proposals we could use that time for it14:43
nikhilflaper87: are you planning to add tags for other projects to some of the topics?14:43
mfedosinor can discuss artifacts twice14:43
flaper87nikhil: yes14:43
nikhilcool14:43
jokke_flaper87: mind to update the etherpad what you have put on the working sessions14:43
*** Swami has joined #openstack-meeting-414:44
jokke_or was it only the first one that had no details14:44
flaper87the schedule is still a draft since I wanted to know if there were conflicts14:44
flaper87jokke_: probably just the first one14:44
jokke_it was ... sorry, my bad14:44
flaper87the etherpad should be updated14:44
flaper87:D14:44
flaper87or, almost updated14:44
*** Guest68187 has quit IRC14:44
*** lbragstad has quit IRC14:44
flaper87again, session leaders, check your calendars and make sure there are no conflicts14:44
flaper87I'll send an email out to the ML14:45
flaper87but I thought about sharing it here as well14:45
flaper87thanks to all the session leaders14:45
*** blewis has joined #openstack-meeting-414:45
flaper87we <3 y'all14:45
*** blewis is now known as Guest7254914:45
flaper87at least I do :)14:45
rosmaitaflaper87: the two late sessions on thursday conflict with searchlight14:45
*** dims_ has joined #openstack-meeting-414:45
rosmaitaso maybe schedule stuff for people who don't care about searchlight at those times?14:46
*** lbragstad has joined #openstack-meeting-414:46
flaper87rosmaita: yeah, that's unfortunate. Everything conflicts this summit14:46
rosmaitai know, that's the way it goes14:46
*** IlyaG has joined #openstack-meeting-414:47
jokke_priorities ... everyone should know how to prioritize glance ;P14:47
*** carl_baldwin has joined #openstack-meeting-414:47
nikhil:P14:47
flaper87rosmaita: I'll see what can be done but I kinda think those two should be there because the image import should go after the fishbowl session14:47
rosmaitadon't worry14:47
flaper87and we can't finilize the priorities before we talk about these sessions and other topics14:47
flaper87I'll take another look there14:47
rosmaitai only want to go to the very last searchlight session at 5:2014:47
nikhilthink like a traveling salesman14:48
*** Guest72549 has quit IRC14:48
*** lbragstad has quit IRC14:48
*** wojdev has quit IRC14:48
rosmaitaso i will be at the image import follow up14:48
flaper87mfedosin: next topic is yours but I'd like to give time to rosmaita's topic if you don't mind14:48
*** dims has quit IRC14:48
flaper87we can talk about yours if there's more time at the end14:48
mfedosinoh, okay then14:48
flaper87mfedosin: thanks14:48
rosmaitamine is real quick14:48
flaper87#topic image import spec: https://review.openstack.org/#/c/232371/ (rosmaita) -14:49
*** openstack changes topic to "image import spec: https://review.openstack.org/#/c/232371/ (rosmaita) - (Meeting topic: Glance)"14:49
flaper87rosmaita: shoot14:49
rosmaitai'm thinking of doing a quick revision to handle the smaller points that have come up and put in some "note" for the topics that still require discussion, but a new patch set hides the inline comments ... any advice?14:49
rosmaitaprobably aimed mostly at people who have added comments already14:49
rosmaitathere are also a lot in the regular comments section, so those won't be hidden14:49
flaper87mmh, if the new PS is a must then do it, we can always go bac in history14:49
nikhilworks for me, I still have them pending in draft :P14:49
flaper87not in time, which is unfortunate14:50
jokke_rosmaita: go for it ... the comments will show up on the previous PS anyways ... make a note that people should read them before commenting the new version (as it won't be last anyways)14:50
*** wojdev has joined #openstack-meeting-414:50
flaper87what normally happens is that people keep discussing in older PS until the discussion is over14:50
nikhilI don't mind porting the comments as the new PS seems vital14:50
flaper87which it never is but I digress14:50
rosmaitaok, sounds like new PS is OK then14:50
mclarenrosmaita: I think we'll probably need a couple more revisions anyway14:50
flaper87rosmaita: go go go go!14:50
rosmaitai'll work onthat righrt away and then we can send out to the ML for more comments14:51
mclarencool14:51
flaper87rosmaita: awesome, looking forward to that14:51
jokke_rosmaita: I think it's better to get the annoyances away so folks can focus on the bikeshedding :P14:51
*** IlyaG has quit IRC14:51
rosmaitajokke_: ++14:51
flaper87jokke_: bike what? there's no such thing14:51
flaper87jokke_: although, I'd rather call it something else14:51
jokke_flaper87: I can introduce :P14:52
flaper87I mean, bikeshedding is not descriptive enough14:52
flaper87:P14:52
*** Piet has joined #openstack-meeting-414:52
flaper87ok14:52
* jokke_ puts the Internet Troll hat on before reviewing 14:52
flaper87#topic Schema validation for 'image-list' in glanceclient (mfedosin)14:52
*** openstack changes topic to "Schema validation for 'image-list' in glanceclient (mfedosin) (Meeting topic: Glance)"14:52
flaper87mfedosin: 5 mins so we can have open discussion (sorry for the timebox)14:52
mfedosinI've got one question14:52
*** VanL_ has joined #openstack-meeting-414:52
mfedosinsome time ago we removed schema validation from image-list14:53
mfedosinhttps://review.openstack.org/#/c/211086/14:53
*** lbragstad has joined #openstack-meeting-414:53
flaper87#link https://review.openstack.org/#/c/211086/14:53
mfedosindo we need it back as an optional feature?14:53
jokke_can we just work towards removing fully validating the server responses?14:53
kairatjokke_, ++14:53
flaper87jokke_: ++14:54
nikhilit should be either there or not, I don't see the value for it to be optional14:54
kairatbut it changes our client14:54
*** lbragstad has quit IRC14:54
*** armax has joined #openstack-meeting-414:54
flaper87that was my recommendation as well14:54
flaper87we shouldn't have it there. If there's a good use-case for it I'm all ears14:54
jokke_we can do gating tests that validates the server responses against schema, but we don't need to gate it on every client run14:54
nikhilso, scrolling back some history pages14:54
mclarenthe only thing I could think of was admin use, but I'm not sure how strong a case that is14:54
mfedosinbut what about just 'get' a single image?14:55
mfedosindo we need it here?14:55
nikhilit was introduced so that people can know that the image records they are getting back are consistent with what the clouds says they should be14:55
flaper87mfedosin: I'd say no14:55
nikhiland for cases when changes happen to images, they can be picked rather quickly14:55
*** Brian_shang has joined #openstack-meeting-414:56
nikhilif the image-meta remains in such a fluid state and constrained by policy, then the user can't know what to expect at a given point of time14:56
*** VanL has quit IRC14:56
*** vikram has joined #openstack-meeting-414:56
mfedosinso, the final decision - we don't introduce optional feature for that :)14:56
*** lbragstad has joined #openstack-meeting-414:56
*** VanL_ has quit IRC14:56
nikhilas the time bound expectation is rather dagenrous14:56
mfedosinam I right?14:56
jokke_mfedosin: I'm happy to review any such proposals :P14:57
nikhilSO, I think it14:57
nikhilit is important14:57
*** VanL has joined #openstack-meeting-414:57
mclarennikhil: as an option or always on?14:57
nikhilalways on14:57
nikhilmclaren: but14:57
kairatnikhil, but we have cases when validation can fail14:57
kairatfor example you changes list of supported images14:57
jokke_well we have had so far nothing but problems from it14:57
kairatand one of formats were deleted14:58
mclarennikhil: not practical -- v1 can create images which don't comply with v2 validation14:58
nikhilI'd love to hear examples14:58
nikhilmclaren: ^14:58
mclarencheck the client bugs :-)14:58
jokke_as said I'd be pro gating schema validations but it does not belong to our client14:58
flaper87there have been cases, fwiw14:58
mfedosinhttps://bugs.launchpad.net/python-glanceclient/+bug/147791014:58
openstackLaunchpad bug 1477910 in python-glanceclient kilo "A user can prevent another user listing images via v2 (in certain cases)" [High,Fix committed] - Assigned to Stuart McLaren (stuart-mclaren)14:58
kairatalso we can't location when show_multiple_locations is false because of this14:58
*** VanL has quit IRC14:59
kairat*can't add/delete14:59
kairatIt just fails on client but server works correctly14:59
*** VanL has joined #openstack-meeting-414:59
mclarenthere have been about 5 or 6 bugs I'm aware of with validation the cause14:59
flaper87that said, I think we need to think this through. For example, I don't think v2 should return images that are not v2 compliant14:59
*** VanL has quit IRC14:59
jokke_nikhil: good example was the schema change that warranted RC2 (I think)14:59
flaper87even if the image was created using v114:59
nikhilflaper87: agreed14:59
mclaren?14:59
jokke_just a bug that blew our client without real reason14:59
nikhiland we would have never caught it if not for validation jokke_ :)15:00
nikhilit's a catch 2215:00
flaper87ok folks, we're almost out of time15:00
rosmaitai agree with jokke_ that the place to verify compliance is the gate15:00
nikhilmclaren: flaper87: how about opening a new official tag that lists such cases and we can discuss on those bugs there?15:00
jokke_nikhil: that's why I'm proposing gating those schemas, not blowing our client on them15:00
mclarenfrom a users point of view if the image is usable via v1 then v2 is broken if they can't use the same image15:00
flaper87I'd like this discussion to move forward a bit more before creating a new tag15:00
mclarennikhil: there was a mail on the mailing list from Jay Pipes recommending it gets switched off (fwiw)15:00
nikhilmay be it should be a post-list process on client15:00
flaper87There's a bug for client validation, lets talk there15:01
*** Brian_shang has quit IRC15:01
flaper87or just create a new thread on the mailing list15:01
mfedosinflaper87, I'll write a message there15:01
mfedosinin mailing list15:01
*** sjmc7 has joined #openstack-meeting-415:01
rosmaitaor discuss at next week's meeting :)15:01
nikhilmclaren: I will look it up . thanks for the pointer.15:01
flaper87mfedosin: thanks15:01
flaper87LOL15:01
flaper87ok, time's up!15:01
mfedosinrosmaita, which is skipped15:01
flaper87thanks everyone15:01
flaper87#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
mfedosinthanks folks15:01
openstackMeeting ended Thu Oct 15 15:01:53 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-10-15-14.01.html15:01
mclarenthanks!15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-10-15-14.01.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-10-15-14.01.log.html15:01
jokke_thanks15:02
*** abhishekk has left #openstack-meeting-415:02
*** mclaren has quit IRC15:02
*** bunting has left #openstack-meeting-415:02
*** kairat has left #openstack-meeting-415:02
nikhil#startmeeting openstack search15:03
openstackMeeting started Thu Oct 15 15:03:19 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: openstack search)"15:03
openstackThe meeting name has been set to 'openstack_search'15:03
*** amotoki has quit IRC15:03
nikhilCourtesy Searchlight meeting reminder in #openstack-meeting-4: lakshmiS, mclaren, nikhil_k, rosmaita, sigmavirus24, TravT, krykowski, david-lyle, wokuma, kragniz, sjmc7, ekarlso, abhijeetm, itisha15:03
david-lyleo/15:03
rosmaitao/15:03
lakshmiS_o/15:03
nikhil#topic agenda15:03
*** openstack changes topic to "agenda (Meeting topic: openstack search)"15:03
nikhilhello everyone!15:03
sjmc7hi!15:04
lakshmiS_hey15:04
nikhilwe've no set agenda today. so it's just us celebrating the first release!!!!!!!15:04
nikhilyayayayayayyay~15:04
lakshmiS_so RC3 i guess by now15:04
sjmc7yay!15:04
sjmc7i think travis tagged it final15:04
lakshmiS_ok15:05
nikhilyeah, we're pretty much beyond the release schedule now :)15:05
*** Brian_shang has joined #openstack-meeting-415:05
nikhil#topic Tokyo summit15:06
*** openstack changes topic to "Tokyo summit (Meeting topic: openstack search)"15:06
sjmc7also, for those attending the summit, we've two sessions on thursday evening - http://mitakadesignsummit.sched.org/type/searchlight#.Vh_AzhCrQxM15:06
sjmc7that was spooky15:06
*** geoffarnold has joined #openstack-meeting-415:06
nikhil#link http://mitakadesignsummit.sched.org/type/SearchLight#.Vh_A7aJan9t15:06
nikhilsjmc7: :)15:06
nikhilTHanks to Travis, the schedule it up there.15:06
sjmc7for the first one, the fishbowl, it would be good to get reps from any services we're interested in courting15:07
*** nkrinner has quit IRC15:07
sjmc7swift and nova especially would be useful15:07
nikhilthe prioritization session is tagged with ops15:07
*** geoffarn_ has joined #openstack-meeting-415:07
sjmc7probably glance for artifacts15:07
lakshmiS_is there a conflict of time with glance session around that time15:08
nikhilsjmc7: if there is a way to get in touch with Travis today or so, we should consider adding nova and glance tag to that one..15:08
nikhilmay be swift too15:08
sjmc7he wasn't sure whether it was considered rude to do that15:08
*** woodard has quit IRC15:08
nikhillakshmiS_: yes, the glance session is about image import refactor as a follow up of the fishbowl15:08
nikhilsjmc7: yeah, we may have to ask the PTLs it they think it's okay..15:09
sjmc7other option is to send something on their mailing lists or irc meetings next week15:09
nikhiltrue15:09
rosmaitayeah, so i will prob miss the first session, will def be at the second though15:09
nikhilnova folks are likely to be at the glance session then15:09
nikhilso, it might be worth reaching out to a liaison or the ptl15:09
nikhilso that we at least someone from nova that can take notes back15:10
*** Brian_shang has quit IRC15:10
*** geoffarnold has quit IRC15:10
*** numans has quit IRC15:11
sjmc7yeah, the timing's unfortunate15:11
nikhilthat reminds me, we should discuss putting names up on the liaisons page so that people know whom to reach out. Travis will most likely be most of them :) but still good to show up on the wiki.15:11
sjmc7since he's not here to argue, i'm ok with that :)15:11
lakshmiS_do you know of any pre-summit session on nova, swift or neutron in next week15:11
nikhil:)15:11
rosmaita#link https://wiki.openstack.org/wiki/CrossProjectLiaisons15:11
nikhilthanks rosmaita15:12
nikhillakshmiS_: I am not aware.15:12
nikhillakshmiS_: although, the public facing nova meetups usually are well publicized on the ML, eventbrite etc15:13
nikhilsame with swift, from what I recollect15:13
nikhilI see the work session is listed as cross project with Horizon. Not sure if we have more to add here david-lyle :)15:14
david-lyleno, not really :P15:14
nikhil:)15:15
david-lylewait the Horizon working session?15:15
sjmc7no15:15
nikhildavid-lyle: no, the SL one tagged with horizon15:15
sjmc7the SL one15:15
nikhil:)15:15
david-lyleoh, I see the little tag now15:15
nikhilsjmc7: we're interleaved at the same wave-length today15:16
sjmc7yeah, we need to stop that15:16
david-lyleprobably just helping define the use cases15:16
*** SimonChung1 has quit IRC15:16
nikhilI see15:16
*** lakshmiS_ has quit IRC15:17
*** lakshmiS has joined #openstack-meeting-415:17
nikhil#topic pre-summit prep15:18
*** openstack changes topic to "pre-summit prep (Meeting topic: openstack search)"15:18
nikhilDO we have any pending reviews or BPs / bugs that we should discuss prior to the summit?15:18
nikhilor send an email to ML to get people attn?15:18
lakshmiSnot for this release but still https://review.openstack.org/#/c/221307/19 needs your review15:19
sjmc7i'm going to put a few BPs up beforehand. i'll send a mail maybe on monday15:19
lakshmiSnikhil: I think the patch has nice traction. just has to push it with final changes based on your findings15:20
*** bharathm has joined #openstack-meeting-415:20
nikhiloh yes, thanks for the reminder lakshmiS. I need to get to that ASAP..15:20
nikhilwill get to that today15:21
nikhilthanks sjmc7. looking forward to them..15:21
lakshmiSnikhil: thanks15:21
nikhil#topic open discussion15:21
*** openstack changes topic to "open discussion (Meeting topic: openstack search)"15:21
*** puranamr has joined #openstack-meeting-415:22
lakshmiSI was going to take a look at swift bp and get some basic patch landed if possible before summit15:22
sjmc7which one?15:22
lakshmiSswift plugin15:22
sjmc7without notifications we're a bit limited15:23
sjmc7which is one reason we need to talk to them at the summit15:23
lakshmiShttps://blueprints.launchpad.net/searchlight/+spec/swift-plugin15:23
lakshmiSyes but we will have something to refer to15:24
*** adduarte has joined #openstack-meeting-415:24
sjmc7yeah, it's a good idea to know what we want. i have some homework for the nova plugin too15:24
sjmc7i guess it's a short meeting this week15:24
nikhilI sent an email introducing seachlight as a new project to the outreachy list.15:25
nikhilthe subject is15:26
nikhil[Outreachy] [INTRODUCTION] Another project.15:26
lakshmiSgreat15:26
nikhilwill look up the link and share with you all.15:26
nikhilAlso, should we skip next week's meeting?15:26
sjmc7let's decide next week15:27
*** puranamr has quit IRC15:27
*** galstrom_zzz is now known as galstrom15:27
sjmc7there imght be some pre-summit stuff15:27
lakshmiSyup based on what we have15:27
sjmc7unless everybody's already left by then15:27
nikhilsure, see if something shows up on the agenda.15:27
*** sdake has joined #openstack-meeting-415:27
*** geoffarn_ has quit IRC15:28
nikhilTHat was it from me.15:28
nikhilIf nothing else..15:28
nikhilthanks all for joining.15:28
*** geoffarnold has joined #openstack-meeting-415:28
lakshmiSthanks15:28
rosmaitathat was painless15:28
rosmaitabye!15:28
nikhilcya15:28
lakshmiS:)15:28
*** belmoreira has quit IRC15:28
nikhil#endmeeting15:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:28
openstackMeeting ended Thu Oct 15 15:28:42 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-10-15-15.03.html15:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-10-15-15.03.txt15:28
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-10-15-15.03.log.html15:28
*** lakshmiS has left #openstack-meeting-415:28
*** sjmc7 has left #openstack-meeting-415:29
*** daneyon has joined #openstack-meeting-415:33
*** geoffarnold is now known as geoffarnoldX15:34
*** woodard has joined #openstack-meeting-415:34
*** geoffarnoldX is now known as geoffarnold15:34
*** geoffarnold is now known as geoffarnoldX15:35
*** bpokorny has joined #openstack-meeting-415:38
*** banix has joined #openstack-meeting-415:39
*** FallenPegasus has joined #openstack-meeting-415:40
*** IlyaG has joined #openstack-meeting-415:42
*** FallenPegasus has quit IRC15:44
*** evgenyf has quit IRC15:44
*** blewis has joined #openstack-meeting-415:46
*** blewis is now known as Guest2779915:46
*** sdake has quit IRC15:48
*** geoffarnoldX has quit IRC15:49
*** geoffarnold has joined #openstack-meeting-415:49
*** vivek-ebay has joined #openstack-meeting-415:51
*** jmckind is now known as jmckind_15:52
*** jmckind_ is now known as jmckind15:52
*** woodard_ has joined #openstack-meeting-415:53
*** woodard_ has quit IRC15:53
*** woodard_ has joined #openstack-meeting-415:53
*** woodard has quit IRC15:55
*** chem has quit IRC15:58
*** lazy_prince has quit IRC15:59
*** stevelle has joined #openstack-meeting-416:00
*** Sam-I-Am has joined #openstack-meeting-416:00
*** bgmccollum has joined #openstack-meeting-416:00
*** vikram has quit IRC16:01
*** odyssey4me has joined #openstack-meeting-416:01
odyssey4me#startmeeting OpenStack Ansible Meeting16:01
openstackMeeting started Thu Oct 15 16:01:24 2015 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:01
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:01
Sam-I-Amyo16:01
d34dh0r53o/16:01
odyssey4me#topic Agenda & rollcall16:01
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:01
*** Bjoern_ has joined #openstack-meeting-416:02
*** git-harry has joined #openstack-meeting-416:02
Sam-I-Amyo, again16:02
*** b3rnard0 has joined #openstack-meeting-416:02
*** wojdev has quit IRC16:02
*** prometheanfire has joined #openstack-meeting-416:02
*** puranamr has joined #openstack-meeting-416:02
prometheanfireo/16:02
palendae'lo16:03
b3rnard0hola16:03
odyssey4mehowdy all16:04
odyssey4meshall we get on it, or are we waiting for anyone else16:04
odyssey4mecloudnull has sent apologies as he's not feeling well at all16:04
jasondotstaro/16:05
odyssey4me#topic Review action items from last week16:05
*** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)"16:05
odyssey4me#link http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-10-08-16.00.html16:05
odyssey4meodyssey4me verify master has fix commited and change status of https://bugs.launchpad.net/openstack-ansible/trunk/+bug/148275616:05
openstackLaunchpad bug 1482756 in openstack-ansible trunk "networking fails due to new ebtables-based arp spoofing protection" [High,Fix committed] - Assigned to Jesse Pretorius (jesse-pretorius)16:05
odyssey4methat is done16:06
*** yamahata has joined #openstack-meeting-416:06
odyssey4methe one final piece is https://review.openstack.org/23492616:06
odyssey4mewhich is really just an update for neutron which allows Liberty's config to use the upstream default16:07
odyssey4menext: mhayden update https://bugs.launchpad.net/openstack-ansible/+bug/1491440 with current status16:07
openstackLaunchpad bug 1491440 in openstack-ansible trunk "Restarting containers leads to 'dangling' veth interfaces" [Medium,In progress] - Assigned to Major Hayden (rackerhacker)16:07
odyssey4memhayden what's up with that? ;)16:07
Sam-I-Amodyssey4me: in that neutron arp thing, did you add the ml2 extension?16:07
ApsuNetlink is hard.16:07
Sam-I-Amor plan to...16:07
odyssey4meSam-I-Am there is no need - the config template capability allows the deployer to set whatever they want16:08
odyssey4meso the approach for Liberty+ is to use upstream defaults and deployers can override anything in any conf16:08
Sam-I-Amin liberty, if you default to enabling arp spoof protection, you should also by default enable the port_security extension16:08
Sam-I-Amnever trust defaults in neutron config files, they're terrible16:09
*** qwebirc56364 has joined #openstack-meeting-416:09
odyssey4meSam-I-Am if that is done by default upstream, then it is how it will be for us16:09
odyssey4mewe don't use the config files - we rely on the code defaults16:09
odyssey4memhayden you around?16:09
*** Sam-I-Am has left #openstack-meeting-416:10
odyssey4meok, that action item will have to carry16:10
odyssey4me#action mhayden update https://bugs.launchpad.net/openstack-ansible/+bug/1491440 with current status16:10
openstackLaunchpad bug 1491440 in openstack-ansible trunk "Restarting containers leads to 'dangling' veth interfaces" [Medium,In progress] - Assigned to Major Hayden (rackerhacker)16:10
*** geoffarnold has quit IRC16:10
odyssey4menext: jasondotstar work on https://bugs.launchpad.net/openstack-ansible/+bug/146986816:10
openstackLaunchpad bug 1469868 in openstack-ansible "OpenStack Ansible Does Not Ship Glance Metadata Definitions" [Wishlist,Confirmed]16:10
*** puranamr has quit IRC16:10
*** geoffarnold has joined #openstack-meeting-416:11
*** puranamr has joined #openstack-meeting-416:11
*** Swami has quit IRC16:11
odyssey4meI see that this just came up in the channel16:11
jasondotstarhttps://review.openstack.org/#/c/235425/ is under review - got some comments16:11
odyssey4me#link https://review.openstack.org/23542516:11
odyssey4meand I see that sigmavirus24 has already provided feedback16:11
jasondotstarI'll make the adjustments accordingly16:11
sigmavirus24Thanks jasondotstar16:11
sigmavirus24You'll probably want with_items to make sure you find all locations =P16:11
jasondotstarsigmavirus24: +116:12
sigmavirus24thanks for tackling that jasondotstar16:12
odyssey4me++16:12
jasondotstarnp, first one for the ansible team16:12
jasondotstar:-)16:12
odyssey4mealright, next16:12
odyssey4me#topic Liberty Release Blueprints16:12
*** openstack changes topic to "Liberty Release Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:12
odyssey4methere are still some WIP as shown in https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:13
odyssey4meas with the venv reviews16:13
odyssey4meI'm hoping that we can get them finalised and merged by next week so that we can let it bake for a week before we release, which is planned for Firday.16:13
odyssey4me*Friday16:13
odyssey4meany questions or comments?16:14
*** vivek-eb_ has joined #openstack-meeting-416:14
odyssey4meNote that the venv reviews are also a deliberable for the Liberty release.16:14
*** vivek-ebay has quit IRC16:14
*** erikmwilson has joined #openstack-meeting-416:15
palendaeWhen is upstream's Libety release?16:17
odyssey4metoday16:17
palendaeAh16:17
odyssey4me#topic Mitaka Agenda16:18
*** openstack changes topic to "Mitaka Agenda (Meeting topic: OpenStack Ansible Meeting)"16:18
odyssey4me#link https://etherpad.openstack.org/p/openstack-ansible-mitaka-summit16:18
odyssey4meso, we have two fishbowl sessions16:18
*** puranamr has quit IRC16:18
*** puranamr has joined #openstack-meeting-416:19
odyssey4meone is http://sched.co/4Qed and the other is http://sched.co/4QbH16:19
*** akwasnie has quit IRC16:19
odyssey4mefishbowl sessions are named on the summit agenda and large rooms16:19
odyssey4mewe have several proposals in the etherpad16:20
odyssey4meI'd like some input on which proposals are considered most important for a large public audience?16:20
odyssey4mewhether already proposed, or not16:20
*** puranamr has quit IRC16:21
palendaeI know the image-based deployment options have been coming up a lot internally16:21
palendaeProbably worth exploring16:21
*** woodard_ has quit IRC16:22
odyssey4meI'd like to make a call, then send out ML announcements with the etherpad links16:22
odyssey4meI do agree that image-based deployments would be great to discuss. palendae are you still keen to moderate that?16:23
palendaeSure; I don't really have an opinion myself, but I'd like to hear ideas16:23
*** SimonChung has joined #openstack-meeting-416:23
*** KunalGandhi has joined #openstack-meeting-416:23
palendaeI think the kolla team has insights to share16:23
odyssey4mesure, I'm sure that many people do16:24
prometheanfirethey said they wanted to join my session but claim scheduling conflicts16:25
palendaeI think cloudnull, who's not here, had a few ideas from our side, but I think it's of general concern to operators16:25
*** puranamr has joined #openstack-meeting-416:25
odyssey4meas moderator you'll need to prep with probing questions, some analysis of stuff you can find and will have to be clear about what outcome you want to see16:25
odyssey4meyeah, cloudnull has already done some PoC work - and mhayden has some insights too16:26
odyssey4meI've done a little testing too16:26
palendaeAlright, I can draft some questions. Is that etherpad a good place for now?16:26
odyssey4meok cool, so we'll announce that as one16:26
palendaeOr does that get on the official docs?16:26
palendaeEr, official schedule16:26
odyssey4meI'll setup etherpads for these two sessions straight after the meeting16:26
palendaeOk16:26
odyssey4meand yes, it'll be very widely published16:26
palendaeThe questions?16:27
palendaeOr the title?16:27
*** puranamr has quit IRC16:27
*** woodard has joined #openstack-meeting-416:27
odyssey4methe etherpad we use for that session - I'll setup one up, then rely on you to put a skeleton of some sort together on it16:27
palendaeSure16:27
odyssey4meI want to send it out to the ML next week monday at the latest16:28
palendaeOk16:28
*** woodard has quit IRC16:28
odyssey4methat way people can already pose questions and notes16:28
palendaeYep, fair16:28
*** woodard has joined #openstack-meeting-416:28
*** puranamr has joined #openstack-meeting-416:28
odyssey4meFor the other session I'd like to invite feedback from anyone on how we're doing... but that seems a bit naf16:29
odyssey4meSo perhaps we should do a session on enabling multi OS support for openstack-ansible?16:29
palendaeThat sounds like a good one16:30
stevellethat seems like fit for a work session maybe16:30
stevelleI am not sure if that benefits from fishbowl but16:30
stevelleI don't really know, to say that again16:30
odyssey4meyeah, I think it's been a broad interest and may bring in some fresh faces16:31
*** geoffarnold has quit IRC16:31
*** geoffarnold has joined #openstack-meeting-416:32
odyssey4methen for the workroom slot, perhaps we should buckle down and discuss our lessons learned and how we can do better16:32
odyssey4mehow does that sound?16:32
stevelleI was drawn to the idea of revisiting dynamic inventory16:32
odyssey4mehmm, another option I just realised for the fishbowl session is to talk about upgrades16:33
*** jmckind is now known as jmckind_16:33
odyssey4meit'd be great to get a broad set of feedback for handling upgrades properly16:33
palendaeI know someone from CERN mentioned they wanted to talk about how they upgrade to every openstack release16:34
palendaeI want to ask them how they do that without disrupting business16:34
palendaeOr "work"16:34
palendaeNot sure if that's generally applicable or not. prometheanfire were you doing operator sessions?16:35
*** sdake has joined #openstack-meeting-416:35
palendaeThat audience would probably be interested16:35
prometheanfireyes16:35
prometheanfirehttps://etherpad.openstack.org/p/TYO-ops-infrastructure-containers16:36
prometheanfireit's wednesday from 11:15 to 11:5516:36
palendaeThanks16:36
prometheanfirethere are also other upgrades talks16:37
prometheanfirehttps://etherpad.openstack.org/p/TYO-ops-upgrades16:37
odyssey4methat's before our session - so it may be good to attend that, then come armed with that info for a discussion?16:37
prometheanfireyes?16:37
prometheanfirethat a question?16:37
odyssey4meyeah - I'm suggesting that perhaps we make or second fishbowl session (3:40 pm on wed) a workshop on upgrades16:38
prometheanfirethat sounds good16:38
odyssey4meso the first one (at 2:50pm will be about image-based deployment)16:38
palendaeOk16:38
odyssey4medo we think those two topics are of a broad interest and useful to the project?16:38
palendaeI believe so16:39
palendaeWould like other opinions16:39
odyssey4megreat!16:39
odyssey4meok, then the work session at 5:30pm...16:40
palendaeWonder if they have any documentaton on what video hook ups the rooms have16:40
prometheanfireI'm gonna scope out at least my room before :P16:40
palendaeYeah, I'd kind of like to know now, since I'm still waffling on what devices to take16:40
palendaeBut that's a tangent16:40
odyssey4meperhaps for the workroom slot we should take a look at dynamic inventory16:41
odyssey4meit seems to be the greatest cause for confusion when new users are configuring OSA16:41
odyssey4meand for developers trying to add functionality16:42
palendaeDo we want to discuss the Ansible community day at all?16:43
palendaeI think that's Tuesday?16:43
odyssey4meI'd like to also do a sprint where we go through a role analysis and see how we can simplify how we build roles and set an improved pattern.16:43
odyssey4meAnsible community day is Thu16:43
palendaeOk16:43
odyssey4mehttps://etherpad.openstack.org/p/ansible-collabday-mitaka-planning16:43
palendaeI know there were some topics like what needs to happen to move to Ansible 2.016:43
odyssey4methat's pretty much Ansible's gig - our attendance will be to listen mostly16:45
palendaeSure16:45
palendaeMore looking for things we might pitch as discussion topics16:45
*** qwebirc52852 has joined #openstack-meeting-416:46
*** Sukhdev has joined #openstack-meeting-416:46
odyssey4me#action odyssey4me to setup summit etherpads16:46
*** lazy_prince has joined #openstack-meeting-416:46
odyssey4me#action palendae to populate the Image-based deployments etherpad16:46
*** FallenPegasus has joined #openstack-meeting-416:47
odyssey4me#action odyssey4me to populate the upgrade session etherpad16:47
odyssey4me#action odyssey4me to send ML announcements for the summit etherpads16:47
odyssey4meam I missing anything?16:47
*** singlethink has joined #openstack-meeting-416:48
*** s3wong has joined #openstack-meeting-416:49
odyssey4me#topic Open discussion16:49
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:49
odyssey4mealright - is there anything else anyone wants to discuss, highlight or dance a jig about?16:49
stevellehttps://review.openstack.org/#/c/226621/16:50
stevelleI want to highlight this for discussion16:50
odyssey4mesure, go ahead16:50
*** puranamr has quit IRC16:50
*** pcarver has joined #openstack-meeting-416:51
stevelleThis is something that would be a fairly significant change to juno, and I wanted to recruit opinions in the form of reviews.16:51
*** vivek-eb_ has quit IRC16:51
odyssey4meyeah, I'm not fond of the idea of that much change going into juno - that said it is simply an enabler and if enough people confirm that it doesn't break anything to merge it in, then I don't mind16:53
*** geoffarn_ has joined #openstack-meeting-416:53
*** puranamr has joined #openstack-meeting-416:53
odyssey4memy primary concern is not whether it does what it wants to do (ie if you enable https then it actually sets the endpoints, etc)16:53
*** geoffarnold has quit IRC16:53
odyssey4memy primary concern is whether it breaks anything if you don't16:53
odyssey4mefrom the gate check it appears not, but it definitely needs more actual testers as the juno testing is not as thorough as kilo+16:54
*** puranamr has quit IRC16:55
*** subscope has quit IRC16:55
odyssey4meany other opinions/views?16:56
palendaeI tested patchset 1, and got expected endpoints when not enabling it16:57
stevelleIf you don't have something to add right now but you can take a bit of time to consider it, please do this week.16:57
palendaeBut that's been a while16:57
*** johnsom has joined #openstack-meeting-416:58
*** Swami has joined #openstack-meeting-416:58
odyssey4meok, thanks everyone!17:00
*** DericHorn-HP has quit IRC17:00
odyssey4me#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Oct 15 17:00:06 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-10-15-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-10-15-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-10-15-16.01.log.html17:00
*** stevelle has left #openstack-meeting-417:00
*** mohankumar has joined #openstack-meeting-417:00
*** prometheanfire has left #openstack-meeting-417:00
*** b3rnard0 has left #openstack-meeting-417:00
*** vikram_ has joined #openstack-meeting-417:00
*** odyssey4me has left #openstack-meeting-417:00
*** cathy_ has joined #openstack-meeting-417:01
cathy_#startmeeting service_chaining17:02
openstackMeeting started Thu Oct 15 17:02:22 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: service_chaining)"17:02
Swamihi17:02
openstackThe meeting name has been set to 'service_chaining'17:02
johnsomo/17:02
vikram_hi17:02
cathy_hi everyone17:02
pcarverhi17:02
*** puranamr has joined #openstack-meeting-417:02
s3wonghello17:02
mohankumarhi17:03
cathy_any topic you would like to discuss today?17:03
vikram_cathy_: I have few questions17:04
cathy_One topic we need to discuss is how to ensure new update of the patches do not break the functionality, how to enforce running of the UT scripts. what do you think?17:04
cathy_vikram_: sure, go ahead17:04
*** puranamr has quit IRC17:04
vikram_cathy_: want to discuss about a comment received for the CLI patch17:04
vikram_https://review.openstack.org/#/c/210008/17:05
cathy_#topic discuss about a comment received for the CLI patch17:05
*** openstack changes topic to "discuss about a comment received for the CLI patch (Meeting topic: service_chaining)"17:05
cathy_let me take a look at the comment.17:05
*** puranamr has joined #openstack-meeting-417:05
cathy_vikram_: which one?17:06
vikram_Do we need to support empty flow_classifier list for port-chain update17:06
vikram_https://review.openstack.org/#/c/210008/14/networking_sfc/cli/port_chain.py17:06
vikram_L10817:06
*** amotoki has joined #openstack-meeting-417:06
*** Bjoern_ has left #openstack-meeting-417:06
vikram_if yes then we need to have a separate cli option for this17:07
vikram_may be --no-flow-classifier17:07
*** LouisF has joined #openstack-meeting-417:07
LouisFhi17:07
vikram_hi LouisF17:07
cathy_LouisF: hi17:07
vikram_what everyone thinks about this?17:08
vikram_amotoki: ping17:08
amotokihi17:08
-amotoki- scrolling back the meeting log in a browser.17:08
vikram_amotoki: I think you are aware about --no-flow-classifier discussion17:08
amotokivikram_: yes17:09
johnsomI think the option to not have a flow classifier is good.17:09
vikram_amotoki: I am discussing the same with the team17:09
cathy_amotoki: hi17:09
vikram_My first question is do we need to support it?17:10
amotokiHonestly I am not sure there is a case where we need to set flow-classifiers to []17:10
cathy_vikram_: johnsom we allow no specification of FC when creating SC. I am still going through the comment. vikram_ could you clarify the question?17:10
*** Piet has quit IRC17:10
*** puranamr has quit IRC17:10
*** lbragstad_ has joined #openstack-meeting-417:11
s3wongvikram_: that's my question too... a chain with all Neutron ports specified already but without classifier... how does that work?17:11
vikram_cathy_: The doubt is about updating Portchain information with empty FC list17:11
cathy_vikram_: later the user can add dynamically add more FC to the chain or remove some flow from a  chain17:11
johnsomSo it's a convenience option we are talking about17:11
amotokiIMO it is better to provide a way to specify [] in general, as I stated in the review comment.17:11
amotokione question: do we need to specify FC when creating a port-chain?17:11
cathy_amotoki: no17:12
LouisFamotoki: no17:12
vikram_s3wong: agreed.. I am just wanted to confirm whether we should support empty FC list in either create or update?17:12
amotokiit means we allow empty flow classifiers for port-chain.17:12
SwamiI thought the FC is required for the port-chain to work17:12
vikram_amotoki: +117:12
s3wongSwami: as do I...17:12
*** vivek-ebay has joined #openstack-meeting-417:13
*** VanL has joined #openstack-meeting-417:13
SwamiIs FC not a requirement for port-chaining.17:13
*** harshs has joined #openstack-meeting-417:13
vikram_Swami: I am with Swami.. I also fell we can madate this option17:13
vikram_*feel17:13
amotokiIn my understanding, if FC is not specified, it matches all traffic from a neutron port.17:13
SwamiBecause if we pass an empty classifier does it mean don't check the flow.17:13
LouisFSwami: that is correct no traffic will enter the chain unless a FC is specified17:13
*** bitblt has joined #openstack-meeting-417:13
vikram_LouisF: Is FC a mandatory param?/17:14
LouisFit may be convenient to configure the port chain and then add FCs as needed17:14
amotokiLouisF: my understanding looks wrong according to your comment above.17:14
LouisFvikram_: no17:14
amotokiLouisF: right?17:14
*** geoffarnold has joined #openstack-meeting-417:14
s3wongLouisF: so in essence it is staging the port-chain, but basically not officially "deploying" the chain?17:14
cathy_amotoki: if no FC is specified, then no flow will enter the chain17:14
LouisFs3wong: correct17:14
SwamiI would say that a valid entry in the FC is required for the port-chain to work. But we can make the FC to be updatable.17:15
cathy_s3wong: yes17:15
vikram_Swami: +117:15
amotokicathy_: thanks. no traffic matches to empty FC, so no traffic enters such chain. got it.17:15
LouisFSwami: -117:15
*** sambetts has quit IRC17:15
SwamiLouisF: what is your concern.17:15
*** VanL_ has joined #openstack-meeting-417:16
*** numans has joined #openstack-meeting-417:16
LouisFSwami: as i stated, it is question of staging the PC, it may initially be configured with no FC and then the FCs are added as necessary17:16
mohankumarcathy: then we need to make FC as mandatory param17:16
*** sambetts has joined #openstack-meeting-417:17
SwamiLouisF: So my question is do you even want the agent to work on a port-chain configuration if there is no FC.17:17
amotokione possible use case is to disable a port-chain temporarily or conditionally.17:17
vikram_LouisF: Anyways no point having a PC without a FC17:17
LouisFSwami: so my argument is that FCs are not mandatory17:17
vikram_LouisF: Then why we should allow such conf17:17
cathy_Swami: there could be scenario that during some time period, no flow will go through a chain and then later some flows are added to the chain. This will avoid removing chain and then creating chain frequently.17:17
amotokior enable port-chain conditionally.17:17
*** geoffarnold is now known as geoffarnoldX17:18
Swamicathy_: My point is if you don't have a valid FC, why do we even need the chain setup to be there.17:18
*** geoffarn_ has quit IRC17:18
cathy_amotoki: yes, no FC for a chain at that time means the chain is disabled or not used temporarily17:18
LouisFSwami: operationally a PC can be created initially with no FCs: it is essentially dormant until FCs are added17:19
*** VanL has quit IRC17:19
SwamiThe problem with this you might be stressing the rpc a lot with the agent changes. If everything is in place, it will be single shot.17:19
*** Sukhdev has quit IRC17:19
LouisFthis provides the flexibility of doing this17:19
amotokiSwami: a usecase in my mind is that we setup a port-chain first with no associated flow and then add flow(s) depending on a situation.17:19
LouisFamotoki: agree17:19
vikram_amotoki: IMO, user must have a usecase in mind before creating a PC17:20
SwamiSo in this case do you expect all packets to flow through the chain or no packets to flow through the chain until there is an FC.17:20
*** banix has quit IRC17:20
vikram_amotoki: Why to have the overhead..17:20
LouisFamotoki: this allows for that use case to work17:20
cathy_Swami: I understand your point. but the purpose is for handling the scenario that no flow goes through the chain temporarily and we do no need to end up deleting a chain and then recreating the same chain17:20
cathy_Swami: the latter17:20
Swamicathy_: thanks17:21
vikram_cathy_: but how frequent this can happen17:21
cathy_Swami: no packets to flow through the chain until there is an FC.17:21
amotokivikram_: agree in general and it is typical cases I think.17:21
amotokivikram_: I just imagine possible use cases.17:21
Swamicathy_: If no packets flwo through the chain, then it's ok17:21
Swamis/flwo/flow17:22
vikram_if everyone okay then I have no issues17:22
vikram_Now coming to next question how to specify an empty FC list in update cli17:22
amotokimy impression is if we don't have a reason to disallow empty flow-classifier for port-chain, it looks better to allow empty FC.17:22
Swamicathy_: the only concern that i have is in large scale deployment if you have too many requests coming in with chain creation and then with FC addition, it would cause some timing issues.17:23
vikram_amotoki: agreed17:23
Swamicathy_: if we are ready to deal with those scenarios, then it is ok.17:23
cathy_it could happen. for example, a chain consists of a FW. And there is a Flow associated with the chain. Then after some check passes, the remaining packets of the flow do not need to go through this FW chain. Then another new tenant's flow comes and might need to go through this chain. Or this previous flow sees some security issue and then needs to go through this fW chain again.17:23
amotokiSwami: API concept and acutla behaviors are different things.17:23
amotokiAPI concent should work for all cases.17:24
amotokihow to deal with racing conditions is a different topic.17:24
Swamiamotoki: agreed, but I am talking about the action taken based on the API17:24
cathy_so there will be some period that the chain is not associated with any flow17:24
vikram_How to specify an empty FC list in update cli? Currently it's unaddressed...17:24
cathy_Swami: it is all up to the user. If the user knows that some flows need to go through a chain then he should create the chain with FCs.17:25
*** woodard_ has joined #openstack-meeting-417:25
Swamicathy_: agreed valid point.17:25
LouisFamotoki: so you are suggesting the explicit use of the --no-flow-classifier option on a port-chain-update to remove all FCs from a PC?17:26
vikram_cathy_:agreed17:26
LouisFin the CLI command that is17:26
amotokiLouisF: yes. it is my thought.17:27
LouisFamotoki: i this is a clean way of doing it - what do others think?17:28
vikram_+1 for no-flow-classifier17:28
cathy_amotoki: so if we allow explicit use of --no-flow-classifier option on a port-chain-update, should we allow the explicit use on port-chain-create?17:28
*** woodard has quit IRC17:28
vikram_cathy_: No need17:29
LouisFamotoki: as you mention in your comments there is precedent for using that approach elsewahere in neutron - correct?17:29
*** carl_baldwin has quit IRC17:29
amotokicathy_: there is no good guidline at now, but it can be supported for consistency.17:29
amotokiLouisF: yes.17:29
cathy_amotoki: vikram_ yes, I think it is better to be consistent. thanks.17:29
vikram_cathy_: FC is not a mandate param for create operation.. user can just keep it empty17:29
LouisFcathy_: agree no neew17:30
LouisFneed17:30
cathy_vikram_: I am thinking about consistency17:30
amotokiLouisF: AFAIK, FWaaS CLI adopts a bit different way, but others have similar options.17:30
vikram_to me it's confusing17:30
vikram_more options always create confusion17:30
*** mfalatic has left #openstack-meeting-417:30
cathy_vikram_: LouisF I think similar option in create and update will be good17:30
LouisFcathy_: means that the user has to do that on every port-chain-create17:30
LouisFwith no FC17:31
*** yamamoto has quit IRC17:31
amotokicathy_: at the moment, there are many inconsistency in neutronclient options. If a default value is empty, most sub commands do not provide --no-xxx option but it can be improved.17:31
cathy_LouisF: It is just whether we would like to make it explicit in create port chain similar to update port chain17:31
LouisFi'm open to leave it for consensus17:32
*** yamamoto has joined #openstack-meeting-417:32
cathy_I am open too although personally I like consistency17:32
LouisFshall we vote?17:32
*** yamamoto has quit IRC17:33
vikram_I would like it for update only..17:33
cathy_LouisF: yes17:33
LouisF+117:33
vikram_+1 for update only..17:33
amotoki+1 for update, either ok for create.17:33
LouisF+1 on that is my preference17:33
amotokiLouisF: what does "that' mean?17:34
LouisFamotoki: only on port-chain-update17:34
johnsomYeah, a summary of the vote would be handy17:34
mohankumar+1 for update only17:34
amotokiLouisF: thanks17:34
cathy_mohankumar: Swami s3wong johnsom ?17:34
Swamicathy_:hi17:34
cathy_vote?17:35
mohankumarcathy_: voted for "update only"17:35
s3wong+1 for update only17:35
SwamiI am ok with the proposal +117:35
johnsom+117:35
*** geoffarnoldX has quit IRC17:35
*** VanL_ has quit IRC17:35
cathy_#agreed we will add no flow classifier to the port chain update17:35
*** geoffarnold has joined #openstack-meeting-417:35
*** bharathm has quit IRC17:36
vikram_cathy_: I have one more question..17:36
vikram_can I put it forward17:36
cathy_#agreed we will still allow the case of a chain with no FC17:37
cathy_vikram_: sure17:37
vikram_I can find that there are no FC related interfaces in the drivers base class?17:37
cathy_vikram_: what do you mean? could you clarify?17:38
vikram_cathy_: 1 sec.. let me collect17:38
*** qwebirc56364 has quit IRC17:38
vikram_https://review.openstack.org/#/c/227100/16/networking_sfc/services/portchain/drivers/driver_base.py17:38
vikram_class PortChainAbstractDriver(object):17:39
LouisFvikram_: you mentioned that you would likely need those FC related interfaces for the onos driver - right?17:39
vikram_LouisF: Yes17:39
*** VanL has joined #openstack-meeting-417:39
vikram_My intention is we need to be generic17:39
LouisFvikram_: so your idea is to add them in that file or in a separate file?17:40
vikram_LouisF: same file17:40
vikram_IMO, we can expose them to the driver and driver may or may not implement those..17:40
LouisFvikram_: should be ok - anyone else?17:40
cathy_vikram_: +117:41
cathy_vikram_: I thought we have added them.17:41
LouisFvikram_: can you go ahead and add the needed FC related interfaces17:41
vikram_Will do that17:41
LouisFvikram_: thanks17:41
cathy_vikram_: great thanks17:42
amotokivikram_: does it lead to different behavior per driver? or can users get consistent behavior regardless of drivers?17:42
s3wongYep, that sounds good. Make our driver APIs more usable for various SDN controller solutions17:42
LouisFs3wong: +117:42
cathy_amotoki: user should get consistent behavior regardless of drivers17:42
vikram_amotoki: End result would be same17:42
LouisFamotoki: +117:42
vikram_I am done..17:43
vikram_I think amotoki has some idea about the plugin framework17:43
amotokivikram_: cathy_: good. we are all in the same page :)17:43
cathy_amotoki: Yes, that is a must :-)17:43
vikram_amotoki: would you like to discuss it?17:43
s3wongamotoki: I think it should be fine... in essence we are giving the driver a flow programming interface which should map directly to OpenFlow like constructs17:43
cathy_#topic plugin framework17:44
*** openstack changes topic to "plugin framework (Meeting topic: service_chaining)"17:44
amotokivikram_ seems to try to move new topic17:44
cathy_amotoki: would you like to discuss the plugin framework?17:45
amotokiin the last meeting, we discussed how many service plugins we should have.17:45
vikram_cathy_: thanks for moving the topic17:45
cathy_vikram_: sure17:45
amotokiI think the general consensus was one.17:45
s3wongamotoki: I think that is the topic vikram_ wants to move to, and you get the ball :-)17:45
amotoki:)17:45
mohankumar:)17:46
amotokiwhat in my mind is to have one service plugin for 'sfc' and it loads all required extensions.17:46
vikram_amotoki: I am with you ;)17:46
Swami+117:46
amotokiour concern is how we can migrate to a generic flow classifier extension once it lands.17:46
amotokias far as I gathered, it is the only reason we have two service plugins.17:47
*** salv-orlando has joined #openstack-meeting-417:47
amotokiis it correct?17:47
vikram_yes17:47
cathy_amotoki: yes17:47
amotokiso I am now trying to have one service plugin for 'sfc' in the initial flow classifier extension patch.17:48
cathy_amotoki: so it can be more decoupled and we can move it to the generic FC easier17:48
amotokithe plugin would be very thin17:48
*** degorenko is now known as _degorenko17:48
vikram_amotoki: I feel the extension in the same patch would increae it's testability as well17:49
amotokicathy_: do you mean if we have a separate service plugin for flow classifier we need to query a correspondng service plugin17:49
vikram_*increase17:49
amotokiand we can decouple things more clearly?17:50
*** bgmccollum has left #openstack-meeting-417:50
vikram_amotoki: I think the original intention was to develop it as a separate service..17:50
amotokion the other hand, without plugin, we cannot test in a real neutron-server.17:50
vikram_cathy_: please correct me if wrong17:51
amotokiokay, a separate plugin for classifier sounds okay. all other features are implemented into 'port-chain' plugin?17:51
vikram_amotoki: We need to add for FC..17:52
vikram_amotoki: It's pending17:52
*** adduarte has quit IRC17:52
cathy_amotoki: sorry I am back. yes we need to query a correspondng service plugin17:52
vikram_Will do that17:52
*** banix has joined #openstack-meeting-417:52
vikram_cathy_: We think we don't need 2 service plugins17:52
cathy_amotoki: yes17:52
cathy_amotoki: yes all other features are implemented into 'port-chain' plugin?17:53
cathy_amotoki: yes all other features are implemented into 'port-chain' plugin17:53
amotokicathy_: understood now.17:53
vikram_cathy_: Current patch doesn't handle FC stuffs in port_chain service plugins17:53
amotokiso is it better to rename 'port-chain' pluign to 'sfc' plugin?17:53
vikram_cathy_: we got to add those..17:54
s3wongamotoki, vikram_: so with one service plugin, in the future, if other services (say FWaaS) wants to use FC, they would essentially be dependent on sfc service plugin?17:54
vikram_s3wong: FC will be a CORE extension17:54
vikram_s3wong: so no need ;)17:54
s3wongvikram_: I see ...17:54
amotokiwhat we need then is to query CORE plugin and consume methods from Core plugin.17:55
LouisFamotoki: query for FC - right?17:55
amotokiLouisF: yes at now and after generic FC lands it will be provided by core plugin.17:55
vikram_I think we are all okay with one plug-in I believe17:56
Swami+117:56
vikram_+217:56
LouisF+117:56
*** geoffarnold has quit IRC17:56
mohankumar+117:56
amotokione plugin for all FC and others?17:56
s3wongLouisF: once FC lands in Neutron, us in SFC would be calling FC APIs which then taps into whatever driver/plugin that implements the FC core extensions17:56
vikram_one sfc plugin for networking-sfc17:57
*** geoffarnold has joined #openstack-meeting-417:57
*** VanL has quit IRC17:57
cathy_vikram_: hold on17:57
amotokiOr one plugin for all features except FC and a separate plugin for FC?17:57
vikram_cathy_: sure17:57
LouisFs3wong: do you see a problem there?17:58
vikram_s3ong: Common FC is only about maintaining a common DB17:59
*** numans has quit IRC17:59
vikram_s3wong: Common FC is only about maintaining a common DB17:59
vikram_I think time is UP..18:00
s3wongLouisF: well, (a) the FC extension that eventually lands in Neutron NEEDS to be compatible with how SFC consumes FC today (else we all go in and give a -1, and amotoki can give a -2), and (2) the separation needs to be a coordinated effort between whoever doing it in Neutron18:00
*** lbragstad has quit IRC18:00
*** Guest27799 has quit IRC18:00
*** lbragstad_ is now known as lbragstad18:00
s3wongvikram_: no API change?18:00
s3wong(yeah, time's up. Sorry)18:00
vikram_s3wong: nope18:00
LouisFs3wong: ok18:00
amotokii don't want to -2. it is emergency.18:01
LouisFmohankumar: we have tested with you CLI and making good progress18:01
s3wongamotoki: :-) yeah, a bit of a joke there :-)18:01
amotoki:-)18:01
*** cathy_ has quit IRC18:01
s3wongoh no, cathy_ is gone. No one to #endmeeting...18:01
*** david-lyle has quit IRC18:01
*** bharathm has joined #openstack-meeting-418:01
mohankumarLouisF : ok18:01
amotokilet's finish the meeting18:01
vikram_i think cathy_ is not there.. We are out of time18:01
LouisFok18:02
LouisF#endmeeting18:02
*** SumitNaiksatam has joined #openstack-meeting-418:02
vikram_bye18:02
*** ivar-lazzaro has joined #openstack-meeting-418:02
*** cathy_ has joined #openstack-meeting-418:02
Swamibye18:02
mohankumarbye18:02
cathy_hi18:02
amotokiLouisF is co-chair?18:02
s3wongcathy_: please end meeting18:02
LouisFactually not18:02
amotokicathy_: please end the meeting18:02
cathy_worry I am disconnected18:02
LouisFbye18:02
cathy_#endmeeting18:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:02
*** david-lyle has joined #openstack-meeting-418:02
openstackMeeting ended Thu Oct 15 18:02:46 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-10-15-17.02.html18:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-10-15-17.02.txt18:02
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-10-15-17.02.log.html18:02
*** VanL has joined #openstack-meeting-418:03
*** amotoki has quit IRC18:03
*** SimonChung1 has joined #openstack-meeting-418:03
*** SimonChung has quit IRC18:04
*** johnsom has left #openstack-meeting-418:04
*** cathy_ has quit IRC18:05
*** vikram_ has quit IRC18:05
*** mohankumar has quit IRC18:06
*** julim has joined #openstack-meeting-418:07
*** Sukhdev has joined #openstack-meeting-418:07
*** bitblt has quit IRC18:16
*** numans has joined #openstack-meeting-418:17
*** geoffarnold has quit IRC18:17
*** geoffarnold has joined #openstack-meeting-418:18
*** LouisF has quit IRC18:21
*** jmckind_ is now known as jmckind18:27
*** ajmiller_ is now known as ajmiller18:29
*** yamamoto has joined #openstack-meeting-418:33
*** geoffarnold has quit IRC18:39
*** geoffarn_ has joined #openstack-meeting-418:39
*** wojdev has joined #openstack-meeting-418:41
*** dims has joined #openstack-meeting-418:43
*** dims_ has quit IRC18:45
*** dims has quit IRC18:47
*** yamamoto has quit IRC18:53
*** carl_baldwin has joined #openstack-meeting-418:58
*** vivek-eb_ has joined #openstack-meeting-418:59
*** geoffarn_ has quit IRC19:00
*** geoffarnold has joined #openstack-meeting-419:01
*** VanL has quit IRC19:02
*** dzamboni has quit IRC19:03
*** vivek-ebay has quit IRC19:03
*** armax has quit IRC19:05
*** SumitNaiksatam has left #openstack-meeting-419:05
*** dims has joined #openstack-meeting-419:11
*** SimonChung1 has quit IRC19:12
*** VanL has joined #openstack-meeting-419:13
*** aha__ has joined #openstack-meeting-419:14
*** SimonChung has joined #openstack-meeting-419:15
*** geoffarnold has quit IRC19:21
*** geoffarnold has joined #openstack-meeting-419:22
*** VanL has quit IRC19:23
*** jmckind is now known as jmckind_19:25
*** numans has quit IRC19:26
*** jmckind_ is now known as jmckind19:26
*** lazy_prince has quit IRC19:28
*** singlethink has quit IRC19:30
*** dims has quit IRC19:30
*** salv-orlando has quit IRC19:32
*** jmckind is now known as jmckind_19:36
*** bpokorny has quit IRC19:38
*** qwebirc52852 has quit IRC19:38
*** numans has joined #openstack-meeting-419:39
*** geoffarnold is now known as geoffarnoldX19:39
*** woodard has joined #openstack-meeting-419:40
*** singlethink has joined #openstack-meeting-419:41
*** armax has joined #openstack-meeting-419:41
*** geoffarnoldX has quit IRC19:42
*** woodard_ has quit IRC19:43
*** geoffarnold has joined #openstack-meeting-419:43
*** woodard has quit IRC19:46
*** Sukhdev has quit IRC19:47
*** woodard has joined #openstack-meeting-419:47
*** woodard_ has joined #openstack-meeting-419:51
*** banix has quit IRC19:52
*** mestery_ has joined #openstack-meeting-419:53
*** woodard has quit IRC19:54
*** ivar-laz_ has joined #openstack-meeting-419:59
*** Piet has joined #openstack-meeting-419:59
*** salv-orlando has joined #openstack-meeting-420:02
*** ivar-lazzaro has quit IRC20:03
*** dane_leblanc_ has joined #openstack-meeting-420:04
*** geoffarn_ has joined #openstack-meeting-420:04
*** banix has joined #openstack-meeting-420:05
*** geoffarnold has quit IRC20:05
*** VW has quit IRC20:05
*** VW has joined #openstack-meeting-420:06
*** SimonChung1 has joined #openstack-meeting-420:06
*** SimonChung1 has quit IRC20:07
*** SimonChung1 has joined #openstack-meeting-420:07
*** SimonChung2 has joined #openstack-meeting-420:07
*** SimonChung1 has quit IRC20:07
*** SimonChung has quit IRC20:07
*** dane_leblanc has quit IRC20:07
*** SimonChung2 has quit IRC20:07
*** SimonChung has joined #openstack-meeting-420:07
*** SimonChung1 has joined #openstack-meeting-420:08
*** SimonChung has quit IRC20:08
*** armax has quit IRC20:08
*** dwalleck has joined #openstack-meeting-420:09
*** VW has quit IRC20:10
*** armax has joined #openstack-meeting-420:11
*** VW has joined #openstack-meeting-420:13
*** mestery_ has quit IRC20:19
*** sambetts has quit IRC20:24
*** geoffarn_ has quit IRC20:25
*** armax has quit IRC20:26
*** geoffarnold has joined #openstack-meeting-420:26
*** sambetts has joined #openstack-meeting-420:26
*** dwalleck has quit IRC20:28
*** armax has joined #openstack-meeting-420:31
*** mestery_ has joined #openstack-meeting-420:32
*** mestery_ has quit IRC20:32
*** baoli has quit IRC20:32
*** Guest71541 has joined #openstack-meeting-420:32
*** woodard_ has quit IRC20:33
*** woodard has joined #openstack-meeting-420:35
*** julim has quit IRC20:35
*** VanL has joined #openstack-meeting-420:36
*** bpokorny has joined #openstack-meeting-420:37
*** woodard has quit IRC20:41
*** Sukhdev has joined #openstack-meeting-420:46
*** Guest71541 is now known as dims_20:46
*** geoffarnold has quit IRC20:46
*** geoffarnold has joined #openstack-meeting-420:47
*** DericHorn-HP has joined #openstack-meeting-420:54
*** dwalleck has joined #openstack-meeting-420:55
*** VanL has quit IRC21:01
*** banix has quit IRC21:02
*** jwagner is now known as jwagner_away21:04
*** harshs has quit IRC21:06
*** geoffarnold has quit IRC21:08
*** geoffarnold has joined #openstack-meeting-421:08
*** blahRus has joined #openstack-meeting-421:14
*** ivar-laz_ has quit IRC21:18
*** VanL has joined #openstack-meeting-421:20
*** geoffarnold has quit IRC21:29
*** geoffarnold has joined #openstack-meeting-421:30
*** vivek-eb_ has quit IRC21:33
*** SimonChung has joined #openstack-meeting-421:34
*** SimonChung1 has quit IRC21:34
*** SimonChung1 has joined #openstack-meeting-421:35
*** SimonChung has quit IRC21:35
*** VanL has quit IRC21:35
*** woodard has joined #openstack-meeting-421:38
*** ivar-lazzaro has joined #openstack-meeting-421:39
*** ivar-lazzaro has quit IRC21:39
*** DericHorn-HP has quit IRC21:40
*** qwebirc91817 has joined #openstack-meeting-421:40
*** qwebirc91817 has left #openstack-meeting-421:41
*** Piet has quit IRC21:45
*** ivar-lazzaro has joined #openstack-meeting-421:45
*** FallenPegasus has quit IRC21:49
*** FallenPegasus has joined #openstack-meeting-421:49
*** dwalleck has quit IRC21:50
*** geoffarnold has quit IRC21:50
*** geoffarnold has joined #openstack-meeting-421:51
*** klamath has quit IRC21:51
*** Sukhdev has quit IRC21:57
*** vivek-ebay has joined #openstack-meeting-421:57
*** dwalleck has joined #openstack-meeting-421:58
*** mfedosin_ has joined #openstack-meeting-422:01
*** SimonChung1 has quit IRC22:01
*** geoffarnold has quit IRC22:01
*** jmckind_ has quit IRC22:04
*** VanL has joined #openstack-meeting-422:06
*** geoffarnold has joined #openstack-meeting-422:06
*** VanL has joined #openstack-meeting-422:06
*** sigmavirus24 is now known as sigmavirus24_awa22:08
*** mestery has quit IRC22:08
*** harshs has joined #openstack-meeting-422:12
*** Sukhdev has joined #openstack-meeting-422:23
*** galstrom is now known as galstrom_zzz22:25
*** VW has quit IRC22:31
*** VW has joined #openstack-meeting-422:31
*** VW has quit IRC22:31
*** VW has joined #openstack-meeting-422:32
*** wojdev has quit IRC22:33
*** dwalleck has quit IRC22:36
*** SimonChung has joined #openstack-meeting-422:37
*** Sukhdev has quit IRC22:39
*** woodard has quit IRC22:42
*** woodard has joined #openstack-meeting-422:43
*** VW has quit IRC22:45
*** Sukhdev has joined #openstack-meeting-422:45
*** dwalleck has joined #openstack-meeting-422:48
*** singlethink has quit IRC22:49
*** klamath has joined #openstack-meeting-422:51
*** klamath has quit IRC22:51
*** klamath has joined #openstack-meeting-422:52
*** daneyon has quit IRC22:55
*** pmesserli has quit IRC22:55
*** bharathm has quit IRC22:56
*** bharathm has joined #openstack-meeting-422:56
*** Sukhdev has quit IRC22:58
*** klamath has quit IRC22:58
*** Sukhdev has joined #openstack-meeting-423:01
*** SimonChung1 has joined #openstack-meeting-423:02
*** SimonChung has quit IRC23:02
*** SimonChung has joined #openstack-meeting-423:03
*** SimonChung1 has quit IRC23:03
*** daneyon has joined #openstack-meeting-423:03
*** geoffarnold is now known as geoffarnoldX23:04
*** dwalleck has quit IRC23:07
*** dwalleck has joined #openstack-meeting-423:08
*** bpokorny has quit IRC23:08
*** david-lyle has quit IRC23:09
*** david-lyle has joined #openstack-meeting-423:09
*** geoffarnoldX is now known as geoffarnold23:10
*** geoffarnold has quit IRC23:11
*** delattec has quit IRC23:12
*** carl_baldwin has quit IRC23:12
*** salv-orl_ has joined #openstack-meeting-423:15
*** Piet has joined #openstack-meeting-423:16
*** wshao has joined #openstack-meeting-423:17
*** salv-orlando has quit IRC23:18
*** blahRus has quit IRC23:19
*** sdake has quit IRC23:22
*** banix has joined #openstack-meeting-423:24
*** s3wong_ has joined #openstack-meeting-423:26
*** dane_leblanc_ has quit IRC23:27
*** inteq has joined #openstack-meeting-423:27
*** nikhil_k has joined #openstack-meeting-423:27
*** Kiall has quit IRC23:30
*** persia has quit IRC23:30
*** persia has joined #openstack-meeting-423:30
*** baigk1 has joined #openstack-meeting-423:31
*** dwalleck_ has joined #openstack-meeting-423:31
*** miguelgrinberg has quit IRC23:31
*** Kiall has joined #openstack-meeting-423:31
*** miguelgrinberg has joined #openstack-meeting-423:31
*** Piet has quit IRC23:32
*** s3wong has quit IRC23:32
*** nikhil has quit IRC23:32
*** scotticus has quit IRC23:32
*** baigk has quit IRC23:32
*** baigk1 is now known as baigk23:32
*** yamahata__ has joined #openstack-meeting-423:33
*** SimonChung has quit IRC23:33
*** dwalleck has quit IRC23:33
*** cgoncalves has quit IRC23:33
*** gchamoul has quit IRC23:34
*** hogepodge has quit IRC23:34
*** inteq has quit IRC23:34
*** jckasper has quit IRC23:34
*** sbadia has quit IRC23:34
*** bapalm has quit IRC23:34
*** bogdando has quit IRC23:34
*** isq_ has quit IRC23:34
*** wojdev has joined #openstack-meeting-423:35
*** cgoncalves has joined #openstack-meeting-423:35
*** wojdev has quit IRC23:37
*** IlyaG has quit IRC23:37
*** s3wong_ is now known as s3wong23:38
*** scott_ has joined #openstack-meeting-423:39
*** gchamoul has joined #openstack-meeting-423:39
*** bapalm has joined #openstack-meeting-423:39
*** scott_ is now known as Guest4012023:39
*** sbadia has joined #openstack-meeting-423:41
*** coolsvap has quit IRC23:54
*** dstanek has quit IRC23:54
*** jcook has quit IRC23:54
*** wshao has quit IRC23:54
*** bharathm has quit IRC23:54
*** sambetts has quit IRC23:54
*** bradjones has quit IRC23:54
*** ajmiller has quit IRC23:54
*** jmccrory has quit IRC23:54
*** B_Smith has quit IRC23:54
*** iurygregory has quit IRC23:54
*** mancdaz has quit IRC23:54
*** git-harry has quit IRC23:54
*** matrohon has quit IRC23:54
*** johnthetubaguy has quit IRC23:54
*** nikhil_k has quit IRC23:54
*** VanL has quit IRC23:54
*** ivar-lazzaro has quit IRC23:54
*** dims_ has quit IRC23:54
*** SamYaple has quit IRC23:54
*** davidlenwell has quit IRC23:54
*** ag___ has quit IRC23:54
*** sbalukoff1 has quit IRC23:54
*** meteorfox has quit IRC23:54
*** alex_didenko has quit IRC23:54
*** serverascode has quit IRC23:54
*** gema has quit IRC23:54
*** vishwanathj has quit IRC23:54
*** mfisch has quit IRC23:54
*** Adri2000 has quit IRC23:54
*** xgerman has quit IRC23:54
*** igordcard_ has quit IRC23:54
*** kelv has quit IRC23:54
*** zigo has quit IRC23:54
*** tonyb has quit IRC23:54
*** galstrom_zzz has quit IRC23:54
*** zz_zz_ja has quit IRC23:54
*** sarob has quit IRC23:54
*** krotscheck has quit IRC23:54
*** rharwood has quit IRC23:54
*** sigmavirus24_awa has quit IRC23:54
*** eglute has quit IRC23:54
*** d34dh0r53 has quit IRC23:54
*** cloudnull has quit IRC23:54
*** GheRivero has quit IRC23:54
*** jroll has quit IRC23:54
*** palendae has quit IRC23:54
*** timsim has quit IRC23:54
*** dolphm has quit IRC23:54
*** mgagne has quit IRC23:54
*** vivek-ebay has quit IRC23:54
*** barrett1 has quit IRC23:54
*** marcusvrn_ has quit IRC23:54
*** mmedvede has quit IRC23:54
*** myatsenko has quit IRC23:54
*** briancurtin has quit IRC23:54
*** nibalizer has quit IRC23:54
*** amandap has quit IRC23:54
*** crinkle has quit IRC23:54
*** hughhalf has quit IRC23:54
*** harmw has quit IRC23:54
*** andymccr has quit IRC23:54
*** banix has quit IRC23:54
*** armax has quit IRC23:54
*** Swami has quit IRC23:54
*** Daviey has quit IRC23:54
*** rex_lee_ has quit IRC23:54
*** yhvh has quit IRC23:54
*** mugsie has quit IRC23:54
*** shakamunyi has quit IRC23:54
*** masteinhauser has quit IRC23:54
*** chigang has quit IRC23:54
*** ativelkov has quit IRC23:54
*** Kiall has quit IRC23:54
*** persia has quit IRC23:54
*** zehicle has quit IRC23:54
*** sbalukoff has quit IRC23:54
*** sbog has quit IRC23:54
*** kbyrne has quit IRC23:54
*** pkoniszewski has quit IRC23:54
*** Hunner has quit IRC23:54
*** bapalm has quit IRC23:54
*** sbadia has quit IRC23:54
*** mfedosin_ has quit IRC23:54
*** jpeeler has quit IRC23:54
*** devananda has quit IRC23:54
*** pcarver has quit IRC23:54
*** _degorenko has quit IRC23:54
*** mentat has quit IRC23:54
*** bknudson has quit IRC23:54
*** russellb has quit IRC23:55
*** tristanC has quit IRC23:55
*** hughsaunders has quit IRC23:55
*** jlvillal has quit IRC23:55
*** rosmaita has quit IRC23:55
*** anteaya has quit IRC23:55
*** fc__ has quit IRC23:55
*** david-lyle has quit IRC23:55
*** harshs has quit IRC23:55
*** lbragstad has quit IRC23:55
*** zhiyan has quit IRC23:55
*** ashtokolov has quit IRC23:55
*** sweston has quit IRC23:55
*** dougwig has quit IRC23:55
*** _ody has quit IRC23:55
*** partner has quit IRC23:55
*** Guest40120 has quit IRC23:55
*** s3wong has quit IRC23:55
*** Sukhdev has quit IRC23:55
*** aderyugin has quit IRC23:55
*** amit213 has quit IRC23:55
*** jokke_ has quit IRC23:55
*** dhellmann has quit IRC23:55
*** rods has quit IRC23:55
*** EmilienM has quit IRC23:55
*** notmyname has quit IRC23:55
*** daneyon has quit IRC23:55
*** numans has quit IRC23:55
*** blogan has quit IRC23:55
*** HenryG has quit IRC23:55
*** d0ugal has quit IRC23:55
*** spredzy has quit IRC23:55
*** pleia2 has quit IRC23:55
*** kfjohnson_ has quit IRC23:55
*** mfedosin has quit IRC23:55
*** gchamoul has quit IRC23:55
*** miguelgrinberg has quit IRC23:55
*** dwalleck_ has quit IRC23:55
*** baigk has quit IRC23:55
*** yamahata has quit IRC23:55
*** irenab has quit IRC23:55
*** nihilifer has quit IRC23:55
*** sballe has quit IRC23:55
*** skath has quit IRC23:55
*** fungi has quit IRC23:55
*** ChrisPriceAB has quit IRC23:55
*** flaper87 has quit IRC23:55
*** kragniz has quit IRC23:55
*** saneax_ has quit IRC23:55
*** bnemec has quit IRC23:55
*** j^2 has quit IRC23:55
*** SergeyLukjanov has quit IRC23:55
*** sc68cal has quit IRC23:55
*** patrickeast has quit IRC23:55
*** dilyin has quit IRC23:55
*** _fortis has quit IRC23:55
*** markmcclain has quit IRC23:55
*** mhayden has quit IRC23:55
*** amaksimov has quit IRC23:55
*** pc-pothole has quit IRC23:55
*** mattymo has quit IRC23:55
*** FallenPegasus has quit IRC23:55
*** KunalGandhi has quit IRC23:55
*** jasondotstar has quit IRC23:55
*** pasquier-s has quit IRC23:55
*** morgabra has quit IRC23:55
*** clayton has quit IRC23:55
*** med_ has quit IRC23:55
*** yamahata__ has quit IRC23:55
*** salv-orl_ has quit IRC23:55
*** woodard has quit IRC23:55
*** hemanthm has quit IRC23:55
*** ttx has quit IRC23:55
*** krtaylor has quit IRC23:55
*** purp has quit IRC23:55
*** epheo has quit IRC23:55
*** trey has quit IRC23:55
*** ekarlso has quit IRC23:55
*** jwang_ has quit IRC23:55
*** kevinbenton has quit IRC23:55
*** erikmwilson has quit IRC23:55
*** jwagner_away has quit IRC23:55
*** timello has quit IRC23:55
*** Apsu has quit IRC23:55
*** raginbajin has quit IRC23:55
*** aha__ has quit IRC23:55
*** Sukhdev has joined #openstack-meeting-423:59

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