09:00:29 #startmeeting blazar 09:00:29 Meeting started Tue Mar 28 09:00:29 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:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:32 The meeting name has been set to 'blazar' 09:00:48 #topic RollCall 09:00:58 o/ 09:01:17 o/ 09:01:41 I heard r-mibu and pierre can't join this meeting. 09:01:49 hiro-kobayashi: tejaswi: hello 09:01:58 hello 09:02:05 hello 09:02:31 Today's agenda is... 09:02:44 1. gate job 09:02:47 2. AOB 09:03:04 anything else? (less topics) 09:03:14 Nothing from my side 09:03:51 I want to check if anyone is working on the horizon plug-in for Blazar ? 09:04:29 tejaswi: ok, let's discuss it first. 09:04:43 #topic Horizon Plugin 09:05:19 priteau said he has that in Chameleon cloud. 09:05:37 I did not find the code in chameleon github. 09:05:42 And he showed me the GUI at the Barcelona summit. 09:05:44 let me check one more time 09:05:52 hi there. sorry for being late 09:06:10 Hi GeraldK! 09:06:24 GeraldK: hi 09:06:38 tejaswi: yes, please. Do you have a Horizon plugin, too? 09:06:46 GeraldK: we're talking about Horizon plugin. 09:07:18 tejaswi: do you know the link to Chamereon's github? 09:07:43 hiro-kobayashi: No, I do not have horizon plugin. 09:07:45 https://github.com/ChameleonCloud/blazar 09:09:50 I find fork of Horizon repo in Chameleon 09:09:51 https://github.com/ChameleonCloud/horizon 09:10:32 Thanks masahito! 09:10:58 Should the Horizon plugin be separated from blazar repo? 09:11:01 It has a branch named 'chameleon'. so it might have code we want :) 09:11:21 hiro-kobayashi: depends on the case. 09:11:34 Got it 09:12:31 IMO, we're in early stage. so placing the plugin in blazar repo is easy to do maintenance. 09:12:55 +1 09:13:25 tejaswi: Are you planning to own Horizon plugin blueprint? 09:13:59 hiro-kobayashi: Yes, I would like to work on the horizon plugin. 09:14:33 if you plan to or start to work on the bp, please assigne yourself in launchpad. 09:14:48 https://blueprints.launchpad.net/blazar/+spec/climate-dashboard 09:14:52 hiro-kobayashi: Should we ask Pierre for the existing code ? I did not find the code in github 09:15:15 masahito: ok 09:15:33 tejaswi: Thanks for owning it! Yes, its better to ask Pierre 09:16:07 hiro-kobayashi: ok. I will check with Pierre. 09:16:26 tejaswi: thanks for taking the bp! 09:16:52 tejaswi: And you may find it here: https://github.com/ChameleonCloud/horizon/tree/chameleon 09:17:42 I heard he is in US this week. so openstack-dev ML or somewhere seems to be better. 09:18:29 hiro-kobayashi: I've checked the repo. However, it does not have blazar plugin. Anyways, I will ask Pierre 09:18:57 tejaswi: OK. Pierre will help you anyway 09:20:03 hiro-kobayashi: ok. thanks 09:20:07 any comments for the plugin? 09:20:42 #topic gate job 09:21:23 Now I'm thinking change tempest test from non-voting to voting job. 09:21:45 additionally, I'd like to add python3.x job as no- 09:21:55 as non-voting job. 09:22:03 +1 09:22:15 any comments? 09:23:38 ok, then I'll activate the gate jobs. 09:23:50 okay for me 09:23:59 #topic AOB 09:24:16 we have less topics today. 09:24:40 does someone have topics to discuss? 09:24:48 SPEC for on_end is the only BP spec we have so far? 09:25:18 I will review the latest patch set today. 09:25:47 GeraldK: Yes, only one SPEC for now. Thanks a lot for your review! 09:26:27 on the new instance reservation BP spec, can we have some discussion via ML first on the different options how this could be realized? 09:26:59 it's good idea. 09:27:28 Tejaswi, can you also check with your colleagues, e.g. Arun on this topic. AFAIK they have good background on it. 09:27:56 I'm drafting the feature in my mind now :-) 09:28:06 :-) 09:28:19 GeraldK: ok. I will check with Arun 09:28:28 brain storming sounds nice. 09:29:02 we can also setup Etherpad if you prefer to ML 09:29:30 masahito: do you want to take the lead on this discussion? 09:29:43 GeraldK: Sounds good! I think using Etherpad is more efficient 09:29:44 sure, I planned to do it. 09:29:56 +1 09:30:08 +1 thanks masahito 09:30:37 #action start a discussion about instance reservation (masa) 09:30:41 for the other topics like "support atomic transactions" do you think we also need discussion on Etherpad first or is the way forward more clear? 09:31:11 IMO, it's be ok to start from spec. 09:31:25 +1 09:31:40 +1 09:32:09 In term of "atomic transactions", we have 2 context. 1. transaction in API request. 2. transaction in blazar's internal task. 09:32:32 okay. 09:32:39 but both could be resolved by same way. 09:33:28 another topic: what about the status of the reported bugs? 09:33:41 I see that for https://bugs.launchpad.net/blazar/+bug/1404190 we have two patches under review 09:33:41 Launchpad bug 1404190 in Blazar "No validation for --physical-reservation arguments of lease-create command" [High,Confirmed] - Assigned to Hiroaki Kobayashi (hiro-kobayashi) 09:34:55 It's ready to be merged. So please review them 09:35:13 https://review.openstack.org/#/c/140306/ 09:35:17 https://review.openstack.org/#/c/143044/ 09:35:19 okay. 09:35:25 this patch is in my review queue. I'll check it later. 09:35:38 Thanks! 09:36:37 no more topics from my side. 09:37:04 I have one topic 09:37:28 We should decide when to move to Blazar API v2 09:38:31 Supporting both v1 and v2 needs a lot work when changing APIs 09:38:46 like on-end-option blueprint 09:38:47 hiro-kobayashi: do you have demands to have v2? 09:39:27 When changing APIs, v2 is easy in terms of documentation 09:40:00 So, I think it's better focusing on v2 and deprecate v1 in the near future 09:40:58 IMO, changing API version should happen when API 'schema' is changed. 09:41:29 For implementation side, don't need to change the version. 09:41:51 I agree but we have to maintain two APIs for now. 09:42:02 but AFAIK some parameters of lease lacks in v1, right? 09:42:42 masahito: right. I think "before_end" capability is not supported in v1. 09:43:35 So, I plan to support "before_end" capability only for v2. How do you think? 09:45:09 If it means changing an action type in API, I agree. If it means changing an action in config, I don't agree. 09:46:00 It means in API, not in config 09:46:34 I think it's ok. 09:46:36 Even if you use v1, you can change the before_end action by config 09:47:23 hiro-kobayashi: could you listing tasks to make v2 API official? 09:47:34 ok 09:47:37 1. documentation 09:47:47 2. blazar client supports 09:47:56 3. gate job 09:48:40 IIRC, we need to prepare the above things to make v2 official. 09:49:05 Yes, I agree 09:49:32 1 is ready. 2 has once proposed but abandoned. 3 should be added. 09:50:19 last 10 mins 09:51:37 if nothing, we can end the meeting early 09:51:51 nothing from my side 09:52:36 Thanks, all! 09:52:52 #endmeeting