09:00:12 #startmeeting blazar 09:00:13 Meeting started Tue Jun 27 09:00:12 2017 UTC and is due to finish in 60 minutes. The chair is hiro-kobayashi. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:16 The meeting name has been set to 'blazar' 09:00:20 #chair priteau 09:00:20 Current chairs: hiro-kobayashi priteau 09:00:30 #topic RollCall 09:00:33 o/ 09:00:39 o/ 09:00:49 masahito and h_ito cannot attend today 09:01:10 OK. Let's start our meeting! 09:01:20 Today's agenda is: 09:01:28 1. Horizon plugin 09:01:32 2. status update 09:01:35 3. AOB 09:01:38 anything else? 09:02:13 #topic Horizon plugin 09:02:42 priteau has shared a horizon plugin used in the ChameleonCloud last week 09:02:54 Thank you very much, priteau :-) 09:03:16 No problem 09:03:35 I've retrieved essentials and tested in my env, and it works! 09:03:55 It looks fine! 09:04:04 Some of the functionality such as lease calendar doesn't have the necessary API support, so it is reading from the blazar database directly 09:04:14 We can't use this method 09:04:38 It complicates the deployment 09:04:51 IMO, we can use it at first 09:04:52 But basic operations for create / update / delete should work fine 09:05:51 I think we can allow horizon to access blazar DB 09:06:12 for now 09:06:21 How do you think? 09:07:21 I am not a fan of the idea. In some deployments it might be impossible, e.g. Horizon is deployed in an environment that can't reach the database due to IP filtering 09:08:03 Maybe if we keep this part experimental 09:09:16 Then, how about including this part and notice users that it's experimental 09:09:28 ? 09:09:56 It might be acceptable. We should ask masahito's opinion when he's back 09:10:09 OK 09:10:51 And I want to discuss which repo should the dashboard hosted 09:11:05 The lease calendar was really built for Chameleon, and it provides a lot more data to users which operators may not want to give 09:11:20 e.g. it shows which hypervisor are allocated to leases 09:12:04 priteau: right. so hat should be updated in the future 09:13:09 hiro-kobayashi: no strong opinion. blazar-dashboard may be one option 09:13:17 about repo, I think it's better to create a new repo 09:13:49 hiro-kobayashi: Also, the calendar part wasn't written by me so there might be licensing issues. We will need to review this before it can be integrated. 09:13:56 bertys_: agree. Many other project have *-dashboard repos 09:14:22 priteau: Got it. That's very important. 09:14:48 +1 for creating a new repo. In Chameleon we've kept it in python-blazarclient/contrib/horizon, but it's confusing 09:15:11 It's only there because the original code contribution from Pablo Andres Fuente put it there 09:15:12 ok for me 09:15:34 OK. then, I'll create a new repo after checking masahito's opinion 09:15:44 hiro-kobayashi: So in the style of https://github.com/openstack/sahara-dashboard or https://github.com/openstack/cloudkitty-dashboard 09:16:01 Yes 09:17:10 That looks good to me. We should check if there are Horizon guidelines for this kind of repo 09:18:17 I've read Horizon plugin guides, but couldn't find the repo rules 09:18:35 I don't see any either. Maybe there aren't any 09:18:47 That's how to create a dashboard: https://docs.openstack.org/developer/horizon/contributor/tutorials/dashboard.html 09:19:09 Other *-dashboard are same style. So I'll follow them 09:19:24 hiro-kobayashi: thanks 09:19:45 And I've also been adding test code. After completing that, I will push the patch 09:20:35 if the licensing issues are not clear at that time, I'll exclude the calendar part 09:21:28 I think that would be better for now. The developer has left so it may take me some time to track down legal issues. 09:22:17 priteau: okay 09:22:53 I appreciate it! 09:23:20 Anything else about Horizon? 09:24:11 #topic status updates 09:24:29 Do you have any updates to share here? 09:25:38 All of my updates are about Horizon, which have been already shared 09:26:17 Sorry, got disconnected 09:26:30 priteau: np :) 09:26:38 current topic is status updates 09:26:40 I have reviewed all our internal Chameleon patches to Blazar and selected several of them for submitting upstream. 09:27:02 Thanks! 09:27:03 I am busy adapting them for master, writing tests, and submitting 09:27:12 I have done that for two already, more to go. 09:28:11 That would be a heavy work. Please tell us if you need any help 09:28:59 We don't have that many actually. Some of my patches fixing bugs were already duplicated by Masahito or you. 09:29:16 e.g. terminating instances when leases edn 09:30:16 priteau_: right 09:30:40 any other updates? 09:31:13 #topic AOB 09:31:40 If there is no AOB, we can finish todays meeting 09:31:52 I won't be able to join the meeting next week 09:32:08 It's 4th of July, so US independence day 09:32:09 priteau_: OK 09:33:40 OK. that's all for today's meeting! Thanks! 09:33:54 #endmeeting