Wednesday, 2016-03-30

*** avarner_ has quit IRC00:02
*** yuywz has joined #openstack-meeting-400:06
*** prithiv has joined #openstack-meeting-400:06
*** Sukhdev has quit IRC00:07
*** IlyaG has quit IRC00:09
*** minwang2 has quit IRC00:10
*** Sukhdev has joined #openstack-meeting-400:10
*** uck has quit IRC00:11
*** ajmiller has quit IRC00:12
*** IlyaG has joined #openstack-meeting-400:16
*** Swami has quit IRC00:17
*** SumitNaiksatam has quit IRC00:19
*** fawadkhaliq has quit IRC00:20
*** fawadkhaliq has joined #openstack-meeting-400:20
*** sdake has quit IRC00:22
*** sdake has joined #openstack-meeting-400:24
*** fawadkhaliq has quit IRC00:24
*** xingchao has joined #openstack-meeting-400:26
*** bobh has quit IRC00:27
*** IlyaG has quit IRC00:29
*** xingchao has quit IRC00:31
*** baoli has joined #openstack-meeting-400:32
*** SimonChung1 has quit IRC00:33
*** baoli_ has joined #openstack-meeting-400:34
*** baoli has quit IRC00:38
*** prashantD has quit IRC00:40
*** baoli_ has quit IRC00:45
*** May-meimei has quit IRC00:52
*** prithiv has quit IRC00:56
*** prithiv has joined #openstack-meeting-400:57
*** prithiv has quit IRC00:57
*** May-meimei has joined #openstack-meeting-400:59
*** sdake_ has joined #openstack-meeting-400:59
*** sdake has quit IRC01:02
*** banix has joined #openstack-meeting-401:02
*** IlyaG has joined #openstack-meeting-401:04
*** baoli has joined #openstack-meeting-401:06
*** Sukhdev has quit IRC01:08
*** IlyaG has quit IRC01:09
*** baoli has quit IRC01:10
*** baoli has joined #openstack-meeting-401:11
*** baohua has joined #openstack-meeting-401:12
*** baoli has quit IRC01:12
*** zhurong_ has joined #openstack-meeting-401:20
*** emagana has joined #openstack-meeting-401:24
*** emagana has quit IRC01:29
*** yhvh has quit IRC01:29
*** yhvh has joined #openstack-meeting-401:30
*** raginbajin has quit IRC01:30
*** krotscheck_dcm has quit IRC01:31
*** raginbajin has joined #openstack-meeting-401:31
*** krotscheck has joined #openstack-meeting-401:33
*** baoli has joined #openstack-meeting-401:34
*** Jeffrey4l has joined #openstack-meeting-401:36
*** sridhar_ram has quit IRC01:40
*** baoli has quit IRC01:41
*** SimonChung has joined #openstack-meeting-401:41
*** SimonChung1 has joined #openstack-meeting-401:43
*** baoli has joined #openstack-meeting-401:43
*** SimonChung has quit IRC01:46
*** unicell has quit IRC01:53
*** baoli has quit IRC01:53
*** dave-mccowan has joined #openstack-meeting-401:54
*** salv-orl_ has joined #openstack-meeting-401:55
*** salv-orl_ has quit IRC01:58
*** salv-orl_ has joined #openstack-meeting-401:58
*** salv-orlando has quit IRC01:59
*** dims has quit IRC01:59
*** thorst has joined #openstack-meeting-402:00
*** xingchao has joined #openstack-meeting-402:02
*** dims has joined #openstack-meeting-402:04
*** salv-orl_ has quit IRC02:05
*** xingchao has quit IRC02:05
*** xingchao has joined #openstack-meeting-402:06
*** xingchao has quit IRC02:10
*** Rocky_g has quit IRC02:14
*** thorst has quit IRC02:17
*** lakshmiS has joined #openstack-meeting-402:18
*** julim has joined #openstack-meeting-402:18
*** bpokorny has quit IRC02:21
*** azbiswas has joined #openstack-meeting-402:28
*** yamahata has quit IRC02:34
*** iyamahat has quit IRC02:34
*** xingchao has joined #openstack-meeting-402:42
*** dims_ has joined #openstack-meeting-402:45
*** dims has quit IRC02:46
*** GB21 has joined #openstack-meeting-402:49
*** prashantD has joined #openstack-meeting-402:54
*** azbiswas has quit IRC02:56
*** s3wong has quit IRC03:05
*** azbiswas has joined #openstack-meeting-403:05
*** sdake_ is now known as sdake03:07
*** bpokorny has joined #openstack-meeting-403:14
*** sdake_ has joined #openstack-meeting-403:17
*** sdake has quit IRC03:20
*** vhoward has quit IRC03:24
*** bpokorny has quit IRC03:25
*** GB21 has quit IRC03:25
*** baoli has joined #openstack-meeting-403:28
*** yamahata has joined #openstack-meeting-403:31
*** baoli has quit IRC03:32
*** iyamahat has joined #openstack-meeting-403:32
*** harshs has joined #openstack-meeting-403:36
*** askb has joined #openstack-meeting-403:42
*** baohua has quit IRC03:51
*** baohua has joined #openstack-meeting-403:52
*** baohua has quit IRC03:53
*** emagana has joined #openstack-meeting-403:54
*** iyamahat has quit IRC03:55
*** baohua has joined #openstack-meeting-403:55
*** banix has quit IRC03:56
*** emagana has quit IRC03:59
*** javeriak has joined #openstack-meeting-404:00
*** IlyaG has joined #openstack-meeting-404:06
*** IlyaG has quit IRC04:10
*** IlyaG has joined #openstack-meeting-404:10
*** vishnoianil has quit IRC04:13
*** nihilifer has quit IRC04:15
*** dave-mccowan has quit IRC04:16
*** nihilifer has joined #openstack-meeting-404:16
*** harshs has quit IRC04:17
*** fawadkhaliq has joined #openstack-meeting-404:18
*** xingchao has quit IRC04:21
*** harshs has joined #openstack-meeting-404:22
*** mohankumar has joined #openstack-meeting-404:24
*** baohua has quit IRC04:26
*** mohankumar has quit IRC04:29
*** galstrom_zzz is now known as galstrom04:30
*** markvoelker has joined #openstack-meeting-404:36
*** mohankumar has joined #openstack-meeting-404:41
*** mohankumar has quit IRC04:54
*** MarkAtwood has joined #openstack-meeting-404:56
*** javeriak has quit IRC04:57
*** GB21 has joined #openstack-meeting-404:57
*** vishwanathj is now known as vishwanathj_zzz05:03
*** javeriak has joined #openstack-meeting-405:06
*** baohua has joined #openstack-meeting-405:07
*** vishnoianil has joined #openstack-meeting-405:15
*** mohankumar has joined #openstack-meeting-405:15
*** prashantD has quit IRC05:18
*** mohankumar has quit IRC05:19
*** sdake_ has quit IRC05:20
*** nkrinner has joined #openstack-meeting-405:25
*** Sukhdev has joined #openstack-meeting-405:28
*** sdake has joined #openstack-meeting-405:29
*** hdaniel has joined #openstack-meeting-405:30
*** mohankumar has joined #openstack-meeting-405:32
*** lakshmiS has quit IRC05:33
*** javeriak has quit IRC05:37
*** Sukhdev has quit IRC05:39
*** xingchao has joined #openstack-meeting-405:40
*** sridhar_ram has joined #openstack-meeting-405:45
*** anilvenkata has joined #openstack-meeting-405:47
*** sdake has quit IRC05:48
*** sdake has joined #openstack-meeting-405:51
*** sridhar_ram1 has joined #openstack-meeting-405:55
*** sridhar_ram has quit IRC05:57
*** emagana has joined #openstack-meeting-405:58
*** irenab has joined #openstack-meeting-405:59
*** iyamahat has joined #openstack-meeting-406:01
*** emagana has quit IRC06:03
*** javeriak has joined #openstack-meeting-406:04
*** azbiswas has quit IRC06:05
*** javeriak has quit IRC06:08
*** Sukhdev has joined #openstack-meeting-406:09
*** markvoelker has quit IRC06:10
*** javeriak has joined #openstack-meeting-406:11
*** sridhar_ram1 is now known as sridhar_ram06:14
*** harshs has quit IRC06:16
*** numans has joined #openstack-meeting-406:19
*** yuli_s has joined #openstack-meeting-406:23
*** javeriak has quit IRC06:24
*** javeriak has joined #openstack-meeting-406:25
*** markvoelker has joined #openstack-meeting-406:26
*** hdaniel has quit IRC06:28
*** unicell has joined #openstack-meeting-406:30
*** azbiswas has joined #openstack-meeting-406:34
*** azbiswas has quit IRC06:37
*** salv-orlando has joined #openstack-meeting-406:37
*** azbiswas has joined #openstack-meeting-406:38
*** markvoelker has quit IRC06:39
*** azbiswas_ has joined #openstack-meeting-406:40
*** mrunge_ is now known as mrunge06:40
*** azbiswas has quit IRC06:43
*** wanghua has joined #openstack-meeting-406:44
*** azbiswas has joined #openstack-meeting-406:46
*** azbiswas_ has quit IRC06:49
*** galstrom is now known as galstrom_zzz06:51
*** zeih has joined #openstack-meeting-406:58
*** javeriak has quit IRC07:05
*** javeriak has joined #openstack-meeting-407:07
*** Sukhdev has quit IRC07:08
*** sridhar_ram has quit IRC07:09
*** yamahata has quit IRC07:16
*** yamahata has joined #openstack-meeting-407:17
*** matrohon has joined #openstack-meeting-407:17
*** cartik has joined #openstack-meeting-407:22
*** fawadkhaliq has quit IRC07:24
*** daneyon has quit IRC07:24
*** daneyon has joined #openstack-meeting-407:25
*** GB21 has quit IRC07:25
*** jmckind_ has quit IRC07:26
*** xingchao has quit IRC07:27
*** cartik has quit IRC07:28
*** jschwarz has joined #openstack-meeting-407:33
*** IlyaG has quit IRC07:37
*** IlyaG has joined #openstack-meeting-407:38
*** markvoelker has joined #openstack-meeting-407:40
*** jed56 has joined #openstack-meeting-407:40
*** markvoelker has quit IRC07:45
*** sdake_ has joined #openstack-meeting-407:49
*** azbiswas has quit IRC07:49
*** sdake has quit IRC07:51
*** xingchao has joined #openstack-meeting-407:52
*** salv-orlando has quit IRC07:58
*** mbound has joined #openstack-meeting-407:59
*** salv-orlando has joined #openstack-meeting-408:08
*** _degorenko|afk is now known as degorenko08:18
*** ihrachys has joined #openstack-meeting-408:20
*** hdaniel has joined #openstack-meeting-408:20
*** yamahata has quit IRC08:22
*** zhurong_ has quit IRC08:23
*** zhurong has joined #openstack-meeting-408:25
*** javeriak has quit IRC08:28
*** dgonzalez has quit IRC08:29
*** dgonzalez has joined #openstack-meeting-408:35
*** sdake_ has quit IRC08:36
*** iberezovskiy_afk is now known as iberezovskiy08:37
*** markvoelker has joined #openstack-meeting-408:42
*** pbourke has quit IRC08:43
*** pbourke has joined #openstack-meeting-408:44
*** iyamahat has quit IRC08:47
*** markvoelker has quit IRC08:47
*** prithiv has joined #openstack-meeting-408:51
*** mohankumar has quit IRC08:55
*** yuywz has quit IRC08:55
*** yuywz has joined #openstack-meeting-408:55
*** GB21 has joined #openstack-meeting-408:56
*** yuywz has quit IRC09:00
*** GB21 has quit IRC09:01
*** GB21 has joined #openstack-meeting-409:01
*** mohankumar has joined #openstack-meeting-409:01
*** mohankumar has quit IRC09:06
*** mohankumar has joined #openstack-meeting-409:17
*** mohankumar has quit IRC09:22
*** mfedosin has joined #openstack-meeting-409:30
*** baohua has quit IRC09:30
*** prithiv has quit IRC09:30
*** mfedosin has quit IRC09:34
*** mohankumar has joined #openstack-meeting-409:34
*** javeriak has joined #openstack-meeting-409:43
*** markvoelker has joined #openstack-meeting-409:44
*** markvoelker has quit IRC09:49
*** Jeffrey4l has quit IRC09:57
*** prithiv has joined #openstack-meeting-410:02
*** yuli_s has left #openstack-meeting-410:02
*** zeih has quit IRC10:21
*** vikram___ has joined #openstack-meeting-410:23
*** javeriak has quit IRC10:23
*** javeriak has joined #openstack-meeting-410:24
*** mohankumar has quit IRC10:33
*** baohua has joined #openstack-meeting-410:34
*** GB21 has quit IRC10:47
*** xingchao has quit IRC10:49
*** zeih has joined #openstack-meeting-410:51
*** xingchao has joined #openstack-meeting-410:55
*** vikram___ has quit IRC10:59
*** xingchao has quit IRC11:03
-openstackstatus- NOTICE: Gate on project-config is currently broken due to IRC tests. The problem has been detected and we are working to fix the issue as soon as possible.11:14
*** banix has joined #openstack-meeting-411:15
*** banix has quit IRC11:18
*** prithiv has quit IRC11:19
*** rtheis has joined #openstack-meeting-411:26
*** mohankumar has joined #openstack-meeting-411:26
*** mohankumar has quit IRC11:31
*** dave-mccowan has joined #openstack-meeting-411:40
*** GB21 has joined #openstack-meeting-411:41
*** javeriak has quit IRC11:41
*** mohankumar has joined #openstack-meeting-411:43
*** markvoelker has joined #openstack-meeting-411:46
*** GB21 has quit IRC11:49
*** GB21 has joined #openstack-meeting-411:51
*** thorst has joined #openstack-meeting-411:51
*** markvoelker has quit IRC11:51
*** tojuvone has joined #openstack-meeting-411:54
*** tojuvone has quit IRC11:55
*** tojuvone has joined #openstack-meeting-411:56
*** _tojuvone has joined #openstack-meeting-412:06
*** _tojuvone has quit IRC12:09
*** zeih has quit IRC12:12
*** javeriak has joined #openstack-meeting-412:12
*** numans has quit IRC12:16
*** numans has joined #openstack-meeting-412:16
*** david-lyle_ has joined #openstack-meeting-412:17
*** david-lyle has quit IRC12:17
*** GB21 has quit IRC12:17
*** GB21 has joined #openstack-meeting-412:19
*** klamath has joined #openstack-meeting-412:20
*** klamath has quit IRC12:20
*** klamath has joined #openstack-meeting-412:21
*** woodard has joined #openstack-meeting-412:27
*** woodard has quit IRC12:27
*** vikram___ has joined #openstack-meeting-412:27
*** woodard has joined #openstack-meeting-412:28
*** salv-orl_ has joined #openstack-meeting-412:28
*** salv-orlando has quit IRC12:31
*** mbound has quit IRC12:34
*** banix has joined #openstack-meeting-412:34
*** mbound has joined #openstack-meeting-412:36
*** GB21 has quit IRC12:38
*** baoli has joined #openstack-meeting-412:39
*** baoli has quit IRC12:39
*** baoli has joined #openstack-meeting-412:39
*** zeih has joined #openstack-meeting-412:39
*** woodard has quit IRC12:40
*** woodard has joined #openstack-meeting-412:42
*** markvoelker has joined #openstack-meeting-412:47
*** neelashah has joined #openstack-meeting-412:49
*** javeriak has quit IRC12:49
*** javeriak has joined #openstack-meeting-412:50
*** javeriak has quit IRC12:51
*** markvoelker has quit IRC12:51
*** vhoward has joined #openstack-meeting-412:52
*** ninag has joined #openstack-meeting-412:53
*** baoli_ has joined #openstack-meeting-412:54
*** sdague has joined #openstack-meeting-412:56
*** baoli has quit IRC12:57
*** cdent has joined #openstack-meeting-412:58
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Mar 30 13:00:16 2016 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
alex_xuwho is here today?13:00
cdento/13:00
sdagueo/13:00
tojuvoneHi13:00
*** zhurong has quit IRC13:01
*** dtardivel has joined #openstack-meeting-413:01
alex_xuok, today is quiet13:01
alex_xulet's start the meeting13:02
alex_xu#topic Nova Microversion testing in Tempest13:02
*** openstack changes topic to "Nova Microversion testing in Tempest (Meeting topic: nova api)"13:02
oomichihi13:02
alex_xugmann isn't here, but looks like good progress13:02
edleafeo/13:02
alex_xui think we can skip this now, let's go next13:03
*** andymaier has joined #openstack-meeting-413:03
alex_xu#topic API ref doc13:03
*** openstack changes topic to "API ref doc (Meeting topic: nova api)"13:03
* edleafe is split between meeting and phone13:03
alex_xusdague: I added topic at here, do you want to track the work from now?13:03
sdaguesure, that sounds like a good plan13:03
alex_xuI see you begin to restack the patches13:03
sdaguehere is where we stand13:04
sdaguethe giant WIP stream is now a 2 patch series in nova13:04
sdaguehttps://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:wip_api_docs213:04
*** annegentle has joined #openstack-meeting-413:04
sdaguethe first patch is the infrastructure, which includes the sphinx extension13:04
sdaguethe second patch is content for servers & versions13:05
sdaguethe api-ref build publish jobs are now a thing13:05
sdagueso with https://review.openstack.org/#/c/298763/13:05
sdagueyou can see the built api-ref - http://docs-draft.openstack.org/63/298763/4/check/gate-nova-api-ref/6983838//api-ref/build/html/13:05
alex_xuso cool we already have job at here13:06
sdagueyes, that was done yesterday13:06
sdagueit doesn't publish anywhere on merge yet13:06
sdaguebut we can see what the output will be13:06
alex_xusdague: cool, what is next plan?13:06
sdaguethose 2 changes should probably get reviewed for real, and we should land something13:07
sdaguenext up, auggy, annegentle, and karen are working on the wadl2rst converter13:07
sdagueso hopefully in a week or two we could bulk import most of the data13:07
alex_xumaybe we should change the topic name, it make people it still in WIP13:07
sdaguethen do fixups13:08
oomichisdague: after your patch, we will remove the content of nova api from api-site repo, right?13:08
alex_xusdague: cool, import the *.rst parameters.yaml, right?13:08
sdagueoomichi: after we get the entire thing working and publishing13:08
sdagueoomichi: I expect the cut over to be after Austin for sure13:09
oomichisdague: ok, I got the point13:09
sdagueI expect once we get the bulk import of data we're going to need to do a week long doc sprint to fix things that didn't convert properly13:09
*** vtech has joined #openstack-meeting-413:10
alex_xu++13:10
johnthetubaguycool, thats looking awesome, so we have the framework and example up, so we can then add in the details afterwards13:10
sdaguejohnthetubaguy: right, that was the attempt13:10
sdagueit demonstrates this as multiple rst files13:10
sdaguewhich is how I expect we'll manage it13:10
oomichiyeah, nice steps for moving forward13:11
*** cloudtrainme has joined #openstack-meeting-413:11
sdagueso, next steps, please review those so we can have the framework and initial data in tree13:11
* edleafe applauds sdague 13:11
*** brunograz has joined #openstack-meeting-413:11
* alex_xu begin to review from tomorrow13:12
johnthetubaguyis the plan to later extract the plugin to the docutils I guess?13:12
sdaguejohnthetubaguy: yes, once we get all the formatting quirks sorted out13:12
johnthetubaguysdague: cool13:12
sdagueright now it's going to be easier to fix things if it stays in tree13:13
sdaguebecause once we extract it, we'll have to cut releases of the extension for it to be used by projects13:13
johnthetubaguyyeah, sounds like totally the right call13:13
johnthetubaguyI am thinking along similar lines for the feature classification matrix plugin13:13
sdaguemy expectation is that we'll extract it during second milestone13:13
*** brunograz has left #openstack-meeting-413:14
*** pmesserli has joined #openstack-meeting-413:14
sdagueok, I think that's about it on that front. We're making good progress.13:15
alex_xusdague: thanks for making this forward13:15
alex_xuif no more question, we will move to next topic13:15
alex_xu#topic open13:16
*** mbound has quit IRC13:16
*** openstack changes topic to "open (Meeting topic: nova api)"13:16
alex_xulet's talk about newton works13:16
alex_xu#link https://etherpad.openstack.org/p/newton-nova-api-ideas13:16
*** mbound has joined #openstack-meeting-413:17
johnthetubaguyit sounds like we have our work cut out with microversion docs and testing, once we have the above stuff in place?13:17
cdentI have a gabbi-related spec for api testing that I'll add to the etherpad13:17
*** annegentle has quit IRC13:17
sdagueI think that after API docs, the top user features would be discoverable policy and structured errors13:18
*** woodard_ has joined #openstack-meeting-413:18
sdaguewhich is the things I'd want to prioritize13:18
*** obondarev has joined #openstack-meeting-413:18
*** neelashah1 has joined #openstack-meeting-413:18
*** nikhil_k has joined #openstack-meeting-413:18
alex_xuI also see something the summit ideas etherpad also13:19
alex_xu#link https://etherpad.openstack.org/p/newton-nova-summit-ideas13:19
alex_xuso...let go the api ideas etherpad first i think13:19
alex_xuhow about let us list out the thing we think about for newton?13:19
*** obondarev_ has quit IRC13:19
alex_xuam i still online?13:19
sdaguealex_xu: yeh, it was just delayed for a minute13:19
*** neelashah has quit IRC13:19
*** oomichi has quit IRC13:19
alex_xuok...network delay13:19
*** nikhil has quit IRC13:19
*** oomichi has joined #openstack-meeting-413:19
alex_xusdague: yes, looks like discoverable policy on the top13:20
johnthetubaguysdague: +1 your points there around policy and errors being the big things13:20
sdagueI'll be honest, I'm not super excited about swapping out test infrastructures given the amount of churn that ends up being13:20
*** woodard has quit IRC13:20
sdaguedoing something in parallel might be fine to demonstrate13:20
johnthetubaguyerror wise, were we thinking about fixing up instance actions, or starting something more task-ey?13:20
cdentyeah, my preference would not be to replace the api-samples, but to augment13:20
cdentI've just added a link on the spec to somewhere I'm using it for tdd13:21
sdaguecdent: yeh, I think that's fine as a low priority background thing during the cycle. Though it does make another dsl people need to remember during reviews.13:21
sdaguejohnthetubaguy: error wise, there is a spec from the api-wg about returning json structured errors13:21
sdagueinstead of just http status code + free form text13:22
johnthetubaguyah, I was thinking more about async error stuff13:22
sdagueso we could actually tell people more specific things like "bare metal computes don't support live migrations"13:22
sdagueinstead of 40013:22
tojuvoneThat would be neat13:22
alex_xuyes, like that13:23
sdagueit would also get us out of these odd binds about trying to put more meaning into http error codes than really exist13:23
sdagueand, we've actually found that in many of our tests we test for a condition which can be created by multiple kinds of failures, and we're actually passing for the wrong reasons13:23
sdaguehttps://github.com/openstack/api-wg/blob/master/guidelines/errors-example.json13:24
johnthetubaguyyeah, thats all good stuff too13:24
sdaguemy feeling is the way you'd implement this in Nova is to add error names out our extensions13:25
johnthetubaguyI guess I was more worried about users telling if things like a snapshot had finished, and if it was a success or not13:25
cdentfix the error message is only half the solution to that problem...13:25
sdaguejohnthetubaguy: sure, that's also a concern13:25
*** trozet has joined #openstack-meeting-413:25
johnthetubaguythats the whole task-ey thing13:25
johnthetubaguyalthough being more precise about the errors seems like a good building block for all that13:25
*** javeriak has joined #openstack-meeting-413:25
sdaguejohnthetubaguy: so, to be honest, I don't think we can do tasks until we get 3 core team members devoting the cycle to it13:26
sdaguecdent: sure, but it's also a big issue that there are times we want to communicate detailed reasons about why things are wrong, and we fail to13:26
sdagueI think laski has a spec up for discoverable policy13:27
alex_xu#link https://review.openstack.org/29015513:27
johnthetubaguyso I need to catch up with alaski as thats duplicating what I was trying with the cross project idea: https://review.openstack.org/#/c/29868613:28
johnthetubaguyalthough I think we are starting to converge on concert proposals, so thats all good13:28
sdaguejohnthetubaguy: I feel like most of the time cross project specs aren't all that useful until they are demonstrated in a project13:29
sdaguethey get too abstract quickly13:29
*** zhurong_ has joined #openstack-meeting-413:30
*** javeriak_ has joined #openstack-meeting-413:30
johnthetubaguysdague: yeah, I agree really, I just did the cross project one first as I thought there was a completing direction that was gaining more traction13:31
sdaguejohnthetubaguy: ok, no prob13:31
johnthetubaguyanyways, totally don't think we should wait for cross project agreement, lets take one for the team, and try make policy work13:31
*** javeriak has quit IRC13:32
*** javeriak_ has quit IRC13:32
*** javeriak has joined #openstack-meeting-413:32
alex_xuany more item, we care about in newton?13:32
johnthetubaguythat sounds like a good pile of stuff to focus on13:33
sdaguepolicy currently has a spec13:33
sdagueapi docs has a specless blueprint13:33
sdagueif structured errors is a thing, it probably needs a spec and an owner13:34
cdent"has a spec" sounds vaguely like "has a posse"13:34
sdague:)13:34
sdaguewell, it has a spec and an owner in laski13:34
sdagueI want to make sure that if we are agreeing on priorities, the priorities all have a driver on them13:34
cdentlaski is a posse all by himself13:34
*** salv-orl_ has quit IRC13:34
sdagueotherwise they will likely not happen13:34
sdaguecdent: ++13:34
johnthetubaguyI am interested in helping with policy, but I don't think I can take on the error stuff13:35
sdagueshould we take this conversation to the mailing list?13:35
johnthetubaguysdague: that sounds like a good idea13:36
sdaguemaybe I can summarize a proposed set of priorities, some things we should do a low priority, and what sort of things we'd need to move forward on13:36
sdagueand we can have discussion there13:36
alex_xuif structured errors is a thing and no one can help, I can help on it13:37
sdague#action sdague to put mailing list post out discussing API priorities in mitaka13:37
alex_xusdague: cool, thanks13:37
*** annegentle has joined #openstack-meeting-413:38
alex_xuanything we want to talk about in another etherpad?13:38
alex_xuit's also about policy. one more thing is flavor extra spec13:39
*** ninag has quit IRC13:39
sdague(fyi, got to drop shortly for a bit, will catch up on additional conversation in logs)13:39
alex_xuok, if no more question on priority, let's move on13:40
alex_xu#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090687.html13:40
alex_xuI have agenda, for a patch whether need microversion.13:41
*** ninag has joined #openstack-meeting-413:41
alex_xu'delete_on_termination' always false in the swap volume api, and it behaviour as when it born13:42
*** ninag has quit IRC13:42
johnthetubaguyso after you call swap volume, it breaks delete_on_termination?13:42
*** annegentle has quit IRC13:43
alex_xujohnthetubaguy: yes, delete_on_termination won't be keep, if we call it as 'break'13:43
johnthetubaguythis sounds like a bug in swap_volume, and doesn't really need a microversion13:43
johnthetubaguyso here is my thinking why...13:43
johnthetubaguyif we added a new swap volume microversion, we would probably want all API versions to not hard code delete_on_termination anyways13:44
johnthetubaguyso we may as well not add the microversion, unless we want to make it easy to discover a system that has this fix13:44
alex_xuok, if we think it is a break, i prefer just no microversion13:45
*** bobh_ has joined #openstack-meeting-413:45
*** mohankumar has quit IRC13:46
oomichithen, we will need to backport it into stables also without microversion bumps13:46
oomichithat seems good for me13:47
*** javeriak has quit IRC13:47
*** markvoelker has joined #openstack-meeting-413:48
alex_xuoomichi: backport to mitaka?13:48
johnthetubaguyoomichi: yeah, good point, its something we could backport then13:48
oomichialex_xu: yeah, I think so if we consider it as a bug13:48
*** zeih has quit IRC13:48
johnthetubaguyso I often mess up these things, but it feels like a bug13:49
alex_xumy concern it is old api, only backport to mitaka isn't enough, that is why i think we need a microversion13:49
oomichijohnthetubaguy: yeah, we faced similar situation before without microversion bump13:49
oomichialex_xu: but the latest microversions are different between releases. impossible to bump microversion due to different  versioning13:50
*** javeriak has joined #openstack-meeting-413:50
*** shangxdy has joined #openstack-meeting-413:50
alex_xuoomichi: yes13:51
alex_xuok, if people think it is right way to go, i will remove the -213:51
*** jmckind has joined #openstack-meeting-413:51
oomichiwe could have x.y.Z for this kind of thing13:51
oomichion version number13:51
oomichialex_xu: +113:52
*** markvoelker has quit IRC13:52
alex_xuok, let's move13:53
alex_xu#link https://review.openstack.org/#/c/29699513:53
tojuvoneThat's me13:53
alex_xutojuvone: yea, your turn13:53
tojuvoneso the have maintenance with time period set when it is13:53
tojuvoneand more13:54
alex_xutojuvone: the time period is just for a record? nova won't do anything based on the time period?13:54
tojuvoneas of sdague comment wanted also to have opinions about how much of this should land in Nova13:55
tojuvonetime period is at least important to owner of server. Telco use case he can prepare.. maybe there could be even oneflag more when host is really down13:55
tojuvoneTelco aplication is very keen on things effecting to server state and wants to know13:56
*** brunograz has joined #openstack-meeting-413:57
johnthetubaguyadvertising the expected maintenance window makes a lot of sense to me, but I think we should really look slightly wider at what the user needs to know13:57
johnthetubaguyI think we have the host state working in a way that can tell users when the maintenance has started and finished, but we might need to re-think a few bits of that13:58
tojuvoneAt least like when is the maintenance window palnned and when will the server be down becasue of it13:58
johnthetubaguytojuvone: can we get folks from the large operators group to review this spec?13:58
tojuvoneservice enable/disable is only for not allow scheduling, right13:58
johnthetubaguytojuvone: yes, I think we need more than that, but its a start13:58
johnthetubaguyfor example, we want new builds to go to machines that have the maintenance complete, even if that was done before the expected window started, etc, etc13:59
johnthetubaguyI think we need to sit back and look at the bigger picture a little, and see what work that generates13:59
*** jmckind has quit IRC13:59
tojuvoneyes, there is planty of more stuff.. also like what to do with servers14:00
*** Guest42028 has joined #openstack-meeting-414:00
tojuvonethey can stay on host, be removed or moved (migrate)14:00
*** vincentfrancoise has joined #openstack-meeting-414:00
*** gzhai2 has joined #openstack-meeting-414:00
alex_xuoops, sorry guys, we run out of time14:00
vincentfrancoiseo/14:00
sballe_o/14:00
alex_xu#endmeeting14:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:01
openstackMeeting ended Wed Mar 30 14:01:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
dtardivelo/14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-03-30-13.00.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-03-30-13.00.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-03-30-13.00.log.html14:01
alex_xulet move back to nova channel14:01
acabot#startmeeting watcher14:01
openstackMeeting started Wed Mar 30 14:01:10 2016 UTC and is due to finish in 60 minutes.  The chair is acabot. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: watcher)"14:01
openstackThe meeting name has been set to 'watcher'14:01
acabothello14:01
brunograzhi14:01
gzhai2hello14:01
edleafe#endmeeting\o14:01
sballe_o/14:01
acabot#info agenda https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#03.2F30.2F201614:01
edleafedoh!14:01
sballe_o/14:01
edleafe\o14:01
tkaczynskihi14:01
*** cdent has left #openstack-meeting-414:01
acabotedleafe : nice try;-)14:01
jed56(*_*)14:01
edleafeacabot: heh14:02
sballe_acabot: can you give me access to the slides?14:02
sballe_email is sleipnir012@gmail.com14:02
*** alexchadin has joined #openstack-meeting-414:02
*** marcusvrn_ has joined #openstack-meeting-414:02
alexchadinhi14:02
tpeoplesHi14:03
acabotsorry just refresh the agenda14:03
acabotand the link should work now14:03
acabot#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:03
acabot#info contributing page https://wiki.openstack.org/wiki/Watcher/Contributing#Blueprints has been updated to reflect discussions of past meetings about bugs and BPs states14:04
*** jmckind has joined #openstack-meeting-414:04
*** jinquan has joined #openstack-meeting-414:04
acabot#info a final version of slides for the OpenStack summit is available at https://docs.google.com/presentation/d/1pGaimFOkpZ66bWH8wWkc5eZLvxFovUj2V3YfZsQMKHE/edit?usp=sharing14:05
sballe_+114:05
acabotas the summit schedule is now available, we can start defining meeting times for Watcher14:05
acabotwe will be 4 people from bcom, dtardivel, vincentmahe, xavier & acabot14:06
sballe_intel will be sballe, tkaczynski and nishi14:06
acabotwho will be there from IBM ?14:07
sballe_gzhai2: are you coming too?14:07
gzhai2sballe_: No :(14:07
sballe_I asked for you to attend so I was hoping you could14:07
*** Guest42028 has quit IRC14:07
acabottpeoples: will you be at the summit ?14:08
gzhai2budget...14:08
*** seanmurphy has joined #openstack-meeting-414:08
sballe_hmmm14:08
tpeoplesacabot: jwcroppe, me, i'm guessing edleafe? plus some other people from my team since we're based in austin14:08
acabottpeoples: ok ;-)14:08
*** spotz_zzz is now known as spotz14:08
edleafeI'll be making the long journey from San Antonio...14:08
acabotok14:08
sballe_lol14:08
acabotcan we start freezing timeframes for meeting or its too early ?14:09
sballe_my family will be going ot San Antonio sightseeing while I am at OpenStack14:09
sballe_acabot: sure.14:09
tpeoples+114:09
jinquanzte will be  me14:09
sballe_acabot: I won;t be there Fri due to a personal commitement14:09
acabotI had a discussion with hvprash from walmart to set up a meeting on tuesday afternoon14:09
acabotjinquan: great to have you there14:10
sballe_acabot: Tues afternoon +114:10
sballe_acabot: do we know when the brown bag is?14:10
jinquanMy main concern is to learn  : )14:10
*** iyamahat has joined #openstack-meeting-414:10
acabotI think we can set a meeting 2 to 6pm tuesday14:10
sballe_+114:11
acabotand then plan other meetings on wednesday and thursday14:11
acabotso no Watcher meeting on monday14:11
edleafeI'll be buried in the nova design summit meetings, but will try to make some Watcher sessions14:12
acabot#info Watcher team will met at the summit on Tuesday 2-6pm in the developer lounge14:12
*** sigmavirus24_awa is now known as sigmavirus2414:12
acabotany other announcement ?14:12
acabot#topic Review Action Items14:13
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:13
*** rbak has joined #openstack-meeting-414:13
acabot#info "Achieved goal should be returned by each strategy" has been merged14:13
acabotthx for the quick review14:13
gzhai2acabot: when to merge its code?14:14
vincentfrancoisegzhai2: the specs14:14
acabotgzhai2: im speaking about the specs now14:14
gzhai2sorry.14:14
*** avarner has joined #openstack-meeting-414:14
acabotwe need reviews on https://review.openstack.org/#/c/286153/ & https://review.openstack.org/#/c/289880/14:15
acabotalexstav : thx for adding comments to your last PS14:15
acabottkaczynski : as jed56 did a lot of reviews on the scoring module, we will now review it with dtardivel14:16
dtardivel+114:16
*** markvoelker has joined #openstack-meeting-414:16
tkaczynskiacabot: thanks!14:16
acabot#action dtardivel review https://review.openstack.org/#/c/289880/14:16
acabot#action acabot review https://review.openstack.org/#/c/289880/14:16
tpeoplesacabot: for the specs that are being pushed to N, shall we abandon from the mitaka directory and add them to the newton dir?14:16
jed56tpeoples +114:17
acabottpeoples : yes we will have to do that but next week as we are still on the mitaka cycle14:17
edleafetpeoples: generally yes - just re-propose for Newton14:17
acabottpeoples: I would ask you to do it next week14:17
tpeoplesk. my point being i know my BP won't make M so... ok.14:17
jed56tkaczynski i will a review the last patchset but for me it  was good14:17
jed56:)14:18
jed56good job14:18
acabotwho wants to review https://review.openstack.org/#/c/286153/ ?14:18
*** ajmiller has joined #openstack-meeting-414:19
tkaczynskijed56 thanks :)14:19
gzhai2acabot: I can have a look.14:19
dtardivelacabot: I think we need now core reviewer on this patchset14:20
acabot#info https://review.openstack.org/#/c/283449/ was locked due to licensing issues, but finally its ok so can we merge it ?14:20
tpeoplesacabot: yes14:20
acabot#action gzhai2 review https://review.openstack.org/#/c/286153/14:20
tpeoplesacabot: spoke with joe, he was fine with it after i explained it to him, but he must not have had time to remove his -114:21
acabotsballe_ : could you please have a look at https://review.openstack.org/#/c/283449/ ? I think its important14:21
seanmurphyi can review something if you like14:21
acabot#action seanmurphy review https://review.openstack.org/#/c/283449/ thx sean ;-)14:22
seanmurphynp14:22
seanmurphyby eow?14:22
jed56acabot before to merge 283449 we should take some comments into account (   global_score = (nb_empty_nodes/nb_migrations*100) => need to handle the case when this is 0.)14:22
acabotedleafe: can we have specs merged in MItaka but implement in Newton ?14:22
edleafeGenerally, you re-propose specs that didn't get implemented in a given cycle14:23
edleafeIt's usually automatic approval14:23
acabotseanmurphy : ok so before our next meeting would be fine14:23
edleafeBut sometimes project priorities can change between cycles14:23
*** javeriak has quit IRC14:24
seanmurphyacabot: ack - will do before next meeting14:24
edleafeThe re-approval just helps assure that the old spec is still where you want to go14:24
acabotedleafe: ok thx14:24
*** mohankumar has joined #openstack-meeting-414:24
acabottpeoples: https://review.openstack.org/#/c/287019/ when do you plan to make additions ?14:25
tpeoplesacabot:  it's been on my list just haven't gotten to it yet. i'll put up a non-WIP by tomorrow14:25
acabot#action tpeoples set a non-WIP work on https://review.openstack.org/#/c/287019/14:26
acabotmoving to watcher code14:26
*** Swami has joined #openstack-meeting-414:26
acabotthe strategy from seanmurphy's team has been merged14:26
acabotcongrats to the team14:26
seanmurphycool - thanks!14:27
brunograz+114:27
acabot#info vincentfrancoise has added a lot of code on the BP "The achieved goal should be returned by each strategy"14:27
acabot#link https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/get-goal-from-strategy14:28
seanmurphywe need to take stock and see how and where we can continue to contribute further14:28
seanmurphyyou will hear more from us!14:28
acabotseanmurphy : I hope so !14:28
gzhai2acabot: do we plan to merge it in M?14:28
acabotgzhai2 : actually it is my plan14:28
acabotbut do you think the team will be able to review all the code by friday ?14:29
dtardivelgzhai2: we need reviewers :)14:29
*** javeriak has joined #openstack-meeting-414:29
gzhai2Sure. I can try and review this patch series.14:29
acabotif we want to have this BP implemented in M (it would be a great improvement), we need reviewers in the next 2 days !14:30
vincentfrancoiseFYI, I still have 2 changeset to finish and push: 1 for strategies API and the other one for the doc update14:30
tpeoplesi'll review14:30
acabotwho will be able to review this code by EOW ?14:30
vincentfrancoisewhich will make a total of 8 changesets14:30
acabot#action gzhai2 review https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/get-goal-from-strategy asap14:30
acabot#action tpeoples review https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/get-goal-from-strategy asap14:30
acabot#action dtardivel review https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/get-goal-from-strategy asap14:31
acabothttps://review.openstack.org/#/c/297556/ also needs reviews but as it is nested with the current work from vincentfrancoise, I think we will move it to N14:32
acabothttps://review.openstack.org/#/c/292188/ need a new PS as there is a merge conflict and additional reviews14:33
gzhai2i'll ask junjie14:33
gzhai2But still need another round review after it.14:33
acabot#action junjie submit a new PS for https://review.openstack.org/#/c/292188/14:34
acabotgzhai2: yes14:34
acaboton watcher client, there are 2 reviews open linked to "The achieved goal should be returned by each strategy" & "Enable strategy parameters "14:35
acabotso we already discussed them previously14:35
jinquani will review after  junjie submit a new PS for https://review.openstack.org/#/c/292188/14:35
acabot#action jinquan review https://review.openstack.org/#/c/292188/14:35
acabot#info Watcher-dashboard will be impacted by The achieved goal should be returned by each strategy implementation in Watcher, we need a contributor to work on it14:36
*** armax_ has joined #openstack-meeting-414:36
acabotif we merge this BP in M, we need to fix watcher-dashboard before the summit14:36
acabotanyone who wants to work on it ?14:37
acabotalways hard to find someone who wants to work on horizon :-D14:37
acabot#topic Blueprint/Bug Review and Discussion14:38
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:38
acabot#info RC-Final target 5 BPs & 9 bugs and is due on April 1st https://launchpad.net/watcher/+milestone/mitaka-rc-final14:38
*** armax has quit IRC14:39
*** armax_ is now known as armax14:39
acabotafter our discussion today, we can keep https://blueprints.launchpad.net/watcher/+spec/get-goal-from-strategy & https://blueprints.launchpad.net/watcher/+spec/basic-cloud-consolidation-integration14:39
acabotjinquan : what about https://blueprints.launchpad.net/watcher/+spec/select-destinations-filter ?14:39
tkaczynskiacabot: scoring module BP is not targeted?14:39
acabottkaczynski : we moved it to N last week14:40
jinquani am start coding from 29.march14:40
acabottkaczynski : did I made a mistake ?14:40
tkaczynskiacabot: I thought that we want to get BP now and implementation in N14:41
jinquani think it need take a few days for me14:41
*** baohua has quit IRC14:41
acabottkaczynski : yes sorry, what I'm focusing right now is what we have implemented in M14:41
tkaczynskiacabot: from my perspective it doesn't really matter. but I'd like to close working on the BP and start implementing it14:41
*** hdaniel has quit IRC14:41
tkaczynskiso as long as the BP will get merged soon, I'm good14:42
acabotjinquan : ok so I suppose you wont be able to deliver it before April 1st right ?14:42
*** cloudtrainme has quit IRC14:42
jinquan acabot, yes  :(14:43
acabotgzhai2: ok to move https://blueprints.launchpad.net/watcher/+spec/optimization-threshold to N ?14:43
tkaczynskisballe_: do you think we need to have scoring module BP for Mitaka?14:43
*** sdake has joined #openstack-meeting-414:44
gzhai2acabot: ok. But I want a try as this patch is not so big:)14:44
*** hogepodge has quit IRC14:44
gzhai2acabot: but it depends on progress of vincent's patch series.14:44
*** Sukhdev has joined #openstack-meeting-414:45
acabotgzhai2 : the problem I see is that we will merge vincentfrancoise code on Friday and you wont have time to integrate it before we freeze the rc-final14:45
gzhai2acabot: ok.14:45
gzhai2move to N14:45
acabot#action acabot move 3 BPs from Mitaka RC-final to Newton-114:45
jed56sorry about that gzhai214:45
*** annegent_ has joined #openstack-meeting-414:46
acabot#topic Open Discussion14:46
*** openstack changes topic to "Open Discussion (Meeting topic: watcher)"14:46
*** markvoelker has quit IRC14:46
acabotShould we split in different repos the framework code and the available strategies ?14:46
acabotas we start to have more and more strategies available on watcher, it would be nice to separate reviews from Watcher framework and strategies14:47
gzhai2currently it's ok i think.14:47
acabotwhat do you think about having a dedicated repo for strategies implementation ?14:48
gzhai2Who'll maintain the new strategy repo?14:48
acabotit will be one more repo with client and dashboard14:48
tpeoplesi'm not sure we'll get much benefit from that. i'd rather keep them together tbh, at least for the time being if nothing other than for simplicity14:49
acabotthe idea is mostly to separate concerns, reviewing strategies is very different tha watcher framework14:49
jed56the main idea is to have the "core" strategies and the others and to facilitate the "incubation"14:50
gzhai2How deep you separate them? A total new project with client/dashboard/API?14:50
tkaczynskiacabot tpeoples: I think having a separate repo for strategies will dogfood the strategy pluggability14:50
dtardivelacabot: Could we maintain only a list of available strategy into a new Watcher wiki section. Each strategy implementation will have its dedicated GIT repo, outside Watcher one.14:50
jed56maybe is to early ?14:51
tkaczynskiwe need a simple way to add strategies to watcher as plug-ins, including goals and everything14:51
seanmurphyto me this looks too decoupled14:51
acabotit would be nice to have core reviewers for strategies (not the same as the framework core)14:51
seanmurphyi think it is better to keep the together for now14:51
tpeoplesi agree with seanmurphy. maybe we can plan to discuss this at the summit?14:51
acabottpeoples : +114:51
jed56+114:51
seanmurphyi think the strategy code would soon become orphaned14:52
acabotits probably to early now, I will add it to the agenda for the summit14:52
*** javeriak has quit IRC14:52
acabotseanmurphy : its a big risk14:52
alexchadin+114:53
acabotany other open discussion for today ?14:53
dtardivelacabot: if we create a new repo, who will maintain it later ? not the core team ...14:53
acabotdtardivel : I think we need to define a specific core team for maintaining strategies14:54
acabotdtardivel : so we need more people involved ;-)14:55
*** MarkAtwood has quit IRC14:55
*** emagana has joined #openstack-meeting-414:56
*** sdake_ has joined #openstack-meeting-414:56
jed56acabot i agree14:56
acabotok so thank you everyone14:57
acabothave a good day/night14:57
tkaczynskibye14:57
*** rbak_ has joined #openstack-meeting-414:57
*** sdake has quit IRC14:57
gzhai2thank you acabot14:57
vincentfrancoisebye14:57
acabot#endmeeting14:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:57
openstackMeeting ended Wed Mar 30 14:57:40 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-03-30-14.01.html14:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-03-30-14.01.txt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-03-30-14.01.log.html14:57
jed56bye14:57
*** gzhai2 has left #openstack-meeting-414:58
*** jinquan has left #openstack-meeting-414:58
*** ninag has joined #openstack-meeting-414:58
*** yamahata has joined #openstack-meeting-414:58
*** emagana has quit IRC14:58
*** rbak has quit IRC14:59
*** nkrinner has quit IRC15:00
*** emagana has joined #openstack-meeting-415:00
*** emagana has quit IRC15:01
*** emagana has joined #openstack-meeting-415:01
*** annegent_ has quit IRC15:02
*** numans has quit IRC15:05
*** alexchadin has quit IRC15:06
*** anilvenkata has quit IRC15:06
*** sdake has joined #openstack-meeting-415:08
*** minwang2 has joined #openstack-meeting-415:10
*** sdake_ has quit IRC15:10
*** xingchao has joined #openstack-meeting-415:14
*** vishwanathj_zzz is now known as vishwanathj15:16
*** vincentfrancoise has left #openstack-meeting-415:16
*** blahRus has joined #openstack-meeting-415:19
*** lrensing has joined #openstack-meeting-415:20
*** annegentle has joined #openstack-meeting-415:22
*** galstrom_zzz is now known as galstrom15:22
*** javeriak has joined #openstack-meeting-415:23
*** askb_ has joined #openstack-meeting-415:25
*** Sukhdev has quit IRC15:25
*** Sukhdev has joined #openstack-meeting-415:26
*** zeih has joined #openstack-meeting-415:26
*** javeriak_ has joined #openstack-meeting-415:26
*** askb_ has quit IRC15:27
*** askb_ has joined #openstack-meeting-415:27
*** askb has quit IRC15:28
*** javeriak has quit IRC15:28
*** annegentle has quit IRC15:28
*** markvoelker has joined #openstack-meeting-415:29
*** askb_ has quit IRC15:29
*** askb_ has joined #openstack-meeting-415:29
*** askb_ has quit IRC15:31
*** askb_ has joined #openstack-meeting-415:31
*** cloudtrainme has joined #openstack-meeting-415:32
*** minwang2 has quit IRC15:32
*** matrohon has quit IRC15:32
*** askb_ has quit IRC15:32
*** askb_ has joined #openstack-meeting-415:33
*** SimonChung1 has quit IRC15:33
*** javeriak_ has quit IRC15:33
*** javeriak has joined #openstack-meeting-415:34
*** minwang2 has joined #openstack-meeting-415:34
*** xingchao has quit IRC15:34
*** askb_ has quit IRC15:35
*** askb_ has joined #openstack-meeting-415:35
*** galstrom is now known as galstrom_zzz15:35
*** Sukhdev has quit IRC15:35
*** askb_ has quit IRC15:37
*** sridhar_ram has joined #openstack-meeting-415:37
*** askb_ has joined #openstack-meeting-415:37
*** seanmurphy has quit IRC15:38
*** iyamahat has quit IRC15:38
*** yamahata has quit IRC15:38
*** askb_ has quit IRC15:38
*** askb_ has joined #openstack-meeting-415:39
*** jschwarz has quit IRC15:39
*** MarkAtwood has joined #openstack-meeting-415:39
*** seanmurphy has joined #openstack-meeting-415:41
*** armax has quit IRC15:41
*** armax has joined #openstack-meeting-415:42
*** askb_ has quit IRC15:44
*** vikram___ has quit IRC15:44
*** MarkAtwood has quit IRC15:45
*** piet has joined #openstack-meeting-415:46
*** annegentle has joined #openstack-meeting-415:46
*** prashantD has joined #openstack-meeting-415:48
*** annegentle has quit IRC15:51
*** azbiswas has joined #openstack-meeting-415:52
*** azbiswas has joined #openstack-meeting-415:52
*** uck has joined #openstack-meeting-415:53
*** Sukhdev has joined #openstack-meeting-415:54
*** mohankumar has quit IRC15:55
*** iyamahat has joined #openstack-meeting-416:00
*** yamahata has joined #openstack-meeting-416:00
*** dslevin has joined #openstack-meeting-416:00
*** dslevin has quit IRC16:00
*** salv-orlando has joined #openstack-meeting-416:02
*** dslevin has joined #openstack-meeting-416:02
*** Rockyg has joined #openstack-meeting-416:03
*** MarkAtwood has joined #openstack-meeting-416:03
*** dslevin has quit IRC16:03
*** annegentle has joined #openstack-meeting-416:03
*** zeih has quit IRC16:03
*** dslevin has joined #openstack-meeting-416:04
*** irenab has quit IRC16:04
*** dslevin has quit IRC16:04
*** annegentle has quit IRC16:05
*** dslevin has joined #openstack-meeting-416:06
*** irenab has joined #openstack-meeting-416:06
*** dslevin has quit IRC16:06
*** zeih has joined #openstack-meeting-416:06
*** dslevin has joined #openstack-meeting-416:08
*** dslevin has quit IRC16:09
*** dslevin has joined #openstack-meeting-416:10
*** dslevin has quit IRC16:10
*** dslevin has joined #openstack-meeting-416:11
*** salv-orlando has quit IRC16:11
*** dslevin has quit IRC16:12
*** SimonChung has joined #openstack-meeting-416:18
*** brunograz has quit IRC16:18
*** seanmurphy has quit IRC16:19
*** openstack has joined #openstack-meeting-417:06
*** ChanServ sets mode: +o openstack17:06
*** annegentle has joined #openstack-meeting-417:07
*** MarkAtwood has quit IRC17:07
*** fawadkhaliq has quit IRC17:10
*** vtech has quit IRC17:10
*** fawadkhaliq has joined #openstack-meeting-417:11
*** vishnoianil has joined #openstack-meeting-417:11
*** ihrachys has quit IRC17:12
*** MarkAtwood has joined #openstack-meeting-417:13
*** MarkAtwood has quit IRC17:14
*** harshs has joined #openstack-meeting-417:16
*** prashantD_ has joined #openstack-meeting-417:17
*** xiaohhui has quit IRC17:19
*** wenchma has quit IRC17:19
*** shangxdy has quit IRC17:19
*** prashantD_ has quit IRC17:19
*** prashantD has quit IRC17:20
*** prashantD_ has joined #openstack-meeting-417:20
*** MarkAtwood has joined #openstack-meeting-417:21
*** sambetts is now known as sambetts|afk17:22
*** vtech has joined #openstack-meeting-417:22
*** minwang2 has joined #openstack-meeting-417:23
*** degorenko is now known as _degorenko|afk17:25
*** unicell has joined #openstack-meeting-417:29
*** wenchma has joined #openstack-meeting-417:29
*** piet has quit IRC17:30
*** pc_m has joined #openstack-meeting-417:30
*** SimonChung has quit IRC17:33
*** salv-orlando has joined #openstack-meeting-417:33
*** SimonChung has joined #openstack-meeting-417:33
* HenryG waits patiently for dougwig17:33
*** mohankumar has joined #openstack-meeting-417:34
*** MarkAtwood has quit IRC17:34
*** xiaohhui has joined #openstack-meeting-417:35
*** nikhil_k is now known as nikhil17:35
*** MarkAtwood has joined #openstack-meeting-417:36
*** salv-orlando has quit IRC17:40
kevinbenton@dougwig get out of bed #mondays #catpictures17:40
dougwigugh, sorry17:40
dougwig#startmeeting networking_lib17:40
openstackMeeting started Wed Mar 30 17:40:53 2016 UTC and is due to finish in 60 minutes.  The chair is dougwig. Information about MeetBot at http://wiki.debian.org/MeetBot.17:40
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:40
*** openstack changes topic to " (Meeting topic: networking_lib)"17:40
openstackThe meeting name has been set to 'networking_lib'17:40
dougwigi clicked away the calendar reminder and everything17:41
dougwig#topic the db patch17:41
*** openstack changes topic to "the db patch (Meeting topic: networking_lib)"17:41
dougwigwhere are we, HenryG ?17:41
kevinbentonBoise and San Jose17:41
HenryGI am finishing up some test cases, but the patch should be usable. Have you tried it?17:42
kevinbentonThis is the pagination patch?17:42
*** sdake has quit IRC17:42
HenryGno, https://review.openstack.org/26721417:43
dougwigcan we fit that into 0.1.0, or will that be rushing things?17:43
*** jmckind has quit IRC17:43
HenryGI moved some things into private modules, so the code can be published but only experimeters can try it out.17:44
HenryGBut please review the non-private modules to see if they are safe to go in 0.1.0.17:45
dougwigok, so that + pagination, then we can do 0.1.0 and be ready for a g-r patch next week.17:45
dougwigwill do17:45
*** klamath has quit IRC17:47
*** MarkAtwood has quit IRC17:47
*** annegentle has quit IRC17:48
*** MarkAtwood has joined #openstack-meeting-417:48
dougwiganything else for this morning?  i've been sucked into an lbaas driver thing, so i have no progress to report.17:48
*** Sukhdev has quit IRC17:48
HenryGJust want to mention I am pushing patches for switching the neutron code to use lib constants and exceptions.17:49
*** fawadkhaliq has quit IRC17:49
HenryGOne big patch for core neutron so far.17:49
*** annegentle has joined #openstack-meeting-417:50
kevinbentonYay17:50
HenryGPatches for *aaS coming soon.17:50
*** piet has joined #openstack-meeting-417:50
HenryGBetween now and the summit is probably the best time to get these conflict generators merged?17:50
dougwigor just after, yes17:51
*** fawadkhaliq has joined #openstack-meeting-417:51
HenryGThat's all from me17:52
*** MarkAtwood has quit IRC17:52
*** neelashah1 has quit IRC17:53
HenryGI think we should have a neutron-lib code sprint this summer, somewhere nice.17:57
*** s3wong has joined #openstack-meeting-418:00
*** unicell has quit IRC18:02
*** cloudtrainme has quit IRC18:02
*** unicell has joined #openstack-meeting-418:02
dougwigHenryG: i like that idea.18:03
dougwig#endmeeting18:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:03
openstackMeeting ended Wed Mar 30 18:03:49 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:03
*** ninag has quit IRC18:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-03-30-17.40.html18:03
*** annegentle has quit IRC18:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-03-30-17.40.txt18:03
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-03-30-17.40.log.html18:03
*** piet has quit IRC18:07
*** pc_m has left #openstack-meeting-418:07
*** piet has joined #openstack-meeting-418:07
*** piet has quit IRC18:11
*** piet has joined #openstack-meeting-418:11
*** neelashah has joined #openstack-meeting-418:12
*** klamath has joined #openstack-meeting-418:14
*** seanmurphy has joined #openstack-meeting-418:15
*** rbak_ has joined #openstack-meeting-418:19
*** fawadkhaliq has quit IRC18:22
*** fawadkhaliq has joined #openstack-meeting-418:23
*** sridhar_ram has quit IRC18:25
*** davidlenwell has quit IRC18:27
*** zeih has joined #openstack-meeting-418:28
*** SumitNaiksatam has joined #openstack-meeting-418:28
*** baohua has joined #openstack-meeting-418:29
*** piet has quit IRC18:29
*** baoli_ has quit IRC18:30
*** baohua has quit IRC18:33
*** sigmavirus24 is now known as sigmavirus24_awa18:34
*** davidlenwell has joined #openstack-meeting-418:34
*** annegentle has joined #openstack-meeting-418:35
*** piet has joined #openstack-meeting-418:35
*** sigmavirus24_awa is now known as sigmavirus2418:35
*** cloudtrainme has joined #openstack-meeting-418:36
*** numans has joined #openstack-meeting-418:38
*** piet has quit IRC18:38
*** piet has joined #openstack-meeting-418:38
*** Sukhdev has joined #openstack-meeting-418:44
*** krotscheck is now known as krotscheck_dcm18:46
*** javeriak has quit IRC18:49
*** piet has quit IRC18:50
*** piet has joined #openstack-meeting-418:50
*** yamamoto has quit IRC18:53
*** ninag has joined #openstack-meeting-418:53
*** piet has quit IRC18:56
*** sdake has joined #openstack-meeting-418:57
*** piet has joined #openstack-meeting-418:58
*** MarkAtwood has joined #openstack-meeting-418:58
*** cloudtrainme has quit IRC19:00
*** jmckind has joined #openstack-meeting-419:02
*** uck has quit IRC19:02
*** uck has joined #openstack-meeting-419:03
*** DevonBoatwright has joined #openstack-meeting-419:03
*** DevonBoatwright has left #openstack-meeting-419:03
*** salv-orlando has joined #openstack-meeting-419:03
*** Rockyg has quit IRC19:03
*** baoli has joined #openstack-meeting-419:05
*** MarkAtwood has quit IRC19:13
*** mohankumar has quit IRC19:19
*** piet has quit IRC19:20
*** piet has joined #openstack-meeting-419:21
*** fawadkhaliq has quit IRC19:28
*** fawadkhaliq has joined #openstack-meeting-419:28
*** Sukhdev has quit IRC19:44
*** spotz is now known as spotz_zzz19:44
*** baoli has quit IRC19:47
*** mbound has joined #openstack-meeting-419:48
*** dtardivel has quit IRC19:48
*** baoli has joined #openstack-meeting-419:49
*** baoli has quit IRC19:49
*** baoli has joined #openstack-meeting-419:50
*** piet has quit IRC19:51
*** klamath has quit IRC19:52
*** rockyg has joined #openstack-meeting-419:53
*** yamamoto has joined #openstack-meeting-419:53
*** zeih_ has joined #openstack-meeting-419:54
*** fawadkhaliq has quit IRC19:55
*** angdraug has joined #openstack-meeting-419:55
rockygping rbradfor dhellmann jokke_ bknudson for log_wg19:56
rbradforrockyg, hi.19:57
rockygHey.  this should be a quick one19:57
*** hdaniel has joined #openstack-meeting-419:58
*** zeih__ has joined #openstack-meeting-419:59
*** sdake_ has joined #openstack-meeting-420:00
*** zeih_ has quit IRC20:00
rockyg#startmeeting log_wg20:00
openstackMeeting started Wed Mar 30 20:00:51 2016 UTC and is due to finish in 60 minutes.  The chair is rockyg. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: log_wg)"20:00
openstackThe meeting name has been set to 'log_wg'20:00
rockyg#topic summit planning20:01
*** openstack changes topic to "summit planning (Meeting topic: log_wg)"20:01
*** baoli has quit IRC20:01
rbradforare there any sessions scheduled?20:01
rockygSo far, I've been pretty low key about log stuff for this summit.  The config stuff is critical and will go a long ways on lots of areas20:02
*** piet has joined #openstack-meeting-420:02
rockygBut, what, if anything, do we want to get done at the summit?20:02
*** sdake has quit IRC20:02
rockygCertainly, I'd like to recruit folks.  And meet rbradfor    jokke_  will not be there, so you can't meet him.20:02
*** annegentle has quit IRC20:03
*** yamamoto has quit IRC20:03
rbradforlogging in itself is not a standalone thing, how logging affects operators (so monday is ops day), and how logging may affect cross projects or oslo is where I'd expect to hear about it.20:03
rockygYup.  So, what would be a good focus this round for the Ops summit?  I've gotta submit shortly20:04
rockygI will get it if I propose it.20:04
rbradforThe Oslo planning is at https://etherpad.openstack.org/p/newton-oslo-summit-planning20:05
*** fawadkhaliq has joined #openstack-meeting-420:05
rbradforthere is a proposal for mutable logging listed (but driver is not attending)20:05
rockygThere is also a taxonomy of failures that is also happening in Ops.  Log issues will likely arise there, too.20:05
rockygThe ops summit planning etherpad is:  https://etherpad.openstack.org/p/AUS-ops-meetup20:06
rockyg#link https://etherpad.openstack.org/p/AUS-ops-meetup20:06
rockyg#link https://etherpad.openstack.org/p/newton-oslo-summit-planning20:06
rbradforI am planning on attending the ops summit sessions20:07
rockygCool.  And we should get an oslo session.  I'm thinking the right way to start on Error codes and even on the request id stuff is to get the fields added to oslo.log for them20:08
rockygSo what would be a good log topic for the ops summit?20:09
rbradforfor work I'm hoping to focus on, I either have a detailed etherpad (e.g. adoption), or have created specs that can be reviewed and commented on for discussion before austin.20:09
rockygYup.  I'm hoping to create the oslo spec and have a few round with you and maybe others before the summit20:10
rockygFor ops, it's usually more info gathering and dissemination20:10
*** numans has quit IRC20:10
*** angdraug has quit IRC20:12
rockygI'm thinking maybe a discussion of unhandled exceptions for Ops-logging?  Find out if we could clean up logging by handling some of the most common ones?20:12
*** leo_wang has quit IRC20:12
*** angdraug has joined #openstack-meeting-420:13
*** angdraug has quit IRC20:13
*** hdaniel has quit IRC20:13
rockygWhat would you like to learn from Ops?20:14
*** piet has quit IRC20:14
rbradforI'm interested in just hearing what are pain points across deployment and usage, and try to determine if these are Oslo related, and see I can provide input into how these things could move along20:15
rbradforI have yet been able to actually talk with a production operator.20:17
rockygWe could do that. Logging pain points review then drill into top, or exceptions (that was a biggie last time.  It dumps sometimes multi-gig lines into log files)20:17
rbradforyou are mentioned this, but I've never seen any actual examples.20:17
rockygI'll make sure that happens.  But just turning up, you'll meet a ton of them.20:17
*** banix_ has joined #openstack-meeting-420:17
rockygYou should also present/moderate a session on config options.  I can help if you like, but I think once you get started, I'm not needed.  If ever needed.20:18
rockygI did a session on the nova effort at the midcycle20:19
*** banix has quit IRC20:19
*** pleia2 has quit IRC20:19
*** banix_ is now known as banix20:19
*** pleia2 has joined #openstack-meeting-420:20
rockygOh, and I'm still confused about the syslog opts in oslo.log.  The descriptions seem to indicate it went away?????20:20
rockygLots of ops use it.20:20
rockygI'll have an intern for the summer, so I can get lots of stuff done.20:20
*** annegentle has joined #openstack-meeting-420:21
rbradforI'm not familiar with the details, I need to experiement with syslog info. syslog is still an option, it was a specific syslog format that was deprecated and removed.20:21
rockygWhich is why it would be good to get either oslo or cross project spec in decent shape for him/her20:21
rockygAh.  The doc code needs to be clearer on that.20:22
rockygHow about I throw an etherpad together with the oslo log format items I want and we iterate a bit on that before submission to gerrit?20:23
*** sridhar_ram has joined #openstack-meeting-420:23
rbradforsure20:23
rockygAnd we can talk about that at an oslo summit session.20:24
*** fawadkhaliq has quit IRC20:24
rbradforfeel free to add it to the Oslo etherpad quickly. I know Josh is scheduling now.20:24
rockygNow I've promissed something so I have to do it.20:24
rockygI'll add after this meeting20:25
*** fawadkhaliq has joined #openstack-meeting-420:25
*** spzala has joined #openstack-meeting-420:25
rockygand add some comments.20:26
*** ninag has quit IRC20:26
rockygon other proposed sessions, that is....20:26
rockygI think that covers it.  Anything else?  Can I add config options to ops summit with your name on it?20:27
*** zeih__ has quit IRC20:27
rockygOr will you???20:27
rockygIf you moderate, I'll take notes on the etherpad20:28
rbradforI see nobody has mentioned config options, so it's not my place to add this.20:29
*** delattec has joined #openstack-meeting-420:29
rbradforshould there be need to discuss I can be available to discuss20:30
rockygAnyone can add.  It's pretty much unconference style.  The person who wants it/wants to do it puts it up and others vote.20:30
rbradformy goal is to attend the ops summit, listen, learn and contribute when applicable20:31
rockygSo, I put up the taxonomy discussion and all those +1s was to express interest.  Don't ask for permission, seek agreement :)20:31
*** cdelatte has quit IRC20:31
rockygOK.  I'll put up a config session and make you attend and ask questions.20:31
rockygSorry.  But, There is *lots* of interest in getting them fixed and debate about global config sections or not.20:32
*** angdraug has joined #openstack-meeting-420:32
rockygEspecially when you have multi-cloud.20:32
*** sdake has joined #openstack-meeting-420:32
*** delatte has joined #openstack-meeting-420:32
rbradforok, well as you say, if people express interest then we can talk more about it20:32
rockygWill do.20:33
rockygI think thats about it?  I have action items:20:33
*** sdake_ has quit IRC20:33
rockyg#action add logging to oslo planning etherpad20:33
rockyg#action add config opts to Ops planning etherpad20:34
rockyg#action start etherpad for logging format enhancements20:34
rbradforcool20:34
*** delattec has quit IRC20:34
rockygAre we done for this meeting?20:34
rbradforI've nothing more to note. I'll await your etherpads20:35
rockygThanks.  I'll get to it then:)20:35
rockyg3endmeeting20:35
rockyg#endmeeting20:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:35
openstackMeeting ended Wed Mar 30 20:35:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-03-30-20.00.html20:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-03-30-20.00.txt20:35
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-03-30-20.00.log.html20:35
*** woodard_ has quit IRC20:39
*** MarkAtwood has joined #openstack-meeting-420:39
*** klamath has joined #openstack-meeting-420:44
*** matrohon has joined #openstack-meeting-420:45
*** MarkAtwood has quit IRC20:46
*** zeih_ has joined #openstack-meeting-420:48
*** piet has joined #openstack-meeting-420:49
*** delattec has joined #openstack-meeting-420:51
*** delatte has quit IRC20:52
*** Sukhdev has joined #openstack-meeting-420:59
*** matrohon has quit IRC20:59
*** bpokorny has quit IRC21:04
*** sdague has quit IRC21:04
*** SimonChung1 has joined #openstack-meeting-421:04
*** daneyon has joined #openstack-meeting-421:04
*** SimonChung2 has joined #openstack-meeting-421:05
*** SimonChung1 has quit IRC21:05
*** rtheis has quit IRC21:05
*** SimonChung has quit IRC21:05
*** daneyon_ has quit IRC21:07
*** julim has quit IRC21:08
*** shangxdy has joined #openstack-meeting-421:09
*** seanmurphy has quit IRC21:10
*** julim has joined #openstack-meeting-421:11
*** prithiv has joined #openstack-meeting-421:11
*** thorst has quit IRC21:14
*** thorst has joined #openstack-meeting-421:15
*** zeih_ has quit IRC21:16
*** annegentle has quit IRC21:16
*** lrensing has quit IRC21:16
*** thorst_ has joined #openstack-meeting-421:17
*** thorst has quit IRC21:19
*** neelashah has quit IRC21:22
*** thorst_ has quit IRC21:22
*** annegentle has joined #openstack-meeting-421:25
*** Sukhdev has quit IRC21:29
*** annegentle has quit IRC21:30
*** thorst has joined #openstack-meeting-421:34
*** thorst has quit IRC21:39
*** shangxdy has quit IRC21:42
*** bpokorny has joined #openstack-meeting-421:43
*** banix has quit IRC21:44
*** fawadkhaliq has quit IRC21:45
*** piet has quit IRC21:45
*** davidlenwell has quit IRC21:48
*** Sukhdev has joined #openstack-meeting-421:50
*** fawadkhaliq has joined #openstack-meeting-421:52
*** lakshmiS has quit IRC21:53
*** davidlenwell has joined #openstack-meeting-421:55
*** rockyg has quit IRC21:58
*** piet has joined #openstack-meeting-421:58
*** inc0 has joined #openstack-meeting-421:58
*** zeih has quit IRC21:59
*** spzala has quit IRC22:08
*** spzala has joined #openstack-meeting-422:08
*** brucet has joined #openstack-meeting-422:12
*** spzala has quit IRC22:13
*** bobh_ has quit IRC22:14
*** claudiub|2 has quit IRC22:16
*** annegentle has joined #openstack-meeting-422:17
*** brucet has quit IRC22:18
*** fawadkhaliq has quit IRC22:20
*** fawadkhaliq has joined #openstack-meeting-422:20
*** markvoelker has joined #openstack-meeting-422:24
*** vishwanathj has quit IRC22:27
*** sigmavirus24 is now known as sigmavirus24_awa22:27
*** mbound has quit IRC22:28
*** ajmiller has quit IRC22:28
*** ajmiller has joined #openstack-meeting-422:30
*** sshnaidm has quit IRC22:30
*** unicell has quit IRC22:32
*** SimonChung2 has quit IRC22:32
*** SimonChung has joined #openstack-meeting-422:32
*** unicell1 has joined #openstack-meeting-422:32
*** fawadkhaliq has quit IRC22:34
*** sshnaidm has joined #openstack-meeting-422:36
*** fawadkhaliq has joined #openstack-meeting-422:37
*** jmckind has quit IRC22:37
*** delatte has joined #openstack-meeting-422:44
*** spzala has joined #openstack-meeting-422:44
*** sdake has quit IRC22:46
*** sdake has joined #openstack-meeting-422:46
*** delattec has quit IRC22:47
*** SimonChung1 has joined #openstack-meeting-422:49
*** SimonChung has quit IRC22:49
*** asalkeld_ has joined #openstack-meeting-422:55
*** markvoelker has quit IRC22:57
*** Jeffrey4l has joined #openstack-meeting-422:59
*** piet has quit IRC22:59
*** spotz_zzz is now known as spotz22:59
*** prithiv1 has joined #openstack-meeting-423:00
*** prithiv has quit IRC23:00
sdake#startmeeting kolla23:00
openstackMeeting started Wed Mar 30 23:00:47 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.23:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:00
*** openstack changes topic to " (Meeting topic: kolla)"23:00
openstackThe meeting name has been set to 'kolla'23:00
sdake#topic rollcall23:00
*** openstack changes topic to "rollcall (Meeting topic: kolla)"23:00
asalkeld_o/23:00
sdake\o/23:00
akwasniehi23:00
inc0o/23:01
Jeffrey4lo/23:01
*** vhosakot has joined #openstack-meeting-423:02
vhosakoto/23:03
*** annegentle has quit IRC23:03
*** thorst has joined #openstack-meeting-423:03
*** gmmaha has joined #openstack-meeting-423:03
sdake#topic annouoncements23:03
*** openstack changes topic to "annouoncements (Meeting topic: kolla)"23:03
sdakeour agenda is here:23:04
sdake#link https://wiki.openstack.org/wiki/Meetings/Kolla#Agenda_for_next_meeting23:04
sdake1. sam has dropped off the core reviewer team of his own accord.  If he is lilke most peple he probably values his privacy and may not want to be questioned about it.23:05
*** emagana has quit IRC23:05
inc0he will be missed :(23:05
*** blahRus has quit IRC23:05
sdakesam's contributions have been super valuable to kolla and I wish him well in the future23:06
sdakeIf the core team wants to wish him well as well, I thnk that would be appropriate.23:06
sdake2. the irc channel has moved to #openstack-kolla23:06
*** ntpttr has joined #openstack-meeting-423:06
Jeffrey4lmiss him.23:06
*** prithiv has joined #openstack-meeting-423:07
sdake3. the gate which was busted is now fixed for the most part in correct fashions for master and soon mitaka - keep the patches coming23:07
vhosakotthe doc gate is still flaky23:07
sdake4. we have a vote on how to manage the backports underway - please vote.23:08
sdake5. we have a core reviewer nomination under way - please vote.23:08
sdakeany announcements from the community?23:08
*** prithiv1 has quit IRC23:08
*** sridhar_ram has quit IRC23:08
*** emagana has joined #openstack-meeting-423:09
sdake#topic Liberty backport planning23:09
*** openstack changes topic to "Liberty backport planning (Meeting topic: kolla)"23:09
sdakeinc0 all yours23:09
inc0well23:09
inc0https://review.openstack.org/#/c/299563/23:09
inc0so we need a plan23:09
inc0I'm working on getting mitaka code deploying liberty23:09
inc0and got it to work in prototype fashion23:09
*** andymaier has quit IRC23:09
inc0obviously this is ugly and I need to work on it a bit more, but here it is23:10
inc0question - what are we doing with this code?23:10
inc0I see 2 options23:10
inc01. We keep it master and effectively abandon mitaka23:10
inc0liberty* branch23:10
inc02. we backport it to liberty stable and we can remove this "deploy_liberty" nonsense23:11
inc0which means that we'll have 2 branches that will be virtually identical23:11
*** bobh_ has joined #openstack-meeting-423:11
inc0and patches that lands in mitaka will have to be backported23:11
sdakesounds like what the current vote is23:11
inc0I would guess almost all of them23:11
sdakei htink what this means is backporting is effectively blocked until mitaka is released23:12
inc0I'm personally in favor of second options23:12
asalkeld_can't we keep templates for major openstack version in tree23:12
sdaketo make a nice tidy backport process23:12
*** fawadkhaliq has quit IRC23:12
asalkeld_templates/mitaka/*23:12
*** rbak_ has quit IRC23:12
*** bobh_ has quit IRC23:12
asalkeld_so that one branch can at least deploy 2 or 3 releases23:13
*** emagana has quit IRC23:13
inc0well asalkeld_ truth is, our templates aren't super sophisticated (not sure if I wrote this word correctly, you get the idea)23:13
inc0which means we're good at most part23:13
sdakeasalkeld  so you mean templates ike heat-mitaka.j2 heat-liberty.j2?23:13
asalkeld_sdake: yeah (or just add a new directory for each release23:13
inc0well, I wouldn't make a habit out of it23:13
vhosakotyes.. I like 2 option as well.. why should we "make Mitaka deploy Liberty" ? does other OpenStack projects do this ? one release is made to deployed an older relase ?23:13
inc0we may get lucky now, next release mariadb will make breaking change and we're screwed23:14
*** fawadkhaliq has joined #openstack-meeting-423:14
*** sridhar_ram has joined #openstack-meeting-423:14
inc0vhosakot, so other deployment tools usually deploy previous version23:14
*** sridhar_ram has quit IRC23:14
inc0I think Fuel for example is still on Kilo23:14
*** bobh_ has joined #openstack-meeting-423:15
vhosakotMikaka Fuel dpeloys Kila ?23:15
inc0osad I think deploys master23:15
asalkeld_hard to test upgrades if you have to keep checking out different versions of the code23:15
*** Jeffrey4l_ has joined #openstack-meeting-423:15
inc0asalkeld_, but it will be more stable this way23:15
sdakewell we do want stable branches per release23:15
sdakestable/mitaka = atleast mitaka23:16
asalkeld_ok, just an idea23:16
sdakestable/liberty = atleast liberty23:16
inc0well, I think we may get lucky now23:16
inc0but I'd liek to keep 1 release per release23:16
inc0and mitaka - mitaka23:16
*** Jeffrey4l has quit IRC23:16
*** bobh_ has quit IRC23:17
inc0only reason this backport is even a thing is data_containers which were super critically horrible nuke in your own datacenter23:17
inc0and people don't like nukes in dc23:17
sdakeok well here is my thinking on the matter23:17
sdakeinc0 should continue to work on defining HOW we backport23:18
inc0so...my personal favorite is to ditch what we now call liberty, and make liberty out of master + my code once I'm done with it23:18
sdakehe has taken that on that responsibility of his own accord23:18
sdakebut as far as tming goes23:18
*** banix has joined #openstack-meeting-423:18
sdakeI'd really like to wait until Mitaka is tagged23:18
inc0fair enough23:19
sdakeafter Mitaka is tagged, Id' like to distribute the backport work throughout the core reviewr team and our respective community23:19
inc0so what I need from you guys is to help me testing23:19
sdakeso we can get it done in la week or two23:19
sdakerather then 6 months ;)23:19
inc0confirm that serviced deploys correctly and test centos23:19
sdakewe need to teset ubuntu as well23:20
vhosakotcan the backported code to Liberty be tested in gate ?23:20
inc0I'm doing everything on buntu23:20
sdakeour gate testing is weak vhosakot23:20
vhosakotcompute kit23:20
inc0vhosakot, we need to make gate out of it23:20
sdakeonly copute kit and barely that :)23:20
sdakestable/lbierty hs a gate23:20
inc0which will need to change23:21
sdakeif its the same as mitaka why change it?23:21
inc0if it's the same, then no, but is it23:21
inc0?23:21
inc0well, in any case23:21
sdakeit will be - take mitaka cp to liberty23:21
inc0we'll get it done23:22
inc0all I'm saying is, we need to make a decision on HOW23:22
sdakeyup have full confidence in inc0, he got us upgrades rolling with help from the community23:22
sdakeinc0 i prposed in the vote on the mailing list how23:22
sdakeif you think how should be different can you repropose a different thing23:22
inc0wonderful, thank you23:22
inc0I'll do that23:23
sdakeok any Q&A?23:23
*** pmesserli has quit IRC23:23
vhosakotI have Q...23:23
inc0for everyone who helps with backport, drinks are on PTL;23:24
inc0;)23:24
*** salv-orl_ has joined #openstack-meeting-423:24
sdakedrinks are on inc0 he means :)23:24
*** annegentle has joined #openstack-meeting-423:24
vhosakotwill steps to test backport be posted on etherpad ? what to test ? how to test ?23:24
* sdake needs to abuse the corproate card more23:24
inc0vhosakot, so test will be - deploy and do stuff23:24
*** rhallisey has joined #openstack-meeting-423:25
sdakethe deal is we want liberty to be the same as mitaka23:25
rhalliseyhello23:25
vhosakotis this like downloading inc0's patch set, deploy kolla, check basic sanity ?23:25
sdakeso we can leverage all the testing we have gone through23:25
sdakehey rhallisey23:25
rhalliseysrry was at the sstore23:25
inc0but I'll make sure to get it testable (is this even a word?) before we tag mitaka23:25
inc0vhosakot, yeah, pretty much, basic or more advanced, as much as you can23:25
*** prithiv has quit IRC23:26
sdakeinc0 perhaps your proposal is different then what was proposed on the ml23:26
sdakei think we need to have further discussion there23:26
*** rbak has joined #openstack-meeting-423:26
sdakethere being the ml23:26
*** salv-orlando has quit IRC23:26
rhalliseydoes that mean there more needed to be backported?23:26
rhalliseys/there/there is23:26
sdakerhallisey yes - read your email!! ;)23:26
inc0rhallisey, everything will be backported eally23:26
inc0and I mean everything23:27
*** rbak has quit IRC23:27
rhalliseyya I saw that23:27
rhalliseyI +1'd it23:27
rhalliseyunless something changed in the last 1hour23:27
* sdake reads his mail :)23:27
sdakei think inc0 hasn't read my proposal yet23:27
*** sridhar_ram has joined #openstack-meeting-423:27
Jeffrey4l_what the final solution? deploy liberty using mitaka branch Or backport mitaka branch to liberty?23:28
inc0didnt get mail yet23:28
inc0I'm for the latter23:28
sdakeJeffrey4l_ i prefer second choice23:28
Jeffrey4l_I think inc0 using the latter.23:28
*** annegentle has quit IRC23:28
Jeffrey4l_I think inc0 using the former. ( sorry for typo)23:28
Jeffrey4l_I perfer second, too.23:29
inc0Jeffrey4l_, for demo purposes23:29
inc0but I'd rather ditch conditional and make liberty a copy of mitaka with slight changes23:29
vhosakotinc0 said 2nd option  -  2. we backport it to liberty stable and we can remove this "deploy_liberty" nonsense23:29
sdakeok well unfortunately we have a poor turnout at our irc meetings at the 23:00 utc tiemslot23:30
*** cbaesema has joined #openstack-meeting-423:30
sdakeso we really need to have this discussion on the mailing list23:30
sdakeso inc0 slurp your mail and get us going ;)23:31
vhosakotis there a list of things going to be backported to Liberty.... etherpad link ?23:31
sdakeok moving on :)23:31
sdake#topic Liberty rc3 bug triage [timebox 25 minutes]23:31
*** openstack changes topic to "Liberty rc3 bug triage [timebox 25 minutes] (Meeting topic: kolla)"23:31
vhosakotsdake: is there a list of things going to be backported to Liberty23:31
sdakevhosakot perhaps we need to start that - inc0 can yout ake that up ini yuor response?23:31
inc0mail no there, bits slow, instructions unclear23:31
vhosakotcool23:32
*** Jeffrey4l__ has joined #openstack-meeting-423:32
sdakeour deadline for rc3 is friday April 1sst23:32
sdakeas in 2 days23:32
Jeffrey4l__( sorry, offlined just now)23:32
*** Jeffrey4l__ is now known as Jeffrey4l23:32
sdakeI am tagging at the last possible moment for folks to get bug fixes in23:32
*** bobh_ has joined #openstack-meeting-423:33
sdakeAfter that, Mitaka final is April 8th, 201623:33
*** Jeffrey4l_ has quit IRC23:33
sdakeso we are going to go through the painful process of bug categorization for confirmed bugs23:33
*** prithiv has joined #openstack-meeting-423:33
*** prithiv has quit IRC23:33
*** annegentle has joined #openstack-meeting-423:34
sdake#link https://launchpad.net/kolla/+milestone/mitaka-rc323:34
sdakeany bug that is New is probably a backport23:34
sdakelets ignore those23:34
sdakei'll sort those out after the meeting23:34
sdakeanythign confirmed, needs to be fixed asap23:34
asalkeld_lots there23:35
sdakeya we have a slew of bugs23:35
sdakeI really need people to focus on fixxing bugs rather then developing features23:35
sdakewe can handle about 25 bugs a week if we coordinate well23:35
sdakethat is our community capacity23:36
vhosakotthat is good bug-fixing rate23:36
sdakeyes - we have 1 week left until release23:36
sdakewe can't possibly fix all these bugs in the time frame allotted23:36
sdakeplease work on critical bugs23:37
sdakea critical bug is something that stops kolla from functioning properly in our 7 major kolla-ansible operational mdoes23:37
sdakereconfigure, ugprade, deploy, precheck, etc23:37
sdakea high bug is something that is a real probem23:37
vhosakotyes, I'm hardening the prechecks23:37
sdakeI am going to look at a ll the low bugs an bounce them on the 1st if there are not solutiosn for them23:38
sdakeI am going t o look at all the medium bugs and see if they are really low prior to that23:38
sdakewhat i need is help prioirtizing bugs23:38
*** annegentle has quit IRC23:38
sdakethe second peice of help i need is finishign the job on bugs in the in progress state23:39
sdakethe third peice of help i need is fixing bugs in the critical or high states that are unassigned23:39
sdakei will send a request to the mailing list about all of this need for help23:40
sdakebut can anyone point out any holes in this approach?23:40
sdakei'd like to make sure we deliver something that works properly23:40
vhosakotsdake: what about scale bugs related connection limit, nova scheculer with 100 VMs... ?23:41
sdakevhosakot i am looking at that now23:42
vhosakotcool23:42
sdakei would call that critical23:42
sdakeor high at minimum23:42
sdakewhat i'e seen so far with 1000 vm launch is it can't be done23:42
sdakewithout changing koll aaround23:43
sdakeat most on a 64 node clusery you can launch 50 vms23:43
*** angdraug has quit IRC23:43
sdakethat is totaly unacceptable to me ;)23:43
vhosakothow many are compute nodes ?23:43
sdakewe need  to make sure a 100 node cluster works ocrrectly for a fully loaded set of compute nodes23:43
sdake3 controller 10 stroage 87 compute at 256gb ram23:43
sdakeis our arbitrary pie in the sky target23:44
*** inc0 has quit IRC23:44
sdakethis leads to open discussion23:44
sdake#topic open discussion23:44
*** openstack changes topic to "open discussion (Meeting topic: kolla)"23:44
*** inc0 has joined #openstack-meeting-423:44
inc0sorry battery died23:44
vhosakotwe'll need continued help from manjeets and gmmaha to debug/test scale fixes...23:45
sdakeit takes me 6-12 hours to even dig into one ebug vhosakot23:45
sdakebecause i dont hve access to hte metal23:45
*** Jeffrey4l_ has joined #openstack-meeting-423:45
sdakemeanwhile i could be fixing 3-4 critical bugs23:46
vhosakotagreed, scale issues are different/tough23:46
gmmahavhosakot: we can definitely help as best as we can23:46
*** Jeffrey4l has quit IRC23:46
vhosakotthanks gmmaha23:46
inc0I hope to get us some serious hardware soon, for a time at least23:47
vhosakotI need two my reviews to be merged.. they are in queue long23:48
sdakeya folks23:49
sdakestay on top of the queue23:49
sdakei wnt eveyrone to have an opportunity to be first to review a patch23:49
sdakedont wait for someon else to review it first23:49
vhosakothttps://review.openstack.org/#/c/296012/    and    https://review.openstack.org/#/c/296649/23:49
sdakeanything else?23:50
*** annegentle has joined #openstack-meeting-423:51
vhosakotso, is inc0 going to send email about backport23:51
*** SumitNaiksatam has quit IRC23:51
inc0I thought sdake will do it?23:51
sdakehe said he would follow up on the thread23:51
vhosakotah ok ok23:51
inc0ah23:51
sdakeemail already sent23:51
inc0well23:51
vhosakotyes23:51
inc0ok, I'll follow up23:51
inc0tomorrow23:51
inc0I don't trust my skill of constructing correct sentecnes any more today23:52
vhosakothaha23:52
sdakeok well i'll gie folks back 7 minutes of their lives23:53
sdakeplease stay focused on milestone 3 and mitaak final23:53
sdake#endmeeting23:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:54
openstackMeeting ended Wed Mar 30 23:54:09 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-03-30-23.00.html23:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-03-30-23.00.txt23:54
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-03-30-23.00.log.html23:54
*** gmmaha has left #openstack-meeting-423:54
*** rhallisey has left #openstack-meeting-423:54
*** vhosakot has left #openstack-meeting-423:54
*** inc0 has quit IRC23:55
*** ajmiller has quit IRC23:56

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