09:01:06 <masahito> #startmeeting blazar
09:01:07 <openstack> Meeting started Tue Apr 24 09:01:06 2018 UTC and is due to finish in 60 minutes.  The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:01:08 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:01:10 <openstack> The meeting name has been set to 'blazar'
09:01:18 <masahito> hi all, time to blazar meeting
09:01:23 <masahito> #topic RollCall
09:02:02 <hiro-kobayashi> o/
09:02:09 <masahito> Todya's agenda is
09:02:18 <masahito> 1. September PTG
09:02:23 <masahito> 2. PlacementAPI support
09:02:30 <masahito> 3. Reservation re-allocation
09:02:32 <masahito> 4. AOB
09:02:35 <masahito> anything else?
09:02:37 <priteau> o/
09:02:43 <masahito> hiro-kobayashi, priteau: hi
09:02:43 <priteau> Good morning masahito and hiro-kobayashi
09:02:55 <masahito> priteau: good morning :-)
09:03:09 <hiro-kobayashi> hi priteau
09:03:23 <masahito> bertys and GeraldK told me they can't join today's meeting.
09:03:55 <masahito> #topic September PTG survey
09:05:04 <masahito> The official announced the next PTG for Stein will be held in Denver on 10th-14th Sep.
09:05:16 <masahito> http://lists.openstack.org/pipermail/openstack-dev/2018-April/129564.html
09:06:17 <masahito> They asked me that we plan to have PTG during this week.
09:07:11 <masahito> Do you both have a plan to join the PTG?
09:07:33 <hiro-kobayashi> Yes, I plan to join it.
09:07:47 <priteau> I can't say yet, it will depend if my employer is happy for me to travel there
09:08:35 <masahito> They also requested me replaying whether to have or not to have until 2nd May.
09:09:00 <masahito> I plan to join it, too.
09:09:44 <priteau> If it's just hiro-kobayashi and you, would you still hold a Blazar meeting there?
09:10:40 <hiro-kobayashi> I hope new people will join it.
09:10:58 <priteau> That would be great.
09:11:38 <masahito> priteau: If it's just us, we can implement new features there instead of discussion.
09:11:49 <priteau> A hackathon? :-)
09:11:56 <masahito> yes :-)
09:12:05 <hiro-kobayashi> Sounds good :-)
09:12:43 <priteau> I will try to let you know if I can attend as soon as possible, but I might know only weeks from now
09:12:43 <masahito> I plan to join other project meeting. So I'll be there in either case.
09:13:59 <masahito> priteau: got it. The early bird ticket will end by 10th May.
09:14:19 <priteau> I will get a ticket anyway, since refund is possible until end of August
09:14:54 <masahito> sounds nice.
09:15:07 <masahito> anything else for this topic?
09:16:33 <masahito> #topic PlacementAPI support
09:17:13 <masahito> I heard hiro-kobayashi has something to discuss for the topic.
09:17:22 <hiro-kobayashi> yes
09:17:41 <hiro-kobayashi> I created an etherpad for discussing placement support: https://etherpad.openstack.org/p/blazar-placement-design
09:18:12 <hiro-kobayashi> I wrote requirements and basic approaches down there.
09:18:57 <hiro-kobayashi> The approach 1, 3 and 4 were basically copied from the Dublin PTG etherpad.
09:19:19 <hiro-kobayashi> I don't understand much about approach 4, though.
09:19:45 <priteau> Thank you hiro-kobayashi for creating the document
09:20:08 <priteau> I think there is also the concept of aggregates in placement API
09:20:35 <masahito> hiro-kobayashi: Nice works.
09:20:46 <hiro-kobayashi> priteau: Yes it would be. I appreciate it if you could write your idea down there
09:21:09 <hiro-kobayashi> And, feel free to edit existing ideas
09:21:47 <hiro-kobayashi> I think it's better to make a consensus on the basic approach in the Blazar team before Vancouver summit.
09:23:00 <priteau> I will review and add more details as soon as possible, hopefully this week
09:23:15 <masahito> I'd like to add some items for each approach. The way of user interaction with Nova will be changed, etc.
09:23:15 <hiro-kobayashi> Thanks priteau!
09:23:31 <hiro-kobayashi> Thanks!
09:23:39 <masahito> Me too. I'll add my comments, too.
09:24:13 <masahito> After one or two weeks later, we should share this to Placement team.
09:24:44 <masahito> As hiro-kobayashi said, that should be done before the Vancouver summit.
09:25:12 <hiro-kobayashi> masahito: Agree.
09:26:49 <masahito> anything else?
09:27:00 <hiro-kobayashi> Nothing from me.
09:27:25 <masahito> #topic Reservation re-allocation
09:28:02 <masahito> I'm working on this spec now. https://docs.openstack.org/blazar/latest/specs/queens/flavors-extra-specs.html
09:28:59 <masahito> I want talk about the third work items, Add re-allocation logic to ComputeHostExtraCapability management.
09:30:14 <masahito> Based on the discussion on gerrit, Blazar needs to re-allocate reservation once the extra_capability is updated, changed or deleted.
09:31:13 <masahito> However, Host delete API doesn't allow cloud admins to remove hosts if there are reservations to use the hosts.
09:32:29 <masahito> IMHO, if the Update Host API follows the way of the Delete Host API, the Blazar shouldn't accept the update itself.
09:32:48 <priteau> One way to resolve the problem would be to prevent extra capability update if the node is reserved
09:33:07 <hiro-kobayashi> priteau: +1
09:33:28 <priteau> However, that is quite a strong requirement. A better way to handle it would be to prevent extra capability update only if the node has reservations that are using resource_properties
09:34:09 <masahito> make sense.
09:34:09 <priteau> But we could start with the first approach, and then make it smarter
09:34:26 <hiro-kobayashi> Good approach
09:35:14 <masahito> Alternative is disabling the host and resource-monitoring re-allocate the reservations.
09:36:18 <priteau> Will it re-allocate a running reservation? I don't remember the behavior
09:37:11 <masahito> When the reservation is active, resource_changed flag becomes true at least.
09:37:13 <hiro-kobayashi> Currently It is not allowed to reallocate if it's active.
09:38:16 <hiro-kobayashi> masahito: I think blazar should not allow reallocate if it's active except a failure recovery situation.
09:38:47 <masahito> hiro-kobayashi: IIRC, in addition to resource_changed flag, the missing_resource flag becomes true if there is no alternative resource.
09:39:31 <hiro-kobayashi> yes
09:40:40 <masahito> hiro-kobayashi: because it raises complexity of Blazar?
09:41:38 <hiro-kobayashi> masahito: yes.
09:42:36 <masahito> got it.
09:42:57 <masahito> That's from my side. any comment for the topic?
09:43:14 <hiro-kobayashi> If blazar allow reallocation of active reservation, blazar has to handle running instances on removed hosts.
09:44:13 <priteau> masahito: I would prefer starting with a simple approach first and increasing complexity later
09:45:04 <hiro-kobayashi> How about alining with host reservation update?
09:45:07 <hiro-kobayashi> https://github.com/openstack/blazar/blob/master/blazar/plugins/oshosts/host_plugin.py#L527
09:45:53 <masahito> I agreed priteau's idea.  I plan to start with your suggestion first.
09:46:22 <masahito> I'd like to talk the goal of the BP.
09:48:01 <masahito> If the reservation is in pending status, Blazar try to re-allocate. If it's in active, it fails. right?
09:48:51 <masahito> Even if the status is in pending, the update is not allowed in case of missing_resource is true.
09:49:12 <hiro-kobayashi> I think that's right.
09:51:01 <masahito> Make sense. Anyway I'll start with the simple way to do this.
09:51:10 <masahito> #topic AOB
09:51:27 <masahito> Does someone have something to share/discuss?
09:51:35 <masahito> last 10 mins
09:52:31 <hiro-kobayashi> Nothing from me
09:53:24 <priteau> I have completed the support for Ironic using Jay's unmerged Nova aggregates patch. The changes to Blazar were quite small.
09:53:49 <masahito> priteau: Great work!
09:54:30 <hiro-kobayashi> Good news!
09:55:54 <priteau> Moving to placement API will probably be a lot more work ;-)
09:56:41 <masahito> Yes. But that's a really good news. We can move things forward.
09:58:01 <masahito> priteau: btw, do you have some specific topics in next meeting now?  The day of next meeting, 1st May., is holiday in Japan.
09:58:17 <priteau> Nothing specific from me.
09:58:28 <priteau> Would you like to skip the meeting?
09:58:43 <masahito> If nothing and bertys and GeraldK also doesn't have nothing, I want to skip the meeting.
09:58:52 <masahito> priteau: yes.
09:59:02 <priteau> No problem
09:59:39 <masahito> I'll ask them later. If they doesn't have no topics, I announce the skipping in openstack-dev ML.
10:01:17 <masahito> Running out of time. Nice discussion and greate updates!
10:01:28 <masahito> Thanks all. bye.
10:01:38 <priteau> Bye everyone, thank you!
10:01:46 <masahito> #endmeeting