09:00:59 #startmeeting blazar 09:01:00 Meeting started Tue Nov 28 09:00:59 2017 UTC and is due to finish in 60 minutes. The chair is hiro-kobayashi. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:01:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:01:03 The meeting name has been set to 'blazar' 09:01:24 #topic RollCall 09:01:30 o/ 09:01:33 o/ 09:01:48 masahito cannot join today. 09:01:56 #chair priteau 09:01:57 Current chairs: hiro-kobayashi priteau 09:02:25 Todays agenda: https://wiki.openstack.org/wiki/Meetings/Blazar#Next_meetings 09:02:36 1. Blazar client 0.3.1 09:02:45 2. Update team organization diversity tags 09:02:49 3. AOB 09:02:57 Anything else? 09:03:27 hi tejaswi 09:03:35 hi hiro 09:03:53 #topic 1. Blazar client 0.3.1 09:04:13 python-blazarclient was tagged 0.3.1 09:04:56 I could not find update on pypi. 09:06:07 python-blazarclient was never released on PyPI. I suppose there is some setup to do. 09:06:23 It would be better to register blazar packages on pypi, isn't it? 09:06:30 https://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases 09:06:49 Yes, of course. With the right configuration it can be automated 09:07:07 I found old blazar packages: https://pypi.python.org/pypi?%3Aaction=search&term=blazar&submit=search 09:07:56 Those are the initial package with version 0 09:08:06 #link https://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases 09:08:12 It is explained in this document 09:08:31 OK. I'll register this workitem as a bug in Launchpad for keeping track of it. 09:09:10 I don't think we need other packages than the client. Services are not published on PyPI anymore. 09:10:33 priteau: Do you know how other major projects do? 09:10:59 Do they register only client? 09:11:21 Yes. 09:11:54 Got it. I agree that we should register only library projects. 09:12:24 Then, we should remove old blazar and blazar-nova. And update python-blazarclient. 09:12:34 I'll describe it in the bug report. 09:12:55 Anything else about this topic? 09:13:46 #topic 2. Update team organization diversity tags 09:14:23 TC Thierry proposed a patch: https://review.openstack.org/#/c/522536/ 09:14:45 This patch removes single-vendor tag of Blazar :-) 09:15:13 Great! 09:16:35 New contributors have pushed patches to blazar repo recently. So I think no -1 on it :-) 09:17:08 masahito: hi 09:17:15 hiro-kobayashi: hi 09:17:23 faster than expected ;-) 09:17:24 sorry to be late. 09:17:37 #chair masahito 09:17:38 Current chairs: hiro-kobayashi masahito priteau 09:18:06 masahito: we are talking about the single-vendor tag 09:18:43 Diversity of blazar contributors has been getting better :-) 09:19:13 That's good news. 09:19:24 thanks to all who had helped on achieving this 09:19:55 masahito: info: In agenda 1, we agreed we should update python-blazarclient in pypi. And remove old blazar and blazar-nova in pypi. 09:20:04 I hope we could get multi-diversity tag or something like this soon. 09:20:39 hiro-kobayashi: thanks. 09:20:49 I'll read the meeting log later. 09:21:11 zuulv3 has pypi release job, doesn't it? 09:22:10 masahito: yes, it would 09:22:15 release: 09:22:15 jobs: 09:22:15 - release-openstack-python-without-pypi 09:22:17 If so, we should update zuul job file. If not, I need to update it manually. 09:22:48 priteau: thanks! 09:23:10 I think we just need to remove this release block 09:23:12 Let's add release-openstack-python-without-pypi to python-blazarclient. And manually remove blazar and blazar-nova. 09:23:17 then it should use the default template 09:23:42 hiro-kobayashi: no, the code I pasted is what is in project-config/zuul.d/projects.yaml *now* 09:23:45 s/add/remove/ 09:23:59 priteau: ok 09:25:22 Anything else? 09:25:47 We can also switch blazar, blazar-nova, etc. to use the template release-openstack-server 09:26:18 it triggers release-openstack-python-without-pypi, but also the announce-release job 09:26:18 yes. It's my task from last meeting. 09:26:28 which, I think, sends an announcement email? 09:26:42 and needs to update openstack/releasemanagement repo. 09:27:07 maybe. 09:28:26 I've register bug report for tracking pypi workitems: https://bugs.launchpad.net/blazar/+bug/1734842 09:28:26 Launchpad bug 1734842 in Blazar "Update pypi settings" [Undecided,New] 09:29:36 priteau: do you know what the announce-release job do? 09:30:14 description: Send a release announcement after publishing a project 09:30:49 Thanks! 09:32:00 Let's update zuul settings. 09:32:16 Yes, I verified the code, it sends an email announcement 09:33:19 Where to send email? Other projects do that? 09:35:51 Anyway, let's investigate it and discuss at gerrit. 09:36:07 It is sent to openstack-announce 09:36:39 Or at least used to. I haven 09:36:49 I haven't seen any project announcement since last November 09:37:00 Last project annoucements: http://lists.openstack.org/pipermail/openstack-announce/2016-November/date.html 09:37:23 I will ask on the infra channel 09:37:43 priteau: thanks! 09:38:37 Anything else on this topic? 09:39:26 #topic AOB 09:39:49 Do you have updates or things to share here? 09:40:57 I'm working on multi-freepools bp now. I'll push the spec in this week. 09:41:06 that's from my side. 09:41:29 masahito: Great! Thank you for taking it over! 09:41:50 From my side, we've upgraded one of our clouds to Ocata, with Blazar mostly running Pike code 09:42:28 Great news! Is it fine?:-) 09:42:34 I am seeing some issues with leases stuck running the start_lease event. It might be caused by our local modifications, so I need to investigate more. 09:42:44 priteau: great and big challenge. 09:42:56 Oh, and I got an answer about the release emails already 09:43:05 They go to a separate list now: http://lists.openstack.org/pipermail/openstack-announce/2016-November/001966.html 09:44:06 Got it. thanks! 09:44:30 I didn't know release-announce@lists.openstack.org 09:46:39 My updates are reflected to patches on gerrit. So please review them. 09:47:44 Some patches are big, thanks for your patience :-) 09:48:20 If no AOB, we can finish the meeting. 09:49:24 it's okay for me. 09:49:41 OK. Let's finish todays meeting. Thanks all! good bye! 09:49:51 thanks all 09:49:53 #endmeeting