Thursday, 2016-07-21

*** hvprash has quit IRC00:10
*** harlowja has joined #openstack-watcher01:35
*** jed56 has quit IRC02:05
*** diga has joined #openstack-watcher04:04
*** diga has quit IRC04:05
*** diga has joined #openstack-watcher04:06
openstackgerritOpenStack Proposal Bot proposed openstack/python-watcherclient: Updated from global requirements
openstackgerritOpenStack Proposal Bot proposed openstack/watcher: Updated from global requirements
*** diga has quit IRC04:29
*** thorst_ has joined #openstack-watcher04:47
*** thorst_ has quit IRC05:07
*** thorst_ has joined #openstack-watcher05:08
*** thorst_ has quit IRC05:25
*** thorst_ has joined #openstack-watcher05:41
*** thorst_ has quit IRC05:46
*** ecelik has joined #openstack-watcher05:56
*** vincentfrancois1 has joined #openstack-watcher06:24
*** vincentfrancois1 has quit IRC06:46
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/watcher-dashboard: Remove discover from test-requirements
openstackgerritVincent Françoise proposed openstack/watcher: Refactored the compute model and its elements
openstackgerritVincent Françoise proposed openstack/watcher: Added DE Background Scheduler w/ model sync jobs
openstackgerritVincent Françoise proposed openstack/watcher: Loadable Cluster Data Model Collectors
openstackgerritVincent Françoise proposed openstack/watcher: Merged metrics_engine package into decision_engine
openstackgerritVincent Françoise proposed openstack/watcher: Updated DE architecture doc + 'period' param
openstackgerritVincent Françoise proposed openstack/watcher: Cluster data model collector plugin documentation
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/watcher: Remove discover from test-requirements
*** danpawlik has joined #openstack-watcher07:53
*** thorst_ has joined #openstack-watcher08:17
*** thorst_ has quit IRC08:21
*** thorst_ has joined #openstack-watcher09:04
*** thorst_ has quit IRC09:08
*** aspiers has quit IRC09:58
*** akijak has joined #openstack-watcher10:01
*** aspiers has joined #openstack-watcher10:11
*** vincentfrancoise has quit IRC10:11
*** akijak has quit IRC10:44
*** akijak has joined #openstack-watcher10:49
*** vincentfrancoise has joined #openstack-watcher10:51
*** aspiers has quit IRC10:52
*** aspiers has joined #openstack-watcher11:08
*** thorst_ has joined #openstack-watcher11:32
*** thorst_ has quit IRC11:36
*** vincentfrancoise has quit IRC11:41
*** vincentfrancoise has joined #openstack-watcher12:15
openstackgerritVincent Françoise proposed openstack/watcher: Fixed Basic optim tempest test
*** jed56 has joined #openstack-watcher12:52
openstackgerritMerged openstack/watcher: Remove discover from test-requirements
openstackgerritMerged openstack/watcher: Fix dict.keys() PY3 compatible
openstackgerritMerged openstack/python-watcherclient: Updated from global requirements
openstackgerritTomasz Kaczynski proposed openstack/watcher: Add scoring engines to database and API layers
*** thorst_ has joined #openstack-watcher13:12
*** thorst_ has quit IRC13:17
openstackgerritMerged openstack/watcher: Updated from global requirements
*** ecelik has quit IRC13:48
*** hvprash has joined #openstack-watcher13:58
*** hvprash has quit IRC14:02
*** hvprash has joined #openstack-watcher14:03
*** thorst_ has joined #openstack-watcher14:36
*** hvprash has quit IRC14:45
*** hvprash has joined #openstack-watcher14:46
*** hvprash has quit IRC14:50
*** diga has joined #openstack-watcher14:55
tkaczynskihi vincent-bot :)15:05
*** jed56 has quit IRC15:05
tkaczynskiI am just wondering... I will be pushing some next changes related to scoring module soon15:05
vincentfrancoiseI saw you pushed a new patchset earlier on15:06
tkaczynskiI plan to also add a sample scoring engine. it could be a real thing and for example use some ML framework15:06
tkaczynski(yes, I did - nice that you've noticed)15:06
vincentfrancoisewith the uuid field id/uuid/name field combo ^^15:07
tkaczynskiI gave up after hitting the wall with updates/soft deletes15:07
tkaczynskianyway, I have a different question: do you think it's a good idea to add some Machine Learning framework to Watcher?15:08
vincentfrancoisearen't scoring engines capable of doing some machine learning?15:09
tkaczynskifor example scipy package. but it's quite large (39 MB compressed) and it's another dependency not strictly needed15:09
*** thorst_ has quit IRC15:09
vincentfrancoiseoh, I believe this is up to the strategy developer to add extra Python dependencies to his strategy if need be15:10
vincentfrancoisein his own 3rd party project15:10
tkaczynskiwell, yes :) but they need to be implemented first :) you can implement for example a neural network yourself if you like... or you can use a library which some smart folks already did15:10
tkaczynskisure, but then the example scoring engine will be probably very simple and won't use any ML15:11
vincentfrancoiseyeah but all I'm saying is that this scipy dependecy would lie in the 3rd party alongside the 3rd party strategy and not in watcher15:11
vincentfrancoiseof course we shouldn't re=invent the wheel15:12
tkaczynskikind of like a dummy strategy - just implementing the interface, showing up in the CLI and API15:12
vincentfrancoisethat being said15:12
vincentfrancoiseif we want to provide a machine learning based strategy within Watcher15:12
*** diga has quit IRC15:12
vincentfrancoisethen the question of this dependency makes more sense to me15:13
tkaczynskiyes, but we are not doing it yet. my change is simply creating a framework for plugins, nothing more. at this moment I don't have plans to implement any real strategy using scoring engines / ML15:14
tkaczynskisorry, I did say the full truth - I will do that, but as a 3rd party (intel) plugin15:14
tkaczynskiI was just wondering if anybody would like to see some real scoring engine being built-in in watcher15:15
tkaczynskior just a dummy thing doing nothing15:16
vincentfrancoiseI guess having a fully functioning sample using the scoring engine would make a lot of sense15:16
*** hvprash has joined #openstack-watcher15:16
vincentfrancoiseso yeah maybe you can create another dummy-ish strategy using it then15:17
tkaczynskiwell the dummy one also can be made functional - it can for example calculate the maximum value from a given array ;) then there are no additional dependencies etc.15:17
tkaczynskior I could try to come up with some more complicated data model and use a library like scipy to implement it, but the facts are that this one might also not be very useful15:18
tkaczynskias creating a good data model is a job on its own and can take months!15:18
*** thorst_ has joined #openstack-watcher15:18
*** hvprash_ has joined #openstack-watcher15:19
vincentfrancoisethe only rule for the current dummy is that it should not need to call any external sevice to keep it a simple test case in our integration test15:19
vincentfrancoiseso maybe you can add a strategy parameter that can turn on a scoring engine functionality in it (that would be deactivated by default)15:20
*** hvprash has quit IRC15:20
tkaczynskiI actually created one more strategy called dummy_with_scorer, which is supposed to use some dummy_scorer - so that the whole thing can be tested and also serve as an example how to implement a strategy using some scoring engine15:21
vincentfrancoisesounds good to me then15:23
tkaczynskiI was just thinking whether there is any expectation for this dummy_scorer to be any "intelligent"15:23
*** hvprash_ has quit IRC15:23
*** thorst_ has quit IRC15:23
vincentfrancoiseDid you discuss it yesterday at the midcycle?15:23
tkaczynskiunfortunately no, maybe I can just ask this question quickly...15:24
vincentfrancoisebecause I do not personally have a clear answer to this15:24
tkaczynskibecause I think there is no clear answer :)15:25
vincentfrancoisejed56 or acabot seem better placed than me on what is expected or not15:25
tkaczynskiok, I will try to reach them out. if not today, then some other time15:25
vincentfrancoisebut IMHO, the more we can show to anyone trying watcher, the better15:26
tkaczynskisure, this is my intention. but adding a big dependency always has a cost. who knows, maybe adding this scipy package can cause some unrelated problems for watcher etc.15:27
vincentfrancoiseAt some point15:28
tkaczynskithis is why it's not a clear winner, because the scoring engine won't be that useful even with that package (I don't have time to work on the data model full time)15:28
tkaczynski... and I'm not a data scientist :)15:29
vincentfrancoisewe were discussing the eventuality of creating an new repo (openstack or not) that would centralise non-essential plugins that we would support on a best effort basis15:29
tkaczynskiyeah, maybe that would be a better place15:30
vincentfrancoiseat least that way we would be able to provide all the plugins we want without having to put too much in the "core"15:32
vincentfrancoisebut at the time we didn't do it because the effort that represents to maintain plugins in a separate repo was not yet worth it15:33
*** jed56 has joined #openstack-watcher15:35
jed56good morning UTC15:35
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/python-watcherclient: Remove discover from test-requirements
*** thorst_ has joined #openstack-watcher15:43
*** hvprash has joined #openstack-watcher15:53
*** hvprash has quit IRC15:54
*** hvprash has joined #openstack-watcher15:55
openstackgerritPrashanth Hari proposed openstack/python-watcherclient: Add goal_id, strategy_id and host_aggregate CLI options to audit
*** michaelgugino has joined #openstack-watcher16:04
*** vincentfrancoise has quit IRC16:44
*** hvprash has quit IRC16:50
*** vincentfrancoise has joined #openstack-watcher17:17
openstackgerritDrew Thorstensen proposed openstack/watcher: Add hacking checks to watcher
*** michaelgugino has quit IRC17:43
*** harlowja has joined #openstack-watcher17:44
*** harlowja has quit IRC18:35
openstackgerritTin Lam proposed openstack/watcher: Update docs links to
*** harlowja has joined #openstack-watcher18:38
*** harlowja has quit IRC18:59
*** esberglu has joined #openstack-watcher19:22
*** jed56 has quit IRC19:35
*** wootehfoot has joined #openstack-watcher19:36
openstackgerritDrew Thorstensen proposed openstack/watcher: Add hacking checks to watcher
*** harlowja has joined #openstack-watcher20:39
*** thorst_ has quit IRC21:26
*** wootehfoot has quit IRC21:33
*** thorst_ has joined #openstack-watcher21:40
*** harlowja has quit IRC21:41
*** thorst_ has quit IRC21:45
*** harlowja has joined #openstack-watcher21:48
*** harlowja has quit IRC21:48
*** thorst_ has joined #openstack-watcher21:49
*** thorst_ has quit IRC21:53
*** esberglu has quit IRC21:54
*** vincentfrancoise has quit IRC22:03
*** thorst_ has joined #openstack-watcher22:07
*** thorst_ has quit IRC22:08

Generated by 2.14.0 by Marius Gedminas - find it at!