20:00:02 <johnsom> #startmeeting Octavia
20:00:03 <openstack> Meeting started Wed Jan 25 20:00:02 2017 UTC and is due to finish in 60 minutes.  The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:00:06 <openstack> The meeting name has been set to 'octavia'
20:00:14 <johnsom> Hi there folks!
20:00:22 <rm_work> o/
20:00:25 <nmagnezi> o/
20:00:26 <ankur-gupta-f2> howdy
20:00:30 <sindhu> hi
20:00:41 <xgerman> o/
20:00:43 <ndahiwade> o/
20:00:52 <johnsom> #topic Announcements
20:01:12 <johnsom> Ocata-3 is this week.  That means feature freeze.
20:01:41 <johnsom> I plan to start locking things down today, starting with neutron-lbaas.
20:02:25 <johnsom> I really hope we can get the RedHat/Centos patch in so I may delay octavia freeze to tomorrow or maybe even early Friday.
20:02:48 <nmagnezi> doing my best to finish
20:02:49 <nmagnezi> :)
20:02:57 <nmagnezi> with your help
20:03:08 <johnsom> If there are any neutron-lbaas patches you think we should get in, please let me know.  I think we have a pretty good handle on the octavia patches.
20:03:30 <rm_work> we still have ... how long for bugs?
20:03:45 <rm_work> there's a bug fix i'd like to get in if possible (the barbican consumer thing from the ML)
20:03:50 <rm_work> I assume we have a couple weeks?
20:04:02 <johnsom> Feb 13th
20:04:07 <rm_work> k
20:04:07 <johnsom> Week there of
20:04:43 <johnsom> We have a PTG topics list here:
20:04:45 <johnsom> #link https://etherpad.openstack.org/p/octavia-ptg-pike
20:04:58 <johnsom> If you have additional items we should discuss at the PTG
20:05:25 <johnsom> Also, I spent some time this week to update our roadmap page.  It was extremely out of date.
20:05:33 <johnsom> #link https://wiki.openstack.org/wiki/Octavia/Roadmap
20:05:45 <perelman> Hi all
20:05:54 <johnsom> Please let me know if you have comments/feedback/ideas
20:06:26 <johnsom> Any other announcements today?
20:06:33 <xgerman> UDP ha
20:06:43 <johnsom> Yeah, it has been on there....
20:07:01 <johnsom> Someone recently opened an RFE too.  I asked for use case details....
20:07:41 <johnsom> Ok, moving on
20:07:51 <johnsom> #topic Brief progress reports / bugs needing review
20:07:59 <johnsom> Still working on lbaas-merge items:
20:08:06 <johnsom> #link https://etherpad.openstack.org/p/octavia-ocata-merge-review-priority
20:08:16 <johnsom> And if you all have time
20:08:24 <johnsom> #link https://etherpad.openstack.org/p/Active-_Active_Topology_commits
20:08:39 <perelman> Thanks :)
20:08:50 <xgerman> I think last time we asked how to test that?
20:08:59 <johnsom> I have been focused on helping a new user get their environment setup and helping out with the RedHat/CentOS patch
20:09:07 <johnsom> xgerman yes
20:09:55 <johnsom> I have found some bugs along the way and have either fixed them or opened launchpad bugs to track.
20:10:24 <nmagnezi> johnsom, the python3 one, right?
20:10:27 <johnsom> I know there has been some good work on the v2 API as well, so happy to see that
20:10:33 <xgerman> +1
20:10:42 <perelman> I think we have there some explanation.  I will try tomorrow to add more. I am sorry just came back from ski :)
20:11:02 <johnsom> Yeah, a couple of python 3 issues and some error handling for client libraries (neutron-client, etc.)
20:11:10 <nmagnezi> #link https://review.openstack.org/#/c/424851/
20:11:23 <johnsom> perelman Nice, I hope you had good snow
20:11:28 <xgerman> +1
20:11:40 <perelman> It was +2 :))))
20:12:20 <johnsom> nmagnezi Yeah, I found some issues in active/standby under python3.  That patch fixes those.
20:12:57 <johnsom> Any other updates/patch discussions?
20:13:13 <rm_work> i'll have some next week after the freeze is done
20:13:21 <rm_work> nothing for this week
20:13:32 <johnsom> #topic Octavia ocata version
20:14:08 <johnsom> Ok, I just wanted to run it by the team.  I was chatting with rm_work about the up coming release.  He proposed version 0.10.0 for ocata.
20:14:08 <rm_work> 0.10 ?
20:14:31 <johnsom> I like that.  I think we should hold 1.0 for the version with a functional API.
20:14:36 <johnsom> Any thoughts/comments?
20:14:45 <rm_work> Yep, what johnsom said
20:14:59 <nmagnezi> sounds reasonable
20:15:02 <xgerman> +1
20:15:25 * xgerman thinks the industry should go back to year, e.g. Octavia 2017
20:15:45 <johnsom> Ha, but we do two releases a year...
20:15:53 <johnsom> 2017.5?
20:15:54 <xgerman> dog years?
20:16:00 <rm_work> yeah ^^ was just going to say 0.5
20:16:01 <nmagnezi> johnsom, 2017s
20:16:02 <nmagnezi> :D
20:16:03 <rm_work> or by month like ubuntu
20:16:09 <rm_work> 2017.03
20:16:28 <johnsom> #topic Allow creating a loadbalancer with provided "vip { network_id }" in addition to current "vip { subnet_id }" [rm_work]
20:16:45 <johnsom> rm_work - you have the floor on your agenda item
20:17:05 <rm_work> So... yeah. This.
20:17:08 <rm_work> Basically, it would be nice to allow someone to be less specific if they'd like
20:17:20 <rm_work> it doesn't buy much with the current AAP network driver, but with others it would be very good
20:18:02 <johnsom> So, I think we have this...
20:18:03 <johnsom> https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/extensions/lb_network_vip.py
20:18:20 <rm_work> AH it's in n-lbaas extended
20:18:24 <rm_work> I was looking for that
20:18:33 <rm_work> it isn't in octavia at all, but obviously will be soon
20:18:35 <johnsom> I still scratch my head a bit about how we pick a subnet from the network if there is more than one subnet under the network
20:18:45 <rm_work> random.choice(network.subnets)? :P
20:19:01 <johnsom> Well, yeah, currently nlbaas creates the vip and just hands it to us
20:19:04 <xgerman> and random is off and you have them all in one subnet
20:19:05 <rm_work> I mean, if the user doesn't want to be specific, it must be on purpose?
20:19:30 <rm_work> Yeah, so this will actually be in the API as of the merge? in that case, my agenda item is complete :P
20:19:49 <rm_work> what's with "is_visible": False
20:20:16 <johnsom> Yeah, we need to track it as I don't know that it is properly documented, so it might be easy to miss if they also didn't do the test updates.....
20:20:53 <johnsom> rm_work It is a hidden attribute.  It won't show in get calls, etc
20:21:40 <rm_work> hmm
20:21:44 <rm_work> why is that :/
20:21:48 <rm_work> just not necessary?
20:21:52 <rm_work> I guess it doesn't matter
20:22:07 <rm_work> POST the network_id, we pick a subnet, it'll have a subnet selected to return and they can work up the chain
20:22:11 <rm_work> ok then yeah I'm good on my end
20:22:45 <johnsom> Yeah, looking at the patch, they didn't include tests outside of unit tests.  So, please keep us honest on this and make sure we don't miss it.
20:22:56 <johnsom> It's not in the docs
20:23:43 <rm_work> definitely will :)
20:23:43 <johnsom> #topic Open Discussion
20:24:06 <johnsom> Bonus points for writing an API test to cover it....
20:24:07 <johnsom> Grin
20:24:21 <johnsom> Any other topics for today?
20:25:36 <johnsom> Wow, nice.  Lunch time for me then....
20:25:40 <rm_work> o/
20:25:42 <xgerman> :-)
20:25:43 <johnsom> Thanks folks for joining
20:25:44 <xgerman> o/
20:25:57 <nmagnezi> o/
20:26:02 <johnsom> #endmeeting