09:00:57 #startmeeting blazar 09:00:57 Meeting started Tue Apr 11 09:00:57 2017 UTC and is due to finish in 60 minutes. The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:58 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:01:00 The meeting name has been set to 'blazar' 09:01:09 #chair priteau r-mibu 09:01:10 Current chairs: masahito priteau r-mibu 09:01:24 #topic Roll Call 09:01:41 o/ 09:01:43 o/ 09:01:43 o/ 09:02:35 Today's agenda is... 09:02:40 1. ocata/branch 09:02:51 2. boston summit talks 09:03:05 3. Pike bp status check 09:03:12 anything else? 09:03:16 hi there 09:03:24 GeraldK: hi 09:03:57 masahito: forum? 09:04:18 priteau: yes. thanks! 09:04:24 4. forum 09:04:37 btw, hiro-kobayashi is out of town today. 09:05:23 #topic ocata branch 09:05:37 Just notification from my side. 09:06:04 Gerrit is ready to create branch. then I created stable/ocata branch last week. 09:06:13 #link https://github.com/openstack/blazar/tree/stable/ocata 09:06:47 if there is any fix needed to backport, we can do it. 09:07:23 any comment? 09:07:29 fyi: https://docs.openstack.org/project-team-guide/stable-branches.html 09:07:35 Do we have stable branches for blazar-nova and clients too? 09:08:36 as we discuss before, we don't plant to have branches at client side. 09:08:58 blazar-nova needs branch? 09:09:09 Even if we don't backport patches, I think users may want to install blazar with devstack configured to use stable/ocata 09:09:40 If there is no branch, it uses master, but if we make radical changes to master in the future, devstack install of stable/ocata won't work 09:09:52 I am thinking in particular of blazar-nova 09:09:59 +1 to have stable branch for blazar-nova 09:10:15 we have release tag instead of branch now. 09:10:36 ok, I'll create stable branch for blazar-nova. 09:11:14 then, let's go on next. 09:11:35 #topic Boston Summit Talks 09:11:58 Who added the topic in agenda? 09:12:29 I suggested last week that we should talk about it today 09:12:39 It was +1 by several people 09:13:00 we had an offline meeting related to the Promise/Blazar session preparation. 09:13:45 presentation will cover a) problem statement, b) intro to Blazar and OPNFV Promise, c) Resolutions 09:14:38 GeraldK: thanks for update. 09:14:59 Do you need any help from this team? 09:15:55 masahito: we are still in drafting phase. maybe, we will share slides prior to submission for team feedback 09:16:29 GeraldK: got it. 09:16:54 For project update session, I plan to start preparing this week. 09:17:43 The speakers of this talk are priteau, hiro-kobayashi and me. So I plan to have following three sections. 09:17:46 masahito: What do you plan to use? Google Slides is very convenient for collaborating on a presentation 09:18:44 a) overview and current activities of Blazar, b) Ocata release and c) Pike release priorities 09:19:37 priteau: either Google Slides or PowerPoint sharing mail is ok for me. 09:19:49 priteau: do you have any preference? 09:20:03 I prefer Google to avoid a lot of back and forth by email 09:20:35 priteau: got it. 09:21:31 priteau: I think it's better to make outline before writing Google Slide. is it ok to discuss the outline at mail? 09:21:51 yes, outline by email or by etherpad 09:22:24 I'll send you the mail or etherpad page later. 09:22:41 thanks 09:23:20 we also have a forum session in Boston summit. 09:23:32 #link http://forumtopics.openstack.org/cfp/details/124 09:25:06 In this session, we would discuss the requirements from scientific WG. but as tom commented we could discuss "reservation" feature itself here. 09:25:44 Do you know how long the session last? 09:25:58 maybe 40 mins 09:26:23 We won't have much time to discuss Blazar 09:26:52 yes. 09:27:29 So I'm thinking we should organize some meeting about Blazar itself in another time slots. 09:27:50 +1 to have a Blazar team meeting 09:28:23 +1 09:28:38 +1 09:28:58 I'll send a doodle to manage the time slot next week or later. 09:29:30 after forum session time slots are fixed. 09:29:54 I better finish planning my Boston schedule then 09:31:25 ok. 09:31:36 any comments? 09:32:51 #topic Pike BP status 09:33:51 does anyone have update? 09:34:29 I'll start first. 09:34:46 I wrote up overview of new instance reservation. 09:34:51 #link https://etherpad.openstack.org/p/new-instance-reservation 09:35:05 and shared it in openstack-dev ML 09:35:58 the details of implementation is still drafting, but please review the overview. 09:36:39 Thanks masahito 09:37:07 To be clarified why we need "reservation", I focused on motivation/problems. 09:37:44 because there are some discussion about "reserving instances" in operators ML 09:38:40 thanks. that is very useful. 09:39:28 any other updates? 09:40:49 #topic AOB 09:40:58 Still catching up with reviews for me. Work is very busy at the moment 09:42:01 priteau: np. 09:43:39 if there're patches you want to review, please add comments about it. we can keep it in review. 09:44:02 ok 09:44:43 masahito: I agree with your statement in one of the changes that as we have a small team, we can have more high level BP specs and do not necessarily need to deep-dive into implementation details yet 09:45:20 +1 09:47:40 in that case, I think the spec is ready to merge now. 09:47:43 #link https://review.openstack.org/#/c/451249/ 09:49:17 please add +1 if you agree specs or don't disagree specs. because it's very useful for other to check different opinions. 09:49:22 I was just reading it this morning, I will try to go over it by the end of the day 09:49:35 priteau: Thanks!! 09:49:52 I'll chenge its review state 09:51:52 if no other items we can finish this meeting earlier today. 09:52:15 ok 09:52:32 okay. thanks and bye. 09:52:45 then thanks all! 09:52:51 bye all 09:52:51 #endmeeting