Wednesday, 2015-06-10

*** bradjones has joined #openstack-meeting-400:00
*** bradjones has quit IRC00:00
*** bradjones has joined #openstack-meeting-400:00
*** dims has quit IRC00:03
*** dims has joined #openstack-meeting-400:03
*** KunalGandhi has quit IRC00:03
*** KunalGandhi has joined #openstack-meeting-400:04
*** bknudson has joined #openstack-meeting-400:07
*** puranamr has quit IRC00:14
*** markvoelker has joined #openstack-meeting-400:21
*** Rockyg has quit IRC00:22
*** xingchao has quit IRC00:23
*** marcusvrn has quit IRC00:24
*** markvoelker has quit IRC00:26
*** Swami has quit IRC00:28
*** daneyon_ has quit IRC00:30
*** hichtakk has quit IRC00:34
*** hichtakk has joined #openstack-meeting-400:35
*** rfolco has quit IRC00:37
*** Sukhdev has quit IRC01:03
*** tobe has joined #openstack-meeting-401:18
*** xingchao has joined #openstack-meeting-401:19
*** markvoelker has joined #openstack-meeting-401:22
*** vivek-ebay has quit IRC01:23
*** dims has quit IRC01:23
*** galstrom_zzz is now known as galstrom01:24
*** fnaval has quit IRC01:24
*** xingchao has quit IRC01:24
*** TravT has joined #openstack-meeting-401:25
*** markvoelker has quit IRC01:27
*** hichtakk has quit IRC01:37
*** fnaval has joined #openstack-meeting-401:38
*** galstrom is now known as galstrom_zzz01:45
*** bknudson has quit IRC01:46
*** marcusvrn has joined #openstack-meeting-401:48
*** s3wong has quit IRC01:48
*** sarob has quit IRC01:50
*** bharath has quit IRC01:52
*** marcusvrn has quit IRC01:56
*** CheKoLyN has joined #openstack-meeting-401:56
*** kenhui has quit IRC01:57
*** KunalGandhi has quit IRC01:58
*** KunalGandhi has joined #openstack-meeting-401:59
*** asselin_ has joined #openstack-meeting-402:00
*** yamahata has quit IRC02:09
*** VW has joined #openstack-meeting-402:10
*** ajayaa has joined #openstack-meeting-402:10
*** dims has joined #openstack-meeting-402:12
*** KunalGandhi has quit IRC02:14
*** KunalGandhi has joined #openstack-meeting-402:14
*** fitoduarte has joined #openstack-meeting-402:16
*** KunalGan_ has joined #openstack-meeting-402:18
*** KunalGandhi has quit IRC02:19
*** dims has quit IRC02:23
*** fallenpegasus has quit IRC02:26
*** KunalGan_ has quit IRC02:26
*** fallenpegasus has joined #openstack-meeting-402:30
*** banix has quit IRC02:31
*** fallenpegasus has quit IRC02:32
*** fallenpegasus has joined #openstack-meeting-402:32
*** hichtakk has joined #openstack-meeting-402:36
*** VW has quit IRC02:39
*** bradjones has quit IRC02:52
*** bradjones has joined #openstack-meeting-402:53
*** bradjones has quit IRC02:53
*** bradjones has joined #openstack-meeting-402:53
*** galstrom_zzz is now known as galstrom03:03
*** ajayaa has quit IRC03:07
*** hichtakk has quit IRC03:10
*** markvoelker has joined #openstack-meeting-403:11
*** markvoelker has quit IRC03:16
*** mmedvede has quit IRC03:28
*** sigmavirus24 is now known as sigmavirus24_awa03:32
*** mmedvede has joined #openstack-meeting-403:35
*** puranamr has joined #openstack-meeting-403:37
*** ivar-laz_ has quit IRC03:51
*** Sukhdev has joined #openstack-meeting-403:51
*** galstrom is now known as galstrom_zzz04:16
*** amotoki_ has joined #openstack-meeting-404:40
*** amotoki_ has quit IRC04:46
*** amotoki is now known as amotoki_04:46
*** amotoki_ has quit IRC04:49
*** amotoki has joined #openstack-meeting-404:49
*** kenhui has joined #openstack-meeting-404:50
*** CheKoLyN has quit IRC04:55
*** puranamr has quit IRC04:57
*** puranamr has joined #openstack-meeting-404:58
*** puranamr has quit IRC04:59
*** markvoelker has joined #openstack-meeting-405:00
*** puranamr has joined #openstack-meeting-405:03
*** markvoelker has quit IRC05:04
*** lazy_prince has joined #openstack-meeting-405:04
*** fallenpegasus has quit IRC05:08
*** wojdev has joined #openstack-meeting-405:09
*** ajayaa has joined #openstack-meeting-405:10
*** kenhui has quit IRC05:12
*** KunalGandhi has joined #openstack-meeting-405:18
*** nkrinner has joined #openstack-meeting-405:32
*** amotoki_ has joined #openstack-meeting-405:41
*** puranamr has quit IRC05:44
*** fitoduarte has quit IRC05:45
*** amotoki_ has quit IRC05:46
*** wojdev has quit IRC05:50
*** Sukhdev has quit IRC05:51
*** KunalGandhi has quit IRC05:52
*** wojdev has joined #openstack-meeting-405:55
*** wojdev has quit IRC05:59
*** belmoreira has joined #openstack-meeting-406:01
*** puranamr has joined #openstack-meeting-406:05
*** puranamr has quit IRC06:10
*** numan has joined #openstack-meeting-406:16
*** Sukhdev has joined #openstack-meeting-406:19
*** Sukhdev has quit IRC06:33
*** amotoki_ has joined #openstack-meeting-406:41
*** amotoki_ has quit IRC06:47
*** markvoelker has joined #openstack-meeting-406:49
*** markvoelker has quit IRC06:53
*** nihilifer_ has joined #openstack-meeting-407:11
*** nihilifer_ has left #openstack-meeting-407:12
*** paramite has joined #openstack-meeting-407:20
*** armax has quit IRC07:26
*** mmedvede has quit IRC07:37
*** amotoki_ has joined #openstack-meeting-407:43
*** amotoki_ has quit IRC07:48
*** watanabe_isao has joined #openstack-meeting-407:50
*** GB21 has joined #openstack-meeting-407:59
*** paramite has quit IRC08:31
*** watanabe_isao has quit IRC08:33
*** markvoelker has joined #openstack-meeting-408:37
*** bradjones has quit IRC08:40
*** markvoelker has quit IRC08:42
*** bradjones has joined #openstack-meeting-408:42
*** bradjones has quit IRC08:42
*** bradjones has joined #openstack-meeting-408:42
*** amotoki_ has joined #openstack-meeting-408:44
*** amotoki_ has quit IRC08:48
*** vishwanathj has quit IRC08:51
*** yamahata has joined #openstack-meeting-409:07
*** GeetikaBatra__ has joined #openstack-meeting-409:18
*** GB21 has quit IRC09:19
*** dims has joined #openstack-meeting-409:27
*** dims has quit IRC09:31
*** GeetikaBatra__ has quit IRC09:32
*** GB21 has joined #openstack-meeting-409:46
*** fesp has joined #openstack-meeting-409:48
*** dims has joined #openstack-meeting-409:51
*** dims_ has joined #openstack-meeting-409:52
*** fesp has quit IRC09:55
*** GB21 has quit IRC09:56
*** dims has quit IRC09:56
*** matrohon has joined #openstack-meeting-410:16
*** markvoelker has joined #openstack-meeting-410:23
*** markvoelker has quit IRC10:27
*** GB21 has joined #openstack-meeting-410:40
*** amotoki_ has joined #openstack-meeting-410:45
*** amotoki_ has quit IRC10:50
*** asselin has quit IRC10:50
*** xingchao has joined #openstack-meeting-410:52
*** amotoki has quit IRC10:54
*** xingchao has quit IRC10:56
*** amotoki has joined #openstack-meeting-411:12
*** numan has quit IRC11:12
*** kei has joined #openstack-meeting-411:13
*** numan has joined #openstack-meeting-411:22
*** markvoelker has joined #openstack-meeting-411:24
*** amotoki has quit IRC11:25
*** markvoelker has quit IRC11:28
*** jdziukx has joined #openstack-meeting-411:43
*** marcusvrn has joined #openstack-meeting-411:43
*** marcusvrn1 has joined #openstack-meeting-411:46
*** marcusvrn has quit IRC11:46
*** tobe has quit IRC11:47
*** marcusvrn1 has quit IRC11:51
*** marcusvrn has joined #openstack-meeting-411:51
*** Kiall has quit IRC11:53
*** Kiall has joined #openstack-meeting-411:53
*** markvoelker has joined #openstack-meeting-411:54
*** Kiall has quit IRC11:56
*** Kiall has joined #openstack-meeting-411:57
*** janonymous_ has joined #openstack-meeting-412:24
*** bradjones has quit IRC12:26
*** bradjones has joined #openstack-meeting-412:27
*** bradjones has quit IRC12:27
*** bradjones has joined #openstack-meeting-412:27
*** GeetikaBatra__ has joined #openstack-meeting-412:28
*** GB21 has quit IRC12:30
*** amotoki has joined #openstack-meeting-412:30
*** VW has joined #openstack-meeting-412:37
*** VW has quit IRC12:39
*** rfolco has joined #openstack-meeting-412:40
*** VW has joined #openstack-meeting-412:40
*** qwebirc99779 has joined #openstack-meeting-412:40
*** salv-orlando has quit IRC12:45
*** bknudson has joined #openstack-meeting-412:53
*** klamath has joined #openstack-meeting-412:57
*** klamath has quit IRC12:57
*** sigmavirus24_awa is now known as sigmavirus2412:58
*** klamath has joined #openstack-meeting-412:58
*** nfedotov has joined #openstack-meeting-413:01
*** tariqkhp has joined #openstack-meeting-413:03
*** janonymous_ is now known as janonymous__13:07
*** janonymous__ is now known as janonymous_13:08
*** ajayaa has quit IRC13:15
*** singlethink has joined #openstack-meeting-413:23
*** qwebirc99779 has quit IRC13:24
*** VW_ has joined #openstack-meeting-413:30
*** VW has quit IRC13:31
*** puranamr has joined #openstack-meeting-413:32
*** rods1 has joined #openstack-meeting-413:34
*** tariqkhp has quit IRC13:35
*** vishwanathj has joined #openstack-meeting-413:37
*** janonymous_ has quit IRC13:37
*** vishwana_ has joined #openstack-meeting-413:39
*** xingchao has joined #openstack-meeting-413:41
*** vishwanathj has quit IRC13:42
*** puranamr has quit IRC13:43
*** puranamr has joined #openstack-meeting-413:44
*** xingchao has quit IRC13:45
*** GeetikaBatra__ has quit IRC13:49
*** matrohon has quit IRC13:53
*** igordcard_ has quit IRC13:56
*** igordcard_ has joined #openstack-meeting-413:57
*** puranamr has quit IRC13:57
*** VW_ has quit IRC13:58
*** kevsi_ has joined #openstack-meeting-414:00
*** kevsi_ has quit IRC14:01
*** kevsi_ has joined #openstack-meeting-414:02
*** fnaval has quit IRC14:04
*** VW has joined #openstack-meeting-414:05
*** xingchao has joined #openstack-meeting-414:09
*** aventerav has joined #openstack-meeting-414:09
*** britthouser has joined #openstack-meeting-414:10
*** britthou_ has quit IRC14:12
*** jckasper has quit IRC14:13
*** VW has quit IRC14:16
*** amotoki has quit IRC14:17
*** amotoki has joined #openstack-meeting-414:17
*** amotoki has quit IRC14:18
*** puranamr has joined #openstack-meeting-414:18
*** amotoki has joined #openstack-meeting-414:19
*** amotoki has quit IRC14:20
*** amotoki has joined #openstack-meeting-414:20
*** puranamr has quit IRC14:23
*** fnaval has joined #openstack-meeting-414:23
*** nkrinner has quit IRC14:29
*** fnaval has quit IRC14:37
*** sbalukoff has quit IRC14:39
*** ajmiller has joined #openstack-meeting-414:47
*** fallenpegasus has joined #openstack-meeting-414:49
*** VW has joined #openstack-meeting-414:50
*** BobBall has joined #openstack-meeting-414:55
*** belmoreira has quit IRC14:57
*** mmedvede has joined #openstack-meeting-414:57
*** patrickeast has joined #openstack-meeting-414:58
krtaylor#startmeeting third-party15:00
openstackMeeting started Wed Jun 10 15:00:49 2015 UTC and is due to finish in 60 minutes.  The chair is krtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: third-party)"15:00
openstackThe meeting name has been set to 'third_party'15:00
swestono/15:01
krtaylorwho's here for third party ci working group?15:01
patrickeasthi15:01
mmedvedeo/15:01
asselin_hi15:01
marcusvrnHi15:01
BobBallo_15:01
BobBallThat's a mostly.15:01
*** zz_ja is now known as ja15:01
ja3pci15:02
krtaylorhi everyone! looks like we have a good group today15:02
krtaylorhere's the agenda15:02
krtaylor#link https://wiki.openstack.org/wiki/Meetings/ThirdParty#6.2F10.2F15_1500_UTC15:02
*** jckasper has joined #openstack-meeting-415:03
*** wznoinsk has joined #openstack-meeting-415:03
*** fnaval has joined #openstack-meeting-415:03
*** dims_ has quit IRC15:03
krtaylor#topic Announcements15:03
*** openstack changes topic to "Announcements (Meeting topic: third-party)"15:03
asselin_BobBall, are you double-booked?15:03
BobBallYup!15:03
BobBallAlways am... But moving the other meeting (as it happens :) )15:04
* BobBall is also in #openstack-meeting :)15:04
krtaylorThe cinder volume driver deadline is June 19th, coming up15:04
*** galstrom_zzz is now known as galstrom15:04
krtaylorre: double booking, I am hoping to fix that, we'll discuss in a bit15:04
krtaylorany other quick announcements or reminders?15:05
asselin_cinder deadling is actually June 12th for CI to start posting 1 week before June 19th to be merged15:05
krtaylorah, thanks for that clarification asselin_15:05
krtaylorif nothing else, on to active work items then15:06
krtaylor#topic Monitoring dashboard status15:07
*** openstack changes topic to "Monitoring dashboard status (Meeting topic: third-party)"15:07
krtaylorjust to level set, we had a good initial discussion in the Monday office hours meeting15:07
krtaylorthe spec for the dashboard has stalled15:07
*** dims has joined #openstack-meeting-415:08
*** dims has quit IRC15:08
krtaylorthere are several instances of the scoreboard being seen around15:08
*** patrickeast has quit IRC15:08
BobBallAny examples worth sharing?15:08
*** dims has joined #openstack-meeting-415:08
*** jwagner is now known as jwagner_away15:08
krtaylorso the question is, either we need to get support behind the existing spec15:08
BobBallDo these scoreboards look at all CIs or just their own?15:09
krtayloryes, links coming15:09
*** patrickeast has joined #openstack-meeting-415:09
BobBallAlso spec link would be good :)15:09
krtaylorspec:15:09
krtaylor#link  https://review.openstack.org/#/c/135170/15:09
*** kenhui has joined #openstack-meeting-415:09
krtaylorI just had the scoreboard link, one sec15:10
*** patrickeast has quit IRC15:10
*** patrickeast has joined #openstack-meeting-415:10
asselin_patrickeast commented to use the scoreboard he setup15:10
swestonthis spec has been difficult to move forward ... every time I think we are about to get a +2, somebody posts another review that stalls it.  Reminds me of the charlie brown football.15:11
swestonhttp://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack%2Fcinder&user=&timeframe=2415:11
krtaylorasselin_, do you have that link handy?15:11
sweston^ link for scoreboard15:11
krtaylorthats it, thanks sweston15:11
swestonkrtaylor: yup15:11
BobBall"This web page is not available"15:11
BobBalldoes it work for others?15:11
*** jwagner_away is now known as jwagner15:12
asselin_works for me15:12
mmedvedewfm as well15:12
BobBallStupid corporate firewall!15:12
asselin_do we need a spec to do the scoreboard?15:12
asselin_patrickeast made one w/o a spec15:12
asselin_so I'm questioning the purpose of the spec really....15:12
patrickeastsry, i keep dropping off the meeting (on my phone)15:13
krtaylorasselin_, good question, but the initial radar was also made w/o spec15:13
patrickeastasselin_: i was wondering about that too15:13
asselin_I was looking at this unrelated spec: https://review.openstack.org/#/c/188574/15:13
krtaylorI can see where sweston would think that was somewhat unfair15:13
asselin_and basically, someone set something up, and wrote a spec afterwards to host it by openstack15:13
krtaylorsince sweston had to go through the painful spec process15:13
patrickeasti agree 100%, its kind of backwards15:14
asselin_I think we should do something similar for the dashboard15:14
patrickeastbut on the other hand… we need something15:14
patrickeastwhether its my scoreboard, or sweston’s dashboard, or radar or whatever15:14
swestonyup, this is the circle we've been in for months15:15
asselin_get something working, iterate, and once we're happy, copy that spec outline to have it hosted by infra15:15
patrickeastand i think i’m not alone in saying that waitin for another round of spec hmm-hawing isn’t going to get us anywhere15:15
asselin_patrickeast, +115:15
krtayloragreed, so the question is, do we stay with the new radar?15:15
patrickeastunless our goal is to revisit it again in M15:15
swestonradar should be the permanent solution ... the scoreboard is good for adhoc reporting, but does not help the understanding of history and trends15:16
asselin_M is for Maybe15:16
patrickeastsweston: +115:16
patrickeastone thing im wondering is if maybe we are having this conversation in the wrong venue15:17
patrickeastsince clearly even if we all agree on something it wont make it happen15:17
patrickeastwe kind of need the infra cores to back it15:17
asselin_patrickeast, no we don't15:17
patrickeastaren’t they the +2’s we need on that spec?15:17
asselin_patrickeast, you didn't to create the scorecard15:17
patrickeasttrue15:18
krtaylorso, I'd propose, abandoning the spec, having infra host scoreboard for a tactical solution, then radar for the strategic way forward15:18
asselin_patrickeast, goes back to what I was saying...why do we need the spec at all?15:18
patrickeastasselin_: haha yea, fair point15:18
*** britthouser has quit IRC15:18
krtaylorexactly, stand up one, patch to have it hosted, that would be the spec15:18
asselin_so, we do need a spec to have infra host scoreoard15:18
asselin_or host radar15:19
krtaylorI'd say no, else we would have had an approved spec long ago15:19
*** britthouser has joined #openstack-meeting-415:19
asselin_and if we want a spec, it should be in third-party-specs where we can +2 it ourselves15:19
krtaylorhm, good point15:20
swestonkrtaylor: I like your plan.  I am reluctant to abandon the spec, as in my opinion I don't think the spec should be related to infra hosting the solution15:20
swestonasselin_: yes, that would be a good solution, +115:20
krtaylorsweston, it can remain actually, or we can have a third-party-specs copy15:21
wznoinsksweston: sorry to inject out of nowhere here, would nagios check and bothering alert email be just enough? you can pull report from nagios on how many times the check failed/what status of the check was (like CI name that was suspected) ?15:21
krtaylorwznoinsk, lets have that discussion in the open discussion at the end of the meeting15:21
asselin_wznoinsk, I think we need something more visual to compare all 3rd party cis15:22
*** carl_baldwin has joined #openstack-meeting-415:22
krtayloroh, as an alternative, understand now15:22
swestonwznoinsk: no problem ... nagios needs data to run against, the dashboard is for the collection of the data15:22
krtayloryes, we know email will be ignored15:22
swestonkrtaylor: hehe15:22
*** ajayaa has joined #openstack-meeting-415:23
krtaylorso, do we have an agreement?15:23
*** MarkAtwood has joined #openstack-meeting-415:23
asselin_krtaylor, can you summarize just to be clear?15:23
swestonkrtaylor: can you clarify what is on the table now15:24
krtaylorI think we all agree on scoreboard immediately, radar long term15:24
asselin_+115:24
swestoncan we vote? makes me feel important ...15:24
sweston;-)15:24
krtaylorhehheh sure15:24
asselin_let's see if it works this time15:24
krtaylor#startvote15:25
openstackUnable to parse vote topic and options.15:25
krtaylorlol15:25
krtaylornope15:25
asselin_#help15:25
swestonah, well, most fun I've had all week.15:25
sweston+1 for scoreboard short term, dashboard long term15:25
patrickeast+115:25
krtaylor#startvote scoreboard immediately, radar long term15:25
openstackUnable to parse vote topic and options.15:25
ja+115:25
marcusvrn+115:26
mmedvede+115:26
asselin_krtaylor, use #help15:26
asselin_+115:26
krtaylor#help startvote15:26
krtaylor#help15:26
BobBall+115:26
krtaylorlol15:26
asselin_or not :)15:26
krtaylor+115:26
BobBallI don't see any -1s though!15:26
krtaylorI can show it this way15:26
krtaylor#topic Vote on  scoreboard immediately, radar long term15:27
*** openstack changes topic to "Vote on scoreboard immediately, radar long term (Meeting topic: third-party)"15:27
*** yamahata has quit IRC15:27
krtaylor#topic Vote results: 7 voting +1, 0 voting -115:27
*** openstack changes topic to "Vote results: 7 voting +1, 0 voting -1 (Meeting topic: third-party)"15:27
asselin_Example: #startvote Should bshum be the release manager from now on? Yes, No15:28
*** yamahata has joined #openstack-meeting-415:28
krtaylor#startvote  scoreboard immediately, radar long term? yes,  no15:28
openstackBegin voting on: scoreboard immediately, radar long term? Valid vote options are yes, no.15:28
openstackVote using '#vote OPTION'. Only your last vote counts.15:28
BobBall#vote yes15:28
krtaylor#vote yes15:29
asselin_#vote yes15:29
mmedvede#vote yes15:29
sweston#vote yes15:29
marcusvrn#vote yes15:29
BobBallYou're right sweston - it does make me feel important.15:29
krtayloryea, we figured out the vote15:29
swestonBobBall: right? ;-)15:29
patrickeast#vote yest15:29
openstackpatrickeast: yest is not a valid option. Valid options are yes, no.15:29
patrickeast#vote yes15:29
patrickeastwhew15:29
krtaylorhahhahaaaa15:29
patrickeastalmost missed it and paniced15:29
krtayloranyone else?15:30
patrickeastpanicked even15:30
krtaylor#topic Monitoring dashboard15:31
*** openstack changes topic to "Monitoring dashboard (Meeting topic: third-party)"15:31
swestonI hate to get stuck on this, but I do not feel that we've solved the second issue of what to do about the current spec15:31
asselin_krtaylor, need to #endvote15:31
krtaylorlast call15:31
BobBallWas going to say, shouldn't it be finished ;)15:31
krtaylor#endvote15:31
openstackVoted on "scoreboard immediately, radar long term?" Results are15:31
openstackyes (7): asselin_, krtaylor, sweston, BobBall, marcusvrn, mmedvede, patrickeast15:31
krtaylorcool, so the question is: what to do with the spec?15:32
*** lazy_prince has quit IRC15:33
asselin_I think we need a new spec to get scoreboard hosted by infra15:33
krtaylordo we want a third-party-specs15:33
krtaylordo we need a spec for that? I guess infra should answer that15:33
*** sdake has joined #openstack-meeting-415:33
asselin_do we need  a new repo? or just add a folder to out exiting?15:34
asselin_krtaylor, yes we do15:34
*** kenhui has quit IRC15:34
* krtaylor is having trouble parsing this15:34
krtaylorfolder in thrid-party-ci-tools?15:35
krtaylorthird15:35
asselin_krtaylor, yes15:35
asselin_krtaylor, or a new third-party-ci-tools-spec repo?15:35
krtaylorthat would give us a place for the existing spec, sweston 's15:36
swestonI think the other factor is, that this spec should have been closed a long time ago, but there has not been a +2 quick enough from a core, and then additional questions get posted to it.  We had agreement on this spec a month ago15:36
swestonso I am inclined to move it to a place where we can approve it15:37
krtayloryes, and we have 2 topics here15:37
krtaylor1) spec 2) hosting15:37
swestonyes, may we vote, again on 1, and then we can vote on 215:37
krtaylorhow about we just make a dir under the tools repo for now, we can always pull it out into a new repo15:38
asselin_krtaylor, +115:38
swestonkrtaylor: +115:38
krtaylorso the proposal is: move the existing radar spec to a /spec dir under the third-party-ci-tools repo15:38
*** singlethink has quit IRC15:39
asselin_#agree  move the existing radar spec to a /spec dir under the third-party-ci-tools repo15:39
krtaylor#startvote move the existing radar spec to a /spec dir under the third-party-ci-tools repo? yes, no15:39
openstackBegin voting on: move the existing radar spec to a /spec dir under the third-party-ci-tools repo? Valid vote options are yes, no.15:39
openstackVote using '#vote OPTION'. Only your last vote counts.15:39
asselin_#vote yes15:39
sweston#yes15:39
krtaylornow I am abusing the start vote tool  :)15:39
mmedvede#vode yes15:39
swestonah ..15:39
sweston#vote yes15:39
mmedvede#vote yes15:39
krtaylor#vote yes15:39
marcusvrn#vote yes15:39
ja#vote yes15:40
*** praveens has joined #openstack-meeting-415:40
swestonkrtaylor: feels good, though ... right?15:40
krtaylorlol15:40
*** blahRus has joined #openstack-meeting-415:40
krtaylorlast call15:40
krtaylor#endvote15:41
openstackVoted on "move the existing radar spec to a /spec dir under the third-party-ci-tools repo?" Results are15:41
openstackyes (6): asselin_, krtaylor, sweston, marcusvrn, mmedvede, ja15:41
*** rhallisey has joined #openstack-meeting-415:41
krtaylorcool, so, last is, spec for hosting or just patchset15:41
*** inc0 has joined #openstack-meeting-415:41
*** rhallisey has left #openstack-meeting-415:41
*** numan has quit IRC15:42
krtaylorlet's see if a patch will do it, pointing to a running copy of scoreboard, that might be spec enough15:42
krtaylorcomments?15:42
asselin_krtaylor, not sure we have an option....or I'm misunderstanding15:42
swestonI am not following either, a patch to what, exactly15:43
krtaylornot sure either, the process of hosting vs spec15:44
krtaylordo vs. talk about it15:45
mmedvedegetting it hosted by infra vs hosting ourselves?15:45
asselin_krtaylor, we can't just 'do' if we want infra to host it15:46
*** Sukhdev has joined #openstack-meeting-415:46
krtayloryes, thats the question15:46
asselin_krtaylor, but if we host it ourselves, no spec needed15:46
mmedvedeI think it is better for infra to host it15:46
krtaylorok, now I understand your comment15:46
krtayloryes, we want infra to host15:46
asselin_if scoreboard is shorterm, we can consider hosting ourselves15:46
asselin_patrickeast already has one hosted15:47
krtaylorbut where is that hosted?15:47
krtaylorourselves is infra :)15:47
asselin_amazon lol :)15:47
krtaylorhehheh15:47
swestonyeah, but infra hosting it has the benefit of standardizing on the url, one supported place for everyone to go15:47
*** jwagner is now known as jwagner_away15:47
marcusvrnand how can we contribute to the patrickeas's scoreboard?15:48
mmedvedeBut patrickeast is paying for it, and it would not be enough once it would get a lot of hits15:48
patrickeasthaha yea its a very small vm on ec215:48
patrickeastit couldn’t handle much more load than it gets now15:48
krtayloragreed, infra needs to host so that all projects can use it as a reference for CI system reliability15:48
marcusvrnI cloned the scoreboard and added more CIs, for example15:48
swestonpatrickeast should have some ads at the top for revenue generation15:48
patrickeastit is technically sponsored by Pure Storage15:48
swestonhehe15:48
patrickeasti’m using my work account15:48
asselin_+1 for ad support :)15:49
*** armax has joined #openstack-meeting-415:49
patrickeastlol15:49
mmedvedehaha15:49
marcusvrnlol15:49
asselin_we'd get a lot of hits for sure15:49
krtaylormarcusvrn, you can patch the third-party-ci-tools/scoreboard for improvements15:49
*** jwagner_away is now known as jwagner15:49
krtaylor#link https://github.com/stackforge/third-party-ci-tools/tree/master/monitoring/scoreboard15:50
asselin_I can help write a spec to get it hosted by infra15:50
krtaylorok, so the proposal is to have infra host the scoreboard for an immediate solution15:51
krtayloranother vote  ?  :)15:51
swestonwhohoo, one more abuse of the voting?15:51
asselin_let's vote to vote15:51
swestonI say go15:51
marcusvrnkrtaylor: ok15:51
krtaylorany no's?15:51
krtaylor(running out of time)15:52
krtaylorlast call15:52
krtaylorok, asselin_, you have the pen on that spec?15:52
asselin_sure15:52
krtaylorasselin_, I'll be happy to help, I'm sure others will review as well15:53
krtaylorsweston, any other thoughts?15:54
*** GeetikaBatra__ has joined #openstack-meeting-415:54
swestonkrtaylor: nope, you've got them all for the moment15:54
krtaylorsweston, again, I want to thank you for all the hard work on the spec and radar code, it was a great effort15:54
*** GeetikaBatra__ is now known as GB2115:54
krtaylorwe'll keep this moving15:54
*** rhallisey has joined #openstack-meeting-415:54
krtaylor#topic Meeting frequency and time15:55
*** openstack changes topic to "Meeting frequency and time (Meeting topic: third-party)"15:55
swestonkrtaylor: you're welcome! and thanks for the appreciation, feels good15:55
marcusvrnkrtaylor: short term means how much time for scoreboard?15:55
krtaylorquickly, I want to mention that I have proposed moving this meeting time and day15:55
asselin_marcusvrn, until radar is ready15:55
*** rhallisey has left #openstack-meeting-415:55
krtaylorhere is the proposal:15:55
krtaylor#link https://review.openstack.org/#/c/190221/15:56
*** mstachow has joined #openstack-meeting-415:56
krtaylorplease review15:56
*** dannywilson has joined #openstack-meeting-415:56
krtayloroops it failed, gotta fix that15:56
krtayloranyway, I'll also follow up with email15:56
marcusvrnkrtaylor: agreed! This meeting is at my lunch time :P15:57
krtaylorthe proposal is to move for less neutron  and cinder conflicts, eliminate poorly attended 0400UTC time15:57
swestonjenkins checks ical files now? but my coffee maker is still broken ...15:57
krtaylorwe are also discussing TPCIWG items in the Monday meetings now, so I see less need for this time every week, move to every other15:58
*** pdb has joined #openstack-meeting-415:58
* patrickeast should start going to monday meetings again15:58
*** juggler has joined #openstack-meeting-415:58
mmedvedeme too15:58
*** ivar-lazzaro has joined #openstack-meeting-415:59
krtaylorwe can continue to have deeper dives on topics here15:59
krtayloralmost out of time15:59
*** rhallisey has joined #openstack-meeting-415:59
krtaylorthanks everyone, really good meeting today15:59
swestonyes, thanks all15:59
*** Kupo24z has joined #openstack-meeting-415:59
krtaylor#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Jun 10 16:00:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-06-10-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-06-10-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-06-10-15.00.log.html16:00
rhallisey#startmeeting kolla16:01
openstackMeeting started Wed Jun 10 16:01:08 2015 UTC and is due to finish in 60 minutes.  The chair is rhallisey. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: kolla)"16:01
openstackThe meeting name has been set to 'kolla'16:01
*** singlethink has joined #openstack-meeting-416:01
rhallisey#topic rollcall16:01
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:01
rhalliseyhello16:01
pdbhi16:01
Kupo24zhi16:01
jpeelerhi!16:01
mstachowhi :) !16:01
SamYaplehere i am16:01
*** ja is now known as zz_ja16:01
jugglero/ [visiting..]16:01
Slowero/16:01
sdakeyar folks o/16:01
sdakehey juggler visiting :)16:02
juggleryello sdake!16:02
rhalliseyhey hall16:02
rhalliseyhey all16:02
kevsi_hi16:02
*** Kupo24z is now known as loth16:02
lothhey16:02
*** bmace has joined #openstack-meeting-416:03
*** patrickeast has left #openstack-meeting-416:03
*** jasonsb has joined #openstack-meeting-416:03
rhallisey#topic Announcements16:03
*** openstack changes topic to "Announcements (Meeting topic: kolla)"16:03
rhalliseyOk so we are looking to do a mid cycle meetup16:03
rhallisey#link http://doodle.com/su62amktdrp5mrez16:03
rhalliseylets take ~2min to check that out16:04
*** vinkman has joined #openstack-meeting-416:04
rhalliseyit will be help in San Jose16:04
sdakehelp is the right word :)16:04
rhalliseyheld*16:04
rhalliseyha16:04
jasonsbare you interested in having new people attend or is it more of a working session?16:05
rhalliseyany Kolla dev is welcome, it looks like we will have good participation16:05
sdakejpeeler around?16:05
sdakei also invited the operators16:05
sdakei get mandre can't make it from europe16:05
jpeeleri'm here16:05
sdakecurious what your conflicts are for the second two weeks16:06
sdakeis it like a pto thing?16:06
pdbit would be cool if you could do some hangouts as part of it16:06
rhalliseyjasonsb, I would say it's a working session, but there are lots of new people so I would say anyone is welcome16:06
pdbfor us who can't make it across the water16:06
jasonsbrhallisey: awesome16:06
jpeelersdake: i'm going to be on my honeymoon!16:06
jpeelerbut i doubt there's travel funds for me anyway16:06
sdakejasonb absolutely midcycles are open to the public16:06
*** daneyon has joined #openstack-meeting-416:06
sdakeoh no shit16:06
sdakewell grats to ya !16:07
rhalliseydaneyon, hey16:07
daneyonhey16:07
sdakejpeeler I may have to schedule you out of the meeting looking at the current poll stats unfortunately16:07
bmace+1 pdb.  not sure if you are having this stuff in a room that has video-conf tech for remote folks.16:07
sdakehey dnayeon16:07
*** jmccarthy has joined #openstack-meeting-416:07
sdakewe will likely have full telepresence via webex16:07
sdakebut I can't confirm until I have dates16:08
sdakethat is why it wasn't in the announcement post16:08
rhalliseyI'm sure we can accommodate16:08
jmccarthyDid I miss rollcall ?16:08
jpeelersdake: thanks! it's ok - not sure about funding like i said16:08
rhalliseyjmccarthy, yes, that's ok :)16:08
jmccarthyI'm here =)16:08
jugglerI think the bot recorded you jmcc :)16:08
rhalliseyok next, there has been a suggestion to change the time of this meeting from 1600 UTC to 1700 UTC16:09
* jpeeler just saw the telepresence comment16:09
SamYapleno16:09
rhalliseyif you have an issue with that or you like that idea please respond on the email thread with a +1 or a -116:09
SamYaplei can barely stay up for this one16:09
pdbyeah I already replied on the mailing list but it would be a -1 from me16:09
sdakesamyaple do you usually make the 2200 meeting?16:10
SamYapleno16:10
jugglerSamY curious, what is the localtime for you?16:10
rhalliseyexpress your concern via mailing list and we will address that time in two weeks16:10
SamYapleCentral/US, but im thirdshift juggler16:10
SamYaplerhallisey: will do16:10
rhalliseySamYaple, thanks16:10
rhallisey#topic Manifesto Definition Finalization16:11
*** openstack changes topic to "Manifesto Definition Finalization (Meeting topic: kolla)"16:11
rhallisey#link https://etherpad.openstack.org/p/kolla-manifesto16:11
jugglerSamY ouch, thanks for being here then :)16:11
SamYapleno thank YOU juggler16:11
rhalliseylast week we voted on this16:11
rhalliseyI just wanted to see if we can come to a final consensus16:11
jugglermay i make two observations of feedback?16:12
sdakejuggler no16:12
jugglerok :)16:12
sdakeyou mean on the manifesto?16:12
jugglersure16:12
juggleractually 316:12
sdakewhich feedback, if its the stuf we did last week no16:13
sdakeif its the stuff in lines 5-20 yes :)16:13
jugglerthe stuff in line 516:13
sdakeok feel free :)16:13
jugglerand line 116:13
*** ivar-lazzaro has quit IRC16:14
jugglerline 5: I think the "is" should be an "are"16:14
rhalliseyanyone who hasn't approved/disapproved leave a +1/-1 below line 516:14
jugglerline 5: I think "production ready" should be "production-ready"16:14
rhalliseyjuggler, leave your feedback as a comment16:14
sdakejuggler this is what he voting is for :)16:14
rhalliseyI think most of the community is voted, but anyone who hasn't yet you have 2 min16:15
jugglerline 1: Although Manifesto is a valid word, it does weigh some possibly controversial connotations. Perhaps considering a different word, such as "framework" or "action plan" might be suitable considering the open source community experience16:15
inc0community's manifesto...16:16
jugglerjust some outside observations :)16:16
bmacemanifesto is fine.  just because some people have had some odd / questionable ones doesn't make the word invalid :)16:16
sdakebmace+1 voice of reason ;)16:17
rhalliseyIt seem like the general idea and most of the wording is in agreement16:18
rhalliseythat is good progress16:18
sdakecan we finalize the wording ? :)16:18
pdbwhen do we get the tshirts?16:18
SamYaplepop the champange16:18
jugglerpdb lol16:18
bmacehow do you want to do that sdake?  have folks write out the full thing with final wording and then vote on those?16:18
jugglerrhallisey indeed16:19
sdakebmace seems to heavyweight16:19
rhalliseysdake, yes, but we need to make another draft16:19
sdakebmace there is one bone of conflict, the use of is vs are16:19
bmaceor come up with a summary of the micro-changes to the existing one and then people vote on those?  the is vs. are thing is a common one.16:19
SamYaplei say git commit and let the patches decide16:19
sdakeboth is and are are wrong here imo16:19
bmacesure, i think there are several suggestions to yank or re-order a couple of words, some for the sake of minimum verbosity.16:19
sdakewhat would be best is which, which removes the plurality16:20
pdbdanehans suggestion is perfect imo16:20
rhalliseyI agree with danehans suggestion also16:20
pdbI think that part came from my original suggestion, my intention was it was the OpenStack that results from kolla that is fast/stable etc.16:20
sdakedanehans suggestion sovles problem16:20
sdakecan someone make a new draft above the old draft (rhallisey?) with the suggested change so we can read i t in full glory16:21
rhalliseyya I got it16:21
sdakeok quick check for errors16:22
sdakei dont think we need to revote or anything since the wording doesn't materially change the mission16:22
rhalliseyfine with me16:22
SamYapleyup16:22
rhalliseyany objections.. let me look at other comments16:22
jugglerhow about production-ready ?16:23
sdakejuggler that is probably better16:23
rhalliseyI'm fine with that16:23
rhalliseyjmccarthy, you had another comment?16:23
rhalliseyanyone else?16:24
jugglerjust from what i've seen in industry :)16:24
jmccarthyNot intentionally - just the one16:24
rhalliseyjmccarthy, I like having fast as an adjective for kolla16:24
jmccarthyOk I have no major gripe with it, I was just trying to find something to chop16:25
sdakeagree i like fast16:25
pdb+1 on fast16:25
rhalliseyok cool16:25
bmace+1 for trying to be fast at least :)16:25
rhalliseygood work on that16:25
rhalliseylots of community input16:25
sdaketrying to be fast lol :)16:25
rhalliseymoving on16:25
sdakeya brain melt making that one happen ;)16:25
rhallisey#topic Continuous integration16:25
*** openstack changes topic to "Continuous integration (Meeting topic: kolla)"16:25
sdakeI'll update the wiki with it soon16:25
rhalliseySamYaple, jpeeler any updates?16:25
SamYaplei have not been able to provice jpeeler with an aio networking deal yet16:26
jpeelerno, i've been waiting on the networking changes ow baremetal installs to communicate properly16:26
SamYaplelinux-bridge agent is messing with the l2 stuff16:26
SamYaplei can get ovs to work16:26
rhalliseySamYaple, any idea for a time frame?16:26
SamYaplehonestly i dont know if linux bridge can work with a single nic16:27
* sdake groans16:27
SamYapleyea my reaction too16:27
rhallisey:(16:27
sdakesamyaple what about with that mosnterof a script i pasted using bridges16:27
* SamYaple groans16:27
sdakecould that be in some way used even  if it were hacky16:28
SamYapleif it can be hacky, then creating a few vlxan interfaces hsould work16:28
SamYaplebut it will be hacky for sure16:28
sdakei think we are good with hacky16:28
jpeelerreally just want signle nic solution16:28
bmacehacky > impossible16:28
SamYaplei cant get floating ips to work is the issue here16:28
sdakewhat does it take teo create vxlan interfaces16:28
jugglerbmace +116:28
SamYaplei mean with a single interface, im not sure about vxlan16:28
rhalliseyok needs further investigation.. noted16:29
sdakewell dont care how its done, but needs to be done - if you can't do it, I'm not really sure what the next step is16:29
sdakebecause I tried andfailed, fang tried and failed, you tried and resultspending :)16:30
sdakeyour our last great hope :)16:30
harmwhi guys!16:30
SamYaplewhy can we not use two or more interfaces again?16:30
rhalliseyharmw, hey16:30
SamYapleo/16:30
sdakesamyaple the gate machine only has one interface I think16:30
SamYapleok16:30
sdakeits not like we get to say "hey I want 4 routed interfaces" to infra16:30
sdakejpeeler, can you double check that tho16:30
jpeelerand i'm sure others only have one nic too16:31
sdakeit maybe we get two interfaces16:31
harmwmy coreos dockervm has only 1 nic, and that 'just works' so I'm interested in what the issue is16:31
sdakebeyond the gate problem alot of ofolks want to quickly run kolla16:31
jpeelerright16:31
sdakeand quikcly and neutron don't go hand in hand16:31
rhalliseyindeed16:31
SamYaplei mean, if neutron is using infra, then they have to either have multiple interfaces or solved this issue16:31
jpeelerdevstack works with just one nic. surely docker can16:31
pdbSamYaple: thats what I was thinking16:31
sdakedevstack uses ovs jpeeler16:31
SamYaplejpeeler: right, but with linuxbridge?16:31
SamYapleovs i can do in my sleep16:31
pdband we cant use ovs because?16:32
jpeeleri missed why we must use linux bridge (not a networking guy)16:32
sdakethat is all we got atm jpeeler16:32
SamYapleOVS container doesnt exist yet16:32
harmwwe don't have ovs yet16:32
sdakebut ideally we should have ovs and linuxbridge as options16:32
SamYapleIm going to submit on top of fang to get that finished16:32
rhalliseyya OVS is WIP16:32
sdakethose are the two that peope lwant16:32
jpeelerso maybe we have a new pre-req?16:32
inc0by the way...whats up with ovs? this one is kinda critical...16:32
*** praveens has quit IRC16:33
SamYapleinc0: i was waiting on fang, but i see no progress for a while. ill check with fang and patch ontop16:33
pdbits blocked waiting for docker 1.7 afaik16:33
rhalliseyinc0, feng has been working on it, I believe he said it works16:33
SamYaplehe is 90% done16:33
rhalliseyor close to16:33
SamYaplepdb: it is not16:33
pdboh, disregard then :)16:33
harmwdocker 1.6 was neutron magic, 1.7 cinder magic16:33
harmwor something :)16:33
sdakewe are not blocked on docker 1.7 for anything atm but cinder and we are good there with the dev versions16:33
rhalliseyya 1.7 is required for cinder :)16:33
SamYaplecinder/neutron namespace propogation16:33
harmwyep16:34
rhalliseyok we're getting a little off topic, let's move on16:34
sdakeif ovs sovles this gating problem16:34
sdakeI guess I would be good with it16:34
rhalliseycarry over the discussion16:34
rhallisey#topic Liberty Priority Review16:34
SamYapleaye aye16:34
*** openstack changes topic to "Liberty Priority Review (Meeting topic: kolla)"16:34
sdakewould be nice to gate on linuxbridge tho ;)16:34
rhalliseysdake, agreed16:34
rhalliseyfirst BP:  Add a HA container for RabbitMQ16:34
SamYaplerhallisey: that souldnt be a seperate container16:35
rhalliseywas someone working on this?16:35
inc0mstachow will, correct Michal?16:35
inc0after Galera16:35
mstachowThat's correct16:35
SamYaplerabbitmq _is_ HA, it just needs configuration16:35
harmwmirroring, right?16:35
rhalliseyjust an fyi, we're going to go through these BP's quickly16:35
SamYapleyou have to tell the other nodes how to join the cluster, thats it really16:35
rhallisey30sec ea16:35
mstachowThat means we will have updated rabbitmq container ;)16:36
rhalliseySamYaple, next you have two16:36
rhalliseyGenerate ini-type configuration files dynamically16:36
rhalliseyRun with one Interface with Neutron16:36
rhalliseycan you update the status of those? If anything has changed16:36
SamYaplegenerate ini waiting on the spec sdake wrote16:37
rhalliseyjpeeler,  Use tempest to gate our built infrastructure same to you16:37
*** Swami has joined #openstack-meeting-416:37
SamYapleit will tweak how its finally commited as16:37
rhalliseyok thanks16:37
rhalliseyinc0,  Turn galera into a container16:37
sdakerhallisey was that gating thing a milestone 1 blueprint?16:37
rhalliseyI saw your review is up16:37
mstachowThat's me - not inc016:38
inc0its mstachow's , but yeah16:38
rhalliseyoh woops16:38
rhalliseysdake, ya16:38
sdakeimo we should move that out16:38
rhalliseysdake, ok16:38
inc0(he is also Michal, be careful!)16:38
sdaketoo much blockage16:38
rhalliseymstachow, change you status as needed16:38
rhalliseylets see I have a few Cinder BPs16:38
rhalliseythey just need reviews, which would be greatly welcomed16:39
sdakereminder: date is June 25th16:39
*** jckasper has quit IRC16:39
sdakefor deadline16:39
harmwrhallisey: again? guess I missed that16:39
rhalliseyharmw, I haven't updated yet I'm on pto16:39
rhalliseynext week16:39
harmwok, cool16:39
jpeeleri need to write on up for ironic, will do that today16:39
rhalliseythe final BP's look good they all have code reviews up16:40
sdakejpeeler write up what a blueprint?16:40
rhalliseyso folks keep up on the code reviews as best as you can16:40
rhalliseythere's lots to look at16:40
jpeelersdake: yeah16:40
sdakejpeeler there is already a blueprint16:40
rhalliseyjpeeler, I thought there was one16:40
jpeeleroh my bad16:40
sdakejpeeler if you want to take it over feel free :)16:40
sdakeI'm not sure whos working on it16:41
sdakeor if its being worked on16:41
rhalliseyI don't think anyone has worked on it yet16:41
inc0ironic will be required for contenerizing tripleo's undercloud, so I'd opt for bumping priority up16:41
jpeeleryeah i'll take it over if nobody is...16:41
rhalliseyinc0, it would be yes16:41
rhalliseyjpeeler, cool thanks16:41
*** praveens has joined #openstack-meeting-416:41
*** xingchao has quit IRC16:41
sdakeso quick thing about these priorities16:41
jpeelerinc0: that's why :)16:41
* sdake gets on soapbox16:41
sdakethere are a million containers we could produce16:42
sdakewell not really, more like another 20 or so for various services16:42
sdakethis would require packaging the big tent16:42
sdakeI think we have a solid kset of serivces to start with16:42
sdakeif there are some gaps for things like tripleo, lets get those done16:42
sdakebut i'd like to see us focus more on the deploy side of things in the short term16:42
sdakerather then packaging the big tent16:43
sdakethat is a job for RDO16:43
sdakeor source base installs when we get to it16:43
*** xingchao has joined #openstack-meeting-416:43
* sdake gets off soapbox ;)16:43
harmw+1 on deployment for starters16:43
jpeeleragreed16:43
pdb+116:43
harmwplus multihost16:43
rhalliseyok cool16:44
rhalliseyon that note..16:44
rhallisey#topic Ansible Deployment Tooling16:44
*** openstack changes topic to "Ansible Deployment Tooling (Meeting topic: kolla)"16:44
sdakeanyway something to thing about re why things are prioritized the wayt hey are and organized into various liberty-xyz16:44
rhallisey#link https://review.openstack.org/#/c/189157/16:44
sdakenice 30 comments!16:45
rhalliseythis is the current spec for ansible16:45
*** nfedotov has quit IRC16:45
inc0there is quite a discussion about external configs16:45
SamYapleenough so i believe it warrants existing as an option16:45
rhalliseythanks for the comments everyone... If we want to have any further discussion about the spec we can do that now16:45
sdakeexternal configs and 56-57 seem to be the hot areas on the config16:45
sdakeon teh spec16:45
rhalliseysdake, I think external config is a great feature16:46
sdakelines 56-5716:46
inc0SamYaple, thing is, I'm reluctant on having 2 methods of configs16:46
sdakefor lines 56-57 should we just tell people to piss off :)16:46
rhalliseyanyone want to voice their opinion?16:46
SamYapleinc0: were going to have 2 period16:46
pdbthe thing to note here is that SamYaple has come up with a way that may satisfy both sides16:46
SamYaplecrudini is one of them16:47
SamYaplethe bind/env methods are very simliar, enough to count as one in my opinion16:47
pdbit essentially allows external configs while maintaining the idempotency requirement16:47
sdakepdb you mean immutability requirement16:47
SamYaplethe lines of code bind ands would be 10-20, maybe16:47
pdbSamYaple: yes sorry16:47
pdbso my current vote is to support that + crudini16:48
sdakeso re two sources of truth16:48
*** sarob has joined #openstack-meeting-416:48
*** ajayaa has quit IRC16:48
harmwwill we be pushing full cfg files with this? or just the bits that apply to a shipped config-dist?16:48
sdakesamyaple your proposal doesn't solve that problem?16:48
sdakeharmw that is covered inthe spec16:48
harmwok16:48
pdbhmm it does not :(16:49
rhalliseyone bonus of having 2 configs is when we get to deploying the many setups of neutron/cinder, it will be easier to generate those containers from a config file someone has already created16:49
bmacei think there is an option that we discussed, i don't know if it is in the spec yet.. but there would be a flag that controls if kolla pushes out configs at all.. after the initial set up the user can just manage all their configs however they want, puppet, chef... vi + rsync, whatever.16:49
SamYaplesdake: i dont know if it solves that since i dont fully understand "two sources of truth", but it is a very big deal to most people and _not_ a required method16:49
bmacei believe sdake is concerned about having multiple places "in charge" of the config data.16:49
rhalliseybmace, exactly16:49
bmacewhich is why it needs to be clearly either a) kolla control or b) user control.16:50
sdakesamyaple reading your 7:09 proposal atm16:50
SamYaplei believe I can tie env/bind/users own config all together16:50
inc0rhallisey, at some point we might want to have different configs on several nodes, so you'd need to use different containers with just one option that differs?16:50
SamYapleit dont believe it will add that much extra work, it certianly wont be dokcer start commands16:51
SamYapleextra* docker start commands16:51
rhalliseyinc0, kolla as a tool can be used to build and run containers16:52
pdbout of interest, am I the only one who is not a fan of the env method regardless of the internal/external debate?16:52
SamYaplethe 3 cases as I see them16:52
SamYaple1 env variables as spec describes16:52
SamYaple2 ansible lays out configs and the get bind mounted into the container, local changes persist to config until ansible runs again16:52
SamYaple3 user managed configs16:52
rhalliseyso we can allow users to build their own or we can build them and they can run them16:52
SamYaplepdb: no, im not a fan. but i understand the argument16:53
*** dannywilson has quit IRC16:53
inc0my suggestion: just expose /etc/myproject from host to container and have config there16:53
sdakethis breaks immutability!16:53
inc0I don't see why kolla should even care about config management? this is muddy place16:53
SamYaplesdake: i dont think anyone cares at that level16:53
SamYaplebut you can keep immutability with the env option16:54
sdakeis the env option you mean the docker moduels you created?16:54
bmacesdake at least it doesn't allow for the modification of the config file while the container is actually running, so better than a straight up bind / direct-read.16:54
SamYapleyes sdake16:54
sdakebmace agreed16:54
sdakeso as I red your 7:08 proposal have 3 models16:54
sdake1 is crudini16:54
sdake2 is bindmount with immutability brekage16:55
sdake3 is docker env without immutabilitybreakage16:55
*** ivar-lazzaro has joined #openstack-meeting-416:55
SamYapleyes. all user managed configs can be lumped in with 216:55
*** mfedosin has quit IRC16:55
sdake2 results in two sources of truth as well16:55
pdbthere's a variation on 2) that gives mutability16:55
pdb*immutability16:55
pdb:/16:55
SamYaplepdb: there really isnt16:56
sdakei want to hear variation of 2 that gives immutability16:56
harmwimmutability is something we shouldn't throw away easily..16:56
*** bharath has joined #openstack-meeting-416:56
pdbcontainer copies configs into itself on start16:56
inc0pdb, changes of configs will be small pit in hell16:56
SamYaplepdb: yea but thats the same as doign it the env way, since ansible starts it16:56
*** asselin has joined #openstack-meeting-416:56
bmacewith 2, either kolla blows down new config files and wipes out any local changes, or they configure an option to control all configs themselves.. so there is only one master, that is the intent at least.16:56
pdbSamYaple: you can drop your own configs on there for it to grab though16:57
rhalliseywhy can't we do 1 and 3 ( as optional)?16:57
inc0also, we'll want services to be able to reread configs without restarting, and all these makes this impossible16:57
SamYaplerhallisey: would be my vote16:57
rhallisey1 is our primary and 3 as optional16:57
SamYapleinc0: thats not possible anyway16:57
harmwshould we move in complete configs, we'll be tasked with keeping those up2date as well... we shouldn't be bottered with that16:57
inc0SamYaple, actually it is16:57
inc0using oslo.config16:57
inc0but what is lacking is way to call it inside service, but that's not that hard16:58
SamYapleinc0: are you saying sevices reread thier configs on the fly right now?16:58
rhalliseyhey guys keep in mind we have 2min left16:58
SamYapletable that inc016:58
harmw(was about to say just that)16:58
sdakeoslo.config is web scale16:58
SamYapleall of the users and admins I have spoken with want option 2 to exist16:59
SamYapleit doesnt need to be default, but it needs to be there16:59
sdakeok i would relaly like to get to the bottom of the config strategy, so can we overflow for a bit into #kolla since our time is out :)16:59
rhalliseySamYaple, why do they care about option 2 if you can offer 3?16:59
inc0I come from ops background and yeah, ops will want it, immutability or not16:59
SamYaplerhallisey: #kolla17:00
rhalliseyoption 2 makes me think of devstack17:00
rhalliseyok out of time17:00
*** jasonsb has left #openstack-meeting-417:00
rhalliseywe will move over to #kolla17:00
rhalliseythanks all!17:00
*** jmccarthy has left #openstack-meeting-417:00
rhallisey#endmeeting kolla17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Jun 10 17:00:40 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-06-10-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-06-10-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-06-10-16.01.log.html17:00
*** kenhui has joined #openstack-meeting-417:08
*** bmace has left #openstack-meeting-417:09
*** puranamr has joined #openstack-meeting-417:11
*** simon-AS559 has joined #openstack-meeting-417:12
*** loth has quit IRC17:15
*** KunalGandhi has joined #openstack-meeting-417:15
*** kenhui has quit IRC17:16
*** singleth_ has joined #openstack-meeting-417:16
*** singlethink has quit IRC17:20
*** daneyon has quit IRC17:21
*** rhallisey is now known as rhallisey|PTO17:23
*** praveens has quit IRC17:23
*** xingchao has quit IRC17:25
*** belmoreira has joined #openstack-meeting-417:30
*** sdake has quit IRC17:31
*** sbalukoff has joined #openstack-meeting-417:32
*** inc0 has quit IRC17:34
*** ivar-lazzaro has quit IRC17:37
*** krtaylor has quit IRC17:37
*** daneyon has joined #openstack-meeting-417:40
*** jckasper has joined #openstack-meeting-417:41
*** IlyaG has joined #openstack-meeting-417:41
*** yamahata has quit IRC17:42
*** mwang2_ has joined #openstack-meeting-417:44
*** Slower has quit IRC17:44
*** Slower has joined #openstack-meeting-417:45
*** mwang2 has quit IRC17:45
*** Sukhdev has quit IRC17:46
*** GB21 has quit IRC17:46
*** Sukhdev has joined #openstack-meeting-417:46
*** MarkAtwood has quit IRC17:54
*** fallenpegasus has quit IRC17:55
*** dannywilson has joined #openstack-meeting-417:56
*** vinkman has left #openstack-meeting-417:56
*** krtaylor has joined #openstack-meeting-417:59
*** dannywil_ has joined #openstack-meeting-418:00
*** dannywilson has quit IRC18:00
*** s3wong has joined #openstack-meeting-418:06
*** daneyon has quit IRC18:14
*** daneyon has joined #openstack-meeting-418:16
*** yamahata has joined #openstack-meeting-418:20
*** Sukhdev has quit IRC18:22
*** bradjones has quit IRC18:23
*** bradjones has joined #openstack-meeting-418:24
*** bradjones has quit IRC18:24
*** bradjones has joined #openstack-meeting-418:24
*** singlethink has joined #openstack-meeting-418:26
*** daneyon has quit IRC18:26
*** amotoki has quit IRC18:28
*** singleth_ has quit IRC18:29
*** ivar-lazzaro has joined #openstack-meeting-418:29
*** aventerav has quit IRC18:32
*** ivar-lazzaro has quit IRC18:34
*** aventerav has joined #openstack-meeting-418:37
*** fallenpegasus has joined #openstack-meeting-418:38
*** ivar-lazzaro has joined #openstack-meeting-418:40
*** bharath has quit IRC18:47
*** jwagner is now known as jwagner_away18:51
*** vinkman has joined #openstack-meeting-418:53
*** jwagner_away is now known as jwagner18:53
*** vinkman has left #openstack-meeting-418:53
*** nateziemann has joined #openstack-meeting-418:58
*** Swami has quit IRC19:05
*** xingchao has joined #openstack-meeting-419:14
*** Sukhdev has joined #openstack-meeting-419:14
*** puranamr has quit IRC19:17
*** mstachow has quit IRC19:24
*** Bjoern__ has joined #openstack-meeting-419:25
*** paramite has joined #openstack-meeting-419:26
*** xingchao has quit IRC19:27
*** jwagner is now known as jwagner_away19:28
*** amotoki has joined #openstack-meeting-419:29
*** puranamr has joined #openstack-meeting-419:30
*** amotoki has quit IRC19:34
*** kenhui has joined #openstack-meeting-419:35
*** paramite has quit IRC19:36
*** tpatil has joined #openstack-meeting-419:42
*** nateziemann has quit IRC19:47
*** galstrom is now known as galstrom_zzz19:55
*** galstrom_zzz is now known as galstrom19:56
*** jwagner_away is now known as jwagner19:58
*** fallenpegasus has quit IRC19:59
*** mwang2_ has quit IRC20:00
*** mwang2 has joined #openstack-meeting-420:01
tpatilIs there is log working group meeting today?20:02
jokke_o/20:02
dhellmanno/20:02
dhellmannI don't see Rocky...20:03
*** puranamr has quit IRC20:03
*** IlyaG has quit IRC20:03
tpatilok20:03
jokke_should we go on without her or give few more minutes?20:04
jokke_I haven't received any agenda either so I'm not really up to speed what's going on20:05
dhellmannlet's at least start a meeting to record that we were here, maybe we can use the time to figure out what we need to be doing20:05
tpatilI wanted to talk about the Request Id specs as mentioned in the agenda20:05
dhellmann#startmeeting log_wg20:05
openstackMeeting started Wed Jun 10 20:05:38 2015 UTC and is due to finish in 60 minutes.  The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot.20:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:05
*** openstack changes topic to " (Meeting topic: log_wg)"20:05
openstackThe meeting name has been set to 'log_wg'20:05
*** mwang2_ has joined #openstack-meeting-420:05
dhellmann#topic attendance20:05
*** openstack changes topic to "attendance (Meeting topic: log_wg)"20:05
jokke_o/20:05
dhellmannwho's here for the logging group meeting?20:05
dhellmanno/20:06
tpatilo/20:06
dhellmann#topic request-id spec20:06
*** openstack changes topic to "request-id spec (Meeting topic: log_wg)"20:06
dhellmanntpatil: you're up!20:06
tpatilWe have reached out on the openstack -dev mailing list to get consensus on any of 3 proposed solutions.20:06
*** sdake has joined #openstack-meeting-420:06
tpatil#1 Return tuple containing headers and body from : 3 +1’s20:06
tpatil#2 Use thread local storage to store 'x-openstack-request-id' returned from headers : 0 +120:06
tpatil#3 Unique request-id across OpenStack Services : 1 +120:07
tpatilPros and cons of each of the above solutions is also discussed on the openstack-dev mailing list thread.20:07
dhellmanntpatil: have you had any luck talking with the rally/osprofiler team about reusing the work they did?20:07
tpatil#link : http://lists.openstack.org/pipermail/openstack-dev/2015-May/064842.html20:07
tpatildhellmann: Not yet, We have to check how does that works.20:07
tpatilSo far, Solution #1 is leading but still I don’t see any +1 on the specs20:08
dhellmanntpatil: I think you're going to get much more traction with that20:08
*** mwang2 has quit IRC20:08
dhellmanntpatil: no, I'm -2 on that approach because it breaks backwards compatibility with existing users of those clients and we can't do that20:08
*** fallenpegasus has joined #openstack-meeting-420:08
tpatildhellman: You are correct20:09
tpatildhellman:Based on your comment, we have come up with Solution #2. Please so far no have given +1 on the specs.20:09
tpatilWe need some direction from the community. We are totally committed to implement this spec for Liberty.20:10
dhellmannok, I have been waiting to see what the osprofiler discussion brings up, because we want to find a shared solution to this and they seem to already be doing it pretty well20:10
tpatilAnother point is, If client api bindings are used in the third party applications, then there is no way for them to know the x-openstack-request-id so they might find it difficult to resolve the issue with the service provider.20:11
tpatilIf x-openstack-request-id is made available as in Solution #1 and #2,then I think it could solve many such potential use cases.20:11
dhellmannwe can fix that with documentation, though20:11
dhellmannyeah, changing the return type of all client API calls is really really not an option, so you need to look at the other solutions more closely20:12
tpatildhellman: solution #2 is next closer solution then, but so far no response on that solution.20:13
dhellmanntpatil: as I said, I am reserving judgement until I see the update discussion osprofiler. Please talk to boris-42 and the rest of the osprofiler team about it.20:13
tpatildhellman: Sure , Thanks. I will understand about osprofiler till then.20:14
dhellmanntpatil: ok, sounds good, thank you20:14
dhellmanntpatil: you should also talk to the openstack sdk team about how best to expose request ids in the new python sdk20:15
jokke_I'm wondering if I responded to that mail or not20:16
tpatildhellman: Ok, I will do that. Thanks.20:17
*** VW has quit IRC20:17
dhellmanntpatil: excellent20:17
dhellmannjokke_: ?20:17
dhellmann#topic other pending action items20:19
*** openstack changes topic to "other pending action items (Meeting topic: log_wg)"20:19
dhellmanndo we have anything else we need to be working on?20:19
dhellmannthere is the message id spec to be updated, too, I wonder if we should find someone to help Rocky with those changes?20:19
*** VW has joined #openstack-meeting-420:19
jokke_I thin we should ... I unfortunately don't have the cycles to do it atm. due to internal commitments20:21
jokke_think20:21
dhellmannI'm not the best advocate, since I'm not sure it's a good idea to begin with :-)20:21
jokke_;)20:22
jokke_Yeah ... these two are just the big things ops are crying from us ... and I totally understand why20:22
jokke_has there been any continuation on that log formatting change we talked about in the summit?20:24
jokke_is there anything we could act on?20:24
*** VW has quit IRC20:24
dhellmannI've been bogged down with some other work, so haven't started that, yet.20:24
dhellmannthere are a couple of parts of that20:24
dhellmannfirst, we need all projects to be using oslo.context as the base for their request context20:25
dhellmannthat gives us a central place to make sure we have good values to be used in oslo.log default format strings20:25
dhellmannso if folks have time, and want to start with something, updating projects to use oslo.context would be a good first step20:25
jokke_ok, it would be also nice to have the projects using oslo.log as well20:25
dhellmannyes, that's a good second step -- if a project is using neither, it may need to be updated to use both at the same time20:26
jokke_ok, good to know ... I think there was some work done on Glance around that and I'll have a look where it's hanging20:26
jokke_Swift is one good example IIRC they don't use oslo.log20:26
dhellmannyeah, I don't expect them to adopt it20:26
dhellmannlet's focus on the projects that are already using the incubated version of that code, first20:27
jokke_aa ok20:27
jokke_we have still those around as well?20:27
dhellmannI honestly haven't looked yet20:27
jokke_no worries20:28
dhellmannas far as I know, we either have projects using incubated oslo logging code, oslo.log, or they are swift.20:28
jokke_;)20:28
dhellmannI don't think there are any other projects not using some form of that logging code20:28
jokke_ok, do you know the reasoning behind swift being the special snowflake?20:29
*** Slower has quit IRC20:29
dhellmannhistory20:29
notmynamelogging predates oslo.log, oslo logging has a lot of nova-isms (at least originally) and not enough other stuff (again, originally), and logs are as much an api as anything else20:29
notmynameor as dhellmann said, "history" ;-)20:30
dhellmannyeah, I'm not really interested in changing that situation right now -- we have a lot of other projects that we can work with to clean up their logs20:30
dhellmannswift's logs are good, they're just different20:30
*** galstrom is now known as galstrom_zzz20:30
jokke_fair enough20:30
dhellmannnotmyname: thanks :-)20:30
*** VW has joined #openstack-meeting-420:30
notmynamefor the record, I am interested in log compatibility20:30
dhellmannthat's good to know20:31
dhellmannit would be good to collect a summary of how swift logging is different from oslo.log, and what features may be needed to reconcile the 220:31
notmynamehttp://docs.openstack.org/developer/swift/logs.html20:31
dhellmannk, thanks20:32
*** IlyaG has joined #openstack-meeting-420:32
notmynameI too would be interested in that. if you have a summary at some point, i'd love to read it20:32
dhellmannnotmyname: you might find https://blueprints.launchpad.net/oslo.log/+spec/app-agnostic-logging-parameters interesting, although it does not yet try to directly address the swift case20:33
notmynameoh yes. the "instance" was one of my beefs with oslo.log20:33
dhellmannyeah, we got that from nova, and we're working to get rid of it this cycle to be replaced with "resource"20:34
dhellmannok, let's move on20:35
dhellmann#topic open discussion20:35
*** openstack changes topic to "open discussion (Meeting topic: log_wg)"20:35
notmynameI'm happy to take this up later. I won't jump in your meeting any longer ;-)20:35
jokke_btw bit aside from the topic ... It's funny to follow this power battle between Swift and Nova from perspective where I haven't been involved that long that I would know all the history around20:35
dhellmanndoes anyone have anything else to raise?20:35
notmynamebut good to see progress :-)20:35
dhellmannnotmyname: no, thanks for dropping by, I appreciate the feedback and references20:35
notmynamejokke_: power battel?20:35
*** ajmiller_ has joined #openstack-meeting-420:36
jokke_notmyname: oh yeah ... lots of folks expecting everyone else doing stuff in specific way because [swift|nova] does it that specific way20:36
*** dannywilson has joined #openstack-meeting-420:37
jokke_it's quite funny in an annoying way20:37
notmynamejokke_: it's mostly independent organic growth and lack of communication (on all sides) that has gotten us to where we are today20:37
*** sdake has quit IRC20:37
notmynamebut that being said, I'm not generally displeased with the state of most things where there are differences. there is room for improvement, of course20:38
jokke_notmyname: yeah I kind of figured that out over past few months and it is easier to filter now.20:39
notmyname:-)20:39
*** dannywil_ has quit IRC20:39
*** ajmiller has quit IRC20:40
jokke_notmyname: differencies are not bad in general (otherwise we could have just one project and recycle everything) ... they become a problem when people expects the history to drive the future (or the differencies are somewhere like in logs that makes the troubleshooting nightmare)20:40
*** IlyaG has quit IRC20:40
jokke_which would be nice to get sorted ... I don't care what projects does per default but it would be nice to have easy way to uniform for those who do prefer it20:41
notmynamewhen people expect their view of history to drive someone else's future ;-)20:41
notmynamejokke_: yup. I agree with that20:41
notmynamemostly that's a question of prioritization20:42
jokke_notmyname: I didn't want to get to that specifics ... next good step would be start picking names as examples ;)20:42
notmynameso to get eg logs to unify (ie the general topic of this meeting, AIUI), we need the ability in swift to configure the logged fields20:43
*** rhefner has left #openstack-meeting-420:43
notmynameand simply nobody has sat down and typed in that code20:43
notmynamebut I'd definitely support someone who wanted to, and I'd be happy to review it20:44
jokke_notmyname: so you wouldn't see a problem bringing oslo.log in swift it the default output would look like it is now (and the would be config option to turn it looking like rest of the OS service logs) and someone would actually do the work to get that done?20:45
dhellmannI hope to finish the projects I'm working on now in the next couple of weeks, and start working on some of this logging stuff then.20:45
*** Slower has joined #openstack-meeting-420:45
jokke_notmyname: because if that's the case I probably could try at least to allocate the cycles for M to do that (for Liberty I have already too much on my plate)20:47
notmynamejokke_: I think a new dependency is a separate concern. suffice to say, maybe. but I'm not sure that would be necessary20:47
notmynamedoes oslo.log depend on oslo.config?20:47
*** puranamr has joined #openstack-meeting-420:47
dhellmannnotmyname: yes20:47
notmynameah20:47
dhellmannthat's how deployers configure the format string20:47
notmynameusing oslo.config would be very painful for swift. unlikely to happen20:48
dhellmanneven if it's just for the log settings?20:48
jokke_notmyname: ah, didn't think of that, but perhaps we can work around it20:48
notmynametherefore log configuration would be done in a config format in swift's configs20:49
dhellmannyeah, as I said, we'll get further working with some of the other projects to start20:49
jokke_sounds like a plan20:50
jokke_My biggest wish atm is that on the next summit we would have some concrete out of this workgroup to secure the ops collaboration with us. If we don't get anything done why should they waste their (and we ours) time on this20:51
dhellmannyes, I think that's a valid concern20:52
dhellmannso far the 2 proposals being championed by this group don't have a lot of traction among developers20:52
jokke_nope ... and I'm really sad about that because those have been the two biggest painpoints the actual deployers have brought to us20:53
dhellmannwell, the request id thing just needs more work, but the message id proposal is going to cause a lot of developer pain the way it is now so I think that one needs to be very seriously rethought with that in mind20:54
jokke_the third on same magnitude has been the log formatting20:54
dhellmannthat's going to happen just as a matter of getting everyone to use the same log library, so I'm not as worried about that20:54
*** daneyon has joined #openstack-meeting-420:56
dhellmannwe're about out of time, is there anything else we should try to cover this week?20:56
jokke_I think we're pretty set ... I'll try to reach Rocky before next meeting and sync up with her to see where she needs help20:57
*** puranamr has quit IRC20:57
*** fallenpegasus has quit IRC20:58
dhellmannsounds good20:58
dhellmannlet's call it 2 minutes early, then20:58
dhellmann#endmeeting20:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:58
*** puranamr has joined #openstack-meeting-420:58
openstackMeeting ended Wed Jun 10 20:58:35 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-06-10-20.05.html20:58
jokke_yeah, thanks20:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-06-10-20.05.txt20:58
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-06-10-20.05.log.html20:58
dhellmannthanks, jokke_20:58
tpatilThanks,everyone20:58
dhellmannthanks, tpatil, I didn't realize you were still here :-)20:59
jokke_nite all20:59
tpatildhellman: I was on silence mode :)20:59
dhellmanntpatil: I need to find the stealth mode switch in my irc client :-)20:59
*** tpatil has left #openstack-meeting-421:03
*** belmoreira has quit IRC21:04
*** simon-AS559 has quit IRC21:04
*** songole has joined #openstack-meeting-421:04
*** songole has left #openstack-meeting-421:04
*** simon-AS559 has joined #openstack-meeting-421:06
*** simon-AS5591 has joined #openstack-meeting-421:08
*** fallenpegasus has joined #openstack-meeting-421:10
*** simon-AS559 has quit IRC21:12
*** Sukhdev has quit IRC21:14
*** VW has quit IRC21:16
*** ziemann has joined #openstack-meeting-421:21
*** sdake has joined #openstack-meeting-421:22
*** singleth_ has joined #openstack-meeting-421:22
*** singlethink has quit IRC21:25
*** amotoki has joined #openstack-meeting-421:31
*** bnemec has quit IRC21:31
*** KunalGandhi has quit IRC21:33
*** simon-AS5591 has quit IRC21:35
*** amotoki has quit IRC21:36
*** singlethink has joined #openstack-meeting-421:38
*** Swami has joined #openstack-meeting-421:40
*** singleth_ has quit IRC21:41
*** singlethink has quit IRC21:44
*** bharath has joined #openstack-meeting-421:47
*** puranamr has quit IRC21:47
*** bharath has quit IRC21:52
*** marcusvrn has quit IRC21:54
*** ivar-laz_ has joined #openstack-meeting-422:02
*** klamath has quit IRC22:04
*** ivar-lazzaro has quit IRC22:05
*** salv-orlando has joined #openstack-meeting-422:05
*** daneyon has quit IRC22:06
*** Sukhdev has joined #openstack-meeting-422:07
*** kenhui has quit IRC22:07
*** fallenpegasus has quit IRC22:08
*** singlethink has joined #openstack-meeting-422:09
*** jwagner is now known as jwagner_away22:13
*** salv-orlando has quit IRC22:18
*** bharath has joined #openstack-meeting-422:26
*** amotoki has joined #openstack-meeting-422:32
*** s3wong has quit IRC22:34
*** KunalGandhi has joined #openstack-meeting-422:35
*** s3wong has joined #openstack-meeting-422:36
*** salv-orlando has joined #openstack-meeting-422:36
*** amotoki has quit IRC22:36
*** singlethink has quit IRC22:36
*** ziemann has quit IRC22:37
*** Bjoern__ has quit IRC22:42
*** daneyon has joined #openstack-meeting-422:44
*** daneyon has quit IRC22:45
*** daneyon has joined #openstack-meeting-422:45
*** kenhui has joined #openstack-meeting-422:46
*** sigmavirus24 is now known as sigmavirus24_awa22:46
*** puranamr has joined #openstack-meeting-422:48
*** puranamr has quit IRC22:53
*** bknudson has quit IRC22:54
*** krtaylor has quit IRC22:54
*** puranamr has joined #openstack-meeting-423:01
*** nateziemann has joined #openstack-meeting-423:03
*** kenhui has quit IRC23:03
*** daneyon has quit IRC23:04
*** daneyon has joined #openstack-meeting-423:07
*** aventerav has quit IRC23:08
*** kenhui has joined #openstack-meeting-423:08
*** rods1 has quit IRC23:10
*** sdake has quit IRC23:10
*** Gavin_Pratt_HP has joined #openstack-meeting-423:13
*** xingchao has joined #openstack-meeting-423:14
*** daneyon has quit IRC23:19
*** daneyon has joined #openstack-meeting-423:19
*** xingchao has quit IRC23:21
*** ivar-laz_ has quit IRC23:24
*** daneyon has quit IRC23:25
*** ivar-lazzaro has joined #openstack-meeting-423:25
*** xingchao has joined #openstack-meeting-423:35
*** krtaylor has joined #openstack-meeting-423:38
*** david-lyle has quit IRC23:40
*** carl_baldwin has quit IRC23:42
*** blahRus has quit IRC23:44
*** IlyaG has joined #openstack-meeting-423:53
*** circ-user-zdm0N has joined #openstack-meeting-423:57
*** circ-user-zdm0N is now known as markvoelker_23:57
*** markvoelker_ has quit IRC23:58
*** Gavin_Pratt_HP has quit IRC23:59
*** IlyaG has quit IRC23:59

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