14:00:40 <acabot> #startmeeting watcher
14:00:41 <openstack> Meeting started Wed Feb 17 14:00:40 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:42 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:44 <openstack> The meeting name has been set to 'watcher'
14:00:46 <acabot> hello
14:01:02 <sballe> o/
14:01:03 <seanmurphy> hi
14:01:06 <brunograz> hi
14:01:15 <tkaczynski> hi
14:01:21 <vtech> o/
14:01:28 <jed56> \o
14:01:34 <dtardivel> o/
14:01:38 <acabot> #info agenda for today https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#02.2F17.2F2016
14:01:47 <jwcroppe> o/
14:02:02 <edleafe> \o
14:02:10 <acabot> #topic Announcements
14:02:34 <acabot> a couple of annoucements regarding discussions on the mailing list
14:02:44 <vincentfrancoise> o/
14:02:59 <acabot> #info No Open Core #link http://lists.openstack.org/pipermail/openstack-dev/2016-February/085855.html
14:04:07 <acabot> the important thing in this thread is : "It should have a fully-functional, production-grade open source implementation. If you need proprietary software or a commercial entity to fully use the functionality of a project or getting serious about it, then it should not be accepted in OpenStack as an official project."
14:04:25 <jwcroppe> interesting
14:04:34 <sballe> Agreed
14:04:37 <jwcroppe> I think that's in line w/ what we discussed
14:04:46 <acabot> its important to deliver Watcher as a "full" project
14:04:53 <edleafe> acabot: and what is the concern with Watcher
14:04:56 <edleafe> ?
14:04:59 <acabot> jwcroppe I agree
14:05:09 <gzhai3> what we miss so far?
14:05:15 <sballe> I don't believe we have any concern
14:05:26 <acabot> its more an info that we should keep that in mind
14:05:45 <acabot> but we are fully compliant right now
14:05:47 <edleafe> The concern in that thread was Poppy, which tries to generalize an API for CDNs
14:05:56 <edleafe> There are no free/open CDNs out there
14:06:10 <sballe> Oh that makes sense
14:06:40 <edleafe> So the only way to actually use Poppy (and test it) would be to pay for a closed CDN provider
14:06:55 <tkaczynski> same applies to scoring module - it will not depend on TAP or any other external software
14:07:16 <sballe> Agreed
14:07:25 <jwcroppe> acabot: I agree with this overall - I think we just need to continue to be mindful of this as we make assertions about what Watcher 'requires' to be used
14:07:43 <acabot> jwcroppe : +1
14:08:04 <acabot> #info roadmap for Nova scheduler  #link http://lists.openstack.org/pipermail/openstack-dev/2016-February/086371.html
14:08:36 <acabot> its a very long thread but interesting to see how the nova scheduler will evolve during mitaka and newton
14:08:57 <acabot> and how we can take advantage of these evolutions in Watcher
14:08:59 <edleafe> jwcroppe: yes. The other concern with Poppy is that it relies on Cassandra, which only works with the Oracle JDK.
14:09:03 <sballe> I will read it as soon as I get off my phone ;-)
14:09:45 <edleafe> jwcroppe: so requiring the use of a closed product is another bad thing to do
14:10:03 <acabot> #info our talks are open to vote until tomorrow, so if you didnt took the time to give a +3, please do it
14:10:13 <sballe> Oh I see even though it is open source
14:10:53 <acabot> any other announcement ?
14:11:26 <seanmurphy> link to talk to vote for please? (if someone has it handy)
14:11:26 <jwcroppe> edleafe: agree
14:11:36 <sballe> I am working on getting us to intel for the next mid cycle
14:11:37 <acabot> jwcroppe : is tpeoples off this week ?
14:11:56 <vincentfrancoise> #link https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/7108#link https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/7113
14:11:58 <edleafe> sballe: yes, but if they could convince the Cassandra people to support OpenJDK, then it would be fine
14:12:16 <sballe> edleafe: makes sense
14:12:36 <acabot> #topic Review Action Items
14:13:36 <acabot> we have a lot of specs open
14:13:55 <jwcroppe> acabot: on my list to do today
14:14:02 <sballe> Same here
14:15:01 <acabot> #action sballe jwcroppe review https://review.openstack.org/#/c/273556/ https://review.openstack.org/#/c/276586/ https://review.openstack.org/#/c/274688/ https://review.openstack.org/#/c/266446/  https://review.openstack.org/#/c/278516/​​
14:15:06 <tkaczynski> my action items are still waiting - struggling to setup devstack env. I'm putting all my time there...
14:15:44 <acabot> tkaczynski : ok could you please use the openstack-watcher irc channel for support ?
14:16:08 <tkaczynski> acabot ok
14:16:10 <dtardivel> or openstack-dev irc channel
14:16:17 <acabot> as it is logged, its better if we need to give the same explanations later
14:16:54 <acabot> we also need specs for high priority BPs
14:17:21 <acabot> #action tkaczynski submit a drafted spec for https://blueprints.launchpad.net/watcher/+spec/scoring-module
14:17:55 <acabot> jwcroppe: tpeoples had an action to submit a spec for https://blueprints.launchpad.net/watcher/+spec/cluster-model-objects-wrapper, any update on this ?
14:18:15 <jwcroppe> He is out today - I'll check with him tomorrow (and let's make an action for him)
14:18:37 <acabot> #action tpeoples submit a spec for https://blueprints.launchpad.net/watcher/+spec/cluster-model-objects-wrapper
14:19:09 <acabot> #action acabot submit a drafted spec for https://blueprints.launchpad.net/watcher/+spec/select-destinations-filter
14:19:41 <acabot> we received an email from alexstav regarding https://blueprints.launchpad.net/watcher/+spec/watcher-overload-underload
14:20:15 <acabot> he will submit a spec for this BP as we had to explain the contribution process
14:20:30 <acabot> #action alexstav submit a spec for https://blueprints.launchpad.net/watcher/+spec/watcher-overload-underload
14:21:19 <acabot> on Watcher side
14:21:42 <acabot> #info Delete related actions when deleting an action plan has been merged
14:22:12 <acabot> there are bug fixes in review
14:22:43 <acabot> gzhai3 : could you do some code reviewing this week ?
14:22:49 <gzhai3> sure
14:22:53 <dtardivel> acabot: watcher-dashboard initial pachset will be merged today
14:23:23 <acabot> dtardivel : ok tpeoples had an action to review it
14:23:50 <acabot> jwcroppe : can we merge the initial commit today ?
14:24:20 <jwcroppe> I think so
14:24:42 <dtardivel> watcher-dashboard plugin will be now automatically deployed within horizon, in devstack.
14:24:50 <acabot> #action dtardivel merge watcher-dashboard initial commit today
14:25:40 <acabot> #topic Blueprint/Bug Review and Discussion
14:26:12 <dtardivel> new watcher-dashboard HTML documentation will be also set online soon
14:27:03 <acabot> #info regarding the SSL support we discussed last week, there are 3 open bugs (2 on devstack, 1 on watcher)
14:28:04 <acabot> vtech: did you already start implementing ZHAW strategy ?
14:28:25 <dtardivel> yes, by reading these bugs, you will be able to apply workaround on your devstack env, waiting for official fixes
14:28:40 <seanmurphy> we did not start the watcher implementation yet
14:28:50 <seanmurphy> we had a variant designed for openstack before
14:29:04 <seanmurphy> we have looked a little at the watcher supports and the example strategy
14:29:17 <seanmurphy> but we have not specifically started the implementation yet
14:29:25 <seanmurphy> it is going up the prio list
14:29:28 <acabot> seanmurphy : ok thx
14:29:33 <seanmurphy> we should have something for next week
14:29:44 <seanmurphy> i will discuss the process with you/jed outside this chat
14:29:59 <acabot> seanmurphy : I think we will be able to merge the spec before end of week so you can start implementing
14:30:07 <seanmurphy> ok
14:30:11 <acabot> thx
14:30:16 <gzhai3> pwd
14:30:38 <jed56> cool
14:31:15 <acabot> edleafe : any update from the nova team regarding the BP https://review.openstack.org/#/c/276840/
14:31:32 <edleafe> no, not anything yet
14:31:38 <acabot> ok
14:31:54 <dtardivel> seanmurphy: can you have discussion on openstack-watcher IRC channel please. It will benefits everyone
14:32:05 <seanmurphy> for sure
14:32:36 <edleafe> acabot: it probably won't see much action until Newton
14:32:47 <acabot> edleafe : yes I suppose
14:33:25 <acabot> a quick look at bugs targeted for Mitaka https://launchpad.net/watcher/+milestone/mitaka-3
14:34:00 <jwcroppe> edleafe: it'd be interesting to get bauza's take on
14:34:20 <acabot> many of them are unassigned but I correctly understand the release schedule, we can fix them after mitaka-3 milestone
14:35:16 <acabot> #topic Open Discussion
14:36:28 <acabot> I had an action after the mid-cycle to share the actions on the mailing list but I didn't find any other project doing it...
14:36:45 <acabot> do you think we should do it anyway ?
14:37:20 <jwcroppe> acabot: hmm, maybe not 'actions' explicitly - but a quick summary of discussions ?
14:37:46 <sballe> jwcroppe: +1
14:37:46 <jwcroppe> ...even a quick pointer to our etherpad
14:37:57 <acabot> jwcroppe : other projects share the etherpad
14:38:34 <acabot> ok so a link to the etherpad and a quick review of decisions made ?
14:38:46 <sballe> +1
14:38:58 <gzhai3> +1
14:39:11 <edleafe> jwcroppe: sorry, on a team call now
14:39:26 <acabot> #action acabot  share a link to the etherpad and a quick review of decisions made on the ML
14:39:31 <seanmurphy> i would like to have some idea how it went/discussions/conclusions etc
14:39:43 <edleafe> jwcroppe: but since he was in on the original discussion with alaski, I think it won't be too contentious
14:39:53 <acabot> seanmurphy : did you look at the etherpad already ?
14:40:08 <seanmurphy> no - i was not aware it existed tbh
14:40:32 <acabot> #info mid-cycle etherpad #link https://etherpad.openstack.org/p/mitaka-watcher-midcycle
14:42:01 <seanmurphy> thanks
14:42:44 <acabot> we had a discussion this morning with jed56, dtardivel, vmahe & vincentfrancoise about updating the class hierarchy in Watcher strategies to deal with input parameters (threshold) and output parameters (efficacy indicator)
14:43:18 <acabot> it will impact 2 open BPs https://blueprints.launchpad.net/watcher/+spec/efficacy-indicator & https://blueprints.launchpad.net/watcher/+spec/optimization-threshold
14:43:36 <gzhai3> how to refactoring?
14:43:46 <tkaczynski> acabot: what about scoring module? will it impact it as well?
14:43:50 <acabot> vmahe is working on an updated class diagram that will be part of the efficacy indicator spec
14:43:59 <acabot> tkaczynski : not at all
14:45:07 <acabot> the idea is to create a new class between "base strategy" and "strategy" to hold a goal and a list of efficacy indicators
14:45:23 <acabot> it will be a lot clearer with a schema ;-)
14:45:55 <vmahe> there should be a base class for all strategies that achieve the same goal
14:46:06 <vmahe> those strategies would also share the same efficacy indicators
14:46:26 <vmahe> so that we can compare them
14:46:36 <acabot> the hierarchy would be baseStrategy->energyStrategy->dummy
14:46:43 <jed56> I think is more easy to discuss that around a specification :)
14:46:51 <vmahe> +1
14:47:07 <gzhai3> +1
14:47:32 <jed56> I think acabot just want to let you know that the possible impacts :)
14:47:40 <vincentfrancoise> +1
14:47:42 <acabot> jed56 : +1 right my point is to say that the BP regarding the threshold will be impacted
14:48:23 <acabot> so gzhai3 please review the efficacy indicator spec as soon as vmahe has submitted the schema
14:48:31 <vmahe> I will also write a new bp saying that the goal will be returned by each strategy or each common parent strategy
14:48:34 <gzhai3> acabot: ok
14:49:12 <acabot> so we will have 3 BPs correlated
14:50:07 <acabot> but il will be much easier and cleaner to hold input/output parameters of strategies
14:51:37 <acabot> sballe : any update on the cross projects meeting ?
14:52:31 <dtardivel> sballe: ^
14:52:36 <sballe> No they mostly discussed how to do user policies across the projects
14:52:49 <acabot> ok
14:52:57 <acabot> meeting with congress ?
14:53:16 <sballe> The idea is to not have user be admin to be able to do more advanced things
14:53:22 <sballe> No progress on congress yet
14:53:33 <sballe> Will follow with them this week
14:54:08 <sballe> I need to figure out who to talk to
14:54:15 <acabot> ok
14:54:37 <acabot> any other subject ?
14:56:09 <sballe> Not from me
14:56:46 <acabot> sballe: did you get an update for the lab submission through INTEL ?
14:57:23 <sballe> So it turns out it is for the intel booth
14:57:35 <jwcroppe> nothing else from me
14:57:37 <sballe> I submitted it again
14:57:43 <acabot> :-) ok
14:58:27 <sballe> But this time only a demo
14:58:27 <sballe> No lab
14:58:31 <sballe> acabot: ^^
14:58:32 <acabot> #info vmahe submitted a new BP https://blueprints.launchpad.net/watcher/+spec/get-goal-from-strategy
14:59:08 <acabot> ok thank you
14:59:24 <acabot> have a good day (night for gzhai3 ;-))
14:59:26 <jed56> bye have nice (day,afternoon, .. )
14:59:30 <sballe> Bye
14:59:31 <tkaczynski> by
14:59:34 <vincentfrancoise> bye
14:59:36 <seanmurphy> bye guys
14:59:37 <tkaczynski> bye ;)
14:59:44 <dtardivel> bye
14:59:45 <acabot> #endmeeting