09:01:06 <masahito> #startmeeting blazar
09:01:07 <openstack> Meeting started Tue Oct 31 09:01:06 2017 UTC and is due to finish in 60 minutes.  The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:01:08 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:01:10 <openstack> The meeting name has been set to 'blazar'
09:01:29 <masahito> #topic RollCall
09:01:40 <hiro-kobayashi> o/
09:01:45 <hrito> o/
09:02:05 <masahito> Today's agenda is
09:02:07 <tejaswi> o/
09:02:12 <priteau> o/
09:02:12 <masahito> 1. onboarding session
09:02:20 <masahito> 2. next weekly meeting
09:02:25 <masahito> 3. specs in review
09:02:28 <masahito> 4. AOB
09:02:31 <masahito> anything else?
09:02:44 <masahito> hiro-kobayashi hrito tejaswi priteau: hi all o/
09:02:50 <masahito> #chair hiro-kobayashi priteau
09:02:51 <openstack> Current chairs: hiro-kobayashi masahito priteau
09:03:41 <masahito> #topic onboarding session
09:04:29 <masahito> As I mentioned, Blazar team has onboarding session at the Sydeny Summit.
09:04:39 <masahito> I created the slide deck for the session.
09:04:52 <masahito> https://docs.google.com/presentation/d/1vOYlFuIK4NX7C73xT-JQkkRdsPzjG1BMq_bXCMKvEe4/edit?usp=sharing
09:05:33 <masahito> The purpose of the session is dive into the blazar details as well as introduce project overview.
09:05:40 <hiro-kobayashi> Great! thanks you very much
09:06:31 <masahito> So I plan to introduce blazar overview first, then we'll have QA time later.
09:08:01 <masahito> priteau: is it okay to mention Chameleon project in the slide as a real deployer of Blazar?
09:08:08 <priteau> Of course!
09:08:16 <masahito> priteau: thanks!
09:08:54 <masahito> If you find something that should be improved, feel free to update the presentation!
09:09:26 <masahito> any comments for the onboarding?
09:11:13 <priteau> Should we link to official docs rather than the wiki?
09:11:38 <masahito> right.
09:11:52 <masahito> The official docs is better.
09:11:58 <hiro-kobayashi> +1
09:12:52 <masahito> I noticed blazar isn't listed in https://docs.openstack.org/queens/projects.html yet.
09:13:10 <masahito> But it'll be listed once hiro-kobayashi's patch.
09:13:41 <priteau> I made a few little changes to the slides
09:13:44 <priteau> They look great!
09:15:02 <masahito> priteau: thanks. I really appreciate you.
09:15:29 <masahito> okay then, let's move on to next.
09:15:54 <masahito> #topic next meeting and meeting at the Summit
09:16:21 <masahito> I plan to skip next weekly meeting because of the Sydney Summit.
09:17:10 <masahito> Is it okay? Or if someone want to have the meeting, could someone do a chair?
09:17:53 <hiro-kobayashi> okay for me and I cannot attend.
09:17:58 <priteau> ok for me
09:18:41 <masahito> okay, let's skip next meeting. I'll send it to ML.
09:19:36 <masahito> And I'd like to ask all that should we have Blazar team meeting in the Summit?
09:20:39 <masahito> IMHO, I don't have strong opinion we should have the meeting b/c we had a virtual meetup at the last PTG.
09:21:11 <hiro-kobayashi> me, neither.
09:22:41 <priteau> I don't think we need a meeting since we have agreed on the list of blueprints to work on
09:23:18 <masahito> okay.
09:23:49 <masahito> I hope new comers of blazar will join the onboarding session.
09:24:20 <masahito> #topic Specs in review board
09:25:07 <masahito> I can see three specs in gerrit now.
09:25:12 <masahito> 1. https://review.openstack.org/#/c/508093/
09:25:18 <masahito> 2. https://review.openstack.org/#/c/506551/
09:25:26 <masahito> 3. https://review.openstack.org/#/c/516222/
09:26:17 <masahito> #1 and #2 looks we need to do much activities to complete the specs.
09:27:24 <masahito> So to make things forward, I'd like to merge #1 and #2. Then it's good to start the implementation.
09:28:03 <masahito> How do you think?
09:28:04 <priteau> I'll try to review the latest version of the specs today
09:28:16 <priteau> You already have a +2 so if it looks good to me I will merge
09:28:32 <hiro-kobayashi> thanks, priteau!
09:28:39 <masahito> priteau: thanks!
09:30:46 <masahito> nothing more to Specs. Let't move on to last item.
09:32:15 <masahito> #topic AOB
09:32:56 <masahito> Does someone have topics to share/discuss/etc?
09:33:07 <hrito_> I have one
09:33:51 <hrito_> I've assigned another task and I don't have much time to implement the BP: https://blueprints.launchpad.net/blazar/+spec/deploy-api-in-wsgi
09:34:16 <hrito_> So I would appreciate it if someone could take over this BP.
09:35:50 <masahito> hrito_: That's a bad news ;-0  Is it hard to join the activities in the future?
09:37:14 <hrito_> Maybe I will have time to fix some bugs but it's hard to implement BP :-<
09:37:36 <hiro-kobayashi> hrito_: How about the task to get backward compatibility for https://review.openstack.org/#/c/498340/ ? Can you complete it?
09:38:48 <hrito_> hiro-kobayashi: At least, I'll try to complete it
09:40:53 <masahito> hrito_: If you have not much time to implement the blazarclient one, please let me know.
09:41:21 <hrito_> masahito: ok, thanks
09:41:55 <masahito> It's a critical bug for client and dashboard. We need to fix it at least before Q release.
09:42:23 <hrito_> masahito: right
09:42:38 <masahito> hrito_: okay, I hope you can work well in another task.
09:42:51 <hrito_> thanks!
09:43:18 <hrito_> that's all from me
09:44:46 <hiro-kobayashi> I have 1 topic about the state-machine spec
09:45:27 <hiro-kobayashi> I proposed a base implementation for the spec: https://review.openstack.org/#/c/512198/
09:46:28 <hiro-kobayashi> In this implementation, I proposed a new module 'statuses' and removed the module 'states'
09:47:01 <hiro-kobayashi> the states module uses status, status_reason, action of leases table
09:47:31 <hiro-kobayashi> On the other hand, the statuses module uses only the 'status'
09:47:53 <hiro-kobayashi> priteau: Is it acceptable for ChameleonCloud?
09:48:17 <priteau> Sure. It's simpler that way and more in line with other OpenStack services
09:48:49 <hiro-kobayashi> pritau: good to hear that :-)
09:49:14 <hiro-kobayashi> Then I will continue implementation after the spec is merged.
09:49:51 <hiro-kobayashi> That's all from me
09:50:12 <masahito> statuses.py looks bit strange for me. Is there any reason the name isn't status.py?
09:51:38 <hiro-kobayashi> Not a strong reason, but just follows other module names like exceptions, opts, and so on.
09:51:47 <priteau> It's the plural of status
09:52:26 <hiro-kobayashi> The statuses module contains multiple *Status classes, so I named it statuses.py.
09:52:44 <hiro-kobayashi> But I don't have a strong preference for it.
09:53:32 <hiro-kobayashi> How do you all think which is better, statuses.py or status.py?
09:54:06 <masahito> hiro-kobayashi: I see. I usually see the the plural naming only at directory name. So I asked it.
09:54:17 <priteau> An alternative would be to keep using states, but that means changing the model to use state field
09:56:10 <hiro-kobayashi> priteau: Are you proposing to add a new 'state' field?
09:56:22 <hiro-kobayashi> for leases table?
09:56:26 <masahito> priteau: yes, but it could confuse new contributors because of the naming difference.
09:56:28 <priteau> To rename status to state, but that
09:56:32 <priteau> that's a lot of change
09:57:20 <hiro-kobayashi> priteau: yes. And I think if we rename it, the status field of reservations and events tables should be also renamed.
09:57:51 <priteau> It is probably too much change.
09:57:52 <hiro-kobayashi> Can ChameleonCloud accept accept such a big change?
09:58:13 <priteau> Chameleon follows what the upstream community decides :-)
09:59:11 <priteau> The question is, is it worth changing the model and lots of code, just to rename status to state
09:59:14 <hiro-kobayashi> OK. We should keep backward compatibility, anyway.
09:59:14 <priteau> Probably not worth it
09:59:34 <hiro-kobayashi> priteau: agree.
10:00:42 <hiro-kobayashi> masahito: If you prefer 'status.py' and no one has an objection, I'll rename it 'status.py'
10:00:49 <masahito> time is up. keep discussion on the gerrit or IRC.
10:01:27 <hiro-kobayashi> OK
10:01:28 <masahito> hiro-kobayashi: I don't review the patch well. So you can update it after I review it.
10:01:42 <hiro-kobayashi> masahito: ok. thanks
10:01:42 <masahito> hiro-kobayashi: it can reduce extra-works.
10:01:57 <masahito> bye, all
10:02:17 <masahito> See you in Sydney or next meeting in two week!
10:02:25 <masahito> #endmeeting