14:00:09 <acabot__> #startmeeting watcher
14:00:10 <openstack> Meeting started Wed Feb 24 14:00:09 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:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:13 <openstack> The meeting name has been set to 'watcher'
14:00:16 <acabot__> hi
14:00:18 <edleafe> \o
14:00:21 <seanmurphy> hi all
14:00:25 <jed56> (O_O)
14:00:30 <brunograz> hi
14:00:36 <tkaczynski> hi
14:00:43 <acabot__> meeting agenda #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#02.2F24.2F2016
14:00:47 <vtech_> o/
14:00:57 <vincentfrancoise> o/
14:01:00 <tpeoples> o/
14:01:20 <gzhai> hi
14:01:36 <acabot__> #topic Announcements
14:02:06 <dtardivel> hi
14:02:22 <acabot__> #info dtardivel nominates vincentfrancoise as a Watcher core contributor
14:02:37 <acabot__> we had a couple of +1 on the ML
14:03:02 <jed56> even a +2
14:03:10 <jed56> :)
14:03:11 <gzhai> +1
14:03:11 <acabot__> does anybody "dont want" vincentfrancoise as a core ? :-)
14:03:38 <gzhai> vincent did a great job.
14:04:10 <acabot__> I also think so
14:04:13 <tpeoples> +1
14:04:48 <acabot__> #action dtardivel set vincentfrancoise as core contributor on watcher, python-watcherclient & watcher-dashboard
14:05:14 <dtardivel> acabot__: done :)
14:05:21 <acabot__> #info mid-cycle highlights have been shared through the ML
14:05:21 <vincentfrancoise> I was already core on watcher-dashboard since I was the one creating the project :)
14:05:48 <acabot__> if I missed something important in the list please reply to it
14:06:00 <acabot__> #link http://lists.openstack.org/pipermail/openstack-dev/2016-February/087174.html
14:06:15 <vincentfrancoise> BTW, maybe we should discuss on who is to be core on watcher-dashboard at some point
14:07:11 <acabot__> true, do we have any candidate to become core on watcher-dashboard ?
14:07:11 <acabot__> or we can do it through the ML
14:07:50 <acabot__> today we only have vincentfrancoise right ?
14:07:51 <vincentfrancoise> FYI, dtardivel and I are the only core on watcher-dashboard
14:07:56 <acabot__> ok
14:08:41 <acabot__> tpeoples gzhai : do you want to be part of the watcher-dasboard core ?
14:09:07 <acabot__> we can wait for more contributors related to horizon stuff
14:09:18 <gzhai> I want more time for watcher...
14:09:23 <tpeoples> doubtful, i'm not all that interested in UI side / JS. let me have more of a look and get back to you
14:10:39 <acabot__> ok lets continue with vincentfrancoise & dtardivel as core for now
14:11:05 <acabot__> any other annoucement from the team ?
14:11:18 <vincentfrancoise> It's just that we need to make sure we take this new project into account whenever writing new BPs
14:12:04 <tpeoples> for sure vincentfrancoise
14:12:27 <gzhai> I'll attend openstack hackathon in Chengdu, China. And ask for a slot for watcher presentation:)
14:12:46 <acabot__> gzhai : great !
14:13:02 <gzhai> Will use some previous slides to introduce watcher to China openstack community.
14:13:05 <vmahe> hi
14:13:17 <dtardivel> watcher-dashboard tagged 0.0.1 available  ( + online doc, + docker container image watcher/dashboard)
14:13:34 <tpeoples> i apologize for my lack of activity in the past week and a half. that is going to change.. jfyi if you were wondering where the heck i've been :(
14:13:38 <acabot__> #info gzhai will try to introduce Watcher to an openstack hackathon in Chengdu, China
14:14:05 <acabot__> tpeoples : yes we thought you were in vacation :-D
14:14:06 <dtardivel> gzhai: +1
14:14:49 <tpeoples> i had to move offices, lots of other stuff going on. like i said, it will change
14:15:08 <tpeoples> if not kick me out
14:15:10 <tpeoples> :)
14:15:16 <acabot__> dtardivel shouldn't we align versions between watcher, watcher-pythonclient and watcher-dashboard at some point ?
14:15:33 <tkaczynski> tpeoples: no worries, I did the code review in the meantime and added some comments
14:16:17 <dtardivel> gzhai: what will be the number of your attendees ?
14:16:36 <gzhai> 30~40 in last year.
14:16:50 <acabot__> #topic Review Action Items
14:16:54 <gzhai> big company in china, like Huawei, 99cloud.
14:17:04 <dtardivel> acabot__: not necessary ...
14:17:18 <vincentfrancoise> gzhai: nice!
14:17:34 <acabot__> gzhai : I'm on the Huawei booth right now at Mobile World Congress ;-)
14:17:45 <gzhai> :)
14:17:50 <tpeoples> dtardivel: because they should be able version agnostic? e.g., python-watcherclient should be able to interact with a watcher backend of a different version?
14:17:59 <gzhai> Huawei put a lot of resources for openstack.
14:20:18 <acabot__> tpeoples : as think that until we are in version 0.x, you need to get the latest version of each component to run Watcher, right ?
14:20:20 <dtardivel> tpeoples: python-watcherclient should support different version of watcher API.
14:20:22 <vincentfrancoise> tpeoples: I guess we just need to stabilize watcher-dashboard a little more before aligning the versions
14:20:36 <acabot__> vincentfrancoise ok
14:20:49 <acabot__> lets move on watcher specs
14:21:01 <tpeoples> acabot__: i think that is only true in these early stages where we aren't worrying about backwards compatibility. in the future that shouldn't be necessary
14:21:09 <jed56> vincentfrancoise : we don't have to align the version
14:21:11 <tpeoples> +1 vincentfrancoise
14:21:15 <vincentfrancoise> The 0.0.1 tag was put just so we can generate the docker containers, otherwise we wouldn't have tagged it
14:21:16 <jed56> we can but this is not mandatory
14:21:42 <jed56> since we have the api compatibility
14:21:52 <acabot__> i'm just concerned about the distance between 0.0.1 & 0.23 :-)
14:22:13 <jed56> this is a problem ? :)
14:22:25 <vincentfrancoise> I reckon we can deal with in Newton if needed
14:22:49 <acabot__> jed56 : not really, just that 0.1 could have been better ;-)
14:23:13 <dtardivel> acabot: watcher, python-watcherclient and watcher-dashboard are independent project, with independent life-cycle. We just implemented and pushed a beta PROD version of the dashboard, so this is the reason of version 0.0.1 today.
14:23:29 <jed56> yes but our 0.1 is quite stable
14:23:30 <jed56> :)
14:23:57 <acabot__> jed56 dtardivel : Ok i'm fine with that guys
14:24:27 <jed56> one commit => 0.0.1  : )
14:24:34 <jed56> two commit 0.1
14:24:35 <jed56> lol
14:24:38 <acabot__> #info Efficacy indicators specs has been merged too fast and we realized that it needs improvements
14:24:50 <jed56> three commit 1.0 stable
14:25:02 <gzhai> :)
14:25:06 <acabot__> so there is a new review open https://review.openstack.org/#/c/283449/, sorry for the confusion
14:25:51 <acabot__> we have 2 specs open for a long time now (ZHAW strategy & workload balance strategy)
14:25:56 <gzhai> acabot__: I'm looking at this.
14:26:16 <acabot__> I suggest to merge them by EOW
14:26:34 <acabot__> seanmurphy vtech : what do you think ?
14:26:41 <seanmurphy> to merge the 2 strategies?
14:26:45 <seanmurphy> i saw this in the agenda
14:26:54 <seanmurphy> we are doing our implementation as you might have seen
14:27:09 <seanmurphy> there is the point that they seem to be contradictory
14:27:14 <seanmurphy> at least at the initial glance
14:27:34 <acabot__> no no sorry
14:27:35 <seanmurphy> one focused on consolidation and one focuses on even distribution of load iiuc
14:27:56 <acabot__> not merge the 2 strategies into one but having both specs merged in gerrit :-)
14:28:09 <seanmurphy> ok
14:28:20 <acabot__> my sentence is confusing :-)
14:28:28 <seanmurphy> i don’t understand the advantages/disadvantages of this tbh
14:28:55 <seanmurphy> i did not read the spec for the workload balance strategy
14:29:15 <gzhai> Who can help to review workload balance?
14:29:16 <acabot__> seanmurphy : could you have a look at it by EOW ?
14:29:27 <seanmurphy> form our selfish perspective, we would say ‘what is the benefit of this?'
14:29:35 <seanmurphy> and also ‘does it mean we would have to change our implementation
14:29:42 <seanmurphy> for sure i can look
14:30:14 <acabot__> seanmurphy : not sure to follow you, are you taking about the process of merging the spec in watcher-spec repo ?
14:30:16 <seanmurphy> not that we don’t want to be constructive, but i’m just unclear on what the point is/what the benefit is
14:30:33 <seanmurphy> ah - sorry
14:30:43 <seanmurphy> confusion - my bad
14:30:52 <seanmurphy> so you’re not talking abt merging them into each other
14:30:53 <seanmurphy> right
14:31:21 <seanmurphy> ok - if it’s just a q of whether our strategy can be merged by eow
14:31:26 <seanmurphy> then this is doable
14:31:27 <acabot__> seanmurphy: ok back on our feet
14:31:38 <jed56> woah I was lost :)
14:31:45 <vincentfrancoise> +1
14:32:03 <seanmurphy> regarding the workload balance issue - we can provide a review of this
14:32:25 <acabot__> #action seanmurphy acabot review specs https://review.openstack.org/#/c/271028/ & https://review.openstack.org/#/c/276586/ by EOW
14:33:13 <jed56> you can add me
14:34:08 <acabot__> gzhai : I think we need more reviews on https://review.openstack.org/#/c/274688/, what do you think ?
14:34:08 <acabot__> #action jed56 review specs https://review.openstack.org/#/c/271028/ & https://review.openstack.org/#/c/276586/ by EOW
14:34:46 <gzhai> +1
14:36:07 <acabot__> vmahe I think we should look at the impact we discussed on efficacy indicators on the input parameters specs
14:36:42 <jed56> +1
14:37:01 <vmahe> +
14:37:05 <vmahe> +1
14:37:25 <acabot__> #action vmahe review https://review.openstack.org/#/c/274688/
14:37:48 <acabot__> we have a couple of BPs with high priority that needs specs
14:38:14 <acabot__> tomasz is setting up devstack before starting the scoring module
14:38:35 <acabot__> tpeoples: what about the objects wrapper ?
14:38:46 <jed56> tomasz: did you success to setup devstack ?
14:38:56 <tpeoples> acabot__: i *will* get a spec for that in next 2 days
14:39:37 <tpeoples> i saw tomasz' comments on the devstack review... i will make a few more updates there
14:39:40 <acabot__> #action tpeoples submit a drafted spec for https://blueprints.launchpad.net/watcher/+spec/cluster-model-objects-wrapper
14:39:42 <acabot__> thx
14:40:09 <dtardivel> tpeoples: I will review it after
14:40:17 <acabot__> I will submit a spec for https://blueprints.launchpad.net/watcher/+spec/select-destinations-filter
14:40:30 <tkaczynski> jed56 I'm very close. I have controller + compute nodes, able to boot vm, but live migration is not working. troubleshooting it now, got some help from other openstack contributors here in Gdansk
14:40:35 <acabot__> #action acabot submit a drafted spec for https://blueprints.launchpad.net/watcher/+spec/select-destinations-filter
14:41:21 <dtardivel> tkaczynski: maybe, we can help you on live migration. Is it on NFS setup ?
14:41:29 <tpeoples> tkaczynski: are you using multiple virtualbox VMs? just curious
14:41:34 <acabot__> we can jump to devstack doc improvements ;-)
14:42:40 <tkaczynski> yes, NFS is working fine. there was some unclear error in the n-cpu logs, we suspect libvirt or qemu problem, but need to investigate
14:42:57 <tpeoples> tkaczynski: did you set up SSH keys?
14:43:17 <tkaczynski> yes, of course. and confirmed with ssh to/from stack/root
14:43:26 <tpeoples> hmm ok
14:43:35 <tkaczynski> and yes, using 2 virtualbox VMs
14:43:41 <tpeoples> cool
14:44:23 <acabot__> #info 17 bug fixes are in review, so we need reviewers
14:44:32 <tkaczynski> once I have it configured, I plan to setup the whole thing again and document it, so I can repeat that process
14:44:42 <tpeoples> #action tpeoples review
14:44:57 <acabot__> I assume that with vincentfrancoise as core it will be easier to merge them
14:44:59 <tpeoples> tkaczynski: that would be awesome if we add that to our docs
14:45:32 <acabot__> tpeoples: +1
14:46:20 <acabot__> nothing new on python-watcherclient
14:46:35 <acabot__> #info initial commit for watcher-dashboard has been merged
14:46:52 <acabot__> #action acabot set-up launchpad for watcher-dashboard
14:47:15 <acabot__> #topic Blueprint/Bug Review and Discussion
14:48:01 <brunograz> tkaczynski: we have an old blog post about setting live migration in Openstack - it might be helpful #link https://blog.zhaw.ch/icclab/setting-up-live-migration-in-openstack-icehouse/
14:48:24 <acabot__> we need to start implementing workload balance strategy if we want to demonstrate it in Austin
14:48:44 <acabot__> gzhai : do you have any update on junjie stuff ?
14:48:54 <tkaczynski> brunograz thanks, I'll definitely have a look there
14:49:22 <gzhai> acabot__: He is working on the specs.
14:49:59 <gzhai> we are preparing the algothm to start working on workload migration spec.
14:50:55 <acabot__> did he starts implementing or not yet ?
14:51:43 <gzhai> acabot__: not yet. We will start soon.
14:52:24 <gzhai> And want to more review for the spec to avoid unnecessary work:)
14:52:49 <jed56> gzhai i will
14:53:15 <gzhai> jed56: thanks
14:54:15 <jed56> ping acabot_
14:54:26 <acabot_> back
14:54:36 <acabot_> sorry wifi disconnection
14:54:59 <acabot_> #topic Open Discussion
14:54:59 <acabot_> #topic Open Discussion
14:55:37 <acabot_> ping jed56
14:55:48 <seanmurphy> we have a blog post which we’re writing in which we mention watcher and the fact that we’re contributing to it - it’s for an eu proj
14:56:12 <acabot_> seanmurphy: looks great
14:56:34 <acabot_> #info seanmurphy will write a blog post mentionning Watcher contributions
14:56:50 <seanmurphy> yep - it’s already drafted - it will go out this week
14:56:50 <dtardivel> acabot_: is implementation of Watcher policy.json file mandatory for m3 ?
14:57:14 <acabot_> dtardivel: no its not
14:57:37 <acabot_> not in my mitaka-3 list...
14:57:59 <acabot_> you mean this one https://blueprints.launchpad.net/watcher/+spec/watcher-policies ?
14:58:24 <acabot_> its not targeted yet so Newton
14:58:37 <dtardivel> acabot_: yes I do
14:59:18 <acabot_> thank you guys
14:59:24 <tpeoples> ttyl
14:59:40 <seanmurphy> ttyl
14:59:42 <acabot_> bye
14:59:45 <brunograz> bye
14:59:46 <dtardivel> adiós Antoine
14:59:47 <vincentfrancoise> bye
14:59:49 <gzhai> bye
14:59:49 <jed56> bye
14:59:51 <edleafe> bye
14:59:55 <acabot_> #endmeeting
14:59:58 <tkaczynski> bye
15:01:32 <edleafe> acabot_: you have to #endmeeting with the same nick you started it with
15:01:52 <edleafe> e.g., 'acabot__' (two underscores)
15:02:00 <acabot_> right
15:02:55 <acabot__> #endmeeting