09:00:17 <priteau> #startmeeting blazar
09:00:18 <openstack> Meeting started Tue Oct  2 09:00:17 2018 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:22 <openstack> The meeting name has been set to 'blazar'
09:00:38 <priteau> #topic Roll call
09:00:47 <masahito> o/
09:00:56 <tetsuro> o/
09:00:56 <bertys> o/
09:01:10 <priteau> Hello everyone
09:01:31 <priteau> I don't have a big agenda today
09:01:34 <priteau> 1. Project Update @ Berlin Summit
09:01:38 <priteau> 2. OpenStack-wide Goals
09:01:41 <priteau> 3. AOB
09:01:58 <priteau> #topic Project Update @ Berlin Summit
09:02:34 <priteau> I have registered for the summit and sent the proof to confirm our project update slot
09:03:19 <priteau> We are on the official schedule now
09:03:39 <priteau> #link https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22775/blazar-project-update
09:03:46 <priteau> Tuesday, November 13, 11:25am-11:45am
09:03:53 <bertys> priteau: Thanks, I have registered as well.
09:04:04 <masahito> Thanks
09:04:12 <priteau> Does this time work for you masahito and bertys?
09:04:29 <priteau> This is at the beginning of the summit
09:04:37 <masahito> No problem.
09:04:49 <priteau> Almost right after the keynotes
09:04:51 <bertys> works for me as well
09:05:20 <priteau> bertys: Could you please update your speaker profile which shows up on the page?
09:05:58 <priteau> You can put a picture and a little bio
09:06:11 <priteau> It's manage within your OpenStack profile
09:06:18 <priteau> *managed*
09:06:28 <bertys> priteau: ok, will do, no problem
09:06:54 <priteau> Unless you want to remain incognito ;-)
09:07:54 <priteau> I am going to ask whether there is a specific slide deck template to follow, and if not use the previous one
09:08:11 <priteau> Then I will circulate the slides so we can start contributing
09:09:13 <priteau> I haven't yet looked closely at the summit schedule, anything interesting?
09:09:42 <masahito> me neither.
09:11:22 <priteau> We should see a draft forum schedule next week (October 10)
09:11:43 <priteau> Moving on to the next topic
09:11:49 <priteau> #topic OpenStack-wide Goals
09:12:39 <priteau> On the ML there is already a discussion of goals for the T release
09:13:04 <priteau> #link http://lists.openstack.org/pipermail/openstack-dev/2018-September/135097.html
09:13:28 <priteau> Interestingly the discussion has focused around openstackclient support
09:14:08 <priteau> We are planning to make progress on our own OSC plugin this cycle so it should give us a head start for the T cycle!
09:14:32 <masahito> Nice
09:15:22 <priteau> And for Stein, we need to start working on our upgrade checker
09:15:26 <priteau> #link https://governance.openstack.org/tc/goals/stein/upgrade-checkers.html
09:15:39 <masahito> We have less CLI commands. It's easy to migrate to OSC.
09:16:36 <priteau> masahito: It's not hard work but we still need to take the time to do it :-)
09:17:07 <bertys> priteau: I guess you already saw the feedback from Matt @ https://storyboard.openstack.org/#!/story/2003657, right ?
09:17:50 <priteau> bertys: I had not, thanks for letting me know.
09:18:53 <priteau> I see that there is now a oslo.upgradecheck library
09:19:56 <bertys> right, has been accepted https://github.com/openstack/oslo.upgradecheck & https://review.openstack.org/#/c/602483/
09:20:07 <priteau> Seems like the agreement is to have a noop checker if there is nothing to watch out for upgrade
09:20:52 <priteau> That's from the Week R-29 Update
09:21:19 <priteau> #link https://review.openstack.org/#/c/603465/
09:21:26 <priteau> Monasca's noop upgrade checker
09:21:36 <masahito> priteau: do you have a list of issues you hit while you upgrade the Chameleon Cloud?
09:22:15 <masahito> If there is, backporting from the list is nice.
09:22:21 <priteau> masahito: Most issues were linked to all our local changes, including DB schema changes. I don't recall if there was an issue with upstream code.
09:22:28 <priteau> But I will check.
09:22:56 <masahito> Of course, noop checker is nice, too. because Blazar is operator friendly project :-)
09:24:13 <priteau> It may be required for all projects to have a checker, even if noop, by the end of the cycle
09:25:36 <priteau> If I can find some time during the week I can try to push an initial patch
09:26:20 <priteau> Anything else to discuss on this topic?
09:26:38 <masahito> nothing from my side
09:27:18 <priteau> #topic AOB
09:27:41 <priteau> I see there's been some discussion on the approach to use for placement client in https://review.openstack.org/#/c/584625/
09:28:18 <masahito> priteau: Thanks for putting it on the table
09:28:32 <priteau> For what it's worth, my opinion is that we should move forward with tetsuro's code. We can always change it to use a common library if one is created
09:29:12 <tetsuro> Agreed.
09:29:45 <masahito> +1
09:30:01 <priteau> bertys: ?
09:31:44 <bertys> priteau: My original intention was to review tetsuro's patches once https://review.openstack.org/#/c/527728/ is merged
09:32:50 <priteau> But do you agree with the approach of writing our own client code for now, so we can make rapid progress?
09:34:25 <priteau> Creating a common library that can be used by multiple projects is going to require time
09:34:26 <bertys> I do not want to block making progress on blazar side so I will provide some feedback this week
09:35:10 <priteau> Thanks
09:35:12 <tetsuro> bertys: Thanks
09:36:02 <priteau> Any other AOB topics?
09:36:09 <masahito> I have few updates.
09:36:56 <masahito> 1. pushed scenario tests for the instance reservations. The scenario comes basically from host reservation's one.
09:37:03 <masahito> https://review.openstack.org/#/q/topic:bug/1714438+(status:open+OR+status:merged)
09:37:31 <masahito> 2. Updated patches for resource-availability-api
09:37:48 <masahito> That's from my side.
09:38:23 <priteau> Thank you masahito. I started to review the instance reservation patches earlier this morning :-)
09:39:10 <masahito> thanks
09:39:49 <tetsuro> Ah, great work on instance scenario tests, thank you so much.
09:40:32 <priteau> tetsuro: Anything new on your side?
09:40:35 <tetsuro> Since I was a bit worried about moving on Placement related changes without instance scenario tests
09:41:29 <tetsuro> Not really new from me this week, sorry.
09:42:07 <masahito> tetsuro: I'm planning to add more scenario once we've added a new tag to the tempest plugin for stable/queens.
09:42:23 <priteau> My AOB is that Chameleon needs network resource reservation, so I am going to work on prototyping an approach
09:43:53 <masahito> priteau: I'm testing our ideas of floating IP reservation in the PTG in my local to find out pros/cons.
09:44:21 <masahito> priteau: Which are you working on floatingIP or VLAN?
09:44:28 <priteau> That's great. I am going to focus more on the VLAN side of things.
09:45:25 <masahito> Great. We can work for it in parallel :-)
09:46:05 <priteau> Please keep me updated as you make progress
09:46:41 <masahito> sure
09:47:27 <priteau> Anything else for AOB? If not we can end the meeting early and go back to work!
09:49:16 <masahito> ah, just fyi
09:49:36 <masahito> I noticed tetsuro became officially placement-core.
09:49:44 <masahito> congrats!!
09:50:09 <tetsuro> Yes, that happened last Thursday. Thanks.
09:50:15 <priteau> Congratulations tetsuro!
09:50:42 <bertys> tetsuro: congrats and keep up the good work!
09:51:24 <tetsuro> Yup, thanks. Never let you down.
09:53:00 <priteau> I don't hear anything else. Let's end early.
09:53:07 <priteau> Have a good week everyone, thanks for joining.
09:53:13 <priteau> #endmeeting