09:00:29 <masahito> #startmeeting blazar
09:00:30 <openstack> Meeting started Tue Mar 13 09:00:29 2018 UTC and is due to finish in 60 minutes.  The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:31 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:33 <openstack> The meeting name has been set to 'blazar'
09:00:49 <masahito> #topic RollCall
09:01:02 <priteau> o/
09:01:12 <hiro-kobayashi> o/
09:01:16 <bertys> o/
09:01:25 <masahito> today's agenda is
09:01:43 <masahito> 1. team photo
09:01:49 <masahito> 2. Rocky milestone
09:01:52 <masahito> 3. AOB
09:01:55 <masahito> anything else?
09:02:06 <masahito> priteau, hiro-kobayashi, bertys: hi
09:03:13 <masahito> I hope all had good and safe trip from Dublin to your home.
09:03:15 <priteau> Pending patches for Queens? I think there were some dashboard commits not yet merged in stable/queens
09:03:34 <masahito> got it.
09:03:41 <masahito> #topic team photo
09:04:11 <masahito> It's a fyi.
09:04:36 <masahito> The foundation shared the team photo as you see in openstack-dev ML.
09:04:49 <masahito> https://www.dropbox.com/sh/dtei3ovfi7z74vo/AAB6nLiArw8fYBiO-X_vDGyna?dl=0
09:05:50 <masahito> Blazar team photo is also there
09:05:53 <priteau> Thanks for sharing!
09:06:43 <hiro-kobayashi> It was sunny :-)
09:07:13 <masahito> The wether is completely different among the teams.
09:07:34 <priteau> And there was no snow (yet)
09:07:49 <masahito> s/wether/weather
09:08:36 <masahito> okay, move on to next :-)
09:08:47 <masahito> #topic Rocky milestone
09:09:57 <masahito> I created rocky series in launchpad and assigned some BPs and bugs to each milestone.
09:09:59 <masahito> https://launchpad.net/blazar/rocky
09:10:21 <hiro-kobayashi> thanks!
09:11:23 <masahito> Most of BPs are targeted to r-2 as we need design and implementation phases.
09:12:11 <masahito> But there is not big intent. So feel free to move the milestone if needed.
09:12:37 <masahito> Same for bugs.
09:12:51 <bertys> masahito: thanks, would it be possible to change "expected" date for rocky-1 milestone?
09:13:15 <bertys> from January to April?
09:13:44 <bertys> #link https://releases.openstack.org/rocky/schedule.html
09:13:52 <masahito> Oops.
09:14:11 <masahito> Done
09:14:17 <bertys> thanks
09:14:51 <priteau> Who's Dmitriy Dyachkov?
09:15:48 <priteau> He's the assignee from 4 years ago, we should probably change it ;-)
09:15:50 <masahito> Dmitriy Dyachkov could be a member of previous activities.
09:15:55 <priteau> For this bug: https://bugs.launchpad.net/blazar/+bug/1255106
09:15:56 <openstack> Launchpad bug 1255106 in Blazar "API unittests coverage is unsufficient" [Medium,Confirmed] - Assigned to Dmitriy Dyachkov (ddyachkov)
09:16:28 <masahito> yes. we could take it over.
09:17:19 <hiro-kobayashi> Is https://blueprints.launchpad.net/blazar/+spec/stop-using-customized-filter related to placement API?
09:17:35 <hiro-kobayashi> If so, milestone should be S+?
09:18:00 <hiro-kobayashi> s/milestone/milestone target/
09:18:06 <masahito> The calendar view and resource usage API hasn't been reported yet. So I didn't assign it.
09:18:52 <priteau> masahito: There is already a bp for it: https://blueprints.launchpad.net/blazar/+spec/resource-availability-api
09:19:33 <masahito> hiro-kobayashi: The design phase is planned to Rocky so I put it in r-3 to easily track.
09:20:00 <hiro-kobayashi> Got it.
09:20:58 <masahito> hiro-kobayashi: If it's confusing, it's okay to remove milestone target.
09:21:32 <masahito> priteau: Look like. I forgot adding the target to the BP.
09:21:40 <masahito> priteau: thanks.
09:22:15 <masahito> For the calender view, I imagine two BPs are required.
09:23:16 <masahito> 1. reservation detail API and 2. dashboard view depends-on #1
09:23:24 <priteau> You mean a new one for the calendar support in dashboard?
09:25:06 <priteau> I can create one for calendar view
09:25:11 <masahito> yes. I think separated BPs are more easy to write specs and finish tasks.
09:25:31 <hiro-kobayashi> +1
09:25:53 <masahito> priteau: thank you.
09:26:55 <masahito> other comments?
09:27:09 <priteau> Created at https://blueprints.launchpad.net/blazar/+spec/calendar-view
09:29:18 <masahito> priteau: thank you.
09:31:18 <masahito> priteau: It's okay to separate the description of query availability API from https://blueprints.launchpad.net/blazar/+spec/resource-availability-api ?
09:31:51 <priteau> Right, we decided they will be two separate APIs?
09:31:51 <masahito> Just for tracking.
09:32:25 <priteau> Fine with me.
09:32:29 <masahito> yes. thanks. They will be two APIs.
09:32:37 <masahito> then, move on to next.
09:33:03 <masahito> #topic Pending patches
09:34:23 <masahito> priteau: Which patches for Queens are in review board now?  I can't find it.
09:34:57 <priteau> It's not proposed for queens yet, but I thought hiro-kobayashi said he wanted to include https://review.openstack.org/541564 in the release
09:35:51 <masahito> oh, I see.
09:35:51 <hiro-kobayashi> priteau: It does not have to be merged to stable/queens
09:36:05 <priteau> OK, sorry for misunderstanding
09:37:09 <hiro-kobayashi> I'm sorry perhaps I changed my mind ;-)
09:37:18 <priteau> Then I think we could be good for Queens
09:37:56 <masahito> yes, it's fine to backport it.
09:41:34 <hiro-kobayashi> Now that there is no task for Queens :-)
09:41:47 <masahito> okay, if hiro-kobayashi want to backport it again, then let's do that ;-)
09:41:58 <hiro-kobayashi> OK
09:42:01 <priteau> I will let hiro-kobayashi decide.
09:42:16 <hiro-kobayashi> Now I think it's not needed.
09:43:05 <hiro-kobayashi> for Queens
09:44:14 <masahito> #topic AOB
09:44:32 <masahito> anything else to share/discuss/etc?
09:45:04 <hiro-kobayashi> Nothing from my side.
09:45:21 <masahito> we discussed a lot in the last PTG. There could be less topics.
09:46:24 <bertys> only one topic related to Heat. Any opinion whether or not to have blazar host update by heat?
09:46:25 <priteau> I have started developing OpenStackClient support, will work on it as time allows
09:46:35 <bertys> #link https://review.openstack.org/#/c/534576/
09:48:46 <hiro-kobayashi> bertys: I think it doesn't have to support updates for now because the reservation's object model does not match with Heat.
09:49:04 <masahito> I'm okay for heat to have host update in first patch.
09:49:33 <hiro-kobayashi> Oh, I'm sorry my opinion was about Lease...
09:50:01 <hiro-kobayashi> Agree with masahito
09:50:10 <masahito> hiro-kobayashi: if the patch update is supported, it fits the model?
09:50:19 <masahito> ah, race condition...
09:50:52 <priteau> Even if there was API support already, how would a user express removing an extra capability from a host in a Heat template?
09:51:46 <masahito> Heat uses blazarclient to call Blazar API instead of direct API call. So the usage of client wouldn't be changed whether patch is supported or not.
09:52:18 <priteau> masahito: But client will likely change
09:54:13 <masahito> priteau: but the heat template isn't change
09:55:26 <priteau> I guess the question is, do we want Heat to provide host update feature with partial support (no removing of extra capability), or not provide it at all until we have full support.
09:55:34 <masahito> ah, does anyone know the grammar of heat update for host?
09:56:56 <priteau> I believe that Heat may be keeping a copy of the host declaration with its original extra capabilities. When a user updates the template and removes a capability from it, Heat detects it and does an update with the new values.
09:59:54 <masahito> Heat calls host update API with diff of original extra capabilities and new one?
10:01:23 <priteau> That's my understanding
10:01:59 <masahito> If so, current implementation doesn't seem to allow deleting update. "delete" means '' padding.
10:03:36 <masahito> original is {'k1': 'v1', 'k2': 'v2'}. new is {'
10:03:53 <masahito> new is {'k1': 'v1'}.
10:04:16 <priteau> Maybe we should prioritize support for removing extra capa so that the Heat patch can fully support the feature.
10:05:22 <masahito> in that case the handle_update calls host update with {'k1': 'v1'}. It's not user's intent.
10:05:43 <masahito> priteau: yes, right.
10:06:41 <masahito> I'll ask kaz whether it's allowed to add host update later.
10:06:42 <priteau> We could always ask them to merge lease support first
10:06:53 <bertys> thanks... Let's end the meeting and many thanks for your work during Queens release
10:07:45 <masahito> Host update should not be support for first implementation.
10:08:17 <masahito> oh, running out of time. I didn't notice. thanks, bertys.
10:08:44 <masahito> then, see you.
10:08:45 <priteau> Thanks everyone
10:08:48 <masahito> bye
10:08:48 <priteau> Bye!
10:08:56 <masahito> #endmeeting