09:01:40 <masahito> #startmeeting blazar
09:01:41 <openstack> Meeting started Tue Dec 12 09:01:40 2017 UTC and is due to finish in 60 minutes.  The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:01:42 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:01:44 <openstack> The meeting name has been set to 'blazar'
09:02:23 <masahito> #topic RollCall
09:02:36 <hiro-kobayashi> o/
09:03:12 <priteau> o/
09:03:18 <masahito> today's agenda is
09:03:27 <masahito> 1. PTG schedule
09:03:34 <masahito> 2. Q-2 release
09:03:36 <masahito> 3. AOB
09:03:41 <masahito> 4. review meeting
09:03:49 <masahito> anything else?
09:04:01 <masahito> hiro-kobayashi, priteau: o/
09:05:07 <masahito> #topic PTG schedule
09:05:43 <masahito> The foundation asked me how many days Blazar team will have the meeting in the Dublin PTG.
09:06:37 <masahito> From my experience, I thought two days works for us.
09:06:44 <hiro-kobayashi> +1
09:07:07 <priteau> Is that two full days?
09:07:38 <masahito> I have already replied them with the plan because of short response due date.
09:07:56 <masahito> My plan was two full days.
09:08:21 <masahito> Of course, we have less topics. we can finish early.
09:09:11 <priteau> Sounds good
09:11:32 <masahito> According to ptg web site, Wednesday to Friday are for single project meeting. So Blazar's meeting could be Wednesday and Thursday.
09:11:36 <masahito> https://www.openstack.org/ptg/
09:12:21 <masahito> I'll share the specific schedule once I
09:12:37 <masahito> once I've received the details.
09:12:48 <hiro-kobayashi> thanks
09:12:48 <masahito> any comments?
09:14:21 <masahito> ok, let's move on to next.
09:14:27 <masahito> #topic Q-2 release
09:15:05 <masahito> Last week was Q-2 release milestone but not yet released q-2 of blazar.
09:15:25 <masahito> The release patch is still in review board now. https://review.openstack.org/#/c/526616/
09:16:06 <masahito> I hope this will be merged soon after zuul job updates.
09:16:16 <masahito> any comments?
09:16:55 <bertys__> thanks priteau and masahito
09:18:55 <priteau> masahito: Should blazar-nova be of type library or service?
09:19:58 <masahito> priteau: I thought it's a library b/c blazar-nova doesn't have its API.
09:20:42 <masahito> Does zuul use a different release job for a library project?
09:21:01 <priteau> You must be right
09:21:02 <priteau> https://releases.openstack.org/reference/deliverable_types.html#library
09:21:55 <priteau> Libraries are often pushed to PyPI, but I believe my patch configures blazar-nova to just be a tarball release
09:23:16 <masahito> meaning 'publish-to-pypi' template is good for the job?
09:23:44 <priteau> I used publish-to-pypi only for python-blazarclient
09:24:10 <priteau> Should we make blazar-nova installable via PyPI?
09:25:19 <hiro-kobayashi> I think only python-blazarclient is enough.
09:25:31 <priteau> Operators will install nova from tarballs anyway
09:25:43 <priteau> or from packages, etc.
09:26:58 <masahito> right. blazar-nova don't need to support PyPI.
09:27:57 <masahito> But I don't see library can't use release-openstack-server job in the above link.
09:28:26 <priteau> masahito: I didn't say it couldn't. I think our patches are good.
09:28:29 <masahito> It's not matter to keep current both patch sets, isn't it?
09:28:48 <masahito> priteau: oh, right :-)
09:29:41 <masahito> other comments?
09:30:45 <masahito> #topic AOB
09:31:24 <masahito> Before moving on to review meeting, we should have AOB topic.
09:31:36 <masahito> Does someone have something to share/discuss?
09:32:16 <hiro-kobayashi> Nothing from me
09:32:36 <hiro-kobayashi> Oh, I have one topic.
09:33:33 <hiro-kobayashi> I found instance reservation doesn't work with Cells v2 deployment because anti-affinity check does not work
09:33:53 <hiro-kobayashi> https://bugs.launchpad.net/blazar/+bug/1737676
09:33:54 <openstack> Launchpad bug 1737676 in Blazar "Enable anti-affinity check for instance reservation" [Undecided,New]
09:35:25 <hiro-kobayashi> I've been investigating and thinking of a solution. But no good solution yet :-(
09:36:04 <hiro-kobayashi> I think this bug should be high-prioritized.
09:36:33 <masahito> The doc says upcalls don't happen when the cloud is deployed as MULTI cell.
09:36:48 <hiro-kobayashi> right
09:37:18 <masahito> Does the bug happen when we deploy single cell?
09:37:57 <hiro-kobayashi> Perhaps it's specific to my test environment. So I've been investigating root cause.
09:38:21 <hiro-kobayashi> My test env is single cell.
09:38:59 <masahito> As you said, it's an high priority bug. I'll also check it.
09:39:15 <hiro-kobayashi> thanks
09:39:47 <masahito> anything else?
09:40:35 <hiro-kobayashi> additional info: my env has single cell but uses super conductor
09:41:58 <masahito> hiro-kobayashi: thanks the info
09:42:43 <masahito> okay, we can start review meeting from now.
09:43:20 <priteau> Just one thing before moving on
09:43:27 <priteau> The other day I was saying that we were running a new version of Blazar on Chameleon and seeing issues with some leases failing to start.
09:43:43 <priteau> I believe this may have been caused by a badly merged patch in our fork.
09:44:08 <priteau> I fixed the issue and will be checking if the problem still happens.
09:45:00 <masahito> priteau: Nice!
09:45:18 <priteau> Otherwise Blazar is working well.
09:45:40 <masahito> The issue always happens at start time?
09:46:09 <masahito> s/happens/happend/
09:46:48 <priteau> Always at start time, but only for some leases. It was because a patch that fixes a race condition had been partially reverted during the merge.
09:48:03 <masahito> got it.
09:48:52 <masahito> If you find the root cause is in master, please report it.
09:49:39 <priteau> I believe it's was only in our fork.
09:51:13 <masahito> Okay
09:51:58 <masahito> For the review meeting, I'd like to move the openstack-blazar channel because of limited time of this channel.
09:52:35 <hiro-kobayashi> okay
09:53:10 <priteau> No problem
09:53:17 <bertys> okay, 5 minutes break?
09:53:32 <masahito> okay.
09:54:07 <masahito> let's start in 5 mins.
09:55:03 <masahito> thanks for the weekly meerting. I tell the end of the meeting to the meeting bot.
09:55:11 <masahito> #endmeeting