14:00:06 <acabot> #startmeeting watcher
14:00:07 <openstack> Meeting started Wed Sep  7 14:00:06 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:08 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:10 <openstack> The meeting name has been set to 'watcher'
14:00:15 <sballe_> o/
14:00:17 <acabot> hi
14:00:27 <hanrong1> hi
14:00:36 <acabot> packed agenda today :-) #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#09.2F07.2F2016
14:00:46 <hanrong1> Jinquan's right hand was broken, and he couldn't attend the meeting for two weeks.
14:00:50 <tkaczynski> hi
14:01:02 <acabot> hanrong1 : ok thx for leeting us know
14:01:19 <hanrong1> :)
14:01:31 <dtardivel> hi
14:01:32 <jwcroppe> o/
14:01:38 <acabot> #topic Announcements
14:01:42 <vincentfrancoise> o/
14:01:47 <tamilhce> hi
14:02:04 <alexchadin> hi
14:02:13 <acabot> hi tamilhce, welcome
14:02:26 <acabot> #info PTL nominations will be held next week
14:02:33 <acabot> #link https://governance.openstack.org/election/
14:02:45 <acabot> #info candidacy must be submitted through Gerrit
14:02:51 <acabot> #link https://governance.openstack.org/election/#how-to-submit-your-candidacy
14:02:59 <sballe_> wow already. time flies
14:03:10 <mrhillsman> o/
14:03:45 <acabot> as some of you join late, here is the agenda again #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#09.2F07.2F2016
14:04:02 <acabot> #info watcher 0.29.0, python-watcherclient 0.25.0 & watcher-dashboard 0.4.0 have been announced
14:04:33 <acabot> all packages available on pypi
14:04:53 <acabot> we just discovered there is something wrong with watcher-dashboard in devstack
14:05:03 <acabot> we have to take a look
14:05:17 <acabot> now we are waiting for the Newton branch
14:05:26 <acabot> #info 3 patches are needed for Newton branch handled by dhellmann
14:05:33 <acabot> #link http://lists.openstack.org/pipermail/openstack-dev/2016-September/102829.html
14:06:01 <acabot> We need to confirm our speakers for Barcelona
14:06:12 <acabot> sballe_ & hanrong1 confirmed last week
14:06:22 <acabot> jwcroppe will you replace Taylor ?
14:06:35 <acabot> or we can have someone from bcom
14:07:19 <acabot> I also saw that sballe_ is working on slides already
14:08:04 * dtardivel test
14:08:10 <sballe_> yes
14:08:21 * acabot is waiting for answers...:-)
14:08:35 <sballe_> jwcroppe: ?
14:09:22 <acabot> #action acabot open a thread on the ML to discuss talk for Barcelona
14:09:32 <acabot> #info Project Teams Gathering will be held in Atlanta Feb 20-24, 2017
14:09:56 <acabot> next mid-cycle will be replaced by the PTG
14:10:05 <sballe_> I liked it better when we were organizing the meetup. We could choose location and dates
14:10:36 <acabot> I do agree but it will be a lot easier to have cross projects discussions
14:11:13 <acabot> so if you plan to attend our next mid-cycle, keep Feb 20-24 clear
14:11:26 <acabot> any other announcement ?
14:11:46 <acabot> #topic Review Action Items
14:11:52 <acabot> specs
14:11:59 <acabot> Resize instance base on workload should be retargeted to Ocata
14:12:06 <acabot> #link https://review.openstack.org/#/c/359690/
14:12:16 <acabot> #action jinquan retarget https://review.openstack.org/#/c/359690/
14:12:26 <acabot> Limit concurrent actions invoked by Watcher needs reviews
14:12:39 <acabot> #link https://review.openstack.org/#/c/348049/
14:12:44 <jwcroppe> acabot, sballe_: in short-term it's looking unlikely to have an official replacement
14:12:55 <jwcroppe> acabot: Re: that spec - thanks.  Been out there a few weeks now
14:13:11 <acabot> jwcroppe : ok but we are not talking about code but speaking at the summit ;-)
14:13:29 <acabot> #action jwcroppe answer comments on https://review.openstack.org/#/c/348049/
14:13:45 <jwcroppe> acabot: oh, in that case - yes - I'll cover that talk with the team :)
14:14:00 <acabot> jwcroppe : ok thx
14:14:37 <jwcroppe> acabot: will push the spec for Ocata and address comments today
14:14:40 <acabot> #action jwcroppe hanrong1 sballe_ acabot prepare talk for Barcelona summit
14:14:53 <acabot> ok
14:14:58 <diga> Hi
14:15:09 <acabot> diga : welcome we were talking about your spec :-)
14:15:13 <diga> sorry, got late due to traffic jam
14:15:16 <diga> :)
14:15:24 <acabot> automatic triggering audit needs reviews
14:15:32 <acabot> #link https://review.openstack.org/#/c/342473/
14:15:33 <diga> yes
14:15:42 <acabot> actually now it needs a new PS
14:15:50 <diga> okay
14:15:53 <acabot> #action diga add a PS for https://review.openstack.org/#/c/342473/
14:16:13 <acabot> moving to Watcher
14:16:20 <acabot> Graph cluster model implementation needs discussion regarding Heat
14:16:26 <acabot> #link https://review.openstack.org/#/c/362730/
14:16:41 <acabot> sballe_ : do you think we can have a discussion with Greg ?
14:16:43 <diga> acabot: Actually I didn't get vincentfrancoise comments on having RPC over notification
14:17:18 <acabot> he didn't mention Heat in the spec and he is using it in his code
14:17:21 <sballe_> acabot: yes
14:17:28 <acabot> its surprising
14:17:32 <sballe_> Greg was suppose to be inthe IRC meeting
14:17:45 <sballe_> I agree
14:18:01 <acabot> ok could you set up an adhoc meeting with him ?
14:18:12 <sballe_> yes. will do
14:18:23 <acabot> #action sballe_ set up a meeting with Greg to discuss https://review.openstack.org/#/c/362730/
14:18:25 <sballe_> give me an action to do so and I will remember
14:18:42 <acabot> Add documentation for Scoring Module should be merged before branching
14:18:48 <acabot> #link https://review.openstack.org/#/c/362827/
14:18:58 <vincentfrancoise> diga: thw way action plans are currently triggered is via an RPC call that is sent from the watcher API to the watcher Applier when someone sends a request to trigger the execution of an action plan
14:19:19 <acabot> as the feature is included in Newton, I would like to have it merged asap
14:19:30 <diga> vincentfrancoise: got it
14:19:40 <acabot> tkaczynski : thx for being reactive
14:19:57 <vincentfrancoise> diga: my point is that we should the same underlying mechanism (i.e. the RPC call) but from within the Decision Engine when we want to do our automatic triggering of our action plan
14:19:58 <acabot> does any core can have a final look at it ?
14:20:08 <tkaczynski> acabot: no problem, cleaning my garden :)
14:20:19 <diga> vincentfrancoise: okay
14:20:40 <vincentfrancoise> acabot: I +2'd it already
14:21:05 <dtardivel> acabot: I will do
14:21:16 <acabot> #action dtardivel review https://review.openstack.org/#/c/362827/
14:21:25 <diga> vincentfrancoise: will rework on my patch & incorporate suggested changes
14:21:28 <alexchadin> acabot: I've already reviewed it twice
14:22:03 <acabot> ok you already W+1 :-D
14:22:07 <acabot> #undo
14:22:09 <openstack> Removing item from minutes: <ircmeeting.items.Action object at 0x7f5bbf2c9890>
14:22:16 <acabot> thx
14:22:27 <acabot> Add rally-jobs folder to get rally support needs a doc addition
14:22:33 <acabot> #link https://review.openstack.org/#/c/333371/
14:22:57 <acabot> alexchadin : could you add a link from watcher doc in your PS ?
14:23:38 <alexchadin> acabot: what do you mean?
14:24:04 <acabot> we discussed it last week, we need to add a Rally item on http://docs.openstack.org/developer/watcher/
14:24:54 <alexchadin> acabot: ah, I remember it. Do I need to add new section here?
14:25:01 <alexchadin> Related to the rally tests?
14:25:27 <acabot> yes just saying that Watcher support rally and devs can use it
14:25:55 <alexchadin> I will discuss it with dtardivel then
14:26:01 <alexchadin> ok, will do by EOW
14:26:02 <dtardivel> alexchadin: I can help u ....
14:26:04 <acabot> #action alexchadin add a doc section for Rally
14:26:18 <acabot> Implemented GMR plugin to show CDM structures is needed for scalability tests
14:26:24 <acabot> #link https://review.openstack.org/#/c/366032/
14:26:34 <acabot> so we need reviews on this
14:26:48 <sballe_> I'll do it
14:26:48 <acabot> who wants to review it ?
14:27:09 <dtardivel> acabot: I'm reviewing it
14:27:18 <acabot> #action sballe_ dtardivel review https://review.openstack.org/#/c/366032/
14:27:30 <acabot> #topic Blueprint/Bug Review and Discussion
14:27:48 <acabot> #info Current milestone is Newton-rc1 due September 12th - only one BP (scalability tests) & bug fixes
14:27:58 <acabot> #link https://launchpad.net/watcher/+milestone/newton-rc1
14:28:10 <acabot> When the action plan is empty, it's state is incorrect needs discussion
14:28:16 <acabot> #link https://bugs.launchpad.net/watcher/+bug/1619155
14:28:16 <openstack> Launchpad bug 1619155 in watcher "When the action plan is empty, it's state is incorrect " [Undecided,In progress] - Assigned to licanwei (li-canwei2)
14:29:04 <acabot> as a reminder, if you file a bug, please wait for triage before fixing it
14:29:17 <acabot> we are doing bug triage periodicaly
14:29:30 <hanrong1> I will tell him
14:29:45 <sballe_> I was just going to ask.. I have seen several submittion and I wasn't sure if they had been triaged
14:30:03 <acabot> so the bug is related to the state of the action plan when there is no action to execute
14:30:39 <acabot> I dont think in this case it must be in "Failed" state
14:31:05 <gzhai> acabot:+1
14:31:05 <vincentfrancoise> regarding this bug, I agree that the RECOMMENDED state isn't great, but IMHO it should be either SUCCEEDED or CANCELLED
14:31:37 <acabot> IMHO it should be SUCCEEDED as the infra is already optimized
14:31:48 <alexchadin> great work:D
14:31:50 <vincentfrancoise> acabot: +1
14:31:55 <acabot> and CANCELED would look like an error
14:32:04 <sballe_> acabot: +1
14:32:05 <acabot> what do you think ?
14:32:18 <alexchadin> +1 for SUCCEEDED
14:32:30 <hanrong1> SUCCEEDED +1
14:32:58 <dtardivel> SUCCEEDED +1
14:33:05 <acabot> hanrong1 : if you know licanwei, can you share this discussion with him ?
14:33:19 <acabot> I think we can go for SUCCEEDED
14:33:23 <hanrong1> yes, I will
14:34:02 <acabot> #action acabot update https://bugs.launchpad.net/watcher/+bug/1619155 to set a SUCCEEDED state
14:34:02 <openstack> Launchpad bug 1619155 in watcher "When the action plan is empty, it's state is incorrect " [Undecided,In progress] - Assigned to licanwei (li-canwei2)
14:34:14 <acabot> dependency to discuss between Limit Concurrent Actions & Improve the storage of the ActionPlan
14:34:20 <acabot> #link https://blueprints.launchpad.net/watcher/+spec/limit-concurrent-actions
14:34:26 <acabot> #link https://blueprints.launchpad.net/watcher/+spec/planner-storage-action-plan
14:34:34 <acabot> alexchadin : you wanted to discuss it ?
14:34:41 <alexchadin> acabot: yeap
14:35:01 <jwcroppe> alexchadin: ok, cool
14:35:04 <alexchadin> for now we have graph algorithm that launches action in order, right?
14:36:00 <jwcroppe> right
14:36:01 <alexchadin> It's made using TaskFlow
14:36:03 <dtardivel> alexchadin: It's just a linked action chain for now. But we use taskflow which support graph
14:36:19 <jwcroppe> i.e., 1 at a time
14:37:41 <acabot> I think its useless to handle a limit of concurrent actions in the current state of Watcher as there is only one action at a time
14:38:06 <acabot> I know that Taskflow can handle it but we dont do it yet
14:38:15 <alexchadin> ok, with my approach to the limiting of actions we don't have a dependency on planner-storage-action-plan
14:38:24 <acabot> thats the main idea of https://blueprints.launchpad.net/watcher/+spec/planner-storage-action-plan
14:38:40 <jwcroppe> acabot: +1 given its current state - this came up at the mid-cycle
14:39:04 <sballe_> acabot: +1
14:39:07 <acabot> alexchadin : what do you mean by "your approach" ?
14:40:00 <jwcroppe> acabot: once https://blueprints.launchpad.net/watcher/+spec/planner-storage-action-plan is implemented, then we have a need for the limiter spec
14:40:01 <alexchadin> I propose to check count of active actions by using class argument
14:40:47 <alexchadin> static argument, that will be personal for each kind of action (nop, migration, powering off, etc)
14:41:12 <alexchadin> no matter in which order we will launch it
14:41:16 <alexchadin> them*
14:41:18 <acabot> alexchadin : ok but in this case its pretty far from what jwcroppe proposed as a spec
14:41:28 <jwcroppe> alexchadin: btw, I replied to your comment in the spec ... the idea was that you could also have different limits for different audits/scopes
14:42:22 <alexchadin> I think, we could have pre-defined limits in configuration file for each kind of actions
14:42:37 <jwcroppe> alexchadin: will you be @ the summit?
14:42:46 <alexchadin> jwcroppe: yeap:)
14:43:02 <acabot> alexchadin : could you please iterate on jwcroppe spec ?
14:43:11 <jwcroppe> alexchadin: cool - let's iterate there as well.  there are many ways we can tackle this
14:43:47 <alexchadin> acabot: yes, I will try to introduce my vision of this spec in near future
14:43:50 <alexchadin> is it ok?
14:43:52 <acabot> please work together on work items because I think you both have quite a different view
14:43:57 <jwcroppe> acabot: +1 ... let's iterate on some ideas in the spec and if we're still back and forth we can whiteboard in Spain
14:44:10 <acabot> cool
14:44:14 <alexchadin> +1
14:44:26 <acabot> #action jwcroppe alexchadin iterate on  https://review.openstack.org/#/c/348049/1/specs/newton/approved/limit-concurrent-actions.rst
14:44:36 <jwcroppe> alexchadin: feel free to create a new spec as well if you'd like and we can compare/contrast - or even form a hybrid
14:44:53 <acabot> #topic Open discussions
14:44:53 <alexchadin> jwcroppe: sure, thank you!
14:45:04 <jwcroppe> I'm happy to adapt my spec to pick up on the elements that yours captures... ok great
14:45:09 <acabot> Platform status for scalability tests
14:45:25 <acabot> sballe_ gzhai : can I let you give a status ?
14:45:59 <sballe_> acabot: I am having issue with IRC
14:46:02 <acabot> to put everybody on the same page, I tried to summerize it in https://docs.google.com/presentation/d/1I6OPqUXDfB2BbcI3Zr0625mb92N-UaPY8YNhgmjkLts/edit?usp=sharing
14:46:23 <sballe_> gzhai: can you give the update?
14:46:28 <acabot> please use animations if you want to have something readable :-D
14:47:09 <sballe_> ok I can try. The systems are up and the base OpenStack has been installed, today the team will install Monasca, ceilosca
14:47:12 <sballe_> and Watcher
14:47:41 <sballe_> gzhai is running some tests with PBK
14:47:45 <gzhai> the container exit and I can't get the log
14:48:19 <sballe_> We are still working out the details with dtardivel and his scripts apparently ;-)
14:49:11 <dtardivel> gzhai: if the container aborted, normaly you can get logs: docker pkb logs
14:50:33 <acabot> gzhai : could you copy paste the output after running "pkb" ?
14:50:56 <acabot> we can deal with that on our IRC channel
14:51:07 <dtardivel> acabot: maybe on openstack-watcher channel
14:51:08 <acabot> any other topic to discuss ?
14:51:09 <gzhai> Will VM exit after running benchmark?
14:51:21 <dtardivel> gzhai: yes
14:51:47 <acabot> tamilhce mrhillsman : do you want to introduce yourself ?
14:52:05 <tamilhce> yeah iam tamil vanan
14:52:18 <tamilhce> new to penstack contribution
14:52:31 <tamilhce> *openstack
14:52:49 <acabot> ok thats great, for which company are you working ?
14:53:27 <tamilhce> i work for a startup
14:54:04 <tamilhce> i could see some issues in heat docs
14:54:27 <tamilhce> reg: https://bugs.launchpad.net/heat/+bug/1618802
14:54:27 <openstack> Launchpad bug 1618802 in heat "[devref] handle_signal is not documented" [Undecided,In progress] - Assigned to tamil vanan (tamilhce)
14:54:27 <acabot> tamilhce : any specific interest in Watcher ?
14:54:36 <acabot> I mean doc, code, specs, tests ?
14:55:34 <tamilhce> i am interested in code
14:56:12 <acabot> ok great, in this case you are more than welcome to start with bugs
14:56:24 <acabot> we have low-hanging-fruits bugs
14:56:44 <acabot> https://bugs.launchpad.net/watcher/+bugs?field.tag=low-hanging-fruit
14:56:46 <mrhillsman> mrhillsman
14:56:54 <mrhillsman> openstack innovation center - ops team lead
14:56:58 <acabot> currently only one ;-)
14:57:07 <mrhillsman> rackspace/intel collaboration
14:57:10 <acabot> mrhillsman : ok thx for the intro
14:57:47 <acabot> mrhillsman : we asked OSIC for a test infra a couple of months ago but we didn't get any answer
14:58:09 <acabot> mrhillsman : we finally managed to get a test infra at Intel
14:58:14 <mrhillsman> we can dialogue further about it
14:58:18 <mrhillsman> oh
14:58:35 <mrhillsman> you all went through the online forme?
14:58:37 <mrhillsman> form?
14:58:39 <acabot> yes
14:58:49 <acabot> I received an email confirmation
14:58:57 <acabot> but no news after
14:58:58 <mrhillsman> ok, if you want to discuss further we can do so offline
14:58:59 <sballe_> yes and Leong couldn;'d find it :-(
14:59:07 <mrhillsman> meh
14:59:18 <sballe_> mrhillsman: are you from rackSpace or Intel?
14:59:29 <mrhillsman> Rackspace side
14:59:32 <sballe_> Oh I see now Intel. Welcome :-)
14:59:46 <acabot> I have to close the meeting, sorry guys
14:59:49 <acabot> thank you
14:59:54 <sballe_> ok np. bye
14:59:56 <mrhillsman> mrhillsman@gmail.com
15:00:00 <dtardivel> bye
15:00:02 <acabot> #endmeeting