Thursday, 2015-11-12

*** ajmiller has joined #openstack-meeting-400:00
*** sdake has joined #openstack-meeting-400:01
*** Piet has quit IRC00:02
*** sdake has quit IRC00:03
*** baoli has quit IRC00:03
*** sdake has joined #openstack-meeting-400:07
*** pmesserli has quit IRC00:10
*** memogarcia has quit IRC00:23
*** bmoss has joined #openstack-meeting-400:27
*** bmoss has left #openstack-meeting-400:27
*** yamahata has joined #openstack-meeting-400:28
*** Piet has joined #openstack-meeting-400:29
*** bobh has quit IRC00:30
*** MarkAtwood has quit IRC00:32
*** memogarcia has joined #openstack-meeting-400:32
*** JRobinson__ has joined #openstack-meeting-400:33
*** angdraug has quit IRC00:34
*** limao has joined #openstack-meeting-400:40
*** amotoki has joined #openstack-meeting-400:41
*** IlyaG has quit IRC00:46
*** Swami has quit IRC00:46
*** yamahata has quit IRC00:49
*** IlyaG has joined #openstack-meeting-400:50
*** IlyaG has quit IRC00:53
*** memogarcia has quit IRC00:55
*** memogarcia has joined #openstack-meeting-401:02
*** julim has quit IRC01:02
*** yamahata has joined #openstack-meeting-401:06
*** sdake has quit IRC01:10
*** SimonChung has quit IRC01:13
*** ajmiller has quit IRC01:15
*** yamahata has quit IRC01:21
*** baohua has joined #openstack-meeting-401:30
*** xingchao has joined #openstack-meeting-401:32
*** itisha has joined #openstack-meeting-401:39
*** Sukhdev has quit IRC01:41
*** xingchao has quit IRC01:52
*** bpokorny has quit IRC01:53
*** janiceonchn has quit IRC01:54
*** sdake has joined #openstack-meeting-401:56
*** MarkAtwood has joined #openstack-meeting-402:01
*** JRobinson__ has quit IRC02:04
*** zeih has joined #openstack-meeting-402:07
*** zeih_ has quit IRC02:07
*** memogarcia has quit IRC02:08
*** memogarcia has joined #openstack-meeting-402:10
*** sdake has quit IRC02:15
*** baoli has joined #openstack-meeting-402:15
*** baoli has quit IRC02:17
*** baoli has joined #openstack-meeting-402:17
*** baoli has quit IRC02:18
*** baoli has joined #openstack-meeting-402:19
*** s3wong has quit IRC02:19
*** janiceonchn has joined #openstack-meeting-402:24
*** xingchao has joined #openstack-meeting-402:24
*** banix has joined #openstack-meeting-402:25
*** janiceonchn has quit IRC02:39
*** prashantD has quit IRC02:43
*** sdake has joined #openstack-meeting-402:44
*** IlyaG has joined #openstack-meeting-402:44
*** dims has quit IRC02:57
*** dims has joined #openstack-meeting-403:07
*** IlyaG has quit IRC03:08
*** memogarcia has quit IRC03:09
*** memogarcia has joined #openstack-meeting-403:11
*** dims has quit IRC03:14
*** dims has joined #openstack-meeting-403:16
*** memogarcia has quit IRC03:23
*** dims has quit IRC03:25
*** memogarcia has joined #openstack-meeting-403:25
*** sdake has quit IRC03:39
*** sdake has joined #openstack-meeting-403:40
*** zehicle has joined #openstack-meeting-403:49
*** itisha has quit IRC03:51
*** memogarcia has quit IRC03:54
*** memogarcia has joined #openstack-meeting-403:56
*** zehicle has quit IRC03:58
*** xingchao has quit IRC04:31
*** memogarcia has quit IRC04:39
*** memogarcia has joined #openstack-meeting-404:41
*** JRobinson__ has joined #openstack-meeting-405:09
*** zehicle has joined #openstack-meeting-405:11
*** fawadkhaliq has joined #openstack-meeting-405:14
*** baoli has quit IRC05:20
*** irenab has quit IRC06:07
*** xingchao has joined #openstack-meeting-406:10
*** numans has joined #openstack-meeting-406:10
*** jpekkari has joined #openstack-meeting-406:13
*** numans has quit IRC06:14
*** banix has quit IRC06:32
*** gb21 has joined #openstack-meeting-406:39
*** JRobinson__ has quit IRC06:41
*** irenab has joined #openstack-meeting-406:41
*** zehicle has quit IRC06:44
*** sc68cal has quit IRC06:45
*** numans has joined #openstack-meeting-406:49
*** JRobinson__ has joined #openstack-meeting-406:53
*** baoli has joined #openstack-meeting-406:55
*** numans has quit IRC06:58
*** numans has joined #openstack-meeting-407:01
*** baoli has quit IRC07:01
*** numans has quit IRC07:12
*** tfukushima has joined #openstack-meeting-407:13
*** nkrinner has quit IRC07:17
*** nkrinner has joined #openstack-meeting-407:17
*** tfukushima has quit IRC07:19
*** yamamoto has quit IRC07:22
*** tfukushima has joined #openstack-meeting-407:22
*** salv-orlando has joined #openstack-meeting-407:23
*** armax has quit IRC07:34
*** yamamoto has joined #openstack-meeting-408:01
*** zeih has quit IRC08:10
*** gb21 has quit IRC08:22
*** sdake has quit IRC08:24
*** sdake has joined #openstack-meeting-408:25
*** yamamoto has quit IRC08:29
*** sc68cal has joined #openstack-meeting-408:31
*** gb21 has joined #openstack-meeting-408:34
*** andymaier has joined #openstack-meeting-408:35
*** andymaier_ has joined #openstack-meeting-408:35
*** andymaier_ has quit IRC08:38
*** numans has joined #openstack-meeting-408:38
*** numans has quit IRC08:39
*** numans has joined #openstack-meeting-408:39
*** amotoki has quit IRC08:40
*** dshakhray has joined #openstack-meeting-408:42
*** salv-orlando has quit IRC08:46
*** yamamoto has joined #openstack-meeting-408:47
*** sdake has quit IRC08:49
*** sdake has joined #openstack-meeting-408:49
*** zeih has joined #openstack-meeting-408:50
*** yamamoto has quit IRC08:56
*** baohua has quit IRC08:58
*** matrohon has joined #openstack-meeting-409:00
*** sdake has quit IRC09:00
*** MarkAtwood has quit IRC09:01
*** MarkAtwo_ has joined #openstack-meeting-409:01
*** MarkAtwood has joined #openstack-meeting-409:03
*** MarkAtwo_ has quit IRC09:06
*** sdake has joined #openstack-meeting-409:07
*** JRobinson__ has quit IRC09:08
*** yamamoto has joined #openstack-meeting-409:12
*** yamamoto has quit IRC09:16
*** memogarcia has quit IRC09:25
*** tfukushima has quit IRC09:26
*** tfukushima has joined #openstack-meeting-409:30
*** memogarcia has joined #openstack-meeting-409:32
*** sdake has quit IRC09:46
*** igordcard has joined #openstack-meeting-409:47
*** memogarcia has quit IRC09:58
*** andymaier has quit IRC09:58
*** igordcard_ has joined #openstack-meeting-410:03
*** igordcard has quit IRC10:06
*** memogarcia has joined #openstack-meeting-410:06
*** pbourke has quit IRC10:16
*** pbourke has joined #openstack-meeting-410:17
*** yamamoto has joined #openstack-meeting-410:17
*** yamamoto has quit IRC10:22
*** sdake has joined #openstack-meeting-410:25
*** janiceonchn has joined #openstack-meeting-410:32
*** janiceonchn has quit IRC10:33
*** MarkAtwood has quit IRC10:34
*** yamamoto has joined #openstack-meeting-410:37
*** sdake has quit IRC10:41
*** memogarcia has quit IRC10:41
*** sdake has joined #openstack-meeting-410:41
*** igordcard__ has joined #openstack-meeting-410:44
*** yamamoto has quit IRC10:45
*** igordcard_ has quit IRC10:46
*** lkoranda_ has joined #openstack-meeting-410:48
*** lkoranda has quit IRC10:51
*** memogarcia has joined #openstack-meeting-410:51
*** jgjhgsonchn88523 has joined #openstack-meeting-410:53
*** lkoranda_ has quit IRC10:53
*** memogarcia has quit IRC10:55
*** limao has quit IRC10:56
*** tfukushima has quit IRC10:56
*** memogarcia has joined #openstack-meeting-410:57
*** sdake has quit IRC10:57
*** sdake has joined #openstack-meeting-410:57
*** lkoranda has joined #openstack-meeting-410:58
*** baohua has joined #openstack-meeting-410:58
*** baoli has joined #openstack-meeting-410:58
*** baoli has quit IRC11:03
*** dzamboni has joined #openstack-meeting-411:03
*** sdake has quit IRC11:13
*** sdake has joined #openstack-meeting-411:13
*** dims_ has joined #openstack-meeting-411:14
*** baoli has joined #openstack-meeting-411:14
*** irenab has quit IRC11:14
*** memogarcia has quit IRC11:16
*** baoli has quit IRC11:19
*** memogarcia has joined #openstack-meeting-411:23
*** sdake has quit IRC11:29
*** xingchao has quit IRC11:35
*** fawadkhaliq has quit IRC11:35
*** memogarcia has quit IRC11:41
*** baoli has joined #openstack-meeting-411:41
*** memogarcia has joined #openstack-meeting-411:42
*** cloudtrainme has joined #openstack-meeting-411:44
*** yamamoto has joined #openstack-meeting-411:46
*** baoli has quit IRC11:46
*** yamamoto has quit IRC11:51
*** lakshmiS has joined #openstack-meeting-411:58
*** lakshmiS_ has joined #openstack-meeting-412:02
*** lakshmiS has quit IRC12:04
*** jgjhgsonchn88523 has quit IRC12:08
*** xingchao has joined #openstack-meeting-412:10
*** memogarcia has quit IRC12:11
*** memogarcia has joined #openstack-meeting-412:19
*** yamamoto has joined #openstack-meeting-412:23
*** baoli has joined #openstack-meeting-412:39
*** qwebirc98722 has joined #openstack-meeting-412:40
* qwebirc98722 slaps saneax around a bit with a large fishbot12:40
* qwebirc98722 slaps sballe around a bit with a large fishbot12:40
*** qwebirc98722 has quit IRC12:40
*** qwebirc71670 has joined #openstack-meeting-412:41
*** memogarcia has quit IRC12:43
*** baoli has quit IRC12:44
*** mageshgv has joined #openstack-meeting-412:46
*** memogarcia has joined #openstack-meeting-412:50
*** baoli has joined #openstack-meeting-412:53
*** cloudtrainme has quit IRC12:58
*** cloudtrainme has joined #openstack-meeting-412:59
*** lakshmiS_ has quit IRC13:03
*** klamath has joined #openstack-meeting-413:07
*** klamath has quit IRC13:07
*** klamath has joined #openstack-meeting-413:08
*** qwebirc71670 has quit IRC13:08
*** bobh has joined #openstack-meeting-413:13
*** woodard has joined #openstack-meeting-413:14
*** woodard has quit IRC13:14
*** woodard has joined #openstack-meeting-413:15
*** bobh has quit IRC13:20
*** mestery has joined #openstack-meeting-413:21
*** dims_ has quit IRC13:24
*** jpekkari has quit IRC13:25
*** dims has joined #openstack-meeting-413:26
*** memogarcia has quit IRC13:27
*** memogarcia has joined #openstack-meeting-413:29
*** memogarcia has quit IRC13:42
*** lakshmiS has joined #openstack-meeting-413:45
*** Piet has quit IRC13:45
*** sdake has joined #openstack-meeting-413:46
*** abhishekk has joined #openstack-meeting-413:50
*** memogarcia has joined #openstack-meeting-413:51
*** ajmiller has joined #openstack-meeting-413:55
*** bpoulos has joined #openstack-meeting-413:57
*** mfedosin has joined #openstack-meeting-413:58
flaper87Courtesy meeting reminder: ativelkov, cpallares, flaper87, flwang1, hemanthm, ivasilevskaya, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k13:59
flaper87Courtesy meeting reminder: Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, ajayaa, GB21, bpoulos, harshs, abhishekk, bunting13:59
flaper87Courtesy meeting reminder: dshakhray, wxy, dhellmann, kairatyY13:59
*** kairat has joined #openstack-meeting-413:59
flaper87#startmeeting Glance13:59
openstackMeeting started Thu Nov 12 13:59:48 2015 UTC and is due to finish in 60 minutes.  The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
*** openstack changes topic to " (Meeting topic: Glance)"13:59
openstackThe meeting name has been set to 'glance'13:59
kairato/13:59
abhishekko/13:59
flaper87#topic Roll Call14:00
dshakhrayo/14:00
*** openstack changes topic to "Roll Call (Meeting topic: Glance)"14:00
flaper87so, who's around ?14:00
flaper87:D14:00
flaper87pppppplllll14:00
flaper87:D14:00
* flaper87 has a terrible connection today14:00
gb21o/14:00
flaper87#topic Agenda14:00
*** openstack changes topic to "Agenda (Meeting topic: Glance)"14:00
flaper87#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
bpouloso/14:00
*** julim has joined #openstack-meeting-414:00
flaper87That's our agenda for today14:00
mfedosino/14:01
flaper87not much to say today more than updates14:01
flaper87#topic Updates from summit http://lists.openstack.org/pipermail/openstack-dev/2015-November/078235.html (flaper87)14:01
*** openstack changes topic to "Updates from summit http://lists.openstack.org/pipermail/openstack-dev/2015-November/078235.html (flaper87) (Meeting topic: Glance)"14:01
*** jckasper has joined #openstack-meeting-414:01
flaper87So, that's the email with the summary from the summit14:02
flaper87Hope you all read it and you all love it14:02
flaper87:P14:02
*** sdake has quit IRC14:02
flaper87jokes apart, are there questions from that email?14:02
*** mclaren has joined #openstack-meeting-414:02
nikhil_ko/14:02
flaper87I'd like to take some time to answer questions and doubts from the summit14:02
flaper87nikhil_k: yoooooooooooooooooo14:02
flaper87Even for people that attended14:02
*** bunting has joined #openstack-meeting-414:03
flaper87During summits we discuss many things but nothing is written on stone14:03
mfedosinflaper87: it was briefly and clearly :)14:03
flaper87I'd like that to be clear to everyone and make sure ppl know that feedback is always welcome14:03
kairatflaper87, I need to clarify one question :)14:03
kairatit is related to priorities14:03
flaper87kairat: shoot14:03
flaper87I've priorities in the topics for today too14:04
kairatOk14:04
kairatlet's talk about it later)14:04
flaper87:D14:04
*** cloudtrainme has quit IRC14:04
flaper87ok, any other questions I can delay answers for ?14:04
flaper87:D14:04
flaper87I'll take that as a no14:05
flaper87#topic Priorities for Mitaka http://specs.openstack.org/openstack/glance-specs/priorities/mitaka-priorities.html (flaper87)14:05
*** openstack changes topic to "Priorities for Mitaka http://specs.openstack.org/openstack/glance-specs/priorities/mitaka-priorities.html (flaper87) (Meeting topic: Glance)"14:05
flaper87kairat: gimme 1s14:05
kairatflaper87, ok14:05
*** pmesserli has joined #openstack-meeting-414:05
flaper87That's the list of priorities. That's what we should focus our review strengths on. However, that doesn't mean we won't review other patches14:05
*** sdake has joined #openstack-meeting-414:06
*** yamamoto has quit IRC14:06
flaper87The priorities list helps reviews to know what to focus on when in doubt and to communicate to the community what the team wants to achieve during the cycle14:06
Jokke_o/14:06
flaper87there are things that have a clear plan forward (or focus)14:06
flaper87and  there are others that will still happen (hopefully) but are less "critical"14:07
flaper87Hope that it's clear that the priorities list *doesn't* mean other things won't be reviewed14:07
flaper87that's it from me14:07
flaper87kairat: shoot14:07
nikhil_ksounds good. so, this is a immutable list, correct?14:07
kairatSo I got this: https://review.openstack.org/#/c/233687/14:08
flaper87nikhil_k: yup14:08
kairatand i was interesting if priorities is like restrictions14:08
* nikhil_k has a small KB so typing very slow14:08
kairator like things that we should be focused on14:08
flaper87kairat: to some extent it also works as a way to know what we would like to have in the cycle or not14:09
flaper87if there are 10 specs impacting the API, we might need to choose which ones we'll let in14:09
kairatI understand the reasoning but it is a correct to have -2 on all bp that is not included in priorities14:09
Jokke_kairat: looking that change ... I don't think it was priority reason it got -2'd14:09
* nikhil_k still absorbing new process & waiting for things to fan out before giving feedback (about feedback req before)14:09
flaper87kairat: no, in fact, there are other specs there that don't have -2's14:10
mfedosinkairat: I think that -2 is not related to priorities14:10
flaper87and yeah, that14:10
flaper87what mfedosin and Jokke_ said14:10
mfedosinwe just postponed your feature to N14:10
mfedosinbecause there are a lot of changes in Mitaka14:11
* flaper87 is scared about the import process work14:11
flaper87that's gonna be huge and it'll require lots of time14:11
mclarenhe's not alone14:11
kairatOk, so no features except priorities?14:11
kairatand bugs of course14:12
*** salv-orlando has joined #openstack-meeting-414:12
flaper87kairat: no, that's not what we are saying14:12
*** cloudtrainme has joined #openstack-meeting-414:12
flaper87please, take a look at the list of specs14:12
nikhil_kkairat: let's work on case by case basis, I think the break would be mostly on api changes14:12
flaper87there *are* new features there14:12
flaper87we simply can't afford them all14:12
flaper87nikhil_k: ++14:12
*** woodard has quit IRC14:12
*** memogarcia has quit IRC14:12
kairatflaper87, ok, is it mentioned in your spec?14:13
* flaper87 has 10s lag14:13
flaper87kairat: it is, AFAIK14:13
kairatflaper87, ok, need to review it again, thanks14:13
flaper87There's also a reason why we call it priorities list and not "exclusive list of things we'll accept"14:14
flaper87The process is new and these questions are awesome14:14
nikhil_kkairat: you potentially have 30 mins to move fwd for your spec at drivers' mtg14:14
Jokke_kairat: the point is that due to the fact that we're doing major rework around our core functionalities, we do not want to have multiple things parallel poking those, so if we break something we have decent idea what actually broke it14:14
nikhil_kdedicated mins14:14
flaper87lets clarify them so we have a clearer process14:14
flaper87kairat: if it's not clear enough on the priorities spec, let me know and I'll happily amend it14:15
*** bobh has joined #openstack-meeting-414:15
* nikhil_k still doesn't know the spec :P14:15
kairatThanks guys=)14:15
flaper87nikhil_k: http://specs.openstack.org/openstack/glance-specs/priorities/mitaka-priorities.html14:15
flaper87#link http://specs.openstack.org/openstack/glance-specs/priorities/mitaka-priorities.html14:15
flaper87ok, moving on (unless there are other questions)14:15
nikhil_kflaper87: thanks. I was curious about kairat's one.14:16
flaper87nikhil_k: ah, sorry. misunderstood14:16
* flaper87 (facepalm)14:16
flaper87#topic Glance v2 additional filtering https://blueprints.launchpad.net/glance/+spec/v2-additional-filtering https://review.openstack.org/#/c/197388/ (slow progress) <- required for Nova v2 adoption (mfedosin)14:16
*** openstack changes topic to "Glance v2 additional filtering https://blueprints.launchpad.net/glance/+spec/v2-additional-filtering https://review.openstack.org/#/c/197388/ (slow progress) <- required for Nova v2 adoption (mfedosin) (Meeting topic: Glance)"14:16
flaper87that's a long topic name14:16
kairatnikhil_k, https://review.openstack.org/#/c/233687/14:16
flaper87:D14:16
mfedosinoh yes14:16
flaper87mfedosin: floor is yours14:16
abhishekkhttps://review.openstack.org/#/c/233687/14:16
abhishekknikhil_k: ^14:16
mfedosinI tried to explain the issue14:17
*** memogarcia has joined #openstack-meeting-414:17
mfedosinso, yeah - we have this spec merged in Liberty14:17
mfedosinbut the progress is slow :(14:17
flaper87mfedosin: FWIW, I have re-propossed it for Mitaka14:18
mfedosinand we really need this feature to port Nova to v214:18
flaper87but we need commitment from someone14:18
* flaper87 can't find the link14:18
flaper87#link https://review.openstack.org/#/c/230971/14:18
flaper87that one14:18
*** woodard has joined #openstack-meeting-414:18
flaper87What exactly do you need?14:19
mfedosinso I'm okay to take it on and start writing the code14:19
flaper87mind expanding a bit so we're all on the same page14:19
mfedosinI need this feature asap14:19
mfedosinbecause it blocks v2 image-list for Nova14:19
Jokke_mfedosin: is that the piece we discussed with Jay in the Tokyo?14:19
mfedosinJokke_: yes14:19
mfedosinnot exactly - I wanted to implement it in the client14:20
mfedosinbut having it on the server side is perfect14:20
nikhil_kthanks kairat, abhishekk, mfedosin14:20
Jokke_well if we get it working ;P14:20
flaper87mfedosin: I don't think ppl here know exactly what you need14:20
mclarenIs anything in particular blocking this? Or is it just reviews?14:20
flaper87I do :P14:20
flaper87but please, explain to others14:20
flaper87mclaren: I think we need to get the spec in again and the code up14:21
flaper87:D14:21
*** sdake has quit IRC14:21
mclarenok, so paperwork...14:21
flaper87mclaren: right :D14:21
nikhil_kwait, this is changes-since correct?14:21
kairatmclaren, it doesn;t pass tests14:21
*** sdake has joined #openstack-meeting-414:22
mfedosinI wish Steve to be here to talk about it14:22
Jokke_nikhil_k: yes14:22
kairatand progress on this feature is quite slow14:22
mfedosinnikhil_k: yes, it's kindof changed since14:22
flaper87nikhil_k: yup14:22
mclarenOk, so Steve is blocking us :-)14:22
flaper87sorta14:22
nikhil_kI see, thanks all.14:22
Jokke_so we need some way to filter our output to simulate changed-since so we can keep nova API unbroken14:22
flaper87I'll ping Steve and get his feedback and ask him if he's fine with us taking this over14:22
mfedosinso, if he doesn't mind we can implement it14:22
mfedosinme and kairat14:23
* flaper87 is not sure if his messages are reaching destination14:23
mfedosinflaper87: please do :)14:23
flaper87:D14:23
mfedosinI can ping him as well14:23
flaper87ok ok14:23
flaper87Lets get this going14:23
mclarenhey I'll ping him too!14:24
flaper87mfedosin: then don't wait for me14:24
kairatheh14:24
flaper87mfedosin: when you do, please, update the spec14:24
flaper87:)14:24
mfedosinlet's ping him all :D14:24
flaper87it needs a nick of the person who's going to work on this14:24
mfedosinflaper87: yep, I will update it14:24
nikhil_kjust send am email14:24
flaper87after that, we can merge that spec. I'll re-read it to make sure it doesn't have weird impacts on the rest of the work14:24
nikhil_ka*14:24
*** jmckind has joined #openstack-meeting-414:24
flaper87email + ping + sms + telegram14:25
flaper87done14:25
flaper87:D14:25
nikhil_kforgot pager14:25
nikhil_k:P14:25
flaper87damnit14:25
flaper87:(14:25
flaper87:D14:25
flaper87mfedosin: anything else ?14:25
mfedosinnope sir14:25
flaper87sweet, thanks for working on that14:25
flaper87#topic Glance upgrades (flaper87)14:25
*** openstack changes topic to "Glance upgrades (flaper87) (Meeting topic: Glance)"14:25
Jokke_flaper87: did you send a fax to the office?14:26
*** memogarcia has quit IRC14:26
flaper87I don't really have much to say here and it's perhaps an open question. How do we feel about the upgrade process in Glance? What are we missing?14:26
nikhil_kwhich upgrades? API, DB, other (service) imports?14:27
mclarenDocumentation?14:27
flaper87I think we haven't revisited this topic in a bit and, while we have migrations in place, I think it'd be great to check if there's something we need to do to improve it14:27
flaper87Everything Juno -> Kilo -> Liberty -> Mitaka14:27
flaper87It's a wide open question14:27
nikhil_kyeah, good question14:27
nikhil_khas anyone tried it ?14:27
flaper87There's a lot of work on communicating what the services' upgrade story is14:28
flaper87Whether they support upgrades AND whether they support rolling upgrades14:28
mclarennikhil_k: Not since a few releases ago unfortunately...14:28
flaper87I've been meaning to take some time to test the above but I wanted to ask if ppl have given that a try14:28
nikhil_kthanks mclaren14:29
flaper87ok, I guess we need to clear that story a bit14:29
* flaper87 wonders if rosmaita has done upgrades14:29
nikhil_kI will put this in my TODO list for the first few items when fully back.14:29
nikhil_kI doubt it14:29
flaper87I'll start an etherpad to collect thoughts and issues about this14:29
flaper87nikhil_k: ah, nice14:29
flaper87thanks14:29
nikhil_kflaper87: do you have time for explaining rolling upgrade expectations?14:29
* flaper87 removes that from his todo list14:29
flaper87:P14:29
flaper87Sure14:30
flaper87tl;dr: The expectation is that you can upgrade 1 glance-api node at a time to avoid having down times14:30
abhishekki have tried nova's online schema migration from juno >> kilo14:30
abhishekkbut they have reverted it now14:30
flaper87sometimes that's complicated when there are schema migrations, hence versionobjects14:31
*** fawadkhaliq has joined #openstack-meeting-414:31
Jokke_flaper87: I don't think the API side is our problem14:31
nikhil_kgotcha, I am recollecting a bit on vo now.14:31
*** jmckind is now known as jmckind_14:31
Jokke_flaper87: problem is when we do the DB migration and need to roll the registries14:31
flaper87If we have a problem in the db side, I believe it'll affect the API as well14:32
flaper87:)14:32
*** memogarcia has joined #openstack-meeting-414:32
nikhil_kflaper87: I thought the same14:32
* nikhil_k is unsure if we added virtual size in juno or not14:32
flaper87if we have an old glance-api node running and we migrate the db under-the-hood, the glance-api node could break14:33
flaper87and that will cause a downtime14:33
flaper87nikhil_k: thanks for taking this14:33
flaper87nikhil_k: I think it was Icehouse14:33
Jokke_flaper87: our API <--> Registry communications have been really stable ... we really haven't introduced too huge expectations from the DB (on old functionality)14:33
flaper87the same applies to the registry node14:33
flaper87you need to upgrade those14:33
flaper87and there are environments running without the registry service14:34
flaper87pure glance-api envs14:34
Jokke_flaper87: what I mean is, we most of the time survive just well if we upgrade API nodes and don't expect new features to work before reg/db has been upgraded14:34
nikhil_kAlso, can do do guarantees on sub-set of the API. say only CRUD on image+properties?14:34
*** rosmaita has joined #openstack-meeting-414:34
flaper87Jokke_: I believe that's not a good expectation and surviving that is pure luck14:35
flaper87:D14:35
nikhil_kWe had a few API changes to metadef APIs but that's admin only and not sure of the operator expectations on those14:35
Jokke_but as you said other way around is the pain and we need to roll our registries at the point we run db migrations14:35
mclarenwe need to document what order to upgrade things in (if we haven't done so)14:35
flaper87mclaren: that was part of my question :D14:35
nikhil_khuh14:35
flaper87I don't think we've ever talked about this explicitly and we've just been happy with db migrations14:35
flaper87which are great but not enough to make transitions smooth14:36
nikhil_kit's interesting that a IT would want to upgrade API before DB14:36
nikhil_kIT team14:36
flaper87ok, it seems we need clarify our story here and, as mclaren said, document it14:36
flaper87nikhil_k: indeed14:36
flaper87nikhil_k: looking forward to your findings14:36
mclarenmy 2 cents is that things will probably mostly work ok, but if we really start looking we could find potential issues. Eg I think the way the v2 registry error handling is done assumes the same code is on the API and registry nodes14:37
*** sdake has quit IRC14:37
flaper87mclaren: ++14:37
nikhil_kespecially given the possibility of DB sync going corrupt w/ restarts, extraneously long DB upgrades etc.14:37
flaper87I think it's time for us to look for those issues and improve our story there. It'd be great to at least identify them and work on a long term plan to fix them14:37
Jokke_and it will get trickier when you are running API only implementation14:37
*** sdake has joined #openstack-meeting-414:38
mclarensounds like a mission for the next release :-)14:38
Jokke_++14:38
flaper87not saying this has to be all fixed in Mitaka - I mean, that'd be awesome - but definitely something for N14:38
flaper87mclaren: out of my MIND!14:38
flaper87>.>14:38
nikhil_koh, there was a question on the upgrades for libraries breaking stuff14:38
flaper87Identifying the issues now will help us build a plan for N and O14:39
nikhil_k++14:39
flaper87ok14:39
flaper87moving on, unless there are more questions14:39
mfedosinNO plans :)14:39
*** Claudio2 has joined #openstack-meeting-414:39
nikhil_kbut I will take this item for mitaka14:39
nikhil_kif ok14:39
Jokke_nikhil_k: absolutely not, you must not try to upgrade ;)14:40
* nikhil_k ties with co-qa liaison responsibilities14:40
flaper87I'd like to have time for the reviews list14:40
flaper87nikhil_k: we can discuss this further on -glance when you're back14:40
flaper87:D14:40
flaper87#topic Bug / Review Triage Day  (flaper87)14:40
*** openstack changes topic to "Bug / Review Triage Day  (flaper87) (Meeting topic: Glance)"14:40
*** memogarcia has quit IRC14:40
flaper87real quick: I'm thinking of organizing a Bug/Review triage/squash day. I know some folks are still out or not fully back on brain power14:40
flaper87nikhil_k: +114:40
*** TravT has joined #openstack-meeting-414:40
flaper87so, I'm not going to propose it for this week, or next week.14:40
flaper87What about the week after next week ?14:41
kairatbig + 1 on this14:41
mclarensure thing14:41
mfedosinI'm in14:41
flaper87We're getting closer to M-1 and I'd like to have 1 of these days on every milestone14:41
nikhil_kworks for me, thanks!14:41
flaper87AWESOME!14:41
kairatIt would be useful for other to help glance fixin g the updated bugs14:41
flaper87sweet14:41
* flaper87 dances14:41
Jokke_flaper87: So Mon 23rd it is?14:42
flaper87I'll send an email out with a proposed day14:42
bpoulosin the US, we have Thanksgiving week then14:42
flaper87Jokke_: yeah, that week14:42
flaper87bpoulos: oh uh, you US ppl14:42
nikhil_kohai bpoulos, you're lurking :)14:42
Jokke_flaper87: not that week, Monday14:42
flaper87>.>14:42
flaper87bpoulos: do ppl take the whole week of ?14:42
*** memogarcia has joined #openstack-meeting-414:42
Jokke_exactly for the reason bpoulos brought up :P14:42
nikhil_kcan't believe he missed thanksgiving week14:42
bpouloseveryone takes Thursday and Friday off, but some people take off the whole week14:42
bpoulosit depends on how far away they live from family usually14:42
flaper87well, Mon 23rd works me14:42
flaper87I'll send 2 dates, one for next week and one for the week after next week14:43
flaper87we can vote on the m-l14:43
Jokke_++14:43
flaper87bpoulos: thanks for brining that up14:43
flaper87bringing, even14:43
bpoulosflaper87: np14:43
flaper87ok, moving on14:43
flaper87#topic Reviews / Bugs14:43
*** openstack changes topic to "Reviews / Bugs (Meeting topic: Glance)"14:43
flaper87glance_store broken ceph gate -> https://review.openstack.org/#/c/243706/14:43
flaper87not sure who put that there14:43
flaper87(or any of those)14:44
mfedosinI did14:44
flaper87mfedosin: was that you?14:44
mfedosinyes14:44
Jokke_mfedosin: so is glance_store breaking ceph or other way around?14:44
flaper87anything specific you want to say? or just raise awareness ?14:44
mfedosinwe have it broken and we can't merge commits to glance_store14:44
*** cpallares has joined #openstack-meeting-414:44
flaper87btw, I'll do a triage on the reviews today/tomorrow to refresh the dashboard14:45
mfedosinjust raise awareness14:45
nikhil_kwhy don't we keep these optional14:45
flaper87:D14:45
mfedosinbecause I have no idea how to fix it14:45
nikhil_k(Sorry that was a actual question)14:45
kairatnikhil_k, there is a lot of installations with ceph+glance14:45
Jokke_mfedosin: ok, and have you checked is it only master or are all branches same way broken?14:45
kairatAFAIK14:45
mfedosinand it blocks our trust work for swift driver14:45
nikhil_kyeah, but not all drivers should have to wait on the gate14:45
flaper87Multitenant swift driver doesn't work? https://bugs.launchpad.net/swift/+bug/151102514:45
openstackLaunchpad bug 1511025 in OpenStack Object Storage (swift) "Image download with multi tenant true fails" [Undecided,New]14:45
mclarenis there a bug in for the broken gate?14:45
flaper87nikhil_k: ++14:45
flaper87we need to fix our functional tests for glance_store14:45
flaper87kragniz: was working on that but he doesn't like us anymore (joke)14:46
nikhil_kI think the core reviewers would be wise enough to notice the failure and stop the ceph patches in this case14:46
mfedosinfunctional test are ok14:46
mfedosintempest is broken :)14:46
flaper87Multitenant swift driver doesn't work? https://bugs.launchpad.net/swift/+bug/151102514:46
openstackLaunchpad bug 1511025 in OpenStack Object Storage (swift) "Image download with multi tenant true fails" [Undecided,New]14:46
flaper87ops14:46
flaper87Trusts for Glance are ready btw :) welcome to review https://review.openstack.org/#/c/229878/14:47
flaper87that's the work for trusts14:47
mfedosinand yeah - we can't make multitenant driver work14:47
flaper87(please, note the spec hasn't landed)14:47
flaper87feel free to review but abstain from approving until the spec lands14:47
mfedosinand it seems like bunting can't neither14:47
nikhil_klooks like a bunch of auth failures there14:47
mclarenmultitenant broken? :-( we really need all our stores tested in the gate14:47
buntingbunting: Sorry?14:47
buntingmfedosin: Sorry?14:48
mclarenbunting: https://bugs.launchpad.net/swift/+bug/151102514:48
openstackLaunchpad bug 1511025 in OpenStack Object Storage (swift) "Image download with multi tenant true fails" [Undecided,New]14:48
kairatbunting, you found a bug14:48
mfedosinbunting: is it your bug https://bugs.launchpad.net/swift/+bug/1511025 ?14:48
flaper87mclaren: ++14:48
flaper87I wish someone would take what kragniz started14:48
buntingAh right :)14:49
nikhil_k#link http://logs.openstack.org/06/243706/1/check/gate-tempest-dsvm-full-ceph-src-glance_store/1420d1b/console.html#_2015-11-12_12_45_56_22014:49
mfedosinmclaren: can you fix bug/1511025 ?14:49
mclarenflaper87: bunting is the new kragniz ;-)14:49
kairatheh14:50
mclarenmfedosin: magically? :-)14:50
nikhil_kI think we should move this to non-voting to avoid last minute screams for stuff like security patches blocked on unrelated gate14:50
flaper87mclaren: w00000000h000000000000000000000000014:50
flaper87bunting: well, sir. You found yourself a new task14:50
flaper87:D14:50
buntingflaper87: Whooooo ):14:50
bunting:)14:50
flaper87:D14:50
flaper87#topic Open Discussion14:50
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"14:50
mclarenmfedosin: myself and bunting can hopefully take a look, I definitely want that fixed...14:51
mfedosinmclaren: +114:51
flaper87anything folks want to bring up or talk about?14:51
mclareno/14:51
buntingmclaren: ++14:51
mfedosinafter that we can start working on trusts for MT driver14:51
bpoulosI'd like to bring something up about the image signature verification14:51
flaper87mclaren: same here but I don't think I'll have time to make it happen other than providing reviews14:51
*** jgjhgsonchn88523 has joined #openstack-meeting-414:51
flaper87bpoulos: shoot14:51
bpoulosat the summit, we decided to leave the checksum as-is, and then add a second, configurable hash14:51
bpouloscurrently, the signature is of the checksum, which is MD5, which is insecure14:51
bpoulosand discussing this feature with Nova, they are completely opposed to ever supporting anything with MD514:52
bpoulosthey want to sign the image data directly, rather than signing a hash of the image data14:52
bpouloswould the glance community be opposed to doing the signature verification where the checksum is computed?14:52
bpoulosthis would only occur if the signature properties are present14:52
bpoulosinitially, there was opposition to a second hash being done14:52
*** zeih_ has joined #openstack-meeting-414:52
bpoulosbut now it seems that as long as the hash is optional, the community is ok with it14:52
bpoulosbased on the discussion about the configurable hash at the summit14:53
*** zeih has quit IRC14:53
Jokke_bpoulos: that kind of makes sense ... _but_ how big performance impact using more complex algo's there would cause?14:53
*** jmckind_ has quit IRC14:53
*** tekentaro has joined #openstack-meeting-414:53
*** sdake has quit IRC14:53
flaper87mmh14:53
bpoulosit's just doing a hash such as SHA-256 or SHA-51214:53
bpoulosit would be the same as computing a separate configurable hash14:53
flaper87gotcha14:54
nikhil_kbpoulos: that would mean, we needing a published protected image property?14:54
bpoulosand it would only be what the user requested for the signature14:54
bpouloswe could use the existing signature metadata properties14:54
bpouloswithout issue14:54
bpouloswe already define a signature hash method14:54
Jokke_makes sense to me14:54
flaper87bpoulos: has this been brought up on the m-l ? I still have some backlog there14:54
flaper87where did the nova discussion happen?14:54
nikhil_kflaper87:  not yet14:55
bpoulosno, the discussion has been on the nova spec14:55
bpouloslet me grab the link14:55
tekentaroany plans for adding new cores to team?, all other teams are expanding14:55
flaper87tekentaro: there are plans14:55
bpouloshttps://review.openstack.org/#/c/188874/14:55
flaper87however, the fact that other teams are expanding, it doesn't mean we should (hope this doesn't come out harsh)14:55
Jokke_flaper87: ++14:55
tekentaroflaper87: ok14:55
Jokke_peer pressure might be difficult to resist14:56
*** IlyaG has joined #openstack-meeting-414:56
*** memogarcia has quit IRC14:56
* flaper87 resists peer preasure very well unless there's alcohol involved14:56
* flaper87 stfu14:56
nikhil_kbpoulos: do we need to have published protected image property?14:56
bpoulosno, i don't believe so14:57
flaper87bpoulos: it makes sense to me as well, fwiw14:57
nikhil_khow do we ensure the consistency/existence of it then?14:57
bpouloswe check for the optional properties14:57
tekentarojokke_: i understood, I just remembered we have reduced 2-3 members month before14:57
bpoulosjust like we're doing now14:57
flaper87and I trust Daniel's opinions14:57
flaper87bpoulos: wonder if we could bring this up on the m-l ?14:57
bpoulosflaper87: sure, if that's what you'd prefer14:58
nikhil_kbpoulos: yeah, but I think we need to have it protected.14:58
bpoulosnikhil_k: why?14:58
nikhil_kand now I think we are different page14:58
rosmaitadon't  mean to interrupt, but anyone interested in the image import refactor, please look at the spec and leave comments: https://review.openstack.org/#/c/232371/ ... so far only flaper87 and mclaren have commented (which is good, they are high-quality comments, but now is the time to get your opinion known)14:58
Jokke_tekentaro: we really didn't ... those people reduced themselves long time ago. We just did the paperwork14:58
mclarenrosmaita: got a few mins to chat after the meeting?14:58
nikhil_kbpoulos: sorry, in my dictionary prot prop != base prop14:58
*** baohua has quit IRC14:58
flaper87not saying we should ask nova to accept it but rather discussing how we can do it in glance14:59
flaper87and get feedback from nova and other folks14:59
flaper87bpoulos: your work impacts several services and it's super important for the community14:59
* flaper87 senses the lag slowing down his messages14:59
nikhil_kbpoulos: so, we will have it optional but by default restricted to teh user and documented so that it will be used for signing14:59
rosmaitamclaren: got searchlight meeting, how about 11:00 utc in openstack-glance ?14:59
bpoulosi'll bring it up on the m-l so we can discuss further there14:59
flaper87ok, we're running out of time14:59
flaper87rosmaita: ++14:59
flaper87rosmaita: ++14:59
*** memogarcia has joined #openstack-meeting-414:59
mclarenrosmaita: 11:00?15:00
flaper87rosmaita: ++15:00
flaper87one more time15:00
flaper87rosmaita: ++15:00
flaper87:D15:00
flaper87ok, out of time15:00
*** sjmc7 has joined #openstack-meeting-415:00
flaper87thanks ppl15:00
mclarenthanks!15:00
kairatthanks15:00
nikhil_krosmaita: I don't want to leave comments and disappear for a few days!15:00
nikhil_kthat is quite likely15:00
Jokke_thanks folks15:00
abhishekkthanks15:00
*** kairat has left #openstack-meeting-415:00
rosmaitanikhil_k: that's ok, i will ignore your comments if i don't like them :)15:00
tekentarothank you!15:00
*** tekentaro has quit IRC15:00
bpoulosthanks!15:00
*** dims has quit IRC15:01
nikhil_krosmaita: sure! I have a treat for you in that case :)15:01
* nikhil_k done15:01
*** yingjun has joined #openstack-meeting-415:02
nikhil_k#chairs15:02
nikhil_k#chair15:02
nikhil_knot sure if flaper87 dropped off15:02
nikhil_kwth, let's try15:02
flaper87#endmeeting15:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:02
openstackMeeting ended Thu Nov 12 15:02:52 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-11-12-13.59.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-11-12-13.59.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-11-12-13.59.log.html15:02
TravTthanks, guys!15:03
*** abhishekk has quit IRC15:03
TravT#startmeeting openstack search15:03
openstackMeeting started Thu Nov 12 15:03:17 2015 UTC and is due to finish in 60 minutes.  The chair is TravT. 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
sjmc7ello15:03
david-lyleo/15:03
lakshmiSo/15:03
TravThowdy!15:03
yingjun;)15:04
nikhil_ko/15:04
TravTOk, here's our agenda: https://etherpad.openstack.org/p/search-team-meeting-agenda15:04
TravTtake a look and see if there's anything to add15:04
TravTalthough we've got a really full plate today, i think.15:05
rosmaitao/15:05
*** bpoulos has left #openstack-meeting-415:05
gb21o/15:05
TravT#topic Feature request workflow (blueprints, specs, bugs, etc) (TravT)15:05
*** openstack changes topic to "Feature request workflow (blueprints, specs, bugs, etc) (TravT) (Meeting topic: openstack search)"15:05
*** cpallares has left #openstack-meeting-415:06
TravTI sent a message to ML: http://permalink.gmane.org/gmane.comp.cloud.openstack.devel/6878615:06
*** yamamoto has joined #openstack-meeting-415:06
*** dims has joined #openstack-meeting-415:07
TravTsummary is, I think the time has come to document our feature request processes, and to specifically include how we handle feature requests that are more complicated15:07
sjmc7i did wonder what the reason for seperate -specs repositories was, whenever that started (juno?)15:08
TravTthat is supporting a way to review requests that are more complicated than launchpad effectively handles15:08
sjmc7but otherwise i’m in favor of being able to review specs in gerrit15:08
TravTi'm not sure, maybe to support separation of core spec reviewers and core code reviewers?15:09
nikhil_ksjmc7: it also shows up in a clean way and consolidated manner (across cycles) on specs.openstack.org15:09
TravTalso many projects have multiple repos,15:09
rosmaitait's also a source of documentation15:09
rosmaitaspecs.openstack.org15:10
*** Claudio2 has quit IRC15:10
nikhil_kthere was a good question if specs are documentation or workflow process for feature proposal15:10
rosmaitawhat nikhil_k said15:10
sjmc7i think both - i’m ok keeping them in the /docs directory in the source tree for now15:10
david-lyleI think it can only be documentation of the plan15:10
nikhil_kTravT: LP can be spammed with blueprints and fortunately hasn't been the case with SL15:11
david-lylefinal and spec may not precisely align15:11
*** lakshmiS_ has joined #openstack-meeting-415:11
nikhil_kalso, one critical update from cross project mtg15:11
TravTso, with what I proposed is that we basically are doing specs when needed, but they go in our source doc tree.15:11
TravThere's an example: https://review.openstack.org/#/c/243386/15:11
nikhil_kthe release mgmt is going away from LP into a different tool for bugs15:11
*** lakshmiS has quit IRC15:11
*** yamamoto has quit IRC15:11
nikhil_kthat being said, teams would still have the option to maintain their own LP page15:11
rosmaitaTravT: i'm not sure what the benefit of being non-standard on this is?15:12
*** bunting has left #openstack-meeting-415:12
TravTi debated a bit on that as well... here was some of my thinking.15:12
TravTwe document everything else in one location for searchlight15:12
*** jmckind has joined #openstack-meeting-415:12
rosmaitabut as david-lyle said, that's mostly finished product, not design15:13
TravTwhy do we have to go somewhere else (diff website, diff source repo) etc to document designs15:13
*** memogarcia has quit IRC15:13
rosmaitaTravT: because some will be approved, and of those, only some will actually be implemented15:14
david-lyleyeah approving a spec or bp does not directly correlate to implementation15:14
nikhil_k(nice rosmaita!) and rest of them put in the bucket list :)15:14
*** woodard has quit IRC15:14
TravTyeah, that part i get, which is why I included a status in the feature design template15:15
TravThttp://docs-draft.openstack.org/81/243881/2/check/gate-searchlight-docs/8270651//doc/build/html/feature-designs/template.html15:15
TravTbut there was one other idea...15:15
*** lakshmiS has joined #openstack-meeting-415:15
TravTcan we sometimes have feature requests be submitted as though there were actual doc updates?15:15
TravThttp://docs-draft.openstack.org/81/243881/2/check/gate-searchlight-docs/8270651//doc/build/html/feature-requests-bugs.html#as-user-docs15:15
*** MarkAtwood has joined #openstack-meeting-415:15
*** rbak has joined #openstack-meeting-415:15
TravTsome of this is coming from experience on horizon where we seem to be in a constant state of trying to get people to document there features.15:16
TravTs/there/their15:16
*** memogarcia has joined #openstack-meeting-415:16
TravTand was trying to think if there was a way to streamline it all15:16
nikhil_kgood luck with that :)15:17
yingjunMaybe it is better to make a new directory to hold the implemented feature?15:17
david-lyleTravT: that was just poor review standards, shouldn't have happened15:17
TravTbut if you guys think we should just do specs, we can do that too.  Will just need to setup spec repo15:17
sjmc7i’m fine with either15:17
rosmaitaTravT: we definitely want to make sure there's something to find for searchlight at specs.openstack.org15:17
sjmc7agree that being standard is probably more sensible15:17
rosmaitacould be a redirect, i guess15:18
*** lakshmiS_ has quit IRC15:18
nikhil_k+115:18
rosmaitabut that could be confusing, too15:18
nikhil_kif we can setup docs/ in searchlight to be shown at specs.openstack.org it would be great15:18
david-lyleI would be reluctant to merge spec and code repos, but what tool houses specs, meh15:18
rosmaitaTravT: i appreciate your desire to keep things streamlined, but it might be better overall to go with the flow15:18
rosmaitaof the rest of openstack15:18
TravTokay, that sounds reasonable.15:18
TravTi'll put up a request for spec repo.15:19
rosmaita+115:19
nikhil_kTravT: the reason is that we would be playing cat and mouse while the overall flow is driven by release team15:19
TravTbut, please give comments on rest of workflow15:19
TravThttp://docs-draft.openstack.org/81/243881/2/check/gate-searchlight-docs/8270651//doc/build/html/feature-requests-bugs.html#workflow15:19
* david-lyle hopes to be watching 40 repos by the end of Mitaka15:19
TravTbasically, not require a spec for every feature.15:20
nikhil_k#link https://review.openstack.org/#/c/24388115:20
TravTonly when needed15:20
TravTor do you guys think one should always be required?15:21
TravTwhich is contrary to previous discussions15:21
* nikhil_k fine either way15:22
david-lyle+1 for less overhead for lightweight changes15:22
*** praveens has joined #openstack-meeting-415:22
sjmc7for anything that’s really straightforward i don’t think it’s necessary15:22
* nikhil_k actually doesn't care much about what process to follow too. just giving feedback.15:22
sjmc7much as i enjoy nitpicking reviews over people’s grammar15:22
rosmaitathe argument for a spec is TravT's documentation point15:22
rosmaitait forces some doc to work from for the "real" doc15:22
david-lylesjmc7: I think it's just your misunderstanding of "proper" English :P15:23
nikhil_kha15:23
nikhil_kno approvals without at least one rap in the spec15:23
sjmc7it’s going to make a comeback, any day now. i’m not that bothered either, but i think the project’s still small enough we can be a bit informal15:24
TravTI like lightweight where we can, because I can still go through and manage them fairly easily.15:24
TravTOk, I'll amend the review to have a spec repo.15:25
rosmaitamaybe we propose bp only for small feature, but require a section "how this would be documented for users"15:25
nikhil_ksorry I have to drop off for travel. will catch from logs later.15:25
TravTthanks nikhil_k15:25
rosmaitanikhil_k: travel safely!15:25
TravTnext boring stuff topic...15:25
TravT#topic Reno release notes:15:25
nikhil_kthanks guys!15:25
*** openstack changes topic to "Reno release notes: (Meeting topic: openstack search)"15:25
* nikhil_k &15:26
TravThttps://blueprints.launchpad.net/searchlight/+spec/setup-reno-based-release-notes15:26
TravTbasically, relmgr wants us to put a little yml file in the repo for big features15:26
TravTand release notes will be generated from that15:26
TravTAre there any volunteers to set this up for searchlight (I can if nobody else is interested)?15:27
lakshmiSi can try15:27
*** xingchao has quit IRC15:27
TravTthx Lakshmi.15:28
*** igordcard__ has quit IRC15:28
TravTI'll assign that bp to you15:28
lakshmiSok15:28
*** igordcard has joined #openstack-meeting-415:28
rosmaitalakshmiS: doug h just did it for glance15:28
*** memogarcia has quit IRC15:29
TravTok, now slowly move to maybe more interesting15:29
lakshmiSthanks rosmaita: will take a look15:29
TravT#topic Summit review15:29
*** openstack changes topic to "Summit review (Meeting topic: openstack search)"15:29
TravTThe presentation Steve, Lakshmi, and I did is available on youtube.15:29
TravT#link https://www.youtube.com/watch?v=0jYXsK4j26s15:30
TravTFYI.15:30
TravTThe venue was rather challenging... we were in the back corner of the marketplace pretty far from the main conference sessions and the design summit15:30
TravTI counted around 45 - 50 attendees15:30
TravTbut there were glance and horizon design sessions at the same time15:31
*** jckasper has quit IRC15:31
TravTwhich were about a 15 minute walk away15:31
*** zehicle has joined #openstack-meeting-415:31
TravTBut overall, it went well.15:31
*** rob__ has joined #openstack-meeting-415:32
TravTI took all the priorities and integrations and opened blueprints for them15:32
*** nkrinner has quit IRC15:32
TravTand took a swag at priority15:32
TravThttps://blueprints.launchpad.net/searchlight15:32
TravTif you disagree on any, let me know15:33
rosmaitalakshmiS: i think these are the relevant changes for reno: https://review.openstack.org/#/c/241323/ , https://review.openstack.org/#/c/243302/, https://review.openstack.org/#/c/241322/ , https://review.openstack.org/#/c/241321/15:33
TravTBut, my question is whether or not you all would be interested in doing a BP review and prioritization session next week?15:34
sjmc7i added a couple more yesterday (at the top of the ‘undefined’ list)15:34
TravTyeah, i also want to add one related to our /index API15:34
*** praveens has quit IRC15:34
*** sdake has joined #openstack-meeting-415:35
lakshmiSthanks rosmaita15:35
*** memogarcia has joined #openstack-meeting-415:35
sjmc7i think we have a pretty good idea of the priorities coming out of the summit, that list looks good15:35
lakshmiSTravT: that sounds good15:35
rosmaitaTravT: +115:35
sjmc7i’d be ok doing more design type reviews once there are more fleshed out specs15:35
TravTi'm not sure what lakshmiS and rosmaita are +1'ing15:36
rosmaitaBP review & prioritization next week15:36
david-lyleprobably that the prioritized list meets expectatoins15:36
lakshmiSi think its good to get everyone to review the list on BP15:36
david-lyleor that15:36
david-lyle:P15:36
*** jmckind_ has joined #openstack-meeting-415:36
TravTok, i can do tuesday or wednesday at the same time or later next week15:37
*** jmckind_ has quit IRC15:37
rosmaitaTravT: tues,wed same time works for me15:38
*** jmckind has quit IRC15:38
*** jmckind_ has joined #openstack-meeting-415:38
TravTlet's plan on Tuesday 15:00 UTC.  We'll start in the #openstack-searchlight15:38
TravTlet's get to some technical topics...15:39
*** jmckind_ has quit IRC15:39
*** sdake_ has joined #openstack-meeting-415:39
TravT#topic Swift integration15:39
*** openstack changes topic to "Swift integration (Meeting topic: openstack search)"15:39
TravTDo we have briancline?15:39
TravTdoesn't look like it.15:39
*** sdake has quit IRC15:39
lakshmiSnope15:39
TravTWell, I think it'd be good to share status updates with others.15:40
TravTsjmc7 you went to the meeting yesterday... want to give a summary?15:40
*** fawadkhaliq has quit IRC15:40
*** jmckind has joined #openstack-meeting-415:40
sjmc7the swift folks aren’t keen on bring in dependencies for things in tree, particularly oslo things (although as brian pointed out the keystone middleware brings in most of oslo)15:41
lakshmiS:(15:41
sjmc7but in principle there’s support for adding notifications15:41
*** jmckind has quit IRC15:41
sjmc7so something simple out of tree is our best bet for now15:41
TravT#link http://eavesdrop.openstack.org/meetings/swift/2015/swift.2015-11-11-21.00.log.html15:42
TravTstarting at 21:31:0915:42
TravTFYI15:42
*** jmckind has joined #openstack-meeting-415:42
sjmc7that was the summary, really, plus a lot of bike shedding15:42
TravTsjmc7: it seemed to me that they were okay with possibly adding a soft dependency15:42
TravTlike they do with keystone15:42
*** jmckind has quit IRC15:42
TravThow does that work for them?15:42
sjmc7you have to install keystonemiddleware separately15:43
TravTso, basically put it in the deploy pipeline?15:43
*** jmckind has joined #openstack-meeting-415:43
sjmc7they didn’t seem very keen on adding anything in the swift tree15:43
*** rosmaita_ has joined #openstack-meeting-415:43
sjmc7yeah, then enable the middleware15:43
*** sdake has joined #openstack-meeting-415:43
sjmc7there is some precedent for external middleware15:43
*** daddyjoseph97 has joined #openstack-meeting-415:44
*** baoli has quit IRC15:44
lakshmiSthat would make it tough to have code sit in swift which depends on oslo directly15:44
*** jmckind has quit IRC15:44
sjmc7right - nothing can be added to requirements.txt15:44
sjmc7so the question is whether the file that sends notifications lives in swift or not, and the feeling i got was ‘not’, at least for now15:44
*** jmckind has joined #openstack-meeting-415:44
*** rosmaita has left #openstack-meeting-415:45
sjmc7but i think the best plan is to put something together to show them15:45
sjmc7nobody really had a good handle on what would be involved; they don’t use the oslo libraries much15:45
*** rosmaita_ is now known as rosmaita15:45
*** numans has quit IRC15:45
*** jmckind has quit IRC15:45
TravTso, this could be put into searchlight repo, but that might be problematic for packaging and deploy15:45
TravTi'm not a packaging person, so i don't know15:46
*** baoli has joined #openstack-meeting-415:46
sjmc7no, i don’t think that’s a good idea15:46
*** memogarcia has quit IRC15:46
lakshmiSagree with sjmc7 on have it use oslo and start discussing after a patch15:46
*** salv-orlando has quit IRC15:46
sjmc7i think a good first step would be to put some middleware together, and possibly proopse it as a review15:46
sjmc7alternatively stackforge it for now15:46
TravTstart it as a review15:46
*** dshakhray has quit IRC15:46
sjmc7i’m going to cobble something together today i think15:46
TravTi'm sure it'll get bumped out.15:46
sjmc7yeah15:47
TravTbut, might as well get it up there for their input15:47
TravTmaking it easy to review is important15:47
*** sdake_ has quit IRC15:47
sjmc7yep. well, it’s one file and reasonably straightforward15:47
*** jckasper has joined #openstack-meeting-415:47
*** baoli has quit IRC15:48
TravTlakshmiS: were you able to start on the initial indexing for swift?15:48
lakshmiSswift should consider a conditional install based on the notification approach used15:48
lakshmiSyes started on it15:49
lakshmiSwill put WIP patch once i have the basic things working15:50
TravTok.15:50
*** jmckind has joined #openstack-meeting-415:50
TravTdaddyjoseph97: saw you joined.  anything to report related to swift integration?15:50
*** memogarcia has joined #openstack-meeting-415:51
*** Piet has joined #openstack-meeting-415:51
TravTmaybe not...15:51
daddyjoseph97sorry, was in standup...15:52
TravTno worries.15:52
*** baoli has joined #openstack-meeting-415:52
TravTtime is running short, so just will open it up for people to talk about remaining blueprints.15:52
TravT#topic BP review15:52
*** openstack changes topic to "BP review (Meeting topic: openstack search)"15:52
daddyjoseph97I am in favor of conditional install just as briancline had mentioned about dependencies common to keystoneclient15:52
*** numans has joined #openstack-meeting-415:53
TravTsjmc7 put out a request for review here:15:53
*** odyssey4me has joined #openstack-meeting-415:53
TravT#link http://lists.openstack.org/pipermail/openstack-dev/2015-October/077962.html15:53
*** woodard has joined #openstack-meeting-415:54
TravThe and i have chatted a bit about it separately15:54
TravTI think we need this BP into a spec repo for proper review15:54
TravTyingjun: I saw you entered the zaqar BP15:54
*** lakshmiS has quit IRC15:54
sjmc7yeah, i’ll do that once we’re agreed where they’re going15:54
TravThttps://blueprints.launchpad.net/searchlight/+spec/zaqar-notification15:54
*** lakshmiS has joined #openstack-meeting-415:55
TravTyingjun: i will look at it today, but will try to get a spec repo up15:55
TravTi think that one will need it15:55
*** angdraug has joined #openstack-meeting-415:55
TravTgb21: are you around?15:56
yingjunthat’s not me, i think15:56
*** memogarcia has quit IRC15:56
*** mgariepy has joined #openstack-meeting-415:56
*** cloudtrainme has quit IRC15:56
TravToh, my bad.15:56
yingjunno problem:)15:57
TravTWell, i think we've run out of time to have additional effective discussion on these BPs today.15:57
TravTwe can do that in room if needed15:57
TravTanything else from anybody?15:57
TravTok, well, thanks everybody!15:58
*** baoli has quit IRC15:58
sjmc7thanks15:58
TravT#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Thu Nov 12 15:58:26 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-11-12-15.03.html15:58
*** sjmc7 has left #openstack-meeting-415:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-11-12-15.03.txt15:58
rosmaitanope, see you Tues at 15 UTC in #openstack-searchlight15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-11-12-15.03.log.html15:58
*** prometheanfire has joined #openstack-meeting-415:58
*** lakshmiS has left #openstack-meeting-415:58
*** yingjun has left #openstack-meeting-415:58
*** baoli has joined #openstack-meeting-416:00
odyssey4me#startmeeting OpenStack Ansible Meeting16:00
openstackMeeting started Thu Nov 12 16:00:48 2015 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:00
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:00
prometheanfire\o16:01
*** TravT has left #openstack-meeting-416:01
*** BjoernT has joined #openstack-meeting-416:01
*** mattt has joined #openstack-meeting-416:01
cloudnullo/16:01
hughsaundershey16:01
mattto/16:01
*** cindy_ has joined #openstack-meeting-416:01
d34dh0r53o/16:01
BjoernTo/ ?16:01
*** KLevenstein has joined #openstack-meeting-416:01
andymccro/16:01
* palendae waits for rollcall16:01
hughsaundersBjoernT: not sure if you're here?16:02
BjoernTyes16:02
*** oneswig has joined #openstack-meeting-416:02
odyssey4melol, whoops16:02
odyssey4me#topic Agenda & rollcall16:03
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:03
*** egonzalez has joined #openstack-meeting-416:03
palendaeHello!16:03
d34dh0r53o/16:03
oneswig\o16:03
*** memogarcia has joined #openstack-meeting-416:03
KLevensteino/16:03
cloudnullo/ v216:03
cloudnullwelcome oneswig16:04
prometheanfire\o16:04
oneswigcloudnull: thanks, first tiem16:04
prometheanfirewe'll be gentle16:04
odyssey4mewelcome oneswig :)16:05
odyssey4meright, let's get the show on the road16: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
odyssey4meexcept it wasn't last week, or the week before (summit week)16:05
*** Sam-I-Am has joined #openstack-meeting-416:05
Sam-I-Ammoo.16:05
odyssey4me#link http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-10-22-16.02.html16:05
*** bgmccollum has joined #openstack-meeting-416:05
odyssey4meno action items, so all is well16:06
odyssey4me#topic Items in progress or otherwise in need of work16:06
*** openstack changes topic to "Items in progress or otherwise in need of work (Meeting topic: OpenStack Ansible Meeting)"16:06
odyssey4me#topic Installation guide blueprint16:06
*** openstack changes topic to "Installation guide blueprint (Meeting topic: OpenStack Ansible Meeting)"16:06
odyssey4meKLevenstein Sam-I-Am ^ your topic :)16:06
Sam-I-Amyup16:06
*** erikwilson has joined #openstack-meeting-416:07
cloudnullwhat say you ?! :)16:07
Sam-I-AmKLevenstein: moo?16:07
Sam-I-Amok...16:07
Sam-I-Amso here's the thing16:07
KLevensteinmostly I wanted to call attention to it16:07
Sam-I-Amoh, there she is16:07
KLevensteinsince I think it’s important16:07
*** xenolog13 has left #openstack-meeting-416:07
odyssey4meit is :)16:08
odyssey4meare we looking for volunteers to make it happen? or further input of some sort?16:08
Sam-I-Amfurther input16:08
KLevensteinit’s also relevant to various things we’re trying to manage from the rpc-openstack side16:08
Sam-I-Amthe direction it takes (and o-a in general) impacts rpc-openstack16:09
*** stanchan has joined #openstack-meeting-416:09
Sam-I-Amthe original plan was to more or less point to or consume the o-a docs for the generic installation bits... the rpc docs merely augment it with rpc-specific things16:09
odyssey4me#link http://specs.openstack.org/openstack/openstack-ansible-specs/specs/mitaka/install-guide.html16:09
Sam-I-Amhowever, it seems like o-a is taking a turn toward not being opinionated or fully deployable... just modules to consume.16:10
*** sigmavirus24_awa is now known as sigmavirus2416:10
*** baoli has quit IRC16:10
odyssey4menot exactly, but continue16:10
Sam-I-Amwell thats the problem16:10
Sam-I-Amdocs doesnt really know whats happening with o-a16:10
cloudnullSam-I-Am:  no, OSA will break the modules out but the repo will still continue to be deployable16:11
*** jckasper has quit IRC16:11
KLevensteinwe could use input on the spec, then, for more clarity on what needs to be documented, and how.16:11
cloudnull's/modules/roles/'16:11
Sam-I-Amwe're trying to figure out if we should create (or continue to maintain) an entirely separate install guide for rpc that covers all of the things rpc needs... or expect that we can consume the o-a install guide.16:12
Sam-I-Amcloudnull: submodules?16:12
odyssey4meKLevenstein ah, I think when the spec was approved it seemed to cloudnull and I that the work was already in mind - it wasn't clear that there was a desire for input16:12
cloudnull#/kickban Sam-I-Am16:12
cloudnull:)16:12
odyssey4meok, so if I may I can clarify the general direction16:12
Sam-I-Amodyssey4me: i wrote the spec when people were out on the assumption that o-a was keeping a conventional install guide that installs an opinionated-enough system that works16:12
cloudnull^ Sam-I-Am that should continue16:13
KLevenstein(fwiw I believe we should treat the OA installation documentation and the rpc-openstack documentation as completely separate documents.)16:13
odyssey4meeffectively the roles, playbooks and scripts in the repository(ies) are tools in a toolbox for deployers to use as they choose16:13
cloudnullSam-I-Am: the role movement will have no effect on the deploy-ability of the OSA project.16:14
odyssey4meas per the spec in http://specs.openstack.org/openstack/openstack-ansible-specs/specs/mitaka/gate-split.html the repository will still provide meta plays to showcase how to use everything to implement well known use cases16:14
odyssey4methere will need to be pre-role documentation for OSA to describe the options for configuring the roles... I would guess that you would not want to duplicate these docs in rpc-openstack16:15
odyssey4me*per role16:15
KLevensteinodyssey4me: okay, the spec should capture that type of information16:15
Sam-I-Amthe idea was minimizing duplication and places to track changes16:15
Sam-I-Amif its not specific to rpc, it resides in the o-a docs16:16
odyssey4methere will also need to be documentation for how to use the tooling to setup your environment - essentially the basic install guide we now have16:16
Sam-I-Amtherefore if o-a docs change, the rpc docs follow16:16
odyssey4meso I agree with cloudnull here, the existing install guide provides value to OSA and will continue too16:16
*** memogarcia has quit IRC16:16
*** jmckind has quit IRC16:17
Sam-I-Amok. question is... can we expect it to be maintained?16:17
*** jmckind_ has joined #openstack-meeting-416:17
odyssey4meand it would be awesome to have rpc-docs working on OSA docs as upstream and then only looking at specific RPC opinionations in a different docs location16:17
Sam-I-Amthere's still some rax technical debt in it (such as the architecture)16:17
odyssey4meSam-I-Am yes, thus far the maintenance has been done by the community, for the community16:17
odyssey4mewe could do with some help making it pretty, as it's become an organic growth mess16:18
Sam-I-Amtrue. does it work still?16:18
odyssey4meor even not pretty, but to keep it simple and validated on an ongoing basis16:18
Sam-I-Amit sort of has fallen by the wayside16:18
Sam-I-Amhence the spec... effort to figure out how to make it both useful and easier to maintain?16:19
odyssey4mewe've had many patches in the last few months from people working through them and validating them, so I expect that it still works16:19
KLevensteinodyssey4me: I think if we (rpcdocs, and anyone else) have a clearer idea of what needs to be added/maintained in OA, it’ll—yes, what Sam-I-Am said16:19
odyssey4mea large proportion of the specs since the liberty release has been docs16:19
*** egonzalez has quit IRC16:19
KLevensteinso I’d like to see the spec enhanced a bit with things like what you said: add pre-role documentation, etc.16:19
Sam-I-Ambasically i'm looking for more info on recommended structure16:20
odyssey4meok, perhaps we can set aside half of next thu's meeting to work through that in an etherpad, with discussion?16:20
Sam-I-Amright now the docs are more or less a copy of what we had for rpc16:20
odyssey4mebasically if you guys can facilitate a structured discussion then we can focus energy on it with a productive outcome16:20
cloudnullor maybe we carry that convo into the channel ?16:20
Sam-I-Amor that16:21
KLevensteinodyssey4me cloudnull: I approve16:21
cloudnullbut an etherpad to outline all the things would be great .16:21
KLevensteinI can set up an etherpad16:21
*** kbyrne has joined #openstack-meeting-416:21
cloudnullsweet16:21
odyssey4meyeah, we can chat after the meeting a bit - but I think that a structured and prepared for discussion that's facilitated would be most productive - which needs the time to prep16:21
KLevensteinhere you go: https://etherpad.openstack.org/p/oa-install-docs16:22
odyssey4me#link https://etherpad.openstack.org/p/oa-install-docs16:22
*** jckasper has joined #openstack-meeting-416:22
Sam-I-Amyay16:22
odyssey4meok, so we can work up a framework and put Q&A's in during the next week - then can we have a volunteer to actually facilitate the finalisaiton of it in next week's meeting?16:23
*** zeih_ has quit IRC16:23
*** memogarcia has joined #openstack-meeting-416:23
odyssey4meKLevenstein would you be happy to do so?16:23
Sam-I-Ami may not be around for next week's meeting16:23
KLevensteinsure16:23
odyssey4megreat, thanks!16:24
odyssey4me#action KLevenstein to facilitate a discussion for documentation improvements in the next community meeting16:24
odyssey4me#action all to contribute to https://etherpad.openstack.org/p/oa-install-docs with thoughts/ideas/questions ahead of the workshop16:25
*** stanchan_ has joined #openstack-meeting-416:25
*** egonzalez has joined #openstack-meeting-416:25
odyssey4mealright, we have no other specific topic at hand on the agenda but I did want to make sure that we have some open discussion16:26
odyssey4me#topic Open discussion16:26
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:26
*** memogarcia has quit IRC16:26
palendaeI'd appreciate people's thoughts on https://review.openstack.org/#/c/242225/16:26
matttpalendae: no immediate feedback, other than thank you16:27
*** stanchan has quit IRC16:27
palendaeIt's gonna require some work; I'd really like to get to the point where tests can just import the dynamic inventory, but I think that'll have to be done in steps16:27
odyssey4mepalendae I haven't looked in too much detail, but a few thoughts16:27
odyssey4meone is that the general standard for tests in openstack projects appears to be to use the directory 'tests', not 'test' - so that'd be good to change16:28
*** blahRus has joined #openstack-meeting-416:29
odyssey4mealso, I think that we're going to end up with a variety of tests with other files needed, like this - so I'd suggest an extra subfolder with a name that matches the tox env name - does that make sense?16:29
palendaeYeah. We're also going to need different files for inventory tests, because testing with the AIO example files is just 1 case16:30
odyssey4meie put all files into tests/inventory/16:30
cloudnullpalendae:   I think that change is great as a first step to generally improving our inventory bits16:30
odyssey4meah sure, but perhaps that can be an additional case added afterwards16:30
*** memogarcia has joined #openstack-meeting-416:30
cloudnullso thank you ++16:30
palendaeodyssey4me: Right, I'm not adding those right now16:30
palendaeBut they'll be needed16:31
odyssey4meI'm pretty sure that there could be a lot more tests implemented for the dynamic inventory.16:31
palendaeAbsolutely16:31
matttdid we hit any issues in the past w/ the inventory that we haven't accounted for yet?16:32
mattti know the dupe IP thing was the obvious16:32
odyssey4memattt TDD doesn't work like that :p16:32
palendaemattt: One that may be a candidate https://bugs.launchpad.net/openstack-ansible/+bug/151288316:33
openstackLaunchpad bug 1512883 in openstack-ansible "Host name of haproxy in openstack_user_config.yml causes recursion error" [Undecided,Confirmed]16:33
palendaeThough I've not really dug into that16:33
odyssey4meone of the goals for this cycle is to increase test coverage to improve code quality16:35
matttwe should do this for every bit of python that we have in openstack-ansible16:35
matttall the modules that we're carrying etc.16:35
odyssey4meso it'd be great if those interested could spend some cycles considering how best to do some of that16:35
matttso i think this is a great start16:35
cloudnullmattt: ++ i think once we find a place for the libs/plugins to live outside of the main repo we can embark on adding tests and such16:36
odyssey4methis also comes into play for improving infrastructure upgrades - for example, before upgrading - run some tests to confirm that the environment is actually in good working order16:36
cloudnullalso there's a lot of work happening in ansible for v2.0 interms of openstack libs to manage installs16:36
odyssey4methen afterwards, do another test to confirm that stuff's not broken16:36
palendaeI think ideally the inventory will become a lib that could stand alone, too16:36
cloudnullwe might want to see what we can begin using there.16:36
palendaeBut that may be a long way off16:36
*** Konstantinos has joined #openstack-meeting-416:37
odyssey4meso we need to think about tests in layers - unit, functional, etc16:37
*** Konstantinos has quit IRC16:37
*** prashantD has joined #openstack-meeting-416:39
odyssey4mealright, anyone else got something they want to raise?16:39
*** konstantinos has joined #openstack-meeting-416:40
*** sdake has quit IRC16:40
matttthe neutron db migrations change, if someone has time to test16:40
mattt(pulling up the review now)16:40
mattthttps://review.openstack.org/#/c/240560/16:40
*** fawadkhaliq has joined #openstack-meeting-416:40
*** pabelanger has joined #openstack-meeting-416:41
pabelangerohai16:41
cloudnull++ https://review.openstack.org/#/c/241483/ -- when people have time16:41
pabelangersorry I am last16:41
pabelangerlaste*16:41
pabelangergrr16:41
*** Prithiv has joined #openstack-meeting-416:41
cloudnullo/ hi pabelanger16:41
*** memogarcia has quit IRC16:41
odyssey4mepabelanger o/ and welcome16:42
*** sdake has joined #openstack-meeting-416:42
odyssey4mewe're currently in open discussion, so feel free to introduce yourself and present anything for discussion16:42
pabelangerSince it is open discussion, let me do intros.  Name is Paul Belanger, work at Red Hat. Looking to help contribute to ansible more. Been working with openstack-infra for the last 3.5 years, so I want to help improving the testing infra for ansible (roles)16:43
cloudnullwelcome  !16:43
pabelangerSo, over the next few days. I'll likely be asking questions / helping to move all the ansible roles to a common test format.  For example, tox -eansible-lint16:43
odyssey4mepabelanger yeah, I've tried to engage on that topic with infra a few times but the interest is small, so your collaboration is welcome!16:43
pabelangertalking to cloudnull last night, seem we both share a common goal16:43
cloudnull++16:44
pabelangerodyssey4me: Ya, for sure.  Personally, I have an unofficial project at https://github.com/openstack/ansible-role-nodepool and have plans to build out testing for it.  If we can share testing stuff, I think it will be great16:44
oneswigAs a general question of direction, is the long-term aim to have modules that provide mechanism and configuration data to implement policy?  It looks like this is the way the project is driving?16:44
odyssey4mepabelanger agreed, the more we can help each other the better16:45
odyssey4meoneswig if I understand what you mean - that is currently how everything's designed but we're driving to make that clearer16:46
*** bpokorny has joined #openstack-meeting-416:46
pabelangergreat. So, like I said. I'll likely be asking some questions in the coming days and help bridge the effort between openstack-ansible and openstack-infra :)16:46
oneswigodyssey4me thanks I'm interested in using OSA to explore different configs and seeing the effect16:47
odyssey4meoneswig right now it seems like everything's tightly coupled, even though all roles are usable independently - we're splitting the roles out into their own repositories to clarify that they're independently usable, but the playbooks also form two functions16:47
pabelangerBut with that, I have to run.  Need to walk daughter to school.16:47
*** Konstantinos1 has joined #openstack-meeting-416:47
odyssey4meone function is that we have playbooks which do certain functions - like install keystone on multiple hosts, or build containers on multiple hosts16:48
odyssey4meawesome, thanks pabelanger16:48
odyssey4methose playbooks can be seen as kind-of an API within the project... they can get consumed by meta-playbooks16:48
*** memogarcia has joined #openstack-meeting-416:49
odyssey4methe meta-playbooks may be built by deployers to mix and match things as they want, but we also include meta-playbooks which cover the use-cases we test with and support16:49
oneswigodyssey4me this sounds like just what I am looking for, thanks16:49
odyssey4methen we have configuration, which we split entirely out of the code tree - and only provide samples and docs in tree16:49
*** Konstantinos1 has left #openstack-meeting-416:50
*** zeih has joined #openstack-meeting-416:50
odyssey4meoneswig great!16:50
odyssey4meanyone else wish to raise anything?16:51
* Sam-I-Am raises a beer16:51
*** konstantinos has quit IRC16:53
*** memogarcia has quit IRC16:54
odyssey4mealright, thank you all for your time :)16:54
odyssey4me#endmeeting16:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:54
openstackMeeting ended Thu Nov 12 16:54:25 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-11-12-16.00.html16:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-11-12-16.00.txt16:54
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-11-12-16.00.log.html16:54
*** oneswig has left #openstack-meeting-416:54
*** zeih has quit IRC16:55
*** mattt has left #openstack-meeting-416:55
*** cathy_ has joined #openstack-meeting-416:57
*** johnsom has joined #openstack-meeting-416:57
*** armax has joined #openstack-meeting-416:58
*** memogarcia has joined #openstack-meeting-416:58
igordcardcathy_, hi16:59
cathy_#startmeeting service_chaining16:59
openstackMeeting started Thu Nov 12 16:59:44 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.16:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:59
*** openstack changes topic to " (Meeting topic: service_chaining)"16:59
openstackThe meeting name has been set to 'service_chaining'16:59
*** KLevenstein has left #openstack-meeting-416:59
johnsomo/16:59
cathy_hi everyone16:59
pcarverhi16:59
igordcardhi all16:59
*** odyssey4me has left #openstack-meeting-417:00
*** daneyon has joined #openstack-meeting-417:00
*** mohankumar has joined #openstack-meeting-417:00
*** stanchan has joined #openstack-meeting-417:01
*** stanchan_ has quit IRC17:01
cathy_hope everyone  had a good time at the summit. Now let's work on getting the sfc code ready and released.17:01
*** daneyon has quit IRC17:01
*** stanchan has quit IRC17:01
*** bgmccollum has left #openstack-meeting-417:01
cathy_I I have the following topics to discuss today17:01
*** daneyon has joined #openstack-meeting-417:02
*** stanchan has joined #openstack-meeting-417:02
*** Sam-I-Am has left #openstack-meeting-417:03
cathy_1. Flow classifier plugin being separate from port chain plugin, 2.Rebase our code on Neutron Liberty stable branch, 3.Dependency setup  4.Put Code review completion time line.17:03
cathy_any other topic you would like to discuss?17:03
*** daneyon_ has joined #openstack-meeting-417:03
*** BjoernT has left #openstack-meeting-417:04
cathy_#topic Flow classifier plugin being separate from port chain plugin17:04
*** openstack changes topic to "Flow classifier plugin being separate from port chain plugin (Meeting topic: service_chaining)"17:04
*** prometheanfire has left #openstack-meeting-417:04
*** egonzalez has left #openstack-meeting-417:04
pcarverThat looks like a good list, but if there's time I'd like to let people who aren't at OPNFV know about some of the conversations that took place yesterday.17:04
cathy_pcarver: sure17:04
*** mgariepy has left #openstack-meeting-417:04
mohankumarhi17:04
cathy_This separate FC plugin is a leftover topic from our last IRC meeting.17:05
igordcardpcarver, good, thanks17:05
cathy_It seems most of us think we should keep the FC plugin as a separate plugin from the port chain plugin.17:05
cathy_Anyone has different opinion?17:06
*** lakshmiS has joined #openstack-meeting-417:06
*** lakshmiS has left #openstack-meeting-417:06
*** daneyon has quit IRC17:06
pcarverI think we should at least make a good faith effort to define a common classifier and only have a separate one if there are solid technical reasons why it can't be common.17:06
*** sdake_ has joined #openstack-meeting-417:07
pcarverThere are at least three different components of Neutron that need to do flow classification and the user shouldn't be forced to use three different APIs.17:07
*** baoli has joined #openstack-meeting-417:07
pcarverUnless there's some really fundamental technical reason we can't express all the necessary semantics.17:08
igordcardis it going to be extensible/supporting plugging in different classification criteria? say a custom L7 classification engine?17:08
johnsomI agree.  Aligning and working to define a common code base is in our best interest17:08
cathy_pcarver: Agree. I think our current FC can be evolved easily to a common FC.17:08
pcarverSean Collins did some PoC work but I haven't had a chance to take a look at it. Did anybody else see it?17:08
*** sdake has quit IRC17:09
pcarverhttps://github.com/sc68cal/neutron-classifier17:09
cathy_But for now, as we discussed before, let's keep it in networking-sfc but implement it as a separate plugin.17:09
*** baoli_ has joined #openstack-meeting-417:09
*** s3wong has joined #openstack-meeting-417:09
pcarvercathy_: agree on keeping it in until there's something ready to replace it with17:09
cathy_as separate plugin for future migration17:09
s3wongsorry, late17:10
cathy_s3wong: hi17:10
cathy_s3wong: np17:10
mohankumarcathy_ :  Agree17:10
*** memogarcia has quit IRC17:10
*** stanchan_ has joined #openstack-meeting-417:11
*** galstrom_zzz is now known as galstrom17:11
cathy_igordcard: yes it will support L7 param based classification. But we have not implement that part yet, but the API has it17:11
*** stanchan has quit IRC17:12
*** qwebirc51097 has joined #openstack-meeting-417:12
cathy_The API has an extension place for it.17:12
*** baoli has quit IRC17:12
*** memogarcia has joined #openstack-meeting-417:13
igordcardcathy_, thanks, yeah I see the L7 params, have you finished the "design" of this?17:13
cathy_So everyone agrees to keep the flow classifier in networking-sfc but implement it as a separate plugin? Any different opinion?17:13
pcarver+117:13
johnsom+117:13
igordcard+117:14
s3wong+117:14
mohankumar+117:14
cathy_igordcard: no detail design/implementation for this phase, we can do it in next phase17:14
igordcardcathy_, okay, good, thanks17:14
cathy_#agreed keep the flow classifier in networking-sfc but implement it as a separate plugin17:14
cathy_now let's go to next topic17:14
*** mclaren has quit IRC17:15
cathy_#topic Rebase our code on Neutron Liberty stable branch17:15
*** openstack changes topic to "Rebase our code on Neutron Liberty stable branch (Meeting topic: service_chaining)"17:15
*** pabelanger has left #openstack-meeting-417:16
cathy_I have not monitored the Liberty release label. Is there a stable label to rebase our sfc code? Or should we just base our code on master branch?17:16
cathy_armax: are you there? Could you shed some light on this?17:17
johnsom7.0.0 is the stable tag, but there is a stable/liberty branch as well17:18
s3wongcathy_: I do believe it is customary for OpenStack release management to tag integrated release with stable/<release-name>17:18
armaxcathy_: for stable branches you should reach out to mestery17:18
johnsomYou probably want the branch if you want stable as critical fixes will be backported17:18
armaxmestery: he’s our release guru17:18
mesteryarmax cathy_: Even better, file a bug and follow the process :)17:18
armaxcathy_: do you need a stable branch?17:18
*** SimonChung has joined #openstack-meeting-417:18
cathy_armax: yes I would like to rebase SFC code on a stable Neutron branch17:19
johnsomI don't think you want to cut a stable branch yet.17:19
Prithivany particular reason for keeping it as a separate plugin ?17:20
armaxcathy_: ok17:20
pcarvermestery: I think Cathy's question may be a bit different although I'm not sure I grasp the details. She's not asking about releasing networking-sfc, she's asking about pinning networking-sfc to a Neutron release17:20
cathy_mestery: could you point us to a link on the filing bug and process? I know one link but would like to make sure it is the right one17:20
cathy_pcarver: you are right17:20
mesterypcarver: Why would it be pinned to a neutron release?17:20
mesteryThat doesn't make sense17:20
mesteryIt's release independent17:20
mesteryarmax: What am I missing?17:21
cathy_mestery: we have some dependency on neutron code17:21
pcarvermestery: I'm not sure I understand the details, we may need more discussion on what exactly the dependency is17:21
johnsomI'm not sure why you would want it pinned either17:21
*** xingchao has joined #openstack-meeting-417:22
pcarverOne issue we have (that we need to follow up on) is the subclassing of the OvS agent17:22
cathy_pcarver: yes, that is the dependency.17:23
pcarverWe know we need to resolve that, but for the time being we're deriving a customized OvS agent from the Neutron one in order to add the OvS flows needed to direct traffic through chains17:23
cathy_mestery: johnsom that is why I am thinking about rebasing to latest stable Neutron code base17:23
igordcardso isn't it enough to make use of master neutron?17:24
johnsomWouldn't you want to track master changes?17:24
pcarverI presume we're going to need to keep pulling OvS agent updates into networking-sfc until we can get an extensibility mechanism into the Neutron OvS agent that allows us to manipulate flows in the required manner17:25
pcarverigordcard, johnsom: That's the ideal, but we don't think it works yet17:25
cathy_igordcard: johnsom yes we would like to track master changes, but some times new bugs in master impact our testing17:26
pcarverwe need to to add flows into OvS and we don't think the Neutron OvS agent has a mechanism for us to extend it in the required way to add the flows we need17:26
cathy_so I am thinking about doing sync once in a while to stable master branch labels.17:27
igordcardpcarver, but neither does the liberty branch of it, right?17:27
igordcardcathy_, sorry, sync to stable branches or master branch?17:28
pcarverigordcard: correct. Discussion about enhancing the extensibility just came up at the summit and is still in the information gather stage. What we're talking about is the need to update networking-sfc's derived version periodically.17:28
*** sdake_ has quit IRC17:28
cathy_igordcard: sorry I was confusing you folks.17:28
cathy_I am thinking about stable master branch labels.17:29
*** sdake has joined #openstack-meeting-417:29
cathy_Are there such labels?17:29
igordcardpcarver, cathy_ , okay, yeah I see - so update it periodically so you get the best balance between mitaka-progress and not wasting time fixing conflicts due to recent master branch work in neutron17:30
pcarverWe don't want the networking-sfc derived agent to diverge from the upstream Neutron version in the mean time while we're working through what needs to be enhanced in the upstream version to allow us to deprecate the derived version.17:30
johnsomNot that I am aware of.  It's stable/liberty, master, or there will likely be lables for the milestones, M1, M2, etc17:30
*** sdake has quit IRC17:30
cathy_igordcard: yes17:30
*** sdake has joined #openstack-meeting-417:31
cathy_johnsom: Ok, then probably what we can do is to rebase to milestone labels? thought?17:32
cathy_pcarver: yes, sure agree17:33
cathy_johnsom: do you know if there us M1 label available now?17:34
johnsomM1 gets cut the first week in December per the schedule17:35
johnsom#link https://wiki.openstack.org/wiki/Mitaka_Release_Schedule17:35
cathy_johnsom: thanks, then we can do the rebase in early December.17:35
cathy_Ok, let's go to the next topic.17:36
cathy_#topic dependency setup17:37
*** openstack changes topic to "dependency setup (Meeting topic: service_chaining)"17:37
cathy_Here is what is stated on the openstack guideline: The dependency on Neutron must not be present in requirements lists though, and instead belongs to tox.ini depenndency section. Direct library usage requires that this library is mentioned in requirements lists of the subproject To keep your subproject in sync with neutron, it is highly recommended that you register your project in openstack/requirements:projects.txt file t17:38
cathy_Once a subproject opts in global requirements synchronization, it should enable check-requirements jobs in project-config.17:39
*** mohankumar has quit IRC17:40
*** qwebirc51097 has quit IRC17:40
cathy_could anyone take an action item to make sure our networking-sfc is doing what is stated above for subproject?17:40
*** memogarcia has quit IRC17:41
cathy_s3wong: pcarver  could you help with this?17:41
pcarvercathy_: I'll take a look at it17:41
cathy_pcarver: thanks!17:41
igordcardcathy_, the plan in the future is to merge back to neutron correct?17:42
igordcardafter mitaka17:42
pcarverI understand the bit about the check-requirements job. I need to look into the bit about tox.ini part17:42
*** iyamahat has joined #openstack-meeting-417:42
johnsompcarver You can look at neutron-lbaas which uses zuul cloner.  Not sure if it's the right way to get neutron or not, but it works.17:42
cathy_#action Paul will take a look at the dependency setup requirement for subproject and make sure our SFC is compliant with what is required.17:42
*** memogarcia has joined #openstack-meeting-417:43
cathy_igordcard: I don't think subproject needs to merge back to neutron. My understanding is that we can release independently but we need Neutron release team to help tag it for release.17:43
cathy_Ok, let's go to next topic17:44
*** mohankumar has joined #openstack-meeting-417:44
cathy_#topic Put Code review completion time line17:44
*** openstack changes topic to "Put Code review completion time line (Meeting topic: service_chaining)"17:44
cathy_what is a good time line for everyone to finish the detail review for every patch out there and then we can start working on the release of the codes?17:46
*** david-lyle has quit IRC17:46
s3wongcathy_: some reviews have comments... should we wait for them to be addressed?17:47
cathy_I am thinking about just putting one timeline. Each of us can work on the review of each patch based on our own schedule and expertise as long as we finish them by the time line.17:47
cathy_s3wong: sure, we should upload new patches to incorporate those comments.17:48
*** mbuil has joined #openstack-meeting-417:48
*** numans has quit IRC17:48
cathy_I just came back from business trip and then headed to the OPNVF Summit. I will take a look at all patches and make sure people upload new patches.17:48
igordcardI will try to review as much as I can17:49
cathy_I am thinking about having the comments incorporated by next Tuesday.17:49
igordcardme and Prithiv want to further contribute to the design and development of networking-sfc17:49
*** jckasper has quit IRC17:49
cathy_igordcard: thanks for joining the effort !17:49
s3wongcathy_: what kind of timeline are you thinking of?17:50
pcarvercathy_: I'm backlogged with travel too, but am hoping to get some reviews done over the weekend (assuming I recover from being sick, I'm still not feeling great)17:50
mohankumarcathy_:  by this month end we'll  finish review and rework and start rebase by december17:50
*** mbuil has left #openstack-meeting-417:50
s3wongcathy_: I agree the patches had been under review for a while now; our original goal was to get them in before the summit, which didn't work out17:50
*** Prithiv has quit IRC17:50
cathy_mohankumar: I am OK with the time line your suggested17:51
cathy_s3wong: yes, it is always postponed:-) let's be firm this time.17:51
cathy_pcarver: thanks. Hope you will get better soon17:51
mohankumarcathy_:thanks17:51
cathy_anyone disagree with end of Nov as the time line to finish and freeze the review as proposed by mohankumar ?17:52
s3wongcathy_: so we are going with end of November then?17:52
cathy_s3wong: ok with you?17:52
s3wongcathy_: oops, we typed at the same time :-)17:52
s3wongcathy_: +117:52
cathy_pcarver: johnsom igordcard ?17:53
cathy_pcarver: johnsom igordcard OK with you?17:53
*** memogarcia has quit IRC17:53
igordcard+117:53
pcarver+117:53
johnsomSure, that lines up with M1 nicely17:53
*** cindy_ has quit IRC17:53
*** sdake has quit IRC17:54
cathy_#agreed we'll  finish review and rework by end of Nov and start working on release in December17:54
*** iyamahat has quit IRC17:55
cathy_#topic update on OPNFV SFC presentation17:55
*** openstack changes topic to "update on OPNFV SFC presentation (Meeting topic: service_chaining)"17:55
*** iyamahat has joined #openstack-meeting-417:55
cathy_pcarver: your turn:-)17:55
cathy_we have 5 minutes left17:56
cathy_4 min now:-)17:56
pcarverSo we had some interesting discussions at the OPNFV summit and there were quite a few presentations on SFC17:56
pcarverOne in particular involved Tacker invoking Open Daylight to perform the chaining.17:56
cathy_that one bypasses Neutron17:57
s3wongpcarver: yes, the Redhat folks want to put up a demo for the summit17:57
pcarverCathy and I were advocating for the use of networking-sfc as an API mediation layer which allows the implementation intelligence to reside in whatever SDN controller anyone happens to prefer17:57
s3wongpcarver, cathy_: speaking as a Tacker team-member, we are fully onboard to use networking-sfc17:58
cathy_After our presentation, people get to know the SFC work in neutron. The redhat guy is thinking about integrating tacker with networking-sfc17:58
s3wongpcarver, cathy_: it is a work item for Tacker for the M release, around M-2 timeframe17:58
cathy_s3wong: great. That is inline with my thought too17:58
pcarvers3wong: great. I think it makes sense for Tacker to call networking-sfc API and then our driver model delegates out to whichever SDN controller mech driver is appropriate17:59
s3wongcathy_: Dan and Tim are fully aware of networking-sfc, and we have agreed to use it --- however, we also need to have ODL driver for networking-sfc for their use case17:59
*** SumitNaiksatam has joined #openstack-meeting-417:59
pcarverI personally need to get up to speed with Tacker, but I tend to think that Tacker supporting different SFC APIs for all the myriad of SDN controllers is the wrong place17:59
s3wongcathy_, pcarver: as you guys are fully aware, OPNFV seems to favor ODL18:00
*** LouisF has joined #openstack-meeting-418:00
s3wongpcarver: no disagreement from me18:00
LouisFhi18:00
pcarvers3wong: I'm not sure that's 100% true. ODL was the only SDN controller in the first release of OPNFV, but now Contrail and ONOS seem to be showing a strong presence18:00
*** memogarcia has joined #openstack-meeting-418:00
s3wongLouisF: not aware of changes in PDT to PST?  :-)18:01
s3wongpcarver: I see. The OPNFV SFC team seems to be very committed to ODL though18:01
cathy_s3wong: we need to let more people know Neutron's role and the SFC work. Otherwise people will think they can just integrate with ODL directly without using Neutron.18:01
pcarverAnd I don't think that Tacker support for SFC should be dependent on OPNFV inclusion.18:01
*** sdake has joined #openstack-meeting-418:02
cathy_OK time is up. let's continue our discussion next week.18:02
cathy_#endmeeting18:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:02
openstackMeeting ended Thu Nov 12 18:02:55 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-11-12-16.59.html18:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-11-12-16.59.txt18:03
igordcardbye all18:03
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-11-12-16.59.log.html18:03
pcarverIf we have a strong ML-like abstraction of API from mech driver in networking-sfc we should be able to support any SDN-C that wants to write a mech driver18:03
cathy_by all18:03
mohankumarbye18:03
*** dzamboni has quit IRC18:03
*** dshakhray has joined #openstack-meeting-418:03
cathy_pcarver: 100% agree.18:03
s3wongpcarver: we do to a certain extent --- that we have an ordered list of drivers18:03
s3wongpcarver: to emulate the whole ML2 model is a bit of work (precommit/postcommit, multi-threaded support...etc)18:04
*** numans has joined #openstack-meeting-418:04
pcarvers3wong: I just mean in spirit of decoupling API from SDN-C specific driver, not necessarily an exact model of ML218:05
s3wongpcarver: sure, that would be driver interface, which doesn't have exposure of specific SDN-C models18:06
*** cathy_ has quit IRC18:08
*** memogarcia has quit IRC18:11
*** memogarcia has joined #openstack-meeting-418:13
*** memogarcia has quit IRC18:16
*** sdake has quit IRC18:18
*** johnsom has left #openstack-meeting-418:20
*** bnemec has quit IRC18:21
*** xingchao has quit IRC18:23
*** memogarcia has joined #openstack-meeting-418:23
*** LouisF has quit IRC18:26
*** iyamahat has quit IRC18:26
*** memogarcia has quit IRC18:26
*** mohankumar has quit IRC18:27
*** memogarcia has joined #openstack-meeting-418:29
*** jpeeler has quit IRC18:30
*** ivar-lazzaro has joined #openstack-meeting-418:38
*** yamahata has joined #openstack-meeting-418:38
*** fawadkhaliq has quit IRC18:39
*** EmilienM has quit IRC18:42
*** jpeeler has joined #openstack-meeting-418:44
*** jpeeler has quit IRC18:44
*** jpeeler has joined #openstack-meeting-418:44
*** IlyaG has quit IRC18:44
*** EmilienM has joined #openstack-meeting-418:45
*** jpeeler has quit IRC18:47
*** sdake has joined #openstack-meeting-418:49
*** yamahata has quit IRC18:50
*** sdake has quit IRC18:51
*** MarkAtwood has quit IRC18:51
*** Piet has quit IRC18:57
*** angdraug has quit IRC18:58
*** memogarcia has quit IRC18:58
*** jpeeler has joined #openstack-meeting-419:00
*** erikwilson has quit IRC19:00
*** memogarcia has joined #openstack-meeting-419:01
*** Sukhdev has joined #openstack-meeting-419:01
*** Piet has joined #openstack-meeting-419:04
*** mageshgv has quit IRC19:05
*** Piet has quit IRC19:09
*** jckasper has joined #openstack-meeting-419:10
*** fitoduarte has joined #openstack-meeting-419:11
*** IlyaG has joined #openstack-meeting-419:12
*** iyamahat has joined #openstack-meeting-419:13
*** bpokorny_ has joined #openstack-meeting-419:15
*** iyamahat has quit IRC19:17
*** mfedosin has quit IRC19:17
*** iyamahat has joined #openstack-meeting-419:17
*** bpokorny has quit IRC19:19
*** SumitNaiksatam has quit IRC19:20
*** iyamahat has quit IRC19:22
*** sdake has joined #openstack-meeting-419:22
*** xingchao has joined #openstack-meeting-419:23
*** memogarcia has quit IRC19:27
*** bpokorny_ has quit IRC19:29
*** bpokorny has joined #openstack-meeting-419:29
*** xingchao has quit IRC19:29
*** banix has joined #openstack-meeting-419:30
*** bnemec has joined #openstack-meeting-419:33
*** med_ is now known as openstackgerrit_19:39
*** angdraug has joined #openstack-meeting-419:40
*** openstackgerrit_ is now known as med_19:40
*** iyamahat has joined #openstack-meeting-419:41
*** igordcard has quit IRC19:44
*** sdake_ has joined #openstack-meeting-419:46
*** sdake has quit IRC19:49
*** SumitNaiksatam has joined #openstack-meeting-419:51
*** iyamahat has quit IRC19:52
*** iyamahat has joined #openstack-meeting-419:53
*** iurygregory has quit IRC20:04
*** sdake_ has quit IRC20:14
*** sdake has joined #openstack-meeting-420:17
*** mestery has quit IRC20:24
*** MarkAtwood has joined #openstack-meeting-420:32
*** stanchan has joined #openstack-meeting-420:32
*** iyamahat has quit IRC20:32
*** iyamahat has joined #openstack-meeting-420:33
*** stanchan has quit IRC20:33
*** stanchan has joined #openstack-meeting-420:33
*** stanchan_ has quit IRC20:34
*** dshakhray has quit IRC20:36
*** numans has quit IRC20:38
*** memogarcia has joined #openstack-meeting-420:40
*** memogarcia has quit IRC20:46
*** Sukhdev has quit IRC20:46
*** jmckind_ has quit IRC20:48
*** sdake has quit IRC20:54
*** memogarcia has joined #openstack-meeting-420:55
*** cloudtrainme has joined #openstack-meeting-420:55
*** memogarcia has quit IRC20:57
*** iyamahat has quit IRC20:59
*** ivar-laz_ has joined #openstack-meeting-421:00
*** ivar-lazzaro has quit IRC21:03
*** sdake has joined #openstack-meeting-421:11
*** banix has quit IRC21:13
*** sdake_ has joined #openstack-meeting-421:15
*** yamamoto has joined #openstack-meeting-421:16
*** sdake has quit IRC21:17
*** Guest60041 is now known as scotticus21:18
*** rbak has quit IRC21:19
*** Piet has joined #openstack-meeting-421:22
*** yamamoto has quit IRC21:24
*** iyamahat has joined #openstack-meeting-421:25
*** xingchao has joined #openstack-meeting-421:28
*** iyamahat has quit IRC21:30
*** iyamahat_ has joined #openstack-meeting-421:30
*** xingchao has quit IRC21:32
*** memogarcia has joined #openstack-meeting-421:35
*** woodard has quit IRC21:37
*** jmckind has joined #openstack-meeting-421:37
*** jmckind has quit IRC21:38
*** jmckind has joined #openstack-meeting-421:38
*** jmckind has quit IRC21:39
*** jmckind has joined #openstack-meeting-421:40
*** jmckind has quit IRC21:46
*** iyamahat_ has quit IRC21:47
*** iyamahat_ has joined #openstack-meeting-421:48
*** memogarcia has quit IRC21:48
*** memogarcia has joined #openstack-meeting-421:51
*** zeih has joined #openstack-meeting-421:52
*** zeih has quit IRC21:56
*** memogarcia has quit IRC21:58
*** harshs has joined #openstack-meeting-422:05
*** MarkAtwood has quit IRC22:05
*** yamamoto has joined #openstack-meeting-422:05
*** iyamahat_ has quit IRC22:07
*** iyamahat_ has joined #openstack-meeting-422:08
*** Sukhdev has joined #openstack-meeting-422:10
*** stanchan_ has joined #openstack-meeting-422:12
*** mfedosin has joined #openstack-meeting-422:13
*** stanchan has quit IRC22:13
*** IlyaG has quit IRC22:14
*** julim has quit IRC22:14
*** david-lyle has joined #openstack-meeting-422:16
*** zeih has joined #openstack-meeting-422:19
*** memogarcia has joined #openstack-meeting-422:23
*** dims_ has joined #openstack-meeting-422:23
*** dims has quit IRC22:25
*** zeih has quit IRC22:26
*** jckasper has quit IRC22:29
*** prashantD has quit IRC22:29
*** prashantD has joined #openstack-meeting-422:31
*** iyamahat_ has quit IRC22:40
*** memogarcia has quit IRC22:43
*** sdake_ has quit IRC22:44
*** mfedosin has quit IRC22:45
*** zeih has joined #openstack-meeting-422:49
*** ivar-laz_ has quit IRC22:49
*** zeih has quit IRC22:56
*** sigmavirus24 is now known as sigmavirus24_awa22:59
*** ivar-lazzaro has joined #openstack-meeting-423:01
*** memogarcia has joined #openstack-meeting-423:03
*** jckasper has joined #openstack-meeting-423:05
*** galstrom is now known as galstrom_zzz23:08
*** klamath has quit IRC23:08
*** jckasper has quit IRC23:12
*** memogarcia has quit IRC23:16
*** blahRus has quit IRC23:16
*** zeih has joined #openstack-meeting-423:19
*** daddyjoseph971 has joined #openstack-meeting-423:20
*** daddyjoseph97 has quit IRC23:22
*** sdake has joined #openstack-meeting-423:23
*** ivar-lazzaro has quit IRC23:23
*** ivar-lazzaro has joined #openstack-meeting-423:24
*** ivar-lazzaro has quit IRC23:24
*** zeih has quit IRC23:26
*** sdake_ has joined #openstack-meeting-423:26
*** sdake has quit IRC23:28
*** ivar-lazzaro has joined #openstack-meeting-423:29
*** xingchao has joined #openstack-meeting-423:29
*** rbak has joined #openstack-meeting-423:35
*** xingchao has quit IRC23:36
*** nikhil_k_ has joined #openstack-meeting-423:37
*** nikhil_k has quit IRC23:40
*** woodard has joined #openstack-meeting-423:41
*** SimonChung has quit IRC23:42
*** SimonChung1 has joined #openstack-meeting-423:42
*** SimonChung has joined #openstack-meeting-423:43
*** SimonChung has quit IRC23:43
*** SimonChung2 has joined #openstack-meeting-423:43
*** SimonChung1 has quit IRC23:43
*** SimonChung has joined #openstack-meeting-423:44
*** SimonChung2 has quit IRC23:44
*** zeih has joined #openstack-meeting-423:48
*** woodard has quit IRC23:51
*** woodard has joined #openstack-meeting-423:52
*** jgjhgsonchn88523 has quit IRC23:54
*** iyamahat_ has joined #openstack-meeting-423:54
*** zeih has quit IRC23:55
*** harshs has quit IRC23:56

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