09:00:35 #startmeeting blazar 09:00:36 Meeting started Tue Feb 12 09:00:35 2019 UTC and is due to finish in 60 minutes. The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:39 The meeting name has been set to 'blazar' 09:01:16 #topic Roll call 09:01:32 o/ 09:01:41 Hi masahito 09:02:12 hi 09:02:23 Hi tetsuro 09:03:04 #topic stein-3 milestone 09:03:53 We're getting closer to the stein-3 milestone 09:04:13 I've been working on refreshing some bug fixes that were implemented for Chameleon 09:05:20 Looks like today I may be able to review the new floating IP patches and placement work 09:06:38 masahito: I suppose you won't have time to work on "reservation candidate API" in this cycle? 09:07:20 priteau: right. sorry, no much time to work for it. 09:07:59 No problem. Allocation API was much more important IMHO. 09:08:53 masahito: I left some questions on the floating IP spec. https://review.openstack.org/#/c/609302/ 09:09:43 tetsuro: thanks! I'll check it later. 09:11:34 Thanks tetsuro for your work on fixing https://bugs.launchpad.net/blazar/+bug/1814594 09:11:35 Launchpad bug 1814594 in Blazar "Failure to create a host" [High,In progress] - Assigned to Tetsuro Nakamura (tetsuro0907) 09:12:20 This was a random find really. I usually deploy DevStack on CentOS7, but that day used Ubuntu16.04 which had hostnames configured differently. 09:12:42 Good catch, thanks a lot 09:12:43 masahito: tetsuro's patches are at https://review.openstack.org/#/q/status:open+project:openstack/blazar+branch:master+topic:bug/1814594 09:14:46 I'll check it. thanks tetsuro 09:15:46 Anything else to discuss for stein-3? 09:18:06 The network is unstable.. sorry. 09:18:55 No worries 09:18:58 Let's move to AOB 09:19:02 #topic AOB 09:19:24 Anything special to share today? 09:20:12 nop 09:21:23 May I ask tetsuro's patch if nothing? 09:21:48 sure 09:24:28 The patch and its commit message looks good to me. Is it needed any upgrading script that changes host_name to hypervisor_name in DB? 09:24:50 Or does the problem only happen in placement support? 09:24:56 Ah 09:25:01 good question. 09:25:08 Wait a moment plez 09:26:24 masahito: Both values of `hypervisor_hostname` and `service_name` are already in the database for each compute host 09:26:33 We're just getting another value to pass to placement 09:26:41 No DB changes are required 09:26:42 Yes, that's true 09:26:57 priteau is right, thanks 09:27:29 Okay, thanks. 09:31:15 Chameleon has been using a similar approach because it uses an experimental patch that allows host aggregates to be linked with hypervisor hostnames 09:32:24 Good to know 09:32:39 Any other questions? 09:32:52 https://review.openstack.org/#/q/topic:bug/1813252 also needs more eyes. 09:33:13 Thanks for the remidner 09:34:23 Not from me any more 09:35:48 Nothing from my side. 09:36:34 Thank you for joining today. 09:36:45 Thanks 09:36:53 Bye! 09:36:54 thanks 09:36:56 #endmeeting