09:01:26 <masahito> #startmeeting blazar 09:01:27 <openstack> Meeting started Tue Jul 10 09:01:26 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:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:01:31 <openstack> The meeting name has been set to 'blazar' 09:01:57 <masahito> #topic RollCall 09:02:00 <priteau> o/ 09:02:14 <hiro-kobayashi> o/ 09:02:24 <masahito> Today's agenda is 09:02:34 <masahito> 1. Non-client libraries release 09:02:42 <masahito> 2. AOB 09:02:46 <masahito> 3. Review meeting 09:02:51 <masahito> anything else? 09:02:57 <tetsuro> o/ 09:03:02 <masahito> priteau, hiro-kobayashi, tetsuro: hello 09:04:13 <masahito> #topic Non-client libraries release 09:05:37 <masahito> FYI, 20th July is final non-client libraries release 09:06:23 <priteau> We don't have any, do we? 09:06:31 <masahito> I'll cut stable/rocky branch if needed and put 2.0.0 tag to blazar-nova, dashboard, tempest 09:07:16 <priteau> masahito: are those considered libraries? 09:07:29 <masahito> oops, you're right, priteau. 09:07:30 <priteau> I thought we would tag them at the same time as blazar 09:07:37 <priteau> End of August 09:07:59 <priteau> Non-client libraries are things like oslo 09:08:08 <masahito> According to the schedule docs it's about oslo and others. https://releases.openstack.org/rocky/schedule.html#final-release-for-non-client-libraries 09:09:02 <masahito> I was confused in pip libraries. 09:10:53 <priteau> The next release step for us should be rocky-3 09:11:03 <hiro-kobayashi> blazar-nova is listed as a library project: https://releases.openstack.org/rocky/index.html#library-projects 09:11:06 <masahito> rocky-3 and client release 09:11:34 <priteau> hiro-kobayashi: good catch! 09:11:58 <priteau> Do we have any pending patches on blazar-nova? 09:12:41 <masahito> I see the one patch https://review.openstack.org/#/c/555355/ 09:12:53 <masahito> hiro-kobayashi: thanks. 09:14:04 <masahito> Looks like the gate log is already removed. Let's wait the gate job result. 09:15:12 <masahito> any comments? 09:16:31 <masahito> #topic AOB 09:16:39 <masahito> less topic today. 09:17:00 <priteau> I noticed we haven't discussed the Berlin summit 09:17:14 <masahito> Before starting review meeting, does someone have some thing to discuss or share? 09:17:19 <priteau> The CFP is July 17 09:17:31 <masahito> priteau: nice catch. 09:17:50 <priteau> That's next Tuesday, so if we want to have Blazar presentations that's the last week to work on it 09:18:46 <priteau> Is anyone planning to submit a talk? 09:18:57 <masahito> Do you all already have idea for blazar OFFICIAL presentation? 09:20:10 <tetsuro> I'm going to submit a talk about the usage of placement from blazar, as a GENERAL presentation. 09:20:28 <priteau> Is there a track for project updates? 09:20:32 <masahito> I plan to submit one talk with OPNFV Doctor project. 09:20:39 <priteau> We can cover new features in Rocky 09:20:45 <hiro-kobayashi> tetsuro: great 09:21:26 <masahito> Usually, TC members ask having project update session after the CFP to PTL. 09:22:06 <masahito> I didn't receive any notice, but I hope there is the update session. 09:22:47 <priteau> The summit is shorter than others, only 3 days 09:22:57 <priteau> Maybe some sessions are not happening 09:23:05 <priteau> It would be good to ask before the CFP closes 09:24:02 <masahito> right, I'll ask TC member later. 09:24:10 <priteau> Thanks! 09:26:42 <masahito> anything else? 09:28:04 <masahito> If nothing, we can move to review meeting. 09:28:21 <tetsuro> I saw a new unit test fails sometimes in local and in gate. http://logs.openstack.org/65/578065/6/check/openstack-tox-py27/555b9af/testr_results.htm 09:28:24 <hiro-kobayashi> i'm oks 09:28:33 <hiro-kobayashi> i'm okay 09:28:45 <tetsuro> I'll submit shortly for this bug report and fix. 09:29:03 <tetsuro> Just to report. 09:29:15 <tetsuro> Nothing else from me. 09:29:16 <masahito> I listed links to series of patches in this meeting agenda page. 09:29:26 <masahito> https://wiki.openstack.org/wiki/Meetings/Blazar 09:29:48 <hiro-kobayashi> tetsuro: that link looks invalid 09:29:55 <masahito> tetsuro: thanks for digging into the bug :-) 09:30:25 <tetsuro> hiro: oops, thanks. http://logs.openstack.org/65/578065/6/check/openstack-tox-py27/555b9af/testr_results.html.gz 09:31:42 <hiro-kobayashi> tetsuro: thanks 09:33:04 <masahito> priteau: IIRC, you're not available after 10am UTC right? 09:33:22 <priteau> I can stay longer 09:35:23 <masahito> got it. So let's start the review from high priority and completed patch. 09:35:44 <masahito> And continuing to next week. 09:36:33 <masahito> Let's start from cleaning time 09:36:46 <masahito> https://review.openstack.org/#/c/575021/ 09:37:07 <hiro-kobayashi> I think the discussion point is default value for the cleaning_time option 09:37:45 <hiro-kobayashi> I set 5 min but priteau and Stig set it's a big change 09:37:56 <hiro-kobayashi> s/set/said/ 09:38:43 <hiro-kobayashi> I think it's reasonable and I'm okay to set zero as a default value. 09:39:01 <masahito> Now that I'm thinking about it, no default change is easy to upgrade and less confusing. 09:39:34 <hiro-kobayashi> Agree. 09:39:40 <priteau> Stig also makes a good point that it can make reservations unaligned with time boundaries 09:40:35 <hiro-kobayashi> Right. It's important for operators. 09:40:46 <priteau> For example, if a user reserves a node for a full day (00:00 to 00:00 the next day), with cleaning time the next user would only be able to reserve from 00:05 09:41:44 <masahito> This example looks fine for me. 09:42:58 <masahito> The Blazar's reservation is similar to hotel booking mechanism. The cleaning time should be placed out of each reservation. 09:43:18 <tetsuro> Yeah, I don't see any problems on that example either. 09:44:29 <priteau> It's just that if users want to keep reservations aligned, they would need to know the cleaning time 09:46:05 <priteau> Anyway, I think hiro-kobayashi was agreeing to set default to zero? 09:46:06 <masahito> ah, it's a case that same one user want to try create two reservation continuously, isn't it? 09:46:22 <hiro-kobayashi> priteau: Do you mean the cleaning time value should be exposed to users? 09:46:32 <hiro-kobayashi> priteau: yes, i agree with zero. 09:46:33 <priteau> Same user or two or more users working together 09:47:12 <priteau> Alice and Bob plan together so that Alice books one node on Monday, Bob the same node on Tuesday 09:47:28 <masahito> I now understand the situation you and Stig mentioned. 09:47:39 <priteau> But Bob is surprised when his reservation starting at 00:00 on Tuesday is rejected 09:47:54 <priteau> When we have resource availability API, that will be easier to handle 09:48:04 <priteau> Blazar will be able to say, reserve from 00:05 09:48:13 <hiro-kobayashi> make sense 09:48:19 <priteau> But at the moment it is trial and error 09:48:25 <tetsuro> I see. 09:48:34 <masahito> From my experience, this type of "user effected config" should be announced by cloud operator. 09:49:41 <priteau> That's right, though if we make default 5 minutes, some operators won't think about announcing it 09:49:43 <masahito> List of AZ names, what reservation plugin is supported in the cloud, and etc 09:49:54 <masahito> right. 09:50:23 <masahito> So setting the default to 0 makes sense to me. 09:50:23 <priteau> hiro-kobayashi: I think the cleaning time will effectively be exposed to users by the resource availability API 09:51:15 <hiro-kobayashi> cool 09:51:44 <priteau> So we are all in agreement to update the patch to set default to 0? 09:52:02 <masahito> yes, of course. 09:52:07 <tetsuro> defaulted to zero makes sense. 09:52:08 <hiro-kobayashi> yes. I'll update and push the patch. 09:52:53 <priteau> Thanks! 09:53:05 <masahito> if nothing more, let's move on to Placement API support 09:53:19 <masahito> spec: https://review.openstack.org/#/c/576343/ 09:53:34 <masahito> patch #1: https://review.openstack.org/#/c/578073/ 09:53:42 <masahito> patch #2: https://review.openstack.org/#/c/578065/ 09:53:48 <masahito> patch #3: https://review.openstack.org/#/c/578637/ 09:53:55 <masahito> patch #4: https://review.openstack.org/#/c/578017/ 09:54:48 <priteau> I am sorry, I haven't had the chance to look at the spec or any of these patches yet 09:54:54 <hiro-kobayashi> I don't plan to add anything to the spec anymore. So, if you think it's okay, let's merge it. 09:55:01 <masahito> For Rocky cycle, I'm happy the spec is merged at least. If the patch series are merged, it's great. 09:55:04 <hiro-kobayashi> priteau: np :-) 09:55:59 <priteau> I will have some minor comments on the spec 09:57:11 <masahito> The spec has concrete description, so I hope it's easy to merge. 09:57:29 <tetsuro> I haven't seen the latest PS of the spec, sorry, but the PS before the latest was all okay to me. 09:59:27 <hiro-kobayashi> thanks. Anyway, tetsuro's placement related patches will not be affected by spec changes. So, let's review them. 09:59:48 <masahito> Running out weekly meeting time. 10:00:10 <masahito> Let's move to #openstack-blazar 10:00:27 <hiro-kobayashi> ok 10:00:32 <masahito> thanks all 10:00:38 <tetsuro> thanks! 10:00:39 <masahito> #endmeeting