09:00:46 <masahito> #startmeeting blazar
09:00:47 <openstack> Meeting started Tue Feb 14 09:00:46 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:48 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:50 <openstack> The meeting name has been set to 'blazar'
09:00:58 <masahito> hi all
09:01:09 <masahito> #chair hiro-kobayashi priteau r-mibu
09:01:10 <hiro-kobayashi> hi
09:01:11 <openstack> Current chairs: hiro-kobayashi masahito priteau r-mibu
09:01:31 <masahito> #topic rollcall
09:01:38 <masahito> o/
09:01:38 <r-mibu> o/
09:01:40 <hiro-kobayashi> o/
09:01:45 <priteau> o/
09:01:54 <GeraldK> o/
09:02:11 <masahito> Today's agenda is...
09:02:19 <masahito> 1. Action items from last call
09:02:26 <masahito> 2. Loads to Ocata release
09:02:32 <masahito> 3. Next meeting
09:02:43 <masahito> 4. +1 or +2 at Code review
09:02:51 <masahito> 5. Pike cycle discussion
09:02:56 <masahito> anything else?
09:03:34 <masahito> ok, then move on to
09:03:46 <masahito> #topic Action items from last meeting
09:04:09 <masahito> I can see 3 items from last meeting
09:04:17 <masahito> 1. ACTION: migrate namespace climate to blazar by the end of Feb.
09:04:24 <masahito> 2. ACTION: review and update the doc in github wiki and doc/source
09:04:34 <masahito> 3. ACTION: write a release note that says 'instance reservation is not supported in Ocata'
09:04:40 <masahito> any update?
09:05:32 <hiro-kobayashi> #1, masahito migrated the namespace, thanks!
09:05:53 <hiro-kobayashi> I'm reviewing it now
09:06:03 <masahito> hiro-kobayashi: ok, thanks
09:06:14 <priteau> I will review your migration patches this week
09:06:24 <masahito> priteau: got it.
09:06:38 <hiro-kobayashi> And I pushed blazar-nova patche related to masahito's patch: https://review.openstack.org/#/c/433483/
09:06:54 <hiro-kobayashi> Please review it, too
09:07:13 <hiro-kobayashi> The biggest migration is for blazar repo
09:07:28 <hiro-kobayashi> Does anyone work on it?
09:08:07 <masahito> I'm not yet. I plant to start tomorrow.
09:08:28 <masahito> hiro-kobayashi: if you're working I'll stop it.
09:08:38 <hiro-kobayashi> Not yet
09:08:43 <masahito> ok
09:09:01 <hiro-kobayashi> masahito: Thanks a lot!
09:09:17 <masahito> when you start above a task, change bug assignee to yourself.
09:09:18 <masahito> https://launchpad.net/blazar/+milestone/0.2.0
09:09:49 <masahito> I listed all task that we need to finish by Ocata release in the link.
09:10:03 <priteau> Thank you very much for sorting Launchpad bugs and milestones
09:10:07 <priteau> It's well organized now
09:10:33 <GeraldK> thanks masahito. that's quite useful
09:11:02 <masahito> once all bug is marked "fix committed" we can release and stand great start points :-)
09:11:54 <masahito> another update is nothing, go to next
09:12:16 <hiro-kobayashi> Oh I hove one more update
09:12:26 <hiro-kobayashi> about action #3
09:13:11 <hiro-kobayashi> I pushed some patches related to release note. so please review them.
09:13:28 <masahito> hiro-kobayashi: sure
09:13:59 <hiro-kobayashi> If there should be more notes, please push patches like : https://review.openstack.org/#/c/431320/
09:14:41 <masahito> then...
09:14:50 <masahito> #topic Loads to Ocata release
09:15:26 <masahito> as I mentioned before I added O release (0.2.0 release) milestone in launchpad.
09:15:33 <masahito> #link https://launchpad.net/blazar/+milestone/0.2.0
09:15:53 <masahito> When we fix the bug in the list, we'll release it.
09:16:13 <masahito> any comments or idea?
09:17:21 <hiro-kobayashi> I completely agree with the milestone.
09:17:36 <priteau> Looks good too. I will check again the Etherpad to see if anything was missed.
09:17:50 <masahito> thanks all.
09:17:52 <priteau> comment about https://bugs.launchpad.net/blazar/+bug/1663204: I sent the email to openstack-dev, all Blazar cores, and the committer of the patch that changed the behavior. No answer yet.
09:17:52 <openstack> Launchpad bug 1663204 in Blazar "Non-admin users cannot create reservations with default policy rules" [High,Triaged] - Assigned to Pierre Riteau (priteau)
09:18:48 <hiro-kobayashi> priteau: thank you for handling it
09:20:11 <masahito> priteau: you have the exact way to solve it now?
09:20:46 <priteau> masahito: I know how to fix it. I will work on the patch this week.
09:21:20 <masahito> priteau: ok, then we can fix it. Thanks.
09:22:15 <masahito> let's move on to next.
09:22:26 <masahito> #topic Next weekly meeting
09:22:51 <masahito> Some of us will be in PTG next week.
09:23:34 <priteau> Our usual slot is in the middle of the night in Atlanta
09:23:48 <masahito> I think it's hard to join weekly meeting from Atlanta.
09:24:11 <hiro-kobayashi> Yeah, now it's 4 a.m. in Atlanta
09:24:14 <masahito> so do we have next weekly meeting or skip?
09:24:33 <masahito> hiro-kobayashi: haha, I guess I'll be in flight
09:24:52 <priteau> We should skip the next meeting but keep in touch via Gerrit / Launchpad / email
09:25:02 <GeraldK> priteau: +1
09:25:10 <masahito> +1
09:25:25 <hiro-kobayashi> +1
09:26:00 <r-mibu> +1
09:26:13 <masahito> ok, skip the next meeting but keep in touch.
09:26:43 <masahito> #topic +1 or +2 at Code Review
09:27:25 <GeraldK> and -1 or -2 at code review
09:27:38 <masahito> I heard one problem in gerrit review board that after one of cores add CR +2 it hides others -1 in gerrit board.
09:27:47 <masahito> GeraldK: right.
09:28:07 <masahito> IMO, there're two options for the problems.
09:28:40 <priteau> masahito: I don't think the +2 hides the -1, but it enables the W+1 button, so the -1 reviews can be easily overlooked
09:28:51 <masahito> 1. After cores try to W +1, another core need to check -1 exists in the patch.  Of course, if the -1 is not related to the patch or like this, the core can push W +1 bottun :-)
09:29:35 <masahito> s/After/ When/
09:29:42 <masahito> 2. When cores try to CR +2 the core uses +1 instead of +2. And then another core who tries to add W+1 adds both CR+2 and W+1.
09:30:47 <hiro-kobayashi> priteau: it's hided in list view though
09:31:07 <masahito> priteau: IIRC, cores can push W+1 bottun anytime.
09:31:37 <priteau> masahito: I mean the blue button that shows up when there is at least one existing +2
09:32:25 <masahito> priteau: got it.
09:33:21 <priteau> I would be happy to go with option 2)
09:33:39 <hiro-kobayashi> Do you know how it is managed in another projects?
09:34:06 <hiro-kobayashi> I think it's better to follow major project's way
09:34:24 <masahito> priteau: when there is CR-2 at least one, does the blue button dissapear?
09:34:59 <priteau> masahito: I think so. CR-2 means "blocks merging"
09:35:44 <masahito> priteau: From my understanding CR-2 means "blocks merging and *not required* the patch now"
09:36:10 <masahito> CR-1 means "blocks merging and needed some improvements for merge"
09:37:50 <masahito> from the meaning, I think -2 have too strong opinion to hide the blue button.
09:38:41 <masahito> but of course, we could missingly push the button.
09:39:08 <priteau> masahito: I guess it depends on interpretation. When I used -2 I didn't want to offend anyone, but I strongly thought the patch should not be merged until further improvements where made, and there was already a +2 on it
09:39:22 <priteau> by the way, there is this core reviewer guide: http://docs.openstack.org/infra/manual/core.html
09:41:03 <masahito> priteau: I know you didn't want to offend anyone. of course.
09:42:17 <masahito> priteau: so, you think 2. looks better?
09:42:45 <priteau> masahito: I am not sure. It doesn't seem to follow what OpenStack documentation recommends.
09:43:07 <GeraldK> see also here: http://docs.openstack.org/infra/manual/developers.html in section "Code Review"
09:43:14 <masahito> hiro-kobayashi: r-mibu: GeraldK: how do you think?
09:44:15 <hiro-kobayashi> I think it's better to follow major project's way. How is it managed in Congress?
09:44:34 <GeraldK> IMHO, -1 should be used if we ask for some update of the code; -2 to be used for blocking the patch if you think it is harmful
09:45:19 <GeraldK> IMHO, all -1 should have been addressed (either by taking it into account or by a reply that is explaining why it could not be taken into account)
09:45:35 <GeraldK> before workflow +1
09:46:54 <masahito> I think Congress doesn't follow OpenStack standards. The team uses option #2 because it's easy to see +2 or -1 in patch *list page*
09:47:40 <GeraldK> IMHO, it is okay if a core votes +2. we can have the gentleman agreement that WF+1 is only pressed when you have checked all comments are addressed. usually, if there is a -1, this will anyway be removed once a new patch set is uploaded.
09:47:48 <hiro-kobayashi> masahito: thanks
09:48:21 <GeraldK> I am no core so anyway I am limited to -1/+1 so I will leave this decision up to you cores
09:48:35 <priteau> GeraldK: +1
09:48:36 <hiro-kobayashi> GeraldK: +1
09:48:44 <priteau> Checking for all -1 before merging
09:48:52 <hiro-kobayashi> yes
09:49:01 <masahito> ok,
09:49:27 <masahito> we have a great agreement :)
09:50:02 <masahito> Any comments for the topic?
09:50:35 <masahito> If nothing, we can move to open discussion.
09:51:00 <masahito> #topic Open Discussion
09:52:18 <masahito> I'd like to start our new discussion to Pike
09:52:51 <masahito> we gathered some new features we want in the etherpad.
09:52:52 <masahito> https://etherpad.openstack.org/p/Blazar_status_2016
09:53:49 <GeraldK> shall we organize the tasks similar to the Blazar 0.2.0 milestones launchpad?
09:53:58 <masahito> IIRC, most of us will be in Boston but we can start the discussion before Boston.
09:54:16 <hiro-kobayashi> I’v been updating existing launchpad blueprints and adding some new blueprints for future release.
09:54:22 <masahito> GeraldK: right.
09:54:31 <hiro-kobayashi> #link https://blueprints.launchpad.net/blazar
09:54:48 <hiro-kobayashi> But It's not completed yet
09:54:59 <hiro-kobayashi> I’ve applied nova-specs template to all of blazar blueprints, for describing blueprints (and specs) in detail.
09:55:07 <masahito> ok, it looks like I should create a new milestone 0.3.0.
09:55:32 <GeraldK> hiro-kobayashi: thanks. I think it is reasonable to align to nova specs
09:55:47 <hiro-kobayashi> Then we will pick up blueprints for 0.3.0
09:56:24 <hiro-kobayashi> I thinks all ToDo have been listed in Launchpad blueprints
09:56:35 <GeraldK> so everybody should check if we miss some specs in the launchpad
09:56:41 <hiro-kobayashi> Please check it and add some blueprints if needed
09:56:56 <hiro-kobayashi> GeraldK: yes please
09:57:23 <masahito> hiro-kobayashi: just one question. Can we implements all new features by P?
09:57:53 <hiro-kobayashi> I don't think so. So we have to prioritize them
09:57:55 <masahito> hiro-kobayashi: if not, we should pick up hight priority new features.
09:58:11 <GeraldK> should we do this prioritization in Etherpad?
09:58:14 <hiro-kobayashi> masahito: yes
09:58:23 <masahito> GeraldK: I think so.
09:58:31 <GeraldK> masahito: okay.
09:59:05 <masahito> because we should focus on some features and it makes us have good progress.
10:00:13 <masahito> I think vote +1 to each features in the etherpad and pick up features from higher numbers.
10:00:26 <hiro-kobayashi> OK
10:00:45 <hiro-kobayashi> After prioritize them, we will decide assignees
10:01:15 <masahito> running out time
10:01:20 <GeraldK> we could copy&paste the list from launchpad to the etherpad as this list may be better organized that the current collection of ideas in the Etherpad. what do you think?
10:01:47 <masahito> GeraldK: +1
10:01:50 <priteau> GeraldK: merging them is a good idea
10:02:05 <GeraldK> okay. I will copy&paste later today.
10:02:16 <hiro-kobayashi> Thanks!
10:02:18 <masahito> GeraldK: thanks!!
10:02:40 <masahito> then, thanks all!
10:02:53 <masahito> #endmeeting