Thursday, 2018-01-11

*** iyamahat_ has quit IRC00:01
*** iyamahat_ has joined #openstack-meeting-300:05
*** diablo_rojo has quit IRC00:05
*** diablo_rojo has joined #openstack-meeting-300:06
*** iyamahat_ has quit IRC00:06
*** yamamoto has quit IRC00:24
*** yamamoto has joined #openstack-meeting-300:27
*** yamamoto has quit IRC00:39
*** wanghao has quit IRC00:42
*** wanghao has joined #openstack-meeting-300:42
*** rmcall has quit IRC00:46
*** rmcall has joined #openstack-meeting-300:46
*** lyan has joined #openstack-meeting-300:58
*** slaweq_ has joined #openstack-meeting-301:21
*** slaweq_ has quit IRC01:25
*** sgrasley1 has joined #openstack-meeting-301:32
*** zhurong has joined #openstack-meeting-301:33
*** yamamoto has joined #openstack-meeting-301:39
*** shu-mutou-AWAY is now known as shu-mutou01:46
*** yamamoto has quit IRC01:47
*** VW has joined #openstack-meeting-301:47
*** markvoelker has joined #openstack-meeting-301:50
*** bobh has joined #openstack-meeting-301:53
*** lyan has quit IRC02:00
*** wanghao_ has joined #openstack-meeting-302:08
*** wanghao has quit IRC02:08
*** yamahata has joined #openstack-meeting-302:18
*** yamamoto has joined #openstack-meeting-302:19
*** rmcall has quit IRC02:20
*** markvoelker has quit IRC02:36
*** yamahata has quit IRC02:38
*** yamahata has joined #openstack-meeting-302:39
*** hongbin has joined #openstack-meeting-302:44
*** shuyingya has joined #openstack-meeting-302:52
*** wanghao has joined #openstack-meeting-302:54
*** yamahata has quit IRC02:54
*** wanghao_ has quit IRC02:54
*** wanghao_ has joined #openstack-meeting-302:59
*** wanghao has quit IRC03:00
*** rmcall has joined #openstack-meeting-303:10
*** yamamoto_ has joined #openstack-meeting-303:12
*** yamamoto has quit IRC03:16
*** wanghao has joined #openstack-meeting-303:19
*** wanghao has quit IRC03:20
*** wanghao has joined #openstack-meeting-303:20
*** wanghao_ has quit IRC03:21
*** harlowja_ has quit IRC03:21
*** slaweq_ has joined #openstack-meeting-303:21
*** slaweq_ has quit IRC03:26
*** VW has quit IRC03:32
*** VW has joined #openstack-meeting-303:32
*** VW has quit IRC03:37
*** absubram has quit IRC04:06
*** anilvenkata has joined #openstack-meeting-304:11
*** bobh has quit IRC04:11
*** zhurong has quit IRC04:12
*** spzala has joined #openstack-meeting-304:31
*** shu-mutou has quit IRC04:35
*** shu-mutou has joined #openstack-meeting-304:36
*** tuanla____ has joined #openstack-meeting-304:41
*** spzala has quit IRC04:42
*** absubram has joined #openstack-meeting-304:44
*** rmcall has quit IRC04:54
*** psachin has joined #openstack-meeting-305:21
*** psachin has quit IRC05:27
*** zhurong has joined #openstack-meeting-305:28
*** harlowja has joined #openstack-meeting-305:29
*** gcb has quit IRC05:30
*** gcb has joined #openstack-meeting-305:31
*** hongbin has quit IRC05:32
*** shu-mutou is now known as shu-mutou-AWAY05:32
*** psachin has joined #openstack-meeting-305:35
*** kaz has joined #openstack-meeting-305:43
*** markvoelker has joined #openstack-meeting-305:47
*** coolsvap has joined #openstack-meeting-305:47
*** slaweq has joined #openstack-meeting-306:09
*** marios has joined #openstack-meeting-306:13
*** slaweq has quit IRC06:13
*** markvoelker has quit IRC06:40
*** markvoelker has joined #openstack-meeting-306:42
*** yamamoto has joined #openstack-meeting-306:45
*** alexchadin has joined #openstack-meeting-306:46
*** harlowja has quit IRC06:47
*** yamamoto_ has quit IRC06:49
*** absubram has quit IRC07:12
*** pcaruana has joined #openstack-meeting-307:21
*** dims_ has quit IRC07:21
*** anilvenkata has quit IRC07:23
*** anilvenkata has joined #openstack-meeting-307:24
*** dims has joined #openstack-meeting-307:25
*** reedip has quit IRC07:34
*** reedip has joined #openstack-meeting-307:47
*** slaweq_ has joined #openstack-meeting-308:10
*** apetrich has quit IRC08:13
*** slaweq_ has quit IRC08:14
*** alexchadin has quit IRC08:28
*** kaz has quit IRC08:29
*** cshastri has joined #openstack-meeting-308:31
*** reedip has quit IRC08:34
*** alexchadin has joined #openstack-meeting-308:41
*** pcaruana has quit IRC08:44
*** reedip has joined #openstack-meeting-308:46
*** georgk has joined #openstack-meeting-308:47
*** julim has quit IRC08:48
*** julim has joined #openstack-meeting-308:48
*** wanghao has quit IRC08:58
*** wanghao has joined #openstack-meeting-308:58
*** wanghao has quit IRC08:59
*** wanghao has joined #openstack-meeting-308:59
*** wanghao has quit IRC09:00
*** wanghao has joined #openstack-meeting-309:00
*** wanghao has quit IRC09:00
*** wanghao has joined #openstack-meeting-309:01
*** wanghao has quit IRC09:03
*** wanghao has joined #openstack-meeting-309:04
*** wanghao has quit IRC09:04
*** wanghao has joined #openstack-meeting-309:04
*** wanghao has quit IRC09:05
*** wanghao has joined #openstack-meeting-309:05
*** wanghao has quit IRC09:06
*** wanghao has joined #openstack-meeting-309:06
*** wanghao has quit IRC09:07
*** wanghao has joined #openstack-meeting-309:07
*** wanghao has quit IRC09:07
*** wanghao has joined #openstack-meeting-309:08
*** wanghao has quit IRC09:08
*** wanghao has joined #openstack-meeting-309:08
*** wanghao has quit IRC09:09
*** wanghao has joined #openstack-meeting-309:09
*** wanghao has quit IRC09:10
*** wanghao has joined #openstack-meeting-309:10
*** wanghao has quit IRC09:10
*** jgu has quit IRC09:16
*** jgu has joined #openstack-meeting-309:16
*** e0ne has joined #openstack-meeting-309:21
*** apetrich has joined #openstack-meeting-309:53
*** pcaruana has joined #openstack-meeting-310:04
*** slaweq_ has joined #openstack-meeting-310:11
*** markvoelker has quit IRC10:13
*** sambetts|afk is now known as sambetts10:14
*** slaweq_ has quit IRC10:15
*** pbourke has joined #openstack-meeting-310:16
*** alexchadin has quit IRC10:34
*** ywat has quit IRC10:34
*** cshastri has quit IRC10:35
*** zhurong has quit IRC10:35
*** e0ne has quit IRC10:38
*** e0ne has joined #openstack-meeting-310:39
*** cshastri has joined #openstack-meeting-310:48
*** numans has quit IRC10:54
*** numans has joined #openstack-meeting-310:55
*** shuyingy_ has joined #openstack-meeting-310:59
*** shuyingya has quit IRC11:03
*** anilvenkata has quit IRC11:05
*** tuanla____ has quit IRC11:21
*** apetrich has quit IRC11:38
*** sdague has joined #openstack-meeting-311:39
*** e0ne has quit IRC11:58
*** davidlenwell has quit IRC12:01
*** yamamoto has quit IRC12:01
*** davidlenwell has joined #openstack-meeting-312:01
*** yamamoto has joined #openstack-meeting-312:01
*** pcaruana has quit IRC12:02
*** pcaruana|afk| has joined #openstack-meeting-312:02
*** slaweq has joined #openstack-meeting-312:11
*** markvoelker has joined #openstack-meeting-312:14
*** slaweq has quit IRC12:16
*** raildo has joined #openstack-meeting-312:19
*** jgu_ has joined #openstack-meeting-312:22
*** mrmartin has quit IRC12:24
*** jgu has quit IRC12:26
*** e0ne has joined #openstack-meeting-312:30
*** e0ne has quit IRC12:33
*** mrmartin has joined #openstack-meeting-312:39
*** e0ne has joined #openstack-meeting-312:42
*** shuyingy_ has quit IRC12:42
*** bobh has joined #openstack-meeting-312:42
*** markvoelker has quit IRC12:48
*** haint has joined #openstack-meeting-312:48
*** absubram has joined #openstack-meeting-312:48
*** pgadiya has joined #openstack-meeting-312:49
*** pcaruana|afk| has quit IRC12:49
*** krtaylor_ has quit IRC12:50
*** e0ne has quit IRC12:52
*** absubram_ has joined #openstack-meeting-312:52
*** absubram has quit IRC12:53
*** absubram_ is now known as absubram12:53
*** e0ne has joined #openstack-meeting-312:53
*** pcaruana|afk| has joined #openstack-meeting-313:02
*** tosky has joined #openstack-meeting-313:06
*** e0ne has quit IRC13:20
*** shuyingy_ has joined #openstack-meeting-313:21
*** e0ne has joined #openstack-meeting-313:24
*** absubram has quit IRC13:25
*** bobh has quit IRC13:25
*** georgk has quit IRC13:26
*** e0ne has quit IRC13:30
*** e0ne has joined #openstack-meeting-313:33
*** apetrich has joined #openstack-meeting-313:33
*** e0ne has quit IRC13:34
*** lhx_ has joined #openstack-meeting-313:37
*** markvoelker has joined #openstack-meeting-313:44
*** tosky has quit IRC13:50
*** tosky has joined #openstack-meeting-313:54
*** lyan_ has joined #openstack-meeting-313:54
*** pgadiya has quit IRC13:56
*** jeremyfreudberg has joined #openstack-meeting-313:57
*** e0ne has joined #openstack-meeting-313:58
*** alexchadin has joined #openstack-meeting-313:59
tellesnobrega#startmeeting sahara14:00
openstackMeeting started Thu Jan 11 14:00:15 2018 UTC and is due to finish in 60 minutes.  The chair is tellesnobrega. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
tellesnobregawe all are here14:01
shuyingy_Hi guys14:01
tellesnobregathat is new :)14:02
tellesnobregahey all14:02
tellesnobregalets get started14:02
tellesnobrega#topic News/Updates14:02
*** openstack changes topic to "News/Updates (Meeting topic: sahara)"14:02
tellesnobregaI'm doing small fixes on the images, not much left to do there. Now I'm focusing on fixing some of the bugs we talked about in Denver (file transfer is the first). Also I want to start testing S3 integration as well as APIv214:03
toskystill checking the images produced by sahara-image-pack; finally fixed the CLI tests (the patch for tempest just landed); starting to tackle sahara-extra and upload of oozie tarballs14:04
shuyingy_Business travel takes me half of the week. Get back yesterday and start working on solve problem in vanilla upgrade14:04
tosky(and nagging and complaining for mass-doc changes, but that touched sahara only partially)14:04
jeremyfreudbergi haven't had much time to focus on upstream.... but i have (finally) fixing s3_hadoop on my mind. and also apiv2 in client14:04
jeremyfreudbergre apiv2 in client, i think i will post a patch doing version discovery the wrong way, then have monty fix it (The patch isn't just that, it also will have all the other v1->v2 changes reflected)14:05
tellesnobregajeremyfreudberg, we need to start testing APIv2 asap, when are you sending the patch?14:06
tellesnobregaa rough estimation is ok14:06
jeremyfreudberglate tonight14:07
toskywrong patch forcing monty to fix it, I like the strategy :)14:07
jeremyfreudbergyes, my version of cunningham's law14:08
tellesnobregawhat could go wrong using that?14:08
*** julim has quit IRC14:08
tellesnobregamore updates?14:09
jeremyfreudbergwell, about force deletre14:10
jeremyfreudbergi have a patch that you guys can review BUT actually i am thinking about it some more and i think stack abandon might be not the best choice14:10
tellesnobregawhat is the choice you are thinking of?14:11
jeremyfreudbergjust do a stack delete, but don't wait for deletion. then, unhide the stack14:11
toskylet's discuss the details now or let's switch topic?14:12
jeremyfreudbergtosky, yes, probably switch topic if no more updates14:12
jeremyfreudbergjumped the gun a bit14:12
tellesnobregalet me switch topic so we can discuss it14:12
tellesnobrega#topic Force Delete details14:12
*** openstack changes topic to "Force Delete details (Meeting topic: sahara)"14:12
*** slaweq has joined #openstack-meeting-314:12
tellesnobregayou have the floor jeremyfreudberg14:12
jeremyfreudbergcurrent version of the patch does force delete like this: 1) put stack in deleting state 2) immediately abandon it 3) drop from db and other cleanup14:13
jeremyfreudbergdrop cluster, i mean14:13
jeremyfreudbergmy new idea is: 1) put stack in deleting state, don't wait for deletion to complete 2) unhide stack 3) drop cluster from db14:14
jeremyfreudbergthe problem with abandon was that the user has no idea what was orphaned14:14
tellesnobregathe step that I don't understand, probably due to lack of knowledge on heat, but what does unhide stack means14:15
shuyingy_could you explain about the step 214:15
jeremyfreudbergyes, unhide stack is actually a very funny thing14:15
jeremyfreudbergi will explain14:15
jeremyfreudbergsahara actually has a special arrangement with heat, that all stacks with a tag data-processing-cluster are "hidden"14:16
jeremyfreudbergso you need to specifically query for hidden stacks to see them in api/cli14:16
shuyingy_yes, heat stack-list -a14:17
jeremyfreudbergbut if i remove the tag from the stack, suddenly the user can see the stack and will know to clean stuff up14:17
*** slaweq has quit IRC14:17
tellesnobregaby user you mean cloud operator?14:17
jeremyfreudbergby user i mean the real user14:18
*** markvoelker has quit IRC14:18
tellesnobregathat makes sense to me14:18
tellesnobregashuyingy_, tosky ?14:18
shuyingy_I don't understand what can we benefit if we see the stack14:19
toskyand the "drop cluster from db" solves the issue when heat stack is clean, but the cluster is stuck in deletion state from the sahara point of view?14:19
jeremyfreudbergtosky, my force delete solution fixes (by my estimate) 90%+ of cases where cluster is stuck deleting because heat stack won't finish deleting14:21
jeremyfreudbergby providing alternate way of getting to the final "drop from db" step that doesn't wait for heat stack delete to finish14:21
jeremyfreudbergyour case where sahara is still in deleting but stack is already gone is not fixed by my patch, but if the stack is already gone and you issue the delete call again the delete should finish fine14:22
shuyingy_jeremyfreudberg, I have tried to delete the stack in "heat stack-list -a", but most of time sahara can't delete because stack status is failed14:22
shuyingy_I see14:23
*** shuyingy_ is now known as shuyingya14:23
tellesnobregaafter the stack is completely gone that should be ok shuyingya14:23
jeremyfreudbergbasically here's my point:14:23
shuyingyaI got it.14:23
* jeremyfreudberg will summarize anyway14:24
*** psachin has quit IRC14:24
tellesnobregaplease do jeremyfreudberg14:24
*** julim has joined #openstack-meeting-314:24
jeremyfreudbergthe only way we can have a meaningful force delete option here is if we don't await stack deletion and proceed on to drop cluster from db regardless of stack status14:25
jeremyfreudbergthe implications of that:14:25
jeremyfreudberg- user might still want to know what resources didn't end up deleted14:25
jeremyfreudberg- but, if the stack really was undeleteable (DELETE_FAILED) then that still doesn't mean that the user will have any easier of a time14:26
jeremyfreudbergi mean the user's manual cleanup still won't be easy14:26
jeremyfreudbergi think we all get the idea, i don't want to waste half the meeting on it14:27
jeremyfreudbergplease follow up on the patch itself if you have concerns14:28
shuyingyajeremyfreudberg, If I remember correctly, heat has an option to configure what kind of stack should be hidden. how can you unhiden it?14:28
jeremyfreudbergyou can do a PATCH on stack to update tags list14:28
jeremyfreudbergi was planning just to remove the tag14:28
jeremyfreudbergthe conf option stays the same14:28
shuyingyatotally understand it14:29
tellesnobregaare we all settled on this topic?14:30
jeremyfreudbergshuyingya, continue14:30
shuyingyajeremyfreudberg, why stack-abandon is not a proper way?14:31
*** VW has joined #openstack-meeting-314:32
*** shuyingy_ has joined #openstack-meeting-314:33
*** shuyingy_ is now known as shuyingya_14:33
jeremyfreudbergit would work okay, but it's unnecessary. it basically means "drop stack from heat db" but why should we be hiding stuff from user, i guess is my point14:33
shuyingya_sorry, network broken14:33
tellesnobregaI guess the point boils down to, does the end user need to know about heat stack status when using sahara?14:34
jeremyfreudbergtellesnobrega, basically yes14:35
*** shuyingya has quit IRC14:36
jeremyfreudbergi will continue to think about it, but i really think we should move on so we can use meeting time more efficiently14:37
shuyingya_I need take some time to think about it14:37
shuyingya_let's move on14:37
tellesnobregawe can continue on the patch14:37
tellesnobrega#topic Dublin PTG14:37
*** openstack changes topic to "Dublin PTG (Meeting topic: sahara)"14:38
shuyingya_did you receive the email form me?14:38
tellesnobregaI started an etherpad so we can start putting stuff together for the PTG14:38
jeremyfreudbergshuyingya_, yes, saw email14:38
shuyingya_let's continue tellesnobrega's topic14:38
toskyyep, we can talk about oozie afterwards, I have few questions too14:39
tellesnobregaplease take some time to write down topic ideas, so we can start getting ready for the PTG14:39
shuyingya_will do14:39
tellesnobregaalso, I know tosky and I will be there, jeremyfreudberg almost sure, how about you shuyingya_ ?14:39
toskysure (I was thinking about copy-pasting the final TODO list from Queens PTG for easier comparison)14:39
tellesnobregatosky, we can certainly do that14:40
shuyingya_I am not sure right now. maybe not14:40
tellesnobregaif you can apply to TSP please do14:40
tellesnobregayou are a core reviewer, they will probably see you as high priority14:41
tellesnobregaI was also thinking, what do you guys think of creating a trello board so we can have a better tracking system of sahara todos, feature status and so on14:41
tellesnobregawait, before you answer that question14:41
tellesnobregaI will close this topic and change to Open Discussion14:42
tellesnobregaand after this we can jump into oozie and openstack-hadoop stuff14:42
tellesnobrega#topic Open Discussion14:42
*** openstack changes topic to "Open Discussion (Meeting topic: sahara)"14:42
tellesnobregawhat do you guys think of creating a trello board so we can have a better tracking system of sahara todos, feature status and so on?14:42
jeremyfreudbergtrello is a decent idea (and actually i am already doing that)14:43
shuyingya_this tool looks like cool14:44
tellesnobregatosky, shuyingya_, any objections? I know some people hate it14:44
shuyingya_I am OK with it.14:44
toskywhy not trying storyboard then?14:45
jeremyfreudbergthe one objection that someone could have is why not storyboard maybe14:45
* tosky <- someone14:45
jeremyfreudbergyes, beat tosky by one second14:45
tellesnobregacould be, I never used storyboard14:45
tellesnobregaby trello I meant some place we can have a better tracking system than keep going back to an 3-6 months old etherpad14:46
shuyingya_I never used storyboard and trello :(14:46
toskyin fact "migrate to storyboard" is something I'd like to propose for Rocky - it's not going to be a community goal, but still we will use it at some point14:46
jeremyfreudbergtosky, is it possible to do a "soft" transition, meaning keep bugs on LP for now and just to do Task tracking on Storyboard?14:47
toskyjeremyfreudberg: I don't know, it's something to ask to... uhm... I don't know :)14:47
tellesnobregaTC maybe?14:47
toskyprobably (or they can redirect)14:47
tellesnobregatosky, do you have a link to storyboard?14:48
*** hongbin has joined #openstack-meeting-314:48
tellesnobregaand I will follow up with that14:48
tellesnobregasince we mainly agree that we need something better than what we have today14:48
jeremyfreudbergyes, as long as we have some tracking tool then i will be happy14:49
jeremyfreudberglet's use the last ten minutes for shuyingya_ oozie stuff14:49
shuyingya_do you have any questions about the description in the email?14:50
toskytellesnobrega: topic!14:51
toskyoh, open discussion already, sorry14:51
jeremyfreudbergshuyingya_, basically you are saying that running the job normally against swift is working, but when you use oozie to launch job, something is missing14:51
shuyingya_good news is that all testcases has passed.14:51
shuyingya_jeremyfreudberg, do you mean you want know how to start the job?14:52
*** Swami has joined #openstack-meeting-314:52
shuyingya_the command is :openstack dataprocessing job execute --cluster gogo --job-template vanilla-job-template --configs mapred.reduce.class:org.apache.oozie.example.SampleReducer fs.swift.service.sahara.username:admin fs.swift.service.sahara.password:admin --input 92e6b254-66a0-4b05-a989-40993bb5d9b7 --output 0cced149-5400-4afa-9d49-32295d74065d14:53
toskyone thing that I noticed and I don't understand is: why the generated jar is always hadoop-openstack-3.0.0-SNAPSHOT.jar , even if we specify different values of hadoop.version?14:53
jeremyfreudbergtosky, i think that naming is given by something in pom, but it doesn't mean anything14:53
jeremyfreudberghardcoded somewhere14:53
toskywhat is the difference then?14:53
jeremyfreudbergshuyingya_, what i meant was just to clarify the meaning of the email. there is the oozie way (sahara edp) and the normal way (hadoop command?)14:54
*** zhipeng has joined #openstack-meeting-314:54
shuyingya_I run it with sahara comand14:54
tellesnobregajeremyfreudberg, for us, the normal way  is using oozie (sahara way)14:55
jeremyfreudbergshuyingya_, i see. my mistake. i was imagining things14:55
shuyingya_yes, hadoop-openstack-3.0.0-SNAPSHOT.jar doesn't mean anything14:55
jeremyfreudbergshuyingya_, i'm wondering if you can try the job with `hadoop jar ...` maybe the oozie classpath is different than normal hadoop classpath14:56
tellesnobregawhat changed so httpclient is not present anymore? and what is the best way to put it back on?14:57
jeremyfreudbergshuyingya_, we can also try to get this change in:
jeremyfreudbergapache people just stopped importing httpclient completely14:58
jeremyfreudbergand rewrote to use a different library14:58
*** mlavalle has joined #openstack-meeting-314:59
tellesnobregafrom our side? what need httpclient? can we change it to use httpresponse?14:59
shuyingya_jeremyfreudberg, I know what you mean and I also thought about to apply the change in 3.0.0. have no time to test14:59
shuyingya_:) I will try it out tomorrow14:59
jeremyfreudbergif you say uploading the jar fixes it, we can just do that too15:00
tellesnobregaquick first fix until we come up with something better15:00
tellesnobregawe are at the top of the hour15:00
tellesnobregawe have to close it now15:00
tellesnobregathanks guys, shuyingya_ update us on progress on this and what do you think will be the best approach for now15:00
tellesnobregajeremyfreudberg, if you need help with APIv2 let me know15:01
shuyingya_If you guys OK, I will post the patch with work around method tomorrow15:01
tellesnobregatosky, do your thing :)15:01
tellesnobregasounds good shuyingya_15:01
tellesnobregathanks all15:01
*** openstack changes topic to "OpenStack Meetings ||"15:01
openstackMeeting ended Thu Jan 11 15:01:40 2018 UTC.  Information about MeetBot at . (v 0.1.4)15:01
openstackMinutes (text):
mlavalle#startmeeting neutron_l315:01
openstackMeeting started Thu Jan 11 15:01:46 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
*** markvoelker has joined #openstack-meeting-315:02
*** jeremyfreudberg has quit IRC15:02
mlavalleHi there!15:02
*** markvoelker has quit IRC15:02
mlavalleThat was a long farewell by the Sahara guys15:03
mlavalle#topic Announcements15:03
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:03
mlavallehaleyb: must be digging himself out from the snow15:04
*** janzian has joined #openstack-meeting-315:05
mlavalleWe are a little more that a week from the Q-3 milestone15:05
mlavalleand we are a month and a half away from the Dublin PTG15:05
* mlavalle booked his flight yesterday15:05
haleybmlavalle: sorry, was doing a report for a meeting in progress15:06
SwamiI need to drop of early today. I have to drop kids at school.15:06
mlavalleok, let's move on15:06
mlavalle#topic Bugs15:06
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:06
mlavallego ahead Swami15:06
*** tosky has left #openstack-meeting-315:06
Swamithanks mlavalle15:07
openstackLaunchpad bug 1735866 in neutron "Snat namespace misses iptables rules for floating ip." [Undecided,In progress] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)15:07
SwamiThis is a new bug that was filed. I triaged it and pushed in a patch.15:08
SwamiPatch is up for review.15:08
SwamiI did see a zuul failure, but not related to the patch. Did a recheck on it.15:08
haleybSwami: that bug shows a different patch15:09
Swamihaleyb: Yes sorry wrong post15:09
haleyb - which is in the gate15:09
openstackLaunchpad bug 1735866 in neutron "Snat namespace misses iptables rules for floating ip." [Undecided,In progress] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)15:09
SwamiThat bug patch already is in the merge queue.15:09
openstackLaunchpad bug 1741411 in neutron "Centralized floating ip Error status" [Medium,In progress] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)15:09
SwamiYes that is the bug.15:10
SwamiThis is the patch up for review.15:10
mlavalleI was going to ask about that one15:10
mlavalleThanks for picking it up15:11
SwamiThere was an issue with the restart of the dvr_no_external agent. That case was not handled.15:11
openstackLaunchpad bug 1736068 in neutron "DVR lost centralized floating ip when the ha state switched." [High,In progress] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)15:12
Swamithere is a patch up for review.15:12
SwamiThis patch was failing zuul and I rebased.15:13
SwamiBut I do see that was some unnecessary change in this patch that was coupled with the bug. I have given a comment. If it is not addressed I will fix it.15:13
openstackLaunchpad bug 1740450 in neutron "Restarting l3 agent results in lost of centralized fip in snat ns" [Undecided,New]15:14
SwamiThis is similar to bug 174141115:14
openstackbug 1741411 in neutron "Centralized floating ip Error status" [Medium,In progress] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)15:14
SwamiBut not sure if they are the same. I have posted some comments in there, on the agent that is getting restarted with HA.15:14
SwamiIf time permits I will triage it again and see what is wrong there.15:15
openstackLaunchpad bug 1717302 in neutron "Tempest floatingip scenario tests failing on DVR Multinode setup with HA" [High,Confirmed] - Assigned to Brian Haley (brian-haley)15:15
SwamiThis is a long standing bug and I did not spend any time on this during this week.15:16
SwamiI will spend some time again this week to see if I can nail down.15:16
haleybi did not either, but might have time tomorrow15:16
mlavallehaleyb: but we did something in the CI meeting about it, right?15:16
haleybmlavalle: we have marked the test as unstable i believe15:17
mlavalleyeah, that's it15:17
mlavallebut not really fixed it15:17
Swamimlavalle: but still we need to find out the issue.15:17
Swamimlavalle: I was almost close when stopped working on it.15:17
Swamihaleyb: let me know your initial findings and will take it from there. I wanted another pair of eyes to look at it.15:18
haleybSwami: ok15:18
SwamiThat's all I have for today.15:18
mlavalleI have a question for haleyb and Swami15:19
mlavalleit is about
openstackLaunchpad bug 1741407 in neutron "L3 HA: 2 masters after restart of l3 agent" [Undecided,New]15:19
mlavallehaleyb already told me he doesn't have the environment to confirm this bug15:19
*** cleong has joined #openstack-meeting-315:20
mlavallehow about you Swami?15:20
mlavalleI am really trying to understand if among the 3 of us we have a gap with HA15:20
haleybmlavalle: i know we had another recent l3-ha dual-master bug which should have been fixed15:20
Swamimlavalle: I don't have the environment as well. But there is a bug above that requires HA, when I have the environment I can check it out.15:21
openstackLaunchpad bug 1731595 in neutron (Ubuntu Zesty) "L3 HA: multiple agents are active at the same time" [High,Fix committed] - Assigned to Corey Bryant (corey.bryant)15:21
SwamiI don't have the environment handy.15:21
mlavalleSwami: ah ok, so a HA environment is something you can deploy easily15:21
Swamimlavalle: Yes I can. But I have not tried earlier dual-master. Master-slave is what I have tried before.15:22
mlavalleI was really trying to decide if I should specialize on that and have something readily available when HA bugs show up15:22
mlavalleSwami: great. In that case carry on15:22
mlavalleI was worried about a possible gap15:23
haleybmlavalle: i really should have one always available as a lot of customers run it, there's just a lot of overhead15:23
mlavalleok, understood15:23
*** markvoelker has joined #openstack-meeting-315:24
Swamimlavalle: back to you.15:24
*** bobh has joined #openstack-meeting-315:24
mlavalleThe only thing that I want to mention on my side is that merged about 2 hours ago15:24
mlavalleso we shouldn't be running double check / gate jobs anymore today15:25
haleybor triple? :-p15:26
mlavallethat's right15:26
*** rmcall has joined #openstack-meeting-315:26
mlavalleas haleyb pointed out yesterday15:26
haleybihar found that other job, funny how we only found it when updating grafana since there were a lot of stats15:27
mlavallethe problem was that tempest-full was in the Tempest repo. So the duplication wasn't apparent with the files I was migrating15:28
haleyband merged, i never got back after the update15:28
*** alexchad_ has joined #openstack-meeting-315:28
haleyb^^ the grafana change15:28
mlavalle#topic dvr_openflow15:29
*** openstack changes topic to "dvr_openflow (Meeting topic: neutron_l3)"15:29
mlavalledavid_chou: over to you15:30
david_chouI still work on the base ovs-dpdk test case, not much progress. But I got a VM enviroment in one of Intel internal cloud which is similar the environment David Shaughnessy's group use, hope eaiser to get their help.15:30
david_chouhat's all I have today.15:30
david_chouThat's ^^^15:31
*** alexchadin has quit IRC15:31
mlavalledavid_chou: Thanks for the update15:31
mlavalle#Open Agenda15:32
mlavalle#topic Open Agenda15:32
*** openstack changes topic to "Open Agenda (Meeting topic: neutron_l3)"15:32
mlavalleany toher topics we should discuss today?15:32
mlavalleok Team15:33
mlavallesee you next week15:33
*** openstack changes topic to "OpenStack Meetings ||"15:33
openstackMeeting ended Thu Jan 11 15:33:46 2018 UTC.  Information about MeetBot at . (v 0.1.4)15:33
openstackMinutes (text):
*** Swami has quit IRC15:33
*** yamamoto has quit IRC15:37
*** alexchad_ has quit IRC15:37
*** yamamoto has joined #openstack-meeting-315:38
*** zhipeng has quit IRC15:38
*** yamamoto has quit IRC15:43
*** elmiko has joined #openstack-meeting-315:52
*** alexchadin has joined #openstack-meeting-315:53
*** cdent has joined #openstack-meeting-315:56
*** janzian has left #openstack-meeting-315:57
*** dtantsur has joined #openstack-meeting-315:58
cdentwho wants to hold the baton today?15:58
cdentedleafe, dtantsur, elmiko15:59
* edleafe hides15:59
elmikoi can do it15:59
cdentgo fer it15:59
elmiko#startmeeting api sig15:59
openstackMeeting started Thu Jan 11 15:59:44 2018 UTC and is due to finish in 60 minutes.  The chair is elmiko. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
*** openstack changes topic to " (Meeting topic: api sig)"15:59
openstackThe meeting name has been set to 'api_sig'15:59
elmikooooh 16 seconds early15:59
elmiko#chair cdent elmiko edleafe dtantsur16:00
openstackCurrent chairs: cdent dtantsur edleafe elmiko16:00
elmiko#topic previous meeting action items16:00
*** openstack changes topic to "previous meeting action items (Meeting topic: api sig)"16:00
* edleafe comes out of hiding16:00
*** mjturek has joined #openstack-meeting-316:01
cdentI did the writing for the annual report and was told "it's pefect!"16:01
cdentso I guess that went well16:01
elmiko#topic open mic and ongoing or new biz16:02
*** openstack changes topic to "open mic and ongoing or new biz (Meeting topic: api sig)"16:02
cdentexcept that the quoted person spelt perfect perfectly16:02
elmikook, so i see a topic of how do we encourage change without becoming the api police16:03
elmikoany thoughts?16:03
cdentrelated to that, monty has proposed a couple of openstack-wide goals related to api stuff, including the recent pagination stuff16:03
openstackRemoving item from minutes: #link
* cdent is standing16:04
dtantsura starting guide and a template for new projects?16:04
dtantsurand openstack-wide goals indeed16:04
* edleafe thinks cdent is wobbling16:04
cdentdtantsur: by template do you mean stub code or something less specific?16:05
dtantsurcdent: similar to cookiecutter16:05
elmikodtantsur: well, some of this was in relation to how we encourage projects to use the pagination rfc stuff, like should we open bugs or ?16:05
dtantsursomething, preparing the python code and one CRUD resource with eerything set up16:05
dtantsurmajor versions, microversions, discovery...16:05
cdentdtantsur: I'd be pretty leary of code, but a cookbook on what the code can do would be useful16:06
elmikoooh, are you talking about a project template?16:06
* dtantsur opens google translate16:06
elmikocookbook ++, we went around the code template idea once before and it wasn't generally deemed worth it16:06
elmikotoo many options, too many variables16:06
cdentand too many opinions16:07
dtantsuractually, we may want to get into the business of chosing the recommended framework for new projects16:07
dtantsurand making sure it has enough libs for common stuff16:07
edleafeonly cdent's opinion counts, thoguh16:07
edleafedtantsur: how do you mean?16:08
edleafedtantsur: what would be an example?16:08
dtantsuredleafe: e.g. "use Flask; use <this library> for Restful API, <this middleware> for microversions, plug keystonemiddleware this way"16:08
edleafedtantsur: that sounds more like the stuff that the (now defunct) Architecture WG was focusing on16:09
dtantsurto me it sounds like something we could help with, even though it does grow our missing a tiny bit16:10
cdentedleafe: perhaps api-wg would not address such things, but the api-sig might16:10
dtantsurotherwise we have a lof of recommendations, but no practical help in implementing them..16:10
dtantsurit can mean some understandable resistance16:10
dtantsurs/mean/meet/ WUT?16:10
cdentsuch advice would be something other than "guidance"16:11
cdentthere's nothing new on api-schema is there?16:13
elmikoi had always thought that adding some code projects would help drive some traffic to the sig(ex. wg), but it never seemed to gain much traction16:13
*** slaweq_ has joined #openstack-meeting-316:13
elmikocdent: i don't think so, but i also don't know for sure16:14
cdentI think I just left it on the agenda as a reminder16:14
*** mlavalle has quit IRC16:14
elmikoso, do we have anything to record about encouragin projects to adopt the guidelines for things like pagination?16:14
elmikolast time we talked about opening bugs on projects that might need it, is this something we would pursue?16:15
cdentdo you all agree that it is okay for them to sometimes be an openstack-wide goal?16:15
cdentor is that too stick-ish?16:15
dtantsursometimes - yes16:15
edleafeelmiko: there's always this:
elmikoman, that seems so heacy16:15
elmikoedleafe: LOL, not quite my style but yeah16:16
edleafecdent: aren't goals supposed to be complete-able in one cycle?16:16
elmikocdent: my question to that would be, if we say something is an openstack-wide goal (eg pagination either in headers or body), then how do we get buy-in from the community for our pronouncements?16:17
*** mjturek has quit IRC16:17
cdentedleafe: yeah, thus why the pagination thing is just one thing16:17
cdentelmiko: the goal has to be approved by the tc and the tc won't approve it if there isn't perceived buy in16:17
cdentand if there isn't a champion to drive it16:17
*** slaweq_ has quit IRC16:17
elmikoand would we need a separate process for declaring something a goal like that?16:18
edleafecdent: yeah, that's what I thought16:18
cdentelmiko: we don't really do the declaring (unless we feel like it) see16:18
elmikoso, i'm ok with the openstack-wide goal if we have a higher body to help us (ie the tc)16:18
*** mjturek has joined #openstack-meeting-316:18
edleafeSo saying "adding/correcting pagination links" is doable, but "conforming to the API guidelines" would not be16:18
elmikoi had not seen that page, given that i am ok with going forward on the goals16:19
cdentwe miss you in openstack elmiko16:19
elmiko<3 i miss y'all too =)16:20
elmikook, so for this week is it fair to say that we agree the sig will works towards identifying pieces of the guidelines with high impact that should be promoted to openstack-wide goals?16:21
cdentthere's only two goal (usually) per cycle, so this is not a solution, simply a tool16:21
elmikoah, gotcha16:22
cdentbut it would be safe to say that we seem okay to use the tool16:22
elmikostill though, getting pagination fixed across the ecosystem in a single cycle would be a big accomplishment16:22
elmikook then, moving along16:22
elmikoanyone wanna talk about health check apis?16:22
elmiko(i'm not sure who added this)16:23
dtantsurI'm not sure from these links what we should talk about right now16:23
cdentsorry, that was me.16:24
elmikoi wasn't sure if we had an advocate in attendence16:24
*** e0ne has quit IRC16:24
cdentthere's work in progress to establish health check tools (things that make it easy to kill contiainers when not healthy)16:24
*** alexchadin has quit IRC16:24
cdentthe api-sig has been invited to help define the api for the for that, so that the implementation is consistent across services16:25
cdentthings like the same well known url16:25
*** alexchadin has joined #openstack-meeting-316:25
cdentthere's an oslo-spec in progress16:25
cdenti think it is suffering from internet over-engineering task force16:26
cdentbut lays out some of the goals16:26
* elmiko chuckles16:27
elmikoi had not heard ioetf XD16:27
*** shuyingya_ has quit IRC16:27
dtantsurI'd say this document should first appear in api-sig indeed16:27
*** shuyingya has joined #openstack-meeting-316:27
cdentthe oslo-spec is mostly about the backend16:27
cdentbut as the api-sig, we're under no obligation to only attend to documents in our domain, being active on that spec is desired and invited16:28
edleafeseems like there could be two parallel efforts: the oslo one to implement, and the api-sig to review and create the guidelines as needed16:29
*** alexchadin has quit IRC16:29
* cdent nods16:30
dtantsuryeah.. thought I'd still prefer the api-sig one to show up first16:30
cdenttoo late? :)16:31
dtantsurthere are interesting things from our perspective that seem missing: like how to manage microversions?16:31
dtantsuris it going to have separate microversions? the same as project? none?16:31
*** absubram has joined #openstack-meeting-316:31
*** shuyingya has quit IRC16:32
cdentthat, too, sounds like ioetf16:32
cdentthis thing should answer yes, no, and maybe maybe16:32
edleafeI guess I would have to know more of the health check mechanisms to consider the need for versioning16:32
cdentreading the specs and the etherpads will help to illuminate some of the thinking, especially the comments on the spec will identify some of the different ideas16:33
* dtantsur puts on his review list16:33
cdentthere are some preconceptions which could probably be adjusted usefully16:33
elmikoaside from the guidance about which libs to use and code stuff, i think this would really be nice to land as a guideline16:34
elmiko*assuming* that a concensus can be achieved16:34
* elmiko is skimming over the review16:35
* cdent nods16:35
*** absubram has quit IRC16:36
elmikoi realize we might not be as quick to react as the folks driving that review though, so i'm curious if there is a way for us to signal this intention to those folks and get their advice16:37
edleafecomment on the review?16:37
cdentjust say so on the review16:37
elmikothat sounds way too reasonable16:38
elmiko#action elmiko add thoughts to health check review about becoming an api-sig guideline16:38
edleafeok, then show up at their homes and bang on their doors16:38
elmikosound good?16:38
* edleafe likes being unreasonable16:38
cdenttake that gun from earlier16:39
elmikocdent: fair enough lol16:39
elmikomoving on...16:40
elmiko#topic guidelines16:40
*** openstack changes topic to "guidelines (Meeting topic: api sig)"16:40
elmikothere was that addition from mordred, anything else?16:40
dtantsur#link :)16:40
cdentdtantsur's new thing is vera nice16:41
*** absubram has joined #openstack-meeting-316:41
cdentIf dtantsur likes we should probably freeze it?16:41
dtantsurcdent: I haven't checked it yet, but you can freeze it. I will let you know if I really object :)16:41
edleafefreeze it, baby!16:42
elmikook, and we need to do some reviews on dtantsur's16:43
elmikowell, i do at least16:43
edleafeyeah, I need to review, too16:43
dtantsurMOAR REVIEWS \o/16:43
elmiko#topic bug review16:44
*** openstack changes topic to "bug review (Meeting topic: api sig)"16:44
elmikoanything new here?16:44
cdentno sir16:44
elmiko#topic weekly newsletter16:45
*** openstack changes topic to "weekly newsletter (Meeting topic: api sig)"16:45
cdentit's been a while since I have, so... me?16:45
elmikoi'm cool with that, i have a preso after this meeting anyways16:45
cdentI'll go sit somewhere, so I can actually type16:45
* edleafe pats cdent on the back16:46
elmikofor completeness16:46
cdentI know, right?16:46
elmiko     #link
*** marios has quit IRC16:46
elmikoalrighty then, any last comments?16:46
cdentI'll ping when I have something to review16:46
elmikook, we get back 14 minutes. thanks all! =)16:46
*** openstack changes topic to "OpenStack Meetings ||"16:47
openstackMeeting ended Thu Jan 11 16:47:03 2018 UTC.  Information about MeetBot at . (v 0.1.4)16:47
openstackMinutes (text):
*** cdent has quit IRC16:47
*** elmiko has left #openstack-meeting-316:47
*** dtantsur has left #openstack-meeting-316:47
*** chyka has joined #openstack-meeting-316:55
*** pcaruana|afk| has quit IRC16:57
*** iyamahat has joined #openstack-meeting-317:03
*** iyamahat has quit IRC17:11
*** lhx_ has quit IRC17:11
*** mjturek has quit IRC17:13
*** mjturek has joined #openstack-meeting-317:14
*** VW has quit IRC17:20
*** VW has joined #openstack-meeting-317:21
*** amotoki has quit IRC17:24
*** slaweq has joined #openstack-meeting-317:33
*** coolsvap has quit IRC17:36
*** slaweq has quit IRC17:37
*** VW has quit IRC17:39
*** VW has joined #openstack-meeting-317:40
*** cshastri has quit IRC17:41
*** caboucha has joined #openstack-meeting-317:45
*** absubram has quit IRC17:46
*** sambetts is now known as sambetts|afk17:54
*** yamamoto has joined #openstack-meeting-318:00
*** yamamoto has quit IRC18:04
*** SumitNaiksatam has joined #openstack-meeting-318:19
*** rmcall has quit IRC18:21
*** iyamahat has joined #openstack-meeting-318:43
*** yamahata has joined #openstack-meeting-318:53
*** slaweq has joined #openstack-meeting-319:20
*** alexchadin has joined #openstack-meeting-319:29
*** harlowja has joined #openstack-meeting-319:43
*** alexchadin has quit IRC19:51
*** caboucha has quit IRC20:20
*** SumitNaiksatam has quit IRC20:29
*** caboucha has joined #openstack-meeting-320:29
*** VW has quit IRC20:42
*** VW has joined #openstack-meeting-320:45
*** jgu_ has quit IRC20:55
*** e0ne has joined #openstack-meeting-320:55
*** raildo has quit IRC20:56
*** mjturek has quit IRC21:00
*** mjturek has joined #openstack-meeting-321:01
*** krtaylor has joined #openstack-meeting-321:02
*** david-lyle has quit IRC21:03
*** krtaylor has quit IRC21:03
*** david-lyle has joined #openstack-meeting-321:04
*** krtaylor has joined #openstack-meeting-321:04
*** e0ne has quit IRC21:09
*** e0ne has joined #openstack-meeting-321:32
*** cleong has quit IRC21:33
*** numans has quit IRC21:36
*** numans has joined #openstack-meeting-321:36
*** slaweq has quit IRC21:55
*** slaweq has joined #openstack-meeting-321:56
*** e0ne has quit IRC21:57
*** lyan_ has quit IRC22:26
*** bobh has quit IRC22:32
*** caboucha has quit IRC22:41
*** slaweq has quit IRC22:46
*** markvoelker has quit IRC22:49
*** markvoelker has joined #openstack-meeting-322:49
*** markvoelker has quit IRC22:54
*** markvoelker has joined #openstack-meeting-322:56
*** julim has quit IRC22:56
*** markvoelker has quit IRC22:59
*** markvoelker has joined #openstack-meeting-323:00
*** markvoelker has quit IRC23:05
*** mjturek has quit IRC23:09
*** hongbin has quit IRC23:53

Generated by 2.15.3 by Marius Gedminas - find it at!