13:00:16 #startmeeting watcher 13:00:17 Meeting started Wed Aug 30 13:00:16 2017 UTC and is due to finish in 60 minutes. The chair is alexchadin. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:20 The meeting name has been set to 'watcher' 13:00:23 o/ 13:00:30 hi 13:00:40 hi 13:00:53 today we have the following agenda: https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#08.2F30.2F2017 13:00:55 hi 13:01:20 #topic Announcements 13:01:27 Watcher has reached final Pike release with 1.4.1 version 13:01:43 Congratulations, team! 13:02:01 great! 13:02:05 We've done a lot of works! 13:02:18 morning 13:02:19 hi 13:02:21 Hi 13:02:27 hi sballe_ aspiers Yumeng__ 13:02:42 hi 13:02:55 sballe_: we have reached 1.4.1 version along with final Pike release 13:03:17 fantastic news! congrats to the team 13:03:42 We should set priorities to Watcher blueprints especially for new ones. 13:04:49 I propose to dedicate today's meeting to review some blueprints and review other blueprints during the next meetings 13:05:12 +1 13:05:15 do you agree? 13:05:20 ok 13:05:28 agree 13:05:50 alexchadin : +1. Could you send the link about meeting agenda? I am out of my office using my phone 13:05:56 +1 13:06:03 Yumeng__: https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#08.2F30.2F2017 13:06:09 Thanks! 13:06:22 #topic Blueprint Review 13:06:38 workload-characterization-grammar #link https://blueprints.launchpad.net/watcher/+spec/workload-characterization-grammar 13:07:03 I see that spec is very well detailed and ready to be implemented 13:07:41 yes it is and I believe Walmart had started it 13:08:17 I do not have any helpers this quarter :-( 13:08:50 if somebody wants to take it over feel free to do so 13:09:06 sballe_: what the status of Chris Spencer? I remember you've said some time ago that he might be able to work on watcher a little bit 13:09:38 sballe_: but it seems that he is on other project 13:10:01 Chris has moved on to another porject at Intel and so has Pru 13:11:55 I suggest to set medium priority on it until we find helper for you 13:12:53 proposal, we review the spec again. because it is so long, it is not easy to take over the work. 13:14:25 suzhengwei: feel free to review it, although it's pretty clear to understand and to implement 13:14:54 sballe_: what do you think about priority? 13:15:04 sounds good Medium or Low 13:15:49 sballe_: I propose Medium to improve chances to see it implemented in Queens 13:16:12 👍🏻 13:16:31 fine 13:16:36 move on 13:16:42 event-driven-optimization-based #link https://blueprints.launchpad.net/watcher/+spec/event-driven-optimization-based 13:18:31 Jean-Emile proposed good use case that let watcher to react on particular events and make some decisions based on them 13:20:10 there should be some sort of manager, that will be listening to the events from wide range of publishers and launch audit with specified options 13:21:37 do someone want to try write a spec for it? 13:22:29 I don't exclude that this spec may be split up 13:22:56 This is a big job. we need seperate it into pieces. 13:23:01 agreed 13:24:02 write your propositions about separating it on bp's whiteboard 13:24:50 suzhengwei: can you provide your point of view about it? 13:26:22 ok, I have marked it. But now i am foucs to the usage problem. 13:26:36 I'll try too 13:26:40 I will review it if free 13:26:52 good 13:27:05 neutron-model-integration #link https://blueprints.launchpad.net/watcher/+spec/neutron-model-integration 13:27:14 I propose to move it to low priority 13:27:24 +1 13:27:27 +1 13:28:18 this topic is too big to start working on it now 13:28:34 i am not sure use case now. 13:29:02 hidekazu: we will need to discuss it additionally 13:29:21 notifications-actionplan-cancel #link https://blueprints.launchpad.net/watcher/+spec/notifications-actionplan-cancel 13:29:42 adisky__: I see that everything is good with this bp and spec is about to be merged 13:30:35 alexchadin: yes, it will be completed in queens 13:30:38 adisky__: I will set series goal to the Queens 13:30:40 great 13:30:53 queens-1? 13:31:04 alexchadin: +1 13:32:41 vm-migration-ordering #link https://blueprints.launchpad.net/watcher/+spec/vm-migration-ordering 13:34:52 aspiers: what is your plan about this bp? 13:35:27 it seems a guidance. some part of it is implementted in watcher. 13:35:57 does all dependent blueprint implemented? 13:36:45 I don't have a clear plan yet 13:36:58 at least watcher-planner-selector is not implemented yet, if dependency tree is true. 13:36:58 adisky__: planner-selector hasn't been implemented yet 13:36:58 except that the Python code for the ordering is already written 13:37:00 Not sure. 13:37:33 actually in the Atlanta PTG we discussed this 13:37:48 and at the time, there were no strategies which required this kind of ordering 13:37:57 alexchadin: then as per the tree, we need to implement planner selector first 13:38:48 adisky__: yes, that probably makes sense 13:38:48 in some strategies, the migrations has consider such problem. 13:39:11 I would like to propose a new strategy for VM consolidation, which would require ordering 13:39:28 but I still need to write a blueprint for that 13:39:37 Ok, I'll left it with medium priority 13:40:21 aspiers: we've already discussed it, it would be interesting 13:40:44 I can explain more details at the PTG also 13:41:35 I won't be at PTG, unfortunately 13:41:51 aspiers: we can make a call in hangouts, for example 13:41:55 sure 13:42:03 good 13:42:43 watcher-planner-selector #link https://blueprints.launchpad.net/watcher/+spec/watcher-planner-selector 13:44:22 I'd like to take this BP cause I worked on workload_stabilization planner 13:45:46 extend-node-status #link https://blueprints.launchpad.net/watcher/+spec/extend-node-status 13:46:25 I have update it today. 13:47:24 usage problem. 13:48:43 suzhengwei: so your main idea is to let other services know that watcher disabled or enabled particular compute node, right? 13:49:01 yes. 13:49:33 al least, we should known which nodes is disabled not by watcher. 13:50:34 we do nothing to such nodes. 13:50:36 ok, I'll tag it to Queens 13:51:01 good 13:51:21 add-name-for-audit-in-watcher-dashboard #link https://blueprints.launchpad.net/watcher/+spec/add-name-for-audit-in-watcher-dashboard 13:52:00 Yumeng__: do you plan to work on it during the Queens cycle? 13:52:16 alexchadin : yes. This is part of bp: add name for audit 13:53:23 Yumeng__: won't you mind if I set low priority on it? 13:53:28 alexchadin: low is fine 13:53:33 great 13:53:43 This is a easy and small one 13:55:05 api-validation #link https://blueprints.launchpad.net/watcher/+spec/api-validation 13:56:39 adisky__: let's discuss it a little bit later cause it's uncertainly to me for now 13:57:17 alexchadin: ok, i will start working on it, only after discussion 13:57:29 adisky__: +1 13:57:43 well, seems that's today 13:57:52 that's it* 13:58:14 thank you for attending :) 13:58:27 and for your contribution to the Watcher 13:58:50 have a nice day and bye! 13:58:53 bye 13:58:54 bye 13:58:56 bye 13:59:24 bye 13:59:55 #endmeeting