08:00:11 #startmeeting watcher 08:00:12 Meeting started Wed Jun 5 08:00:11 2019 UTC and is due to finish in 60 minutes. The chair is licanwei. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:15 The meeting name has been set to 'watcher' 08:00:59 say sum12: are you here? 08:01:19 Agenda for today: https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#06.2F05.2F2019 08:01:39 sum12 is in the channel but not sure if afk or not 08:01:44 #topic Announcements 08:02:21 This week is Train-1 milestone. 08:03:02 We have completed 5 BPs 08:03:31 Thank you Dantalion and chenker! 08:03:50 Thank you too. 08:04:06 thanks everyone :) 08:04:13 #topic Review 08:04:16 haha.. 08:04:52 https://review.opendev.org/#/c/661245/ Add Placement helper needs review 08:05:30 will have time to do reviews next week, placement helper is first priority (I am currently abroad) 08:05:45 Dantalion: thanks~ 08:06:16 where you are 08:06:28 Back home in the Netherlands~ 08:07:30 https://review.opendev.org/#/c/661121/ Optimize hypervisor API calls needs review 08:08:47 https://review.opendev.org/#/c/662089/ Optimize NovaHelper.get_compute_node_by_hostname needs review 08:09:12 I think these patch are good. 08:09:34 They are Matt's commits 08:10:04 I'll review again~ 08:10:34 https://review.opendev.org/#/c/661976/ Move datasource query_retry into baseclass needs review 08:11:09 I need to update this patch to ensure backwards compatibility 08:11:32 ok 08:13:27 today i want to talk about instane.name and node.name 08:14:37 Dantalion: about backwards compatibility, 08:16:36 https://review.opendev.org/#/c/656622/ 08:17:30 this merged patch has backwards compatibility problem 08:18:26 Other than with strategy or datasource plugins? 08:19:06 I think since the interface changed compatibility problems are impossible to prevent but happy to hear ideas 08:20:08 Dantalion: we changed the audit parameter, about basic strategy , change node to compute_node , for example 08:21:15 In Stein, some tempest tests failed, https://review.opendev.org/#/c/662045/ 08:21:19 Ah yes that is true we could do that it can be both node and compute_node and stop support node in next release. I think compute_node is more clear but should support both for at least a while 08:22:04 Dantalion: yeh, I agree with you 08:22:18 Do we want spec for this or should I just do it? 08:22:49 Dantalion: I don't think we need a spec, it's clear :) 08:23:03 Okaj i'll start next week 08:23:18 Dantalion: nice~ 08:23:49 https://review.opendev.org/#/c/649341/ Grafana proxy datasource to retrieve metrics needs new patch 08:24:15 I need to rebase this to use new exception names 08:24:31 Dantalion: ok 08:24:52 https://review.opendev.org/#/c/661301/ Implement the configuration for Grafana datasource needs new patch 08:25:25 I will add documentation as separate patch since it will be quite long to explain everything clearly 08:25:41 good idea 08:25:48 Dantalion: thanks 08:26:02 https://review.opendev.org/#/c/660393/ Improve DevStack documentation to support metrics] needs review 08:27:22 I'll review again 08:28:00 last one:https://review.opendev.org/#/c/660011/ Add resource_name in action input parameter field needs new patch 08:29:28 I will try to review next week 08:29:59 after we have decided on humand_id / name 08:30:34 We need to define how to use humand_id /instance name/host name ... 08:30:56 # topic Discussion 08:31:22 I think instance name is clear than human_id 08:31:29 Now let's discuss again 08:32:08 In Watcher data model, compute node and instance all have human_id field 08:32:24 example: 08:32:43 08:32:58 08:33:34 Now computenode' s human_id is null 08:33:54 and compute node also has a hostname field 08:34:23 I think we should define how to use these fields 08:35:18 I think uuid and hostname is enough. 08:35:34 remove human_id ,use hostname and instance name 08:35:53 or remove hostname and instance name, use human_id 08:35:56 ? 08:36:18 Now human_id is unused 08:37:16 instance human_id is how we identify virtual machines for Grafana 08:38:07 Why not using uuid? 08:38:08 Dantalion: Why don't you use vm uuid? 08:39:05 Because storing hostname as identifier allows to query dns server to get ip without having to use openstack clients for example 08:39:39 Which identifier to use for storing is not something I can control either is managed by other team 08:40:10 but keep in mind what identifier to use is configurable and will differ in every deployment this is simply how CERN has done it. 08:41:00 Dantalion: Is VM name OK? 08:43:14 let me see novaclient's code 08:44:38 https://github.com/openstack/python-novaclient/blob/2595bac2294ce05e389eaab6636977963d5fc66c/novaclient/base.py#L152 08:44:59 Dantalion: Because instance human_id comes from nova client, maybe we plan to get data directely from nova API 08:46:15 so human_id = instance_data['human_id'] ? 08:46:32 just like that placement helper 08:47:24 Or do you mean if data from model is missing just use uuid to get object from nova API? 08:47:50 human_id = instance_data['name'] 08:48:48 Dantalion: No, I mean maybe we can get rid of novaclient, get data directely from nova API 08:50:17 What is the benefit of using nova API directly? 08:52:38 Now, when watcher create datamodel , instance's human_id actually is instance.name, but when updating datamodel, instance'human_id uses ['display_name'] 08:53:47 Dantalion: If we use nova API directly, we will don't need Matt to change novaclient for optimization 08:53:59 We need to confirm that their values are currently the same field 08:54:24 I think we need novaclient. 08:54:30 Ah I see, can someone show example difference between instance.name and display_name as I have no access to an openstack 08:54:59 Let me have a try. 08:56:03 Dantalion: need to confirm the difference~ 08:57:21 I'll confirm after the meeting 08:57:52 Okaj yes I agree that the update should use same value as used when creating the data model. 08:58:16 okaj 08:58:17 Dantalion: yes 08:58:31 i will confirm this after our meeting 08:58:42 We need to be careful to keep value that looks like hostname from compute_node in instance data model in the example: tempest-testexecutestrategies-server-1452042406 08:59:01 this will be used at CERN to identify virtual machines in Grafana databases 08:59:22 Ok 08:59:27 But I do not mind if the attribute is renamed 08:59:29 thank you all 08:59:38 I'll end the meeting 08:59:39 Yes thank you 08:59:47 ok 09:00:03 #endmeeting