09:00:03 #startmeeting blazar 09:00:04 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 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:07 The meeting name has been set to 'blazar' 09:00:11 #topic Roll call 09:00:22 o/ 09:00:54 Hello masahito 09:02:11 I spot tetsuro as well 09:03:37 0/ 09:04:08 No bertys however 09:04:33 Well, let's start 09:05:14 Agenda for today is code review and next meetings 09:05:20 #topic Code review 09:06:04 I see tetsuro's placement patch was just approved 09:07:00 Yes, I added W+1 just now. 09:07:10 Thanks a lot. I will begin another series to enable affinity. 09:08:06 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 Right. The gate job failure is just I forgot to update unit tests when I changed the response body schema. 09:09:42 I fixed it. 09:10:25 Thank you 09:10:43 Finally we can have this functionality for stein-2 :) 09:11:41 Small patches that are easy to review: 09:11:58 New version of Asmita's patch for min/max IntOpt values: https://review.openstack.org/#/c/625514/ 09:12:13 Mailing list address update… https://review.openstack.org/#/c/625244/ 09:13:01 Another one: https://review.openstack.org/#/c/621925/ 09:14:49 Small typo fix from me: https://review.openstack.org/#/c/625607/ 09:16:50 I would like to discuss what to do for the mutable config patch 09:16:52 https://review.openstack.org/#/c/585847/ 09:17:23 There is nothing wrong with the patch itself, it is implemented as it should be 09:17:43 However, it is not possible to use the functionality because blazar-manager doesn't like receiving a SIGHUP 09:18:06 Looks like meaning less patch for current blazar. 09:18:32 I'm okay to go the patch. 09:18:43 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 +1. reasonable 09:21:12 +1 09:21:24 I will change the commit message to reflect the fact that it doesn't yet work though 09:25:01 Updated commit message: https://review.openstack.org/#/c/585847/ 09:25:04 Please review 09:26:41 Done 09:26:59 Great 09:28:00 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 yes. I'm checking and replying the comment now. 09:29:52 I want to talk Akihiro's comment that Blazar should have a config which declares a set of floating IP address. 09:31:19 What about this approach: 09:31:23 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 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 And it checks that the IP *is* within the CIDR network 09:32:34 This way, the admin doesn't have to manually keep the blazar config in sync with the Neutron state 09:32:51 What do you think? 09:34:01 That's what I was thinking for the spec. Of course, it makes sense. 09:35:04 Let's propose this then 09:35:06 Ahh, I didn't mention any validation in the spec. 09:35:33 It would be that's why he commented. 09:35:49 okay, I reply it. 09:37:52 Do you have only the spec or have you started writing some code as well? 09:38:38 nothing 09:39:46 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 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 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 Nice 09:44:52 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 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 Many of these already have a fix in Chameleon, it often just needs a test case and a release note 09:46:29 I will let you know if any don't have anything started that you could work on 09:47:44 got it. 09:48:59 11 minutes left, let's talk about the next meetings. 09:49:08 #topic Next meetings 09:49:32 As you probably know, next Tuesday is Christmas and the Tuesday after is New Year's Day 09:49:44 So I propose that we cancel both meetings 09:49:51 +1 09:49:58 Next meeting would be on January 8 09:51:00 That's just after the stein-2 milestone. Will you have some time for code review until then? 09:51:29 (via Gerrit, not IRC meeting) 09:51:51 I'll work until on 28th Dec and start on 7th Jan. 09:52:57 So I have some days to review the codes. 09:53:50 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 #topic AOB 09:55:02 Anything else to discuss? 09:56:26 The next Summit and PTG is announced. http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000961.html 09:57:51 I'm not sure I can attend it now. 09:58:14 Thanks for sharing. I am not sure I will be there, it's not a great timing for me. 09:59:00 We can discuss closer to the date. Early bird registration is open until February 1st. 09:59:54 That's all for today. Thanks for joining 10:00:02 Have a great holiday season. 10:00:05 #endmeeting