14:00:04 #startmeeting watcher 14:00:05 Meeting started Wed Mar 2 14:00:04 2016 UTC and is due to finish in 60 minutes. The chair is acabot_. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:08 hi 14:00:08 The meeting name has been set to 'watcher' 14:00:25 hi 14:00:33 o/ 14:00:42 welcome ptklechat ;-) 14:00:59 hi 14:01:04 thx ! Hello all ! 14:01:17 hi 14:01:22 hi 14:01:33 our agenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#03.2F02.2F2016 14:01:44 o/ 14:01:48 o/ 14:01:55 o/ 14:02:07 #topic Annoucements 14:02:25 o/ 14:02:28 #info Mitaka-3 release is expected tomorrow 14:02:46 I can say that we are far from the schedule we planned at the mid-cycle ;-) 14:03:17 acabot_ what are the exact dates? 14:03:32 3rd of March 14:03:43 #link https://launchpad.net/watcher/+milestone/mitaka-3 14:03:48 acabot_: I will be on the plane all day tomorrow so I can spend that time doing reviews 14:04:11 most of our BPs have specs but implementation is not started yet 14:04:48 sballe_: there are a lot of open reviews on documentation 14:04:59 FYI, for Mitaka release schedule #link http://releases.openstack.org/mitaka/schedule.html 14:05:19 ok I will reviews doc stuff 14:05:34 Ditto 14:06:05 so the question is, should we now target Newton-1 which is pretty far away, or we create intermediate milestones before the Austin summit ? 14:06:42 Newton-1 will be around mid-june 14:06:52 I vote intermediate 14:07:02 +1 14:07:12 +1 14:07:17 +1 14:07:23 +1 14:07:25 +2 14:07:27 +1 for an rc1 14:07:30 Intermed would be nice. 14:07:54 ok si I will create an RC1 mid-march and probably an RC2 mid-april 14:08:02 +1 14:08:09 that makes a lot of sense to me 14:08:09 re: scoring-module: I'm finally setup with devstack, started working on BP and implementation in parallel. but given the schedule, it will be really hard to have both in the next 2 weeks or so. voting for intermediate milestone 14:08:17 Great! 14:08:29 and +1 on irc1 14:09:28 #action acabot create an RC1 mid-march and probably an RC2 mid-april 14:09:44 #action jwcroppe sballe_ review doc on Watcher 14:10:00 any other annoucement ? 14:10:46 #topic Review Action Items 14:11:39 #info some specs have been merged this week "Added specification for ZHAW load consolidation", "optimization threshold spec" & "Define the scope of an Audit as pool of resources" 14:12:12 we can now start working on implemented them, I know that vtech & seanmurphy already started implementing 14:12:24 and brunograz 14:12:50 gzhai2: did you already start implementing the optimization threshold ? 14:12:50 we expect to submit something for review today 14:13:01 not yet. start on workload balance migration strategy spec 14:13:01 seanmurphy : great thx 14:13:31 acabot_: I have been out so didn't check. Is Junjie's spec mereged yet 14:13:35 gzhai2 : you mean are you replacing junjie on this ? 14:13:55 I'll do the coding. 14:14:13 sballe_: not yet but I would like to do it asap 14:14:32 acabot_: Yeah I agree 14:14:45 hi, sorry to be late 14:14:54 gzhai2: ok so what about optimization threshold ? Should I unprioritize it ? 14:15:21 acabot_: we will also use optimization thresholds in our algorithm. I drafted the idea here - https://github.com/icclab/watcher/commit/3b9c4652dd784e38affa9f5887351b6b09141de8 14:15:57 will probably hardcode them at first, but it can be adjusted later on... 14:16:00 gzhai2: What happened to Junjie? 14:16:26 vtech: thx did you had a look at the spec https://github.com/openstack/watcher-specs/blob/master/specs/mitaka/approved/optimization-threshold.rst 14:16:28 i thought we discussed that having the optimization threshold was going to be important to display at the summit. i know we're behind schedule but i think we should still push for that 14:16:50 sballe_: Junjie has some other tasks? You can check. 14:17:13 gzhai2: check with Nishi? 14:17:18 tpeoples: I agree we definitely need to pass parameters to a strategy for the summit 14:17:23 ok let's take it off line 14:18:03 acabot_: I haven't, but will check it out. 14:18:37 #action vtech look at the spec https://github.com/openstack/watcher-specs/blob/master/specs/mitaka/approved/optimization-threshold.rst not implemented yet 14:18:57 and efficacy indicator affect it. 14:19:21 sballe_ : Intel has 2 very important BPs related to the demo in Austin, do you think you can make them ? 14:19:53 acabot_: I am checking with Nishi to see what is going on 14:20:05 sballe_: ok thx 14:20:13 I'll let you know as soon as I hear back from her 14:20:54 #action sballe_ check with nishi whats going on regarding the BPs https://blueprints.launchpad.net/watcher/+spec/workload-balance-migration-strategy & https://blueprints.launchpad.net/watcher/+spec/optimization-threshold 14:22:41 https://review.openstack.org/#/c/276586/ is waiting for reviews 14:23:05 #action acabot jwcroppe sballe_ review https://review.openstack.org/#/c/276586/ to merge asap 14:23:37 vmahe could you provide a new PS for https://review.openstack.org/#/c/283449/ ? 14:24:10 after gzhai2 comments 14:24:38 yes, I'm on it but I need to double check one point with jed56 14:25:00 #action vmahe provide a new PS for https://review.openstack.org/#/c/286153/ 14:25:11 sorry 14:25:22 #action vmahe provide a new PS for https://review.openstack.org/#/c/283449/ 14:26:01 alexstav submitted a spec of their strategy Add Overload standard deviation strategy spec 14:26:11 #link https://review.openstack.org/#/c/286153/ 14:26:34 but I dont think he is on IRC right now to tell us if it is open for reviews 14:27:29 pwd 14:27:40 #info tpeoples submitted a WIP on "Cluster model objects wrapper" and is looking for feedback on https://review.openstack.org/#/c/287019/ 14:28:03 yes, i want to get feedback to ensure the spec captures what was discussed at the midcycle 14:28:17 before i run off and do implementation since it's going to be a decent amount of work 14:28:18 ok 14:28:48 jwcroppe: edleafe: can you guys take a look at that when you have free time please? 14:29:02 #action acabot jwcroppe sballe_ jed56 edleafe review https://review.openstack.org/#/c/287019/ for a first feedback 14:29:32 tpeoples: I'll try, but it's crunch time in nova land due to M-3 closing today 14:30:05 edleafe: no worries i understand, even in the next few days is ok if you can 14:30:38 we need specs for "Provide a scoring module for Watcher" and tkaczynski is working on it 14:30:58 yes, full steam on it 14:31:09 and I'm working on specs for https://blueprints.launchpad.net/watcher/+spec/select-destinations-filter 14:31:28 #action tkaczynski submit a spec for https://blueprints.launchpad.net/watcher/+spec/scoring-module 14:31:43 #action acabot submit a spec for https://blueprints.launchpad.net/watcher/+spec/select-destinations-filter 14:31:59 #action acabot_ submit a spec for https://blueprints.launchpad.net/watcher/+spec/select-destinations-filter 14:32:12 thats is for specs 14:32:21 on Watcher code 14:33:42 #info vincentfrancoise has pushed implementation of https://blueprints.launchpad.net/watcher/+spec/db-purge-engine 14:33:42 and is looking for reviewers 14:33:42 especially for doc updates 14:33:42 vincentfrancoise: any specific review you want to mention ? 14:34:18 well I missed a work item 14:34:30 so I'll put this one in WIP 14:34:40 though it won't take much time to finish it 14:35:32 ok, i will review that 14:36:03 vincentfrancoise: any way to get a list of open doc reviews on gerrit ? 14:36:03 #action tpeoples review code for https://blueprints.launchpad.net/watcher/+spec/db-purge-engine 14:37:33 #info a couple of bugs have been fixed 14:38:02 nothing new on python-watcherclient 14:38:38 #info launchpad for watcher-dashboard has been set up with Mitaka milestones 14:39:18 we will probably need a new BP to align the dashboard features with the python-watcherclient ones 14:40:03 acabot_: BP or wishlist Bugs 14:40:41 dtardivel: could this fit in a whishlist bug ? 14:40:48 wishlist sorry 14:40:58 acabot_: vincentfrancoise and I will have a look on missing feature on dashboard 14:41:27 #action dtardivel vincentfrancoise will have a look on missing feature on dashboard 14:41:27 acabot_: regarding your doc reviews question: use the following query to see open reviews that touch a doc file: https://review.openstack.org/#/q/status:open+project:openstack/watcher+file:doc 14:41:51 tpeoples: great ! thx 14:42:15 acabot_: If it is just a missing button, we can open a wishlist bug no ? 14:42:17 #action sballe_ jwcroppe acabot review open doc updates https://review.openstack.org/#/q/status:open+project:openstack/watcher+file:doc 14:42:31 dtardivel: seems reasonable to me 14:42:41 dtardivel: right I thaught it was much more than that :-) 14:43:22 #topic Blueprint/Bug Review and Discussion 14:44:01 #info we realized that adding actions implies a code modification in the planner and this should be improved 14:44:28 question: what's the process to submit a new BP for review? 14:44:55 I submitted a BP for this BTW #link https://blueprints.launchpad.net/watcher/+spec/generic-planner 14:45:02 tkaczynski: are you talking about BP or specs ? 14:45:14 sorry, spec for existing BP 14:45:27 vincentfrancoise: ok great thx 14:45:45 (scoring-module in mind) 14:46:11 tkaczynski: check watcher-specs.git 14:46:30 tkaczynski: there is a quick doc here to submit our first patch https://wiki.openstack.org/wiki/Watcher/Contributing 14:47:13 tkaczynski: https://github.com/openstack/watcher-specs is the repo that holds the specs. https://github.com/openstack/watcher-specs/blob/master/specs/mitaka/approved/mitaka-template.rst is the example spec file 14:47:55 yes, I've seen the watcher-specs. repo. thanks acabot_ and tpeoples 14:48:21 tkaczynski : do not hesitate to ping me on IRC if you are in trouble with git review ;-) 14:48:24 I wasn't sure how to do reviews, there's a tool for that, cool 14:48:47 tkaczynski: yes we use gerrit for specs and code 14:48:53 acabot_ thanks :) 14:49:19 #topic Open Discussion 14:49:41 acabot_: talking about BP, in Launchpad, some BP are not updated with URL of their spec. We should have a look on them ... 14:50:11 dtardivel: yes I try to do it every time a spec is merged but I did not this week.. 14:51:02 setup package name is python-watcher instead of watcher, why? 14:51:32 gzhai2: watcher was already in use on pypi 14:51:45 as we are in open discussion, I do not really understand why we had a big slow down right after the mid-cycle 14:52:33 was it because we tried to put too much BPs in the Mitaka-3 serie ? 14:52:35 from my side - devstack setup stopped me. I had tons of issues which were resolved only few days ago 14:53:28 now playing catch up with spec and implementation 14:53:56 no, that wasn't the issue for me acabot_. internal work that came up unfortunately. was just bad timing to happen right after the midcycle 14:54:28 when do summit talks that were accepted get released? 14:55:04 around March 10th 14:55:15 right after the early bird tickets ends 14:55:38 Hi Guys ! Just introducing.. I am a new member and interested in this project. At Walmart we have similar challenges for resource optimization and we would like to start playing with watcher and have some interesting use cases. Also, looking forward to contribute. 14:56:04 welcome hvprash 14:56:05 hvprash : you are more than welcome ! 14:56:11 Welcome 14:56:26 thx, this is my first meeting and have been reading the docs. 14:56:34 hi hvprash :) 14:56:36 hvprash : did you already looked at Watcher code ? 14:57:00 hvprash: ok great, we have a complete devstack setup now 14:57:16 hvprash: it should be quite easy to set up ;-) 14:57:25 ;-) 14:57:41 acobot_, may have some question on setting it up initially ? whats the best way to ask help and get acquainted ? 14:58:00 hvprash: please use IRC #openstack-watcher 14:58:10 there is always someone here to help you 14:58:14 awesome ! thx a lot 14:58:38 hvprash : do you plan to be in Austin ? 14:58:42 yes 14:58:54 great, we will have meetings there 14:59:05 would like to meet you all and share our problems and challenges and how we can help 14:59:31 looks great 14:59:37 so time is over 14:59:38 hvprash: look forward to meeting you 14:59:42 thank you everyone 14:59:45 thanks 14:59:49 thanks 14:59:49 talk to you later 14:59:49 thx everyone 14:59:50 thanks acabot_ 14:59:52 bye 14:59:53 bye 14:59:55 bye 14:59:57 bye 15:00:01 bye 15:00:02 #endmeeting