09:00:16 #startmeeting blazar 09:00:16 Meeting started Tue Jul 17 09:00:16 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:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:20 The meeting name has been set to 'blazar' 09:00:30 Hi Blazar folks! 09:00:38 #topic RollCall 09:00:43 o/ 09:00:49 o/ 09:01:00 o/ 09:01:12 priteau, tetsuro, bertys: hello 09:01:17 Today's agenda is 09:01:17 Hi everyone 09:01:30 1. Non-client libraries release 09:01:39 2. Project Update in the Berlin summit 09:01:44 3. the gate failure 09:01:47 4. AOB 09:01:58 and following review meeting. 09:02:03 anything else? 09:02:10 hi 09:02:24 hiro-kobayashi: hi 09:04:01 #topic Non-client release 09:04:46 As we talked in the last meeting, I pushed the release patch for the blazar-nova 2.0.0 09:04:56 https://review.openstack.org/#/c/583159/ 09:05:37 Great, thanks masahito 09:06:00 The version number is aligned to the Blazar server's version. 09:06:04 any comment? 09:08:02 #topic Project Update in the Berlin summit 09:08:23 This item is also fyi. 09:09:29 I mailed TC members wether we can have the session or not. But I've not received any response yet. 09:11:31 Thank you for checking it! 09:11:44 I hope they'll arrange the session series in the summit and we'll be included. 09:12:12 CFP is closing on July 18th at 6:59 am UTC 09:12:46 If we don't get any answer from TC by that time, should we submit a talk? 09:13:20 I am sure that if there is actually a project update session, they will make sure we don't have a duplicate talk 09:14:46 Yes, if possible I want to submit a talk. 09:15:03 masahito: with the timezone difference you can still submit tomorrow :-) 09:15:17 One issue I'm hitting is I'm involved in 3 talks already. 09:17:46 Is that the maximum number of talks one can submit? 09:18:08 Two of them are Blazar related talks. So I could do some update in those. 09:18:41 priteau: yes. One person only can submit 3 talks regardless of main speaker or co-speaker. 09:20:18 Who is attending Berlin by the way? 09:20:23 I am not sure if I will be there yet 09:20:41 I'll be there. 09:21:17 I will not be there 09:21:43 I'll be there 09:22:01 If some of us can be there, it's okay to submit the update session by your name. 09:22:08 Same as priteau, not sure if I will be there 09:22:27 And if needed, I'm also okay to join the session later. 09:23:55 So who could submit a project update talk if needed? tetsuro? 09:24:12 Anyway. I try to ping them again, and if needed I'll submit a update session. 09:24:34 but you can't masa, can you? 09:25:07 One of my proposal is a talk with tetsuro. So I hope I can exit from tetsuro's talk :-) 09:25:25 Heh 09:25:47 I think that's more reasonable way to go. 09:26:18 than I submit update session 09:26:34 Sounds good 09:26:52 okay, the problem is solved :-) 09:27:04 #topic the gate failure 09:27:45 I see the gate failure because of pylint update and the fix of the issue. https://review.openstack.org/#/c/583080/ 09:28:19 Yes, please review it and merge it asap 09:28:23 hiro-kobayashi: Thanks for digging it. 09:29:32 I saw major projects like Cinder take the same approach: https://github.com/openstack/cinder/blob/master/tox.ini#L87 09:30:11 My one question is the required version of pytlint doesn't appear in requirements.txt, do it? 09:30:29 hiro-kobayashi: Is pylint moved out of requirements.txt because it is in the openstack/requirements blacklist? 09:31:40 Yes, it is not listed in the global-requirements. 09:32:18 The latest version 2.0.0 which was released yesterday does not support python2. That's why it broke some tests. 09:33:08 Some projects have it in their test-requirements.txt though. We could ask what's the recommended approach. 09:33:47 I noticed pylint is removed from test-requirements.txt. tox.ini specifies requirements.txt not test-requirements.txt 09:33:52 Doesn't those project hit gate failure? 09:34:17 They use pylint==1.4.5 09:34:36 or pylint==1.7.1 09:35:12 hiro-kobayashi: If we remove pylint from test-requirements.txt, shouldn't we also remove it from lower-constraints.txt? 09:35:51 I thinks lower-constraints contains more packages than listed in the requirements file. 09:36:00 So, I think we can keep it. 09:36:50 It's because it lists all dependencies, and their dependencies. 09:36:58 IIRC, lower-constraints.txt is maintained by requirements repo. 09:37:51 um, I don't know the maintenance policy of lower-constraints :-( 09:39:06 ``Each project team may also optionally maintain a list of “lower bounds” constraints for the dependencies used to test the project in a lower-constraints.txt file`` by https://docs.openstack.org/project-team-guide/dependency-management.html#solution 09:39:08 My thoughts for the upcomming milestone release, 1. remove pylint from test-requirements.txt (It could fix gate failure except openstack-tox-pylint), 2. find a right versioning of pylint. 09:39:35 How do you think? 09:40:16 hiro-kobayashi: yes, I think we have to maintain the file 09:40:42 There is a little script in openstack/requirements to automatically generate it too 09:41:12 masahito: isn't that what hiro-kobayashi's patch does? 09:41:35 masahito: I think we should merge my patch asap. Then, upload a new patch if it does not meet with the OpenStack standard. 09:42:09 I think we should move other patches forward. 09:42:27 My concern is specifying package version in tox.ini. 09:43:26 From my experience, this type of "special case" usually causes annoying issue later. 09:44:02 hiro-kobayashi: I agree we should move forward. 09:45:43 I added more details to the commit message 09:45:53 thanks! 09:46:33 okay, let's merge this patch and check openstack's standard. 09:46:34 Gave a +2. We can fix lower-constraints and other issues later. 09:47:00 OK 09:47:42 Another idea is putting non-voting tag to py27 gate job :-) 09:48:04 Anyway, let's move on to next. 09:48:22 #topic AOB 09:48:36 Does someone have something to share or discuss? 09:48:58 Not from me 09:49:28 fyi: Blazar is listed on project-navigator now. https://www.openstack.org/software/project-navigator#orchestration 09:49:52 great! 09:50:18 nice. 09:50:18 I saw that recently, great news! 09:50:28 The mouse looks bigger than other mascots... :-) 09:50:49 fyi, Wiki page for upcoming PTG @ https://wiki.openstack.org/wiki/PTG/Stein/Etherpads, we may want to add Blazar too... 09:52:36 Done 09:52:44 thanks 09:53:30 anything else? 09:53:36 I have 09:53:55 As you all know, I will change my job next month. 09:54:27 The next weekly meeting is the last time for me to join as current position. 09:55:06 We will miss you hiro-kobayashi! 09:55:07 So, I’m sorry but I expect my contribution will considerably decrease. 09:56:40 I will try to join as an individual contributor ;-) 09:57:27 I'll miss you, too. I'm really appreciate your productive contributions and happy working with you. 09:58:49 It was great to promote this project with you all! Thank you so much! 09:59:29 I hope your next job is well and am looking forward to seeing you as an individual :-) 10:00:02 thanks! 10:00:28 thanks again hiro! Time to move to blazar irc? 10:01:12 ah, yes. running out of time. 10:01:32 moving to #openstack-blazar then let's start review meeting. 10:01:41 #endmeeting