09:02:18 #startmeeting blazar 09:02:19 Meeting started Tue Apr 10 09:02:18 2018 UTC and is due to finish in 60 minutes. The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:02:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:02:23 The meeting name has been set to 'blazar' 09:02:49 #topic RollCall 09:02:53 o/ 09:02:54 priteau: hello 09:02:56 o/ 09:02:57 o/ 09:03:09 hiro-kobayashi, bertys: hello 09:03:13 today's agenda is 09:03:25 1. the Forum 09:03:32 2. story board migration 09:03:35 3. AOB 09:03:40 anything else? 09:04:02 Agenda looks good to me 09:04:52 let's get started. 09:04:59 #topic the Forum 09:05:48 As we discussed in the previous meeting, the Blazar team is thinking to propose a forum topic. 09:06:24 I wrote a breif draft for the submission. Please see/review it. 09:06:31 https://etherpad.openstack.org/p/blazar-forum-vancouver 09:07:26 thanks! 09:08:10 The dedline of the submission is this weekend. I'll submit it in few days. 09:08:35 Thank you masahito. I am making some small changes. 09:08:47 priteau: thank you. 09:09:06 There is less topics. I hope our proposal will be accepted. 09:09:28 https://wiki.openstack.org/wiki/Forum/Vancouver2018 09:09:59 Does it make sense to list PCI-passthrough devices as a potentially reservable resource? 09:10:16 yes 09:10:31 masahito: thanks for your initial draft! Makes sense to me. Let's collect more use cases/requirements 09:11:32 priteau: ah, It's not an attribute of instance or host, is it? 09:11:57 If you reserve a full host, you'll get the PCI devices with it, so that's already covered 09:12:08 But, for instance reservation, I am not sure if that would already work 09:13:20 I see. The number of PCI device is limited, so that's need to be reserved in case of instance reservation. 09:13:46 Yes, I think so. 09:15:32 let's move on to next 09:15:40 OK, I have made all my changes. I changed Demands to Requirements in the title. 09:15:56 Demands is a bit strong ;-) 09:16:16 priteau: thank you. It looks better to me. 09:16:23 #topic StoryBoard migration 09:17:07 There're some discussion in openstack-dev ML regarding to storyboard migration. 09:18:21 And storyboard team told me that the migration script from the launchpad to the storyboard works for Blazar project. 09:19:09 And also said if possible, let's think about moving to storyboad now. 09:20:22 My topic in the meeting is do you want to move to the storyboard in the R cycle? 09:20:24 masahito: which ML thread is it? 09:20:38 lots of thread 09:21:06 The recent ones seem to be project-specific, e.g. tripleo 09:21:23 I haven't read them, is the feedback from projects good so far? 09:22:33 If others are satisfied with storyboard, I am happy to move as well. 09:23:25 priteau: Agree 09:23:28 I've not read them yet. 09:23:39 What is expected to be migrated to storyboard? Blueprints? 09:24:17 The script only migrates bug reports. 09:25:37 What we need to do are 1. migrating BP, 2. creating whiteboard? for milestone, 3. other misc things. 09:27:12 I'm asking the them the two things: 1. who does BP migration, we or storyboard team? 2. how can we handle milestone and release in the storyboard. 09:28:07 So if there 09:28:45 if there's no problem, I'm okay to move it unless we have time to do that :-) 09:29:56 This blog is a overview of storyboard. https://storyboard-blog.io/ 09:30:07 +1 we should follow standards 09:30:14 If needed, please glance the blog. 09:30:48 Thanks masahito for discussing with the Storyboard team 09:30:50 And this is a view of blazar project. https://storyboard-dev.openstack.org/#!/project/300 09:31:40 masahito: I had quick look at https://storyboard-dev.openstack.org/#!/project/300. Looks ok. Let's clarify who is responsible for what. Thanks 09:32:52 masahito: Does it lose bug categorisation on import, i.e. importance (high, medium, etc.) and status (confirmed, in progress, etc.)? 09:34:40 priteau: looks like yes. That's one of my question to the team. 09:35:21 So I would say let's wait until those questions are answered. Maybe the migration script will improve. 09:35:45 According to the blog, each developers can create own worklists for piroriterizing. 09:37:11 Yes. My plan is migrating storyboard after r-3 milestone if the tool is better than the launchpad 09:37:44 There're less activities after r-3. It's easy to migrate 09:38:33 +1 and let's experiment a bit in the meantime 09:40:01 #topic AOB 09:40:23 Does someone have something to share/discuss/etc? 09:41:35 I just noticed this commit in governance: https://git.openstack.org/cgit/openstack/governance/commit/?id=c85c5b5fbc6e55f8e73d7c263daa2db64443ab18 09:41:52 Have we relinquished direct tagging/branch creation rights? 09:42:55 yes. 09:43:12 Great, just checking. 09:43:51 In AOB, I am behind on code reviews due to travel and deadlines, but hopefully will get back to it later this week. 09:44:07 We don't need to have the right because the release/tagging/branch creation are handled by release repo because Blazar is an official project. 09:44:31 priteau: Got it. 09:44:50 Speaking of release. Next week is r-1 milestone. 09:45:23 I'll put the 2.0.0.0b1 tag in next week. 09:47:06 Is that because we are an official project, we will now increase the major version number at each OpenStack release? 09:47:57 yes. 09:48:56 From my understand, major project increments its major version at each release. 09:51:01 Sounds good 09:51:06 Is there another topic? If nothing, let's finish the meeting early. 09:51:31 Nothing from me. 09:52:15 Thanks everyone, talk to you next week! 09:52:24 thanks all, bye! 09:52:29 #endmeeting