06:02:21 #startmeeting masakari 06:02:21 Meeting started Tue Aug 3 06:02:21 2021 UTC and is due to finish in 60 minutes. The chair is yoctozepto. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:02:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 06:02:21 The meeting name has been set to 'masakari' 06:02:26 o/ 06:02:33 o/ 06:03:59 o/ 06:05:53 o/ 06:06:58 ok, let's start 06:07:01 with the agenda 06:07:18 * CI status 06:07:18 * Important pending reviews (important bugfixes, backports) 06:07:19 * Next release planning 06:07:19 * Open discussion 06:07:23 #topic CI status 06:08:05 all systems green :-) 06:09:28 #topic Important pending reviews (important bugfixes, backports) 06:10:00 still https://review.opendev.org/c/openstack/masakari/+/796732 06:10:44 please remember to review patches :-) 06:11:24 #topic Next release planning 06:11:31 I have seen movements in the specs 06:11:36 but I did not have time to review them again 06:11:47 though I am happy we are progressing 06:13:59 me too. 06:16:25 should we discuss anything today? 06:16:33 I will be reviewing specs this week again 06:16:50 I have the evacuations and consul monitoring in my plans 06:17:10 yes 06:18:28 I reviewed some patchs about 'add-docs' https://review.opendev.org/q/topic:%2522add-docs%2522+(status:open) 06:19:01 ah, yeah; have you incorporated the other patches in the one at the top? 06:19:27 ah, no, I see the change 06:20:05 I reviewed them without comments. 06:20:36 I think they are ok to be merged. 06:21:05 yeah, you applied the comments; thanks; will check and yeah, likely merge 06:21:55 from my side, I would like to add hostmonitor by consul based on them. 06:22:24 makes sense; we should definitely start with it documented :-) 06:23:44 I will try to update them. If you feel it is ok, please merge them. 06:24:20 ok, I will mark them for a review today 06:24:23 thanks 06:24:28 Could we talk about this spec? spec for vm evacuations for host recovery | https://review.opendev.org/c/openstack/masakari-specs/+/789432 06:25:23 ok 06:26:04 I still don't think it is necessary to include migration_uuid. We already have source_host and dest_host. 06:26:31 The migration_uuid cannot be obtained directly. 06:28:04 I mean, we don't have to include it upfront; it could be useful for audit purposes; we can include it once we make nova able to return it 06:28:58 regarding the source host - it is stored at the notification level (all instances from one notification will have the same source host - so it is cleaner not to repeat this information) 06:29:12 I don't think it is necessary to wait for nova api changing, because I don't know how long to pause. 06:29:14 we can have a very efficient join in SQL 06:29:46 suzhengwei: yes, we will not wait for nova; you can skip the migration_uuid for now 06:30:04 I hope the migration_uuid situation is clear now ;-) 06:32:12 so, to rephrase: ignore the migration_uuid for now, don't add it if you don't want to 06:32:18 now for the other two fields 06:32:30 source_host - I already wrote a line about it above 06:32:42 I suggest we move ahead with the spec description. Once nova support the new api, we modify our code. 06:33:49 yes 06:37:50 shenxinxin: do you agree regarding the source_host? 06:38:02 (I am missing your answer to my reasoning) 06:38:39 In our application, we just care about where the instance ha from and to. just the hostname is enough. 06:39:58 What I mean is that adding source_host is more intuitive, and more efficient when querying evacuation records.:) 06:42:13 It doesn't care about other things about the Host, likes type/reserved/control_attr. 06:43:57 yeah, it does not, but duplication is usually a bad thing 06:44:38 ok, I don't care that much, let's go with source_host, but perhaps name it "source_host_name" to be clear what it is 06:45:00 now about the dest_host - what do we need it for? to verify whether the instance has not been re-migrated? 06:45:26 yes. 06:45:30 ok 06:45:37 then the same thing applies, let's append _name 06:46:07 how about source_hostname and dest_hostname? 06:46:53 suzhengwei: fine by me; both variants look good 06:47:04 though source_host_name 06:47:09 makes it easier to create 06:47:14 source_host_whatever 06:47:21 ok 06:47:42 We need to store this instance from and to in the evacuation record, also for migrate back. for dest_host field. 06:47:45 I left two nit comments on the spec review as well 06:48:51 also look at the two comments on PS2, commit message: https://review.opendev.org/c/openstack/masakari-specs/+/789432/2 06:49:09 Ok,thanks. 06:49:17 I think those two name fixes, two nits to fix and the commit message 06:49:27 and I will be approving this 06:49:45 I saw the code has progressed as well so it might be quick to implement :-) and then we focus on consul, great 06:51:34 Ok, I will try to update it these days. 06:51:38 thanks 06:51:58 anything else about Xena today? 06:52:09 not form me 06:52:30 not from me. 06:52:42 not from me. 06:53:52 ok 06:53:56 #topic Open discussion 06:54:05 anything else at all? :D 06:55:57 ok, thank you for meeting today 06:56:03 #endmeeting