08:59:58 <priteau> #startmeeting blazar
08:59:59 <openstack> Meeting started Tue Mar 19 08:59:58 2019 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:00 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:02 <openstack> The meeting name has been set to 'blazar'
09:00:04 <priteau> #topic Roll call
09:00:22 <masahito> o/
09:01:00 <tetsuro> o/
09:01:30 <priteau> Hi masahito & tetsuro
09:02:18 <priteau> I see bertys is online as well.
09:02:25 <bertys> o/ sorry I am late, hi all
09:02:47 <priteau> Agenda for today:
09:02:50 <priteau> 1. Denver Summit Project Update
09:02:53 <priteau> 2. Stein release
09:02:58 <priteau> 3. Train PTL
09:03:00 <priteau> 4. AOB
09:03:24 <priteau> #agenda Denver Summit Project Update
09:03:26 <priteau> #topic Denver Summit Project Update
09:03:51 <priteau> Our project update is now listed on the schedule: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23722/blazar-project-update
09:04:15 <priteau> bertys isn't displayed in the speaker list, I just emailed them to rectify
09:04:40 <priteau> Thank you tetsuro and bertys for volunteering!
09:04:56 <masahito> Thank you
09:05:36 <tetsuro> :)
09:06:03 <priteau> I have created a new slide deck which I dropped in our shared folder, you should all be able to edit it.
09:06:09 <priteau> #link https://docs.google.com/presentation/d/177YVZhWH25E_FeBXfiWbZ_FwL3cFczbh5zmxHvbEGug/edit
09:07:41 <priteau> I updated the first slide with date / location / speakers, rotated the release slides, and created a new slide to talk in more details about our work with Neutron
09:09:02 <priteau> Please, update as you see fit
09:09:59 <priteau> Do you have any questions?
09:10:29 <priteau> masahito: It would nice if you could add some details about floating IP reservation
09:10:42 <masahito> okay.
09:12:07 <priteau> tetsuro: Can you please check that all the placement information is up to date?
09:12:27 <tetsuro> sure. I'll update that slide.
09:12:46 <priteau> Thank you.
09:13:15 <priteau> We can decide in another meeting who talks when. Unless you have other comments, let's talk about the Stein release.
09:14:17 <priteau> #topic Stein release
09:15:06 <priteau> RC1 is very close now. A release patch has been proposed already: https://review.openstack.org/#/c/644304/
09:15:21 <priteau> We have a deadline of Thursday to update it.
09:16:27 <priteau> I would like to merge floating IP reservation and the affinity code by then.
09:17:24 <priteau> Affinity patch series only has two minor open patches:
09:17:31 <priteau> #link https://review.openstack.org/#/c/642969/
09:17:35 <priteau> #link https://review.openstack.org/#/c/636817/
09:17:47 <priteau> bertys and masahito, could you please review?
09:18:15 <masahito> ah, Added +2 and W+1 right now.
09:19:02 <masahito> For the latter.
09:19:43 <priteau> Thank you
09:21:14 <priteau> For floating IP reservation, what is the status? I did review and testing at the end of last week and noticed that the update_lease patch had been dropped from the series and was out of date (it didn't support multiple requested IPs)
09:22:36 <masahito> Its statuses are
09:23:43 <masahito> 1. reserved_floatingips key in Get or List lease API are not implemented yet because it needs some change to db_api.lease_get or lease_list method to query allocation info.
09:25:07 <masahito> 2. the releasenote has not been pushed to the gerrit b/c I want to discuss it include "the floating ip reservation is experimental" or not.
09:26:05 <masahito> 3. I missed the patch for the update API. I try to update in one day.
09:26:14 <masahito> that's a current status.
09:26:58 <priteau> Thanks masahito
09:27:40 <priteau> Having tested floating IP reservation, I think it works well enough, it doesn't have to be called "experimental"
09:28:13 <priteau> But, it isn't fully implemented since we won't ship client support in Stein and we haven't even started working on blazar-dashboard support
09:28:42 <priteau> We could call it "incomplete", following this categorisation of Nova features
09:28:45 <priteau> #link https://docs.openstack.org/nova/latest/user/feature-classification.html#feature-group-maturity
09:29:23 <masahito> Make sense to me.
09:29:56 <masahito> We don't have enough docs for the floating ip reservation as well.
09:30:40 <priteau> I've started working on a CLI doc based on my client implementation
09:30:47 <masahito> I try to write the release note.
09:31:37 <masahito> For the client side, the CLI works for the floating IP reservation unless an user doesn't specify required_fip key.
09:32:18 <bertys> FYI. As soon as I get the okay from Zuul, will merge https://review.openstack.org/#/c/644514
09:32:44 <priteau> masahito: I thought I had tried it on Friday and it worked, maybe I got confused
09:33:06 <priteau> Now that the spec is merged, can we also start merging the base patches for floating IP?
09:33:43 <priteau> Once bertys has approved 644514
09:35:43 <priteau> masahito: have you tested my CLI patch?
09:36:40 <masahito> priteau: Not yet. Sorry, I didn't notice the patch.
09:37:07 <priteau> https://review.openstack.org/#/c/639763/
09:38:00 <masahito> thanks
09:39:57 <priteau> bertys and tetsuro, would you be able to review masahito's code? We can start merging the base patches, they don't need to merge all at the same time
09:41:00 <tetsuro> I'll start to review them though I don't have enough time to review all of them this week.
09:44:08 <priteau> This will be too late for RC1 and it will be hard to justify merging this code past RC1 :(
09:44:24 <priteau> We are already doing an exception as we're past feature freeze
09:45:00 <priteau> bertys: do you have some time for review?
09:46:03 <bertys> Quite challenging as I am out of office tomorrow.
09:47:32 <priteau> Given that this new feature is not changing any of the instance/host reservation code, would you be OK with me merging it with just my +2? And of course the code comes from a core reviewer so it has masahito's implied +2 :-)
09:48:59 <masahito> :-)
09:49:42 <tetsuro> Okay.
09:49:43 <priteau> I know this is bending the rules, but we will still have some time after RC1 to fix issues.
09:50:41 <priteau> I don't think there would be any though. The extra plugin first has to be loaded via blazar.conf to even work.
09:51:32 <priteau> bertys: what do you think?
09:51:45 <bertys> It is okay. Please go ahead.
09:52:41 <priteau> Great, thank you.
09:52:55 <priteau> We just have a few minutes left with the meeting.
09:53:26 <priteau> Sorry, I missed the first call for cycle highlights
09:53:39 <priteau> I just noticed the reminder this morning.
09:53:47 <priteau> "cycle-highlights are due with your rc1"
09:54:38 <priteau> Reminder, cycle highlights are short sentences focusing on the major changes of the release
09:54:43 <priteau> e.g. in Rocky: https://releases.openstack.org/rocky/highlights.html
09:55:34 <priteau> I think ours should be anti-affinity/no affinity support, floating IP reservation, and the allocation API
09:56:02 <priteau> I will draft something and share with you for review, OK?
09:56:08 <tetsuro> +1
09:56:14 <masahito> +1
09:56:23 <bertys> +1
09:57:14 <priteau> Great. Please let me know if we should add another feature that I forgot.
09:57:22 <priteau> #topic Train PTL
09:57:58 <priteau> The election period is not finished yet, but since there are no other candidates I guess I will be PTL for the Train cycle
09:58:06 <priteau> Thank you for your support :-)
09:59:13 <priteau> First focus is on finishing the Stein release, then we can think about Train
09:59:22 <priteau> #topic AOB
09:59:24 <priteau> Anything else?
10:00:41 <masahito> Nothing from my side.
10:00:51 <tetsuro> nothing
10:01:48 <priteau> Looks like we're done. Thanks a lot!
10:01:55 <priteau> Bye everyone
10:01:57 <priteau> #endmeeting