08:00:48 #startmeeting Watcher 08:00:49 Meeting started Wed May 22 08:00:48 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:50 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:52 The meeting name has been set to 'watcher' 08:01:03 Hello 08:01:30 Dantalion: hi 08:01:36 Dantalion: how are you 08:01:47 chenke: I am good thanks for asking 08:02:35 i am glad to be here to talking about watcher. 08:02:51 #topic review action items 08:03:23 https://review.opendev.org/659099 Spec for Grafana proxy datasource needs review 08:04:14 ok 08:04:29 Tokens do not expire in Grafana, I will post this on the spec after meeting 08:04:33 chenke: good~ 08:04:54 Dantalion: thanks 08:06:47 Dantalion: does Watcher depend on some Grafana libs? 08:07:09 No Grafana exposes rest-api 08:07:26 Dantalion: OK~ 08:07:34 next 08:07:44 https://review.opendev.org/659008 Spec for support-keystoneclient-option.rst needs review 08:08:34 I'll review this spec 08:08:57 https://review.opendev.org/656448 Add Placement helper needs review 08:10:03 licanwei: i will review it after this meetting 08:10:22 chenke: thanks 08:10:46 https://review.opendev.org/656622 formal datasource interface implementation needs review 08:11:27 i had reviewed this commit "formal datasource interface implementation " 08:11:50 Overall, it looks good to me. 08:12:29 Dantalion: I'll review it again, 08:12:49 Okaj thanks 08:13:11 it's too many code~ 08:13:37 https://review.opendev.org/660132 remove unused cliutils.py file as osc_lib is used needs review 08:14:55 review +1 08:14:56 Does this file cliutils.py never be used before? 08:15:37 https://review.opendev.org/660295 Remove redundant key 'hostname' needs review 08:16:40 review +1 08:17:08 https://review.opendev.org/#/c/657944/ Audit API supports new force option needs review 08:18:21 ok, i will review it . 08:18:43 the docs about force option i had reviewed. 08:20:12 Dantalion: your comment :'this might lead to a wrong actionplan if the data models are different? 08:20:50 Dantalion: I don't understand your mean 08:21:30 licanwei: in approved spec it is specified that forcing new audit while one is ongoing might have consequences for actionplan 08:21:50 i am also confused with this. 08:22:24 last sentence of problem description: https://specs.openstack.org/openstack/watcher-specs/specs/train/approved/add-force-field-to-audit.html 08:23:33 I think we should add the same warning about wrong actionplan to the release note 08:24:18 i agree it. 08:24:28 Dantalion: yes,If the audit has the same datamodel ,maybe creating wrong actionplan 08:24:46 Dantalion: I'll update the releasenote 08:24:52 Dantalion: thanks 08:24:58 licanwei: Yes thank you 08:25:30 https://review.opendev.org/657211 Add force field to Audit needs review 08:27:38 This looks good to me, nit: is to do boolean type same as other openstack services but the wfield will already ensure a default value so it is not mandatory 08:29:30 Before the actionplan start, datamodel has been changed. I think this question need to be discussed. 08:30:04 Dantalion: object field type? 08:30:21 i will read the code after our meeting. 08:33:13 next 08:33:22 https://review.opendev.org/658571 Cleanup doc dependencies needs review 08:34:29 review +1 08:34:54 https://review.opendev.org/#/c/659688/ Optimize NovaClusterDataModelCollector.add_instance_node needs review 08:35:47 review +1 08:35:55 I will look at this one 08:36:38 I am looking at this commit. 08:37:26 #topic Discussion 08:37:39 this patch is releated to this :https://review.opendev.org/#/c/659886/ 08:37:46 whether we need to rename the field 'human_id' of the data model? 08:38:26 So human_id and hostname are becoming one in nova? 08:38:50 novaclient add this option human_id 08:39:35 Dantalion: no hostname in data model 08:40:28 but if we use cmd "nova show server_id" ,there is not "human_id" 08:40:44 maybe 'name' is better than human_id 08:40:48 only have "name" option 08:41:11 I think data model names should reflect nova names 08:41:29 so name and hostname instead of humand_id 08:41:57 name and hostname can be different right? 08:41:58 yes. 08:42:03 no 08:42:29 if name is always equal to hostname than maybe just have one datamodel attribute not two 08:42:58 yes 08:43:35 For instances the name is usually not a hostname right? 08:43:37 Dantalion: agree 08:43:57 so i want to delete hostname, because it maybe confused with the name of the node. 08:44:45 I think naming the attribute 'name' and removing the second attribute is the good option 08:44:54 now , in this patch, i use human_id to get instance.name. https://review.opendev.org/#/c/660011/4/watcher/decision_engine/strategy/strategies/base.py 08:45:32 I agree. 08:45:58 Dantalion: we should use name or hostname instead of human_id 08:46:23 hostname might give impression it is FQDN while it is not that is why I think name is better 08:46:54 what's the mean about FQDN? 08:47:02 Fully Qualified Domain Name 08:47:07 Dantalion: agree 08:47:10 example: google.com 08:47:53 oh, i understand it. 08:49:04 I'm no other question 08:49:18 I will try split up formal datasource 08:49:25 but will have lots of Depends-On 08:50:09 i think future patch can split it. 08:50:16 now it's ok. 08:53:22 thank you all ,i'll end the meeting 08:53:28 I have no other questions. 08:53:38 thank you until next time 08:53:40 :) 08:53:48 licanwei: thanks too. 08:54:08 Dantalion: bye~ 08:54:12 Dantalion: see you :) 08:54:17 licanwei: bye~ 08:54:19 #endmeeting