14:00:49 #startmeeting watcher 14:00:50 Meeting started Wed Jan 27 14:00:49 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:52 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:54 The meeting name has been set to 'watcher' 14:00:58 hi 14:01:01 o/ 14:01:04 o/ 14:01:07 o/ 14:01:08 hi 14:01:13 hello 14:01:15 hi 14:01:16 hi guys 14:01:17 \o 14:01:35 our agenda #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#01.2F27.2F2016 14:01:35 hi 14:01:44 hello 14:02:03 #topic Announcements 14:02:26 #info mitaka-2 version of Watcher has been released on monday 14:02:51 #info with 9 BPs implemented and 37 bugs fixed 14:03:08 thank you everyone for this great job 14:03:38 we now have an idea of how many BPs we can manage during a serie 14:03:59 * edleafe rushes in late... 14:04:06 #info target is now mitaka-3 scheduled for 3rd of March 14:04:34 #info gzhai is now INTEL core contrib on Watcher 14:04:42 any other announcement ? 14:04:47 acabot: +1 14:05:31 #topic Review Actions Items 14:05:57 seanmurphy has shared specs for ZHAW algo https://review.openstack.org/#/c/271028/ 14:06:05 and is looking for reviews 14:06:22 thanks acabot 14:06:25 I'll review 14:06:33 did you guys start implementing ? 14:06:36 thanks jwcroppe 14:06:42 not yet but soon 14:06:43 same here 14:06:48 have been v busy with other commitments 14:06:52 #action jwcroppe review https://review.openstack.org/#/c/271028/ 14:06:54 into the next week or so 14:07:05 but have been looking at the basic_consolidation example 14:07:07 #action sballe review https://review.openstack.org/#/c/271028/ 14:07:26 seanmurphy you can maybe improve basic_consolidation implementation 14:07:33 vtech seanmurphy : is the doc clear enough ? 14:07:48 jed56 - we can certainly try 14:07:50 do not hesitate to give us feedback to improve the doc 14:08:08 it seem that what you want to do is near 14:08:28 yes jed56 suggest that you improve basic consolidation instead of building a new strategy 14:09:04 ok - that could work 14:09:06 yeah seems like the two are trying to do the same thing 14:09:14 will take a closer look at the spec 14:09:20 so - it prob looks like we should have offline discussion on it 14:09:24 and perhaps it could be an option 14:09:50 ok lets talk on irc before starting implementing a new strategy 14:09:56 if you prefer we can remove the current implementation she was here only for test 14:10:46 ok 14:10:50 all good with us 14:10:56 ok 14:11:03 seanmurphy: that migth be faster for yu too since you have all the plumbing in place already 14:11:22 sballe: yep - good point 14:11:48 IMO It would be nice to keep both and see how they performs 14:12:25 that would imply having the efficacy indicator then 14:12:44 vtech: in this case do not hesitate to get the plumbing from basic_consolidation 14:13:07 yes it could be a good way to test the efficacy indicator 14:13:22 when it will be implemented 14:13:56 vmahe is working on specs for https://blueprints.launchpad.net/watcher/+spec/define-the-audit-scope 14:14:04 what the ETA on the efficacy indicator 14:14:19 oh you answred my questn :) 14:14:47 sballe: the review is open but I need to add work items... I planned to do it this morning but ran out of time, I hope to have it by EOW 14:15:08 no rush... I know how time slips away 14:15:28 cool 14:15:31 we need a status for https://blueprints.launchpad.net/watcher/+spec/watcher-overload-underload but I dont think alexstav is here 14:16:24 a patch from jed56 (https://review.openstack.org/#/c/270642/) needs review 14:16:52 #action tpeoples review https://review.openstack.org/#/c/270642/ 14:17:21 #info jed56 added Voluptuous lib to validate action parameters 14:17:47 #info vincentfrancoise is adding tempest scenarios 14:18:22 #info tpeoples added global requirements 14:18:44 and needs review on https://review.openstack.org/#/c/269310/ https://review.openstack.org/#/c/269296/ 14:18:56 we need to get that merged before i can propose watcher to openstack/requirements.. +1 14:19:25 can we merge this by EOW ? 14:19:57 +2 14:20:02 I will take a look 14:20:05 today 14:20:05 thanks jed56 14:20:05 #action dtardivel review https://review.openstack.org/#/c/269310/ https://review.openstack.org/#/c/269296/ 14:20:21 #action jed56 review https://review.openstack.org/#/c/269310/ https://review.openstack.org/#/c/269296/ 14:20:21 welcome :) 14:20:52 tpeoples: there is an issue with olso.messaging 4.0.0 : we habe error on watcher.conf.sample generation 14:21:32 ok, can you give me details on the review? 14:21:33 tpeoples: no error with 3.1.0 previous version 14:21:49 tpeoples: yes, of course 14:21:55 thanks 14:22:10 #action dtardivel give details about oslo.messaging 4.0.0 error 14:22:12 tpeoples : regarding https://review.openstack.org/#/c/270039/ I moved it to mitaka-3 as we need to do more testing 14:22:43 +1 14:22:49 +1 14:23:02 #info reviews are needed for https://review.openstack.org/#/c/270039/ 14:23:11 +q 14:23:14 +1 14:24:05 acabot: review ongoing in our side 14:24:14 ok 14:24:43 #info tpeoples shared devstack plugin on openstack-dev ML 14:25:07 any other action items you want to share ? 14:25:46 #topic Blueprint/Bug Review and Discussion 14:25:47 tpeoples: what about your last bug about devstack doc #link https://bugs.launchpad.net/watcher/+bug/1538291 14:25:49 Launchpad bug 1538291 in watcher "Improve DevStack documentation" [Undecided,New] - Assigned to Taylor Peoples (tpeoples) 14:26:13 dtardivel: i am going to update the docs to explain how to set up devstack from nothing 14:26:20 instead of just telling them to use the plugin 14:26:24 acabot: junjie and gzhai submitted some bps that we would like to start working n now 14:26:32 tpeoples: +1 14:26:38 +1000 14:26:39 that way someone with no devstack experience should be able to set it up 14:26:44 sballe: yes this is something I'd like to discuss 14:26:58 +1 14:27:00 tpeoples: it is a request coming from openstack-dev ? 14:27:10 our PhD will be able to run devstack ! 14:27:11 no, just from me :) 14:27:21 tpeoples: ok :) 14:27:25 +1 n devsack 14:27:30 devstack :) 14:28:04 so we have many new BPs that we will prioritize next week during our mid-cycle 14:28:15 perfect 14:28:30 please submit BPs before EOW if you want to have them included in mitaka-3 14:28:46 just BP, not spec, right? 14:28:48 I believe mritika created a bp too around fingerprinting. I will follow up with her to make sure I know what she is doing 14:28:59 #info submit BPs before EOW if you want to have them included in mitaka-3 14:29:24 gzhai: could you give us a quick overview of the 3 BPs you submitted ? 14:29:26 sballe cool 14:29:32 gzhai: I would suggest we start on the spec as well in parallel taht way we will be closer to be able to start implementing 14:29:44 tpeoples: thx ;-) 14:29:47 sballe: ok 14:30:05 gzhai: yes BPs only 14:30:27 acabot: why not start on the spec for one of them? 14:30:33 acabot: we will start from the BP of airflow. 14:31:03 sballe gzhai : yes of course, I just want to check that we have all BPs referenced before the mid-cycle 14:31:15 +1 14:31:55 #info gzhai submited 3 new BPs for 3 new optimization strategies 14:32:04 it check the airflows with power/temperature to see if something wrong or just high workload. 14:32:11 acabot: We are just startign the discussion around Watcher and TAP so I am hoping that we can move some of that work in as well as we get it defined. 14:32:39 sballe: sure this is something we will discuss next week 14:32:57 exactly. tkaczynski will be attending the summit as well as 14:33:00 sballe it would be great, but we need quite a lot of discussion to get tothe same page 14:33:42 tkaczynski: I agree but I want to make sure we can make progress an d not have to sit and wait around until the next cycle if we have some work taht can be dne 14:34:33 but as acabot said we'll discuss next week 14:34:34 if tkaczynski and jed56 can have f2f discussion next week, no doubt it will lead to something ;-) 14:34:41 +1 14:35:06 +1 14:35:14 +1 14:36:25 tpeoples jwcroppe : any BPs you plan to add before the mid-cycle ? 14:37:10 same question for brunograz 14:37:19 acabot: will think about it, but i was planning on picking up some of the existing TBH 14:37:40 brunograz cdupont : you wont be able to attend the mid-cycle but do not hesitate to submit BPs 14:38:32 acabot: maybe we can get remote access to brunograz and cdupont when we talk about bps. 14:38:51 assumung they ae interested 14:38:59 sballe: yes sure, everything will be shared on an etherpad 14:39:09 that is true! I forgot 14:39:16 acabot: yes sure 14:39:28 brunograz and myself will be at a project meeting feb 2/3 14:39:49 we can try to be available but we will be a bit tied up 14:40:03 ok, I will share the etherpad link on the agenda page on tuesday 14:40:21 should we keep our weekly meeting next week by the way ? 14:40:46 I think we should skip it since we have the meetup 14:41:10 vote for skip 14:41:16 +1 14:41:17 +1 14:41:28 #info no meeting next week as most of the team will be at the mid-cycle meetup 14:41:54 +1 14:41:58 cross-project liaison, sballe, did you see the action last week ? 14:42:10 briefly. 14:42:19 When was the meeting? 14:42:23 tpeoples suggested that we have a cross-project liaison 14:42:30 I saw that 14:42:32 for watcher 14:42:51 and we are looking for a very nice person to do it ;-) 14:43:15 I am hapy to take on taht role but need jwcroppe to be my backup when I travel and cannot attend 14:43:20 as the meeting is at 10pm french time I'm not sure to be able to attend 14:43:31 also I am a nice person so I fit the criteria :) 14:43:41 sballe: right :-D 14:43:46 +1 14:44:06 jwcroppe : what do you think as being the backup ? 14:44:07 as long as somebody can be a backup when I cannot attend I am cool with htis 14:44:45 I can also be the backup of course 14:45:03 I am sure jwcroppe is fine with being the backyp 14:45:07 acabot:+1 14:45:14 yes, that sounds good 14:45:32 acabot: sign me up and jwcroppe as backup 14:45:34 #action sballe start acting as the cross-projects liaison for Watcher (jwcroppe as backup) 14:46:14 #info final meetup agenda #link https://wiki.openstack.org/wiki/Watcher_mitaka_mid-cycle_meetup_agenda#Agenda 14:46:37 we moved a couple of things from day 1 to 2 according to attendees presence 14:46:45 acabot: jut want to heck this is it right? https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting 14:46:51 s/check 14:47:03 yes sballe 14:47:06 yes 14:47:08 thx 14:47:50 sballe: we will discuss mitaka priorities on day 1 so please send me an email about "your priorities" 14:48:03 will do 14:48:19 sballe: there is a list of CPLs on https://wiki.openstack.org/wiki/CrossProjectLiaisons that i think you should add yourself to too 14:48:24 we will probably adjust them on day 3 after 2 days of thinking... 14:48:59 acabot: +1 14:49:19 vincentfrancoise: experimental jobs and how to be automatic, do you have info on that ? 14:49:37 that was me 14:49:50 awesome work by vincentfrancoise on getting the tempest plugin working 14:49:54 yes but I know that vincentfrancoise looked at it 14:50:06 i think we should consider getting that running automagically 14:50:10 ok, cool 14:50:12 well, whenever the last batch of tempest tests qet merged 14:50:40 sounds good vincentfrancoise 14:50:40 I will make a PS on project-config to make it automatic on the gate 14:51:07 so probably by EOW 14:51:35 will it be a voting job automatically ? 14:51:49 #link https://review.openstack.org/#/c/272551/ 14:51:57 i think it should be voting tbh 14:52:24 tpeoples: +1 14:52:42 tpeoples: +1 will do 14:53:39 #action vincent francoise set tempest test as a voting job on the gate 14:53:45 #action vincentfrancoise set tempest test as a voting job on the gate 14:53:47 since there's nothing left on the agenda.. i have something random. should we include translation with every patchset, or do it all end of release? 14:54:10 internally, we do translation as an after thought with an automated tool 14:54:29 with jed56, we decided to translate it in french as we go along 14:54:41 tpeoples : easier to maintain if its done on every PS IMO 14:54:59 yes 14:55:31 ok, that'll work for now but we may want to consider changing that in the future, but we'll save that discussion 14:55:35 tpeoples: but if we can run your tool just before releasing it could be great too 14:55:36 +1 14:56:10 but it's the same with the sample file which we will eventually remove from the codebase 14:56:42 ok 14:56:44 vincentfrancoise: we can remove the sample file i think and add some documentaiton 14:57:14 jed56: you mean to help developers adding translation in the code ? 14:57:19 jed56: dtardivel will make a wishlist bug on the matter anytime soon 14:57:32 acabot no 14:57:47 watcher.conf.sample 14:58:04 IMO, we will need to review translations just before the release to be sure all translated sentences are coherent 14:58:14 #action dtardivel add a wishlist bug to remove the sample file 14:58:16 +100 14:58:33 dtardivel: ok 14:58:57 +1 dtardivel, part of that automated preferably 14:59:09 see some of you next week in austin 14:59:21 yes see u in Austin 14:59:25 bye 14:59:31 bye 14:59:32 bye 14:59:32 bye! 14:59:33 bye see you next week 14:59:34 bye 14:59:36 bye 14:59:36 have fun in TX! 14:59:38 bye 14:59:42 #endmeeting