09:00:27 #startmeeting blazar 09:00:28 Meeting started Tue Oct 10 09:00:27 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:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:31 The meeting name has been set to 'blazar' 09:00:43 #topic RollCall 09:00:57 o/ 09:00:59 o/ 09:01:00 o/ 09:01:42 priteau_, hiro-kobayashi, hrito: hello 09:01:47 Today's agenda is 09:01:54 1. Onboarding Room 09:01:59 2. Team Mascot 09:02:01 3. AOB 09:02:06 anything else? 09:03:01 hi 09:03:03 okay, let's start first item 09:03:12 hi 09:03:17 #topic Onboarding Room 09:03:23 GeraldK, tejaswi: hi 09:03:55 As I mentioned the last meeting, Blazar team have the onboarding session in the Sydney Summit. 09:04:12 I plan to talk about following topics in it. 09:04:39 1. Blazar introduction, 2. Blazar usecase, 3. Blazar Demo and 4. feature plan 09:05:13 Does someone have other idea that we need to talk there? 09:06:19 Do you cover the internal architecture of Blazar in one of the topics? 09:07:00 priteau_: I'm thinking #1 covers the architecture. 09:07:06 OK 09:07:15 Will 4. feature plan include a description of the relationship with other projects? 09:08:33 GeraldK: okay. We only have the relationship with PlacementAPI (Nova) team, right? 09:09:08 If someone speaks to other project, please let me know. I'll add it :-) 09:09:37 there may be some relationship with the to-be reaper service that is also of interest to other projects 09:09:39 s/speaks to/speaks with/ 09:10:12 when we look at future plans we may also need to talk to Neutron and Cinder folks? 09:11:17 GeraldK: yes. If we mention it, it's good to start to talk to other team. 09:12:02 ok 09:12:13 GeraldK: but I'm still not clear the requirements for Cinder(Storage/Volume) reservation. 09:14:25 other comments for the session? 09:14:51 Is the schedule fixed? 09:15:34 hiro-kobayashi: not yet b/c other forum sessions are in selection phase. 09:15:54 OK 09:17:29 #topic Team Mascot 09:18:25 Official OpenStack project can have its mascot. 09:18:30 #link https://www.openstack.org/project-mascots 09:18:31 https://www.openstack.org/project-mascots 09:18:37 GeraldK: Thanks :-) 09:19:08 Blazar is now official project so we can apply our log. 09:19:21 +1 to do so 09:19:48 +1 09:20:18 We can gather the idea this week, then decides the order in the next meeting. 09:20:53 my proposal was a "house mouse" 09:21:15 Blazar (astronomy) is an obvious choice, but I don't even know why we are named Blazar… 09:21:32 If you have an idea, please listing here or later. 09:21:36 mice are territorial animals and dominant males respect each other's territories. 09:21:39 also, we are just a small project :) 09:21:53 GeraldK: Sounds good :-) 09:22:09 If we go animal like most projects, I would propose a squirrel, because they 09:22:16 "reserve" nuts for the winter 09:22:41 GeraldK: sound nice. 09:23:05 priteau_: me neither. I'm not clear the reason of "Blazar" 09:23:19 priteau: Nice idea! 09:23:32 priteau_: Glance choose a squirrel, isn't it? 09:23:44 masahito: Oh, yes 09:23:52 I like squirrel as we are shelving resources. when it comes to re-using the resources prior to a reservation that does not fit anymore 09:24:00 masahito: it's a chipmunk 09:24:29 But I like the mouse too, as long as it's a cute mascot 09:24:32 mashito: a bit different, haha 09:24:41 s/masahito/priteau/ 09:25:08 GeraldK: in the winter squirrels go dig back the nuts to eat them ;-) 09:25:17 priteau_: oh, I didn't know there is difference. haha 09:26:00 I would imagine our mascot would show the entire squirell with a nut in its hands 09:26:36 so quite different from Glance which shows only the face 09:27:03 priteau_: sounds good! 09:27:40 GeraldK: how did you envision your mouse would look? 09:27:41 I don't have another idea 09:27:54 shrike does same behaviors. 09:28:32 squirrel could look like this: http://7-themes.com/data_images/out/70/7011607-squirrel-nut.jpg 09:29:01 chipmunk and squirrel as quite close and belong to the same family 09:29:59 any other proposals? 09:30:59 Current proposals are 1. house mouse, 2. squirrel, 3, shrike (4. blazar?), aren't these? 09:31:15 Forget the squirrel :( 09:31:42 Each project mascot must be distinct in stylized cartoon illustrations. Therefore, if one team chooses a “squirrel,” another team can’t choose a "chipmunk.” 09:32:02 Found this on http://lists.openstack.org/pipermail/defcore-committee/2016-July/001151.html 09:32:10 Unless these rules don't apply anymore 09:32:32 Wow 09:32:58 Although if it looks different enough 09:33:01 maybe it could work 09:33:53 priteau_: the mouse should hold some cheese 09:34:15 https://vignette2.wikia.nocookie.net/tomandjerry/images/2/23/Jerry_with_a_cheese.jpg/revision/latest?cb=20161207032215 09:34:45 s/should/could/ 09:34:57 Anyway, I'll send the list to the openstack-dev. If you come to mind other idea, please replay it. 09:35:31 thanks 09:35:47 Looks like the guidelines have changed a bit since this mailing list post 09:35:52 Now the mascot page says: 09:35:53 Mascots are assigned are on a first-come, first-served basis. For example, if a cat has already been selected by one project, then another project interested in a cat-like mascot should choose a significantly different type of cat, such as a leopard or tiger. 09:35:59 It's important discussion for us ;-) 09:36:07 So significantly different species are OK 09:36:40 So we have 4 candidates (including blazar)? 09:36:55 yes. 09:37:06 yes. include the blazar. 09:37:40 What is shrike? The bird? https://en.wikipedia.org/wiki/Shrike 09:38:10 priteau_: was wondering the same. there should be a page with explanations behind each mascot. 09:38:14 priteau_: yes. The bird reserves their foods on tree for winter. 09:38:53 I didn't know about that 09:39:10 birds are also quite territorial animals, so that would also match well 09:39:35 The problem with a bird like that is that it will be hard to identify when in cartoon form 09:40:02 It's not very distinctive from any other small bird 09:40:11 priteau_ : yes, and there are already few birds in the list 09:40:23 #link https://www.openstack.org/assets/software/mascots/OS-Mascot-Key.pdf 09:40:53 yes, and the existing birds are very distinctive (parrot, raven, swift, pigeon…) 09:43:07 priteau_: yea... right. 09:43:45 But final decision, duplication or etc, is done by the Foundation. IMO, it's okay to listing it. 09:44:43 other comments about mascot? 09:44:54 if nothing, move on to next. 09:45:48 #topic AOB 09:46:34 Does someone have something to share/discuss/talk? 09:47:02 I have 09:47:40 About the state-machine blueprint, I've changed states graphs. 09:48:31 I care backward compatibility for the reservation state machine 09:49:15 Please check if it is acceptable for Chameleon, priteau 09:50:09 hiro-kobayashi: Thanks. I haven't had time to review it yet, but will do ASAP 09:50:21 priteau: thanks! 09:50:36 After we make a consensus on the state-machine blueprint, I will also work on the resource monitoring blueprint 09:50:49 thanks hiro 09:51:20 And I've been working on the dashboard blueprint: https://review.openstack.org/#/q/status:open+project:openstack/blazar-dashboard+branch:master+topic:bp/host-operation-with-dashboard 09:52:13 Zuul vote -1 but it does not block merging. So, please review them ;-) 09:52:57 I think Zuul -1 can be solved by https://review.openstack.org/#/c/509078/ 09:53:30 hiro-kobayashi: Thanks for the great works! 09:53:43 But there is no way to recheck Zuul check. recheck comment triggers only Jenkins job (Zuul v2). 09:53:51 I'll review it ASAP. 09:53:57 masahito: thanks! 09:54:19 2 more patches may come for the dashboard blueprint ;-) 09:54:25 That's all from me 09:55:29 hiro-kobayashi: thanks again. If you need any help, please let us know. 09:55:39 OK 09:55:55 last 5 mins 09:56:56 if nothing, finish the meeting earlier than as usual. 09:58:33 okay. thanks and bye to everyone 09:58:43 Thanks all, good bye! 09:58:50 thanks all, bye 09:58:52 Thanks. bye! 09:58:58 #endmeeting