Wednesday, 2015-05-27

*** emagana has quit IRC00:01
*** markvoelker has joined #openstack-meeting-400:16
*** banix has quit IRC00:16
*** sigmavirus24_awa is now known as sigmavirus2400:17
*** david-lyle has quit IRC00:20
*** Sukhdev has joined #openstack-meeting-400:22
*** sdake has quit IRC00:22
*** markvoelker has quit IRC00:23
*** markvoelker has joined #openstack-meeting-400:23
*** salv-orlando has joined #openstack-meeting-400:25
*** puranamr has quit IRC00:25
*** sarob has quit IRC00:25
*** puranamr has joined #openstack-meeting-400:26
*** puranamr has quit IRC00:30
*** LouisF has joined #openstack-meeting-400:32
LouisF#startmeeting service-chaining00:33
openstackMeeting started Wed May 27 00:33:01 2015 UTC and is due to finish in 60 minutes.  The chair is LouisF. Information about MeetBot at http://wiki.debian.org/MeetBot.00:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:33
*** openstack changes topic to " (Meeting topic: service-chaining)"00:33
openstackThe meeting name has been set to 'service_chaining'00:33
LouisF#endmeeting00:35
*** openstack changes topic to "(Meeting topic: sc)"00:35
openstackMeeting ended Wed May 27 00:35:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)00:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-05-27-00.33.html00:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-05-27-00.33.txt00:35
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-05-27-00.33.log.html00:35
kragnizLouisF: short meeting :P00:36
LouisFkragniz: only a test00:37
*** daneyon has joined #openstack-meeting-400:38
*** daneyon has quit IRC00:43
*** yamahata has quit IRC00:44
*** LouisF has quit IRC00:49
*** bharath has quit IRC00:53
*** salv-orlando has quit IRC01:03
*** asselin_ has joined #openstack-meeting-401:04
*** fallenpegasus has joined #openstack-meeting-401:05
*** klamath has joined #openstack-meeting-401:07
*** klamath has quit IRC01:07
*** klamath has joined #openstack-meeting-401:07
*** tobe has joined #openstack-meeting-401:09
*** klamath has quit IRC01:11
*** dims has quit IRC01:12
*** IlyaG has quit IRC01:16
*** SumitNaiksatam has quit IRC01:18
*** sigmavirus24 is now known as sigmavirus24_awa01:24
*** david-lyle has joined #openstack-meeting-401:35
*** puranamr has joined #openstack-meeting-401:38
*** puranamr has quit IRC01:42
*** s3wong has quit IRC01:51
*** Sukhdev has quit IRC01:51
*** yamahata has joined #openstack-meeting-401:53
*** ivar-lazzaro has quit IRC02:03
*** salv-orlando has joined #openstack-meeting-402:04
*** salv-orlando has quit IRC02:09
*** salv-orlando has joined #openstack-meeting-402:21
*** salv-orlando has quit IRC02:25
*** daneyon has joined #openstack-meeting-402:27
*** daneyon has quit IRC02:31
*** david-lyle has quit IRC02:33
*** SumitNaiksatam has joined #openstack-meeting-402:35
*** jckasper has joined #openstack-meeting-402:51
*** asselin_ has quit IRC02:54
*** jckasper has quit IRC02:56
*** tobe has quit IRC03:08
*** SumitNaiksatam has quit IRC03:08
*** SumitNaiksatam has joined #openstack-meeting-403:09
*** carl_baldwin has joined #openstack-meeting-403:11
*** david-lyle has joined #openstack-meeting-403:11
*** salv-orlando has joined #openstack-meeting-403:21
*** tobe has joined #openstack-meeting-403:26
*** VW has joined #openstack-meeting-403:26
*** salv-orl_ has joined #openstack-meeting-403:28
*** salv-orlando has quit IRC03:29
*** salv-orl_ has quit IRC03:32
*** salv-orlando has joined #openstack-meeting-403:36
*** salv-orlando has quit IRC03:41
*** salv-orl_ has joined #openstack-meeting-403:43
*** salv-orl_ has quit IRC03:43
*** VW has quit IRC03:44
*** VW has joined #openstack-meeting-403:45
*** sarob has joined #openstack-meeting-403:49
*** emagana has joined #openstack-meeting-403:51
*** sarob has quit IRC03:53
*** sarob has joined #openstack-meeting-403:53
*** bharath has joined #openstack-meeting-403:54
*** armax has quit IRC03:54
*** Sukhdev has joined #openstack-meeting-403:58
*** tobe has quit IRC03:58
*** bharath has quit IRC03:58
*** krtaylor has joined #openstack-meeting-404:04
*** carl_baldwin has quit IRC04:09
*** daneyon has joined #openstack-meeting-404:15
*** eghobo has joined #openstack-meeting-404:16
*** daneyon has quit IRC04:20
*** markvoelker has quit IRC04:31
*** sarob has quit IRC04:34
*** tobe has joined #openstack-meeting-404:34
*** puranamr has joined #openstack-meeting-404:34
*** VW has quit IRC04:58
*** matrohon has joined #openstack-meeting-405:01
*** tobe has quit IRC05:04
*** nkrinner has joined #openstack-meeting-405:05
*** salv-orlando has joined #openstack-meeting-405:16
*** sdake has joined #openstack-meeting-405:18
*** salv-orlando has quit IRC05:21
*** belmoreira has joined #openstack-meeting-405:23
*** matrohon has quit IRC05:27
*** Sukhdev has quit IRC05:34
*** sdake has quit IRC05:40
*** salv-orlando has joined #openstack-meeting-405:44
*** salv-orl_ has joined #openstack-meeting-405:47
*** salv-orlando has quit IRC05:48
*** tobe has joined #openstack-meeting-405:50
*** puranamr has quit IRC05:52
*** salv-or__ has joined #openstack-meeting-405:55
*** salv-orl_ has quit IRC05:55
*** salv-orl_ has joined #openstack-meeting-405:57
*** salv-or__ has quit IRC06:00
*** emagana has quit IRC06:00
*** emagana has joined #openstack-meeting-406:01
*** salv-orlando has joined #openstack-meeting-406:01
*** salv-orl_ has quit IRC06:02
*** daneyon has joined #openstack-meeting-406:04
*** emagana has quit IRC06:05
*** salv-orlando has quit IRC06:06
*** salv-orlando has joined #openstack-meeting-406:06
*** daneyon has quit IRC06:09
*** SumitNaiksatam has quit IRC06:19
*** fallenpegasus has quit IRC06:20
*** SumitNaiksatam has joined #openstack-meeting-406:20
*** tobe has quit IRC06:20
*** salv-orlando has quit IRC06:21
*** salv-orl_ has joined #openstack-meeting-406:28
*** salv-orlando has joined #openstack-meeting-406:31
*** salv-or__ has joined #openstack-meeting-406:33
*** salv-orl_ has quit IRC06:33
*** salv-orlando has quit IRC06:35
*** salv-or__ has quit IRC06:37
*** tobe has joined #openstack-meeting-406:38
*** salv-orlando has joined #openstack-meeting-406:49
*** salv-orl_ has joined #openstack-meeting-406:53
*** salv-orlando has quit IRC06:53
*** salv-orl_ has quit IRC06:58
*** salv-orlando has joined #openstack-meeting-406:58
*** salv-orl_ has joined #openstack-meeting-407:00
*** salv-orlando has quit IRC07:03
*** salv-orl_ has quit IRC07:05
*** [1]evgenyf has joined #openstack-meeting-407:16
*** markvoelker has joined #openstack-meeting-407:17
*** radek__ has joined #openstack-meeting-407:18
*** salv-orlando has joined #openstack-meeting-407:23
*** matrohon has joined #openstack-meeting-407:24
*** emagana has joined #openstack-meeting-407:25
*** salv-orlando has quit IRC07:27
*** salv-orlando has joined #openstack-meeting-407:27
*** emagana has quit IRC07:30
*** salv-orlando has quit IRC07:31
*** salv-orlando has joined #openstack-meeting-407:32
*** salv-orl_ has joined #openstack-meeting-407:35
*** salv-orlando has quit IRC07:36
*** tobe has quit IRC07:37
*** dims has joined #openstack-meeting-407:38
*** tobe has joined #openstack-meeting-407:38
*** eghobo has quit IRC07:39
*** paramite has joined #openstack-meeting-407:40
*** geetika_ has joined #openstack-meeting-407:41
*** dims has quit IRC07:44
*** daneyon has joined #openstack-meeting-407:53
*** daneyon has quit IRC07:58
*** emagana has joined #openstack-meeting-408:04
*** emagana has quit IRC08:09
*** bharath has joined #openstack-meeting-408:13
*** matrohon has quit IRC08:14
*** tobe has quit IRC08:42
*** tobe has joined #openstack-meeting-408:43
*** geetika__ has joined #openstack-meeting-408:49
*** geetika_ has quit IRC08:50
*** emagana has joined #openstack-meeting-408:59
*** daneyon has joined #openstack-meeting-409:01
*** emagana has quit IRC09:03
*** daneyon has quit IRC09:06
*** mfedosin has quit IRC09:12
*** geetika__ has quit IRC09:14
*** belmoreira has quit IRC09:15
*** mfedosin has joined #openstack-meeting-409:17
*** geetika__ has joined #openstack-meeting-409:39
*** emagana has joined #openstack-meeting-409:53
*** emagana has quit IRC09:57
*** jpekkari has joined #openstack-meeting-410:02
*** dims has joined #openstack-meeting-410:09
*** geetika__ has quit IRC10:35
*** rods has joined #openstack-meeting-410:43
*** emagana has joined #openstack-meeting-410:47
*** emagana has quit IRC10:48
*** emagana has joined #openstack-meeting-410:48
*** daneyon has joined #openstack-meeting-410:50
*** emagana has quit IRC10:53
*** daneyon has quit IRC10:55
*** matrohon has joined #openstack-meeting-411:17
*** openstack has joined #openstack-meeting-411:37
*** ChanServ sets mode: +o openstack11:37
*** emagana has joined #openstack-meeting-411:43
*** emagana has quit IRC11:48
*** tobe has joined #openstack-meeting-411:52
*** tobe has quit IRC11:56
*** tobe has joined #openstack-meeting-411:57
*** markvoelker has quit IRC12:04
*** markvoelker has joined #openstack-meeting-412:04
*** rods has quit IRC12:05
*** dims has quit IRC12:31
*** dims has joined #openstack-meeting-412:32
*** emagana has joined #openstack-meeting-412:37
*** daneyon has joined #openstack-meeting-412:39
*** emagana has quit IRC12:41
*** daneyon has quit IRC12:44
*** matrohon has quit IRC12:44
*** rods has joined #openstack-meeting-412:49
*** jpekkari has quit IRC12:51
*** marcusvrn has joined #openstack-meeting-412:52
*** [2]evgenyf has joined #openstack-meeting-412:54
*** [1]evgenyf has quit IRC12:56
*** klamath has joined #openstack-meeting-412:57
*** klamath has quit IRC12:57
*** klamath has joined #openstack-meeting-412:58
*** bknudson has joined #openstack-meeting-413:06
*** jckasper has joined #openstack-meeting-413:07
*** singlethink has joined #openstack-meeting-413:13
*** bharath has quit IRC13:15
*** salv-orl_ has quit IRC13:17
*** VW has joined #openstack-meeting-413:17
*** Bjoern__ has joined #openstack-meeting-413:20
*** matrohon has joined #openstack-meeting-413:25
*** singleth_ has joined #openstack-meeting-413:31
*** emagana has joined #openstack-meeting-413:31
*** sdake_ has joined #openstack-meeting-413:31
*** singlethink has quit IRC13:34
*** emagana has quit IRC13:35
*** sdake has joined #openstack-meeting-413:47
*** qwebirc17933 has joined #openstack-meeting-413:48
*** qwebirc17933 has quit IRC13:49
*** sdake_ has quit IRC13:51
*** singlethink has joined #openstack-meeting-413:51
*** nmj3e has joined #openstack-meeting-413:54
*** singleth_ has quit IRC13:55
*** daneyon has joined #openstack-meeting-414:00
*** radek__ has quit IRC14:01
*** radek__ has joined #openstack-meeting-414:02
*** anthonyper has left #openstack-meeting-414:03
*** saneax has joined #openstack-meeting-414:06
*** sigmavirus24_awa is now known as sigmavirus2414:06
*** paramite is now known as paramite|afk14:09
*** aventerav has joined #openstack-meeting-414:12
*** tobe has quit IRC14:15
*** bharath has joined #openstack-meeting-414:15
*** bharath has quit IRC14:20
*** jokke_ has quit IRC14:24
*** jokke_ has joined #openstack-meeting-414:24
*** paramite|afk is now known as paramite14:25
*** bnemec has quit IRC14:30
*** mestery has quit IRC14:33
*** mestery has joined #openstack-meeting-414:34
*** bnemec has joined #openstack-meeting-414:35
*** dims has quit IRC14:35
*** daneyon_ has joined #openstack-meeting-414:37
*** daneyon has quit IRC14:40
*** emagana has joined #openstack-meeting-414:40
*** salv-orlando has joined #openstack-meeting-414:45
*** GB21 has joined #openstack-meeting-414:45
*** pshige has joined #openstack-meeting-414:48
*** zz_ja is now known as zz_zz_ja14:52
*** patrickeast has joined #openstack-meeting-414:52
*** dims_ has joined #openstack-meeting-414:55
*** carl_baldwin has joined #openstack-meeting-415:00
*** salv-orlando has quit IRC15:00
krtaylor#startmeeting third-party15:00
openstackMeeting started Wed May 27 15:00:56 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:01
krtaylorwho's here for third party CI working group meeting?15:01
patrickeasto/15:01
mmedvedeo/15:01
ctlaugh_o/15:01
*** armax has joined #openstack-meeting-415:01
zz_zz_jao/15:02
krtaylorwelcome everyone15:02
krtaylorit was really good getting to meet some of you in Vancouver15:03
krtaylorok, here's the agenda for today15:03
krtaylor#link https://wiki.openstack.org/wiki/Meetings/ThirdParty#5.2F27.2F15_1500_UTC15:03
krtaylor#topic Annoucements15:04
*** openstack changes topic to "Annoucements (Meeting topic: third-party)"15:04
*** asselin_ has joined #openstack-meeting-415:04
krtaylorthere was an email thread for setting deadlines for cinder volume drivers15:04
krtaylorI believe that date was June 19th15:05
patrickeast19th to be merged, 12th to have ci up and passing15:05
krtaylorpatrickeast, asselin_  can you confirm?15:05
asselin_hi...i'm double-booked...so my response here may be slow15:05
krtaylorasselin_ np15:05
asselin_yes, what patrickeast said K1 merge, K1 - 1 week for CI up and running. Should map to those dates.15:06
krtaylorok, so hopefully those dates get out to everyone, spread the word15:06
krtaylorok, any other quick announcements ?15:07
krtaylor#topic Vancouver BoF session15:08
*** openstack changes topic to "Vancouver BoF session (Meeting topic: third-party)"15:08
krtaylorwe had a good, although small session, intermixed with the BoF15:08
krtaylorit was good to meet everyone, and I had a bunch of follow up conversations after15:09
krtaylorit was a good review of the Xen testing and a brief discussion on what we have coming up to work on for CI systems15:09
krtaylorafter the turn out in Paris, I was expecting more15:10
krtaylorbut that was probably due to several factors15:10
asselin_who is new hear today b/c of BoF session?15:10
krtaylorone being that it was in the other building15:10
krtayloranyone?15:10
*** [2]evgenyf has quit IRC15:11
krtaylorit was interesting to see that most attending the BoF did not know about these meetings, either the office hours meeting or the working group15:11
krtaylorso, I think there is an action there for all of us, to spread the word about this resource15:12
krtaylorthats actually a good bridge to the next topic, these meetings15:13
krtaylorany questions about the BoF?15:13
krtaylor#topic Meeting Frequency15:14
*** openstack changes topic to "Meeting Frequency (Meeting topic: third-party)"15:14
*** nfedotov has joined #openstack-meeting-415:14
*** nfedotov has left #openstack-meeting-415:15
*** singleth_ has joined #openstack-meeting-415:15
krtaylorI wanted to bring up for discussion, then possible email thread, the number of meetings we are having15:15
*** tobe has joined #openstack-meeting-415:15
krtaylorthe 0400UTC meetings are generally not attended well15:15
krtaylorand this one now has a large overlap in status with the office hours meetings15:16
krtaylorhow does everyone feel about these meetings?15:16
krtaylordo we need to reduce the frequency, or just advertise better?15:16
krtaylorI have been trying for many months now to get other systems to participate and share their "secrets" on how they are doing testing15:17
ctlaugh_I only attend this one, not the 0400UTC, but like having it -- the different focus from the office hours meting15:17
*** singlet__ has joined #openstack-meeting-415:18
krtaylorok, good, thanks ctlaugh_15:18
*** singlethink has quit IRC15:18
zz_zz_jawhen you say office hrs, you're talking about the infra mtg on iirc monday late utc?15:18
krtayloryes Mondays 1500UTC15:19
patrickeasti’m ok with the times, but i do think we could probably reduce the frequency, it seems like the 0400 meetings are usually unproductive due to how many people show up15:20
*** tobe has quit IRC15:20
*** fallenpegasus has joined #openstack-meeting-415:20
mmedvedeI normally only show up for this one as well15:20
zz_zz_ja...searching our ThirdParty mtg page, for example, there is no mention of office hrs.  I'm not sure if "their" mtg page exists, or pts to us if the page does exist.  If they're related, how does someone not already embedded figure out where to spend their time most productively?15:21
*** singleth_ has quit IRC15:21
ctlaugh_If there was only 1 meeting, I would probably make arrangements to attend even if it was late (unless it ended up in the middle of the night).  This time is just much more convenient.15:21
zz_zz_jaIf we're trying to attract new people, the content of the advertising matters (why attend this mtg?).15:22
*** singlethink has joined #openstack-meeting-415:22
krtaylorzz_zz_ja, good feedback, I wrote meeting descriptions, but they were quickly changed15:22
krtaylorI guess what I am thinking was that initially, there was a storm of people needing to ask questions about getting started (Office Hours)15:23
krtaylorthat has calmed down15:23
krtaylornot sure if we will get another wave as other projects require CI15:24
krtayloranyway, it was useful to split the meetings, I was just poking at whether it was still useful, and the frequency15:24
asselin_manila is starting15:24
zz_zz_jathe operative variable is probably organization at least as much as project.15:24
*** singlet__ has quit IRC15:25
krtaylorlet's take this to an email thread, see if we can come to a consensus15:26
asselin_+115:27
krtayloralso, I'd really like to get some help chairing the meetings, but I'll add that to the email15:27
krtayloronward then15:28
krtaylor#topic Monitoring dashboard15:28
*** openstack changes topic to "Monitoring dashboard (Meeting topic: third-party)"15:28
krtaylorso the spec is basically done, but not getting a +215:28
krtaylor#link https://review.openstack.org/#/c/135170/15:29
asselin_I pinged infra once...but perhaps the timing was bad15:29
krtaylorsweston, you around?15:29
krtaylorasselin_, yeah, I am hoping that's the issue, but I'll add it to the agenda for next week if we don't get merged soon15:30
krtaylorI don't think there are any open concerns15:30
krtaylorat least none that I know of or that have been in comments15:31
krtaylorwe did have some hall discussions at summit on whether to stay with the radar code or to enhance another one, such as patrickeast 's15:32
krtaylorsweston seems to be very busy with his day job atm15:32
krtaylorany questions about CI monitoring or the dashboard?15:33
ctlaugh_My only other question was whether it would just monitor gerrit, or if it would also (at some point) be able to report CI status of non-gerrit-based CIs15:33
ctlaugh_periodic vs commit-based15:34
krtaylornon-gerrit, meaning not reporting back, or?15:34
krtaylorah, ok15:34
*** paramite has quit IRC15:34
ctlaugh_and yes, not reporting back to gerrit15:35
krtaylorgood point, but I think it would have to be gerrit to start, all systems probably have one project they are reporting back against15:35
krtaylormaybe when the periodic dashboard is done we can figure out how to mine that, but nothing comes to mind15:36
ctlaugh_I'm going to look back at setting up a CI using the puppet modules to test off of gerrit, but we will also be running just nightly jobs as well.  One set of our testing (multiple boards, various OS distros) will never be stable enough to hook into gerrit without irritating everyone :)15:37
krtaylorhere is the link to that periodic dashboard summit session etherpad15:38
krtaylor#link https://etherpad.openstack.org/p/YVR-QA-testing-beyond-the-gate15:38
ctlaugh_thank you15:38
*** VW has quit IRC15:39
krtaylorsdague said that if we wanted to, we could look at accelerating the third party reporting, but that was v2 discussion for them15:39
krtaylorbut he welcomed the idea of us doing that work15:40
*** VW has joined #openstack-meeting-415:40
krtaylorwhich reminds me, I was going to talk to mrodden about that15:41
krtaylorany other comments? questions?15:41
krtaylornext then15:42
*** sacharya has joined #openstack-meeting-415:42
krtaylor#topic Common CI15:42
*** openstack changes topic to "Common CI (Meeting topic: third-party)"15:42
krtaylorasselin_ can you give us a brief summary of the working sessions at summit?15:42
asselin_yes, we had a nice working session during the summit15:43
asselin_we broke out into many small groups working on the various parts15:43
asselin_some of the -infra cores focused on the testing effort and made quite a bit of progress15:43
asselin_we had some new people contribute, juame devessa15:44
asselin_so still a lot of work to do, and now we've got more people on board, so that's helpful15:45
krtaylorit was great to see all the merges15:45
*** eghobo has joined #openstack-meeting-415:45
asselin_yes15:45
asselin_sorry...need to step away for a few minutes.....15:45
krtaylorsure np, patrickeast, ctlaugh_ were you able to attend these working sessions?15:46
ctlaugh_no, I was not15:46
krtaylorI had schedule conflicts :(15:46
patrickeastsame, there were cinder meetings i needed to attend at the same time15:46
*** wznoinsk_ has joined #openstack-meeting-415:47
krtayloryeah, my entire week was a schedule conflict with one thing or another15:47
*** bharath has joined #openstack-meeting-415:47
krtaylorI'm sure it was optimized for someone ;)15:48
*** wznoinsk_ is now known as wznoinsk15:48
krtaylorok, well here is the link for the common CI effort15:48
krtaylor#link https://review.openstack.org/#/q/topic:downstream-puppet,n,z15:49
krtaylorhelp how you can, sign up for a chunk, or at least review the patches15:49
*** saneax has quit IRC15:50
*** Sukhdev has joined #openstack-meeting-415:50
krtaylor#topic Open Discussion15:50
*** openstack changes topic to "Open Discussion (Meeting topic: third-party)"15:50
krtaylorI'll open it up, anything to discuss?15:51
krtaylorimpressions, surprises from summit?15:51
*** eghobo_ has joined #openstack-meeting-415:51
patrickeastoh i had one thing to bring up15:52
*** bharath has quit IRC15:52
krtaylorit was good to see the 2016 summit locations announced15:52
krtaylorpatrickeast, sure15:52
*** inc0__ has joined #openstack-meeting-415:52
patrickeastfor the tools repo, are we planning to just dump stuff in there or is it more restrictive?15:52
patrickeasti ask because i’ve had reviews up for a couple weeks now, should we just ninja +2/A them in? or wait for more people to see them?15:53
krtaylorpatrickeast, ah, good question15:53
krtayloryes, I have been meaning to address those, I'd like to get other eyes on them15:53
krtaylorsummit timing I'm betting15:54
*** barra204 has quit IRC15:54
krtaylor#link https://review.openstack.org/#/q/stackforge/third-party-ci-tools,n,z15:55
krtaylorall, please review15:55
*** eghobo has quit IRC15:55
krtaylorbut, as initial patches, I think we'd be ok with pushing them as is15:55
krtaylorwe don't have tests for the repo, so no gate testing, ect15:56
*** mstachow has joined #openstack-meeting-415:56
mmedvedeI did review and +1 the ones I understand. I think there is no harm approving15:56
*** dannywilson has joined #openstack-meeting-415:56
krtayloragreed15:56
patrickeasti guess one thing to consider is if we want more like a dumping ground spot and then a more thorough review process to put things into more of a production ready state15:56
patrickeasti think we’ve talked about that before, but i forget what the decision was15:57
krtaylorpatrickeast, good point, I guess I was thinking that if the tools grew and took on a life, they would be promoted to their own project and that would include testing, etc15:57
patrickeastyea that makes sense15:58
krtaylorthe could then be promoted again if they made it to infra usefulness15:58
mmedvedeI think less initial friction is good15:58
patrickeastso then the bar should be pretty low for adding stuff to the tools repo, it might be worth us putting together some criteria15:59
*** rhallisey has joined #openstack-meeting-415:59
*** vinod_ has joined #openstack-meeting-415:59
patrickeastmmedvede: +115:59
mmedvede+2 everything! :)15:59
patrickeastlol15:59
*** SamYaple has joined #openstack-meeting-415:59
krtaylorhehheh, well...15:59
krtaylorok, out of time15:59
krtaylorthanks everyone!15:59
mmedvedeagree on criteria though, too much freedom would make it harder down the line...16:00
krtaylor#endmeeting16:00
*** openstack changes topic to "(Meeting topic: sc)"16:00
openstackMeeting ended Wed May 27 16:00:21 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-05-27-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-05-27-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-05-27-15.00.log.html16:00
*** emagana has quit IRC16:00
sdake#startmeeting kolla16:00
openstackMeeting started Wed May 27 16:00:52 2015 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
*** yamahata has quit IRC16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: kolla)"16:00
openstackThe meeting name has been set to 'kolla'16:00
*** zz_zz_ja is now known as zz_zz_zz_ja16:01
*** jpeeler has joined #openstack-meeting-416:01
sdake#topic rollcall16:01
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:01
*** yamahata has joined #openstack-meeting-416:01
rhalliseyhi16:01
SamYaplehello16:01
akwasnieHi16:01
*** patrickeast has left #openstack-meeting-416:01
sdakeo/ folks16:01
mstachowhi all :D16:01
jpeelerhi16:01
daneyon_hey16:02
*** emagana has joined #openstack-meeting-416:02
*** matrohon has quit IRC16:02
sdakeyo daneyon_16:02
sdakewondering where you been bro :)16:02
sdakegrats on 10 years at csco :)16:02
daneyon_thx16:02
sdake#topic announcements16:02
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:02
rhalliseydaneyon_, nice!16:02
sdakefirst off summit was fantastic for containers16:03
sdakewe gave a 40 minute talk on kolla16:03
sdakewhich I htink overall went pretty well and gave the audience an understanding of what we are working on16:03
daneyon_i thought i was at DockerCon then realized it was an openstack conference16:03
sdakeit didn't answer what we are working towards :)16:03
daneyon_lol!!!!16:03
sdakeroflcopter danyeon ;)16:04
sdakeso ya, rockin job at the summit folks16:04
rhallisey:D16:04
sdakeour irc channel members have doubled16:04
sdakethats a sign that people really care ;)16:04
sdakeok on with the meeting16:04
sdake#topic l1 blueprint review16:04
*** openstack changes topic to "l1 blueprint review (Meeting topic: kolla)"16:04
sdakeliberty 1 deadline is June 25th16:05
sdakeunlike previous releases of kolla, where we were kind of loose with the release schedule I want to be strict this time around16:05
sdakeany objections from the core team?16:05
rhalliseynada16:05
daneyon_nope16:06
jpeelersounds good16:06
jpeelerprobably need to start filing more bugs into launchpad too16:06
jpeelerand referencing them from the commit16:06
sdakeya, we really need to stop slacking on the blueprint filing16:07
sdakewe agreed a couple weeks ago to -1 reviews that don't reference a bug or blueprint16:07
sdakebut we agreed to wait until after summit16:07
sdakeso now is the time to put that agreement into affect16:07
sdakeany objections to -1 a review without a blueprint or bug attached?16:08
daneyon_nope16:08
sdakethe reason we file blueprints and bugs is because all that stuff gets dashboarded16:08
*** singleth_ has joined #openstack-meeting-416:08
sdakeso for the younger cats in the crowd a dashboard is how the check writers determine where to write the checks :)16:09
sdakestackalytics is a dashboard16:09
sdakestats matter to some people, so its better if our stats are accurate16:09
sdakeplease don't try to game the stats16:09
sdakebut lets be accurate16:09
sdakeplus it makes my life a whole lot easier determining what is in a release :)16:09
sdake#link https://launchpad.net/kolla/+milestone/l116:09
sdakehere is what is on deck for June 25th16:10
sdakeplease take a moment to review16:10
sdakeif there is something in that list that isn't going to happen for l1, please let me know now or prior to next meeting16:10
sdakei'll give it a few minutes for folks to look it over16:10
*** asselin__ has joined #openstack-meeting-416:11
rhalliseysdake, I might add something..16:12
*** asselin_ has quit IRC16:12
sdakerhallisey we are free to add right up until the 24th of june :)16:12
SamYapleif we need blueprints or bugs to commit now, then ill be adding as well16:12
*** singlethink has quit IRC16:12
rhalliseyI'll add my min-env stuff there too16:12
sdakeif you want to add something and you are not on the drivers team, please contact a someone on the drivers team to handle assigning the blueprint or bug to you and getting it in the l1 release16:13
sdake(i.e. your a new contributor)16:13
sdakesamyaple cool works for me16:13
sdaketry to be accurage with what you want to take on in l116:13
sdakefang has 4 blueprints, I think he may end up dropping some of those to l216:14
inc0__sdake, I'm thinking of putting pacemaker/corosynk for later and start from keepalived16:14
inc0__corosync*16:14
sdakeinc0__ ok did you want me to make that change now?16:14
inc0__I'll do that16:14
sdakeok16:14
sdakethanks :)16:14
sdakeI can use all the help anyone can offer managing the launchpad tracker16:14
* sdake tired of clikcy clicky16:15
sdakeok thats about it for l116:15
sdake#topic kolla manifesto16:15
*** openstack changes topic to "kolla manifesto (Meeting topic: kolla)"16:15
sdake#link https://etherpad.openstack.org/p/kolla-manifesto16:15
sdakethis is a 10 minute collborative editing session of our mission16:15
sdakealot of folks had questions at summit about exactly what we do16:16
sdakewe all have opinions16:16
sdakelets get em out there16:16
sdakea good manifesto should not be a phd dissertation16:16
sdake1-2 liner16:16
sdakenobody has put in "we do deployment"16:19
sdakeI'd like to have a discussion about that16:20
SamYaplei dont agree that it should be a requirement16:20
SamYaplei think rhallisey has what i see down16:20
SamYapleflexible containers to be consumed by deployment tools16:20
sdakesamyaple huh?16:20
*** GB21 has quit IRC16:21
sdakewell we have already agreed unanmously previously deployment would be optioanl16:21
SamYapleah ok then16:21
sdakeshouldn't it be part of our manifesto?16:21
SamYaple"consumed by advanced orchestration tools"? that seems like it16:22
sdakei like line 3 and line 516:22
sdakeperhaps we should merge those into one statement16:22
sdakeany thoughts on that?16:23
SamYaplei agree with both.16:23
jpeeleryep16:24
sdakeline 3 look solid?16:24
SamYapleI dont see security mentioned. i always held that up high16:24
SamYaplelimiting perms where possible16:24
*** pkoniszewski has joined #openstack-meeting-416:25
sdakebest practices?16:25
SamYaplewould that be "best practices"?16:25
sdakewe can define best practices16:25
SamYapleok yea16:25
rhalliseyI like it16:25
sdakeok i'm deleting 4+16:25
daneyon_i like it16:25
sdakeeveryone godo with that?16:25
daneyon_ya16:25
SamYapleyes16:25
jpeeler+116:25
sdakebefoe we decide on this manifesto, I want to have our 2200 meeting to get input from the other folks (mostly mandre) who can't make this timeslot16:26
jpeelerwhere is this text going to officially end up living?16:26
sdakeon our wiki16:26
sdakewhich we dont have :)16:26
sdakewe need a wiki apge16:26
sdakeevery project has a wiki page16:26
sdakeanyone want to tackle that?16:27
sdakeok i'll add to my long list :)16:27
sdake#topic openstack namespace16:27
*** openstack changes topic to "openstack namespace (Meeting topic: kolla)"16:27
sdakeatm we are in the stackforge namespace16:28
sdakethere are not really many written rules about what it takes to get into the openstack namespace16:28
sdakebut I've done it personally with 2 projects16:28
sdakeso I know what it takes16:28
sdakeI am certain we can get there this cycle16:28
sdakewhen we are ready, i'm going to propose us for the openstack namespace16:29
SamYaplewhat defines ready16:29
sdakewe will have a vote on it prior to the git submission to the governance repo16:29
sdakesamyaple its magic :)16:29
SamYaple:D16:29
*** cdelatte has joined #openstack-meeting-416:29
jpeelerSamYaple: it just feels right16:29
sdakejpeeler got it16:29
sdakewe will all know the time16:30
sdakei feel it coming16:30
sdakediversity is part of it16:30
sdakeour community is very diverse16:30
sdakewhich is why kolla rocks :)16:30
sdakeI just wanted to have this discussion at the beginning of the cycle so folks know this isn't a science project and we are not wasting time16:30
sdakeany questions?16:31
inc0__sdake, we should get someone to run kolla on prod:)16:31
inc0__later this release16:31
SamYapleinc0__: got that covered16:31
sdakeinc0__ that would be helpful but not mandatory for openstack namespace16:31
sdake#topic open discussion16:32
*** openstack changes topic to "open discussion (Meeting topic: kolla)"16:32
*** GB21 has joined #openstack-meeting-416:32
rhalliseysdake, I'm going to propose a new blueprint that allow containers to support accepting config from a config file16:32
*** dannywilson has quit IRC16:32
rhalliseyany thoughts?16:32
sdakeconfig file how?16:32
rhalliseypass a config file to overwrite the existing config16:33
sdakepass how16:33
rhalliseyusing --env-file16:33
sdakenot familiar with that16:33
sdakei could rtfm or you could tell me about it16:33
sdakeyou mean our openstack.env file now?16:34
rhalliseythat would be one way to config on the fly16:34
SamYaplehttps://review.openstack.org/#/c/182168/ rhallisey16:34
rhalliseybut I was also hoping to say overwrite nova.conf or something16:34
SamYaplethat takes environment variables and builds a config16:35
inc0__sdake, I found something like that https://groups.google.com/forum/#!msg/docker-user/FyCWLC38Ueg/gh_1-NMc2NYJ16:35
sdakerhallisey I think sam has a plan for that - is yours different in some way?16:35
SamYaplerhallisey: i can work with you on that, im flexible, but i think our end goals are the same16:36
sdakeso I think its pretty clear we need to be able to support random config options to be viable16:36
rhalliseySamYaple, ah ok ya that looks good16:36
sdakehowever we get there wfm16:36
sdakeas long as it doesn't involve bindmounting the host os :)16:37
rhalliseysdake, the reason I think this is important is because it will help us build up our stock of neutron and cinder containers16:37
rhalliseysince that config can be wild16:37
sdakei hear ya16:37
sdakejust no -v /opt/kolla/etc:/etc ;)16:37
SamYapleagreed rhallisey. my patch says ansible, but can easily be generated any number of ways16:37
sdakethat would make me cry inside16:37
inc0__also that would help to decouple kolla containers from deployment methods16:37
SamYaplesdake: is that a jab at yaodu16:37
*** daneyon_ has quit IRC16:38
rhalliseyha16:38
sdakedo you do that in yaodu sam?16:38
SamYaple.... maybe16:38
rhalliseylol16:38
sdakewasn't a jab at that, just the model16:38
sdakeI really want to avoid bindmounting16:38
SamYaple:) i agree with you, thats why im here16:38
sdakelike REALLY want to avoid it16:38
*** GB21 has quit IRC16:38
sdakeand your dict env solves the problem nicely16:38
*** GB21 has joined #openstack-meeting-416:39
sdakeany other open discussion?16:39
rhalliseydocker-registry setup script16:39
rhalliseyI'm looking at that now if you think that's reasonable16:40
sdakedockr registry takes 5 minutes to setup16:40
sdakethe only downside is it sets up on port 5000 by default (atleast in fedora)16:40
rhalliseyya so it's an easy scirpt16:40
sdakemaybe taht should go in setup-docker16:40
sdakeand we should rename thatfile setup-env16:40
rhalliseyya I'm not using 5000 :/16:41
sdakeya clearly thats a bad idea ;-)16:41
mstachowmaybe docker-registry based on bridged network with mapped port?16:41
SamYapledocker-registry is configurable port-wise16:41
inc0__uhh...that would be counterintuitive16:41
SamYaplei use it with 80 and 44316:42
SamYapleit just an env variable i blieve16:42
rhalliseyit is16:42
rhalliseyit's pretty arbitrary16:42
sdakepeople will either use setup-env or not16:42
sdakei dont use it16:42
sdakerather setup-docker16:42
rhalliseyya makes sense16:43
sdakeits for new people to try our code out16:43
sdakemakes sense to me make a bug for it16:43
SamYapleshould we then have a "check" script to ensure the appropriate version and what not?16:43
sdakesince its not really blueprint material )16:43
sdakesamyaple good idea if anyone wants to tackle it16:43
sdakeso I totally blew the agenda16:44
SamYapleprobably could just back it in to setup-docker as an option (and run it after the full script as well)16:44
sdakesamyaple wfm - file bug :)16:44
SamYaplek16:44
sdake#topic continuous integration16:44
*** openstack changes topic to "continuous integration (Meeting topic: kolla)"16:44
sdakeso, F Fantastic job jpeeler did on beating the gate into submission16:44
jpeeler\o/16:45
sdakewe absolutely need an integration gate16:45
SamYaplew00t16:45
sdakethis is required for openstack namespace in my opinion16:45
jpeeleragreed16:45
sdakewe have more work to do16:45
sdakewe have image building working16:45
sdakewhich was a serious chore16:45
sdakewhat is next?16:45
jpeelerjust need a few setup scripts to be completed, think we're pretty close to being able to easily write a bunch of functional tests16:45
sdakenext in my mind is genenv16:46
sdakenext after that is kolla start16:46
jpeeleralthough... i also thought the image building would be a lot simpler. so maybe i should strike easily out16:46
sdakeso genenv and kolla start with neutron16:46
sdakehow precisely are we going to  do that :)16:46
sdakeI think we need some type of bridging setup for neutron to run on one interface16:46
sdakeI want to gate on neutron not nova-network16:47
sdakedaneyon_ any chance you can figure that out?16:48
sdakeI tried and tried for like 5 days16:48
SamYaplesdake: whats the struggle?16:48
sdakewe have a flat interface that should have no ip assigned that has internet access16:48
sdakewe have a public interface that is our management network16:48
sdakeI dont know if the builders have multiple ips16:49
sdakebut I suspect they do not16:49
SamYaplecan we use vlans?16:49
sdakeother projects set up a br-ex16:49
sdakein the gate, I suspect not :)16:49
sdakei mean use sure, but have it work correctly not sure16:49
SamYapleis this multinode testing we are talking about?16:50
sdakesingle node neutron16:50
jpeelerit'd be good to have a working setup with only one network interface for usage outside of the gate too16:50
sdaketotally agree16:50
*** yamahata has quit IRC16:51
sdaketo me, this single interface mode of operation is our most critical need atm16:51
SamYapleso is the network setup responsibility of the container, or external to the container?16:51
sdakekolla setup scripts16:51
jpeelerexternal16:51
sdakelike init-runonce16:51
sdakeor whatever its called now :)16:51
SamYapleyea should be easy to generate a few interfaces, be it bridge or otherwise16:51
sdakesamyaple I tried and tried and couldn't get it to work correctly16:52
sdakebut I didn't follow yoda's advice :)16:52
sdakeso does someone want to do? :)16:52
SamYaplewhen do you need it by? i fear taking on to much and not delivering becuase of a new baby16:53
sdakeat your own pace16:53
sdakebut at the head of the queue :)16:53
SamYapleI can dig into it16:53
sdakenice16:53
*** emagana has quit IRC16:53
sdake#action samyaple is going to save the universe :)16:53
SamYapleagree16:53
sdake:)16:54
sdakegood thing nobody has a shortage of egos here :)16:54
sdakeok anything else on the integrated gate?16:54
SamYaplehow else would we get kolla in the openstack namespace16:54
jpeelersdake: how do images get updated in the docker registry?16:54
sdakejpeeler are you planning to finish the rest of the gating work?16:54
SamYaplejpeeler: you push new images to the registry16:54
jpeelernobody responded to my latest email about that topic16:54
jpeelerhttp://lists.openstack.org/pipermail/openstack-dev/2015-May/064807.html16:55
jpeelermaybe it was too crazy16:55
SamYapleoh sorry i wasnt being sarcastic, i thought you meant local16:55
sdakejpeeler no idea how to do that in an automated way that keeps the infra team happy16:55
sdakeif anyone has ideas how to push that doesn't take 5 hours i'm all ears16:55
sdakejeblair suggested a periodic post job that woudl run every 10-20 commits16:56
SamYaplei do, but it involves shrinking the containers16:56
sdaketo update the images16:56
*** sbalukoff has quit IRC16:56
sdakesamyaple 4 minutes on the clock go :)16:56
sdakewhat is your proposal16:57
SamYapleright now we build containers with n number of layers and that includes stuff that may or may not be removed, due to layers. in yaodu i squeezed off 75% of the size by exporting and rebuilding the container from a tarball16:57
SamYaplethe kolla containres are quite large16:57
SamYaplesmaller size==faster push?16:57
sdakeagree16:57
sdakeso exporing and rebuild only 1 container?16:58
SamYapleit comes at the cost of removing container layer history (like a base image has no build history)16:58
rhalliseydocker save... docker load...?16:58
SamYaplekinda, but it still uses the base image layer rhallisey16:58
SamYapleand all the other tiers16:58
sdakeok this slot is needed shortly lets overflow back into #kolla to finish the discussion on this proposal16:59
sdakethanks for coming :)16:59
sdakelook forward to everyones contributions during liberty!16:59
*** mwang2 has joined #openstack-meeting-416:59
sdakelets rock it :)16:59
sdake#endmeeting16:59
*** openstack changes topic to "(Meeting topic: sc)"16:59
openstackMeeting ended Wed May 27 16:59:22 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-05-27-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-05-27-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-05-27-16.00.log.html16:59
*** rhallisey has left #openstack-meeting-416:59
*** mstachow has left #openstack-meeting-417:00
*** tobe has joined #openstack-meeting-417:04
*** simon-AS559 has joined #openstack-meeting-417:07
*** daneyon has joined #openstack-meeting-417:08
*** daneyon_ has joined #openstack-meeting-417:09
*** tobe has quit IRC17:09
*** mwang2_ has joined #openstack-meeting-417:12
*** pkoniszewski has quit IRC17:12
*** daneyon has quit IRC17:13
*** sdake_ has joined #openstack-meeting-417:14
*** mwang2 has quit IRC17:15
*** sdake has quit IRC17:17
*** SumitNaiksatam has quit IRC17:18
*** puranamr has joined #openstack-meeting-417:18
*** krtaylor has quit IRC17:22
*** puranamr has quit IRC17:22
*** yamahata has joined #openstack-meeting-417:24
*** puranamr has joined #openstack-meeting-417:24
*** GB21 has quit IRC17:24
*** bharath has joined #openstack-meeting-417:24
*** emagana has joined #openstack-meeting-417:31
*** VW has quit IRC17:31
*** puranamr has quit IRC17:31
*** puranamr has joined #openstack-meeting-417:32
*** inc0__ has quit IRC17:39
*** yanping has joined #openstack-meeting-417:40
*** sacharya has quit IRC17:41
*** yanping has left #openstack-meeting-417:41
*** sudipto has joined #openstack-meeting-417:44
*** SumitNaiksatam has joined #openstack-meeting-417:44
*** s3wong has joined #openstack-meeting-417:45
*** emagana has quit IRC17:50
*** Sukhdev has quit IRC17:50
*** asselin__ has quit IRC17:51
*** ivar-lazzaro has joined #openstack-meeting-417:51
*** dannywilson has joined #openstack-meeting-417:52
*** sdake has joined #openstack-meeting-417:55
*** dannywil_ has joined #openstack-meeting-417:55
*** dannywilson has quit IRC17:56
*** aduarte has joined #openstack-meeting-417:57
*** sarob has joined #openstack-meeting-417:58
*** sdake_ has quit IRC17:58
*** simon-AS559 has quit IRC18:01
*** dims_ has quit IRC18:02
*** dims_ has joined #openstack-meeting-418:03
*** sarob_ has joined #openstack-meeting-418:04
*** sarob has quit IRC18:06
*** Sukhdev has joined #openstack-meeting-418:08
*** rods has quit IRC18:09
*** VW has joined #openstack-meeting-418:12
*** Sukhdev has quit IRC18:13
*** rods has joined #openstack-meeting-418:13
*** slaweq has joined #openstack-meeting-418:14
*** krtaylor has joined #openstack-meeting-418:16
*** rods has quit IRC18:19
*** banix has joined #openstack-meeting-418:20
*** jckasper has quit IRC18:22
*** vishwanathj has joined #openstack-meeting-418:27
*** rods has joined #openstack-meeting-418:28
*** qwebirc32260 has joined #openstack-meeting-418:30
*** sudipto has quit IRC18:34
*** sbalukoff has joined #openstack-meeting-418:42
*** sdake_ has joined #openstack-meeting-418:47
*** sudipto has joined #openstack-meeting-418:47
*** Sukhdev has joined #openstack-meeting-418:49
*** VW has quit IRC18:49
*** sdake has quit IRC18:51
*** tobe has joined #openstack-meeting-418:53
*** tobe has quit IRC18:58
*** singlethink has joined #openstack-meeting-419:05
*** sdake has joined #openstack-meeting-419:06
*** singleth_ has quit IRC19:09
*** vishwanathj has quit IRC19:09
*** sdake_ has quit IRC19:10
*** VW has joined #openstack-meeting-419:12
*** qwebirc32260 has quit IRC19:14
*** spredzy is now known as spredzy|afk19:20
*** sudipto has quit IRC19:21
*** sarob_ has quit IRC19:29
*** rgerganov has quit IRC19:31
*** eghobo_ has quit IRC19:42
*** simon-AS559 has joined #openstack-meeting-419:49
*** simon-AS5591 has joined #openstack-meeting-419:50
*** simon-AS559 has quit IRC19:53
*** eghobo has joined #openstack-meeting-419:56
*** sballe has joined #openstack-meeting-419:56
*** eghobo has quit IRC19:58
*** eghobo_ has joined #openstack-meeting-419:59
*** mestery_ has joined #openstack-meeting-420:00
*** ajmiller_ is now known as ajmiller20:01
*** Rockyg has joined #openstack-meeting-420:01
jokke_o/20:01
Rockygo/20:02
nkrinnerhi20:02
Rockygkewl!  We have some people20:02
jokke_:)20:02
Rockyg#startmeeting log_wg20:02
openstackMeeting started Wed May 27 20:02:50 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
*** matrohon has joined #openstack-meeting-420:03
Rockygjokke_: bknudson dhellmann who am I forgetting?20:03
bknudsonhi20:03
*** mestery has quit IRC20:03
RockygHey, there!20:04
dhellmanno/20:04
*** banix has quit IRC20:04
RockygFirst off, I want to thank dhellmann for the new release of oslo.log20:05
RockygThanks, dhellmann!20:05
RockygNext, a recap of discussions at the summit20:05
Rockyg#topic Thanks for new oslo.log!20:06
*** openstack changes topic to "Thanks for new oslo.log! (Meeting topic: log_wg)"20:06
bknudsonwhat did dhellmann do?20:06
bknudsonit's got versionutils, so we should be able to use that in keystone20:06
dims_bknudson: yep it's in there20:06
dhellmannoh, dims_ did that yesterday20:07
*** sdake_ has joined #openstack-meeting-420:07
Rockygalso, got a deprecation message in, global requirement updates20:08
Rockygfixed a TRACE/ERROR issue20:08
*** jckasper has joined #openstack-meeting-420:08
Rockygfixed pep8 errors.20:08
RockygImproved docs around versionutils20:09
Rockygfixed syslog  stuff20:09
jokke_cool20:09
Rockyg741 insertions, 711 deletions.20:09
Rockygonwards.20:10
Rockyg#topic Summit Rehash20:10
*** openstack changes topic to "Summit Rehash (Meeting topic: log_wg)"20:10
*** sdake has quit IRC20:11
Rockygwe now have three competing specs for requester ID.  The second and third are cool because there are changes only in oslo.log and in the  related project, I think.20:12
Rockygtrying to find the links.  But, I have a question/concern for dhellmann, bknudson and other developers.20:12
jokke_hmm-m ... I was reading that e-mail today and I think I'm bit confused around those20:13
Rockygsecond review uses auth_token from Keystone.  I get that one.20:13
*** slaweq has quit IRC20:13
bknudsonauth_token middleware20:13
RockygThird review (don't know if it's there yet) uses ID from os_profiler20:14
dhellmannhttps://review.openstack.org/13483920:14
RockygThanks!20:14
bknudsonos_profiler kind of covered this already so it makes sense to use whatever they did.20:14
bknudsonrather than invent something new20:14
bknudsonmaybe the request ID part could be split out of os_profiler20:14
bknudsonoh, os profiler isn't accepted anyways20:15
*** slaweq has joined #openstack-meeting-420:15
RockygWell, if os_profiler can't be turned off, I can see where this would be ok.20:15
dhellmannbknudson: the spec isn't approved, but some projects have started adding os-profiler20:15
RockygBut, I could see ops guys not wanting the extra bits of a profiler running during production20:15
bknudsonactually it's os-profiler that should be able to use whatever request ID scheme that's actually accepted20:15
dhellmannwe can make it possible to turn off the profiler data collection part, but keep the request id stuff always on20:16
dhellmannyeah, I don't really care what we use as long as we pick one that works for all of our current use cases20:16
Rockygdhellmann: that would make me happier.  It just seems a wierd way to architect for request ids20:16
jokke_bknudson: I do agree, the req-id should be consumed by os-profiler, not other way around20:16
RockygShould we discuss this in the spec reviews, or take it to the mailing list?20:17
RockygI mean, it's nice that it's being taken on by the os-profiler, but I'm pretty sure that Keystone is a better fit for identity/security/architecture reasons20:18
dhellmannthere was a mailing list thread, we should probably follow up there20:18
jokke_++20:19
RockygGreat.20:19
RockygThanks.20:19
dhellmannhttp://lists.openstack.org/pipermail/openstack-dev/2015-May/064842.html20:19
jokke_and related to those 3 Solutions, the message from ops was really loud and clear in the summit, they want the option 3 where a sindle ID follows all the way20:20
RockygYeah.  We never did get to circle back to Abhishek20:20
dhellmannjokke_: yeah, that's unlikely to be accepted by devs though20:20
Rockygjokke_: for logs, yes, with a hop count.  so the first one always has to be passed, but others could come and go?20:21
jokke_dhellmann: I think we should look into mirror on that and think to whom these things are developed for20:21
*** VW has quit IRC20:21
dhellmannsome requests fork, and you wouldn't be able to keep track of the separate threads if you only have one id20:21
dhellmannjokke_: that solution just doesn't work technically, it's not a preference situation20:21
jokke_dhellmann: what does not work on it ... if we create id when it's not in request and pass it forward for any request created by the service, I don't see what technically would block it20:22
dhellmannthe os-profiler model takes care of the threading, so we should look closely at what they do20:23
Rockygdhellmann: jokke_ I think that's why we need to specify what gets passed in the log message, vs what is getting passed around.  We should always pass the initiating requestID around, and sometimes others.20:23
RockygBut, we should only pass the initiating request ID to log messages?20:23
dhellmannjokke_: (a) we can't trust the incoming request id as being unique (b) if nova makes several calls to another backend service like neutron, those each need a separate request id because they might happen in parallel20:24
RockygI think we do need to look at the threading design in os-profiler20:24
*** matrohon has quit IRC20:24
Rockygcan we take this as an action item to investigate further through code review and circle back next week?  Does that make sense?20:25
jokke_dhellmann: the (a) is irrelevant and (b) has good point ... I think way bigger problem is how big ID field we need if we start generating new IDs for every interraction ... good couple of dozen of them for one request and we're pretty quickly out of the uniqueness in big deployment anyways20:26
dhellmannRockyg: it would be good to have someone get all of the folks with proposals together to try to unify them20:26
RockygI would want to know how deep/often the forking happens20:26
jokke_dhellmann: ++20:26
Rockyg++20:26
Rockyg#action contact review authors and set an IRC meet20:26
dhellmannjokke_: if you let me pass "jokke_" as my request id with every client call, you'll very quickly find that your logs are useless20:27
jokke_dhellmann: only regarding your requests and you're just shooting yourself into foot with that20:27
jokke_dhellmann: and that was pretty loose quote from the ops during the session when we were talking about that20:29
RockygI think it would be good if we could get an example log flow and walk through it to see what happens.  In parallel to getting the three devs together20:29
RockygI'll ping the three devs, and the large system ops who was in the session to see what I can arrange.20:30
jokke_Rockyg: thanks20:31
RockygWill set up an etherpad for discussion and post it to the ML thread20:31
dhellmannsounds good20:31
jokke_Rockyg: I'll get a contact from our ops side for you as well as I think I didn't see any of our guys there20:31
RockygAnything else we should bring up from the summit?  Lots of oslo.log stuff, but I don't remember anything controversial about it :-)20:32
dhellmannno, not really20:32
dims_etherpad of the oslo.log session - https://etherpad.openstack.org/p/YVR-oslo-log-plans20:33
dhellmannthe spec to clean up the default handling has already been approved for oslo, so I'll start working on that in a few weeks when some of the other work I'm doing is wrapped up20:33
jokke_dhellmann: anything I can help with there?20:33
RockygOh, shoot.  Just remembered.  I likely won't be on next week.  Need someone else to run the meeting just in case.  I'll be in Boston for my college reunion20:33
*** VW has joined #openstack-meeting-420:34
Rockygthanks for the link, dims_20:34
jokke_#link https://etherpad.openstack.org/p/YVR-oslo-log-plans20:35
dhellmannjokke_: I have a pretty good idea of what's needed, but I'll want reviews20:35
RockygAnd also a heads up.  The primary backers of the os-profiler review are both very *strong* personalities.20:35
*** barra204 has joined #openstack-meeting-420:35
jokke_dhellmann: drop me a line here or e-mail if there's something you want a hand with ...20:35
dhellmannjokke_: sounds good, thanks20:36
jokke_dhellmann: I'll try to find the time for it in reasonable notice20:36
Rockygbknudson: any chance I can get you to discuss this discussion with jamie lennox?  He's the author of the second.20:37
RockygAnd, jokke_, how about abhishek?20:37
bknudsonwe talked to jamielennox at the summit20:37
Rockygbknudson: yeah.  Just an update , or make sure he's following the ML thread20:38
RockygI'll also ping.  And thanks for the IRC handle20:38
jokke_Rockyg: I'm sure Abhishek is up for it ... I certainly am20:38
RockygCool.  We need to make sure we have some serious devops also in the mix.  Get the design down well, first, before end results start appearing.20:39
RockygOK.  next topic20:39
Rockyg#topic open discussion20:39
*** openstack changes topic to "open discussion (Meeting topic: log_wg)"20:39
Rockyganything to talk about?20:39
Rockygthat is anything else?20:40
bknudsondhellmann: you can add me to the reviews for the logging changes.20:40
RockygI'll get on ops docs when I get back from Boston.  Back on 6/820:40
RockygAnd I'll try to actually summarize the sessions and results within a week or two this time.20:41
dhellmannbknudson: will do; I'm going to try to finish the namespace work before I start those20:41
jokke_Rockyg: drop me e-mail before next weeks meeting if you have some updtates ... I can chair it if we have something that needs attention20:41
Rockygjokke_: ok, thanks20:41
*** tobe has joined #openstack-meeting-420:42
RockygAnything else we need to put on the table, or should we call this a wrap?20:42
jokke_I don't have anything at least ... still trying to sort all my mental notes from the summit20:43
* dhellmann has nothing to raise20:43
jokke_and survive from the jetlag ... this time around seems to be nasty one20:43
Rockygdhellmann, dims_: Also, I wanted to make sure you know that nkrinner is interested in working on oslo stuff20:44
*** slaweq has quit IRC20:45
dhellmannRockyg: great!20:45
dims_Rockyg: nkrinner: welcome!20:45
RockygI got that right, nkrinner?20:45
nkrinneryeah, but i still have not started yet...20:45
RockygThese guys can point you at something you can wrap your brain around to start you.20:45
nkrinneri have some other things to finish first, but i expect to start actively looking at oslo from next week on20:45
RockygCool.  then, it's a wrap20:46
dims_nkrinner: just hop onto #openstack-oslo20:46
nkrinnerdims_: thanks!20:46
Rockyg#endmeeting20:46
*** openstack changes topic to "(Meeting topic: sc)"20:46
openstackMeeting ended Wed May 27 20:46:51 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-05-27-20.02.html20:46
jokke_thanks all20:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-05-27-20.02.txt20:46
*** tobe has quit IRC20:46
nkrinnercu20:46
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-05-27-20.02.log.html20:46
dhellmannnkrinner: also, join us monday for our team meeting: http://eavesdrop.openstack.org/#Oslo%20Team%20Meeting20:46
nkrinnerdhellmann: will do, thanks20:47
Rockygthanks, all!20:47
*** nkrinner has quit IRC20:48
*** Sukhdev has quit IRC20:49
*** barra204 has quit IRC20:50
*** daneyon_ has quit IRC21:00
*** simon-AS5591 has quit IRC21:02
*** sdake has joined #openstack-meeting-421:04
*** sdake_ has quit IRC21:08
*** mestery_ is now known as mestery21:12
*** qwebirc17257 has joined #openstack-meeting-421:12
*** qwebirc17257 has left #openstack-meeting-421:12
*** vinod_ has quit IRC21:16
*** dannywil_ has quit IRC21:27
*** dannywilson has joined #openstack-meeting-421:27
*** banix has joined #openstack-meeting-421:28
*** Bjoern__ has quit IRC21:36
*** daneyon has joined #openstack-meeting-421:51
*** dannywilson has quit IRC21:54
*** dannywilson has joined #openstack-meeting-421:55
*** VW has quit IRC21:56
*** VW has joined #openstack-meeting-421:57
*** VW has quit IRC21:59
*** VW has joined #openstack-meeting-421:59
*** radek__ has quit IRC22:02
*** VW has quit IRC22:04
*** Sukhdev has joined #openstack-meeting-422:04
*** Bjoern__ has joined #openstack-meeting-422:05
*** VW has joined #openstack-meeting-422:06
*** VW has quit IRC22:06
*** bknudson has quit IRC22:06
*** VW has joined #openstack-meeting-422:07
*** klamath has quit IRC22:08
*** rods has quit IRC22:09
*** smeisner has joined #openstack-meeting-422:10
*** VW_ has joined #openstack-meeting-422:11
*** VW has quit IRC22:11
*** Rockyg has quit IRC22:11
*** banix has quit IRC22:16
*** banix has joined #openstack-meeting-422:18
*** tobe has joined #openstack-meeting-422:30
*** dannywil_ has joined #openstack-meeting-422:32
*** tobe has quit IRC22:35
*** dannywilson has quit IRC22:35
*** singlethink has quit IRC22:37
*** salv-orlando has joined #openstack-meeting-422:41
*** VW_ has quit IRC22:41
*** geoffarnold has joined #openstack-meeting-422:47
*** krtaylor has quit IRC22:50
*** geoffarnold has quit IRC22:53
*** dannywil_ has quit IRC22:57
*** Rockyg has joined #openstack-meeting-423:01
*** Gavin_Pratt_HP has joined #openstack-meeting-423:02
*** sarob has joined #openstack-meeting-423:03
*** aventerav has quit IRC23:07
*** sarob_ has joined #openstack-meeting-423:10
*** sarob has quit IRC23:12
*** sarob_ is now known as sarob23:12
*** salv-orlando has quit IRC23:14
*** sdake_ has joined #openstack-meeting-423:16
*** ChuckC has joined #openstack-meeting-423:19
*** sdake has quit IRC23:19
*** Bjoern__ has quit IRC23:31
*** tobe has joined #openstack-meeting-423:31
*** asselin_ has joined #openstack-meeting-423:34
*** tobe has quit IRC23:36
*** eghobo_ has quit IRC23:38
*** dims_ has quit IRC23:38
*** eghobo has joined #openstack-meeting-423:38
*** krtaylor has joined #openstack-meeting-423:39
*** dims_ has joined #openstack-meeting-423:40
*** ajmiller has quit IRC23:42
*** fallenpegasus has quit IRC23:52
*** carl_baldwin has quit IRC23:56

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