09:01:32 #startmeeting blazar 09:01:33 Meeting started Tue Jun 5 09:01:32 2018 UTC and is due to finish in 60 minutes. The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:01:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:01:36 The meeting name has been set to 'blazar' 09:01:42 o/ 09:01:53 o/ 09:01:55 o/ 09:02:03 #topic RollCall 09:02:16 hi, blazar folks, nice to meet you. 09:02:19 tetsuro, hiro-kobayashi, priteau: hello 09:02:31 Hello tetsuro, welcome! 09:02:46 i think we have talked did we/ 09:03:00 im tetsuro from NTT 09:03:11 tetsuro: Hello 09:03:16 priteau: tetsuro is a placement guy who I talked at the last meeting :-) 09:03:38 im working on placement especially nested stuff. 09:03:51 hi all! 09:03:59 bertys: hi 09:03:59 hi 09:04:03 today's agenda is 09:04:04 hi! 09:04:13 1. rocky-2 milestone 09:04:17 2. gate failure 09:04:24 3. AOB 09:05:13 tetsuro: Welcome to blazar project. we're planning to use placementAPI. I'm really happy to see you in the meeting. 09:05:41 masahito: thanks, too 09:05:51 OK, let's move on to first topic 09:05:59 #topic rocky-2 milestone 09:06:22 I pushed some patches for r-2 milestone. 09:06:33 https://review.openstack.org/#/c/572269/ 09:06:38 https://review.openstack.org/#/c/572270/ 09:06:42 https://review.openstack.org/#/c/572271/ 09:06:47 https://review.openstack.org/#/c/572272/ 09:07:21 Once the patches have been merged, we'll pass the r2 milestone 09:07:54 Thanks! 09:08:07 I used 1.1.0 tag for blazarclient, blazar-nova, blazar-dashboard following other projects. 09:08:41 I think flavors-extra-specs and multi-freepools patches are ready to be merged. 09:09:19 Are there patches that you still want to merge before tagging rocky-2? 09:10:17 How about https://review.openstack.org/#/c/566802/ , https://review.openstack.org/#/c/564138/ ? 09:10:21 I don't have a specific patches to be merged before r2 09:11:16 I'm neutral to merge the two before r2 or after r2. 09:11:30 hiro-kobayashi: I think I can review the first one quickly after the call, since the remaining comments were minor 09:11:45 priteau: thanks! 09:12:11 But including them in rocky-2 would require masahito to push updated versions of his release patches 09:12:25 yes. 09:12:25 Oh, I got it. 09:12:49 (since they refer to a specific Git SHA) 09:13:17 The due date is 7 June. Don't need to be harry up. 09:13:40 meaning I'm okay to merge it before "r3" 09:13:51 OK. I don't have a strong preference. Let's take the easiest way. 09:14:42 Speaking of updating my release patch, I want to talk a bit about next topic. 09:14:43 Unless we have operators who are ready to deploy and test r2, there is no real benefit in including those patches in this release 09:15:05 Agree 09:15:47 masahito: I am OK to move to the next agenda item 09:16:22 #topic gate failure 09:17:05 I noticed the devstack scenario test in the gate starts to fail 09:18:06 The reason it fails looks unexpected context key in RPC. 09:18:13 http://logs.openstack.org/34/571634/2/check/blazar-devstack-dsvm-py35/7ed339d/logs/screen-blazar-m.txt.gz#_Jun_05_06_18_57_188544 09:19:40 masahito: Could this be caused by a change in oslo.messaging? 09:19:56 I don't see any reference to client_timeout in our code 09:20:00 I'm checking it with the patch https://review.openstack.org/#/c/572290/ and if it's true, I plan to avoid to use the latest oslo.messaging. 09:21:37 The latest oslo.messaging 6.3.0 was released in last week. And the gate failure happens after the release. 09:22:27 Thank you for investigating the problem 09:22:58 My plan is just avoiding 6.3.0 for blazar r2 release, then fixing the problem before r3. 09:23:13 Sounds good 09:25:54 Agreed 09:26:13 #topic AOB 09:26:22 less topics today. 09:26:33 Does someone have something to share/discuss? 09:26:48 I have one topic 09:27:06 Does anyone (plan to) work on the cleaning-time-allowance blueprint? 09:27:24 If not, I plan to work on it. 09:28:16 Thanks hiro-kobayashi. I don't think I will have time to work on it soon. 09:28:20 I don't work for it now. 09:28:24 priteau: does ChameleonCloud has related patch for Ironic support? 09:28:47 Oh, timing error... 09:28:57 hiro-kobayashi: No, as we don't use the Ironic cleaning feature on Chameleon, yet 09:29:18 OK. Then, I will work on it :-) 09:29:54 hiro-kobayashi: thanks for taking it! 09:31:00 I don't have another topic today. 09:32:09 tetsuro: Would you like to self-introduce? :-) 09:32:19 well, 09:32:58 these days I'm 09:33:27 working on placement, but I'm also working on DPDK mainly. 09:33:58 and now im curious and willing to look into blazar world also, so 09:34:22 please help me if you can so that I can help. 09:34:42 thats about it...is it enaough?:) 09:34:56 tetsuro: thanks and welcome! 09:35:19 Sure. If you have any question, feel free to ask us. we can help you :-) 09:35:24 brtys: thanks too. 09:35:40 masahito: thanks. 09:35:52 tetsuro: One major objective for Blazar is to move to use the placement API at some point. 09:36:12 Currently we are using a combination of Nova host aggregates and scheduler filters 09:36:59 gocha. I'll try to help. 09:37:12 tetsuro: Here is a placement support plan: https://etherpad.openstack.org/p/blazar-placement-design . It is still under discussion. 09:37:47 cool. 09:38:19 It's great if we could co-work on it. 09:38:22 We're happy that you would feedback it from Nova (Placement) perspective. 09:39:12 will have a look on that 09:39:49 OK. another topic? if nothing we can finish today's meeting early. 09:40:19 I wanted to mention briefly Neutron support in Blazar 09:40:53 In Chameleon we are interested, not only for reserving floating IPs, but especially for reserving segmentation IDs for provider networks (VLANs) 09:41:25 If time allows, I will try to work on a spec this month that incorporates our design from Dublin 09:42:19 priteau: Sounds Nice! Could you do both floatingIP reservation and segmentation IDs? 09:42:32 Yes, I think the mechanism will be the same 09:42:54 got it. 09:43:20 It's really nice to have a real use case! 09:44:27 Do you also have a plan to write a spec about resource usage API? If less time, I can take over this. 09:45:07 masahito: I am afraid I won't have much time to work on this. 09:45:20 I can do a review if you're happy to write the spec 09:45:26 No problem. 09:45:32 I 09:46:09 I'll start to work on the spec after fixing gate failure :-) 09:46:21 thanks! 09:46:58 Thank you 09:47:20 Thank you, too. 09:47:52 That's a team and OSS activities ;-) 09:49:02 okay, then let's finish the meeting early and back to review and write a spec! 09:49:21 thanks all. 09:49:32 bye 09:49:43 #endmeeting