Wednesday, 2015-07-01

*** VanL has joined #openstack-meeting-400:01
*** bharath has quit IRC00:03
*** bharath has joined #openstack-meeting-400:03
*** bharath has quit IRC00:03
*** bharath has joined #openstack-meeting-400:04
*** saneax has quit IRC00:09
*** bharath has quit IRC00:09
*** aventerav has quit IRC00:12
*** IlyaG_ has quit IRC00:14
*** DericHorn-HP has joined #openstack-meeting-400:15
*** DericHorn-HP has quit IRC00:16
*** VanL has quit IRC00:17
*** csd has quit IRC00:26
*** sdake has quit IRC00:29
*** dims has joined #openstack-meeting-400:32
*** csd has joined #openstack-meeting-400:33
*** dims_ has joined #openstack-meeting-400:35
*** puranamr has quit IRC00:38
*** dims has quit IRC00:39
*** puranamr has joined #openstack-meeting-400:39
*** geoffarnold has quit IRC00:40
*** Swami has quit IRC00:44
*** IlyaG has joined #openstack-meeting-400:46
*** dannywilson has quit IRC00:55
*** sigmavirus24 is now known as sigmavirus24_awa00:58
*** Rockyg has joined #openstack-meeting-401:03
*** igordcard has quit IRC01:04
*** IlyaG has quit IRC01:09
*** armax has quit IRC01:12
*** IlyaG has joined #openstack-meeting-401:14
*** armax has joined #openstack-meeting-401:18
*** armax has quit IRC01:22
*** dannywilson has joined #openstack-meeting-401:23
*** Rockyg has quit IRC01:28
*** asselin_ has joined #openstack-meeting-401:33
*** IlyaG has quit IRC01:36
*** puranamr has quit IRC01:51
*** sdake has joined #openstack-meeting-401:57
*** sdake_ has joined #openstack-meeting-401:59
*** sballe has quit IRC02:02
*** sdake has quit IRC02:02
*** KunalGan_ has quit IRC02:04
*** KunalGandhi has joined #openstack-meeting-402:04
*** IlyaG has joined #openstack-meeting-402:05
*** yamahata has quit IRC02:05
*** smeisner has quit IRC02:08
*** sdake_ has quit IRC02:10
*** sdake has joined #openstack-meeting-402:10
*** smeisner has joined #openstack-meeting-402:11
*** egon has quit IRC02:15
*** ivar-laz_ has joined #openstack-meeting-402:15
*** ivar-laz_ has quit IRC02:15
*** jckasper has quit IRC02:17
*** ivar-lazzaro has quit IRC02:17
*** sbalukoff has quit IRC02:18
*** egon has joined #openstack-meeting-402:20
*** tobe has joined #openstack-meeting-402:29
*** KunalGandhi has quit IRC02:45
*** fallenpegasus has quit IRC03:03
*** bharath has joined #openstack-meeting-403:05
*** bharath has quit IRC03:10
*** carl_baldwin has joined #openstack-meeting-403:11
*** saneax has joined #openstack-meeting-403:35
*** dims_ has quit IRC04:03
*** KunalGandhi has joined #openstack-meeting-404:05
*** KunalGandhi has quit IRC04:09
*** armax has joined #openstack-meeting-404:10
*** KunalGandhi has joined #openstack-meeting-404:12
*** KunalGandhi has quit IRC04:16
*** dannywilson has quit IRC04:21
*** dannywilson has joined #openstack-meeting-404:21
*** MarkAtwood has joined #openstack-meeting-404:26
*** tobe has quit IRC04:26
*** puranamr has joined #openstack-meeting-404:28
*** nkrinner has joined #openstack-meeting-404:41
*** ajayaa_ has joined #openstack-meeting-404:45
*** carl_baldwin has quit IRC04:50
*** irenab has joined #openstack-meeting-404:54
*** ajayaa_ has quit IRC05:01
*** banix has joined #openstack-meeting-405:06
*** dims has joined #openstack-meeting-405:07
*** fallenpegasus has joined #openstack-meeting-405:09
*** dims has quit IRC05:12
*** tobe has joined #openstack-meeting-405:26
*** banix has quit IRC05:37
*** mmedvede has quit IRC05:40
*** dannywilson has quit IRC05:53
*** puranamr has quit IRC05:53
*** tobe has quit IRC05:59
*** GB21 has joined #openstack-meeting-406:13
*** puranamr has joined #openstack-meeting-406:13
*** spredzy|afk is now known as spredzy06:16
*** puranamr has quit IRC06:18
*** ajayaa_ has joined #openstack-meeting-406:19
*** MarkAtwood has quit IRC06:20
*** irenab has quit IRC06:22
*** numan has joined #openstack-meeting-406:24
*** bharath_ has joined #openstack-meeting-406:26
*** yamahata has joined #openstack-meeting-406:39
*** kobis has joined #openstack-meeting-406:45
*** radek_ has joined #openstack-meeting-406:48
*** radek_ has quit IRC06:52
*** tobe has joined #openstack-meeting-406:53
*** radek_ has joined #openstack-meeting-406:53
*** belmoreira has joined #openstack-meeting-406:54
*** frobware_ has joined #openstack-meeting-407:01
*** sankarshan is now known as sankarshan_away07:09
*** irenab has joined #openstack-meeting-407:09
*** fallenpegasus has quit IRC07:12
*** matrohon has joined #openstack-meeting-407:12
*** akwasnie has joined #openstack-meeting-407:14
*** armax has quit IRC07:18
*** lyarwood has quit IRC07:25
*** lyarwood has joined #openstack-meeting-407:26
*** puranamr has joined #openstack-meeting-407:28
*** puranamr has quit IRC07:33
*** sankarshan_away is now known as sankarshan07:39
*** kobis1 has joined #openstack-meeting-407:51
*** kobis has quit IRC07:51
*** sbalukoff has joined #openstack-meeting-407:53
*** bharath_ has quit IRC07:58
*** bharath_ has joined #openstack-meeting-408:23
*** yamahata has quit IRC08:26
*** bharath_ has quit IRC08:35
*** irenab has quit IRC08:54
*** irenab has joined #openstack-meeting-408:55
*** xingchao_ has joined #openstack-meeting-409:06
*** rods_ has joined #openstack-meeting-409:08
*** dims has joined #openstack-meeting-409:08
*** irenab has quit IRC09:12
*** irenab has joined #openstack-meeting-409:14
*** dims has quit IRC09:14
*** xingchao_ has quit IRC09:21
*** wojdev has joined #openstack-meeting-409:43
*** bradjones has quit IRC09:44
*** sdake has quit IRC09:46
*** bradjones has joined #openstack-meeting-409:46
*** bradjones has quit IRC09:46
*** bradjones has joined #openstack-meeting-409:46
*** wojdev has quit IRC09:46
*** wojdev has joined #openstack-meeting-409:54
*** wojdev has quit IRC09:56
*** wojdev has joined #openstack-meeting-409:57
*** wojdev has quit IRC09:57
*** dims has joined #openstack-meeting-409:59
*** bharath_ has joined #openstack-meeting-410:25
*** bharath_ has quit IRC10:25
*** akwasnie has quit IRC10:41
*** DericHorn-HP has joined #openstack-meeting-410:42
*** GeetikaBatra__ has joined #openstack-meeting-410:54
*** rods_ has quit IRC10:54
*** GB21 has quit IRC10:57
*** GeetikaBatra__ has quit IRC11:06
*** ajayaa_ has quit IRC11:23
*** DericHorn-HP has quit IRC11:25
*** matrohon has quit IRC11:27
*** matrohon has joined #openstack-meeting-411:28
*** ajayaa_ has joined #openstack-meeting-411:39
*** tobe has quit IRC11:46
*** xingchao_ has joined #openstack-meeting-411:51
*** matrohon has quit IRC12:04
*** matrohon has joined #openstack-meeting-412:05
*** saneax has quit IRC12:06
*** lyarwood has quit IRC12:07
*** lyarwood has joined #openstack-meeting-412:07
*** markvoelker has quit IRC12:14
*** markvoelker has joined #openstack-meeting-412:14
*** raginbajin has quit IRC12:18
*** kobis1 has quit IRC12:18
*** raginbajin has joined #openstack-meeting-412:19
*** zigo has quit IRC12:28
*** zigo has joined #openstack-meeting-412:29
*** rfolco has joined #openstack-meeting-412:30
*** fallenpegasus has joined #openstack-meeting-412:36
*** bknudson has joined #openstack-meeting-412:45
*** odyssey4me has joined #openstack-meeting-412:50
*** xingchao_ has quit IRC12:51
*** numan has quit IRC12:52
*** matrohon has quit IRC12:54
*** matrohon has joined #openstack-meeting-412:55
*** singlethink has joined #openstack-meeting-412:59
*** kbyrne has quit IRC13:03
*** klamath has joined #openstack-meeting-413:04
*** klamath has quit IRC13:04
*** klamath has joined #openstack-meeting-413:04
*** kbaikov has joined #openstack-meeting-413:05
*** jasondotstar has joined #openstack-meeting-413:14
*** trey has joined #openstack-meeting-413:14
*** mmedvede has joined #openstack-meeting-413:17
*** jckasper has joined #openstack-meeting-413:18
*** matrohon has quit IRC13:21
*** kbyrne has joined #openstack-meeting-413:22
*** matrohon has joined #openstack-meeting-413:22
*** fallenpegasus has quit IRC13:31
*** irenab has quit IRC13:32
*** trey has quit IRC13:43
*** jwagner_away is now known as jwagner13:50
*** TheIntern has joined #openstack-meeting-413:54
*** TheIntern has left #openstack-meeting-413:54
*** dims has quit IRC13:59
raginbajin#startmeeting operators_ops_tools_monitoring14:00
openstackMeeting started Wed Jul  1 14:00:17 2015 UTC and is due to finish in 60 minutes.  The chair is raginbajin. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: operators_ops_tools_monitoring)"14:00
openstackThe meeting name has been set to 'operators_ops_tools_monitoring'14:00
raginbajinThe link for the last meeting can be found here:14:00
*** adityav has joined #openstack-meeting-414:00
raginbajin#link http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-06-17-14.00.html14:00
*** dims has joined #openstack-meeting-414:00
raginbajin^o Here14:00
*** aventerav has joined #openstack-meeting-414:01
raginbajinAnybody else around for the Operators Ops Tools meeting14:03
raginbajin\o14:05
odyssey4meraginbajin I'm here. o/14:05
*** njohnston_ has joined #openstack-meeting-414:05
*** sballe has joined #openstack-meeting-414:06
raginbajinGreat! Hi there.14:06
odyssey4meIt would seem that perhaps we're the only ones here?14:07
raginbajinI does seem like that.14:08
raginbajinSo, we can officially get started I guess that way we have a record of what happened.14:08
raginbajinNot sure if you had anything to bring up.14:09
raginbajin#topic Recap last Ops Tool Meeting14:10
*** openstack changes topic to "Recap last Ops Tool Meeting (Meeting topic: operators_ops_tools_monitoring)"14:10
odyssey4meI unfortunately haven't managed to do the submission for the openstack-logstash-filters respository yet. I haven't had the time to put it all together - been busy on a focused sprint. I do hope to have it done by the next meeting though.14:10
raginbajinGreat!14:10
raginbajin#info Looks like not many of the action items have been worked on from last meeting.14:11
raginbajinI didn't do a good job of sending out notes from the last meeting.14:11
raginbajinI will be better at it this time around in hopes to get more attendance and involvement.14:11
raginbajin#action Ensure that meeting notes get sent to Operators list - Joe14:12
*** sigmavirus24_awa is now known as sigmavirus2414:12
raginbajin#info Logstash-filters repo has not been submitted. Estimating next meeting for completion.14:14
*** matrohon has quit IRC14:15
*** matrohon has joined #openstack-meeting-414:16
*** jckasper has quit IRC14:17
raginbajinSo it doesn't look like we have much to go over.14:17
GonZo2000hi guys sorry about the delay14:17
raginbajinoh14:17
raginbajinnice timing!14:17
*** malini has joined #openstack-meeting-414:18
raginbajinIt was just me and Odyssey here, and there wasn't much to go over14:18
GonZo2000i was looking at the wiki14:18
GonZo2000and to be honest i dont know where to start14:18
raginbajinso I was about to just end the meeting. I did say that I didn't do a good job to send out meeting notes from the last time. so I will do better this time around.14:19
raginbajin#topic Wiki Discusssion14:19
*** openstack changes topic to "Wiki Discusssion (Meeting topic: operators_ops_tools_monitoring)"14:19
GonZo2000we will improve :)14:19
raginbajin#info Unsure on where to begin on updating the wiki14:19
raginbajinDo you have a link for the wiki?14:19
GonZo2000we have to topics on the wiki14:19
GonZo2000Tools and Monitoring14:20
GonZo2000should we merge them in a single tree and grow from there ?14:20
GonZo2000#link https://wiki.openstack.org/wiki/Operations14:20
raginbajinI think maybe having them separate is a good thing. I'm not too sure.14:22
raginbajinI think each of them can be a really large topic14:22
raginbajin#info Need ideas for Topics to include in each of the Monitoring and Tools sections.14:25
raginbajin#action Team needs to look for ways to break down each Monitoring and Tools sections into topics14:26
*** carl_baldwin has joined #openstack-meeting-414:26
GonZo2000i see as a leaf called Tool/Monitoring14:27
GonZo2000and inside branch to each topic14:27
*** carl_baldwin has quit IRC14:27
*** malini has quit IRC14:28
raginbajinAhh ok.14:28
raginbajinThat makes sense then.14:28
raginbajinI think we should just move forward with that then14:29
GonZo2000ok :)14:29
raginbajinI think monitoring is really going to be the biggest section out of it actually.14:29
GonZo2000tools help monitoring ;)14:30
raginbajinor fix what monitoring found14:30
*** VanL has joined #openstack-meeting-414:30
GonZo2000true :)14:31
raginbajinI guess I was just going through - https://etherpad.openstack.org/p/YVR-ops-tools14:31
raginbajinand looking at what was discussed, and most of it could be summarized into the monitoring topic14:31
raginbajinIt was about logging, metering, and alerting.14:31
raginbajinAny of the tools that were mentioned were about how to do those above there topics or interact with those three topics.14:32
*** malini has joined #openstack-meeting-414:32
GonZo2000lets try for the next meeting come with a structure ok ?14:33
*** igordcard_ has quit IRC14:33
raginbajinI think that's a good plan14:34
*** xingchao_ has joined #openstack-meeting-414:34
raginbajin#action Next meeting work on creating a structure for the wiki14:34
*** VanL_ has joined #openstack-meeting-414:36
raginbajinOk I think that is pretty much all we have.14:36
*** matrohon has quit IRC14:36
*** jwang__ has joined #openstack-meeting-414:37
*** yamahata has joined #openstack-meeting-414:37
raginbajinDoes anyone have anything else?14:38
*** matrohon has joined #openstack-meeting-414:38
odyssey4meNot from me. :)14:38
*** matrohon has quit IRC14:38
*** VanL has quit IRC14:39
*** matrohon has joined #openstack-meeting-414:39
raginbajinAlright. Then I will end of the meeting then14:39
*** serverascode_ has joined #openstack-meeting-414:40
raginbajinThanks everyone came out.14:40
raginbajinwho*14:40
raginbajin#endmeeting14:40
*** openstack changes topic to "Automatic Task Triggering (Meeting topic: glance drivers)"14:40
openstackMeeting ended Wed Jul  1 14:40:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-07-01-14.00.html14:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-07-01-14.00.txt14:40
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-07-01-14.00.log.html14:40
*** devanand1 has joined #openstack-meeting-414:41
*** hemanthm_ has joined #openstack-meeting-414:41
*** harmw_ has joined #openstack-meeting-414:41
*** nikhil_k1away has joined #openstack-meeting-414:42
*** odyssey4me has left #openstack-meeting-414:43
*** EmilienM_ has joined #openstack-meeting-414:45
*** njohnston_ has quit IRC14:46
*** rharwood_ has joined #openstack-meeting-414:46
*** sballe has quit IRC14:46
*** marcusvrn has quit IRC14:46
*** mancdaz has quit IRC14:46
*** andymccr has quit IRC14:46
*** jwang_ has quit IRC14:46
*** EmilienM has quit IRC14:46
*** rharwood has quit IRC14:46
*** ctlaugh_ has quit IRC14:46
*** serverascode has quit IRC14:46
*** devananda has quit IRC14:46
*** flaper87 has quit IRC14:46
*** fungi has quit IRC14:46
*** harmw has quit IRC14:46
*** nikhil_k-away has quit IRC14:46
*** hemanthm has quit IRC14:46
*** rharwood_ is now known as rharwood14:46
*** EmilienM_ is now known as EmilienM14:46
*** kobis has joined #openstack-meeting-414:47
*** nkrinner has quit IRC14:47
*** DericHorn-HP has joined #openstack-meeting-414:48
*** flaper87 has joined #openstack-meeting-414:49
*** flaper87 has quit IRC14:49
*** flaper87 has joined #openstack-meeting-414:49
*** carl_baldwin has joined #openstack-meeting-414:49
*** catherine_d|1 has joined #openstack-meeting-414:49
*** matrohon has quit IRC14:53
*** matrohon has joined #openstack-meeting-414:53
*** TheIntern has joined #openstack-meeting-414:53
*** TheIntern has left #openstack-meeting-414:53
*** marcusvrn has joined #openstack-meeting-414:54
*** ctlaugh_ has joined #openstack-meeting-414:54
*** fungi has joined #openstack-meeting-414:54
*** geoffarnold has joined #openstack-meeting-414:55
*** adityav has quit IRC14:55
*** serverascode_ is now known as serverascode14:56
*** irenab has joined #openstack-meeting-414:57
*** geoffarnold has quit IRC14:57
*** VanL_ has quit IRC14:57
*** hurricanerix has joined #openstack-meeting-414:58
*** dfg_ has joined #openstack-meeting-414:58
*** sballe has joined #openstack-meeting-414:58
*** VanL has joined #openstack-meeting-414:58
*** geoffarnold has joined #openstack-meeting-414:58
*** dwalleck has joined #openstack-meeting-414:58
*** auld has joined #openstack-meeting-414:59
eglute#startmeeting DefCore15:00
openstackMeeting started Wed Jul  1 15:00:55 2015 UTC and is due to finish in 60 minutes.  The chair is eglute. 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: DefCore)"15:00
openstackThe meeting name has been set to 'defcore'15:00
zehicleo/15:01
purpo/15:01
markvoelkero/15:01
*** Sam-I-Am has joined #openstack-meeting-415:01
auld0/15:01
*** vinceb has joined #openstack-meeting-415:01
eglutehello everyone! if you have not done so, raise your hand!15:01
dwallecko/15:01
egluteo/15:01
dfg_o/15:01
vincebo/15:01
catherine_d|1o/15:01
eglute#chair zehicle15:01
* zehicle wonders what 0/0 is15:01
openstackCurrent chairs: eglute zehicle15:01
malinio/15:01
*** devanand1 is now known as devananda15:01
zehicleno more cookies15:01
*** gema has joined #openstack-meeting-415:01
*** saneax has joined #openstack-meeting-415:02
zehiclehogepodge, is on route to airport - should be online shortly15:02
zehiclejust had bfast w/ him.15:02
*** Sam-I-Am has left #openstack-meeting-415:02
* eglute feels left out15:02
*** MarkAtwood has joined #openstack-meeting-415:02
* zehicle feels like it's a good day for Greek salads15:02
purp#link http://www.cnet.com/news/siri-gives-a-little-snark-if-you-ask-her-to-divide-0-by-0/15:02
eglute#topic mid-cycle planning15:03
*** openstack changes topic to "mid-cycle planning (Meeting topic: DefCore)"15:03
eglute#link https://etherpad.openstack.org/p/DefCoreFlag.MidCycle15:03
zehicleeglute, sorry.  was going to offer you to join.  :/15:03
* purp waves at Malini who he hasn't seen in quite a while.15:03
gemao/15:03
zehicleassumed you did not want to make the drive for 8:30 start15:03
egluteIBM is hosting our MidCycle! And getting us lunch!15:03
eglutezehicle: no worries!15:03
malinipurp: I am probably the 'other' malini. we get mistaken :)15:04
purpmalini: Ahhh. Well, I'll wave at you anyway. =]15:04
* markvoelker notes that the nearest hotel to IBM is Aloft, but there are other options closeby as well15:04
egluteif you are attending in person and have dietary restrictions, please fill this out: #link http://doodle.com/gsdq767e7chmc8in15:04
* malini waves back @ purp15:05
eglutethank you markvoelker good to know!15:05
zehiclethe IBM location is not close to the Board Meeting.  if you are going to both, it's much better to stay downtown and drive against traffic15:05
egluteaustin traffic is the worst15:05
markvoelkereglute: So what's the plan?  Show up at the front desk at oh-dark-thirty and ask for Vince? =)15:06
*** andymccr has joined #openstack-meeting-415:06
* purp chuckles at eglute's traffic assertion.15:06
zehiclewe could arrange a carpool (I live near the city) depending on # of people15:06
*** barrett has joined #openstack-meeting-415:06
* zehicle orders redbulls for DefCore all-nighter15:06
eglutemarkvoelker yes! the rest of us will show up there at 9 am or so. actually, we need to decide when we want to start and plan agenda15:06
kbaikovo/15:06
*** ajayaa_ has quit IRC15:07
zehicle#topic agenda for Flag 615:07
*** openstack changes topic to "agenda for Flag 6 (Meeting topic: DefCore)"15:07
*** mancdaz has joined #openstack-meeting-415:07
markvoelker#link https://etherpad.openstack.org/p/DefCoreFlag.MidCycle Agenda ideas15:07
vincebFor the Mid-Cycle, we will need to get the names of all the attendees as I will have to get everyone entered in for our security.15:07
zehicleclearly, we are going to talk about midcycle :) 4 weeks from now15:07
zehicleI'd like to talk about network component & capabilities to see if we can get them for 2015.0715:07
*** jckasper has joined #openstack-meeting-415:07
eglutevinceb: we will work on the list15:08
*** mmedvede has quit IRC15:08
eglute+1 on talking about capabilities and working on agenda for midcycle next meeting15:08
vincebOK, that would be great15:08
zehicleany other changes to the agenda?15:08
zehicle#link https://etherpad.openstack.org/p/DefCoreFlag.615:08
hogepodgeo/15:09
vincebI will work on the logistics and send out an email15:09
catherine_d|1markvoelker: I will confirm on the logistics at IBM ... but usually you will show up at the lobby and ask for Vince ... Vince and I should be at the lobby early15:09
eglutethank you vinceb15:09
*** GB21 has joined #openstack-meeting-415:09
eglutei am ok with agenda zehicle15:10
zehicle#topic midcycle15:10
*** openstack changes topic to "midcycle (Meeting topic: DefCore)"15:10
*** belmoreira has quit IRC15:10
barretto/15:10
markvoelkergreat, thanks folks.  Agenda-wise I don't think anyone but me has added anything to the etherpad yet.15:10
markvoelkerWhile I'm happy to monopolize all the conversation =), maybe let's have an AI for this week for folks to get their ideas posted so we can discuss next time?15:10
zehiclemarkvoelker, I edited late15:11
eglutemarkvoelker same here15:11
*** rockyg has joined #openstack-meeting-415:12
eglutenext topic?15:12
egluteor more on agenda/midcycle?15:12
markvoelker#action Please post midcycle agenda ideas to https://etherpad.openstack.org/p/DefCoreFlag.MidCycle so we can settle agenda soonish15:13
zehiclemidcycle15:13
*** hemanthm_ is now known as hemanthm15:13
eglute#topic midcycle15:13
*** openstack changes topic to "midcycle (Meeting topic: DefCore)"15:13
markvoelkereglute: I think we just covered midcycle. =)  Move on to Tokto summit submissions?15:13
markvoelkers/Tokto/Tokyo/15:14
egluteright now the calendar invite is for 48 hours of midcycle fun. I will send out updated invite when we agree on hours we want to be there15:14
zehicleI think we'll need to set a more time oriented agenda15:14
eglutemarkvoelker yes i am ok15:14
eglutezehicle agreed.15:14
eglutetokyo topic?15:14
zehiclemay be worth having an interactive meeting to work on agenda15:14
zehiclehold on...15:14
egluteok15:14
eglutezehicle i think that is a good idea15:14
*** xingchao_ has quit IRC15:15
zehiclewe could do that as a subgroup and then review15:15
eglute+115:15
vinceb+115:15
rockygo/15:15
*** barrett has quit IRC15:15
zehiclehow many people want to participate in the agenda for the f2f?15:15
markvoelkerzehicle: me15:16
eglute#action eglute zehicle to schedule a subgroup meeting for discussing midcycle agenda15:16
zehicleI think it needs to be tomorrow.15:16
zehiclelikely 10 central or 3 central.15:16
eglutei can do tomorrow15:16
eglute10 AM CST and 3 PM CST tomorrow work for me15:17
vincebVinceb: me15:17
* markvoelker notes that that means you all have about 24 hours to get that last action item done15:17
zehicleok, we need quick vote on 10 or 3.  Please reply15:17
eglute+1 10 AM and 3 PM15:17
vinceb3 CDT works for me15:17
markvoelkerEither should be ok for me15:17
markvoelker3 might be marginally better15:18
zehicleok, that's four people OK at 3.  sold.15:18
eglute#action eglute send out invite for 3 PM Thursday meeting15:18
egluteready for tokyo?15:18
zehiclemarkvoelker, some of that may end up being part of the agenda15:19
hogepodge10 CDT best for me, 3 CDT has a conflict15:19
hogepodgeI can cancel the conflict15:19
eglutehogepodge ok, let us know if you need to find a new time, can do it after the meeting as well15:20
*** barrett has joined #openstack-meeting-415:20
eglute#topic Tokyo summit planning15:20
*** openstack changes topic to "Tokyo summit planning (Meeting topic: DefCore)"15:20
*** VanL has quit IRC15:20
eglutewe have about 2 weeks to submit, has anyone already submitted session proposals about defcore/refstack/interop/related?15:20
markvoelkereglute: not yet but I've been talking with some Nova/Neutron folks about a talk on the networking situation w/respect to interop and DefCore15:21
eglutei was thinking it would be useful to have a DefCore 101 session, if it gets accepted15:21
eglutewhat do you think?15:22
hogepodgeI'll think something15:22
*** VanL has joined #openstack-meeting-415:22
zehiclewhat's the community interest in defcore?  what would they want discussed?15:22
*** armax has joined #openstack-meeting-415:22
catherine_d|1eglute: we have not submitted for Refstack yet ... but planning to at least submit one session about Refstack testing update15:22
hogepodgeWe need to reach a wider community to start getting test results in.15:22
eglutezehicle: this would be for all the people that are hearing about defcore for the first time15:22
zehicleI could see a venn diagram type discussion15:22
zehicleI understand but those are generally not voting for sessions15:23
zehicleso we don't generally get them accepted15:23
zehicleone of the challenges with how we structure the conference15:23
markvoelkerzehicle: a primary area of interest for the community is interop.  Talks on hot interop topics (images, networking, etc) would go over well I think.15:23
eglutecatherine_d|1: can you add it on etherpad: https://etherpad.openstack.org/p/DefCoreFlag.615:23
zehiclethat's what I mean w/ venn as a topic15:24
catherine_d|1eglute: will do15:24
zehiclewe'd want concrete examples15:24
hogepodge"The Interoperabe API"15:24
*** Sukhdev has joined #openstack-meeting-415:24
purp"Interoperable OpenStack Clouds: Just Add DefCore"15:24
zehiclehogepodge, something like Unbreaking the Interoperable API?15:24
zehicleI'd like to be able to discuss the specific cases if possible15:25
purpzehicle: can you give a brief example of a case you'd like to discuss?15:25
zehicleohhh.... "square peg, defcore hole"15:25
hogepodgehttps://etherpad.openstack.org/p/tokyo-defcore-talks15:26
eglutecase study of getting clouds defcore certified?15:26
hogepodgeCollaboration point for talks #link https://etherpad.openstack.org/p/tokyo-defcore-talks15:26
zehiclepurp, we're talking about Glance v2 and the issues it causes.15:26
zehicleit would be good to spend 10 minutes talking why it's an issue and the pros and cons15:26
zehiclethat's real interop meat15:26
purp+115:26
*** IlyaG has quit IRC15:26
zehicleif we have 4 top issues, then we've got a talk15:27
hogepodgeglance v1->v2 and the n+1 ways to run a network are interoperability issues we face right now15:27
auld+1 on interop15:27
zehicleothers?15:27
*** kobis has quit IRC15:28
zehiclewe could review some flags15:28
zehicleand what's causing them to surface15:28
zehicleI know there are some interop issues hiding in the flags15:28
zehiclefrom that perspective, we don't have to lock down 4 now.15:28
zehiclewe can agree that we've got 2 solid and a source for more15:28
zehicleand then craft the topic around that15:29
zehiclemultiple speakers?15:29
rockyga couple of PTLs could make it *very* interesting.  Along with Monty15:29
zehicletrue but I dont want to pull them out of the summit15:29
markvoelkerrockyg: already spoke with Kyle Mestery and Russell Bryant about the networking topic.  May have them co-present.15:30
rockygOps vs Devs  What we have/what we need for interop15:30
zehiclethe events are so overlapped we need to be careful of their time15:30
*** kobis has joined #openstack-meeting-415:30
zehiclealso, I would not expect to drive the discussion at the session - it's not the best forum15:30
zehiclewe need to have a hook to get people to vote AND also keep topical for n00bs15:31
eglute+1 zehicle15:31
*** lyarwood has quit IRC15:32
zehiclethen again, we could just throw out "DEFCORE IS BROKEN AND ITS ALL YOUR FAULT!"15:32
eglute+10015:32
purpHeh.15:32
hogepodge"You'll never believe this one weird trick you can do with defcore"15:32
eglutelol15:32
zehiclepolishing my blame-caster15:33
* eglute thinks defcore should have own summit track15:33
*** lyarwood has joined #openstack-meeting-415:33
* eglute interop summit track would be awesome15:33
rockygThe defcore dunking booth  -- then have a devops throw questions at nova/neutron/glance experts15:33
* markvoelker notes that it's 33 past the hour so maybe time to move on....15:33
*** banix has joined #openstack-meeting-415:33
zehicle+1 markvoelker15:33
zehicleI think we've got something good enough to run15:34
rockygActually, Game show.  How do you do "x" across a couuple of public cloud providers and let the devs answer15:34
*** mmedvede has joined #openstack-meeting-415:34
zehicle#action eglute and zehicle to draft topic and submit15:34
zehicle+1 on resubmitting the game show concept15:34
eglute+1 game15:35
eglutetime to talk about capabilities?15:35
zehicle#topic 2015.07 capabilities15:35
*** openstack changes topic to "2015.07 capabilities (Meeting topic: DefCore)"15:35
zehiclewe do need the board to approach an updated guideline based on the subcaps15:35
zehicleI'd also like us to get 2015.04 off the books because of all the flags15:36
hogepodgereorganization or subcaps, should be pretty straight forward. We have flags that will cause rebase issue, but not a big deal15:36
zehicleboth really15:36
markvoelker2015.05 has msot of the same flags though.  Minus about two I think.15:36
markvoelkerOr will have once we finish patching.15:36
zehicleah, ok.  sigh15:37
* zehicle takes that as a sign that we made good decisions quickly in 2015.0415:37
markvoelkerThe trouble with a new spec every month is that there's no time to get much fixed between specs.  Next spec we'll have a much longer cycle.15:37
markvoelkerSpeaking of....15:38
markvoelkerzehicle: this actually isn't 2015.07 we're working on next, right?  It's 2016.01?  We name Guidelines based on when they're approved by the Board15:38
markvoelker(per D4 in 2015A)15:38
zehiclemarkvoelker, the pace is hard if we make major changes.  so far it's been very incremental15:38
hogepodgemarkvoelker: if we merged glance v1 flagging without discussion I will be unhappy. It's a fairly serious issue. v2 is not interoperable, and I firmly believe that the majority of installations out there depend on v115:38
catherine_d|1zehicle: no vendor will pass the spec without some flagged tests (at the minimum those that are flagged because of Tempest bugs)15:38
zehicleat the last meeting, we said there would be a new one to approach15:38
zehicle+1 on some flags15:39
markvoelkerhogepodge: Sure, but we've been discussing that quite a lot I think15:39
zehiclethe idea was that we would have a process for flags worked out before we put them back in15:39
*** jasondotstar has quit IRC15:39
zehicleboard should approve 1) new capabilities groups 2) new schema15:39
zehiclesmall changes but would like to keep that in flow15:40
zehiclemore importantly, I'd like to start the process of getting a NETWORKING component going15:40
zehicleso, we'd need tests -> capabilities for that.  at least 115:40
*** VanL has quit IRC15:40
markvoelkerzehicle: see item in today's agenda. =)15:41
zehiclewe need to component in place so we can think about having it in the platform (or not having it)15:41
zehicleyy15:41
markvoelker:Figuring out Networking (and other important areas of overlap):15:41
zehiclethey are conflated15:41
zehiclesince we have to figure out a window for the guideline changes15:41
zehiclehappy to hold the details until next15:41
markvoelkerzehicle: where networking is concerned, I think we just need to put a patch up and score capabilities15:41
markvoelkerWe haven't actually done that yet15:41
zehiclebut wanted to make sure that we understood the timing to get it into a guideline15:42
hogepodgemarkvoelker: yes, I guess I'd like to see us and the community working towards a decision on that. Some of the comments about "no devs so no v2 proxy in nova" and "it's a glance problem not a nova problem" make me think that there is no effort to make v2 a serious api, unlike what we've seen in cinder and keystone.15:42
markvoelkerIt may very well turn out that nothing meets DefCore Criteria, but if we do the scoring then we'll know where things are falling short, what's closest, and what has to be done to get something over the bar15:42
eglute+1 on scoring networking15:42
hogepodgenetworking we can score and start putting forward as advisory. Also need to decide if we want to try and use the nova proxy and dump nova-net and go all in on neutron.15:43
markvoelkerzehicle: I've already been talking with some folks from nova/neutron about potentially scorable things, so I'm happy to take a stab at something we can score15:43
zehiclemarkvoelker, I'd like to get something there15:43
zehicleso we can start the process going on it15:43
eglutewho can help with scoring networking? we need to get networking as Advisory before the next board meeting15:43
rockyghogepodge, +1000  I agree.  And rumor has it it's Ooh, shiny vs.  the drudgery of making old stuff actually work15:43
hogepodgemarkvoelker: I'm glad you're engaging them on this. Can we get either of them to the midcycle?15:43
zehiclewe should have something in to start the discussion  (works like a motion in Roberts' rules)15:44
*** singlethink has quit IRC15:44
catherine_d|1markvoelker: I can provide test data ...15:44
markvoelkerhogepodge: seems unlikely this late in the game.  I can ask.  John already said he couldn't hop across the poond.15:44
hogepodgemarkvoelker: virtual attendance then?15:44
zehicleat best, we'd have it as advisory for 2015.0715:44
markvoelkerhogepodge: More likley.15:44
hogepodgeAt least for targeted discussions. If there's a good time that works with their schedule we can identify it so they're not up at 2 AM :-D15:45
zehiclethat would then help drive deeper discussion in Tokyo15:45
catherine_d|1zehicle: 2015.07 is targeted for Liberty OpenStack release?15:45
zehicleno15:46
markvoelkerzehicle: catherine_dl1: per 2015A it should go up for approval in January and cover L, K, J15:46
zehiclemarkvoelker, +1.  L is not out until Tokyo15:46
markvoelkerSee timeline at bottom of today's etherpad15:46
zehicleso, 2016.01 would have L15:46
markvoelkerzehicle: wait, what?15:47
zehicleideally, we don't have a 2015.10 BUT I suspect that we will need it15:47
markvoelker2015A says we introduce a draft at the summit, and it gets approved 3 months later15:47
zehicleright - that means that 2015.next would be presented at the summit15:47
rockygright.  2016-115:47
markvoelkerzehicle: ok, gotcha15:47
zehiclewith a target of approval the the BoD mid cycle15:47
zehicleBUT, I'd expect us to recommend a 2015.10 guideline15:48
*** ajayaa_ has joined #openstack-meeting-415:48
markvoelkerzehicle: I'd be -1 on doing a 2015.10 guideline.  CAn't think why we would need it.  Iterating on specs that rapidly doens't foster interoperability.15:48
zehicleotherwise, any network changes will not surface as ADVISORY until 2016.01 and take 6 more months15:48
markvoelkerE.g. we have folks certified aginast a while smattering of different Guidelines b/c we keep introducing new ones.15:49
zehiclegood topic for the midcycle15:49
zehiclemarkvoelker, there are pros and cons15:49
markvoelkerzehicle: personally I think it's unlikely that we'll have networking included in 2016.01 unless we change DefCore Criteria.15:49
zehicleI agree we should not rush but we also need to respond as we discover issues right now15:49
markvoelkerSo I'm not real worried about making it advisory before then.15:50
hogepodgemarkvoelker: zehicle: I see us in a period of growing pains right now. If we do the right thing we should see much more stability a year from now.15:50
zehiclemarkvoelker, it's possible to consider it as a component (not platform)15:50
zehiclethe original criteria did not anticipate having components15:50
markvoelkerEven if we consider it as a Component, the Criteria still apply though15:50
zehiclewe may have to revise that to take components into account15:50
*** jasondotstar has joined #openstack-meeting-415:50
rockygI don't see it being more than a few tests/ basic capabilities for a while15:50
*** barrett has quit IRC15:51
zehiclemarkvoelker, yes!  but "widely adopted" has a different meaning15:51
zehiclewhich is unfortunately very tricky to handle15:51
rockygI can't see it being a platform for  quite a while15:51
zehiclewhen we switch from components to platform15:51
* eglute notes we have only 9 min left15:51
zehiclethis was the discussion that I wanted to drive for this meeting15:51
zehicleso I'm good w/ that15:52
markvoelkerzehicle: let's table this for midcycle.  I don't see any other alternative meanings for the criteria we have approved.15:52
zehiclestill wondering if we have time to get some networking caps in15:52
markvoelkerI think it probably warrants more discussion than 9 minutes will afford. =)15:52
zehiclemarkvoelker, I hope that you are right because we put a lot of time into that15:52
rockygNeeds to be from a tenant perspective to get network in soonish15:52
*** dannywilson has joined #openstack-meeting-415:52
*** ivar-lazzaro has joined #openstack-meeting-415:53
zehicleand that's why these topics are mixed with faster guideline cycles15:53
eglutewe always run out of time to talk about capability scoring. Looks like we might need a separate meeting for that15:53
hogepodgeeglute: +115:53
rockygeglute, ++15:53
*** ivar-lazzaro has quit IRC15:53
*** jwagner is now known as jwagner_away15:53
*** VanL has joined #openstack-meeting-415:53
markvoelkereglute: tend to agree.  See "capabilities review (or planning for it)" in today's agenda15:53
*** jwagner_away is now known as jwagner15:53
hogepodgeI'd like us to schedule a weekly capabilities meeting.15:54
rockyghogepodge, ++15:54
eglutehogepodge agree15:54
markvoelkerhogepodge: I think at this stage an hour per week isn't enough, even if it's a separate meeting15:54
*** ivar-lazzaro has joined #openstack-meeting-415:54
markvoelkerWe need to divide and conquor15:54
markvoelker(see etherpad)15:54
hogepodgeI'd also nominate markvoelker to lead it (VanL did a fantastic job, but seems occupied with other concerns lately)15:54
rockygLink to etherpad, again?15:54
markvoelkerrockyg: https://etherpad.openstack.org/p/DefCoreFlag.615:54
eglutewe need an owner for capabilites scoring. VanL used to own it, not sure if has the time this quarter15:55
zehiclehogepodge, +115:55
*** barrett has joined #openstack-meeting-415:55
markvoelkereglute: hogepodge: perhaps let's confirm with VanL before we shift that responsibility?15:55
VanLThe timing of the meetings has hit at weird times for me since Vancover, apologies, all15:55
rockygmarkvoelker, thanks15:55
* hogepodge hopes markvoelker isn't bothered by him nominating him for hard job15:55
VanLI'm fine with markvoelker15:55
zehiclehogepodge, as also have authority as DefCore secretary to run that15:55
hogepodgeohai VanL!15:55
* hogepodge waves15:55
hogepodgeI'm happy to do that15:56
rockygso, VanL, if you'll run it, you get to pick the time!15:56
*** fallenpegasus has joined #openstack-meeting-415:56
hogepodgemarkvoelker: would two hours work? If we're short on time, nothing may chage that we can't do as much as we want, but that's a nice thing about targeting advisory15:56
* markvoelker is happy to take on whatever level of responsibility will get things done15:56
*** irenab has quit IRC15:57
hogepodgeVanL: your thoughts?15:57
markvoelkerhogepodge: well, my point was that I don't think we need to do all the scoring in a meeting15:57
VanLSo, scoring should take less time15:57
markvoelkerInstead, we need to divvy up scoring and submit patches that we can review *outside* of meetings, then use meeting time for contentious ones15:57
VanLand should be a lot easier than the first go-around.15:57
zehiclewe need to get coverage for the meeting next week15:58
hogepodgemarkvoelker: ok, is it something we can do in parallel? Have someone propose a todo list then collate responses? VanL had an idea of how to programatically (sp) score15:58
* markvoelker sounds two minute warning15:58
zehicle#topic chair for next meeting15:58
*** openstack changes topic to "chair for next meeting (Meeting topic: DefCore)"15:58
VanLThe capabilities meetings over time tended to morph because we needed first to define what the capabilities were/are15:58
markvoelkerhogepodge: sure, I'll send an ML message about it this week15:58
VanLI think that seems to be largely settled at this point w/ the new capabilities15:58
egluteIt will be 3 AM for me during the next meeting, I nominate hogepodge and markvoelker to chair next week's meeting15:58
hogepodgesince mordred and jeblair are big consumers of network api, I'd like their input.15:59
markvoelkerand VanL: I'll drop you a note about ideas for improving scoring.  I'm sure that's something you've thought a lot about, would love to pick your brain a bit.15:59
*** irenab has joined #openstack-meeting-415:59
hogepodgeI'm available and can (co)chair with markvoelker15:59
markvoelkerI'll be here as well15:59
eglutethank you hogepodge15:59
zehiclethanks15:59
eglutethank you markvoelker15:59
* purp nudges on https://review.openstack.org/#/c/188661/ to get it landed15:59
VanLmarkvoelker: Yes, let's grab some time. This week would be better, I have some ETO coming up15:59
markvoelkerVAnL: will do.  I think I'm relatively free tomorrow, so I'll verify and send you a note16:00
hogepodgemarkvoelker: VanL can you include me? I'm scheduled up tomorrow, but would like to join if I can (even if just to listen)16:00
markvoelkerhogepodge: sure16:00
*** armax has quit IRC16:00
markvoelkerok, think we're overtime folks16:01
eglutewe are out of time. any last minute comments or remarks?16:01
zehicleI can't +2 that - it's mine16:01
zehiclethanks for the nudge purp16:01
egluteI can if everyone else reviewed it16:01
purpContinue in #openstack-defcore16:02
* markvoelker will take a look16:02
eglute+1 if you reviewed it and are ok with it16:02
VanLmarkvoelker/hogpodge: I'm free except 10:30-11 and 1-2 (both central)16:02
* markvoelker jots down VanL's schedule16:02
eglute#action everyone reviews https://review.openstack.org/#/c/188661/16:02
hogepodgepurp I have some issues with language and clarity (see last comment)16:02
catherine_d|1VanL: hogepodge: markvoelker: please include me ... have some note about the spread sheet we created earlier16:02
eglute#action eglute will merge https://review.openstack.org/#/c/188661/ after all reviews are in16:02
markvoelkercatherine_dl1: will do16:03
zehicle#endmeeting16:03
*** openstack changes topic to "Automatic Task Triggering (Meeting topic: glance drivers)"16:03
openstackMeeting ended Wed Jul  1 16:03:13 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-07-01-15.00.html16:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-07-01-15.00.txt16:03
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-07-01-15.00.log.html16:03
purphogepodge: Agree. Bringing that up in #openstack-defcore.16:03
*** vinceb has quit IRC16:04
*** singlethink has joined #openstack-meeting-416:05
*** dwalleck has quit IRC16:06
*** asselin_ has quit IRC16:07
*** dwalleck has joined #openstack-meeting-416:07
*** dwalleck has quit IRC16:09
*** lyarwood has quit IRC16:09
*** lyarwood has joined #openstack-meeting-416:09
*** jwagner is now known as jwagner_away16:11
*** fallenpegasus has quit IRC16:11
*** dwalleck has joined #openstack-meeting-416:11
*** sankarshan is now known as sankarshan_away16:14
*** puranamr has joined #openstack-meeting-416:14
*** DericHorn-HP has quit IRC16:15
*** irenab has quit IRC16:16
*** dwalleck has quit IRC16:16
*** DericHorn-HP has joined #openstack-meeting-416:17
*** ajayaa_ has quit IRC16:22
*** ajayaa has joined #openstack-meeting-416:22
*** sdake has joined #openstack-meeting-416:24
*** irenab has joined #openstack-meeting-416:25
*** fallenpegasus has joined #openstack-meeting-416:26
*** matrohon has quit IRC16:27
*** barrett has left #openstack-meeting-416:27
*** sarob_ has joined #openstack-meeting-416:31
*** jwagner_away is now known as jwagner16:32
*** irenab has quit IRC16:32
*** sarob_ has quit IRC16:33
*** malini has quit IRC16:35
*** geoffarnold has quit IRC16:35
*** Swami has joined #openstack-meeting-416:36
*** jckasper has quit IRC16:41
*** tsbot_ has joined #openstack-meeting-416:42
*** geoffarnold has joined #openstack-meeting-416:44
*** GB21 has quit IRC16:47
*** GB21 has joined #openstack-meeting-416:49
*** armax has joined #openstack-meeting-416:52
*** singleth_ has joined #openstack-meeting-416:53
*** belmoreira has joined #openstack-meeting-416:55
*** sbalukoff has quit IRC16:56
*** singlethink has quit IRC16:57
*** VanL has quit IRC17:01
*** lyarwood has quit IRC17:02
*** lyarwood has joined #openstack-meeting-417:02
*** sigmavirus24 is now known as sigmavirus24_awa17:04
*** saneax has quit IRC17:07
*** yamahata has quit IRC17:07
*** xicheng has joined #openstack-meeting-417:11
*** geoffarnold has quit IRC17:13
*** geoffarnold has joined #openstack-meeting-417:14
*** IlyaG has joined #openstack-meeting-417:15
*** SumitNaiksatam has joined #openstack-meeting-417:16
*** wshao has joined #openstack-meeting-417:16
wshao#startmeeting Compass dev17:17
openstackMeeting started Wed Jul  1 17:17:35 2015 UTC and is due to finish in 60 minutes.  The chair is wshao. Information about MeetBot at http://wiki.debian.org/MeetBot.17:17
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:17
*** openstack changes topic to " (Meeting topic: Compass dev)"17:17
openstackThe meeting name has been set to 'compass_dev'17:17
xichengLooks good.17:18
*** malini has joined #openstack-meeting-417:18
wshaoa roll call by #info command17:18
*** malini has quit IRC17:18
*** malini has joined #openstack-meeting-417:18
xicheng#info17:18
xicheng?17:18
wshaowith your name.17:18
*** sdake_ has joined #openstack-meeting-417:18
wshaoas an argument17:18
xicheng#info xicheng17:19
xichengwith or without "#"?17:19
wshaowith17:19
rockygroll call is simply o/17:19
xichengo/17:19
wshaook cool. rocky17:19
xichengo/ xicheng17:19
rockygall people who type during meeting will be recorded as present17:19
rockyggotta go  appt17:20
wshaoThe first topic will be the release schedule. We need to formalize it as we plan to enter openstack program17:20
*** rockyg has quit IRC17:20
xichengare we allowed to type?17:20
*** xiaodongwang has joined #openstack-meeting-417:21
xiaodongwanghello17:21
xichenghello17:21
*** sdake has quit IRC17:21
*** catherine_d|1 has quit IRC17:23
wshao#topic Compass release schedule17:23
*** SumitNaiksatam has quit IRC17:23
*** openstack changes topic to "Compass release schedule (Meeting topic: Compass dev)"17:23
*** SumitNaiksatam has joined #openstack-meeting-417:23
wshaooption 1 is to follow openstack's 6-month.17:23
*** kobis has quit IRC17:24
*** dannywilson has quit IRC17:24
*** Sukhdev has quit IRC17:24
*** ajmiller_ has joined #openstack-meeting-417:25
*** Sukhdev has joined #openstack-meeting-417:25
*** irenab has joined #openstack-meeting-417:25
*** malini has quit IRC17:26
*** trey has joined #openstack-meeting-417:26
*** wshao has quit IRC17:26
*** wshao has joined #openstack-meeting-417:27
*** malini has joined #openstack-meeting-417:28
*** xicheng has quit IRC17:29
*** IlyaG has quit IRC17:30
wshaodefer the rest of agenda to next week17:31
wshao#endmeeting17:31
*** openstack changes topic to "Automatic Task Triggering (Meeting topic: glance drivers)"17:31
openstackMeeting ended Wed Jul  1 17:31:56 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/compass_dev/2015/compass_dev.2015-07-01-17.17.html17:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/compass_dev/2015/compass_dev.2015-07-01-17.17.txt17:31
openstackLog:            http://eavesdrop.openstack.org/meetings/compass_dev/2015/compass_dev.2015-07-01-17.17.log.html17:32
*** rods_ has joined #openstack-meeting-417:32
*** harmw_ is now known as harmw17:32
*** lyarwood has quit IRC17:33
*** lyarwood has joined #openstack-meeting-417:33
*** jckasper has joined #openstack-meeting-417:36
*** trey has quit IRC17:37
*** armax has quit IRC17:37
*** VanL has joined #openstack-meeting-417:37
*** belmoreira has quit IRC17:38
*** Grace has joined #openstack-meeting-417:38
*** VanL_ has joined #openstack-meeting-417:38
*** trey has joined #openstack-meeting-417:39
*** sdake_ is now known as sdake17:39
*** VanL has quit IRC17:42
*** marcusvrn1 has joined #openstack-meeting-417:43
*** armax has joined #openstack-meeting-417:43
*** lyarwood has quit IRC17:44
*** lyarwood has joined #openstack-meeting-417:44
*** malini has quit IRC17:44
*** sdake has quit IRC17:44
*** singlethink has joined #openstack-meeting-417:45
*** malini has joined #openstack-meeting-417:46
*** malini has quit IRC17:46
*** malini has joined #openstack-meeting-417:46
*** mestery_ has joined #openstack-meeting-417:46
*** malini has left #openstack-meeting-417:46
*** sdake has joined #openstack-meeting-417:46
*** marcusvrn has quit IRC17:46
*** singlet__ has joined #openstack-meeting-417:48
*** singleth_ has quit IRC17:48
*** sdake has quit IRC17:48
*** mestery has quit IRC17:49
*** sdake has joined #openstack-meeting-417:49
*** lyarwood has quit IRC17:50
*** singlethink has quit IRC17:51
*** frobware_ has quit IRC17:52
*** lyarwood has joined #openstack-meeting-417:52
*** SumitNaiksatam has quit IRC17:52
*** DericHorn-HP has quit IRC17:55
*** wshao has quit IRC17:55
*** IlyaG has joined #openstack-meeting-417:58
*** puranamr has quit IRC17:59
*** ivar-lazzaro has quit IRC17:59
*** DericHorn-HP has joined #openstack-meeting-418:03
*** mestery_ is now known as mestery18:04
*** delatte has quit IRC18:04
*** cdelatte has joined #openstack-meeting-418:05
*** cdelatte has quit IRC18:06
*** cdelatte has joined #openstack-meeting-418:06
*** sigmavirus24_awa is now known as sigmavirus2418:06
*** auld1 has joined #openstack-meeting-418:08
*** auld has quit IRC18:09
*** igordcard_ has joined #openstack-meeting-418:10
*** ajmiller_ has quit IRC18:12
*** MarkAtwood has quit IRC18:14
*** fallenpegasus has quit IRC18:16
*** padkrish has joined #openstack-meeting-418:18
*** Sukhdev has quit IRC18:19
*** puranamr has joined #openstack-meeting-418:21
*** puranamr has quit IRC18:21
*** s3wong has joined #openstack-meeting-418:21
*** GB21 has quit IRC18:22
*** rods_ has quit IRC18:24
*** puranamr has joined #openstack-meeting-418:24
*** puranamr has quit IRC18:24
*** s3wong has quit IRC18:25
*** ivar-lazzaro has joined #openstack-meeting-418:27
*** vishwanathj has joined #openstack-meeting-418:30
*** dannywilson has joined #openstack-meeting-418:33
*** hurricanerix has left #openstack-meeting-418:34
*** irenab has quit IRC18:38
*** sdake has quit IRC18:38
*** sdake has joined #openstack-meeting-418:38
*** sbalukoff has joined #openstack-meeting-418:40
*** sdake_ has joined #openstack-meeting-418:41
*** Rockyg has joined #openstack-meeting-418:41
*** fallenpegasus has joined #openstack-meeting-418:42
*** sdake has quit IRC18:44
*** Sukhdev has joined #openstack-meeting-418:44
*** SumitNaiksatam has joined #openstack-meeting-418:48
*** bradjones has quit IRC18:51
*** bradjones has joined #openstack-meeting-418:52
*** bradjones has quit IRC18:52
*** bradjones has joined #openstack-meeting-418:52
*** irenab has joined #openstack-meeting-419:01
*** puranamr has joined #openstack-meeting-419:08
*** fallenpegasus has quit IRC19:10
*** DericHorn-HP has quit IRC19:11
*** ajmiller_ has joined #openstack-meeting-419:13
*** singlethink has joined #openstack-meeting-419:15
*** ajmiller has quit IRC19:16
*** singlet__ has quit IRC19:18
*** padkrish has quit IRC19:19
*** padkrish has joined #openstack-meeting-419:20
*** sdake has joined #openstack-meeting-419:21
*** sdake has quit IRC19:23
*** padkrish_ has joined #openstack-meeting-419:23
*** sdake has joined #openstack-meeting-419:23
*** DericHorn-HP has joined #openstack-meeting-419:24
*** padkrish has quit IRC19:24
*** ivar-lazzaro has quit IRC19:25
*** sdake_ has quit IRC19:25
*** IlyaG has quit IRC19:28
*** padkrish_ has quit IRC19:31
*** lyarwood has quit IRC19:31
*** lyarwood has joined #openstack-meeting-419:33
*** armax has quit IRC19:34
*** Rockyg has quit IRC19:35
*** singlethink has quit IRC19:35
*** jasondotstar has quit IRC19:37
*** lyarwood has quit IRC19:38
*** lyarwood_ has joined #openstack-meeting-419:38
*** nkrinner has joined #openstack-meeting-419:40
*** armax has joined #openstack-meeting-419:42
*** vishwana_ has joined #openstack-meeting-419:45
*** vishwanathj has quit IRC19:47
*** Rockyg has joined #openstack-meeting-419:52
Rockygo/19:53
dhellmanno/19:55
*** yamahata has joined #openstack-meeting-419:55
*** singlethink has joined #openstack-meeting-419:56
*** Swami has quit IRC19:57
*** ajayaa has quit IRC19:59
Rockyg#starmeeting log_wg20:01
dhellmannRockyg: missed a T in there :-)20:01
RockygThanks.  Was trying to figure out what I did worng :P20:01
Rockyg#startmeeting log_wg20:01
openstackMeeting started Wed Jul  1 20:01: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:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: log_wg)"20:01
openstackThe meeting name has been set to 'log_wg'20:01
Rockygpings:  jokke_, bknudson20:02
Rockygand who am I forgetting?  Gotta build a list.20:02
bknudsonhi20:03
Rockyghey there!20:03
RockygSo, the new meeting stuff is very non-dev unfriendly.20:04
bknudsonnew meeting stuff?20:04
*** DericHorn-HP has quit IRC20:04
dhellmann?20:04
RockygYeah.  On the ML, there was discussion on app agnostic log parameters.20:05
RockygWasn't aware of the BP, but something we should track/comment/provide resources if possible?20:05
dhellmann#link http://lists.openstack.org/pipermail/openstack-dev/2015-June/067970.html20:05
dhellmann#link https://blueprints.launchpad.net/oslo.log/+spec/app-agnostic-logging-parameters20:05
RockygThanks dhellmann!20:05
Rockyg#topic app agnostic logging20:06
*** openstack changes topic to "app agnostic logging (Meeting topic: log_wg)"20:06
bknudsonlog file formats always seem to be a pain20:06
bknudsonprobably just a bad design20:06
dhellmannthis spec is somewhat related, as well: https://review.openstack.org/19675220:07
Rockyg#link https://review.openstack.org/19675220:07
dhellmannI haven't started work on any of those, yet, but do expect to "soon" when I make a little progress on the release and python 3 work I have on my backlog.20:08
*** DericHorn-HP has joined #openstack-meeting-420:08
Rockygany way we can help?20:08
dhellmannit would be useful to know which projects are not already using the oslo.context and oslo.log libraries20:09
RockygI can likely get that info.20:09
Rockygother than swift, of course ;-)20:09
bknudsonkeystone isn't using oslo.context20:10
dhellmannwe can use https://etherpad.openstack.org/p/liberty-app-agnostic-logging-parameters for notes20:10
Rockyg#action document which projects using 1) oslo.log libraries 2) oslo.context20:10
*** belmoreira has joined #openstack-meeting-420:11
RockygAnother question I have wrt: does the mistral approach seem reasonable?20:11
dhellmannwhat is their approach?20:11
*** daneyon has joined #openstack-meeting-420:11
Rockyg#link https://blueprints.launchpad.net/mistral/+spec/mistral-log-enhancement20:12
Rockygposted in ML yesterday.  I guess it should have also had [log] in the title20:13
*** VanL_ has quit IRC20:14
Rockygspec #link https://review.openstack.org/#/c/173700/20:14
RockygSorry.  Wrong link.20:14
Rockyglemme find the email link.20:15
dhellmannI haven't read the whole patch on that blueprint, but the first few changes look right20:15
bknudsonlooks like they were still using log from oslo-incubator20:15
*** belmoreira has quit IRC20:15
dhellmannyeah20:15
bknudsonmakes you wonder how far behind they are in switch to oslo libs20:16
dhellmannmy guess is pretty far20:16
Rockyg#link http://lists.openstack.org/pipermail/openstack-dev/2015-June/068314.html20:16
bknudsonhttp://git.openstack.org/cgit/openstack/mistral/tree/mistral -- maybe not20:16
bknudsonI don't see any openstack in there20:17
RockygI can find out.  The dev working this stuff works for Huawei and I've actually got a connection20:17
dhellmannoh, I think someone working on this asked me about it on irc a few days ago20:17
dhellmannthey were looking for a way to include more information in the logging context by default, like the task ids they have in mistral20:18
RockygYeah.  They just added a new core.  Seems activity is picking up.20:18
Rockygdhellmann: exactly.20:18
RockygThat's the plan laid out in the above email20:18
dhellmannoh, no, that was email: http://lists.openstack.org/pipermail/openstack-dev/2015-June/068089.html20:19
RockygOh.  oops.20:19
* dhellmann has too many digital interactions to remember the medium any more20:19
RockygOh, right.  The email I posted was the proposal based on your responses.20:19
dhellmannyeah, it was all running together in my head20:20
RockygIt's written like a spec.  Take a look.20:20
Rockygdhellmann: just consider me your secretary wrt logging ;-)20:20
dhellmannI'll have to find that email and reply. I'm not sure overloading resource like that is the right approach, but I don't know what mistral has as an addressable resource20:21
bknudsondo we just set extra=context?20:22
Rockyghttp://lists.openstack.org/pipermail/openstack-dev/2015-June/068314.html20:22
*** VanL has joined #openstack-meeting-420:22
dhellmannbknudson: the keyword adapter in oslo.log pulls any extra keyword args and adds them to extras, so either form works20:22
*** ajmiller_ is now known as ajmiller20:22
Rockygsorry.  wrong link again.  try : http://lists.openstack.org/pipermail/openstack-dev/2015-June/068314.html20:23
dhellmannRockyg: I'll find that message in my email client and reply later today or early tomorrow20:24
bknudsonfound it http://git.openstack.org/cgit/openstack/oslo.log/tree/oslo_log/log.py#n10520:24
RockygCool.  Thanks.  that will give me the info I need.20:24
Rockygready for next topic?20:24
dhellmann++20:25
Rockyg#topic requestID20:25
*** openstack changes topic to "requestID (Meeting topic: log_wg)"20:25
RockygIt's been getting lots of play in xproject.20:25
Rockyg#link https://review.openstack.org/#/c/156508/20:26
Rockygtalks about using tuples, modifying all clients then all projects.  Hmmm.20:26
RockygWill it work?20:27
dhellmannthey've dropped that approach, and I think the new version is workable20:27
*** banix has quit IRC20:27
dhellmannthere are some details to work out, as bknudson points out in the review20:27
bknudsonI doubt it will work in all cases20:27
RockygI'm worried about the same thing the ops guys are worried about:  too many UUIDs and the log messages get too long.20:27
bknudsonin the simplest case looks like it'll be adequate20:28
Rockygdhellmann: oh, good.20:28
RockygSimple case is a good start if it doesn't make the hard case impossible20:28
bknudsonall the new version does is make the request ID available20:28
*** marcusvrn1 has quit IRC20:28
bknudsonit doesn't cover actually logging the value20:28
dhellmannright, that was part 120:28
Rockygbknudson: kewl!20:28
RockygI was catching up on all the comments and missed that the logging part was out.20:30
RockygI think for logging, it could be done with 3 UUIDs: originating, last referring, current20:31
RockygLinked list kinda, with originating being the "reference" id20:32
bknudsonwhat are we logging/20:32
bknudson?20:32
Rockygrequest IDs20:32
dhellmannthis is why I want to see what the osprofiler folks have, because they've figured out how to build the call tree properly so it seems there's no need to redo that work20:32
bknudsonso when the request is complete log the request IDs?20:32
*** padkrish has joined #openstack-meeting-420:32
bknudsonor when the request is made?20:33
RockygAs long as it gets pulled out of the profiler and put into an oslo library or some such.  Ops are unlikely to install the profiler on prod20:33
bknudsonor is it when the request comes in?20:33
dhellmannRockyg: yeah, don't obsess over where that lives. The point is to look at their implementation.20:33
RockygYah.20:33
Rockygbknudson: first action taken to complete the "task" would have get the originating RId20:34
RockygThen each handoff to another project/module gets one (depends on how the project implements internally)20:34
RockygSo, the hand-off passes the original RId and the previous step's RId20:35
RockygI would think the first RId would be created when the call is moved to actionable code/put on a waiting queue.  It needs to be associated with the call.20:36
bknudsonwhat's correlation ID? http://git.openstack.org/cgit/openstack/oslo.middleware/tree/oslo_middleware/correlation_id.py20:36
*** jasondotstar has joined #openstack-meeting-420:37
*** jasondotstar has quit IRC20:37
RockygI think that's the RIDs for notivications.20:37
*** padkrish has quit IRC20:37
RockygBut, dhellmann is the expert.20:37
dhellmanngordc is the middleware expert, I don't know what that is20:37
*** puranamr has quit IRC20:38
RockygOK.  ready for my next topic/question?20:38
bknudsonhttp://git.openstack.org/cgit/openstack/oslo.middleware/tree/oslo_middleware/request_id.py -- the request ID that the server is going to assign is in openstack.request_id in the request env20:39
bknudsonso you've got it if you want to log it I guess20:39
bknudsonthen do you have to pass that along when you make the request to the next service?20:40
RockygSo, yeah.  RId for notifications.  Jay Pipes is pushing this and the Ops want events to log, which would need these20:40
Rockygbknudson: You would think.  But I don't think many have thought it out that far yet.20:40
bknudsoncorrelation ID and request ID look pretty similar20:41
bknudsononly diff is the request ID has req- prefix20:41
RockygYup.  One for APIs, one for events20:41
dhellmannbknudson: here's where correlation_id was added: http://git.openstack.org/cgit/openstack/oslo.middleware/commit/?id=758263a8fba5870f48d2e8d15a13bf383eb389d220:42
bknudsonlooks like correlation ID is to also track requests across services20:43
RockygYup. But outside of the API path.  So, the RPCs,Rabbitq, etc.20:44
bknudsonit's middleware so it's generated from the api request coming in20:44
bknudsonunless there's some other user of middleware20:44
*** nkrinner has quit IRC20:44
*** Sukhdev has quit IRC20:44
*** VanL has quit IRC20:44
dhellmannno, that's a wsgi middleware, so it's the rest call20:44
*** DericHorn-HP has quit IRC20:45
*** Sukhdev has joined #openstack-meeting-420:45
Rockyghmm.20:45
dhellmannone of our pain points on these libraries is definitely documentation :-(20:45
bknudsonmaybe we can deprecate correlation-id in favor of x-openstack-request-id ?20:46
*** puranamr has joined #openstack-meeting-420:46
dhellmannI wonder if that header name is some sort of standard20:46
Rockygor vice versa ;-)20:46
*** daneyon has quit IRC20:47
*** padkrish has joined #openstack-meeting-420:47
dhellmannwell, searching for X_CORRELATION_ID does turn up some hits20:47
bknudsonkeystone has request_id in the default pipeline, no correlation id20:48
dhellmannhere's the old spec for that middleware: https://blueprints.launchpad.net/oslo-incubator/+spec/create-a-unified-correlation-id20:49
Rockygbp doesn't link to anything.20:49
RockygAh!  you found it.20:50
dhellmannand a related old email thread: https://lists.launchpad.net/openstack/msg13082.html20:50
bknudsonI don't see any paste.ini with CorrelationId. It doesn't have a factory function either20:50
dhellmannit might not be used yet20:50
bknudsonTue, 12 Jun 2012 -- the dream will eventually come true!20:51
RockygIt looks like Nova was supposed to put it in v2.1 (roginally v3)20:51
*** VanL has joined #openstack-meeting-420:51
*** banix has joined #openstack-meeting-420:51
dhellmannthe old nova spec: http://git.openstack.org/cgit/openstack/oslo.middleware/commit/?id=758263a8fba5870f48d2e8d15a13bf383eb389d220:52
*** fallenpegasus has joined #openstack-meeting-420:52
RockygIt was supposed to be in Juno.20:52
dhellmannoops20:52
dhellmannhttps://blueprints.launchpad.net/nova/+spec/cross-service-request-id20:52
RockygYup.20:52
dhellmannanyway, it looks like there is lots of prior art here and whoever is pushing this now should pull it all together, summarize the state of what we have and how that's different from what we want20:53
dhellmanninstead of starting from scratch20:53
bknudsonwe might be trying to make something perfect when we should start out with whatever's easy20:54
*** jwagner is now known as jwagner_away20:54
RockygSounds good to me.  I think we have an action and that we have a chance of getting a start on this in Liberty20:54
dhellmannand we might already have half of what we want20:54
Rockyg#action pull all the correlation-id threads together, document, and discuss with Abhishek, etc.20:54
bknudsonwell, it seems like all we're going to get accomplished in L is being able to get the request ID from the response in the python apis.20:55
RockygWell, I think we've gotten some useful work done here today.  I'm happy.20:55
dhellmann++20:56
RockygI'll pull the threads together and post to the ML referring to the current Request-ID spec.20:56
RockygAnd with that any other things to discuss, or close it down?20:56
bknudsonhappy canada day20:57
*** auld1 has quit IRC20:57
RockygHappy Canada Day!20:57
* dhellmann salutes his northern neighbors20:57
Rockyg#endmeeting20:58
*** openstack changes topic to "Automatic Task Triggering (Meeting topic: glance drivers)"20:58
openstackMeeting ended Wed Jul  1 20:58:05 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-07-01-20.01.html20:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-07-01-20.01.txt20:58
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-07-01-20.01.log.html20:58
RockygThanks, guys!20:58
*** auld has joined #openstack-meeting-420:58
*** padkrish has quit IRC20:58
*** padkrish has joined #openstack-meeting-420:59
sdake#startmeeting kolla21:00
openstackMeeting started Wed Jul  1 21:00:27 2015 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: kolla)"21:00
openstackThe meeting name has been set to 'kolla'21:00
sdake#topic rollcall21:00
*** openstack changes topic to "rollcall (Meeting topic: kolla)"21:00
*** marcusvrn has joined #openstack-meeting-421:00
sdakegroan hour too early21:01
sdake#endmeeting21:01
*** openstack changes topic to "Automatic Task Triggering (Meeting topic: glance drivers)"21:01
openstackMeeting ended Wed Jul  1 21:01:04 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-07-01-21.00.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-07-01-21.00.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-07-01-21.00.log.html21:01
*** ajmiller_ has joined #openstack-meeting-421:03
*** padkrish has quit IRC21:03
*** puranamr has quit IRC21:04
*** VanL has quit IRC21:06
*** dfg_ has left #openstack-meeting-421:06
*** ajmiller has quit IRC21:06
*** sdake_ has joined #openstack-meeting-421:07
*** sdake has quit IRC21:09
*** Swami has joined #openstack-meeting-421:13
*** padkrish has joined #openstack-meeting-421:13
*** IlyaG has joined #openstack-meeting-421:21
*** VanL has joined #openstack-meeting-421:21
*** marcusvrn has quit IRC21:23
*** VanL has quit IRC21:30
*** ivar-lazzaro has joined #openstack-meeting-421:33
*** VanL has joined #openstack-meeting-421:33
*** VanL_ has joined #openstack-meeting-421:34
*** s3wong has joined #openstack-meeting-421:35
*** padkrish has quit IRC21:36
*** padkrish has joined #openstack-meeting-421:36
*** VanL has quit IRC21:38
*** vinkman has joined #openstack-meeting-421:39
*** puranamr has joined #openstack-meeting-421:41
*** padkrish has quit IRC21:41
*** IlyaG has quit IRC21:44
*** mandre has joined #openstack-meeting-421:45
*** mmedvede has quit IRC21:48
*** bknudson has quit IRC21:51
*** dannywilson has quit IRC21:55
*** puranamr has quit IRC21:55
*** dannywilson has joined #openstack-meeting-421:56
*** singleth_ has joined #openstack-meeting-421:56
*** nihilifer has joined #openstack-meeting-421:57
*** mwang2 has joined #openstack-meeting-421:57
*** mfalatic has joined #openstack-meeting-421:57
*** mstachow has joined #openstack-meeting-421:58
*** singlethink has quit IRC21:59
*** padkrish has joined #openstack-meeting-422:00
sdake_#startmeeting olla22:00
openstackMeeting started Wed Jul  1 22:00:15 2015 UTC and is due to finish in 60 minutes.  The chair is sdake_. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:00
sdake_#topic rollcall22:00
*** openstack changes topic to " (Meeting topic: olla)"22:00
openstackThe meeting name has been set to 'olla'22:00
*** openstack changes topic to "rollcall (Meeting topic: olla)"22:00
sdake_#endmeeting22:00
*** openstack changes topic to "Automatic Task Triggering (Meeting topic: glance drivers)"22:00
openstackMeeting ended Wed Jul  1 22:00:30 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/olla/2015/olla.2015-07-01-22.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/olla/2015/olla.2015-07-01-22.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/olla/2015/olla.2015-07-01-22.00.log.html22:00
sdake_#startmeeting kolla22:00
openstackMeeting started Wed Jul  1 22:00:38 2015 UTC and is due to finish in 60 minutes.  The chair is sdake_. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:00
*** openstack changes topic to " (Meeting topic: kolla)"22:00
openstackThe meeting name has been set to 'kolla'22:00
sdake_#topic rollcall22:00
*** openstack changes topic to "rollcall (Meeting topic: kolla)"22:00
harmw0/22:00
mstachowolla !22:00
sdake_o/ sorry for the typo there folks :)22:01
mfalatico/22:01
mandrehere o/22:01
sdake_keyboard getting warn22:01
sdake_worn22:01
*** klamath has quit IRC22:01
jpeelerhey22:01
sdake_i'll give it couple more mins for stragglers ;)22:02
*** mwang2 has quit IRC22:02
harmwmstachow: shouldn't you be in bed? :p22:02
mstachowand You ;) ?22:02
harmw:P22:02
sdake_#topic announcements22:02
*** openstack changes topic to "announcements (Meeting topic: kolla)"22:02
harmwL1! woohoo22:03
sdake_midcycle information is avilable now: https://wiki.openstack.org/wiki/Sprints/KollaLibertySprint#Cisco_Specifics22:03
sdake_rather22:03
sdake_#link https://wiki.openstack.org/wiki/Sprints/KollaLibertySprint22:03
sdake_I'll flesh that page out as I get more details22:03
sdake_please book your travel if you intend to attend ;)22:03
sdake_note bay area hotel rates will crank up over next couple weeks, so please please book your hotels now22:04
*** nihilifer_ has joined #openstack-meeting-422:04
sdake_we have room for 25 seats22:04
sdake_i'll send out eventbrite info later today22:04
*** nihilifer has quit IRC22:04
*** nihilifer_ is now known as nihilifer22:04
sdake_if you can't make it because of budget issues, pleae mark the time in your calendar for remote participation22:04
harmwI won't be attending in person22:04
sdake_would like to see as many folks there as possible either remote or local22:05
sdake_harmw ya it will be hard for non-us citizens to make it to the summit because of the timelines22:05
sdake_we have alot of work to do in teh midcycle22:05
harmwvarious reasons, but yes22:05
sdake_I'm not sure if we will always have a midcycle22:05
* mstachow happy because of remote participation !22:05
sdake_but right now we have many unanswered questions that a good face to face meeting can fix :)22:05
harmwyea22:05
sdake_now I should warn, the remote participation will be pretty terrible ;)22:06
sdake_it may be mostly one way unfortunately22:06
sdake_its really hard to get a word in edgewise on the computer22:06
sdake_with a room full of people talking22:06
harmwwe'll see how it rolls22:06
sdake_second announcement22:06
sdake_liberty-1 was released couple days ago22:06
sdake_it all seemed to work for me22:06
sdake_heat seems a bit buggy22:06
sdake_but working22:06
sdake_for example the heat demo deosn't work properly22:06
sdake_also horizon is completely busted22:07
sdake_it would be cool if someone could fix that :)22:07
harmwand thanks for everyone rushing out all those fixes in such a limited window!22:07
harmwhorizon was upstream, right?22:07
mandredo we have bugs logged for all the things you mentioned?22:07
sdake_yes there are bugs22:07
sdake_so we went from 35 bugs at release announcement creation time to 60 bugs at release22:08
sdake_that meanss our ci needs some serious love22:08
harmwyea, I think most if not all issues were logged in our own LP22:08
sdake_#topic continuous integration22:08
*** openstack changes topic to "continuous integration (Meeting topic: kolla)"22:08
harmwsingle nic, period22:08
sdake_ok well before we can do single nick we need internal config of openvswitch working22:09
*** VanL_ has quit IRC22:09
sdake_any taers?22:11
harmwthere is work underway on that right?22:12
sdake_nobody owns it22:12
harmwhm22:12
harmwI could just take a look22:12
sdake_ok this should come behind that other work we talked about today harmw22:12
harmwisn't this something Sam wanted to tackle?22:12
harmwyep22:12
sdake_sam tackled external config22:13
sdake_and then didn't do internal config22:13
sdake_now he wants someone else to do internal config i guess22:13
sdake_we ar egating on internal config to begin22:13
harmwit's on my list anyway, to do something with openvswitch :)22:13
sdake_cool harmw can you make a blueprint22:13
harmwok, assign me22:13
sdake_ok i'll make a blueprint22:13
sdake_#topic liberty-2 planning22:14
*** openstack changes topic to "liberty-2 planning (Meeting topic: kolla)"22:14
sdake_#link https://launchpad.net/kolla/+milestone/liberty-222:14
sdake_please open that up22:14
harmwtempest! wanted to say that in terms of the previous item :)22:14
sdake_harmw I htink jpeeler will tackle that22:15
harmwI'm seeing tons of new containers22:15
sdake_lets focus on one problem at a time - which is the aio networ22:15
sdake_and tempest next22:15
sdake_so lots of started blueprints22:15
sdake_yay ;-)22:15
sdake_our deadline is July 3122:15
sdake_or midcycle is 28,29th22:15
sdake_or/our22:16
*** mmedvede has joined #openstack-meeting-422:16
*** banix has quit IRC22:16
sdake_so our midcycle will define what work we do for the remainder of liberty22:16
harmwyep, though there is something on that list already22:16
harmwfor L322:16
sdake_where22:16
*** sdake_ is now known as sdake22:17
sdakewhich item22:17
harmwhttps://launchpad.net/kolla/+milestone/liberty-322:17
sdakeoh ya22:17
sdakei just push stuff out there that isn't in l222:17
sdakei should probably move that to l222:17
sdakei don't even know whats in l3 atm22:17
sdakeoh its ironic probably - jpeleer said he is doing in l322:17
sdakenot in l222:17
harmw:)22:17
sdakein terms of priorities, I think we have22:17
sdake1. Make ansible work properly22:17
*** dims_ has joined #openstack-meeting-422:17
sdake2. Make from source install work properly22:18
sdake3. Make HA containers work properly22:18
harmwshoudln't 2 be: multinode?22:18
sdakeunderlying these 3 main priorities is ci22:18
sdakeharms 1 = multinode bro22:18
harmwoh ok22:18
sdakedoes anyone see a different set of priorities we should have?22:19
mandreseems good22:19
mstachow+122:19
harmwmaybe putting HA first?22:19
sdakeansible is definately first22:19
sdakesince it givs multinode22:19
sdaketo test ha22:19
harmwsdake: excuse me, ansible is #1 period22:19
sdakewe can swap src and ha, i'm good with that change22:19
harmwI meant HA in favor of source22:19
harmwwould our users benefit from source based, our would that affect only us developers?22:20
harmw(which is good as well, but targets a different audience)22:20
sdakeok vote of A = sdake's priority vote of B = harmw's priority vote of -1 is different priority22:20
sdakeplease vote22:20
mstachowA22:20
mandreagreed HA should have higher priority than source install22:20
nihiliferA22:20
*** dims has quit IRC22:21
mandreB for me22:21
harmwB22:21
sdakeya i think ha is higher prior then src22:21
sdakeso B22:21
jpeeleri kind of liked A...22:21
sdakeseems like we don't really have the entire team here to make a consensus on it22:21
sdakelets just put it this way22:21
sdakewe need to get all 3 done in liberty 222:21
harmwyea, whats in a month anyway :)22:22
jpeelerthat consensus topic reminded me about something for open discussion22:22
sdakewe are going to go over a few blueprints22:22
mandrethe month of july harmw…22:22
sdake#link https://blueprints.launchpad.net/kolla/+spec/standard-start22:22
sdakeharmw can you give us an update on this blueprint22:22
sdakewith relevant links for those to catch up22:22
harmwyea, it's been drafted quite recently so work has yet to take off22:23
sdakewould you mind linking the etherpad22:23
harmwwe're dividing containers between several devs, this has been listed on https://etherpad.openstack.org/p/kolla-standard-start22:23
harmwa separation has been made into two distinct groups of containers, as to where to target our focus first22:24
harmwI'll be adding Glance tomorrow, which can serve as base (well...) for the others22:24
harmwcomments on that epad are, as always, appreciated22:25
sdakecool so looks like that is mostly covered by assignees22:25
sdakethe reason harmw is reporting out is he is the asignee on the blueprint22:25
sdakewhich means he is responsible for wrangling the status22:26
sdakei'll still be responsible for wrangling the blueprints overall :)22:26
harmwnext week I hope to report real progress on this :)22:26
sdake#link https://blueprints.launchpad.net/kolla/+spec/ansible-service22:26
sdakeharmw I hope your done by next week ;-)22:27
sdakethis is adding the ansible framework to each of the services22:27
sdakesamyaple is out so I'll report the status22:27
harmwwith an epad as well: https://etherpad.openstack.org/p/ansibalising-containers22:27
sdake#link https://etherpad.openstack.org/p/ansibalising-containers22:27
sdakethsi one doesn't have alot of assignees22:27
sdakeif your looing to contribute assign yourself as a contributor please22:27
sdakemandre would love for your involvement here ;)22:28
sdakeI am going to leave the midcycle planning until next week22:29
mandrei'll add my name to some of the containers22:29
sdakebecause that meeting has better attendeance22:29
sdakethanks mandre22:29
sdake#topic open discussion22:29
*** sdake is now known as sdake_22:29
sdake_#topic open discussion22:29
*** openstack changes topic to "open discussion (Meeting topic: kolla)"22:29
harmwthere was a recent discussion on the ML regarding meetingtimeslot22:30
harmwthe slot for next week22:30
*** singleth_ has quit IRC22:30
*** aventerav has quit IRC22:30
sdake_ok well I am not changing next week's slot22:30
harmwwas there concensus on moving from 16:00 to 16:30 ?22:30
sdake_but I can change 3 weeks slot around22:31
sdake_and see what happens22:31
harmwnot next week, sure, but that weeknmbr22:31
harmwyou know, odd/even :)22:31
sdake_right22:31
sdake_ok well i'll change it, and we will see if people complain22:31
harmwgreat22:31
sdake_meetings on the half hour are harder to remember ;(22:31
sdake_jpeeler you said you had something for open discussion?22:31
harmwwe'll see what happens22:31
jpeeleri was just wondering if  anybody felt like we rely on IRC more than we should in contrast to using the mailing list? or perhaps this is just a natural progression as the project continues to develop22:32
sdake_i would really like to see more ml usage22:32
sdake_but I think our usage of irc is fantastic!22:32
harmwjpeeler: in what kind of way?22:32
*** padkrish has quit IRC22:32
mandreand now our irc channel is logged anyway22:32
sdake_the nice thing about ml usage is that it shows people its not just me out there22:33
jpeelerharmw: i just feel like we make a lot of decisions on IRC rather than taking it to the list22:33
sdake_if they join our irc channel at 1am they will see a whoel bunch of contribs that have never posted on the ml22:33
*** padkrish has joined #openstack-meeting-422:33
sdake_jpeeler agree22:33
harmwjpeeler: true22:33
mfalaticMailing lists tend to be better for larger discussions (things that may span days or weeks of back and forth, like architecture)22:34
harmwbut isn't this in a some way 'our game' then? forgive me if I'm way off though22:34
sdake_jpeeler do you have suggestions to improve things22:34
*** puranamr has joined #openstack-meeting-422:34
mfalaticPerhaps it's an outgrowth of greater complexity that drives such discussions naturally to mailing lists.22:34
jpeelerwell first i just wanted to see if people agreed and then if so, we can just make more of an effort to do so22:35
sdake_well I think we should use the ml more22:35
harmware other folks on the ML in some way affected by our lack of ML usage btw?22:35
sdake_but I don't know how to encourage it22:35
sdake_harmw YES22:36
sdake_harmw they have to read irc logs to see how decisions are made22:36
sdake_which  they wont do22:36
mandrejpeeler, agreed, it's nice you bring this up22:36
jpeelerIRC logs tend to be litered with lots of fluff - no offense to anybody!22:36
harmwjpeeler: fully agree on that22:36
harmwlog reading sucks22:36
mfalaticIRC logs are a PITA to read.22:36
sdake_ya like steak talking about his new audio gear ;)22:36
harmwyep22:36
mfalaticYeah! Wait...22:36
harmwso, what's the last decision we've made?22:36
sdake_good q harmw22:37
sdake_jpeeler got any examples ;)22:37
mfalaticLogs come in handy sometimes, but they're generally not a good way to keep up with an intricate or ongoing architectural debate.22:37
jpeelerwell making decisions here in the official meeting log is fine22:37
jpeelerbut perhaps discussion the priorities on the ML would have been good22:37
*** padkrish has quit IRC22:37
sdake_this meeting is constrained to 4 hrs a week22:37
sdake_irc is 24 hours a day22:37
sdake_4 hrs a month i mean22:37
sdake_irc meeting is for our highest prioirty topics of discussion22:38
sdake_ml medium priority22:38
sdake_irc low priority22:38
sdake_imo ;)22:38
mfalaticemail is 24x7 but allows greater participation IMHO, when consensus en masse counts.22:38
harmwso all is either high or low :>22:38
mstachowso we should set more medium priorities imo22:38
sdake_our irc meeting is 4 hours a month but our irc time is 24 hrs a day22:38
harmwwhich we actually make good use of22:39
*** pdb-mobile has joined #openstack-meeting-422:39
sdake_hey pdb ;)22:39
pdb-mobileHi22:39
pdb-mobileHmm, am i late22:39
pdb-mobileOr early22:39
sdake_well if someone thinks i have the priorities wrong feel free to correct them ;-)22:39
harmwperhaps we could settle on deciding what to put to the ML when the next decision has to be made22:39
harmwor something like that22:40
sdake_a good topic for ml is something that crosses time boundaries22:40
sdake_that could take multiple days to figure out as mfalatyc pointed out22:40
jpeeleri tend to think of the ML as more of an archive22:40
sdake_the irc meetings are archived22:41
sdake_the irc logs are archived22:41
sdake_everything is archived22:41
jpeelera readable archive :)22:41
sdake_readable lol :) clearly you dont read the ml very often ;)22:41
* mstachow is thinking: is archive archived?22:41
sdake_ok well i'm all for using the ml more22:41
mfalaticArchive is printed using a pin-fed line printer on triplicate paper.22:42
sdake_lets all make an effort when discussing changes in architecture that span multiple days worth of discussion to do it on irc22:42
sdake_minus those that are done via our god awful specs process22:42
harmwdon't you mean the ML there?22:42
jpeeleri assume you meant ML there22:42
sdake_ya ml22:42
sdake_sorry22:42
harmwcool22:42
* jpeeler is done with that22:43
sdake_ya folks it would really hlpe our project grow as well to see us conversing on the mailing list22:43
sdake_part of how projects are measured is by a term called "engagement"22:43
harmwexposure22:43
sdake_engagement is measured by ml participation22:43
sdake_almost exclusively22:43
harmwhm, can't say I like that but ok22:43
sdake_even though our engagement imo is measured by our irc logs which are quite long each day :)22:44
sdake_harmw ya its backwards22:44
harmwindeed22:44
pdb-mobileMl is useful22:44
pdb-mobileFocused streams of conversion you can choose to track or ignore22:44
*** Sukhdev has quit IRC22:45
pdb-mobileEasier to miss important stuff on irc22:45
*** Sukhdev has joined #openstack-meeting-422:45
harmwso true22:45
*** fallenpegasus has quit IRC22:45
harmwmore topics?22:45
mandreML is also an invitation for other devs to get involved in the project22:45
sdake_ya we beat that one into the ground22:46
*** nihilifer has quit IRC22:46
sdake_hey nih*22:46
sdake_any other open topics for discussion22:46
harmwhttps://etherpad.openstack.org/p/kolla-summit-talk-proposals22:47
sdake_or shall we conclude the meeting?22:47
harmwif anyone has input on that, your welcome to add22:47
harmwsome reasoning: there was recent talk in #kolla about interesting stuff to talk about, now I don't know if this was regarding midcycle or summit, but the etherpad may be used to keep track of what could be of interest22:48
sdake_harmw we wil lhave midcycle planning next wendesday22:48
harmwit wasn't much talking btw, more enthusiasm :)22:48
sdake_if you want to do a talk at summit id' suggest keeping it secret until yo submit it so somoene doesn't jack your ideas ;)22:49
harmwI'm not talking, lol22:49
sdake_daneyon and I are doing one22:49
sdake_it would be interesting t osee a talk on someone that is a downstream of olla using kolla in deployment products22:49
harmwprobably to soon for that, but yes22:49
sdake_so for those that watch the logs after, tr yto think how to get that sort of talk into summit :)22:50
sdake_the deadline is july 15th for summit proposals22:50
sdake_but tose are 40 minute talsk, like what daneyon and I gave at summit22:50
sdake_anyway lets not mix things up too much :)22:50
sdake_if you want to do that, recommend working together - 2 people in a talk wor well together22:51
sdake_any other subjects?22:51
sdake_on that note, please book your travel for summit22:51
harmwopionions on Q/A for coding, or should we skip on that for now?22:51
sdake_reference the sprints page for travel info22:51
sdake_harmw lets do that at midcycle22:51
*** padkrish has joined #openstack-meeting-422:51
sdake_that is a perfect midcycle discussion topic22:51
harmwperhaps best22:51
harmwyea22:52
*** nihilifer has joined #openstack-meeting-422:52
sdake_ok, rememeber, priority #1 - Anisbleize Kolla22:52
sdake_lets get cracking!22:52
sdake_#endmeeting22:52
harmwtime to wrap it up22:52
*** openstack changes topic to "Automatic Task Triggering (Meeting topic: glance drivers)"22:52
openstackMeeting ended Wed Jul  1 22:52:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-07-01-22.00.html22:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-07-01-22.00.txt22:52
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-07-01-22.00.log.html22:52
*** mfalatic has left #openstack-meeting-422:53
*** sdake_ has quit IRC22:54
*** mstachow has quit IRC22:54
*** pdb-mobile has quit IRC22:56
*** nihilifer has quit IRC22:56
*** dannywilson has quit IRC23:02
*** dannywilson has joined #openstack-meeting-423:03
*** carl_baldwin has quit IRC23:03
*** mwang2 has joined #openstack-meeting-423:04
*** radek_ has quit IRC23:05
*** saneax has joined #openstack-meeting-423:07
*** mwang2 has quit IRC23:13
*** DericHorn-HP has joined #openstack-meeting-423:13
*** Grace has quit IRC23:16
*** lazy_prince has joined #openstack-meeting-423:26
*** carl_baldwin has joined #openstack-meeting-423:29
*** padkrish has quit IRC23:37
*** padkrish has joined #openstack-meeting-423:38
*** puranamr has quit IRC23:39
*** puranamr has joined #openstack-meeting-423:40
*** padkrish has quit IRC23:42
*** carl_baldwin has quit IRC23:47
*** carl_baldwin has joined #openstack-meeting-423:48
*** DericHorn-HP has quit IRC23:50
*** vinkman has left #openstack-meeting-423:51
*** xingchao_ has joined #openstack-meeting-423:51
*** DericHorn-HP has joined #openstack-meeting-423:52
*** DericHorn-HP has quit IRC23:53
*** trey has quit IRC23:53
*** puranamr_ has joined #openstack-meeting-423:57

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