Thursday, 2018-08-02

*** namnh has joined #openstack-meeting-300:04
*** namnh has quit IRC00:10
*** pbourke has quit IRC00:12
*** mjturek has quit IRC00:17
*** hongbin has joined #openstack-meeting-300:22
*** namnh has joined #openstack-meeting-301:08
*** namnh has quit IRC01:13
*** namnh has joined #openstack-meeting-301:35
*** namnh has quit IRC01:59
*** namnh has joined #openstack-meeting-302:08
*** psachin has joined #openstack-meeting-302:21
*** e0ne has joined #openstack-meeting-302:23
*** e0ne has quit IRC02:23
*** witek has quit IRC02:25
*** witek has joined #openstack-meeting-302:27
*** tellesnobrega has quit IRC02:29
*** bobh has joined #openstack-meeting-302:40
*** bobh has quit IRC02:41
*** bobh has joined #openstack-meeting-302:41
*** bobh has quit IRC02:46
*** gcb has quit IRC03:07
*** Guest43757 has quit IRC03:08
*** yamamoto has quit IRC03:20
*** witek has quit IRC03:33
*** namnh has quit IRC03:44
*** hongbin has quit IRC03:46
*** yamamoto has joined #openstack-meeting-303:55
*** witek has joined #openstack-meeting-303:57
*** yamamoto has quit IRC04:09
*** yamamoto has joined #openstack-meeting-304:40
*** yamamoto has quit IRC04:47
*** yamamoto has joined #openstack-meeting-304:55
*** yamamoto has quit IRC05:05
*** fnordahl has joined #openstack-meeting-305:05
*** yamamoto has joined #openstack-meeting-305:06
*** yamamoto has quit IRC05:06
*** Luzi has joined #openstack-meeting-306:12
*** liuyulong has joined #openstack-meeting-306:52
*** lkoranda has quit IRC07:23
*** lkoranda has joined #openstack-meeting-307:28
*** sgrasley_ has quit IRC07:36
*** yamamoto has joined #openstack-meeting-307:41
*** SotK has quit IRC07:45
*** zerick has quit IRC07:46
*** zerick has joined #openstack-meeting-307:47
*** tssurya has joined #openstack-meeting-308:26
*** Marcin_ has quit IRC08:59
*** pcaruana has joined #openstack-meeting-309:00
*** SotK has joined #openstack-meeting-309:07
*** calbers has joined #openstack-meeting-309:27
*** yamamoto has quit IRC10:02
*** yamamoto has joined #openstack-meeting-310:26
*** yamamoto has quit IRC11:00
*** tellesnobrega has joined #openstack-meeting-311:01
*** tellesnobrega has quit IRC11:04
*** rajinir has quit IRC11:04
*** lamt has quit IRC11:04
*** mattw4_ has quit IRC11:04
*** sergek_ has quit IRC11:04
*** alex_didenko has quit IRC11:04
*** yamamoto has joined #openstack-meeting-311:05
*** alex_didenko has joined #openstack-meeting-311:05
*** calbers has quit IRC11:08
*** calbers has joined #openstack-meeting-311:10
*** mjturek has joined #openstack-meeting-312:37
*** tssurya has quit IRC12:51
*** tssurya has joined #openstack-meeting-312:54
*** raildo has joined #openstack-meeting-312:55
*** tellesnobrega has joined #openstack-meeting-313:24
*** Luzi has quit IRC13:35
*** bobh has joined #openstack-meeting-313:52
*** tosky has joined #openstack-meeting-313:57
*** jeremyfreudberg has joined #openstack-meeting-313:57
tellesnobrega#startmeeting sahara14:00
openstackMeeting started Thu Aug  2 14:00:28 2018 UTC and is due to finish in 60 minutes.  The chair is tellesnobrega. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
tellesnobregashow off hands14:01
tellesnobregao/14:01
jeremyfreudbergo/14:01
tellesnobregatosky?14:02
jeremyfreudberg..14:04
tellesnobrega#topic News/Updates14:04
*** openstack changes topic to "News/Updates (Meeting topic: sahara)"14:04
toskysorry14:04
toskyhere14:04
tellesnobregaSahara R3 was release last week as well as saharaclient 2.014:05
jeremyfreudbergwelcome tosky14:05
tellesnobregayesterday I went through storyboard bugs, we might need to go through it during ptg and try to prioritize the bugs14:06
tellesnobregaso we can try to bring those numbers down14:06
jeremyfreudbergi'll be testing s3 on cdh soon, if there is a bug found i will try to get it included in rocky, same idea for apiv2 bugs14:07
jeremyfreudbergbeyond that i have some doc to write14:07
toskyyou can create a board or worklist for that14:07
tellesnobregatosky, good idea14:07
jeremyfreudbergoh, and not sure if tellesnobrega saw my message the other day, but my tsp request was approved14:08
jeremyfreudbergfor this ptg14:08
tellesnobregajeremyfreudberg, did not see it. That is awesome14:08
jeremyfreudbergtosky: you won't be there, right?14:09
tellesnobregaI think he will make it, not sure just yet14:10
toskyI'm probably going to be there14:10
jeremyfreudbergoh, nice, keep us posted14:10
tellesnobregamore updates?14:10
*** njohnston has joined #openstack-meeting-314:11
tellesnobregalets move on14:12
tellesnobrega#topic sahara-extra14:12
*** openstack changes topic to "sahara-extra (Meeting topic: sahara)"14:12
tellesnobregaSotK, about sahara-extra I talked with doug and sean yesterday and the idea is to backport everything to stable/rocky14:12
tellesnobregaI can write the patches14:13
tellesnobregaI plan to do it today14:13
tellesnobregathe alternative was to drop stable/rocky branch and the work was going to be too much and involve too many people, since there are only 5 patches, we can backport easily14:13
jeremyfreudbergbackporting is fine14:14
jeremyfreudbergi guess the bigger question is, should we adjust the release cadence of sahara-extra from cycle-with-whatever (i'm not looking at the file right now) to independent14:14
jeremyfreudbergi think there is value in releases/tags for sahara-extra, but they don't seem to relate to the main release cycle14:15
tellesnobregaI have to check, but the way it is right is ok, it was a mistake by the script and myself to merge the patch to create stable/rocky14:15
tellesnobregaI shouldn't have created that14:15
*** hongbin_ has joined #openstack-meeting-314:16
jeremyfreudbergtosky: thoughts?14:16
toskybut which patch exactly created stable/rocky?14:17
toskythat's the part where I didn't get - for some older M release?14:17
tellesnobregatosky, https://review.openstack.org/#/c/586182/14:17
toskybecause I don't remember recent 5 patches, so it must have happened some time ago14:17
tellesnobregait created based on the last release14:17
tellesnobregabasically was a timing issue, it created as a library14:18
tellesnobregaso it picked up stuff from last release14:18
jeremyfreudberglooks more like sean did it by accident: https://github.com/openstack/releases/commits/master/deliverables/rocky/sahara-extra.yaml14:18
jeremyfreudbergit went from library->other, but sean missed that14:18
tellesnobregathey have a script that does that, and it failed to detect the type14:18
tellesnobregaexactly14:18
tellesnobregaanything else on this?14:21
jeremyfreudbergi think we are all on the same page on this, with at least a short term plan14:21
tellesnobregayes14:21
tellesnobregalets move on14:21
tellesnobrega#topic Stein PTG14:21
*** openstack changes topic to "Stein PTG (Meeting topic: sahara)"14:21
tellesnobregaI will start an etherpad, probably next week, so we can start planning the PTG discussions14:22
tellesnobregakeep an eye for it and start thinking on topics for the week14:22
jeremyfreudbergbtw, i will most likely only be at ptg on sahara days, leaving on wednesday14:23
jeremyfreudbergpending confirmation from the Foundation's travel agent14:24
tellesnobregasounds good, I will be the whole week, if you need me to attend something I can do it14:24
jeremyfreudbergtellesnobrega: thanks!14:25
jeremyfreudbergi'll let you know14:25
tellesnobregacool14:25
tellesnobregaI don't have anything specific to discuss today14:26
tellesnobregado you have anything else?14:26
jeremyfreudbergwell, we still have the hardware for CI. we still don't really know how make sahara-ci-config work, and i've had no time14:26
jeremyfreudbergbut, just a reminder that it exists14:27
tellesnobregathat might be better for PTG14:27
tellesnobregaface14:27
jeremyfreudbergyes, the actually work we can save till then14:27
jeremyfreudbergor even if not the work, the discussion14:27
*** mjturek has quit IRC14:27
tellesnobregaface to face we might come up with a quicker solution14:27
jeremyfreudbergjust wanted to drop the reminder now14:27
tellesnobregathanks14:27
jeremyfreudbergthat's it from me14:28
jeremyfreudbergtosky: anything from you?14:28
toskynot for now about the PTG14:30
tellesnobregatosky, any other topic?14:30
toskyS3 vs S3a, but I don't have resources to try to fix it14:31
toskyit impacts the tests I'm writing14:32
tellesnobregaok14:32
tellesnobregalet me change topics14:32
jeremyfreudbergtosky: assume that the current s3 types will stay the same. if there's a change like that it will be accompanied by a whole new interface14:32
tellesnobrega#topic S3 vs S3a14:32
*** openstack changes topic to "S3 vs S3a (Meeting topic: sahara)"14:32
toskyI don't think this change would require a new interface14:34
jeremyfreudbergtosky, it wouldn't require a new interface, no14:35
toskyit's just allowing the users to use s3:/ URI also for data sources14:35
tosky(or the job binaries, I always mix them)14:35
jeremyfreudbergit's the DS which uses s3a now14:35
jeremyfreudbergtosky: is your only complaint about the abstraction the s3 vs s3a, or do you have other ideas?14:38
toskyonly the abstraction14:38
jeremyfreudbergyou mean, only the url format14:39
jeremyfreudbergnothing else about the abstraction14:39
toskyyes, exactly14:40
jeremyfreudbergso, should it just allow either protocol? (and munge s3->s3a as needed?)14:42
tellesnobregaI think we should use just one s314:42
jeremyfreudbergwell, i guess you also have your complaint about the http/https for the endpoint14:42
tellesnobregaand munge s3->s3a where needed14:42
toskythat's maybe more tricky, but s3/s3a is immediately visible14:44
jeremyfreudbergthe http/https thing is actually more bothersome to me14:44
jeremyfreudbergbut, to each his own14:45
jeremyfreudbergthe http/https thing is already more solidified though, because of the --s3-ssl flag in OSC, so that's harder to backpedal14:46
jeremyfreudbergthe s3->s3a we could really just sneak in now with nobody noticing (if we supported both formats)14:47
toskyyes, that's what I thought as well14:49
tellesnobregaI think it works14:49
jeremyfreudbergokay, i think i can write a patch that will allow either s3 or s3a to go in14:51
jeremyfreudbergand change the doc, though, to say that s3 is the 'real' way14:51
jeremyfreudbergand i think we can sneak that into rocky14:51
toskythanks14:51
jeremyfreudbergrc1 is a week from today, right?14:52
toskyyes14:52
jeremyfreudbergexcellent14:52
tellesnobregayes14:52
tellesnobregawe have time14:52
jeremyfreudberganything else?14:53
tellesnobregathanks tosky for bringing it up and jeremyfreudberg for the work14:53
tellesnobreganot for me14:53
jeremyfreudbergnp14:53
kaiokmotellesnobrega: can I include some quick info/update to the meeting? it's OSA related14:53
jeremyfreudbergkaiokmo, go ahead14:53
tellesnobregayes please14:54
kaiokmook. so, as long as rocky release is near, and ubuntu bionic is now supported on openstack, the osa team is working to add bionic support on all roles, including sahara14:55
*** bobh has quit IRC14:55
kaiokmothe work seems pretty consistent, and looks like sahara support for bionic is almost done, along with existing xenial, centos7 and opensuse ones14:56
toskythanks for that, I've seen few reviews on openstack-ansible-os_sahara14:56
tellesnobregakaiokmo, awesome, keep us posted and ping us if needed14:57
kaiokmotellesnobrega: no problem. will do14:57
toskykaiokmo: is there any plan to switch the Bionic jobs to python 3, or are they going to stay python 2 for now?14:58
kaiokmoI don't know about that, but I've seen some patches related to python314:59
*** yushiro4 has joined #openstack-meeting-314:59
*** mlavalle has joined #openstack-meeting-314:59
mlavalle#startmeeting neutron_l315:00
openstackmlavalle: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.15:00
*** jeremyfreudberg has quit IRC15:00
toskytellesnobrega: I think you can close now15:00
kaiokmoon xenial, at least, there's on-going work on python3.15:00
*** yushiro4 has left #openstack-meeting-315:00
tellesnobregawill do15:00
toskywe are out of time and people are pushing15:00
kaiokmoI can update you guys later on sahara channel15:00
tellesnobrega#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:01
openstackMeeting ended Thu Aug  2 15:01:00 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
mlavallesorry, didn't mean to push you guys15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2018/sahara.2018-08-02-14.00.html15:01
tellesnobregasorry mlavalle15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2018/sahara.2018-08-02-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2018/sahara.2018-08-02-14.00.log.html15:01
*** tosky has left #openstack-meeting-315:01
tellesnobregathanks everyone15:01
mlavalletellesnobrega: I apologize. I didn't mean to be pushy15:01
tellesnobregano worries ;)15:01
mlavalle#startmeeting neutron_l315:01
openstackMeeting started Thu Aug  2 15:01:30 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
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
haleybhi15:01
manjeetshello15:01
mlavallehey, how are you guys?15:01
haleybgood, too busy, you?15:02
mlavalleabout the same ;-)15:03
manjeetsdoing ok15:03
mlavalle#topic Announcements15:03
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:03
mlavalleWe are in the middle of wrapping up our RC-115:04
mlavalleI want to thank haleyb, slaweq, manjeets, njohnston for the non stopping reviewing over the past few days15:05
mlavalleThanks to you we are in excellent shape15:05
mlavallewe have merged almost everything we wanted to merge in the neutron repo15:05
manjeets:)15:05
mlavalleThe only exception are:15:05
*** alexpilotti has quit IRC15:06
mlavalle1) https://review.openstack.org/#/c/58807915:06
manjeetsthat can go as well, just a minor update needed ?15:06
mlavalleThis is a release note for port forwardings, that I realized yesterday that we hand't included15:06
*** davidsha_ has joined #openstack-meeting-315:06
mlavalleI see manjeets comment and I'll address it when we finish the meeting. I have a question. Is there a specific section for 'config' in the reno format?15:07
manjeetsmlavalle, other: can be used15:07
mlavallemanjeets: ok, I'll use that15:08
haleyband i didn't see any bugs approved for rc1 either, we should probably look through the list and see if anything is important15:08
slaweqmlavalle: there is no such section: https://docs.openstack.org/reno/2.1.2/usage.html#editing-a-release-note15:08
mlavalleslaweq: thanks. I'll use other as suggested by manjeets15:09
mlavallehaleyb: let's do that today and tomorrow15:09
mlavallegood idea15:09
mlavalle2) The only other part missing are some patches for neutron-fwaas. I asked them today to attend tomorrow the drivers meeting to check at that point how they are doing with those patches15:10
mlavalleI rebased and +2ed yesterday the 2 patches they needed on the Neutron side and slaweq caught and alnded them overnight15:12
mlavalleso we have done everything out of their control for them to land the feature in fwaas15:12
mlavallenow it's up to them15:12
mlavalleit's lookin tight, though, based on what ws mentioned earlier today in the fwaas weekly meeting15:13
mlavallein other news, remember the that the PTG will take place on September 10 - 14 in Denver15:14
mlavalleI am staying at the Renaissance hotel15:14
mlavallearriving on Sunday and staying until Saturday15:14
mlavalleLooking forward to see you all there15:15
mlavalleI will start the etherpad today15:15
slaweqI have the same plan like You :)15:15
mlavalleso we can brainstorm ideas to be discussed there15:15
mlavalleslaweq: Great!15:15
haleybi'm sunday to friday15:15
manjeetssunday to friday (Renaissance hotel)15:15
mlavalleNow a bit of bad news....15:16
mlavalleYou guys are stuck with me for another cycle as the Neutron PTL15:16
davidsha_:P15:16
manjeetslol15:16
slaweqLOL15:16
mlavalleLOL15:17
davidsha_Congratz!15:17
mlavalleThanks!15:17
slaweqI was afraid that You will say that You are stepping down :)15:17
slaweqCongratz mlavalle!15:17
mlavalleI love this team, so it's an honor15:17
mlavalleas I said in my nomination15:18
manjeetsMAGA/MANA ? lol mlavalle for 201815:18
mlavallethe highest in my careet15:18
mlavallecareer15:18
mlavalleok, let's move on....15:18
mlavalle#topic Bugs15:18
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:18
mlavallesince we have slaweq's attention, I want to start with https://bugs.launchpad.net/neutron/+bug/176670115:19
openstackLaunchpad bug 1766701 in neutron "Trunk Tests are failing often in dvr-multinode scenario job" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)15:19
mlavalleI've been using the searches that I posted earlier in the bug for kibana15:20
mlavalleand I don't get any hist over the past 7 days15:20
mlavalleslaweq: have you seen cases of those failures lately in you investigations in gerrit?15:20
slaweqno15:21
*** psachin has quit IRC15:21
slaweqbut it's probably like that because those tests are marked as unstable: https://github.com/openstack/neutron-tempest-plugin/blob/master/neutron_tempest_plugin/scenario/test_trunk.py#L14415:21
slaweqso they will be skipped in case of failure15:21
mlavalleso I will create a DNM patch removing the the skip on those test and recheck it constantly15:23
mlavallemakes sense?15:23
slaweqyep15:23
mlavalleok15:23
mlavallethanks15:23
slaweqif You will now work on it, we can even merge such patch and remove unstable_tests() in master15:23
slaweqwill be maybe easier to spot it15:23
slaweqand IIRC it was failing in jobs which are non-voting15:24
mlavalleright15:24
mlavalleok, let's do that15:24
mlavalleI'll propose a patch later today15:24
slaweqok15:24
*** bobh has joined #openstack-meeting-315:25
mlavallemoving on to https://bugs.launchpad.net/neutron/+bug/177445915:25
openstackLaunchpad bug 1774459 in neutron "Update permanent ARP entries for allowed_address_pair IPs in DVR Routers" [High,Confirmed]15:25
mlavallehaleyb: do you think this should be a subject to discuss in the PTG?15:25
haleybmlavalle: yes, based on Swami's last comment it seems it needs some more thought15:26
mlavalleok, I will add it to the etherpad later today, when I start it15:26
mlavallehaleyb: do you have handy the DVR bugs that yamamoto pointed out in his bugs report earlier this week?15:28
* mlavalle looking for the message15:28
yamamotohttps://bugs.launchpad.net/neutron/+bug/1783470  https://bugs.launchpad.net/neutron/+bug/178365415:29
openstackLaunchpad bug 1783470 in neutron "get_subnet_for_dvr returns SNAT mac instead of gateway in subnet_info" [Undecided,In progress] - Assigned to Arjun Baindur (abaindur)15:29
openstackLaunchpad bug 1783654 in neutron "DVR process flow not installed on physical bridge for shared tenant network" [Undecided,New]15:29
haleybthink they were the new ones15:29
mlavalleyes they are15:29
mlavallethanks yamamoto!15:29
haleyb^^ i'm looking at that now, seems a bug, fix was proposed15:29
haleybhttps://review.openstack.org/#/c/58723415:30
haleybi can see an optimization there as well that i'll do as a follow-on15:30
mlavallewow, this is a first time contributor!15:30
mlavalletime to show how welcoming we are :-)15:30
haleybi think he found a couple of these new bugs15:31
mlavalleok, let's take a look at the bug itself and the proposed patch15:31
mlavalleat first glance, it will probably require some tests15:32
haleybpatch looks ok, just needs a test15:32
haleybjynx :)15:32
mlavallelol15:32
mlavallethe other bug is also from him15:33
mlavallehe hasn't proposed a fix yet15:33
mlavalleif haleyb doesn't have bandwidth, I can take a look15:33
haleybhttps://bugs.launchpad.net/neutron/+bug/178365415:33
openstackLaunchpad bug 1783654 in neutron "DVR process flow not installed on physical bridge for shared tenant network" [Undecided,New]15:33
haleybdoh, you already pasted that15:34
mlavalleyeah, I can take a look at it if you don't have bandwidth15:34
haleybmlavalle: if you have bandwidth, else i'll look today/tomorrow15:35
mlavalleI'll start with it then and yell for help if I get to deep in c... water15:35
mlavallehaleyb: do you have any other bugs?15:36
haleybi think there's 2 more new one15:36
haleybhttps://bugs.launchpad.net/neutron/+bug/178372815:36
openstackLaunchpad bug 1783728 in neutron "DVR: router interface creation failure (load testing)" [High,In progress] - Assigned to Oleg Bondarev (obondarev)15:36
*** sambetts|afk is now known as sambetts15:36
haleybfrom oleg our old friend15:37
haleybhttps://review.openstack.org/#/c/586059/15:37
mlavallewow, nice to see him again ;-)15:37
haleyband i already +2'd that, i forgot to add you15:37
haleybi guess if you're ok we have one for rc115:37
mlavalleI just added it to my pile15:37
mlavalleI'll take a look. at first glance seems ok for rc115:38
haleybhttps://bugs.launchpad.net/neutron/+bug/1784837 was the other15:38
openstackLaunchpad bug 1784837 in neutron "Test tempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps.test_in_tenant_traffic fails in neutron-tempest-dvr-ha-multinode-full job" [Medium,Confirmed]15:38
haleybcreated by slaweq yesterday15:39
mlavalleI think we mentioned in the CI meeting that he was going to look at those failures15:40
mlavalleI'll try to take a look this week as part of my bugs deputy duties15:40
slaweqyep15:40
slaweqI found that this test failed few times recently so I reported it15:41
slaweqI don't have any other details about it15:41
mlavalletahnks for the info slaweq15:41
mlavalleany other bugs we should discuss today?15:42
mlavalleok, let's move on15:43
mlavalle#topic Openflow DVR15:43
*** openstack changes topic to "Openflow DVR (Meeting topic: neutron_l3)"15:43
davidsha_Hey15:44
mlavallewe failed to merge this in Rocky15:44
mlavallelet's see if we can move it forward in Stein15:44
davidsha_kk, We're too late to try for an exception for https://review.openstack.org/#/c/528336/ ?15:44
*** elmiko has joined #openstack-meeting-315:45
mlavalleI think we are15:45
davidsha_kk.15:45
mlavallebut let's start looking at merging all this as early as possible during Stein15:45
davidsha_ack, code can't be merged until the week after the PTG correct?15:46
mlavalleis there any update fon your part davidsha_ ?15:46
davidsha_I'm continuing to support Xubo on the work, but it's his feature.15:47
mlavalleok15:47
davidsha_Thanks15:48
mlavallemaybe you have answered this before, but other than configuring the normal parameters for DVR, is there anything else I need to know to deply this feature in a devstack?15:48
mlavalledavidsha_: ^^^^15:48
davidsha_Nope, it's just setting the agent_mode=dvr_bridge15:49
mlavalleok, cool15:49
mlavallemoving on15:49
mlavalle#topic Open agenda15:49
*** openstack changes topic to "Open agenda (Meeting topic: neutron_l3)"15:49
mlavalleI will be in China the week of August 13 - 1715:50
mlavalleso I might not make it to this meeting15:50
mlavalleanything else?15:51
davidsha_Nothing from me.15:51
*** dtantsur has joined #openstack-meeting-315:51
mlavalleok guys, thanks for attending15:51
davidsha_Thanks!15:51
manjeetsI am visiting Uk for 2 weeks, but i'll try to attend meetings15:52
mlavallemanjeets: ack15:52
mlavalle#endmeeting15:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:52
openstackMeeting ended Thu Aug  2 15:52:16 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2018/neutron_l3.2018-08-02-15.01.html15:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2018/neutron_l3.2018-08-02-15.01.txt15:52
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2018/neutron_l3.2018-08-02-15.01.log.html15:52
*** cdent has joined #openstack-meeting-316:00
elmiko#startmeeting api sig16:00
openstackMeeting started Thu Aug  2 16:00:15 2018 UTC and is due to finish in 60 minutes.  The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: api sig)"16:00
openstackThe meeting name has been set to 'api_sig'16:00
elmiko#chair cdent elmiko edleafe dtantsur16:00
openstackCurrent chairs: cdent dtantsur edleafe elmiko16:00
dtantsuro/16:00
elmiko#link https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda16:00
elmikohey folks =)16:00
edleafegeez, just one second before I hit return to start the meeting!16:00
elmikohahaha16:00
* edleafe needs to type faster16:00
elmikoit is a sort of free-for-all at the start there16:01
cdento/16:01
elmikoand here i thought i was waiting before hitting return16:01
elmiko#topic previous meeting action items16:01
edleafeoh sure, rub it in. We all get it, you can type fast16:01
*** openstack changes topic to "previous meeting action items (Meeting topic: api sig)"16:01
elmiko#link http://eavesdrop.openstack.org/meetings/api_sig/2018/16:02
elmikoin fairness, i just cut and pasted16:02
dtantsurheh16:02
elmikothere, now the secret is out16:02
elmikoso, how far did everyone make it through the draft?16:02
edleafeI did16:03
* edleafe gives himself a cookie16:03
cdentI read the whole thing16:03
* elmiko gives edleafe another cookie16:03
* edleafe gives cdent a cookie too16:03
elmikoi made it about 80% through16:03
cdentI even gossiped about the parts I didn't agree with with someone16:03
* elmiko gives cdent another cookie16:03
elmikoooh, bonus points for cdent !16:03
cdentikr16:03
edleafeWhich parts were those?16:03
cdentThe part I didn't agree with was about not using specific 4xx responses16:04
dtantsurI disagree with a few things, this being one of them16:04
* dtantsur tries to remember16:04
dtantsuroverall the thing did not read like something breaking16:05
edleafeI read it nearly a week ago, so the specifics are a bit fuzzy16:05
elmikofor the most part, i found it to be quite sane, my concern for us is going through it more closely to ensure that we haven't make guidance that contradicts (assuming we adopt it as a starting point for something)16:05
dtantsura lot of "do not", but not much "instead do"16:05
cdentyeah, it wasn't particularly revolutionary, sort of gentle intro to REST with some pragmatism added in16:05
elmiko++16:05
dtantsurI think we had something contradicting, but I cannot remember16:06
* dtantsur needs to re-read it16:06
edleafeI felt that a large part of our HTTP guidelines could have been replaced with "hey, read this"16:06
cdentI wasn't really expecting it to provide much in the way of guidance for us, more sort of a lemon zesty refresher from the outside world, squeezed upon our staid interiors16:07
elmikothat would really help spread the load of our guidance edleafe , i'm ++16:07
cdentit _would_ be good to link to it16:07
edleafeSomehow reading an IETF draft proposal doesn't conjure up "lemon zesty" in my mind16:07
cdentperhaps where we say "in the absence of direct guidance look at the rfcs" we could also say "and this good overview"16:07
elmikoi'm kinda curious about our next steps here, like should we review it at a more detailed level? publish a link? wait for it to finalize?16:08
cdentbecause in the end what we want is to be globally consistent16:08
elmikoagreed cdent16:08
cdentI can take that action16:08
elmikosweet, thanks!16:08
cdent#action cdent add links to mnot http protocol thing16:08
edleafeI think our guidelines need to be more succinct than this draft16:08
cdentyes16:09
edleafeBut yeah, linking to it would be excellent16:09
cdentthere's much refactoring and refining it would be good to do16:09
edleafethat draft is almost as wordy as a mordred patch!16:09
elmikohaha16:09
dtantsurlol16:09
* elmiko notes "almost"16:09
cdentunpossible16:09
mordrednothing is that wordy16:09
elmiko=D16:10
elmikoany other comments on this topic?16:10
cdentThe showrunners for the api-sig have mordred pop up over the backstage wall for a few million $$ every few episodes16:10
cdentand then he fades away16:10
elmikoLOL16:10
dtantsur:D16:10
elmikoso good16:10
elmiko#topic open mic and ongoing or new biz16:11
*** openstack changes topic to "open mic and ongoing or new biz (Meeting topic: api sig)"16:11
elmikoi guess we didn't clean up the kruft here, but anything to discuss that is not the draft thingie?16:11
cdentanything we need/want to think about PTG-wise?16:11
edleafeI was thinking that the PTG would be a good place to discuss the draft thingy in more detail16:12
elmikowho is going to be there?16:12
*** mlavalle has left #openstack-meeting-316:12
edleafeI'm hoping to go16:12
edleafeBut IBM is still dragging their collective feet on travel approval16:12
* mordred would like to actually meet with y'all this ptg instead of not doing that like I have done at the last few16:12
mordrededleafe: I do not want to visualize IBM's collective feet16:12
cdentedleafe: you could almost drive up and camp in the halls16:12
* elmiko chuckles16:13
edleafeheh16:13
cdenti'll be there16:13
edleafemordred: actually, just my grand-boss16:13
elmikoit's very unlikely that i will be there16:13
elmikowhich makes me sad =(16:13
edleafeYou say that every time16:13
elmikohaha, i know16:13
edleafeand then you show up16:13
elmikobut this time i feel the winds have changed16:13
elmikoroad trip?16:14
mordredelmiko: I'd suggest that your employer is crazy if they think they should not send you to the PTG16:14
mordredbut, you know, that may just be me16:14
* cdent will fly to detroit, pick up elmiko, go visit cdent's niece in Louisville, then drive to denver?16:14
cdentROAD TRIP16:15
elmikoROAD TRIP16:15
cdentsadly my flights are already booked :(16:15
cdentotherwise that's a great idea16:15
elmikomordred: yeah, i just know some things are changing for our travel budget and i am loathe to push too hard16:15
* dtantsur is not going16:15
edleafeSounds like National Lampoon's Vacation16:15
*** tssurya has quit IRC16:16
cdentSo it might be just me and mordred coming up with ways to enshrine and work around microversion simultaneously16:16
elmikosounds like it16:16
mordredcdent: we can make so many decisios16:16
mordreddecisions16:16
cdent\o/16:16
elmikoand hopefully some sort of update on the graphql situation (assuming one of them is there)16:16
mordredor more probably decisios16:16
edleafeYeah, still no reply from Gilles16:16
elmikoack16:17
dtantsurI'll be looking forward to maybe see some of you in Berlin16:17
cdentI'll be there too.16:17
cdentAfter that things will start getting vague16:17
*** spotz has quit IRC16:18
edleafeIt's funny - IBM tends to spend more on travel later in the year16:18
edleafeProbably be easier to get to Berlin than to Denver :)16:18
elmikoi thought about submitting a talk for berlin, but it was really stretching it16:18
* dtantsur submitted two talks16:19
elmikonice! good luck =)16:19
cdentAt some point I'll start an etherpad for the PTG16:19
elmikothanks cdent16:19
cdent#action cdent start etherpad for api-sig at ptg16:19
edleafecdent is action man this week16:20
elmikoyea seriously16:20
cdentdtantsur, mordred : did you make your microversion proposal?16:20
elmikosomeone get that man a cookie16:20
dtantsurcdent: we did16:20
dtantsurand now I suspect *SOMEONE* did not vote for it ;)16:20
mordredwe're gonna tell everyone about microversions16:20
* cdent does not vote16:20
edleafewhat?? Everyone LOVES microversions!!16:21
elmiko"microversion, it's way of life maaaan"16:21
cdentit's too tedious going through all the proposals16:21
cdentespeically since I never go to presentations...16:21
cdentdoesn't seem right16:21
dtantsurwell, I watch the most interesting ones in recording16:21
mordredcdent: but BUZZWORD BUZZWORD is awesome because BUZZWORD BUZZWORD!16:21
dtantsurso I still feel the right to vote for good stuff16:21
elmikohahaha16:21
* cdent saves all his voting karma for destroying brexit16:22
elmikonice16:22
elmikoanything else for open biz?16:22
* edleafe thinks cdent doesn't understand voting karma16:23
elmiko#topic guidelines16:23
*** openstack changes topic to "guidelines (Meeting topic: api sig)"16:23
elmiko#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:23
elmiko#link https://review.openstack.org/#/q/status:open+project:openstack/api-sig,n,z16:23
cdentno news is good news?16:23
elmikoi think there is nothing go on here this week for guidelines16:23
elmikoyea16:23
elmiko#topic bug review16:24
*** openstack changes topic to "bug review (Meeting topic: api sig)"16:24
elmiko#link https://storyboard.openstack.org/#!/project/103916:24
elmikolooks like the same story here as well16:24
cdentsame again16:24
elmiko#topic weekly newsletter16:24
*** openstack changes topic to "weekly newsletter (Meeting topic: api sig)"16:24
elmiko#link https://etherpad.openstack.org/p/api-sig-newsletter16:24
edleafeBefore you do that...16:24
elmikoany volunteers?16:24
edleafeI just remembered16:24
elmikoshould i switch back the topic?16:24
edleafeInfra will be doing the rename for the sig on Friday16:25
elmikoooh, cool16:25
dtantsur\o/16:25
elmikodo we need to update anything more than the agenda wiki?16:25
edleafeSo we can toss all our API-WG business cards16:25
elmikohahaha16:25
edleafeI don't think so, but we'll see16:26
elmikocool, thanks for the update edleafe16:26
edleafeMaking sure that the github links still work and stuff like that16:26
cdentI had some really cool business cards16:26
cdenthttps://www.youtube.com/watch?v=cISYzA36-ZY16:26
elmikolol, knew it16:27
cdent(this is clearly the most fun hour all week, for me)16:27
elmiko=)16:27
elmikoi'm happy to have been part of it16:27
elmikonow, who's gonna write the newsletter?16:28
edleafesame here16:28
edleafeI wrote it last week16:28
elmikook, edleafe is off the hook16:28
cdentI can do it16:28
elmikoi think it's only fair that i do it since cdent was kind enough to take all the actions this week16:28
elmikoeither way16:28
cdentoh yeah, yeah, that16:28
cdentgo for it16:28
elmikok, i'll ping in a bit16:28
elmikothanks everybody!16:29
elmikonow's your chance for a last word =D16:29
edleafeword16:29
elmiko#endmeeting16:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:29
openstackMeeting ended Thu Aug  2 16:29:25 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:29
elmikoXD16:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_sig/2018/api_sig.2018-08-02-16.00.html16:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_sig/2018/api_sig.2018-08-02-16.00.txt16:29
openstackLog:            http://eavesdrop.openstack.org/meetings/api_sig/2018/api_sig.2018-08-02-16.00.log.html16:29
edleafeI got the last word!16:29
elmikoindeed sir!16:29
dtantsur:D16:29
*** dtantsur has left #openstack-meeting-316:29
*** cdent has left #openstack-meeting-316:33
*** yamamoto has quit IRC16:37
*** raildo has quit IRC16:38
*** yamamoto has joined #openstack-meeting-316:40
*** davidsha_ has quit IRC16:42
*** raildo has joined #openstack-meeting-316:42
*** yamamoto has quit IRC16:55
*** apetrich has joined #openstack-meeting-317:08
*** yamamoto has joined #openstack-meeting-317:19
*** yamamoto has quit IRC17:34
*** yamamoto has joined #openstack-meeting-317:35
*** yamamoto has quit IRC17:35
*** yamamoto has joined #openstack-meeting-317:35
*** yamamoto has quit IRC17:35
*** yamamoto has joined #openstack-meeting-318:01
*** yamamoto has quit IRC18:05
*** sambetts is now known as sambetts|afk18:16
*** mjturek has joined #openstack-meeting-318:27
*** mjturek has quit IRC18:31
*** mjturek has joined #openstack-meeting-318:55
*** tellesnobrega has quit IRC19:28
*** apetrich has quit IRC19:47
*** bobh has quit IRC20:27
*** sambetts|afk has quit IRC20:28
*** sambetts_ has joined #openstack-meeting-320:29
*** ChanServ sets mode: -o openstack20:35
*** bobh has joined #openstack-meeting-320:51
*** bobh has quit IRC21:53
*** hongbin_ has quit IRC22:39
*** lkoranda has quit IRC22:46
*** lkoranda has joined #openstack-meeting-322:52
*** bobh has joined #openstack-meeting-322:52
*** xubozhang_ has joined #openstack-meeting-322:58
*** xubozhang_ has quit IRC22:58
*** bobh has quit IRC23:04
*** mjturek has quit IRC23:13
*** xubozhang_ has joined #openstack-meeting-323:19

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