20:00:18 #startmeeting Octavia 20:00:20 Meeting started Wed May 16 20:00:18 2018 UTC and is due to finish in 60 minutes. The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:23 The meeting name has been set to 'octavia' 20:00:26 Hi folks! 20:00:31 o/ 20:00:35 hi 20:00:51 o/ 20:00:53 o/ 20:01:01 #topic Announcements 20:01:31 Just a heads up, I am going to cancel next weeks meeting as many of us will be at the OpenStack summit in Vancouver. 20:01:47 o/ 20:02:17 BTW, who all is going to the summit? I know that rm_work/mobile, xgerman, and I will be there. Anyone else? 20:02:47 not me, sorry 20:02:58 * johnsom looks sad 20:03:26 Ok, well, there will at least be three of us representing Octavia. 20:03:39 I'm not 20:03:40 nope 20:03:44 how about you dayou? 20:03:44 I have two sessions, a project update and onboarding. 20:04:12 johnsom, nice! I'll watch those :) 20:04:34 Any other announcements I missed? 20:05:06 #topic Brief progress reports / bugs needing review 20:05:39 I have been focused on getting the provider driver code done. Everything is now posted for review except the driver library for the call backs. 20:05:54 I have a few documentation things to update as well. 20:06:05 And of course working on slides for the summti 20:06:19 Any other progress updates to share today? 20:06:52 There is some good stuff on dashboard. One patch posted makes the panels update status automatically. 20:06:59 Very cool to see actually 20:07:25 Adam has also been very busy getting the tempest plugin going. Great progress there 20:07:45 dayou promised this, and delivered :-) 20:07:58 yes, he has been doing great work on dashboard 20:08:03 +1 20:08:05 +1 20:08:21 I also hope to get some reviews in on some client patches as I would like to do a release for that soon too. 20:08:43 Ah yeah I have some debt in the client 20:08:56 Yeah, I need to add the provider API 20:09:26 The release folks are reminding me that we should have a client release soon-ish 20:09:46 Well the debt I have are for features only in master, so 20:09:51 Less urgent 20:10:06 Any other updates? Rally or Grenade? 20:10:28 I think I'm waiting for reviews on grenade 20:10:46 MS2 is the week of June 4th BTW 20:11:12 yeah, painfully aware 20:11:14 nothing new on Rally, we are at the final stretch with tripleO so it got priority 20:11:15 Ok, cool, good to know! Happen to have the link handy? 20:11:34 right afterwards I'll complete the Rally scenario 20:11:38 but it's in a good shape 20:11:42 Ok, cool 20:11:54 johnsom, yes, both cgoncalves and I can share some URLs to patches 20:12:21 #link https://review.openstack.org/#/c/568089/ 20:12:27 #link https://review.openstack.org/#/c/568138/ 20:12:35 Thanks! 20:12:47 https://review.openstack.org/#/q/(owner:%22Carlos+Goncalves+%253Ccgoncalves%2540redhat.com%253E%22)+OR+(owner:%22Nir+Magnezi+%253Cnmagnezi%2540redhat.com%253E%22+) 20:13:03 i guess that work too :) 20:13:16 I'm stuck in summit prep and travel prep for other stuff too, so I'm basically just trying to get through the reviews I have up already for the rest of this week 20:13:45 #link https://review.openstack.org/#/c/568395/ 20:14:10 #link https://review.openstack.org/#/c/568801/ 20:14:15 We've got a few large chunks of stuff just waiting because everyone is working hard on getting stuff done, but now there is so much done that it's a giant pile of reviews 20:14:29 johnsom, we have bunch more.. 20:14:53 Yep, ok, thanks! 20:14:58 So we may want to do a hardcore review spike during summit off-hours if possible <_< 20:15:10 I'll be prodding people about that 20:15:13 I hope there are off hours… 20:15:18 Lol yeah... 20:15:20 Yeah, I have been trying to mix some in. 20:15:28 I feel like usually we have a bit of time 20:15:46 #topic We need to decide on HTTP status codes for driver issues 20:16:06 So I would like some input on the status codes we want to return for provider driver issues. 20:16:11 rm_mobile, off-hours as in at 2 am? :) 20:16:13 #link https://review.openstack.org/#/c/563795/12/octavia/common/exceptions.py 20:16:22 Lol if need be 20:16:27 Ha, his off ours is like 8am 20:16:37 lol 20:16:52 So I initially picked 5xx for some of those 20:17:07 I think 501 for basically all of them 20:17:11 The bummer is that it would be nice if we never return a 500 on purpose 20:17:34 Well, ProviderNotEnabled is clearly user error and valid with 400 20:17:36 501 != 500 20:17:42 Right 20:17:46 But the rest, 501 20:17:49 Basically they didn't enter a valid driver name 20:18:40 Merged openstack/octavia-dashboard master: Imported Translations from Zanata https://review.openstack.org/567789 20:19:02 501 is "Not Implemented" 20:19:25 406 Not Acceptable for ProviderUnsupportedOptionError? 20:19:35 Which seems wrong for "ProviderDriverError" which is basically the driver raised some unknown exception 20:19:51 I think we should use more of 4xx at a quick glance 20:20:22 406 is typically header stuff I think. 20:20:28 405 Method Not Allowed for ProviderUnsupportedOptionError 20:20:33 4xx is all classified as client errrors 20:20:42 Both not implemented and unsupported option could be 400 as well 20:20:47 Which is why I don't like it 20:20:52 https://http.cat/418 20:21:27 4xx "is intended for situations in which the error seems to have been caused by the client" 20:22:04 Which in most cases here is not at all true 20:22:22 We need to stick with 5xx for server config fails 20:22:33 Depends on if you expect a user asking for a feature knows if the driver supports it or not. lol 20:22:46 Lol 20:22:57 johnsom: +1 20:23:02 Ok time to figure out user intent programmatically 20:23:16 So, maybe switch ProviderNotImplementedError and ProviderUnsupportedOptionError to 400? 20:23:25 No thanks IMO 20:23:30 yep, if it’s a RTFM type situation or the user is left intentionally in the dark about whihc providers are installed and support waht 20:24:09 Well there is an API that tells them which drivers are enabled for use. That is why ProviderNotEnabled is clearly a 400 20:24:39 +1 on 400 20:25:03 Yeah, looking again, 501 not implemented is probably right for those. 20:25:05 Yes that one only 20:25:16 So it's really just ProviderDriverError the catch all 20:25:20 The rest need to be 5xx 20:25:39 Do we leave it 500 or give it something else. 20:26:00 501? 20:26:21 If people don't read the error, 500 gets interpreted as "octavia is broken". But.... in a way that driver is broken 20:27:20 ProviderDriverError 500. driver was expected to fulfill request but failed 20:27:31 I guess my vote is to leave it 500 20:27:46 It's the most accurate technically 20:28:43 Any other votes? I think rm_mobile is 501 on that 20:30:32 I like to blame the user… 20:30:55 Yep 20:31:14 500 I never even read, I just assume the server screwed up 20:31:17 so lean towards 4xx but not strong enought for a vote 20:31:23 Usually it's uncaught explosions 20:31:47 Yeah, that is what this is, uncaught driver explosions 20:32:05 Well, we catch it 20:32:13 And we know kinda what's up 20:32:48 how do other driver based projects do it? neutron? 20:33:01 Ok, well, it doesn't sound like we have strong opinions so I'll leave it to the reviewers votes... 20:33:13 I just thought it would be good to discuss as a team 20:33:28 Yeah 20:33:32 +1 20:33:44 #topic Open Discussion 20:33:51 Any other topics for this week? 20:34:40 oh, I need some OSP tech support 20:35:04 especially why Octavia doesn’t work in OSP 12… 20:35:06 Ha 20:35:25 xgerman_, it's not supported (tm) 20:35:37 what's the status code for that? 4xx or 5xx? :P 20:35:38 that's because.. we don't actually ship it in OSP12 as a supported component :) 20:35:40 Very happy to see the OSP 13-beta release notes with Octavia fully supported 20:35:50 +1 20:35:53 johnsom, indeed :) 20:36:15 anywho, the Tech Preview in 12 doesn’t install the SSL certs — hope that’s fixed in 13 20:36:31 yep! 20:36:46 either use can provide certs or let OSP generate 20:37:01 https://bugzilla.redhat.com/show_bug.cgi?id=1462670 20:37:03 bugzilla.redhat.com bug 1462670 in openstack-tripleo-common "Octavia TripleO support: allow auto-generated or user-provided certificates when configuring octavia" [High,Verified] - Assigned to beagles 20:37:08 yup. and anyhow for OSP13 we'll be happy to get any feedback and fix what's needed 20:37:17 OSP Octavia tracker: https://bugzilla.redhat.com/show_bug.cgi?id=1433523 20:37:19 bugzilla.redhat.com bug 1433523 in openstack-octavia "[Tracker] [Octavia] Full support" [High,Assigned] - Assigned to nmagnezi 20:37:24 somehow my org wants to use OSP12 20:37:31 "Assigned to nmagnezi" 20:37:32 * nmagnezi runs 20:37:46 nmagnezi, you're the squad lead :P 20:37:58 cgoncalves, that was a secret.. 20:37:59 xgerman_, bad! OSP13 is LTS 20:38:06 :) 20:38:39 I am juts an engineer (TM) 20:39:55 Anything else today? 20:40:50 Ok, thanks folks! Enjoy the quiet while we are at the Summit. Great time for reviewing..... grin 20:41:04 #endmeeting