09:00:03 <priteau> #startmeeting blazar
09:00:04 <openstack> Meeting started Tue Dec 18 09:00:03 2018 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:07 <openstack> The meeting name has been set to 'blazar'
09:00:11 <priteau> #topic Roll call
09:00:22 <masahito> o/
09:00:54 <priteau> Hello masahito
09:02:11 <priteau> I spot tetsuro as well
09:03:37 <tetsuro> 0/
09:04:08 <priteau> No bertys however
09:04:33 <priteau> Well, let's start
09:05:14 <priteau> Agenda for today is code review and next meetings
09:05:20 <priteau> #topic Code review
09:06:04 <priteau> I see tetsuro's placement patch was just approved
09:07:00 <masahito> Yes, I added W+1 just now.
09:07:10 <tetsuro> Thanks a lot. I will begin another series to enable affinity.
09:08:06 <priteau> masahito: I see you pushed an update to the resource allocation series. I haven't had time to review them this morning but will try to do so today. If I recall correctly it was the unit tests that needed an update.
09:09:17 <masahito> Right. The gate job failure is just I forgot to update unit tests when I changed the response body schema.
09:09:42 <masahito> I fixed it.
09:10:25 <priteau> Thank you
09:10:43 <priteau> Finally we can have this functionality for stein-2 :)
09:11:41 <priteau> Small patches that are easy to review:
09:11:58 <priteau> New version of Asmita's patch for min/max IntOpt values: https://review.openstack.org/#/c/625514/
09:12:13 <priteau> Mailing list address update… https://review.openstack.org/#/c/625244/
09:13:01 <priteau> Another one: https://review.openstack.org/#/c/621925/
09:14:49 <priteau> Small typo fix from me: https://review.openstack.org/#/c/625607/
09:16:50 <priteau> I would like to discuss what to do for the mutable config patch
09:16:52 <priteau> https://review.openstack.org/#/c/585847/
09:17:23 <priteau> There is nothing wrong with the patch itself, it is implemented as it should be
09:17:43 <priteau> However, it is not possible to use the functionality because blazar-manager doesn't like receiving a SIGHUP
09:18:06 <masahito> Looks like meaning less patch for current blazar.
09:18:32 <masahito> I'm okay to go the patch.
09:18:43 <priteau> I am proposing that we merge the patch but, if we cannot resolve the SIGHUP issue at the time of the Stein release, we create a release note containing an "issues" block
09:20:29 <tetsuro> +1. reasonable
09:21:12 <masahito> +1
09:21:24 <priteau> I will change the commit message to reflect the fact that it doesn't yet work though
09:25:01 <priteau> Updated commit message: https://review.openstack.org/#/c/585847/
09:25:04 <priteau> Please review
09:26:41 <masahito> Done
09:26:59 <priteau> Great
09:28:00 <priteau> masahito: Will you push an update to your floating IP spec? There are some comments from Akihiro Motoki. https://review.openstack.org/#/c/609302/
09:28:45 <masahito> yes. I'm checking and replying the comment now.
09:29:52 <masahito> I want to talk Akihiro's comment that Blazar should have a config which declares a set of floating IP address.
09:31:19 <priteau> What about this approach:
09:31:23 <masahito> His suggestion is Blazar has a config option to declare 1. a set of IP addresses blazar can assign for floating IPs or 2. a set of IP address ranges blazar cannot assign for floating IPs.
09:31:44 <priteau> When we create a floating IP in Blazar, Blazar fetches the subnet info from Neutron and verifies that the IP is *not* inside the allocation range
09:32:07 <priteau> And it checks that the IP *is* within the CIDR network
09:32:34 <priteau> This way, the admin doesn't have to manually keep the blazar config in sync with the Neutron state
09:32:51 <priteau> What do you think?
09:34:01 <masahito> That's what I was thinking for the spec. Of course, it makes sense.
09:35:04 <priteau> Let's propose this then
09:35:06 <masahito> Ahh, I didn't mention any validation in the spec.
09:35:33 <masahito> It would be that's why he commented.
09:35:49 <masahito> okay, I reply it.
09:37:52 <priteau> Do you have only the spec or have you started writing some code as well?
09:38:38 <masahito> nothing
09:39:46 <priteau> OK. I am in the opposite situation: I have an implementation of network segment reservation (VLAN, VXLAN, etc.) but no spec yet ;-)
09:40:38 <priteau> The spec for network segments will follow broadly the same approach as floating IP: Blazar can allocate networks outside of the tenant range.
09:42:47 <priteau> We needed the implementation for internal use, but I think I will be able to write a spec and share it early next year
09:43:29 <masahito> Nice
09:44:52 <priteau> I think we've covered most of the patches. Over the next few weeks I hope to make some progress with pushing Chameleon bug fixes upstream, so there will be more to review.
09:45:01 <masahito> It looks like some bug reports for s-2 are assigned to you now.  Do you have time to hit these? If I have time, I can take over some patches.
09:45:57 <priteau> Many of these already have a fix in Chameleon, it often just needs a test case and a release note
09:46:29 <priteau> I will let you know if any don't have anything started that you could work on
09:47:44 <masahito> got it.
09:48:59 <priteau> 11 minutes left, let's talk about the next meetings.
09:49:08 <priteau> #topic Next meetings
09:49:32 <priteau> As you probably know, next Tuesday is Christmas and the Tuesday after is New Year's Day
09:49:44 <priteau> So I propose that we cancel both meetings
09:49:51 <masahito> +1
09:49:58 <priteau> Next meeting would be on January 8
09:51:00 <priteau> That's just after the stein-2 milestone. Will you have some time for code review until then?
09:51:29 <priteau> (via Gerrit, not IRC meeting)
09:51:51 <masahito> I'll work until on 28th Dec and start on 7th Jan.
09:52:57 <masahito> So I have some days to review the codes.
09:53:50 <priteau> Great. I will work the rest of this week and maybe some between 26 and 31. Then back on the 7th of Jan
09:54:56 <priteau> #topic AOB
09:55:02 <priteau> Anything else to discuss?
09:56:26 <masahito> The next Summit and PTG is announced. http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000961.html
09:57:51 <masahito> I'm not sure I can attend it now.
09:58:14 <priteau> Thanks for sharing. I am not sure I will be there, it's not a great timing for me.
09:59:00 <priteau> We can discuss closer to the date. Early bird registration is open until February 1st.
09:59:54 <priteau> That's all for today. Thanks for joining
10:00:02 <priteau> Have a great holiday season.
10:00:05 <priteau> #endmeeting