09:01:58 #startmeeting blazar 09:01:59 Meeting started Tue May 15 09:01:58 2018 UTC and is due to finish in 60 minutes. The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:02:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:02:03 The meeting name has been set to 'blazar' 09:02:12 hi blazar folks 09:02:19 #topic RollCall 09:02:35 o/ 09:03:07 priteau: hi 09:03:17 Today's agenda is 09:03:29 1. the Forum session 09:03:34 2. Next weekly meeting 09:03:37 3. AOB 09:03:41 anything else? 09:04:54 #topic the Forum session 09:05:34 The forum session I proposed is accepted and scheduled on Monday in the Vancouver summit. 09:05:37 https://wiki.openstack.org/wiki/Forum/Vancouver2018 09:05:49 hi 09:05:51 Great news! 09:06:04 I created etherpad for the session. Feel free to write down your idea. 09:06:12 https://etherpad.openstack.org/p/YVR18-forum-reservation-requirements 09:06:14 hiro-kobayashi: hi 09:06:34 The page now has only the copy of my proposal. 09:06:54 The parallel tracks don't have conflicting topics as well, that's good. 09:07:08 right. 09:08:13 Additionally, I found Preemptive instances has one session. I'll join the session. 09:08:16 [1350-1430] Preemptible instances - the way forward - https://etherpad.openstack.org/p/YVR18-pre-emptible-instances 09:08:37 It could be interesting to join the placement sessions too 09:08:51 [1510-1550] Building the path to extracting Placement from Nova https://etherpad.openstack.org/p/YVR-placement-extraction 09:08:58 [1620-1700] Planning to use Placement in Cinder https://etherpad.openstack.org/p/YVR-cinder-placement 09:09:13 (on Monday) 09:09:30 Thanks for sharing session info 09:09:41 The preemptible instances session is on Tuesday 09:10:04 it's better at least one of us join above sessions 09:11:18 I hope the cinder one helps us to make an idea using Placement in Blazar. 09:11:51 And also how to integrate non-compute services with Blazar 09:12:09 hiro-kobayashi and I will be in the summit. We could join the sessions. 09:12:12 priteau: right. 09:12:16 If Cinder moves to using placement, maybe there will be a generic way we can support any service using placement 09:14:01 yes. Anyway, lots of forum sessions are in the summit. 09:16:00 another comment? 09:17:45 That's all from me 09:17:58 me too 09:18:14 got it. let's move on to next 09:18:21 #topic Next weekly meeting 09:18:50 Next week is the summit week as you know. 09:19:04 If possible, I'd like to skip next meeting. 09:20:12 I'm at the summit, too. I'm okay to skip it. 09:20:44 That works for me too as I wouldn't be able to join anyway. 09:21:01 I will be in Chicago next Tuesday. 09:21:30 got it. let's skip next meeting. 09:21:49 priteau: Safe trip to Chicago. 09:22:17 #topic AOB 09:22:29 less topics today. 09:22:40 Does someone have something to share/discuss? 09:23:31 I reviewed masahito's multi-freepools patch today: https://review.openstack.org/#/c/564138/ 09:23:59 I posted one comment but now I have another question. 09:24:08 thanks 09:24:47 it uses 'resource_properties' for instance reservation but 'hypervisor_properties' for host reservation 09:25:32 Which is better, hypervisor_properties or resource_properties? 09:26:12 hypervisor_properties are dynamically imported from Nova when the operator calls add-host 09:26:29 resource_properties query extra_capabilities 09:27:10 Actually, either hypervisor_properties or resource_properties works for the host reservation. 09:27:14 Shouldn't it be hypervisor_properties everywhere? 09:28:13 but for the meaning of az as priteau mentioned, I choose hypervisor_properties. 09:28:45 The az info is imported from Nova. The hypervisor_properties looks good to me. 09:28:55 Got it. Current implementation calls Nova hypervisors API and get az when the add-host is called. So, it is a hypervisor properties. make sense. 09:30:21 We should check whether that 09:30:27 information is kept up to date 09:30:44 i.e. if you add-host to Blazar, then change the AZ in nova, is it reflected in Blazar? 09:30:46 I am not sure it is 09:31:31 We should investigate it. 09:32:16 Current implementation doesn't apply the change. 09:33:01 A polling of notification listener is needed for such capability, right? 09:33:07 s/of/or 09:33:21 IIRC, It's described in the spec. 09:33:23 Or a periodic query of Nova 09:33:58 Or re-add the host to Blazar. 09:34:37 The operator will be prone to forget 09:34:45 I think Blazar should automate it 09:35:58 From operators point of view, I think changing az is rare operation. So I think priority of automation is not so high. 09:36:41 Anyway, changing of az can cause reallocations :-( 09:37:05 IIRC, the az info is managed by nova.conf. At least, the host is need to be reboot. 09:38:30 I'll update the patch set with some change. 09:40:03 masahit: for handling change of az? 09:40:46 hiro-kobayashi: refrecting your comment and add comments or releasenote. 09:40:57 masahito: OK. thanks! 09:41:16 looks nothing more to talk. 09:41:29 let's finish the meeting early. 09:41:53 thanks all. bye! 09:42:04 thanks! bye 09:42:18 Safe trip to Vancouver or Chicago! 09:42:24 #endmeeting