17:00:29 <johnsom> #startmeeting Octavia 17:00:30 <openstack> Meeting started Wed Jul 12 17:00:29 2017 UTC and is due to finish in 60 minutes. The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:35 <openstack> The meeting name has been set to 'octavia' 17:00:55 <johnsom> Hi folks 17:01:01 <sanfern> hi 17:01:02 <gans> hello 17:01:40 <johnsom> Outlook is fighting with me. I updated it for our new time, but I guess it didn't update the full series. Sigh 17:01:43 <jniesz> hi 17:01:47 <johnsom> At least I am here on time... 17:01:47 <nmagnezi> o/ 17:02:08 <evgenyf> o/ 17:02:08 <johnsom> #topic Announcements 17:02:19 <johnsom> We are heading towards feature freeze Pike-3 July 24th 17:02:38 <johnsom> My normal reminder, just a few days left for new features in Pike 17:03:04 <johnsom> Also, I released python-octaviaclient 1.1.0 yesterday. It fixes the l7rules issue. 17:03:22 <johnsom> We have closed out our Pike community goals, py35 support and uwsgi 17:03:29 <johnsom> So, that is good stuff. 17:03:58 <johnsom> Also, our docs have moved under the new scheme: https://docs.openstack.org/octavia/latest/ 17:04:02 <xgerman_> o/ 17:04:16 <johnsom> The old developer link will still work for some time, but this is the new location. 17:04:39 <johnsom> I did a basic restructuring to fit the new standard. We can probably polish more, but it is a start. 17:05:05 <johnsom> The presentation deadline for Sydney is soon. 17:05:35 <johnsom> Two more days. 17:05:41 <nmagnezi> don't forget to share a link for us to vote when time comes :) 17:05:46 <johnsom> FYI, I do not plan to attend Sydney 17:06:06 <johnsom> #link https://www.openstack.org/summit/sydney-2017/call-for-presentations/ 17:06:35 <johnsom> Any other announcements this week? 17:07:42 <johnsom> #topic Brief progress reports / bugs needing review 17:07:56 <johnsom> #link https://etherpad.openstack.org/p/Octavia-Pike-priority-patches 17:08:17 <johnsom> We are tracking a set of priority patches for Pike at that link. If you can, please help review 17:08:31 <johnsom> Also, nmagnezi asked for reviews on: 17:08:38 <johnsom> #link https://review.openstack.org/#/c/469850/ 17:08:44 <johnsom> #link https://review.openstack.org/#/c/464332/ 17:09:42 <johnsom> I have been focused on Docs, governance, and API performance improvement issues recently. 17:10:01 <johnsom> This week I have some internal stuff to attend to, so will mostly be doing reviews and such. 17:10:09 <johnsom> Any other progress updates to share? 17:10:46 <nmagnezi> about tripleO 17:10:56 <nmagnezi> we are close to merging this: https://review.openstack.org/#/c/447496/ 17:11:06 <sanfern> review on https://review.openstack.org/#/c/478385/10 17:11:07 <nmagnezi> next step would be to have this fully automated as well 17:11:08 <xgerman_> Yeah!! 17:11:10 <nmagnezi> just FYI. 17:11:26 <johnsom> Cool stuff 17:11:33 <johnsom> #link https://review.openstack.org/#/c/478385/10 17:11:56 <johnsom> sanfern FYI, we use the #link tag to get the URLs in the minutes. 17:12:15 <sanfern> ok 17:12:28 <johnsom> It highlights it a bit more 17:12:39 <johnsom> #topic Discuss publishing amphora images (xgerman_) 17:12:59 <johnsom> xgerman_ I think you wanted to talk about publishing amp images 17:13:04 <xgerman_> yes 17:13:25 <xgerman_> #link https://governance.openstack.org/tc/resolutions/20170530-binary-artifacts.html 17:14:04 <xgerman_> so the image building process has been a source for a lot of confusion for our users so I was wondering we could provide some artifacts to ease them into Octavia 17:14:16 <johnsom> Reading through that it seems like the TC's stance is "you are on your own" 17:14:26 <xgerman_> yep 17:15:16 <xgerman_> we would only provide stable images and not provide very timely updates aka if their is a security issue we might not get around pushing an update immediately 17:15:37 <xgerman_> but if some vendor wants to step into doing that more timely… 17:15:45 <xgerman_> anyhow, throughts? 17:16:10 <johnsom> Yeah, that is my big concern about this. They would be heavily "at your own risk" unless we do something like a daily build with the base OS updates 17:16:35 <xgerman_> yeah, it might be more to help non-production users 17:17:03 <xgerman_> but there is always the risk people ignore our disclosures… 17:17:32 <johnsom> From the sound of the resolution we might not be able to get infra support to do daily builds either... 17:18:09 <xgerman_> yeah, I think it would be manual for a while unless we get some server somewhere 17:18:12 <johnsom> Yeah, plus it's hard to include disclosures that are prominent with images. Maybe if we gz them or something 17:18:43 <johnsom> Anyone else have input on this? 17:19:08 <xgerman_> nmagnezi? 17:19:17 <johnsom> He just stepped away 17:20:01 <sanfern> can we send some kind of alert on security patch release so users can update 17:21:12 <johnsom> In theory yes. Basically it would trigger any time that base OS vendor pushes a new cloud image. 17:21:12 <xgerman_> since twe only monitor security issues in Octavia actively I doubt we will be able to for the OS 17:21:24 <johnsom> Again, I'm not sure we have the infra for that right now. 17:21:54 <xgerman_> yeah, I think it will be a journey from building images occasionally to setting up more infrastructure 17:21:57 <johnsom> I guess the question I have for this group is, would you find value in it? Was building your own image easy enough? 17:22:27 <johnsom> I have to say as well, those cloud images roll pretty often 17:23:44 <jniesz> I would imagine there is custom packages that a lot of people will add when building their images 17:24:18 <johnsom> Yeah, I know most production shops customize the image to some degree 17:24:22 <jniesz> and we are building our own images already 17:24:46 <xgerman_> yeah, my big concern are those evaluating Octavia and to speed up some 3rd party stuff (e.g. OSA) 17:27:25 <johnsom> Yeah. So, I think the "best" solution would be a daily build if we can find a place to host that. Highly label it DEMO or something. 17:27:36 <xgerman_> yep 17:27:49 <johnsom> DEMO-WARNING-NOT-PRODUCTION-You-have-been-warned.gz 17:27:58 <johnsom> Grin 17:28:11 <jniesz> +1 17:28:24 <xgerman_> wonder how my free dropbox feels about that ;- 17:28:27 <xgerman_> ) 17:28:31 <johnsom> xgerman_ Do you want to ask infra about it? 17:28:39 <xgerman_> sure, I can ask 17:28:54 <johnsom> Ok, let's at least inquire if they would support us in that. 17:29:02 <xgerman_> #action (xgerman) ask infra about daily image build 17:29:38 <johnsom> Ok, anymore on that topic for today? 17:30:19 <johnsom> #topic Discuss having a scenario tests gate the runs with ACTIVE_STANDBY amphoras (nmagnezi) 17:30:35 <johnsom> So, yes, we need that. grin 17:30:42 <xgerman_> +1 17:30:43 <johnsom> Not sure if he is back or not. 17:31:02 <johnsom> FYI, I have setup a new repo for our go forward tempest tests: 17:31:11 <johnsom> #link https://github.com/openstack/octavia-tempest-plugin 17:31:30 <johnsom> It looks like there will be a community goal for queens for projects to move to this model. 17:32:08 <johnsom> In reality our tempest tests need to be re-written using the new "tempest way". 17:33:49 <johnsom> The other challenge we have had with act/stdby is the infra hosts have limited resources, so spinning up the VMs could be a problem. But we can cross that bridge when we get there. 17:34:24 <johnsom> I think really it comes down to do we have someone that can spend some time working on octavia-tempest-plugin and modernizing our tempest suite. 17:34:52 <xgerman_> we should probably apply at the summer of code ;-) 17:36:05 <johnsom> Yes! Interns! Grin 17:36:26 <johnsom> Our last intern wrote most of the act/stdby code. 17:36:57 <xgerman_> yeah, maybe we need to wrk with some local college and hand out coursework 17:37:50 <johnsom> Hmmm, if I had the cycles I would hit up the local university. I know they have done OpenStack courses in the past. 17:37:55 <xgerman_> wasn’t there some QA team in OpenStack we could pawn things to? 17:38:25 <johnsom> Umm, yeah, well, I think that team is short on folks now too. 17:39:00 <johnsom> They have been helpful with "how-to" type questions and such, but I don't think they are in the business of writing tests at the moment 17:39:42 <xgerman_> ok, I guess we are not solving this today 17:39:43 <johnsom> Anyway, it will probably become a focus for Queens if nothing else. 17:40:08 <xgerman_> in Queens we also need to nail down the vendor driver stuff 17:40:15 <johnsom> Yeah, if anyone wants to help there... 17:40:29 <johnsom> Oh definitely, if we don't get started earlier 17:40:50 <johnsom> #topic Open Discussion 17:41:06 <johnsom> Since we have twenty minutes left, any other topics today? 17:41:25 <johnsom> Oh! 17:41:30 <xgerman_> ? 17:41:48 <johnsom> FYI, there is another L3 Active/Active discussion scheduled for Friday. 17:42:02 <cpuga> I'd like to request a review on flavor spec #link https://review.openstack.org/#/c/392485/ 17:42:24 <johnsom> #link http://lists.openstack.org/pipermail/openstack-dev/2017-July/119565.html 17:42:56 <xgerman_> Ok, on th Active-Active front I reworked https://review.openstack.org/#/c/313006/ to make the distributor table look more like the one jsniez proposed 17:43:19 <xgerman_> comments welcome 17:43:37 <johnsom> cpuga it looks like there is a docs error, the new file needs to be added to an index. 17:44:14 <cpuga> I'll take care of that, thx. 17:44:28 <xgerman_> yeah, I think we are close with flavors 17:44:38 <xgerman_> but that also hinges on the 3rd party interface 17:44:55 <johnsom> It will go in here: https://github.com/openstack/octavia/blob/master/doc/source/contributor/index.rst 17:45:13 <johnsom> Actually, that is odd since I have a wild card.... 17:45:38 <johnsom> Oh, I renamed the directory for the new docs migration stuff 17:46:11 <jniesz> yes, I remember having to change mine from 1 to 1.0 17:46:14 <johnsom> Yeah, flavors is on our priority review list. 17:46:38 <johnsom> Yeah, sorry about that. The docs stuff is all getting changed due to the docs team reducing scope. 17:47:00 <johnsom> Octavia docs should be pretty stable now. 17:47:24 <johnsom> Other topics or concerns? 17:48:15 <johnsom> #link https://etherpad.openstack.org/p/Octavia-Pike-priority-patches 17:48:18 <jniesz> xgerman_ the change looks good to support [] for lb and amphora for distributor model 17:48:21 <johnsom> Ok, off to do reviews! 17:48:31 <xgerman_> thanks 17:48:46 <johnsom> #endmeeting