09:00:30 #startmeeting blazar 09:00:31 Meeting started Tue Jun 26 09:00:30 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:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:34 The meeting name has been set to 'blazar' 09:00:43 hi blazar folks, time to blazar meeting. 09:00:49 #topic RollCall 09:01:36 today's agenda is 09:01:43 1. review meeting 09:01:53 2. releasenote for API changes 09:01:57 3. AOB 09:01:57 hi 09:02:11 hiro-kobayashi: hello 09:02:22 anything else? 09:02:44 Hello! 09:02:58 priteau: hello. 09:03:08 Hello masahito and priteau 09:03:27 Let's get started! 09:03:32 #topic review meeting 09:03:38 hi 09:03:42 bertys: hi 09:03:55 hi bertys 09:04:06 I can see lots of patch series in gerrit board now. 09:04:30 And tetsuro seems to start placement supports. 09:05:07 So I'd like to have one or two review meetings if you all sound it's nice. 09:05:13 before R-3 milestone. 09:05:24 Sounds good! 09:06:14 sorry to be late 09:06:15 As usual, we have the meeting right after this weekly meeting. 09:06:18 This is a good idea. I am just back from a short vacation and haven't looked at reviews for almost a week. 09:07:13 The candidates are 10th July or 17th July. Does the day work for you? 09:07:55 Both of them will work for me. 09:08:39 Either of them works for me. 09:08:52 got it. 09:08:54 Both sounds good to me, too. 09:09:31 tetsuro isn't here now. I'll send the candidates to the ML and then decide. 09:09:59 tetsuro was just here :-) 09:10:02 I see tetsuro is here now 09:10:07 can you here me? :) 09:10:20 ah, 09:10:28 I can see you. 09:10:32 sorry to be late! 09:10:37 np. 09:10:41 Both date work for me! 09:10:51 tetsuro: thank! 09:11:33 okay 09:12:04 10th July is better to me because we have chance to update and fix the comment before r-3 09:12:18 the r-3 milestone is 27th July. 09:12:46 let's have the review meeting on 10th July after the weekly meeting. 09:13:01 OK! 09:13:14 okay for me as well 09:13:19 I'm expecting the meeting is two hours as maximum. 09:14:14 When we don't finish to through patches, let's continue it on 17th 09:14:16 If we have a short weekly meeting on July 10, I assume we can start the review meeting early? 09:14:28 yes, of course. 09:15:09 any comment? 09:16:25 I may not be able to stay for the full two hours 09:16:42 But I should be available for the beginning of the meeting 09:16:57 got it. We're small team and have flexibility for the time :-) 09:17:34 let's move on to next. 09:17:44 #topic Releasenote for API change 09:18:27 I am AFK for a few minutes, sorry 09:18:55 As we agreed in the last meeting, we're fixing response code to align the meeting. 09:18:59 priteau: got it. 09:19:57 IMO, the releasenote could become so big if each fixes have individual releasenotes. 09:20:21 So I push a patch to make the summary of the change. 09:20:32 https://review.openstack.org/#/c/577747/ 09:20:48 tetsuro and priteau: Does it make sense? 09:21:58 masahito: yup, this works for me! 09:21:59 Because tetsuro wrote the releasenote but it makes a big note even though this is just one fix. https://review.openstack.org/#/c/575271 09:22:19 Okay, I'll remove that. 09:22:35 tetsuro: thank you. 09:23:31 And let's wait priteau a few minutes :-) He and his team members are a real operator who read the note. 09:23:35 I am back 09:23:45 welcome back! 09:24:08 Overall it looks OK, I will have some comments on phrasing / grammar that I will post on Gerrit 09:25:02 I like tetsuro's release note though, because it explains *why* we did the change 09:25:12 Nice! Thank you. The note is published as one of official docs. 09:25:23 Maybe we can add a bit more information to your release note, masahito 09:26:23 We can discuss on Gerrit 09:26:42 My first patch is for discussing what info we need to have. Welcome to any comments. 09:27:04 Right. we can discuss on the gerrit board. 09:27:20 I have learned in nova community that we can be verbose in docs, so we don't have to be too worried about long docs... anyway 09:27:33 we can continue discussion on gerrit board 09:28:19 thanks your feedback. 09:28:23 Anyway, I'm +1 for the idea to remove reno from my patch. 09:28:31 #topic AOB 09:28:36 I agree with tetsuro. Release notes are also formatted as bullet lists, so the reader can easily scan them 09:29:35 oops, sorry to interrupt. 09:29:51 No problem, I was too slow to write ;-) 09:29:53 Anything else for the releasenote? 09:30:00 Nope 09:30:20 If nothing, let's start AOB :-) 09:30:41 Does someone have something to share or discuss? 09:31:57 I just want to mention one patch that fixing gate failure, https://review.openstack.org/#/c/577746/. 09:33:04 Thanks masahito. May I fix typos in the commit message? :-) 09:33:05 Flask changed its default internal data structure from 1.0.2 and it breaks the blazar-api. 09:33:14 priteau: sure. 09:33:23 masahito: Thank you for solving the failure! 09:33:29 Hi, This is Parthiban. 09:33:30 Ah, I saw this error just now... Cool. Thank you, masa. 09:34:01 Recently I went through OpenStack Security guidelines and I'm trying to implement few of them. - #auth_timing_attack - I have verified the response time of OpenStack with successful & failed attempts, but I cannot figure out difference in response time to a valid vs a failed authentication attempt. 09:34:03 priteau: I'm happy if you can merge it after fix the message. 09:34:10 Will do! 09:34:20 Has this feature already implemented in Openstack? I'm using OpenStack Queens. Can some one help on this? 09:34:31 If this is not the right forum to seek help, please guide me with this regard. 09:34:49 qwebirc77170: This is a meeting channel. You should be asking on #openstack-dev 09:35:13 Or #openstack 09:35:17 Thanks priteau, for the help 09:37:27 anything else? if nothing, we can finish today's meeting early. 09:37:38 No update from me 09:37:58 nothing 09:38:45 let's finish todays meeting. 09:38:52 thanks all! 09:39:03 thank you and good bye all! 09:39:04 bye. 09:39:09 #endmeeting