Wednesday, 2015-04-29

*** britthouser has joined #openstack-meeting-400:02
*** xingchao has quit IRC00:04
*** wojdev has quit IRC00:07
*** britthouser has quit IRC00:14
*** salv-orlando has quit IRC00:16
*** armax has joined #openstack-meeting-400:29
*** eghobo has joined #openstack-meeting-400:30
*** bknudson has quit IRC00:31
*** david-lyle has quit IRC00:32
*** xingchao has joined #openstack-meeting-400:36
*** eghobo_ has joined #openstack-meeting-400:37
*** eghobo has quit IRC00:40
*** IlyaG has joined #openstack-meeting-401:00
*** emagana has joined #openstack-meeting-401:06
*** banix has joined #openstack-meeting-401:06
*** bharath has quit IRC01:09
*** banix has quit IRC01:09
*** emagana has quit IRC01:10
*** xingchao has quit IRC01:10
*** emagana has joined #openstack-meeting-401:11
*** salv-orlando has joined #openstack-meeting-401:17
*** david-lyle has joined #openstack-meeting-401:20
*** britthouser has joined #openstack-meeting-401:22
*** salv-orlando has quit IRC01:22
*** markvoelker has quit IRC01:36
*** s3wong has quit IRC01:46
*** banix has joined #openstack-meeting-401:47
*** yamahata has quit IRC01:48
*** fnaval has quit IRC01:48
*** dims_ is now known as dims01:52
*** mwang2_ has quit IRC01:52
*** bnemec has quit IRC01:56
*** bnemec has joined #openstack-meeting-401:59
*** fnaval has joined #openstack-meeting-402:00
*** dannywilson has joined #openstack-meeting-402:02
*** VW_ has joined #openstack-meeting-402:07
*** xingchao has joined #openstack-meeting-402:11
*** dannywilson has quit IRC02:16
*** dannywilson has joined #openstack-meeting-402:17
*** xingchao has quit IRC02:18
*** dannywilson has quit IRC02:21
*** Swami_ has quit IRC02:24
*** eghobo_ has quit IRC02:29
*** banix has quit IRC02:29
*** david-lyle has quit IRC02:30
*** david-lyle has joined #openstack-meeting-402:31
*** david-lyle has quit IRC02:36
*** emagana has quit IRC02:40
*** markvoelker has joined #openstack-meeting-402:41
*** banix has joined #openstack-meeting-402:42
*** VW_ has quit IRC02:53
*** VW_ has joined #openstack-meeting-402:54
*** salv-orlando has joined #openstack-meeting-403:14
*** xingchao has joined #openstack-meeting-403:18
*** daneyon_ has quit IRC03:20
*** daneyon has joined #openstack-meeting-403:22
*** salv-orlando has quit IRC03:25
*** xingchao has quit IRC03:26
*** yamahata has joined #openstack-meeting-403:27
*** banix has quit IRC03:28
*** IlyaG has quit IRC03:32
*** david-lyle has joined #openstack-meeting-403:32
*** Swami has joined #openstack-meeting-403:33
*** ivar-laz_ has joined #openstack-meeting-403:34
*** IlyaG has joined #openstack-meeting-403:34
*** ivar-lazzaro has quit IRC03:38
*** ivar-laz_ has quit IRC03:38
*** IlyaG has quit IRC03:41
*** IlyaG has joined #openstack-meeting-403:41
*** IlyaG has quit IRC03:44
*** sacharya has joined #openstack-meeting-403:50
*** egon has joined #openstack-meeting-403:52
*** Swami has quit IRC03:53
*** Swami has joined #openstack-meeting-403:56
*** fallenpegasus has joined #openstack-meeting-403:59
*** rm_work is now known as rm_work|away04:00
*** ivar-lazzaro has joined #openstack-meeting-404:01
*** eghobo has joined #openstack-meeting-404:01
*** sdake_ has joined #openstack-meeting-404:04
*** sdake has quit IRC04:08
*** armax has quit IRC04:09
*** sdake_ has quit IRC04:11
*** rm_work|away is now known as rm_work04:13
*** Swami_ has joined #openstack-meeting-404:15
*** Swami has quit IRC04:18
*** VW_ has quit IRC04:18
*** daneyon has quit IRC04:23
*** bobmel_ has joined #openstack-meeting-404:47
*** eghobo has quit IRC04:48
*** bobmel has quit IRC04:50
*** nkrinner has joined #openstack-meeting-404:57
*** sacharya has quit IRC04:58
*** fallenpegasus has quit IRC05:08
*** ajmiller__ has joined #openstack-meeting-405:09
*** ajmiller_ has quit IRC05:12
*** salv-orlando has joined #openstack-meeting-405:15
*** dannywilson has joined #openstack-meeting-405:22
*** salv-orlando has quit IRC05:26
*** dannywilson has quit IRC05:26
*** eghobo has joined #openstack-meeting-405:33
*** eghobo_ has joined #openstack-meeting-405:36
*** ajayaa has joined #openstack-meeting-405:38
*** eghobo has quit IRC05:39
*** wojdev has joined #openstack-meeting-405:50
*** wojdev has quit IRC05:50
*** igordcard_ has quit IRC06:06
*** numan has joined #openstack-meeting-406:06
*** coldiso_ has quit IRC06:11
*** Swami has joined #openstack-meeting-406:13
*** Swami_ has quit IRC06:14
*** igordcard_ has joined #openstack-meeting-406:14
*** eghobo has joined #openstack-meeting-406:19
*** pkoniszewski has joined #openstack-meeting-406:19
*** eghobo_ has quit IRC06:21
*** coldiso has joined #openstack-meeting-406:28
*** salv-orlando has joined #openstack-meeting-406:34
*** Swami has quit IRC06:38
*** salv-orlando has quit IRC06:42
*** eghobo_ has joined #openstack-meeting-406:42
*** eghobo has quit IRC06:46
*** evgenyf has joined #openstack-meeting-406:46
*** fallenpegasus has joined #openstack-meeting-406:47
*** eghobo has joined #openstack-meeting-406:49
*** eghobo_ has quit IRC06:51
*** kobis has joined #openstack-meeting-406:56
*** xingchao has joined #openstack-meeting-407:00
*** ajo has quit IRC07:01
*** xingchao has quit IRC07:06
*** eghobo has quit IRC07:46
*** ajo has joined #openstack-meeting-407:51
*** wojdev has joined #openstack-meeting-407:57
*** imcsk8|afk is now known as imcsk807:59
*** imcsk8 is now known as imcsk8|zZz08:06
*** salv-orlando has joined #openstack-meeting-408:08
*** dims has quit IRC08:10
*** fallenpegasus has quit IRC08:22
*** yamahata has quit IRC08:25
*** xingchao has joined #openstack-meeting-408:53
*** xingchao has quit IRC08:58
*** aswadr has joined #openstack-meeting-409:44
*** dims has joined #openstack-meeting-409:51
*** ajayaa has quit IRC09:57
*** wojdev has quit IRC10:09
*** ajayaa has joined #openstack-meeting-410:10
*** wznoinsk has quit IRC10:27
*** mmedvede has quit IRC10:45
*** wojdev has joined #openstack-meeting-410:50
*** mmedvede has joined #openstack-meeting-410:53
*** wznoinsk has joined #openstack-meeting-410:59
*** dims has quit IRC11:18
*** igordcard has joined #openstack-meeting-411:23
*** overlayer has joined #openstack-meeting-411:23
*** ajayaa has quit IRC11:30
*** overlayer has quit IRC11:34
*** igordcard has quit IRC11:34
*** igordcard has joined #openstack-meeting-411:37
*** igordcard has quit IRC11:40
*** ajayaa has joined #openstack-meeting-411:42
*** mmedvede has quit IRC11:46
*** igordcard has joined #openstack-meeting-411:54
*** mmedvede has joined #openstack-meeting-411:54
*** dims has joined #openstack-meeting-411:56
*** britthouser has quit IRC12:00
*** britthouser has joined #openstack-meeting-412:03
*** igordcard has quit IRC12:05
*** igordcard has joined #openstack-meeting-412:06
*** gchamoul has quit IRC12:12
*** gchamoul has joined #openstack-meeting-412:12
*** rfolco has joined #openstack-meeting-412:22
*** igordcard has quit IRC12:25
*** britthouser has quit IRC12:25
*** igordcard has joined #openstack-meeting-412:25
*** ivar-lazzaro has quit IRC12:25
*** ivar-lazzaro has joined #openstack-meeting-412:28
*** erikmwilson_ is now known as erikmwilson12:35
*** EmilienM is now known as EmilienM|afk12:41
*** ajayaa has quit IRC12:41
*** VW_ has joined #openstack-meeting-412:52
*** ibiris is now known as ibiris_away12:55
*** VW_ has quit IRC12:58
*** xingchao has joined #openstack-meeting-413:00
*** britthouser has joined #openstack-meeting-413:00
*** klamath has joined #openstack-meeting-413:04
*** klamath has quit IRC13:04
*** klamath has joined #openstack-meeting-413:05
*** bknudson has joined #openstack-meeting-413:06
*** ibiris_away is now known as ibiris13:09
*** xingchao has quit IRC13:09
*** jckasper has joined #openstack-meeting-413:13
*** qwazerty is now known as Qwazerty13:24
*** matrohon has joined #openstack-meeting-413:30
*** wojdev has quit IRC13:33
*** ajayaa has joined #openstack-meeting-413:34
*** EmilienM|afk is now known as EmilienM13:37
*** VW_ has joined #openstack-meeting-413:38
*** VW_ has quit IRC13:39
*** VW_ has joined #openstack-meeting-413:40
*** wojdev has joined #openstack-meeting-413:42
*** wojdev has quit IRC13:55
*** wojdev has joined #openstack-meeting-413:55
*** asselin has joined #openstack-meeting-413:56
*** fnaval has quit IRC14:05
-openstackstatus- NOTICE: gerrit has been restarted to clear a stuck events queue. any change events between 13:29-14:05 utc should be rechecked or have their approval votes reapplied to trigger jobs14:05
*** aventerav has joined #openstack-meeting-414:07
*** sigmavirus24_awa is now known as sigmavirus2414:09
*** pkoniszewski has quit IRC14:11
*** yamahata has joined #openstack-meeting-414:14
*** wojdev has quit IRC14:18
*** fnaval has joined #openstack-meeting-414:19
*** xingchao has joined #openstack-meeting-414:20
*** erikmwilson is now known as Guest8463614:20
*** erikmwilson_ has joined #openstack-meeting-414:21
*** wojdev has joined #openstack-meeting-414:22
*** nkrinner has quit IRC14:24
*** ajmiller__ has quit IRC14:25
*** asrangne has joined #openstack-meeting-414:26
*** aswadr has quit IRC14:28
*** xingchao has quit IRC14:39
*** wznoinsk has quit IRC14:39
*** dims has quit IRC14:42
*** dims has joined #openstack-meeting-414:42
*** wznoinsk has joined #openstack-meeting-414:43
*** banix has joined #openstack-meeting-414:47
*** marcusvrn has joined #openstack-meeting-414:49
*** marcusvrn_ has joined #openstack-meeting-414:50
*** ajayaa has quit IRC14:52
*** pkoniszewski has joined #openstack-meeting-414:53
*** kobis has quit IRC14:53
*** kobis has joined #openstack-meeting-414:54
*** emagana has joined #openstack-meeting-414:55
*** kobis has quit IRC14:57
*** kobis has joined #openstack-meeting-414:57
*** imcsk8|zZz is now known as imcsk814:57
*** kobis has quit IRC14:58
*** kobis has joined #openstack-meeting-414:58
*** patrickeast has joined #openstack-meeting-415:00
krtaylor#startmeeting third-party15:00
openstackMeeting started Wed Apr 29 15:00:33 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
asselino/15:00
patrickeasthi everyone15:00
krtaylorHi asselin15:00
*** nfedotov has joined #openstack-meeting-415:00
zz_jamorning15:01
krtaylorhi patrickeast15:01
krtaylorhi zz_ja15:01
marcusvrn_Hi15:01
krtaylorhi marcusvrn15:01
mmedvedehi15:01
*** rhe00_ has joined #openstack-meeting-415:01
rfolcoo/15:01
krtaylorhi mmedvede15:01
krtaylorhi rfolco15:01
rhe00_hi15:01
krtaylormarcusvrn, glad you found out about this meeting, its a good point that we should advertise it more15:02
krtaylorhi rhe00_15:02
krtaylorok, lets get started15:02
krtaylorhere's the agenda for today15:02
nfedotovhello all15:02
marcusvrn_Yeah \o/15:03
krtaylor#link https://wiki.openstack.org/wiki/Meetings/ThirdParty#4.2F29.2F15_1500_UTC15:03
krtaylorhi nfedotov15:03
krtaylorso a quick announcement15:03
krtaylormake note of the Gerrit 2.9 upgrade Saturday May 915:04
*** ajayaa has joined #openstack-meeting-415:05
krtaylor#topic Topics for discussion at Liberty summit15:05
*** openstack changes topic to "Topics for discussion at Liberty summit (Meeting topic: third-party)"15:05
krtaylorthe proposed cross-project session is getting good remarks, looks lik eit may actually happen15:06
krtaylorI would like for it to be more of a discussion, working session or fish bowl15:06
krtaylorhere is the topics etherpad link:15:07
krtaylor#link https://etherpad.openstack.org/p/liberty-third-party-ci-working-group15:07
krtaylorasselin, there is a proposed infra session for the downstream puppet work, correct?15:08
asselinkrtaylor, yes15:08
asselin#link https://etherpad.openstack.org/p/infra-liberty-summit-planning15:09
krtaylorasselin, ok, so we can have that discussion there then, and move documentation to a work items that will follow that work15:09
asselinyes15:09
krtaylorSo I think #4 is important, but may be able to handle in a QA open session15:10
krtaylorso, scanning the list, it looks like the highest priority items to me anyway, are #1 and #315:11
*** xingchao has joined #openstack-meeting-415:12
krtayloralthough #3 is already happening, so that may just be a spot to get operators to contribute15:12
asselin#9 is important to us. If not in 3rd party, we can see about including that in cinder.15:13
asselin10 is covered in -infra session15:13
patrickeastasrangne: +1 for #915:13
patrickeastasselin: *15:13
krtaylorasselin, I agree, but it does have a smaller audience15:13
*** lennyb has joined #openstack-meeting-415:14
asselinis that a cinder issues, or do other projects have a similar need?15:14
asselinfor #915:14
*** wznoinsk_ has joined #openstack-meeting-415:14
patrickeasti assume other vendors have variable configurations they want to test out, right?15:15
krtaylorIs it a common problem in cinder?15:15
krtaylortesting multiple configs per patch?15:15
patrickeastmost backends have multiple switches they can fiddle with for the storage device15:16
asselinthe alternative is to setup specific jobs for each configuration.15:16
patrickeastdifferent authentication, encryption, fabrics, etc15:16
*** banix has quit IRC15:16
asselinyes, there are different backend configurations & openstack configurations.15:16
asseline.g. is multipath installed & enabled in nova.conf?15:17
* ctlaugh_ got in a little late15:17
krtaylorI could see neutron potentially having similar15:18
*** wznoinsk__ has joined #openstack-meeting-415:18
asselinit increases the job permutations...and for some it seems they should be able to test within a single job...15:19
krtayloris there requirements for the testing to include the permutations?15:20
asselinfrom cinder no. for customers, yes15:20
krtayloryep, ok, so a "its the right thing to do" test15:21
krtaylorwe have a few of those requirements as well15:21
krtaylorok, so let's leave that on the short list for summit15:21
*** numan has quit IRC15:21
asselinI think a brainstroming session would be good15:22
*** jckasper has quit IRC15:22
*** carl_baldwin has joined #openstack-meeting-415:22
*** lennyb has quit IRC15:22
krtayloragreed, we need to get broad input for how to improve trust in CI systems15:22
krtaylorfor #7 nfedotov, want to comment15:23
*** jckasper has joined #openstack-meeting-415:23
*** wznoinsk has quit IRC15:23
krtaylorfor #7 these would be tests also outside the required ?15:23
*** wznoinsk__ has quit IRC15:24
*** wznoinsk_ is now known as wznoinsk15:24
*** banix has joined #openstack-meeting-415:24
nfedotovYes. There are tests that could not be merged to tempest15:24
asselinmy opinion is yes it should be allowed.15:25
asselinand should be encouraged, in fact15:25
krtaylornfedotov, what is being asked, how to handle? requirements to do so?15:25
nfedotovI think so too. It may be a non voiting job. Somebody who are interested in results may look at it.15:25
zz_janfedotov, acceptance probably depends on articulating the voting status clearly.15:26
zz_jaIt's hard to imagine objections to non-voting "informational" results15:26
krtaylorthis may be related to #5, where there are tests that *should* be run, but are not required, seems like that is a recurring subject here15:27
*** jckasper has quit IRC15:27
nfedotovYes it is related to #5.15:27
*** jckasper has joined #openstack-meeting-415:27
zz_jakrtaylor, "should" vs "must" ... any binary modifier is probably going to annoy someone.  tagging seems to be the panacea nowadays.15:28
krtaylorwe (powerkvm) are beginning to test outside required projects, we have been planning to post thost log results to our third party system wiki page15:28
zz_ja...I think of should vs must in terms of degree of completeness.  gate is min-required, other levels could be articulated.15:28
krtaylorso the issue is that some tests need to be run, but the projects don't necessarily want to see the results of these posted to each patch, too much noise15:29
krtaylorso, maybe a community place to store "extra" tests?15:29
krtaylorindexed by patch number?15:29
krtaylorok, that would be a good brainstorming subject, and also cross-project15:30
ctlaugh_#5 (at least what I was hoping to convey) is that there are test scenarios (like we are running with ARM) where we can't possibly trigger off of (and comment on) every project and every commit.  I'm looking for a place to report test results that are not tied to a specific patch.15:30
asselinkrtaylor, I prefer to keep it posted with the patch itself15:30
asselinkrtaylor, perhaps a gerrit UI update can help filter the noise15:30
krtaylorasselin, agreed, but the projects don't agree15:30
krtaylorhm, so a better CI comments toggle15:31
asselinkrtaylor, for example15:31
*** evgenyf has quit IRC15:32
krtaylorok, so do we agree that these can be grouped into a discussion topic?15:32
asselin+115:32
patrickeast+115:32
zz_ja+115:33
krtaylorok, so we have #1 and #5/7/915:33
marcusvrn+115:34
ctlaugh_+115:34
krtaylor#4 may be QA, #2 follows #10 to infra15:34
*** sdake has joined #openstack-meeting-415:34
krtaylorthat leaves #815:34
krtaylor#8 is a great work topic for liberty15:35
*** xingchao has quit IRC15:35
asselinperhaps that one should also be proposed in -infra15:35
patrickeastyea they would probably have good input for it15:36
krtaylor#8 lends itself to good best practices discussions for caching/optimizing too15:36
*** VW__ has joined #openstack-meeting-415:36
patrickeast^ that might be something lacking in our documentation15:36
zz_ja+1 infra15:36
krtaylorthat can stay on the active work list for liberty, but do we need to discuss at summit?15:36
asselinkrtaylor, if not formally, we can discuss informally15:37
zz_jaif we think it lands on infra, might be useful to take the temp of the room on it15:37
*** frobware_ has joined #openstack-meeting-415:37
krtaylor#link https://wiki.openstack.org/wiki/ThirdPartyCIWorkingGroup#Development_Priorities15:37
*** VW_ has quit IRC15:37
zz_ja...if there's a groundswell of support, harder for others to say it's not important to infra15:37
krtaylorjust in case some don't know we track CI working group interests  :)15:38
krtaylorzz_ja, we haven't had much "groundswell" on anything  :)15:38
zz_jamight be how the question is asked.15:39
zz_jaif we talk about how to profile *a CI test*, yawn.15:39
asselinI'm thinking more like how it's done in disk image builder15:39
zz_jaif we talk about how to profile any scenario, well every consumer of the main repo should have that problem.15:40
asselinit has built in profiling.15:40
krtaylorok, I'll summarize the topics at the top of that etherpad after this meeting and email for comments15:40
asselinzz_ja, this would be profiling all the parts of the ci job itself15:40
*** VW__ has quit IRC15:41
krtaylorany other comments about summit discussion priorities?15:41
zz_jadepends what "all the parts" means asselin15:41
asselinso the jobs have timestamps. Would be nice to have a tool that can consume that and give your profile of the entire ci job.15:42
zz_ja... profiling often can only see "so far" down into the stack.  depends on implementation what that means though.15:42
zz_jasure15:42
asselincovering all the bash scripts, devstack, tempest, cleanup, uploading, etc.15:42
zz_jaas well as its individual components; it's a classic drill down pattern15:42
krtaylorI think you are both in agreement that is should be discussed :)15:43
zz_jakrtaylor, you and emily will have to proxy of course, no travel for me15:43
*** sacharya has joined #openstack-meeting-415:44
krtaylorwe need to move along in the agenda (time check)15:44
* asselin steps away for a minute15:44
krtaylorwe can handle clarification of topic discussion points via email and etherpad once I get the summit list15:44
krtaylorok, onward then15:44
*** armax has joined #openstack-meeting-415:45
krtaylor#topic Repo for third party tools15:45
*** openstack changes topic to "Repo for third party tools (Meeting topic: third-party)"15:45
krtaylorso, the patch to create the repo got merged, hopefully thats not news to anyone15:46
krtaylorhere is our shiny new repo15:46
krtaylor#link https://github.com/stackforge/third-party-ci-tools15:46
krtaylorand I have pushed an initial patch to get basics out there15:47
*** sdake_ has joined #openstack-meeting-415:47
krtaylorbut we need approvers/cores to get patches merged15:47
krtaylorI have proposed asselin, patrickeast, mmedvede, sweston as cores15:47
krtaylorI have not heard back from sweston yet, but can remove him later if he does not want to take it on15:48
*** igordcard has quit IRC15:48
krtayloroh and me15:48
krtaylorI have not heard anything from the email sent15:49
krtaylorso I am assuming that there is overwhelming support for those proposed15:49
krtaylorcomments?15:49
patrickeastsounds good to me15:49
asselinfrom a diversity point of view, do we have anyone from neutron?15:50
patrickeasti assume we can always adjust as we go as needed15:50
*** daneyon has joined #openstack-meeting-415:50
zz_ja+115:50
krtaylorlets vote, I love using the meeting tools15:50
krtaylor#startvote initial cores as proposed be added to third-party-ci-repo15:51
openstackUnable to parse vote topic and options.15:51
krtaylorhm, interesting15:51
*** sdake has quit IRC15:51
marcusvrnhow can I use this tool to vote?15:51
asselin#help ?15:52
krtaylorhm, it should have given us instructions to use yes or no15:52
zz_jastop reading the pictures in krtaylor's mind ;-)15:52
krtaylor#startvote15:52
openstackUnable to parse vote topic and options.15:52
krtaylorok, whatever a simple +1 -1 will do15:52
zz_jakrtaylor, try your original without the hyphens15:52
mmedvede#startvote agree on initial cores for new repo?15:52
openstackOnly the meeting chair may start a vote.15:52
mmedvedehaha sorry15:52
zz_ja+115:53
mmedvede+115:53
*** rm_work is now known as rm_work|away15:53
krtaylor #startvote agree on initial cores for new repo15:53
asselin+115:53
patrickeast+115:53
krtaylor#startvote agree on initial cores for new repo15:53
zz_ja+115:53
openstackUnable to parse vote topic and options.15:53
marcusvrn#vote yes15:53
marcusvrn :P15:53
marcusvrn+115:53
ctlaugh_+!15:53
krtaylorlol, its broke real good15:53
*** asrangne has quit IRC15:53
krtayloranyway15:53
krtaylor+1 from me15:53
krtaylorany against?15:54
*** dannywilson has joined #openstack-meeting-415:54
*** dannywilson has quit IRC15:54
*** dannywilson has joined #openstack-meeting-415:55
krtaylorlast call for votes15:55
krtaylor#agreed asselin, patrickeast, mmedvede, sweston, krtaylor as initial cores for third party ci tools repo15:55
krtaylorok, 5 mins15:55
*** Sukhdev has joined #openstack-meeting-415:55
*** jckasper has quit IRC15:56
krtaylor#topic Monitoring dashboard status15:56
*** openstack changes topic to "Monitoring dashboard status (Meeting topic: third-party)"15:56
krtaylorI am assuming sweston didn't join us15:56
krtaylorok, then I will contact Timothy Chavez, he is not addressing the resolution of the comment on the patch15:56
krtaylorI believe that is all that is holding that up15:57
marcusvrnjust a question: patrickeast and asselin are from cinder, correct? what about  you, krtaylor and the other 2 folks?15:57
*** banix has quit IRC15:57
patrickeastyep i’m from cinder15:58
krtaylormarcusvrn, ctlaugh_ and I are cross project, but mainly focused on nova15:58
krtaylorsorry if I answered for you ctlaugh_15:58
krtaylorasselin, is it ok if we defer the downstream puppet status, since you gave an update at the office hours meeting on Monday?15:59
asselinkrtaylor, yes15:59
egonquestion for #3 in the etherpad: In terms of getting operators involved, is the suggestion that operators use their own infra, common infra, or just common tools?15:59
*** jckasper has joined #openstack-meeting-415:59
krtaylorok, good, 'cause we are out of time :)15:59
marcusvrnpatrickeast: krtaylor nice! thanks15:59
egonI'll comment in the etherpad...15:59
krtayloregon, yes please15:59
krtaylorthanks everyone, really good meeting as usual15:59
krtaylor#endmeeting16:00
*** openstack changes topic to "Gate is experiencing epic failures due to issues with mirrors, work is underway to mitigate and return to normal levels of sanity"16:00
openstackMeeting ended Wed Apr 29 16:00:38 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-04-29-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-04-29-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-04-29-15.00.log.html16:00
*** igordcard has joined #openstack-meeting-416:02
*** zz_ja is now known as zz_zz_ja16:03
*** wojdev has quit IRC16:04
*** VW_ has joined #openstack-meeting-416:04
*** igordcard has quit IRC16:05
*** sarob has joined #openstack-meeting-416:06
*** eghobo has joined #openstack-meeting-416:06
*** wojdev has joined #openstack-meeting-416:06
*** ryanpetrello_ has quit IRC16:08
*** ryanpetrello_ has joined #openstack-meeting-416:10
*** eghobo has quit IRC16:12
*** eghobo has joined #openstack-meeting-416:13
*** ryanpetrello_ has quit IRC16:14
*** wojdev has quit IRC16:16
*** Swami has joined #openstack-meeting-416:18
*** rhe00_ is now known as rhedlind16:20
*** wojdev has joined #openstack-meeting-416:21
*** banix has joined #openstack-meeting-416:23
*** nfedotov has left #openstack-meeting-416:24
*** wojdev has quit IRC16:29
*** ivar-lazzaro has quit IRC16:32
*** kobis has quit IRC16:34
*** eghobo__ has joined #openstack-meeting-416:35
*** eghobo has quit IRC16:36
*** VW__ has joined #openstack-meeting-416:38
*** VW__ has quit IRC16:38
*** VW__ has joined #openstack-meeting-416:39
*** VW_ has quit IRC16:40
*** armax has quit IRC16:46
*** asselin has quit IRC16:47
*** dmsimard has left #openstack-meeting-416:48
*** armax has joined #openstack-meeting-416:48
*** bobmel has joined #openstack-meeting-416:49
*** matrohon has quit IRC16:50
*** bobmel_ has quit IRC16:52
*** bharath has joined #openstack-meeting-416:52
*** mwang2 has joined #openstack-meeting-416:53
*** marcusvrn has quit IRC16:55
*** marcusvrn_ is now known as marcusvrn16:55
*** marcusvrn1 has joined #openstack-meeting-416:56
*** sdake_ has quit IRC16:59
*** sdake has joined #openstack-meeting-416:59
*** patrickeast has quit IRC17:00
*** pkoniszewski has quit IRC17:01
*** bharath has quit IRC17:01
*** sdake has quit IRC17:02
*** ivar-lazzaro has joined #openstack-meeting-417:03
*** sdake has joined #openstack-meeting-417:03
*** rockyg has joined #openstack-meeting-417:04
*** rockyg has quit IRC17:06
*** rockyg has joined #openstack-meeting-417:06
*** igordcard has joined #openstack-meeting-417:07
*** sdake has quit IRC17:07
*** jwagner is now known as jwagner_away17:07
*** rockyg has left #openstack-meeting-417:10
*** mwang2_ has joined #openstack-meeting-417:10
*** yamahata has quit IRC17:11
*** mwang2 has quit IRC17:11
*** igordcard has quit IRC17:12
*** s3wong has joined #openstack-meeting-417:12
*** eghobo__ has quit IRC17:13
*** igordcard has joined #openstack-meeting-417:13
*** igordcard has quit IRC17:13
*** igordcard has joined #openstack-meeting-417:14
*** ivar-lazzaro has quit IRC17:14
*** ivar-lazzaro has joined #openstack-meeting-417:15
*** ivar-lazzaro has quit IRC17:16
*** fallenpegasus has joined #openstack-meeting-417:16
*** ivar-lazzaro has joined #openstack-meeting-417:17
*** igordcard has quit IRC17:17
*** VW__ has quit IRC17:17
*** marcusvrn has quit IRC17:19
*** sbalukoff has quit IRC17:19
*** banix has quit IRC17:23
*** eghobo has joined #openstack-meeting-417:23
*** Apsu has quit IRC17:23
*** xingchao has joined #openstack-meeting-417:24
*** sdake has joined #openstack-meeting-417:24
*** banix has joined #openstack-meeting-417:27
*** xingchao has quit IRC17:29
*** yamahata has joined #openstack-meeting-417:32
*** emagana has quit IRC17:33
*** Apsu has joined #openstack-meeting-417:34
*** sbalukoff has joined #openstack-meeting-417:37
*** fallenpegasus has quit IRC17:43
*** fallenpegasus has joined #openstack-meeting-417:43
*** fallenpegasus has quit IRC17:48
*** banix has quit IRC17:51
*** wojdev has joined #openstack-meeting-417:52
*** Sukhdev has quit IRC17:55
*** SumitNaiksatam has joined #openstack-meeting-417:56
*** emagana has joined #openstack-meeting-418:01
*** marcusvrn has joined #openstack-meeting-418:01
*** bharath has joined #openstack-meeting-418:02
*** eghobo_ has joined #openstack-meeting-418:02
*** s3wong has quit IRC18:03
*** marcusvrn1 has quit IRC18:04
*** eghobo has quit IRC18:04
*** IlyaG has joined #openstack-meeting-418:04
*** s3wong has joined #openstack-meeting-418:05
*** davidlenwell has quit IRC18:05
*** dannywilson has quit IRC18:05
*** davidlenwell has joined #openstack-meeting-418:05
*** dhellmann has quit IRC18:05
*** banix has joined #openstack-meeting-418:05
*** bharath has quit IRC18:06
*** rm_work|away is now known as rm_work18:07
*** imcsk8 has quit IRC18:08
*** banix has quit IRC18:10
*** banix has joined #openstack-meeting-418:10
*** jwagner_away is now known as jwagner18:15
*** wojdev has quit IRC18:16
*** bharath has joined #openstack-meeting-418:17
*** xingchao has joined #openstack-meeting-418:26
*** VW_ has joined #openstack-meeting-418:27
*** markvoelker has quit IRC18:28
*** sdake has quit IRC18:29
*** britthou_ has joined #openstack-meeting-418:29
*** xingchao has quit IRC18:32
*** britthouser has quit IRC18:32
*** spredzy is now known as spredzy|afk18:32
*** emagana has quit IRC18:36
*** sdake has joined #openstack-meeting-418:37
*** bharath has quit IRC18:41
*** emagana has joined #openstack-meeting-418:43
*** britthouser has joined #openstack-meeting-418:44
*** bharath has joined #openstack-meeting-418:44
*** britthou_ has quit IRC18:48
*** matrohon has joined #openstack-meeting-418:48
*** emagana has quit IRC19:01
*** ivar-laz_ has joined #openstack-meeting-419:02
*** ivar-laz_ has quit IRC19:02
*** ivar-laz_ has joined #openstack-meeting-419:03
*** emagana has joined #openstack-meeting-419:04
*** ivar-lazzaro has quit IRC19:04
*** dhellmann has joined #openstack-meeting-419:06
*** VW_ has quit IRC19:10
*** wojdev has joined #openstack-meeting-419:10
*** marcusvrn has quit IRC19:15
*** banix has quit IRC19:15
*** ivar-laz_ has quit IRC19:16
*** ivar-lazzaro has joined #openstack-meeting-419:17
*** salv-orl_ has joined #openstack-meeting-419:18
*** marcusvrn has joined #openstack-meeting-419:18
*** eghobo_ has quit IRC19:19
*** wojdev has quit IRC19:21
*** bharath has quit IRC19:21
*** salv-orlando has quit IRC19:22
*** ajayaa has quit IRC19:23
*** bharath has joined #openstack-meeting-419:24
*** VW_ has joined #openstack-meeting-419:28
*** wojdev has joined #openstack-meeting-419:28
*** nkrinner has joined #openstack-meeting-419:29
*** banix has joined #openstack-meeting-419:30
*** wojdev has quit IRC19:39
*** eghobo has joined #openstack-meeting-419:40
*** david-lyle has quit IRC19:44
*** sarob has quit IRC19:44
*** david-lyle has joined #openstack-meeting-419:44
*** sarob has joined #openstack-meeting-419:45
*** bharath_ has joined #openstack-meeting-419:46
*** bharath has quit IRC19:47
*** ajayaa has joined #openstack-meeting-419:48
*** bharath has joined #openstack-meeting-419:50
*** dannywilson has joined #openstack-meeting-419:51
*** bharath_ has quit IRC19:52
*** dannywilson has quit IRC19:52
*** dannywilson has joined #openstack-meeting-419:52
*** ivar-lazzaro has quit IRC19:54
*** ivar-lazzaro has joined #openstack-meeting-419:54
*** wojdev has joined #openstack-meeting-419:55
*** ajmiller has joined #openstack-meeting-419:58
*** ajmiller_ has joined #openstack-meeting-419:59
nkrinnerhm20:05
nkrinnerno log working group meeting today i guess20:05
*** sacharya has quit IRC20:07
*** Rockyg has joined #openstack-meeting-420:08
Rockygsorry I'm late.  anyone here?20:09
Rockygfor log_wg?20:09
nkrinnerRockyg: hi20:09
Rockygmy browser crashed and I neded it to log in through the proxy20:09
RockygHey!20:09
Rockyg#startmeeting log_wg20:09
openstackMeeting started Wed Apr 29 20:09:53 2015 UTC and is due to finish in 60 minutes.  The chair is Rockyg. Information about MeetBot at http://wiki.debian.org/MeetBot.20:09
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:09
*** openstack changes topic to " (Meeting topic: log_wg)"20:09
openstackThe meeting name has been set to 'log_wg'20:09
nkrinnerRockyg: but i think it is only the two of us20:10
*** ivar-lazzaro has quit IRC20:10
RockygOk.  Well, it would be great if I could bounce some ideas off of you.20:10
RockygI forget what project you're associated with?20:11
*** ivar-lazzaro has joined #openstack-meeting-420:11
*** emagana has quit IRC20:11
bknudsonI'm around.20:11
nkrinneri also gathered some information on the docimpact/logimpact topic we discussed last meeting20:11
bknudsonyou should send out a ping message when the meeting is started20:11
bknudsonto whomever wants to be notified20:11
RockygAh.20:11
Rockygjokke_:20:11
nkrinneri'm not really associated with any project, but recently i comitted to sahara. but i am more interested in contributing to the oslo project20:12
RockygExcellent.  nkrinner  You are just the person we need ;-)20:12
nkrinner:-)20:12
RockygI can't remember Nikolas/ handle, but I don't think he's on.  Same with Eugeniya20:13
Rockygtopic:  what logging *really* needs20:13
*** emagana has joined #openstack-meeting-420:14
Rockyg#topic what logging *really* needs20:14
*** openstack changes topic to "what logging *really* needs (Meeting topic: log_wg)"20:14
RockygI've been working *a lot* on the spec, but it's been in responding to comments and changing the spec based on the responses.  I'm about 2/3 of the way there20:14
RockygSo, I haven't resubmitted it yet.20:15
bknudsonwhich spec?20:15
RockygTwo things the spec brings out:  1) we need someone to implement the oslo.log changes 2) we need projects to use new oslo.log error code stuff for new work, plus a while you're in there retrofit20:16
Rockygbknudson: lemme find it20:16
bknudsonthere is a summit session proposed for oslo.log20:16
bknudsonsee at the bottom here: https://etherpad.openstack.org/p/liberty-oslo-summit-planning20:17
bknudsonthe working title is "Life, Liberty, and the pursuit of oslo.log changes"20:17
*** galstrom_zzz is now known as galstrom20:17
dhellmanno/20:17
Rockygbknudson: got a line number?20:18
bknudson#line 26820:18
Rockyg#llink https://review.openstack.org/#/c/172552/5/specs/log_message_error-codes.rst,unified20:19
Rockygis the spec with comments.20:19
Rockygcool.  40minutes on oslo.log20:20
bknudsonlots of comments means people are interested20:20
Rockygthat's Thursday?20:20
Rockyghey, dhellmann20:20
bknudsonthis is the proposed schedule -- 5/20 is wed.20:21
dhellmannhi, Rockyg20:21
RockygI found a git repository with rfc5425 full compliance log message formatter in python20:21
RockygOK.  Wednesday.20:21
bknudsonwhat's the license20:21
Rockygmorgan fainberg's apache20:22
bknudsonhttps://tools.ietf.org/html/rfc5425 ?20:22
Rockygsorry 542420:22
dhellmannas a working session, that room is going to be pretty small and the discussion is expected to be very very focused20:22
bknudsoncome to the session expecting to work.20:23
*** marcusvrn has quit IRC20:23
Rockyg#link https://github.com/dpocock/python-rfc5424-logging-formatter20:23
dhellmannRockyg: that's GPL20:23
RockygI've been doing a bunch of digging and reading, etc. to respond to the error code comments.  dhellmann: dang!20:23
bknudsondid morganfainberg write it?20:24
bknudsonwe could probably twist his arm to dual license20:24
bknudsonalthough he'd have to talk to his old employer too.20:24
Rockygsomehow, his name is on the license, but it's a fork of another repository, which, who knows, might be a fork of his.20:24
dhellmannbknudson: looks like metacloud is involved, so we'd have to get them (or EMC, I think) to change it20:24
dhellmannanyway, this is putting the cart before the horse because it's not certain it would be suitable for the changes needed20:25
bknudsonI thought oslo already had syslog formatter20:25
RockygI'm thinking we can get the author to license under apache since it appears he just copied.  Might need to trace proveninance, though20:25
dhellmannbknudson: we do20:25
dhellmannRockyg: let's focus on getting that spec approved before we worry about implementation20:25
Rockygbknudson:  but it's not 100%.  It's missing parts of the header20:25
dhellmannwe might not even need this20:25
Rockygagreed.20:25
bknudsonoops20:26
*** banix has quit IRC20:26
RockygSo, anyway, what I realized is that I would like the xproject time to define what gets written to which logs and when you write to any log.20:27
Rockygwe have oslo logs, console logs, apache logs20:27
*** galstrom is now known as galstrom_zzz20:27
RockygThe api might need to write one thing to the oslo log, and pass log context to the project it is responding to.20:27
RockygIf we come up with a system flow and guideline for logs and logging, it will be much clearer where we need to fill gaps, change, or maybe even drop.20:28
bknudsonThere's another log guideline that was already merged --20:28
bknudson#link https://review.openstack.org/#/c/132552/20:28
jokke_hi ... sorry got caught in middle of something20:28
bknudsonso this is a guildeline for logs and logging.20:29
RockygYup.  That is the basic "developers do this for logging so we have a chance of debugging this stuff" one20:29
bknudsonwell, for logging... it didn't mention whether to use syslog or apache or whatever.20:29
dhellmannyes, I think it makes sense to address these issues separately. Specs need to be small enough to understand and actually act on, either to implement them or to use the policies to help make a decision about something.20:29
dhellmannbknudson: developers do not make that decision. *all* logging goes through the same API, and it can be configured by the deployer to end up wherever they want20:30
Rockygdhellmann: right.  so we need to get the logging "framework" documented/defined for OpenStack as an ecosystem.20:30
bknudsony, developers need to know to not make an assumption20:30
bknudsonjust because devstack gate does it that way20:30
dhellmannRockyg: let's start by defining the desired outcome, and work backwards to an API of some sort.20:31
Rockyggreat20:31
dhellmannI think a lot of what you want is actually already possible, and some of what you want is going to meet quite a bit of resistance (error codes)20:32
RockygYes.20:32
*** ivar-lazzaro has quit IRC20:32
RockygI think error codes would go easier if we have an outline of how logging should work20:32
*** ivar-lazzaro has joined #openstack-meeting-420:32
RockygI kinda started from the middle, went down and am circling back to the top.20:33
dhellmannyeah, it seems like there are several different issues, and we don't have to address them all in one spec20:33
*** ajmiller_ has quit IRC20:33
*** ajmiller has quit IRC20:34
RockygYes.  And if we get the principles down, the notification log stuff will be easier and smoother, too.20:34
RockygI had started a google spreadsheet that I wanted to put the logs in and define certain characteristics20:34
Rockyg#link https://docs.google.com/spreadsheets/d/1XTncfK_droY8E-Uy2icVuU-z9ya38ZBK_ZIRvGfPOXc/edit#gid=020:35
dhellmannwe're not going to completely replace everything that is happening with logging, so we should be thinking in terms of small, incremental changes20:35
*** banix has joined #openstack-meeting-420:36
RockygI thought if we could start with all the logs we have and categorize them, we would get patterns and classes20:36
RockygI expect that console logs are not something we would want to address20:36
RockygExcept as a general "if it goes to the console, make the message meaningful"  kind of thing.20:36
dhellmannconsole logs?20:37
jokke_no, lets not touch anything in vm space unless they run nested openstack :)20:37
Rockygscreen_20:37
jokke_ah .... stdout and errout?20:37
Rockygjokke_: exactly.  Let's stay in the control plane, and out of the "data" plane20:37
dhellmannso that's an example of what I was saying before -- the existing log configuration code is set up to use the console for devstack, the exact same code configures logging files as well20:38
RockygSo nova servers, compute nodes, neutron servers, keystone...20:38
Rockygdhellmann:  Oooh.20:38
bknudsonit's regular python logging20:39
dhellmannall of this configuration stuff is built into the library already20:39
dhellmannright, it's sitting on top of python's logging module20:40
Rockyghmmm.  how do you determine which logfile to write to?  I can understand by "project" but ....20:40
bknudsonthe default config writes to stdout20:40
bknudsonif you want to override the default config to write to separate log files you can do that20:41
dhellmannthere are configuration options to control all of that stuff, and if the simple configuration options aren't enough a deployer can use python's configuration file format to do almost anything you can imagine20:41
Rockygdhellmann: are you by anychance going to have a log library tutorial?20:41
dhellmannno, we don't have a session like that planned20:41
bknudsonhere's a tutorial: https://docs.python.org/2/howto/logging.html#logging-basic-tutorial20:41
RockygOK.  I know about the config file format stuff.  The operators use that to separate debug from everything else20:41
bknudsonfrom the python docs20:41
Rockygdhellmann: will that get me enough info to get deeper into oslo?20:42
dhellmannthe python.org docs?20:42
RockygYeah20:42
bknudsonRockyg: you will want to understand that20:43
bknudsonHere's info on the config file: https://docs.python.org/2/howto/logging.html#configuring-logging20:43
dhellmannunderstanding what the underlying code is capable of will help understand what oslo.log is doing20:43
bknudsonthe oslo stuff is a small layer on top of python logging20:43
bknudsonfor consistency, since it's easy to do everything differently20:43
RockygI think I started it, but ah, that's what I need.  I'll review them both.  I'm also going to watch sdague's debug youtube talk again20:43
dhellmannright, oslo.log mostly maps oslo.config options to behaviors in the standard logging library20:44
RockygYeah.  Theoslo.log  docs are good for figuring out what to put in your log message and how to build it from the dev perspective.20:44
Rockygso, putting the pieces together will give me the flow.  Which I have been trying to get and have not had much success.20:45
bknudsonI didn't know about the yaml config file... we should switch the sample.20:46
bknudsonhttp://git.openstack.org/cgit/openstack/keystone/tree/etc/logging.conf.sample20:46
RockygI grabbed the file from openstack-infra/sys-config/modules20:46
dhellmannbknudson: I think something has to read the yaml and convert it to dictionaries, so we would have to add code for that somewhere20:47
Rockyghttp://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/openstack_project/files/logstash20:47
bknudsondhellmann: oh, it's not built-in, just easy to convert to the dict.20:47
dhellmannbknudson: I *think* so? there's no yaml parser in the stdlib20:47
bknudsonRockyg: logstash is a great example of why we need consistent format20:48
RockygYup.20:48
*** matrohon has quit IRC20:48
bknudsonpeople will get very angry at us if we make it difficult to debug gate issues.20:48
RockygThere is also a .erb file that infra uses to reconfigure the various message formats.20:49
RockygSo they can actually use logstash20:49
bknudsonnot just openstack infra uses logstash, I'm sure there's deployments out there enjoying it too20:49
RockygI've been collecting up all this data and trying to understand it to make it information.  I'm close.20:50
Rockygbknudson: yeah.  the operators grab that file, too.20:50
Rockygthe .erb file20:50
dhellmannRockyg: it would be useful to see your notes, are they in an etherpad somewhere?20:50
RockygI've got them in a few etherpads.  let me consolidate them.  I started, but then tried to get the spec out.20:51
*** ajo has quit IRC20:51
dhellmannok, maybe just between now and the summit20:51
Rockygthen the spec took longer because I kept searching for all the other stuff.20:51
Rockygdhellmann: definitely.20:51
*** praveens has joined #openstack-meeting-420:52
Rockygdhellmann:  I'm about half way through addressing the comments in the spec.  I can work on that this week or the consolidation.  I can have one or the other out by early to mid next week20:52
RockygWhich would be better20:52
dhellmannthe spec, I think20:52
bknudsonget a new rev of the spec out so you can get more comments20:52
RockygOK.  I'll make that happen then focus on getting the data down.20:53
dhellmann++20:53
RockygBut, I want that info so others can look at that, too, before the summit.20:54
RockygMaybe all the different config and other files, tools and a flow and where they get used.20:54
*** jwagner is now known as jwagner_away20:55
*** belmoreira has joined #openstack-meeting-420:55
RockygI think if we have a reasonable understanding/flow/description of how/what things get logged now, it would be a good starting point in summit discussions of figuring out where we want to really go.20:55
bknudsonI'd find it interesting to know how it all works with elasticsearch, logstash, kibana.20:56
dhellmannI thought the focus right now was the format of the messages?20:56
Rockygdhellmann: I think the format is a middle layer, but a really important one we can work on now20:57
bknudsonand whether some things have become irrelevant (syslog)20:57
*** dannywilson has quit IRC20:57
RockygWhich is also why the spec is important.  another round of comments from the dev community and then get the ops guys on it.20:58
*** dannywilson has joined #openstack-meeting-420:58
bknudsonhearing from ops how they want/need it done would be really great20:58
Rockygbknudson: I think the ops are driving the syslog stuff.  It's a more stringent standard, so easier for them to parse20:58
bknudsonsyslog doesn't seem that stringent to me.20:59
bknudsonI've dealt with worse20:59
Rockygbknudson: I've got a bunch of stuff from the Paris summit in etherpads that the ops folks provided, comment on.20:59
*** fallenpegasus has joined #openstack-meeting-421:00
Rockygbknudson: read the rfc and see what python.log is not enforcing.  One thing the operators want is "-" where a message field is left blank21:00
Rockygpython.log lets you just skip that field21:00
bknudsonah, that's where the formatter comes in.21:00
RockygYup.21:00
*** VW_ has quit IRC21:01
RockygIt really isn't that stringent, but is more tightly constricted for format21:01
jokke_bknudson: it would also allow using the syslog header etc. fields more effectively providing the info out of those regardless the backend of the logging21:01
bknudsondefaulting to stringent syslog or having a syslog config option makes sense to me.21:02
RockygOops.  We're out of time.  do we want to continue on?  there's nobody after us.21:02
dhellmannit's the EOD for me here, but you can continue on without me21:02
Rockygeod for dhellmann.  Think of poor jokke_ ;-)21:03
RockygThanks, dhellmann.  I really needed your input today.21:03
RockygIt will take me lots farther.21:03
dhellmannnp, Rockyg :-)21:04
Rockygso, I think this is winding down.  Let's get nkrinner's input on his research than call it a meeting21:04
nkrinnerok21:05
Rockyg#topic tags in launchpad21:05
*** openstack changes topic to "tags in launchpad (Meeting topic: log_wg)"21:05
nkrinnerso last week we discussed if we want something similar like the 'docimpact' tag for commit messages21:05
*** banix has quit IRC21:06
nkrinnerwhat is basically happening there is when a commit message contains a 'docinmpact', a bug is automatically filed against a project, here openstack-manual21:06
nkrinnerit is documented here: https://wiki.openstack.org/wiki/Documentation/DocImpact21:07
bknudsonthere's also a SecurityImpact tag, which I think just sends email rather than filing a bug21:07
nkrinnerimplementation happens mostly here: http://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jeepyb/cmd/notify_impact.py#n16121:07
nkrinnerbknudson: that too, but i did not really look into that yet21:08
nkrinnerso, i think it would be something easy to implement. the hardest thing would be to get a spec approved to do so.21:09
jokke_if anything I think the securityImpact model with automated mail to list is more what we would want21:09
bknudsonthe bug is filed for docimpact because there's more work to do -- write the docs21:09
bknudsonthe email is sent because they're asking for the ossg to look at the change21:09
nkrinneri also wondered where to file the bug against if we go with the docimpact way21:09
nkrinnerso people prefer the securityimpact model?21:10
RockygYeah, we don't have a horizontal project for logs.  At least not yet.21:10
jokke_We do not have a project and we do not have actual work to do if someone is changing their logging21:11
bknudsonwhat kind of changes do you want to see a LogImpact tag on?21:11
RockygWell, translation would21:11
jokke_it's definitely more in lines "We're doing damatical changes about what we spit out, please have a look"21:11
nkrinnerbugs where logging does not give meaningful information21:11
nkrinnera way to tell "we need more/better logs here"21:12
bknudsonoh, it's for bugs, too, and not just commits?21:12
jokke_Rockyg: the translation gets their strings through the i18n tooling anyways21:12
bknudsonThe OSSG mailing list also gets email for security bugs.21:12
nkrinneri prefer that, i think the main focus should be on bugs21:12
Rockygmaybe operators would want mails on log bugs?21:13
*** ajayaa has quit IRC21:13
Rockygat least on any marked critical21:13
bknudsonhttp://lists.openstack.org/pipermail/openstack-security/2015-April/subject.html21:13
bknudsonthat's what the openstack-security list looks like21:14
jokke_nkrinner: so did you find how to trigger those notifications out of bugs filed? Do we have tooling that FE looks for specific bug tags?21:14
*** Sukhdev has joined #openstack-meeting-421:14
nkrinnerjokke_: i did not look at that yet, i was looking at docimpact21:14
Rockyganyone can add a tag to a bug within a project, but is there a way to get the tag to pre-exist on all projects?21:15
nkrinnerwhen i proposed to investigate docimpact, i was not really aware what it does at that point21:15
jokke_https://wiki.openstack.org/wiki/Bug_Tags21:15
nkrinnerbug tags: https://wiki.openstack.org/wiki/Bug_Tags21:15
jokke_;)21:15
Rockygnkrinner: from the other side, if you file a bug with docimpact, how does it get identified to the docs team?21:16
nkrinnerRockyg: it only works with commit messages i think21:16
jokke_Rockyg: in my understanding it does not ... the *Impact is commit message thing21:16
RockygHmmm.21:16
jokke_the security bugs are special cupcake and gets all kind of bells and whistles anyways21:16
bknudsonI think the security tag causes an email21:16
nkrinnerwould you like to have something similar with a log tag?21:17
nkrinnersounds like a better idea to me21:17
jokke_bknudson: I think it's not the tag but the classification of security bug in LP that triggers the e-mail (which is not sent to the public list)21:18
RockygIt would be worth polling the operators about it.  If they want an email, then we could get the tag across all projects21:18
nkrinnerdo operators really want notifications about issues with logging? i want it as a developer though21:19
bknudsonif they're interested they can subscribe to the mailing list21:20
*** VW_ has joined #openstack-meeting-421:20
RockygI wonder if there's a mailing list for the bugs with ops tag?21:20
bknudsonI didn't know about the ops tag.21:21
bknudsonare operators supposed to add that?21:21
Rockyganyone who thinks fixing the bug would make ops' lives easier.21:22
Rockygbut I suspect, usually ops ;-)21:22
RockygThis is good info.  Now we just need to figure out what we should do with it.  Certainly it raises at least one question to ask ops at the summit21:24
RockygLet's think more on this and what other info we want to get from ops at the summit.21:24
Rockygand let's call it a meeting?21:24
Rockyg#endmeeting21:25
*** openstack changes topic to "Gate is experiencing epic failures due to issues with mirrors, work is underway to mitigate and return to normal levels of sanity"21:25
openstackMeeting ended Wed Apr 29 21:25:26 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-04-29-20.09.html21:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-04-29-20.09.txt21:25
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-04-29-20.09.log.html21:25
nkrinnerbye21:25
*** nkrinner has quit IRC21:25
RockygThanks!21:25
jokke_thanks21:25
*** praveens has quit IRC21:27
*** praveens has joined #openstack-meeting-421:27
*** Rockyg has quit IRC21:30
*** praveens has quit IRC21:43
*** SumitNaiksatam has quit IRC21:43
*** bnemec has quit IRC21:52
*** mwang2_ has quit IRC22:00
*** bnemec has joined #openstack-meeting-422:02
*** VW_ has quit IRC22:03
*** Swami has quit IRC22:04
*** VW_ has joined #openstack-meeting-422:06
*** bharath has quit IRC22:06
*** xingchao has joined #openstack-meeting-422:07
*** VW_ has quit IRC22:09
*** VW_ has joined #openstack-meeting-422:09
*** xingchao has quit IRC22:14
*** VW_ has quit IRC22:16
*** bharath has joined #openstack-meeting-422:18
*** belmoreira has quit IRC22:18
*** salv-orlando has joined #openstack-meeting-422:19
*** salv-orl_ has quit IRC22:23
*** britthou_ has joined #openstack-meeting-422:24
*** britthouser has quit IRC22:25
*** jckasper has quit IRC22:27
*** britthouser has joined #openstack-meeting-422:30
*** britthou_ has quit IRC22:30
*** mwang2 has joined #openstack-meeting-422:30
*** klamath has quit IRC22:31
*** xingchao has joined #openstack-meeting-422:36
*** fallenpegasus has quit IRC22:40
*** imcsk8 has joined #openstack-meeting-422:45
*** bknudson has quit IRC22:46
*** Swami has joined #openstack-meeting-422:47
*** bharath has quit IRC22:48
*** daneyon has left #openstack-meeting-422:48
*** carl_baldwin has quit IRC22:51
*** mwang2 has quit IRC22:56
*** rm_work is now known as rm_work|away22:58
*** aventerav has quit IRC22:59
*** dannywilson has quit IRC23:08
*** cgoncalves has quit IRC23:10
*** dannywilson has joined #openstack-meeting-423:11
*** cgoncalves has joined #openstack-meeting-423:12
*** Sukhdev has quit IRC23:14
*** ivar-lazzaro has quit IRC23:18
*** ivar-lazzaro has joined #openstack-meeting-423:19
*** ivar-lazzaro has quit IRC23:20
*** ivar-lazzaro has joined #openstack-meeting-423:20
*** Rockyg has joined #openstack-meeting-423:20
*** fallenpegasus has joined #openstack-meeting-423:22
*** panda has quit IRC23:24
*** panda has joined #openstack-meeting-423:25
*** banix has joined #openstack-meeting-423:33
*** fallenpegasus has quit IRC23:33
*** emagana has quit IRC23:40
*** IlyaG has quit IRC23:47
*** dims has quit IRC23:50
*** dannywil_ has joined #openstack-meeting-423:52
*** dannywilson has quit IRC23:55
*** wojdev has quit IRC23:55
*** dannywil_ has quit IRC23:57
*** stevelle has joined #openstack-meeting-423:59

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