09:00:33 #startmeeting blazar 09:00:34 Meeting started Tue Jul 3 09:00:33 2018 UTC and is due to finish in 60 minutes. The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:37 The meeting name has been set to 'blazar' 09:01:04 #topic RollCall 09:01:07 o/ 09:01:15 o/ 09:01:19 Today's agenda is 09:01:20 o/ 09:01:20 I'm sorry but I will leave in about 30mins 09:01:27 1. Placement support 09:01:33 2. PTG schedule 09:01:35 3. AOB 09:01:44 hiro-kobayashi, priteau, tetsuro: hi 09:01:51 Hi everyone 09:01:58 hello! 09:02:03 hiro-kobayashi: got it. Let's start from your topic. 09:02:07 ok 09:02:14 anything else? 09:02:53 #topic Placement API support 09:02:58 I have one topic to discuss about the Placement spec: https://review.openstack.org/#/c/576343/ 09:03:30 hiro-kobayashi added the item. Let's start from this. 09:03:35 It is about the ID of the host. 09:04:01 To access the resource provider of the compute host, the UUID of the host is neccesary 09:04:50 The host UUID is returned by ver.2.53 and later 09:05:03 See https://developer.openstack.org/api-ref/compute/#show-hypervisor-details in detail. 09:05:36 So, if blazar uses ~2.52 version of Compute API, the id is integer. 09:06:15 When was 2.53 released? 09:06:16 So, I added a new column 'resource_provider_uuid' into the computehosts table 09:06:48 This is for keeping existing host ids. 09:07:01 It's part of the Pike release version 9.1.0 09:07:31 Alternative is not to add the 'resource_provider_uuid' and update the existing host's ids to the string UUID in a migration script. 09:07:45 priteau: yes. 09:08:07 priteau: 2.53 is pike maximum 09:08:15 priteu: In ChameleonCloud, Blazar uses the integer host id, right? 09:08:25 https://docs.openstack.org/nova/latest/reference/api-microversion-history.html 09:08:33 thanks tetsuro 09:09:05 hiro-kobayashi: yes. We are running Ocata's Nova. 09:09:21 priteau: OK. thanks! 09:09:33 Today, I come to think we can use hostname as an identifier and we can get the uuid from the placement using the hostname 09:09:39 But I don't want the fact that we run an older release to complicate the code 09:10:11 hiro-kobayashi: Actually, we create Blazar hosts based on the hypervisor hostname. The lookup of the Nova ID is automatic. 09:10:35 tetsuro: Do you mean the 'resource_provider_uuid' column is not needed? 09:10:53 I mean that is not needed, yes. 09:11:40 hiro-kobayashi: My question is latest Hypervisor list API supports query parameter, right? 09:11:58 tetsuro: make sense. Use the hostname to access the resource provider. 09:12:38 Looks like hostname is identical, so we can use that hostname to get the uuid asking to placement every time 09:12:51 masahito: yes, it seems to. 09:13:06 Looking up from hostname is the most admin-friendly way to do it. 09:14:05 OK. Now it's clear. Remove the 'resource_provider_uuid' and use the hostname instead. Then, the version problem is solved. 09:14:30 Agree? 09:14:44 Agreed. 09:14:49 agreed. 09:14:51 Agreed. 09:15:01 Thanks. I'll update the spec. 09:15:17 1 more thing to share about the Placement spec. 09:15:40 I changed the primary-assignee to tetsuro 09:15:52 that's good with me. 09:15:53 tetsuro has already started implementation and I think it's better. 09:16:09 np 09:16:19 Thanks tetsuro! And I added you in co-authored-by 09:16:42 Thanks! 09:17:18 Thanks tetsuro and hiro-kobayashi! 09:17:30 Thanks a lot! 09:17:36 I'll update the Launchpad assignee, too. 09:17:42 My pleasure ;-) 09:17:52 I already see lots of patch in gerrit. Great works! 09:18:31 That's all about Placement API support 09:19:20 hiro-kobayashi: Thanks. 09:19:29 anything else? 09:20:03 no 09:20:11 #topic PTG schedule 09:20:48 Thierry shared the proposed schedule of the Denver PTG. 09:20:50 Thierry 09:20:58 http://lists.openstack.org/pipermail/openstack-dev/2018-June/131881.html 09:21:19 Blazar is scheduled on Monday and Tuesday. 09:21:44 Does someone have any conflict or problem at the schedule? 09:22:26 nope, I can join 09:22:32 Scientific SIG is also scheduled on Monday. It is one of the schedule conflict. 09:22:36 There's the Scientific SIG at the same time, but I don't know yet if I will attend anyway. 09:23:45 OK. looks no big schedule conflict. 09:24:39 Having Nova separate is the most important, so that we can attend placement API discussions 09:24:39 any comments for the schedule? 09:25:31 Yes. I guess that's why the Blazar is scheduled on Mon. and Tue. 09:25:44 Cool! 09:26:55 #topic AOB 09:27:20 Does someone have topic to share or discuss? 09:28:00 I do 09:28:18 priteau: okay, you have a floor :-) 09:29:42 I am starting a new job at StackHPC today. I will still be involved in Chameleon for some time. 09:30:02 And in Blazar of course :-) 09:30:13 Oh, Congrats! 09:30:23 Congrats!! 09:31:00 Thanks! I have a new email address that I will share with you, though my uchicago.edu address is still working until mid-August. 09:31:17 What is your primary role or mission? 09:32:23 crossing my fingers to your new job 09:32:38 Congrats! 09:33:49 hiro-kobayashi: My role is Senior Technical Lead. StackHPC offers consulting so I may be working for various clients. 09:34:06 Hopefully Blazar will be an important part of it :-) 09:34:46 priteau: Nice role! I hope so :-) 09:36:30 I hope so. We're waiting nice feedbacks from user side and developer side ;-) 09:37:34 I have one item to hear your idea. 09:37:42 I'm sorry but I gotta go. thank you and good bye all 09:37:58 hiro-kobayashi: thanks 09:38:12 TC team asked me whether this team or projct has any problem. 09:38:46 They told they would support the issue. 09:39:55 IMO, complex document links is one of our problem. 09:40:21 any other ideas to ask them? 09:40:59 What is the problem with document links? 09:41:03 s/ to ask them?/ to ask them for support?/ 09:42:16 I means docs.openstac.org or openstack site have lots of link to specific project but the configuration is very complex. 09:42:46 So it's hard to update all the link correctly. 09:44:30 I plan to tell which repoes we should update? 09:45:06 For example, the project navigator doesn't show Blazar project even though we're an official but I can't find the repo for the page. 09:45:31 I see. I think some things on the web page may be managed outside of Git repos. 09:46:02 right. 09:47:41 anything else? if nothing, we can finish early this meeting. 09:48:11 nothing from me. 09:49:20 Nothing else from me. 09:49:21 OK, let's finish the meeting. 09:49:21 thanks all! Next weekly meeting has review meeting, too. 09:49:31 Thanks 09:49:35 bye. 09:49:35 #endmeeting