09:00:00 <priteau> #startmeeting blazar
09:00:01 <openstack> Meeting started Tue Jan 22 09:00:00 2019 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:05 <openstack> The meeting name has been set to 'blazar'
09:00:16 <priteau> #topic Roll call
09:00:43 <masahito> o/
09:01:31 <priteau> Hi masahito
09:02:08 <tetsuro> o/
09:02:21 <priteau> Hi tetsuro
09:03:03 <priteau> Agenda for today: stein-3 milestone and AOB
09:03:09 <priteau> #topicstein-3 milestone
09:03:11 <priteau> #topic stein-3 milestone
09:04:35 <priteau> We have several patch series in progress
09:05:25 <priteau> I have tried to fix the Tempest API tests for resource allocation: https://review.openstack.org/#/c/586859/
09:05:42 <priteau> There are still errors that need to be investigated
09:06:20 <priteau> While browsing the logs, I noticed some errors related to placement
09:06:33 <priteau> e.g. http://logs.openstack.org/59/586859/4/check/blazar-devstack-dsvm/e884936/logs/screen-blazar-m.txt.gz#_Jan_15_07_41_09_087968
09:06:57 <priteau> tetsuro: Do you think you could take a look and check why we're seeing these errors?
09:07:31 <tetsuro> priteau: got it
09:08:05 <priteau> There was also a placement-related bug open: https://bugs.launchpad.net/blazar/+bug/1812642
09:08:06 <openstack> Launchpad bug 1812642 in Blazar "Host creation failed with the error "Remote error: ResourceProviderCreationFailed Failed to create resource provider blazar_<hostname>" [Undecided,New]
09:08:52 <tetsuro> Okay. Looks like I should see that.
09:09:48 <masahito> priteau: thanks for updating the patch.
09:09:50 <priteau> We still have a few weeks to squash bugs but we need stable code near the release
09:12:19 <priteau> The new patch set from tetsuro also needs reviews: https://review.openstack.org/#/q/status:open+project:openstack/blazar+branch:master+topic:bp/no-affinity-instance-reservation
09:14:05 <masahito> I reviewed few patches in the set.
09:15:09 <priteau> Thanks masahito
09:15:23 <priteau> tetsuro: I just added you to the blazar-core and blazar-release groups :-)
09:16:09 <masahito> One question for all is should blazar accept affinity=True/None before merging the patch series?
09:16:20 <masahito> Welcome to the team :-)
09:16:24 <tetsuro> priteau: Ah, thanks. I work to merge good things.
09:16:33 <tetsuro> masa: thanks
09:17:26 <priteau> masahito: I don't understand your question
09:18:54 <masahito> The first patches removes the constraints for affinity option. But some patches on the first one have some changes for supporting affinity=True/None.
09:19:32 <tetsuro> I think I understanc your question.
09:19:58 <masahito> My question is should the constraints be removed at end of the patch series?
09:20:40 <tetsuro> I think you want me to move the constraints check and DB upgrade part from the bottom of the series to top of the series.
09:21:01 <tetsuro> which sounds fair to me.
09:21:12 <masahito> right.
09:21:22 <tetsuro> Ack, will do.
09:21:42 <priteau> Sounds good. You can also rebase on top of master while you're working on it.
09:22:15 <tetsuro> roger, captain :)
09:23:49 <priteau> masahito: Is this patch dependent on soft delete? https://review.openstack.org/#/c/585698/
09:24:09 <masahito> yes
09:24:42 <priteau> OK, I need to revisit my soft delete patch
09:25:40 <masahito> We can merge rest of the patch set to support allocation API and revisit it after blazar support soft-delete.
09:25:55 <priteau> Sounds good to me
09:26:28 <priteau> We need another +2 for bp/resource-allocation-api, from either Bertrand of Tetsuro
09:26:49 <tetsuro> Will revisit it tomorrow if possiblw.
09:27:51 <priteau> And also working API tests would be good :)
09:29:23 <priteau> Anything else to discuss for stein-3 patches?
09:30:45 <tetsuro> nope
09:30:50 <masahito> nothing
09:31:05 <priteau> #topic AOB
09:31:37 <priteau> Anything else to share?
09:33:22 <tetsuro> nope
09:33:26 <masahito> nope
09:34:09 <priteau> Nothing special from me either, so we can finish early this week. More time to work on patches :-)
09:34:47 <priteau> Have a good week everyone, talk to you next Tuesday!
09:35:18 <masahito> Have a good week, too!
09:35:27 <masahito> bye.
09:35:50 <priteau> #endmeeting