09:05:31 <masahito> #startmeeting blazar
09:05:32 <openstack> Meeting started Tue Sep 26 09:05:31 2017 UTC and is due to finish in 60 minutes.  The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:05:33 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:05:35 <openstack> The meeting name has been set to 'blazar'
09:06:07 <masahito> #topic Roll Call
09:06:11 <hiro-kobayashi> o/
09:06:18 <hrito> o/
09:06:38 <tejaswi> o/
09:06:40 <masahito> priteau told me he can't join this meeting.
09:06:45 <bertys> o/
09:06:52 <masahito> hi hiro-kobayashi hrito tejaswi bertys
09:07:14 <masahito> Today's agenda is
09:07:25 <masahito> 1. Forum Submission
09:07:37 <masahito> 2. Proposal to Official Project
09:07:45 <masahito> 3. Specs in revew
09:07:51 <masahito> 4. AOB
09:07:54 <masahito> anything else?
09:09:20 <masahito> #topic Forum Submission
09:10:19 <masahito> The Forum Submission deadline for Sydney summit is this Friday.
09:10:52 <masahito> If we have topics to discuss there, we should propose it.
09:11:25 <masahito> does someone has your idea?
09:14:47 <hiro-kobayashi> Blazar team has many things to discuss internally. And also with placement team. But I don't think of topics for public discussion.
09:15:21 <hiro-kobayashi> I will propose if any topic comes
09:15:43 <masahito> Some possible idea are 1. integration with Heat, 2. gathering other usecase for other resources.
09:16:13 <hiro-kobayashi> sounds good
09:16:51 <hiro-kobayashi> for 1, you mean make blazat to reserve a heat stack?
09:17:04 <hiro-kobayashi> or make heat to call blazar API?
09:17:25 <masahito> but the topics looks more developer side, so it could discuss in next PTG first.
09:17:48 <masahito> hiro-kobayashi: I can imagine 3 pattern for this.
09:19:01 <masahito> 1. Heat template support Blazar's lease.  2. Heat uses Blazar internally to make sure creating stack successfully. 3. Blazar supports Heat as one of resource plugin.
09:20:19 <hiro-kobayashi> Nice. I agree all of the patterns are useful
09:22:11 <masahito> okay, then I'll propose the integration topic to the Forum.
09:22:29 <masahito> and if you all have any topic, don't forget to propose it :-)
09:22:41 <hiro-kobayashi> Thanks masahito!
09:22:46 <hiro-kobayashi> okay
09:23:21 <masahito> #topic Proposal to Offical
09:25:57 <masahito> With a long discussion with TC members, Nova members and others, the proposal got majority of voting by TC members.
09:25:59 <masahito> https://review.openstack.org/#/c/482860/
09:26:22 <hiro-kobayashi> Great
09:26:37 <masahito> According to the ML, Blazar will be accepted as official today.
09:26:39 <masahito> http://lists.openstack.org/pipermail/openstack-dev/2017-September/122487.html
09:27:34 <bertys> masahito: Thanks
09:28:11 <hiro-kobayashi> Will be the best news of Blazar in this year ;-)
09:28:12 <masahito> I think the all great activities by the team members results it.
09:28:34 <masahito> hiro-kobayashi: right.
09:28:43 <masahito> bertys: my pleasure.
09:29:10 <masahito> I want to say great thank you to all.
09:29:47 <hiro-kobayashi> Me too. And of course thanks you very much, PTL masahito!
09:30:44 <masahito> Once Blazar have became official, I'll announce it in openstack-dev ML.
09:31:06 <hiro-kobayashi> thanks
09:31:23 <masahito> other comments for the topic?
09:31:57 <hiro-kobayashi> When can we publish docs in openstack.docs ?
09:32:50 <masahito> hiro-kobayashi: maybe.
09:33:41 <hiro-kobayashi> A lot of tasks after being an official ;-)
09:33:54 <masahito> I guess we need to migrate some stuffs under openstack.org domain; developer's doc, API docs or etc.
09:34:06 <bertys> masahito, hiro-kobayashi: this can be done once Blazar is official. Hopefully we can get help from the community
09:35:07 <masahito> bertys: yes, I think so.
09:35:46 <hiro-kobayashi> we should wait and see for a while :-)
09:37:14 <masahito> yes, TC members told me they'll tell me what we need to do after the proposal are approved.
09:37:37 <hiro-kobayashi> OK
09:38:11 <masahito> then move on next.
09:38:18 <masahito> #topic Specs in review
09:38:40 <masahito> hiro-kobayashi: you added the item, right?
09:38:46 <hiro-kobayashi> masahito: yes
09:39:06 <hiro-kobayashi> I pushed a Spec of resource-monitoring: https://review.openstack.org/#/c/506551/
09:39:34 <hiro-kobayashi> It is based on the discussion at the PTG: https://etherpad.openstack.org/p/blazar-resource-monitoring
09:39:47 <hiro-kobayashi> Please review it.
09:40:00 <masahito> Great!
09:40:43 <hiro-kobayashi> The spec depends on the state-machine blueprint because it adds new states to lease and reservation
09:41:02 <masahito> I'll review it as soon as possible.  This feature could be one of main features in Q cycle.
09:41:22 <hiro-kobayashi> masahito: thanks!
09:41:41 <hiro-kobayashi> The states transition graph should be defined for the first.
09:42:10 <hiro-kobayashi> So, I think the state-machine blueprints should be proceeded before the resource-monitoring blueprint
09:42:40 <hiro-kobayashi> Does anyone plan to work on the state-machine blueprint?
09:43:07 <hiro-kobayashi> If no one, I can take it
09:44:25 <masahito> Your plan for the state-machine is implement a mechanism to change the state? or Just writing state graph in docs?
09:45:25 <hiro-kobayashi> First target is to write states graphs for lease and reservation
09:46:03 <hiro-kobayashi> And change implementation if it does not follow the states graphs
09:46:26 <hiro-kobayashi> I do not plan to introduce a new mechanism for managing states.
09:47:15 <masahito> because it's big task to implement a mechanism to ensure lease and reservation follow the state-machine.
09:47:23 <hiro-kobayashi> To my understanding, the status field is not used (NULL) for now. So I plan to utilize the field.
09:47:39 <hiro-kobayashi> masahito: yes
09:47:41 <masahito> hiro-kobayashi: okay, it makes sense.
09:48:38 <hiro-kobayashi> For the first, I will make states transition graphs and push a spec which includes these graphs
09:48:45 <hiro-kobayashi> So, please review it
09:49:36 <bertys> hiro-kobayashi: quick question in the case 1-2 / resource monitoring BP. Lets's assume that available hosts < min host (lease not started yet / failure occured). I guess we can wait for situation to improve until lease_start. But what shall be done if situation not improved?
09:49:41 <hiro-kobayashi> Maybe first version needs a lot of changes ;-)
09:50:43 <hiro-kobayashi> bertys: I plan to start lease anyway. In this case, the lease status will be ACTIVE_DEGRADED
09:51:58 <bertys> hiro-kobayashi: OK, understood
09:52:47 <hiro-kobayashi> States graphs will help understanding it. So, please wait for a while.
09:54:15 <hiro-kobayashi> That's all for this topic from me
09:54:42 <hiro-kobayashi> Please wait for my spec proposal
09:55:00 <masahito> okay.
09:55:42 <masahito> but it's good for everyone to review the monitoring's BP first.
09:56:01 <hiro-kobayashi> yes, please
09:56:04 <masahito> any comment for the topic?
09:58:14 <masahito> #topic AOB
09:59:33 <masahito> Does someone have something to discuss?
09:59:47 <hiro-kobayashi> Just 1 thing to share
10:00:07 <hiro-kobayashi> I've gotten mail from a new commer to Blazar
10:00:23 <hiro-kobayashi> He tests instance reservation
10:00:40 <hiro-kobayashi> We've gotten a new user :-)
10:00:52 <hiro-kobayashi> that's all
10:00:53 <bertys> hiro-kobayashi: Great!
10:01:17 <hiro-kobayashi> berys: I'll ask him his use cases, etc.
10:01:35 <masahito> good news
10:01:44 <hiro-kobayashi> s/betys/bertys sorry
10:02:12 <bertys> hiro-kobayashi: you made me smile );
10:02:25 <bertys> s/berys/bertys
10:02:37 <hiro-kobayashi> oops...
10:02:44 <bertys> no worries
10:02:51 <hiro-kobayashi> thanks ;-)
10:02:53 <masahito> haha
10:03:25 <masahito> I hope he come to the team.
10:03:51 <masahito> okay, then last 1 min.
10:04:46 <masahito> thanks all, see you in next week.
10:04:59 <hiro-kobayashi> thanks! see you
10:05:11 <bertys> bye
10:05:16 <masahito> #endmeeting