09:00:00 #startmeeting blazar 09:00:01 Meeting started Tue Aug 20 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:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:05 The meeting name has been set to 'blazar' 09:00:08 #topic Roll call 09:00:41 o/ 09:00:44 o/ 09:00:57 Hi masahito and tetsuro! 09:02:11 Do you know if Bertrand is joining? 09:02:58 I have no idea 09:04:28 He may be on holiday, so let's start 09:04:37 Agenda for today: 09:04:40 - Project update @ Shanghai Summit 09:04:44 - Activities @ Shanghai PTG 09:04:51 - Blazar client release 09:04:55 - Change of blazar-dashboard release model 09:04:58 - Code review priorities 09:05:01 - AOB 09:05:24 #topic Project update @ Shanghai Summit 09:06:15 For Shanghai, 40 slots are available for project updates. 09:06:48 Slots will be reserved on a first come, first served basis. 09:07:10 This was notified a week ago so we should reply as soon as possible. 09:08:29 Unfortunately my (non-Blazar) talk was not accepted for the summit. 09:09:59 Given that many placement / nova people are skipping this summit, I'm inclined to skip this one as well, as it's a lot of time spent on travel and logistics. 09:10:40 tetsuro: Are you interested in giving a Blazar project update? You already gave one at last summit, so I understand if you don't feel like doing it again. 09:10:51 I will be the summit. 09:11:09 I don't have any talk accepted, but I'm coming to Shanghai and it is already approved, and I can help to have the session. 09:11:10 s/be the summit/be in the summit/ 09:11:28 the session <- I meant the project update session 09:11:41 masahito: That's good news. Would you be happy to present the project update as well? 09:12:39 We have a choice of 15 min or 40 min session. I think 15 min makes sense for us. 09:12:40 I'm okay to present it if we need to have project update session. 09:13:14 15min makes sense to me. 09:13:47 Especially since we don't yet have as many new features as previous release cycles. 09:14:29 Agree 09:15:43 I'll include Bertrand as well, we can remove him later if he doesn't want / can't participate 09:16:28 I've just submitted the request now 09:16:36 Thanks! 09:16:53 We must also confirm one registration to the summit by Sunday September 29th at 7:00 UTC 09:17:11 If either of you is already registered, I can send the confirmation 09:17:49 I am already registered. 09:18:01 I haven't registered yet because of company reason. 09:18:23 tetsuro: Thanks, I will confirm 09:18:40 I'll check it tomorrow and will change email address in OpenStack ID 09:19:39 Thanks. 09:19:48 #topic Activities @ Shanghai PTG 09:20:32 We've requested a Project Onboarding session at the PTG 09:21:13 We'll have to decide how long would be the session and prepare materials. 09:21:42 I don't think I've ever been to a project onboarding session, but I saw slides online that we can use for inspiration. 09:23:30 There is also the option of holding technical discussions in person at the PTG, if you are interested. We'll want to have a virtual PTG anyway, probably before the summit. 09:25:48 Let me know if you're interested in having some technical discussions. There will be less dedicated space at the PTG, so those discussions would likely be in the shared space and can be organised at the last minute. 09:26:42 I think number of Blazar team member is not big. I'm okay not to have dedicated space. 09:27:25 Shared space is okay to me. 09:28:08 Depends who joins the discussion. Last year in Denver we had quite a big attendance when we discussed with the placement people. But in Shanghai many will not be there. 09:29:12 Even if NTT Data people are joining, it will only be 5 or 6 people in total. 09:30:06 We'll talk again about Project Onboarding in the coming weeks. Let's carry on with the agenda 09:30:13 #topic Blazar client release 09:30:33 We were prompted to release python-blazarclient: https://review.opendev.org/#/c/675314/ 09:31:17 I think there are some infra requirements meaning we need to release at least once in a cycle 09:31:35 The good thing is we have a new feature to include: floating IP reservation. 09:31:49 I just want to include a little fix: https://review.opendev.org/#/c/676217/ 09:32:06 Thanks both for the review, I will create a bug in LP 09:32:16 Thanks 09:32:29 I'm ready to +W if that is reported. 09:33:23 Afterwards I will update the release patch with the latest commit 09:34:06 #topic Change of blazar-dashboard release model 09:34:25 This one needs some discussion 09:34:28 #link https://review.opendev.org/#/c/675471/ 09:34:56 It was proposed to change blazar-dashboard to the cycle-with-rc model 09:36:06 This has been proposed to other projects that haven't released yet in the Train cycle. Some have decided to move to cycle-with-rc, while other requested to stay on cycle-with-intermediary 09:37:06 I like the option of being able to release blazar-dashboard when we want, like with the python client 09:37:18 I don't have an objection to move the release model. 09:38:18 But we don't have much activity on blazar-dashboard at the moment 09:38:33 So it will be difficult justifying stayin on cycle-with-intermediary 09:40:18 If we move to cycle-with-rc, we will have to create an rc1 before Sep 23 - Sep 27 09:40:29 then a final release by Oct 14 - Oct 18 09:41:15 tetsuro: Any thoughts on this topic? 09:42:10 Why has it been cycle-with-intermediary model? 09:42:51 I think it was the model used by most Horizon dashboards at the time 09:43:42 Oh I see, if that is only the reason I don't think there are any blockers to move to cycle-with-rc model? 09:45:29 Right, there is no blocker. We lose some flexibility: for example if we had developers active on blazar-dashboard now, we could release a new version with floating IP support and, assuming that the Horizon API interface doesn't change, it could be deployed on OpenStack Stein . 09:45:49 I suppose we can move back to another model in the future if needed. 09:46:03 Wait, is the python-blazarclient cycle-with-rc or cycle-with-intermediary 09:46:30 python-blazarclient is cycle-with-intermediary 09:46:37 Ah, I see. 09:46:38 Which is why we can release now 09:47:00 But we have people active on python-blazarclient, not so much on the dashboard. 09:48:01 Got it. Okay, then yeah, ideally we will want to come back to the intermediary model. 09:48:29 I'll ask if we can move back easily 09:48:39 I suppose we have until rc1 to decide. 09:49:58 I asked Kendall on Gerrit 09:49:59 In this release we won't have many releases on dashboard. 09:50:03 Thanks. 09:50:16 Let's revisit next week depending on her answer. 09:50:22 Just 10 minutes left 09:50:27 #topic Code review priorities 09:50:46 We have some new patches to review 09:51:07 Jake from Chameleon has submitted a spec for network reservation: https://review.opendev.org/#/c/674089/ 09:51:14 I've already suggested some changes 09:52:05 I've got a placement bugfix that we really need to include in this release: https://review.opendev.org/#/c/671312/ 09:55:27 Ack. I'll have a look shortly 09:55:39 Thank you. It's a very easy one 09:56:21 There are also more patch from Jake: https://review.opendev.org/#/c/672994/ and https://review.opendev.org/#/c/672763/ 09:56:30 And of course the patch series from Asmita 09:56:35 #topic AOB 09:56:43 Anything else to mention before we end? 09:58:17 nothing from my side 09:58:46 nothing 09:59:30 Thanks a lot! 09:59:39 for joining 09:59:50 Talk to you next week! 09:59:53 #endmeeting