Wednesday, 2015-11-11

*** amotoki has joined #openstack-meeting-400:00
*** Sukhdev has joined #openstack-meeting-400:03
*** dims has joined #openstack-meeting-400:08
*** banix has joined #openstack-meeting-400:11
*** dims has quit IRC00:16
*** jmckind has joined #openstack-meeting-400:22
*** armax has joined #openstack-meeting-400:23
*** bpokorny has quit IRC00:23
*** yamahata has joined #openstack-meeting-400:23
*** banix has quit IRC00:25
*** CheKoLyN has quit IRC00:30
*** pmesserli has quit IRC00:31
*** memogarcia has quit IRC00:35
*** memogarcia has joined #openstack-meeting-400:37
*** ducttape_ has joined #openstack-meeting-400:42
*** Sukhdev has quit IRC00:48
*** salv-orlando has quit IRC00:49
*** limao has joined #openstack-meeting-400:49
*** harshs has joined #openstack-meeting-400:59
*** ShillaSaebi has joined #openstack-meeting-401:02
*** harshs_ has joined #openstack-meeting-401:04
*** harshs has quit IRC01:07
*** harshs_ is now known as harshs01:07
*** zeih has joined #openstack-meeting-401:07
*** vikasc_ has joined #openstack-meeting-401:11
*** zeih has quit IRC01:11
*** SimonChung has quit IRC01:13
*** _ducttape_ has joined #openstack-meeting-401:15
*** ducttape_ has quit IRC01:18
*** bobh has joined #openstack-meeting-401:22
*** dims has joined #openstack-meeting-401:27
*** _ducttape_ has quit IRC01:29
*** jruano has quit IRC01:32
*** baigk has quit IRC01:35
*** memogarcia has quit IRC01:35
*** woodard has quit IRC01:37
*** memogarcia has joined #openstack-meeting-401:38
*** xingchao has joined #openstack-meeting-401:39
*** xingchao has quit IRC01:39
*** xingchao has joined #openstack-meeting-401:40
*** angdraug has quit IRC01:40
*** Sukhdev has joined #openstack-meeting-401:43
*** tfukushima has joined #openstack-meeting-401:45
*** Sukhdev has quit IRC01:46
*** baohua has joined #openstack-meeting-401:47
*** prashantD has quit IRC01:55
*** salv-orlando has joined #openstack-meeting-401:57
*** salv-orlando has quit IRC01:59
*** salv-orlando has joined #openstack-meeting-401:59
*** memogarcia has quit IRC02:02
*** xingchao has quit IRC02:07
*** jmckind has quit IRC02:10
*** angdraug has joined #openstack-meeting-402:19
*** ShillaSaebi has quit IRC02:20
*** vikasc_ has quit IRC02:26
*** MarkAtwood has joined #openstack-meeting-402:37
*** xingchao has joined #openstack-meeting-402:37
*** salv-orlando has quit IRC02:46
*** isq has quit IRC02:52
*** isq has joined #openstack-meeting-402:52
*** isq has quit IRC02:53
*** isq has joined #openstack-meeting-402:53
*** MarkAtwood has quit IRC02:54
*** yamahata has quit IRC02:54
*** s3wong has quit IRC03:01
*** woodard has joined #openstack-meeting-403:09
*** Sukhdev has joined #openstack-meeting-403:11
*** woodard has quit IRC03:13
*** ShillaSaebi has joined #openstack-meeting-403:19
*** ShillaSaebi has quit IRC03:20
*** angdraug has quit IRC03:22
*** bobh has quit IRC03:30
*** Sukhdev has quit IRC03:30
*** harshs has quit IRC03:32
*** harshs has joined #openstack-meeting-403:35
*** fawadkhaliq has joined #openstack-meeting-403:39
*** dims has quit IRC03:46
*** salv-orlando has joined #openstack-meeting-403:47
*** MarkAtwood has joined #openstack-meeting-403:47
*** banix has joined #openstack-meeting-403:51
*** salv-orlando has quit IRC03:52
*** harshs has quit IRC03:53
*** zeih has joined #openstack-meeting-403:54
*** vikasc_ has joined #openstack-meeting-403:55
*** zeih has quit IRC03:58
*** vikasc_ has quit IRC04:00
*** fawadkhaliq has quit IRC04:17
*** hogepodge has quit IRC04:35
*** xingchao has quit IRC04:45
*** sdake has joined #openstack-meeting-404:47
*** salv-orlando has joined #openstack-meeting-404:48
*** salv-orlando has quit IRC04:52
*** vishwanathj has quit IRC04:57
*** baoli has quit IRC04:57
*** baoli has joined #openstack-meeting-404:58
*** fawadkhaliq has joined #openstack-meeting-405:02
*** mestery has joined #openstack-meeting-405:08
*** sdake has quit IRC05:10
*** sdake has joined #openstack-meeting-405:15
*** banix has quit IRC05:18
*** baoli has quit IRC05:20
*** baoli has joined #openstack-meeting-405:20
*** xingchao has joined #openstack-meeting-405:22
*** sdake has quit IRC05:24
*** baoli has quit IRC05:25
*** baoli has joined #openstack-meeting-405:27
*** xingchao has quit IRC05:35
*** xingchao has joined #openstack-meeting-405:37
*** harshs has joined #openstack-meeting-405:41
*** subscope has joined #openstack-meeting-405:45
*** ifat_afek has joined #openstack-meeting-405:53
*** mestery has quit IRC06:01
*** fawadkhaliq has quit IRC06:01
*** fawadkhaliq has joined #openstack-meeting-406:02
*** nikhil has quit IRC06:02
*** nikhil has joined #openstack-meeting-406:02
*** fawadk has joined #openstack-meeting-406:03
*** fawadkhaliq has quit IRC06:04
*** jpekkari has joined #openstack-meeting-406:10
*** mestery has joined #openstack-meeting-406:15
*** mestery has quit IRC06:19
*** anil_rao has joined #openstack-meeting-406:19
*** anil_rao has quit IRC06:20
*** harshs has quit IRC06:32
*** subscope has quit IRC06:32
*** zeih has joined #openstack-meeting-406:41
*** harshs has joined #openstack-meeting-406:41
*** zeih has quit IRC06:46
*** harshs has quit IRC06:52
*** jpeeler has quit IRC06:55
*** sdake has joined #openstack-meeting-406:58
*** sdake has quit IRC06:59
*** baoli has quit IRC07:20
*** baoli has joined #openstack-meeting-407:21
*** baoli has quit IRC07:25
*** nkrinner has joined #openstack-meeting-407:26
*** armax has quit IRC07:29
*** logan2 has quit IRC07:40
*** logan2 has joined #openstack-meeting-407:40
*** whydidyoustealmy has joined #openstack-meeting-407:43
*** yamamoto has quit IRC07:43
*** barra204 has quit IRC07:43
*** fawadk has quit IRC07:57
*** fawadkhaliq has joined #openstack-meeting-407:58
*** zeih has joined #openstack-meeting-408:02
*** ifat_afek has quit IRC08:03
*** zeih has quit IRC08:06
*** subscope has joined #openstack-meeting-408:07
*** gb21 has quit IRC08:12
*** fawadkhaliq has quit IRC08:13
*** gb21 has joined #openstack-meeting-408:14
*** zeih has joined #openstack-meeting-408:18
*** yamamoto_ has joined #openstack-meeting-408:23
*** jpeeler has joined #openstack-meeting-408:23
*** ifat_afek has joined #openstack-meeting-408:32
*** subscope has quit IRC08:52
*** slaweq has joined #openstack-meeting-408:55
*** subscope has joined #openstack-meeting-409:08
*** _degorenko is now known as degorenko09:10
*** fawadkhaliq has joined #openstack-meeting-409:12
*** igordcard has joined #openstack-meeting-409:16
*** fawadkhaliq has quit IRC09:23
*** belmoreira has joined #openstack-meeting-409:41
*** fawadkhaliq has joined #openstack-meeting-409:44
*** limao has quit IRC09:45
*** baohua has quit IRC09:45
*** subscope has quit IRC09:46
*** janiceonchn has joined #openstack-meeting-409:46
*** baoli has joined #openstack-meeting-409:48
*** dshakhray has joined #openstack-meeting-409:50
*** baoli has quit IRC09:53
*** yamamoto_ has quit IRC09:54
*** janiceonchn has quit IRC09:57
*** yamamoto has joined #openstack-meeting-409:58
*** subscope has joined #openstack-meeting-409:58
*** amotoki has quit IRC10:00
*** ifat_afek has quit IRC10:01
*** ifat_afek has joined #openstack-meeting-410:01
*** yamamoto has quit IRC10:03
*** yamamoto has joined #openstack-meeting-410:11
*** pbourke has quit IRC10:13
*** pbourke has joined #openstack-meeting-410:16
*** janiceonchn has joined #openstack-meeting-410:24
*** janiceonchn has quit IRC10:24
*** janiceonchn has joined #openstack-meeting-410:25
*** janiceonchn has quit IRC10:25
*** janiceonchn has joined #openstack-meeting-410:26
*** yamamoto has quit IRC10:27
*** ifat_afek has left #openstack-meeting-410:32
*** nikhil has quit IRC10:36
*** nikhil has joined #openstack-meeting-410:36
*** markvoelker has quit IRC10:37
*** Sukhdev has joined #openstack-meeting-410:38
*** limao has joined #openstack-meeting-410:43
*** xingchao has quit IRC10:43
*** yamamoto has joined #openstack-meeting-410:49
*** subscope has quit IRC10:53
*** subscope has joined #openstack-meeting-410:53
*** MarkAtwood has quit IRC11:01
*** xingchao has joined #openstack-meeting-411:09
*** xingchao has quit IRC11:14
*** subscope has quit IRC11:14
*** amotoki has joined #openstack-meeting-411:22
*** fawadkhaliq has quit IRC11:26
*** fawadkhaliq has joined #openstack-meeting-411:34
*** fawadkhaliq has quit IRC11:35
*** fawadkhaliq has joined #openstack-meeting-411:36
*** markvoelker has joined #openstack-meeting-411:37
*** memogarcia has joined #openstack-meeting-411:38
*** tfukushima has quit IRC11:41
*** dims has joined #openstack-meeting-411:41
*** markvoelker has quit IRC11:42
*** MarkAtwood has joined #openstack-meeting-411:47
*** memogarcia has quit IRC11:48
*** slaweq has quit IRC11:50
*** MarkAtwood has quit IRC11:51
*** fawadkhaliq has quit IRC12:02
*** subscope has joined #openstack-meeting-412:04
*** baohua has joined #openstack-meeting-412:05
*** jpekkari has quit IRC12:24
*** baohua_ has joined #openstack-meeting-412:30
*** baohua has quit IRC12:31
*** baohua_ has quit IRC12:42
*** baohua has joined #openstack-meeting-412:42
*** bobh has joined #openstack-meeting-412:53
*** markvoelker has joined #openstack-meeting-412:53
*** markvoelker has quit IRC12:58
*** dims has quit IRC12:59
*** fawadkhaliq has joined #openstack-meeting-412:59
*** bobh has quit IRC12:59
*** salv-orlando has joined #openstack-meeting-413:03
*** igordcard_ has joined #openstack-meeting-413:05
*** memogarcia has joined #openstack-meeting-413:07
*** igordcard has quit IRC13:07
*** salv-orlando has quit IRC13:09
*** delattec has joined #openstack-meeting-413:10
*** yamamoto has quit IRC13:11
*** cdelatte has quit IRC13:13
*** ducttape_ has joined #openstack-meeting-413:13
*** klamath has joined #openstack-meeting-413:15
*** igordcard_ has quit IRC13:17
*** memogarcia has quit IRC13:17
*** mestery has joined #openstack-meeting-413:18
*** igordcard has joined #openstack-meeting-413:18
*** nihilifer has quit IRC13:28
*** prashantD has joined #openstack-meeting-413:28
*** nihilifer has joined #openstack-meeting-413:28
*** baoli has joined #openstack-meeting-413:30
*** baoli_ has joined #openstack-meeting-413:31
*** fawadkhaliq has quit IRC13:32
*** fawadkhaliq has joined #openstack-meeting-413:32
*** igordcard has quit IRC13:32
*** mestery has quit IRC13:34
*** ducttape_ has quit IRC13:34
*** baoli has quit IRC13:35
*** MarkAtwood has joined #openstack-meeting-413:35
*** limao has quit IRC13:36
*** MarkAtwood has quit IRC13:40
*** xingchao has joined #openstack-meeting-413:45
*** mestery has joined #openstack-meeting-413:48
*** subscope has quit IRC13:54
*** markvoelker has joined #openstack-meeting-413:54
*** prashantD has quit IRC13:54
*** woodard has joined #openstack-meeting-413:55
*** woodard has quit IRC13:55
*** woodard has joined #openstack-meeting-413:56
*** Sukhdev has quit IRC13:56
*** markvoelker has quit IRC13:58
*** xingchao has quit IRC14:00
*** gb21 has quit IRC14:02
*** sambetts_ has joined #openstack-meeting-414:02
*** banix has joined #openstack-meeting-414:02
*** xingchao has joined #openstack-meeting-414:03
*** zeih has quit IRC14:04
*** zeih_ has joined #openstack-meeting-414:04
*** pmesserli has joined #openstack-meeting-414:05
*** fawadkhaliq has quit IRC14:07
*** mestery has quit IRC14:08
*** baoli_ has quit IRC14:08
*** sambetts has quit IRC14:08
*** yamamoto has joined #openstack-meeting-414:11
*** ALUVial has joined #openstack-meeting-414:12
*** subscope has joined #openstack-meeting-414:13
*** dims has joined #openstack-meeting-414:15
*** mestery has joined #openstack-meeting-414:15
*** baoli_ has joined #openstack-meeting-414:15
*** markvoelker has joined #openstack-meeting-414:15
*** yamamoto has quit IRC14:17
*** Piet has quit IRC14:17
*** dims has quit IRC14:23
*** sdake has joined #openstack-meeting-414:24
*** Piet has joined #openstack-meeting-414:25
*** dims has joined #openstack-meeting-414:26
*** sambetts_ is now known as sambetts14:27
*** itisha has joined #openstack-meeting-414:29
*** sdake has quit IRC14:30
*** Swami has joined #openstack-meeting-414:33
*** ujuc has joined #openstack-meeting-414:36
*** woodard has quit IRC14:36
*** woodard has joined #openstack-meeting-414:37
*** woodard has quit IRC14:37
*** woodard has joined #openstack-meeting-414:38
*** ALUVial has quit IRC14:38
*** Piet has quit IRC14:40
*** bradjones|away is now known as bradjones14:40
*** david-ly_ has joined #openstack-meeting-414:41
*** david-lyle has quit IRC14:42
*** xingchao has quit IRC14:44
*** ALUVial has joined #openstack-meeting-414:45
*** bobh has joined #openstack-meeting-414:46
*** ducttape_ has joined #openstack-meeting-414:46
*** _ducttape_ has joined #openstack-meeting-414:48
*** ujuc has quit IRC14:50
*** ALUVial has quit IRC14:50
*** sdake has joined #openstack-meeting-414:50
*** ducttape_ has quit IRC14:50
*** ujuc has joined #openstack-meeting-414:51
*** rbak has joined #openstack-meeting-414:54
*** baohua has quit IRC14:55
*** cloudtrainme has joined #openstack-meeting-414:55
*** baohua has joined #openstack-meeting-414:56
*** ALUVial has joined #openstack-meeting-415:00
*** fawadkhaliq has joined #openstack-meeting-415:01
*** dims has quit IRC15:03
*** ALUVial has quit IRC15:06
*** yamamoto has joined #openstack-meeting-415:07
*** jwagner_away is now known as jwagner15:07
*** michael-hoppal_ has joined #openstack-meeting-415:09
*** michael-hoppal_ has left #openstack-meeting-415:09
*** ducttape_ has joined #openstack-meeting-415:09
*** _ducttape_ has quit IRC15:13
*** dzamboni has joined #openstack-meeting-415:15
*** ALUVial has joined #openstack-meeting-415:16
*** sdake has quit IRC15:16
*** baohua has quit IRC15:17
*** baohua has joined #openstack-meeting-415:17
*** ALUVial has left #openstack-meeting-415:18
*** MarkAtwood has joined #openstack-meeting-415:23
*** sigmavirus24_awa is now known as sigmavirus2415:27
*** MarkAtwood has quit IRC15:28
*** vinsh has quit IRC15:31
*** blahRus has joined #openstack-meeting-415:31
*** markvan has joined #openstack-meeting-415:32
*** HenryG has quit IRC15:34
*** salv-orlando has joined #openstack-meeting-415:38
*** HenryG has joined #openstack-meeting-415:38
*** memogarcia has joined #openstack-meeting-415:42
*** Sukhdev has joined #openstack-meeting-415:48
*** sdake has joined #openstack-meeting-415:50
*** yamamoto has quit IRC15:53
*** armax has joined #openstack-meeting-415:56
*** VanL has left #openstack-meeting-415:59
*** Piet has joined #openstack-meeting-416:01
*** bmace has joined #openstack-meeting-416:01
*** _ducttape_ has joined #openstack-meeting-416:02
*** hogepodge has joined #openstack-meeting-416:03
*** ducttape_ has quit IRC16:04
*** jasonsb_ has joined #openstack-meeting-416:05
*** baohua has quit IRC16:05
egluteDefcore meeting is in #openstack-defcore16:06
*** david-ly_ is now known as david-lyle16:07
*** rockyg has joined #openstack-meeting-416:08
*** cloudtrainme has quit IRC16:09
*** baoli_ has quit IRC16:10
*** rockyg has left #openstack-meeting-416:11
*** Swami_ has joined #openstack-meeting-416:11
*** delatte has joined #openstack-meeting-416:11
bloganeglute: ah16:11
egluteblogan join us there!16:12
*** britthou_ has joined #openstack-meeting-416:12
bloganeglute: just did :)16:12
eglute:)16:12
*** harshs has joined #openstack-meeting-416:12
*** belmoreira has quit IRC16:13
*** dzamboni_ has joined #openstack-meeting-416:14
*** subscope has quit IRC16:14
*** harshs has quit IRC16:14
*** subscope has joined #openstack-meeting-416:15
*** subscope has quit IRC16:16
*** cloudtrainme has joined #openstack-meeting-416:16
*** EmilienM has quit IRC16:17
*** dzamboni has quit IRC16:17
*** jasonsb_ has quit IRC16:17
*** Hunner has quit IRC16:17
*** ujuc has quit IRC16:17
*** Swami has quit IRC16:17
*** delattec has quit IRC16:17
*** britthouser has quit IRC16:17
*** Hunner has joined #openstack-meeting-416:17
*** subscope has joined #openstack-meeting-416:17
*** Hunner has quit IRC16:17
*** Hunner has joined #openstack-meeting-416:17
*** EmilienM_ has joined #openstack-meeting-416:17
*** dzamboni_ is now known as dzamboni16:17
*** britthou_ is now known as britthouser16:17
*** britthouser has quit IRC16:18
*** EmilienM_ is now known as EmilienM16:18
*** britthouser has joined #openstack-meeting-416:18
*** britthouser has quit IRC16:21
*** britthouser has joined #openstack-meeting-416:21
*** britthouser has quit IRC16:21
*** britthouser has joined #openstack-meeting-416:22
*** salv-orlando has quit IRC16:23
*** janiceonchn has quit IRC16:23
*** stvnoyes has joined #openstack-meeting-416:25
*** markvan_ has joined #openstack-meeting-416:26
*** markvan has quit IRC16:26
*** subscope has quit IRC16:27
*** zehicle has joined #openstack-meeting-416:28
*** igordcard has joined #openstack-meeting-416:28
*** subscope has joined #openstack-meeting-416:29
*** rhallisey has joined #openstack-meeting-416:30
*** subscope has quit IRC16:30
sdake#startmeeting kolla16:33
openstackMeeting started Wed Nov 11 16:33:12 2015 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:33
*** openstack changes topic to " (Meeting topic: kolla)"16:33
openstackThe meeting name has been set to 'kolla'16:33
*** jmccarthy has joined #openstack-meeting-416:33
sdake#topic rollcall16:33
rhalliseyhi16:33
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:33
jmccarthyhi16:33
stvnoyeshi16:33
sdakeyo \0/16:33
bmacehey16:33
*** subscope has joined #openstack-meeting-416:33
jpeelero/16:33
britthousero/16:33
pbourkehi16:33
pbourkeSamYaple: yo16:34
SamYaplepbourke: pong16:34
sdake#topoic objectives for m1/m2/m316:34
*** jasonsb has joined #openstack-meeting-416:34
sdake#topic objectives for m1/m2/m316:34
*** openstack changes topic to "objectives for m1/m2/m3 (Meeting topic: kolla)"16:34
sdakehey folks16:34
sdakeI'd like to discusss at a high level what our objectives for m1/m2/m3 are16:34
sdaketo facilitate the priorities of blueprints16:34
sdakeI was thinking backend the filling out of the big tent nto m2/m316:35
sdakeand fixing the gaps/problems in m116:35
pbourkehttps://etherpad.openstack.org/p/Kolla-Mitaka-Roadmap16:35
sdakeya thats a pretty weak roadmap imo ;)16:35
sdakewe only ahd 40 mins16:35
pbourkeyeah but its a start16:36
*** prashantD has joined #openstack-meeting-416:36
sdakethings like upgrade are missing16:36
sdakethings like light out recovery are missing16:37
britthouserSo under big tent - are all those containerized and just need ansible? or some have no containers at all?16:37
sdakedoes anyone care what order we go in?16:37
pbourkenope16:37
SamYaplebritthouser: some stuff has no containers16:37
sdakebritthouser some have containers but most need both16:37
britthouserOk. thx16:37
pbourkesdake: how do you want to drive it16:38
SamYaplefyi im working on an outage so ill be in and out16:38
sdakeok so nobody cares on ordering ? :)16:38
pbourkebrainstorm bp titles?16:38
SamYaplesorry16:38
SamYaplebut ping me and ill respond16:38
sdakei just want to know if we should lod all thegood work up front or spread it between miletstones16:39
sdakethe problem wiht loading it all up front is that we will b  bored for m2/m316:39
sdakeof course my definition of good work is stuff that is highly technical and challenging and not repeititve16:39
sdakethis may be different then pbourke 's definition::)16:39
SamYaplewe need logging right now16:40
SamYapleits needed for the gate to be effective16:40
SamYapleand it needs to be backported16:40
sdakei tought we had logging mnus a few sservices16:40
SamYapleno16:40
SamYaplenone of the logging works like it should16:40
SamYaplewe dont capture stack traces16:40
SamYaplethose still go to stderr16:40
SamYapleand we dont do any of the non-openstack services16:40
SamYaplewe need to get that done right and inc0 is out of commision for probably a few weeks16:41
SamYapleI have other gate things I am doing on the side form my real job16:41
sdakeprobably loner - job changes are very dirsuptive16:41
SamYaplesdake: not a job change16:41
SamYaplejust a location change16:41
SamYapledoesnt matter, either way its a big issue16:42
SamYaplei think it can be solved fairly quickly, but someone needs to won it16:42
SamYapleown*16:42
sdakeok well since my memory is not lik ea computes, lets get the stuff in eherpad16:42
sdakeplease folks open up that roadmap etherpad and lets brain storm all the stuff we need to taclke16:42
sdakeand i'll just put em all in m116:42
sdakeand we can roll em as necessary to m2/m316:42
*** memogarcia has quit IRC16:44
sdakefind them and destroy them116:44
britthouserso roadmap sounds alot like the 1.1 list16:45
*** ducttape_ has joined #openstack-meeting-416:45
britthouseris that b/c we'll do those in M1, before backport to liberty?16:45
*** _ducttape_ has quit IRC16:46
*** _ducttape_ has joined #openstack-meeting-416:47
SamYaplebritthouser: the 1.1 list is a subset of this16:47
SamYaplepretty major subset16:47
britthouserOk...I'll double check the 1.1 list and make sure they are in the etherpad too16:47
*** ducttap__ has joined #openstack-meeting-416:49
*** ducttape_ has quit IRC16:49
*** ducttape_ has joined #openstack-meeting-416:51
*** watanabe_isao has joined #openstack-meeting-416:51
sdakeok if thre is nothing else i'll continue16:51
*** _ducttape_ has quit IRC16:51
sdake#topic mitaka #1 review16:52
*** openstack changes topic to "mitaka #1 review (Meeting topic: kolla)"16:52
*** daneyon has joined #openstack-meeting-416:52
sdake#link https://launchpad.net/kolla/+milestone/mitaka-116:52
*** _ducttape_ has joined #openstack-meeting-416:53
sdakethings are looking pretty good, minus we rae not effectivel hditributing the work16:53
sdakewhen i file all those blueprints after this meeting from the brainstorm session16:53
sdakei would like folks to take on blueprints16:53
*** yamamoto has joined #openstack-meeting-416:53
*** ducttap__ has quit IRC16:54
rhalliseywill do16:54
sdakei'd ike to talk abou this blueprint Drop root privileges to the container's application PID/GID16:54
sdakethis is a test case of using work items to track work16:54
sdake(work items re things in the eblueprint tracker fyi)16:54
*** daneyon__ has quit IRC16:54
SamYapledespite the slowdown, Kolla is #12 for most reviews so far this cycle, so dont get too down people. we are still progressing16:54
sdakeif you haven't signed up for a peice of work - please ign up for some16:55
sdakeSamYaple ya the two weeks before and after summit area lawys really slow16:55
sdakepeople on burnout on eithr end - then recovery- then ready to crank ;)16:55
sdakeany blueprint others would like to discuss?16:56
*** alex_didenko has quit IRC16:56
*** ducttape_ has quit IRC16:56
jasonsblogging?16:56
SamYaplejasonsb: i hit on that earlier16:56
*** Sukhdev has quit IRC16:56
sdakethere is no logging blueprint but there ill be sshortly16:56
jasonsbif i get you a video soon can we target EFK stack?16:56
sdakethat sounds fantastic16:56
*** _ducttape_ has quit IRC16:56
sdakeare we sitll going to use ssyslog per node?16:56
*** ducttape_ has joined #openstack-meeting-416:57
jasonsbi was wondering that too16:57
SamYaplei think we need to16:57
sdakei would say yes16:57
jasonsbharm was saying fluentd works good too16:57
*** MarkAtwood has joined #openstack-meeting-416:57
SamYapleew are logging over the socket16:57
jasonsbbut i think syslog is better16:57
sdakeunless there was a compleeling reason not to16:57
SamYaplethen rsyslog would push to a central16:57
SamYaplei dont want the individual services lggging over the network16:57
jasonsbsame tooling could be used for things which don't syslog16:58
jasonsbi suppose that is one advantage16:58
jasonsb(for fluentd)16:58
*** watanabe_isao has quit IRC16:58
*** Watanabe has joined #openstack-meeting-416:58
*** bpokorny has joined #openstack-meeting-416:58
*** yamamoto has quit IRC16:58
jasonsbi think we are talking multiple logging bp's?16:58
jasonsbor roll into one?16:59
sdakewhy multiple16:59
*** Watanabe is now known as Watanabe_isao17:00
jasonsbto reduce risk of one thing slipping efecting the rest17:00
sdakewhat multiple17:00
sdakewrong question ;)17:00
*** aarefiev22 has joined #openstack-meeting-417:00
SamYaplewe need one to make the logging work for all and work right (maybe reopen the old one...)17:00
sdakejasonsb can you put em in our roadmap eetherpad17:00
jasonsbit looked like there was some long tail stuff for logging17:00
SamYapleand one for the multinode17:00
jasonsbie: getting all of the services to work just right17:00
jasonsbSamYaple: +117:01
sdakegot it17:01
sdakeill add those then17:01
sdakeI still plan to put most of the new big tent serices in l2/l317:01
sdakeso we can push those out to N if needed to make our implementation completely solid for N17:02
sdakefor M I mean17:02
sdakepush to M, solid for M17:02
sdakepsuh to N, solid for M17:02
sdakegroan17:02
sdakeand seriousy, we need to get ceilomete rdown17:03
sdakeits almost a compute kit serice17:03
sdakeplease coolsvap get cracking :)17:03
SamYaplesdake: coolsvap was working on that last I heard I believe17:03
SamYaplethe biggest problem there is HA mongodb17:03
sdakeyes i know17:03
SamYaplethat is not an easy thing and there is no glaera for mongodb17:03
sdakei'd be satisified with a single non-ha ceilometer17:05
sdakei realize tha is imprefet but atleaast it wold work some of the time17:05
SamYapleno i dont want to do that17:05
sdakevs none of the time17:05
SamYaplethen we have to provide a path for migration17:05
sdakethe power of the two words "tech preview"17:05
SamYapleas long as we say no migration path im cool with that17:06
sdake#topic open discussion17:06
*** openstack changes topic to "open discussion (Meeting topic: kolla)"17:06
sdakeok folks from thee blueprint list looks like we hae a sle wof blueprints to sort out17:07
sdakei'll get em filed, need people to sign up for them17:07
sdakeanyone have open discussion?17:07
bmacei think we wanted to bring up if folks feel strongly about having the kollacli REST service in the python-kollaclient repo during dev at least.17:07
sdakeit shoudl be there all the time - i dont understand the  Q17:08
britthouserI'm confused about a REST cli?17:08
bmacewe can obviously break it out into a separate repo at some point.  if there are no objections, for the sake of simplicity, it would be easier to refactor in a single repository17:08
britthouserstill coming up to speed here...sorry.17:08
pbourkeideally it would be separate but can be done later17:09
bmacei don't believe any of the other python-Xclient repos have REST server side code in them17:09
*** nikhil_k has joined #openstack-meeting-417:09
bmacethat is my point sdake17:09
pbourkeif you were going to combine it in an existing repo though the kolla one would nearly make more sense17:09
bmacebut since a lot of the code that will be in there is in the cli right now, it is far easier to refactor into a service in a single repo, and move it out wholesale later17:09
bmacei think sdake already did a bunch of work to make the python-kollaclient repo17:10
pbourkeassuming a rest api is needed at all I haven't seen reasons for it yet17:10
nihilifer+1 for pbouke, I'd also pick kolla repo for REST server if we don't want to make a separate repo for it for now17:10
bmaceand not all people using kolla want or need to care about a cli17:10
sdakei'm good with refactoring the rest api wherever is good fot he des17:10
pbourkebmace: everyone voted for it so they do care17:10
pbourkebmace: even if they dont know it ;)17:11
bmacesure, so how about we do the dev in python-kollaclient and we can move the REST service into base kolla if folks want once it is done?17:12
*** nikhil has quit IRC17:12
SamYaple-1 on the REST api.... point me at a reason why we need it please17:12
SamYaplei need convincing17:12
pbourkeid like that conversation to happen17:12
SamYapleits been brought up before17:12
bmaceso that people can add their own UI or whatever programmatic control over kolla deploys?17:13
nihiliferI guess for making a cli like in other bg tent project17:13
SamYapleok. so what deploys that?17:13
SamYaplewhere does that run?17:13
SamYapleits definetely outside of our project scope17:13
bmacewherever they want17:13
*** salv-orlando has joined #openstack-meeting-417:13
sdakei disagree about project scope17:13
sdakeit is a deployment tooll17:13
*** subscope has quit IRC17:13
sdaketherefore in scope17:13
*** Swami_ has quit IRC17:13
SamYapleno its a rest api17:14
SamYaplenot a deployment tool17:14
SamYaplethis is a UI in front of the deployment tool17:14
sdaketo sserver deploying tooling17:14
bmaceyou don't think our deployment is complicated enough that people might not want to mess with stuff by hand?17:14
sdakei'd already call rest a ui17:14
SamYapleyou wont convince me that its in our current scope at all. but do we expand the scope? maybe17:14
sdakealreadyhardly17:14
SamYaplebmace: no? its 4 lines to deploy openstack17:15
bmacelol17:15
bmacesure, if you never want to change anything17:15
SamYapleok so point me at the openstack UI configuration tool for nova17:15
SamYaplecinder17:15
SamYapleneutron17:15
*** inc0 has joined #openstack-meeting-417:15
SamYaplewhere is the rest api to change those configs?17:15
sdakefuel has it17:15
sdakefuel has a rest api for those iirc17:15
SamYaplefuel is not an openstack project17:15
inc0hey, meeting time moved?17:16
sdakeit sort of is, it just isn't a  governed project17:16
bmaceyou know what people complain about with openstack, complexity to deploy. so don't point that out as a reason not to have a ui... it needs to be easier17:16
sdakeinc0 yur late bro ;)17:16
rhalliseyinc0, day light savings dude17:16
inc0oO17:16
inc0I thought it's in 15 minutes17:16
rhalliseywelcome to america inc017:16
SamYaplebmace: we deploy openstack, what deploys the thing you are tlakign about?17:16
inc0duh, sorry guys17:16
SamYaplebmace: does it need a backend?17:16
britthouserThink of the API as allowing other programs to control Kolla instead of a user.17:16
SamYaplebmace: what configures the inventory where it runs?17:17
sdakethe backend is the filesystem17:17
bmaceif people want to use it, they just run it, like a service.  i expect there would be an rpm to install it on some system, just like we do in the oracle distro for the CLI right now17:17
sdakethe softqware is run by init scripts or systemd or the like17:17
SamYapleare we tlaking about some UI or a rest api?17:17
SamYaplethese are widly different things17:17
sdakerest api17:17
inc0what would rest api do in our case?17:18
inc0we don't have any running service17:18
sdakeif someone wants to make a ui on top  more power to them17:18
SamYaplehow does that make it easier to deploy?17:18
sdakebut i think that would be outside scope of kolla17:18
bmaceessentially what the cli does now, breaking it out into a REST service that both the cli can use, but anyone else doing any other sort of deploy automation can use17:18
SamYapleok lets have some moderation here17:18
SamYaplebmace: are you asking for a UI?17:18
inc0bmace, that would be api of ansible or whatever17:18
bmacea cli is a ui..17:18
pbourkewe already have a ui17:18
pbourkebmace: +117:18
SamYaplebmace: GUI17:18
inc0ncurses!17:18
* sdake gets some salt for the popcorn17:19
SamYapleUX is the new terms nowadays17:19
bmacei don't plan on writing a gui right now, but with a rest api in place, people could make one if they want, they could do anything, programatically17:19
SamYaplewhat does a rest interface get us right now that we dont have?17:19
inc0bmace, again, we don't have running service17:19
*** daneyon_ has joined #openstack-meeting-417:19
SamYaplehow does that make it easier to deploy openstack?17:19
sdakea rest ui is a comon pattern in software development because it gets rid of magic pushbutton17:19
inc0nor we plan to, maybe besides mesos17:19
sdakewe want to get rid of magic pushbutton in our softtware17:19
inc0but mesos has it's apis17:19
SamYaplesdake: we dont have a service!17:19
sdakeSamYaple hwat about ansible and deploying all the things?17:20
sdakethat is deifnately a service17:20
SamYaplethats not a service17:20
SamYaplelook up the definition of service17:20
inc0service is constantly running daemon17:20
bmacethat is why i don't feel it needs to be in the core kolla repo, leave it out in another repo as an optional bit people can use, or not, with base kolla17:20
SamYapleinc0: +117:20
bmacejust like the cli17:20
SamYaplebmace: im not saying im opposed to it, but i still havent heard what it adds for value17:20
SamYaplenot to meantion the chicken/egg situtation it gets us in17:21
sdakeit allows  people to write guis for kolla17:21
sdakethere I said what it offers17:21
sdakeenjoy :)17:21
bmaceit isn't that hard to start a service..17:21
SamYaplesdake: great thats outside of scope17:21
sdakegui is outside scope17:21
SamYaplebmace: kolla doesnt touch the host17:21
sdakeenabling not outside scope17:21
bmacean rpm can do it, an apt can do it17:21
SamYaplebmace: it only starts containers17:21
SamYaplepbourke: thgouts here?17:22
bmaceon the deploy host, there are install dependencies, docker, ansible, a number of bits..17:22
pbourkethis is quite a balanced argument :)17:22
pbourkei completely see both sides17:22
sdakepersoanlly id' ike to see a nice gui for koll atoo17:22
inc0well, I have issue with rest api17:22
*** daneyon has quit IRC17:22
SamYaplea GUI doesnt require a rest api17:22
inc0for us17:22
sdakesomething that has a nice lock and shows you how long is left ;)17:22
SamYapleinc0: i do as well for us17:22
pbourkeSamYaple: I was thinking that also17:22
SamYaplesdake: I am actully ok with a GUI.... but not a rest api17:22
sdakea gui requires a rest api to avoid magic pushbutton17:22
pbourkeSamYaple: the api standardises how they interact with kolla though17:23
SamYapleno ansible does that17:23
pbourkehmm17:23
sdakeotherwise the gui encodes business logic within it - no bueno17:23
SamYaplesdake: then that requires a service17:23
pbourkeSamYaple: ansible is very flexible though17:23
SamYapleand then chicken and egg17:23
rhalliseyhmm17:23
pbourkeSamYaple: too much so17:23
inc0I would hate to end up with running gevent/greenlet/django/whatever which will do nothing17:23
inc0besides running one command, which would be ansible-playbook17:24
SamYaplewhy dont we table this. we have many far more important things to do17:24
*** harshs has joined #openstack-meeting-417:24
SamYapleif someone wnats to hammer out a spec we can all review it17:24
sdakethe reason i tcant be tabled is the work is beginning now17:24
nihiliferwhat about just creating separate repo for REST API? you probably will not convince yourselves about whether it's good or not17:24
SamYapleno a rest api or gui has nothing that is holding us up17:24
nihiliferbut it looks like some peaople or companies17:24
inc0nihilifer, noone will stop that17:24
nihiliferjust want to write JS-based GUIS17:25
bmaceit would be in a separate repo, the python-kollaclient17:25
SamYaplenihilifer: not under kollas name? no one will stop. under kollas name we need a spec17:25
inc0fuel has cool gui, but also database, running service and other stuff17:25
sdakebmace id recommend keeping in same repo for now17:25
SamYapleinc0: correct17:25
inc0we don't have database, running service and I don't want to have it tbh, not now in any case17:25
SamYapleinc0: thats a huge thing17:25
*** zehicle has quit IRC17:26
pbourkeSamYaple: what do you have to say on sdake's pushbutton argument17:26
bmacei tend to agree with the others though sdake, that the REST api shouldn't be in base kolla.  it is an optional thing, just like the cli, to make using kolla easier.17:26
SamYaplepbourke: we are the deployers of openstack. we cant be consumed like openstack17:26
*** tpeoples has quit IRC17:26
pbourkeSamYaple: we could be though17:27
inc0in fact, we're quasi-openstack really17:27
SamYaplepbourke: if we want to be tripleo and deploy openstack to deploy openstack, then yes we could17:27
inc0or meta-openstack;)17:27
pbourkeha17:27
inc0metastack17:27
SamYapleim not joking17:27
bmacewe have seen enough confusion by people doing kolla deploys already that it definitely need something on top of it to make it easier.17:27
*** tpeoples has joined #openstack-meeting-417:27
pbourkebmace: right but that's an arg for the existing cli, not the rest api17:27
SamYaplebmace: you dont reduce confusion by adding complexity17:27
inc0bmace, we have cli and we should work on it's usability imho17:28
SamYapleright17:28
SamYaplewe _just_ agreed to work on this cli17:28
inc0write good helps, make it usable17:28
inc0make manpage;)17:28
SamYapleif its as simple as `kolla deploy` `kolla add host` then i dont see what else we need17:28
pbourkeothers could write GUIs in the same way the cli is written17:28
*** SimonChung has joined #openstack-meeting-417:28
rhalliseyya we just had a big doc change to address this17:28
inc0ncurses! (I'll repeat it every now and then;))17:28
*** aarefiev22 has quit IRC17:29
sdakexthe argument for a rest api is to encodee our bussiness logic behind a programmatic api pbourke17:29
sdakei do not like how the cli jamws the business logic and ci together17:29
sdakeits magic fucking pushbutton17:29
pbourketrue enough17:29
sdake'the death of every project ive been involed in that failed17:29
bmacebecause if anyone wants to do any sort of programatic control, using expect and parsing cli output sucks17:29
SamYapleour time is up guys17:30
SamYaplelets move back to #kolla17:30
sdake#endmeeting17:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:30
openstackMeeting ended Wed Nov 11 17:30:10 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-11-11-16.33.html17:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-11-11-16.33.txt17:30
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-11-11-16.33.log.html17:30
*** rhallisey has left #openstack-meeting-417:30
*** bmace has left #openstack-meeting-417:30
*** jasonsb has left #openstack-meeting-417:31
*** subscope has joined #openstack-meeting-417:33
*** cloudtrainme has quit IRC17:34
*** jwagner is now known as jwagner_lunch17:34
*** Swami has joined #openstack-meeting-417:35
*** subscope has quit IRC17:35
*** markvoelker has quit IRC17:35
*** sdake_ has joined #openstack-meeting-417:36
*** cloudtrainme has joined #openstack-meeting-417:36
*** harshs has quit IRC17:37
*** sdake has quit IRC17:38
*** cloudtrainme has quit IRC17:54
*** MarkAtwood has quit IRC18:01
*** baoli has joined #openstack-meeting-418:01
*** banix has quit IRC18:05
*** ducttape_ has quit IRC18:05
*** sdake_ is now known as sdake18:05
*** rlpple has joined #openstack-meeting-418:07
*** jmccarthy has left #openstack-meeting-418:09
*** s3wong has joined #openstack-meeting-418:10
*** baoli has quit IRC18:13
*** baoli has joined #openstack-meeting-418:14
*** rlpple has left #openstack-meeting-418:21
*** ducttape_ has joined #openstack-meeting-418:25
*** dshakhray has quit IRC18:25
*** baoli has quit IRC18:25
*** baoli has joined #openstack-meeting-418:26
*** inc0 has quit IRC18:28
*** IlyaG has joined #openstack-meeting-418:30
*** markvoelker has joined #openstack-meeting-418:31
*** igordcard has quit IRC18:33
*** MarkAtwood has joined #openstack-meeting-418:34
*** ducttape_ has left #openstack-meeting-418:35
*** baoli has quit IRC18:37
*** baoli has joined #openstack-meeting-418:38
*** woodard_ has joined #openstack-meeting-418:42
*** MarkAtwood has quit IRC18:44
*** MarkAtwood has joined #openstack-meeting-418:45
*** woodard has quit IRC18:45
*** fawadkhaliq has quit IRC18:45
*** dims has joined #openstack-meeting-418:48
*** baoli has quit IRC18:49
*** baoli has joined #openstack-meeting-418:50
*** Swami has quit IRC18:51
*** memogarcia has joined #openstack-meeting-418:56
*** Swami has joined #openstack-meeting-418:59
*** Piet has quit IRC19:01
*** baoli has quit IRC19:01
*** baoli has joined #openstack-meeting-419:01
*** banix has joined #openstack-meeting-419:06
*** rharwood has left #openstack-meeting-419:13
*** baoli has quit IRC19:13
*** baoli has joined #openstack-meeting-419:14
*** Sukhdev has joined #openstack-meeting-419:16
*** Sukhdev has quit IRC19:17
*** MarkAtwo_ has joined #openstack-meeting-419:19
*** MarkAtwood has quit IRC19:19
*** Swami has quit IRC19:21
*** jwagner_lunch is now known as jwagner19:21
*** salv-orlando has quit IRC19:22
*** MarkAtwo_ has quit IRC19:22
*** lexholden has joined #openstack-meeting-419:23
*** salv-orlando has joined #openstack-meeting-419:24
*** memogarcia has quit IRC19:24
*** IlyaG_ has joined #openstack-meeting-419:25
*** cloudtrainme has joined #openstack-meeting-419:25
*** baoli has quit IRC19:25
*** baoli has joined #openstack-meeting-419:26
*** IlyaG has quit IRC19:28
*** sdake_ has joined #openstack-meeting-419:29
*** IlyaG_ has quit IRC19:29
*** sdake has quit IRC19:30
*** MarkAtwood has joined #openstack-meeting-419:33
*** Piet has joined #openstack-meeting-419:33
*** sdake has joined #openstack-meeting-419:35
*** sdake_ has quit IRC19:35
*** baoli has quit IRC19:38
*** baoli has joined #openstack-meeting-419:38
*** baoli has quit IRC19:39
*** stanchan has joined #openstack-meeting-419:40
*** baoli has joined #openstack-meeting-419:41
*** Watanabe_isao has quit IRC19:41
*** baoli_ has joined #openstack-meeting-419:44
*** Sukhdev has joined #openstack-meeting-419:45
*** baoli has quit IRC19:47
*** ajmiller has joined #openstack-meeting-419:47
*** Swami has joined #openstack-meeting-419:49
*** angdraug has joined #openstack-meeting-419:49
*** salv-orlando has quit IRC19:52
*** salv-orlando has joined #openstack-meeting-419:53
*** baoli_ has quit IRC19:54
*** baoli has joined #openstack-meeting-419:54
*** salv-orlando has quit IRC19:58
Jokke_o/20:00
j^2hi!20:00
j^2tools right?20:00
Jokke_Log_WG20:01
j^2opps wrong room :P20:01
*** rockyg has joined #openstack-meeting-420:01
*** itisha has quit IRC20:01
Jokke_rockyg: o/20:01
rockygo/20:01
rockygI guess it's time20:01
rockyg#startmeeting log_wg20:02
openstackMeeting started Wed Nov 11 20:02:06 2015 UTC and is due to finish in 60 minutes.  The chair is rockyg. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: log_wg)"20:02
openstackThe meeting name has been set to 'log_wg'20:02
Jokke_I did not kick the meeting off yet as I didn't know if anyone else was coming :)20:02
*** markvan_ is now known as markvan20:02
rockygAgenda:  Review of Summit results; Action items from Summit; Discussion20:03
rockyghey, that's ok.  I'm slow.  Work killed my access to the outside net, so I have to use webchat :P20:03
Jokke_ouch, that's handy20:04
rockyg#topic Review of Summit20:04
*** openstack changes topic to "Review of Summit (Meeting topic: log_wg)"20:04
rockygWe managed to get a fair amount agreed upon.20:04
Jokke_well ...20:05
rockygDynamic reconfiguration of config options for logging and other changeable options was agreed upon and is already being worked20:06
Jokke_I think we agreed to swift focus20:06
Jokke_yes, oh nice20:06
rockygformat for propagating request-id into log messages was agreed upon mostly.  A spec is needed to move this forward20:07
rockygSwift focus?20:07
Jokke_error code discussion20:09
rockygAgreed to work on getting log message levels more consistent across/within projects before pushing error codes.  Need to socialize need for lots of bugs being filed20:10
Jokke_yes20:10
rockygJokke_: still not understanding.  Not enough coffee20:10
Jokke_that was my point, we have been pushing error codes for a year and we decided to swift our focus elsewhere20:12
rockygOh! shift! twice typo'ed20:13
rockygAnything else from Summit?20:13
Jokke_Oh .... I think I'm the one needing coffee20:13
*** memogarcia has joined #openstack-meeting-420:14
Jokke_I think those were the most important bits20:15
rockyg:D20:15
rockygOk.20:15
rockyg#topic Action items from summit20:15
*** openstack changes topic to "Action items from summit (Meeting topic: log_wg)"20:15
rockyg#action write oslo.log spec for request-id inclusion in log messages20:16
rockyg#action post bug requests to operators ML and user group ML20:17
Jokke_did I miss that discussion, mind to give me tl;dr of what was agreed?20:17
Jokke_the request-id one20:17
rockygYup. you missed it.20:17
rockygIt was good.  And hard.  It's amazing how dense developers can be.20:17
rockygSo, recap:20:17
*** stvnoyes has left #openstack-meeting-420:18
*** lexholden has quit IRC20:19
rockyg#info  RequestID would have three fields [original requestID] [current RequestID][next RequestID] or similar.20:19
rockyg#info original requestID is the id of the client call that starts the chain of events.  It is constant until the chain is completed or errors out20:20
*** woodard_ has quit IRC20:20
*** woodard has joined #openstack-meeting-420:21
rockyg#info Current RequestID is the id that is generated when the original request is has been handed off in the API transition20:21
*** woodard has quit IRC20:21
Jokke_so how do we provide that? are we going to finally agree that the service accepts request-id as part of the query?20:21
*** woodard has joined #openstack-meeting-420:22
rockyg#info Next RequestID is the requestID for the handoff to the next API interaction20:22
*** woodard_ has joined #openstack-meeting-420:23
*** memogarcia has quit IRC20:23
rockygSo, the APIs should generate the ID as the handoff occurs.  If need be, the list might endup [orig][last][current].  Not sure, but still a linke list20:23
rockygThe requestID spec implementation will make the local requestID generation happen.20:23
Jokke_that's not problem, that's there already20:24
Jokke_the original one interests me20:24
*** woodard_ has quit IRC20:24
rockygrequestID spec is also implementing the generation in the clients20:24
*** woodard has quit IRC20:24
*** woodard has joined #openstack-meeting-420:25
*** woodard has quit IRC20:25
Jokke_k20:25
rockygThe guys who wrote the spec were there.  They liked getting these into the log messages.  The hard part will be getting the log message generated at handoffs, but since the spec writers are the implementers, they can add the log message calls, too.20:26
*** woodard has joined #openstack-meeting-420:26
rockygI think we are going to suggest using the syslog keyed list field for this.20:27
Jokke_those logs are going to be horrible to read for humans20:27
Jokke_3 UUIDs on every line :(20:28
rockygNah.  Only three extra ids.  What we should do is get the requestID size limited to something reasonable.20:28
*** Sukhdev has quit IRC20:28
Jokke_that's my point. Req id is UUID (current implementation)20:29
rockygUh, requestID can be a sized UUID, so it could be UUID4 or UUID8 or UUID16 rather than 32.  But I think that's a separate spec.20:29
rockygOr maybe a mod to the requestID spec.20:30
rockygWhat we should do is make the size configurable, but consistent.  Set it once for the whole cloud.20:31
Jokke_that would be gr820:31
rockygWhich would mean that we'd need to make sure the uuid generator is part of an oslo lib.20:31
rockygAnd that all generation is done by the lib.20:32
rockygI think we are working through the spec issues :-)20:32
Jokke_and each service advices their clients which size req-id to generate20:32
rockygI bet the ops would love to have a configurable UUID size20:33
rockygSmall clouds wouldn't need as big of uuids as large clouds.  And, we could provide guidance on how to size in the admin docs20:33
Jokke_back in 320:34
rockygnp20:34
*** memogarcia has joined #openstack-meeting-420:35
rockygI took this chance to get some coffee ;-)20:36
*** Swami_ has joined #openstack-meeting-420:36
*** Swami has quit IRC20:37
Jokke_sorry bout that20:37
rockygnot a problem.  I got coffee20:38
Jokke_:)20:38
rockygok.  so, have we beaten this horse enough?20:38
*** salv-orlando has joined #openstack-meeting-420:39
Jokke_yeah, I thik it's ready for glue factory20:39
rockygI won't be able to get to start writing the spec until next week at the earliest.  I have lots of ML catch up to do and have to finish off some expense reports and summit summaries20:40
rockygGood one!20:40
rockyg#action socialize the need for bugs to get the log message levels consistent20:41
rockygwe could do this a number of ways.20:41
rockygI'm wondering if we should try for getting a good number of bugs together, then analyze those to make the guidelines better20:42
Jokke_that wouldn't hurt20:42
rockygI think the ops know better what they need/want than the devs do.20:43
rockygI wonder if we can get a bugs sprint with the ops, just taking an hour or two to file bugs on messages20:43
Jokke_I'd like to get started with having folks filing those their filter lists as bugs20:44
rockygYup.  and it might be easiest to schedule a time when a bunch of them could do it together.  Also might reduce duplication that way.20:46
*** woodard_ has joined #openstack-meeting-420:46
rockygMaybe we should consider a weekly sprint - focus on one project per week?  If we need more than that as a start, we could schedule a second session20:46
Jokke_that could be20:46
rockygI think I could get some Rackspace and som GoDaddy participation on this.  Maybe more.20:47
rockygI think we may have a strategy.20:48
Jokke_good!20:48
rockyg#topic open discussion20:49
*** openstack changes topic to "open discussion (Meeting topic: log_wg)"20:49
*** woodard has quit IRC20:49
rockygWhat I'd love to see also is a bug against every stackdump that happens when running.  Every one should be eliminated and replaced by an error log message20:50
rockygBut maybe we should save that for the error codes timeframe.  Then, each new log instance would get that code at the same time.20:51
*** MarkAtwood has quit IRC20:51
Jokke_that could be20:51
*** belmoreira has joined #openstack-meeting-420:53
rockygWell, let's see what we can make happen this cycle.  Changing log levels for messages should be low hanging fruit.  And with more projects actually scheduling bug triage time, this stuff could get done.20:53
Jokke_yeah, hopefully we get the ops activated20:54
rockygyup.20:55
Jokke_anything else?20:55
rockygSo, how about we call this early?20:55
Jokke_++20:55
rockyg#endmeeting20:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:55
openstackMeeting ended Wed Nov 11 20:55:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-11-11-20.02.html20:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-11-11-20.02.txt20:55
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-11-11-20.02.log.html20:55
rockygYay!20:55
rockygThanbks!20:56
Jokke_cheers20:56
Jokke_next week same place same time20:56
rockyg++20:57
*** sigmavirus24 is now known as sigmavirus24_awa21:03
*** dzamboni has quit IRC21:03
*** IlyaG has joined #openstack-meeting-421:03
*** MarkAtwood has joined #openstack-meeting-421:06
*** memogarcia has quit IRC21:06
*** Swami_ has quit IRC21:07
*** Swami has joined #openstack-meeting-421:07
*** yamamoto has joined #openstack-meeting-421:10
*** memogarcia has joined #openstack-meeting-421:17
*** yamamoto has quit IRC21:22
*** salv-orlando has quit IRC21:22
*** memogarcia has quit IRC21:24
*** salv-orlando has joined #openstack-meeting-421:25
*** dshakhray has joined #openstack-meeting-421:29
*** memogarcia has joined #openstack-meeting-421:34
*** belmoreira has quit IRC21:46
*** bobh has quit IRC21:47
*** _ody has quit IRC21:47
*** Swami has quit IRC21:48
*** bobh has joined #openstack-meeting-421:48
*** rockyg has quit IRC21:51
*** Sukhdev has joined #openstack-meeting-421:52
*** bobh has quit IRC21:53
*** marcusvrn_ has quit IRC21:55
*** krtaylor has quit IRC21:56
*** Swami has joined #openstack-meeting-421:57
*** s3wong has quit IRC21:57
*** subscope has joined #openstack-meeting-421:57
*** Sukhdev has quit IRC21:59
*** ajmiller_ has joined #openstack-meeting-422:00
*** Sukhdev has joined #openstack-meeting-422:01
*** woodard has joined #openstack-meeting-422:02
*** subscope has quit IRC22:02
*** memogarcia has quit IRC22:02
*** ajmiller has quit IRC22:03
*** memogarcia has joined #openstack-meeting-422:04
*** woodard_ has quit IRC22:05
*** woodard has quit IRC22:06
*** SimonChung1 has joined #openstack-meeting-422:07
*** sdake has quit IRC22:07
*** SimonChung1 has quit IRC22:08
*** SimonChung2 has joined #openstack-meeting-422:08
*** SimonChung has quit IRC22:08
*** memogarcia has quit IRC22:08
*** krtaylor has joined #openstack-meeting-422:09
*** yamamoto has joined #openstack-meeting-422:10
*** salv-orlando has quit IRC22:13
*** memogarcia has joined #openstack-meeting-422:14
*** stanchan_ has joined #openstack-meeting-422:18
*** stanchan has quit IRC22:19
*** bobh has joined #openstack-meeting-422:20
*** sdake has joined #openstack-meeting-422:21
*** memogarcia has quit IRC22:23
*** stanchan_ has quit IRC22:28
*** stancha32 has joined #openstack-meeting-422:29
*** stancha32 has quit IRC22:33
*** memogarcia has joined #openstack-meeting-422:35
*** Swami has quit IRC22:38
*** prashantD has quit IRC22:43
*** daneyon_ has quit IRC22:47
*** mestery has quit IRC22:47
*** prashantD has joined #openstack-meeting-422:48
*** njohnston is now known as nate_gone22:48
*** banix has quit IRC22:50
*** jwagner is now known as jwagner_away22:51
*** memogarcia has quit IRC22:53
*** ajmiller has joined #openstack-meeting-422:57
*** ajmiller_ has quit IRC22:57
*** Swami has joined #openstack-meeting-423:03
*** Piet has quit IRC23:06
*** baoli has quit IRC23:07
*** baoli has joined #openstack-meeting-423:08
*** SimonChung2 has quit IRC23:08
*** SimonChung has joined #openstack-meeting-423:08
*** amotoki has quit IRC23:10
*** memogarcia has joined #openstack-meeting-423:13
*** dshakhray has quit IRC23:15
*** ajmiller has quit IRC23:16
*** sdake has quit IRC23:19
*** sdake has joined #openstack-meeting-423:20
*** blahRus has quit IRC23:22
*** Piet has joined #openstack-meeting-423:25
*** klamath has quit IRC23:27
*** memogarcia has quit IRC23:27
*** memogarcia has joined #openstack-meeting-423:31
*** s3wong has joined #openstack-meeting-423:39
*** cloudtrainme has quit IRC23:39
*** sdake_ has joined #openstack-meeting-423:41
*** janiceonchn has joined #openstack-meeting-423:42
*** sdake has quit IRC23:43
*** memogarcia has quit IRC23:53
*** memogarcia has joined #openstack-meeting-423:55
*** rbak has quit IRC23:56
*** sdake_ has quit IRC23:56

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