Wednesday, 2016-03-23

*** thorst has joined #openstack-watcher00:34
*** thorst_ has joined #openstack-watcher00:35
*** thorst has quit IRC00:40
*** thorst_ has quit IRC01:27
*** thorst has joined #openstack-watcher01:27
*** thorst has quit IRC01:36
*** jwcroppe has joined #openstack-watcher01:42
openstackgerritjunjie.huang proposed openstack/watcher: Workload balance migration strategy implementation
*** vtech has quit IRC02:27
*** vtech has joined #openstack-watcher02:27
*** thorst has joined #openstack-watcher02:34
*** thorst has quit IRC02:41
*** jwcroppe has quit IRC03:33
*** jwcroppe has joined #openstack-watcher03:34
*** thorst has joined #openstack-watcher03:39
*** jwcroppe has quit IRC03:39
*** thorst has quit IRC03:46
*** jwcroppe has joined #openstack-watcher04:35
*** thorst has joined #openstack-watcher04:44
*** jwcroppe has quit IRC04:45
*** thorst has quit IRC04:52
*** jwcroppe has joined #openstack-watcher05:41
*** jwcroppe has quit IRC05:49
*** thorst has joined #openstack-watcher05:49
*** thorst has quit IRC05:55
openstackgerritTaylor Peoples proposed openstack/watcher-specs: WIP: Cluster model objects wrapper
*** apoorv has joined #openstack-watcher06:13
*** apoorv has quit IRC06:35
*** jwcroppe has joined #openstack-watcher06:46
*** apoorv has joined #openstack-watcher06:49
*** jwcroppe has quit IRC06:53
*** thorst has joined #openstack-watcher06:53
*** apoorv has quit IRC06:59
*** thorst has quit IRC07:01
*** wootehfoot has quit IRC07:11
*** vtech has quit IRC07:42
*** jwcroppe has joined #openstack-watcher07:50
*** thorst has joined #openstack-watcher07:58
*** jwcroppe has quit IRC08:00
*** dtardivel has joined #openstack-watcher08:00
*** vtech has joined #openstack-watcher08:02
*** thorst has quit IRC08:06
*** apoorv has joined #openstack-watcher08:21
apoorvvincent: thanks a lot you saved much effort08:21
*** vincentfrancoise has joined #openstack-watcher08:29
acabotagenda for our weekly meeting open :
openstackgerritMerged openstack/watcher-specs: Select destination filter for live migration
openstackgerritMerged openstack/watcher-specs: Added doc8 for specs validation
*** jed56 has joined #openstack-watcher08:44
*** jwcroppe has joined #openstack-watcher08:56
*** thorst has joined #openstack-watcher09:03
*** openstackgerrit has quit IRC09:03
*** openstackgerrit has joined #openstack-watcher09:03
*** vtech_ has joined #openstack-watcher09:06
*** vtech has quit IRC09:06
openstackgerritjunjie.huang proposed openstack/watcher: Workload balance migration strategy implementation
*** thorst has quit IRC09:11
*** thorst has joined #openstack-watcher10:08
*** thorst has quit IRC10:16
*** wootehfoot has joined #openstack-watcher10:22
openstackgerritTomasz Kaczynski proposed openstack/watcher-specs: Add specification for Watcher Scoring Module
*** wootehfoot has quit IRC10:50
*** sudipto has joined #openstack-watcher10:53
sudiptoHi there. I have installed watcher and wanted to get some idea on a few operations that i could perform using it. I couldn't find documentation that would explain what user commands i could execute to let's say trigger an audit etc...can someone help pls?10:55
sudiptoI could find the installation guides explain how to configure/install watcher...but didn't find a doc on how to use watcher as yet...10:59
vincentfrancoiseHi sudipto11:00
sudiptoHi vincentfrancoise11:00
vincentfrancoiseThe Watcher documentation is currently available at
vincentfrancoiseIf you want to get started with it11:01
sudiptovincentfrancoise, thanks. i am following through some usage guidelines there.11:01
vincentfrancoiseyou can have a look at where of Watcher CLI commands are explained11:01
sudiptoyeah just checked. thx :)11:02
vincentfrancoisefeel free to ask if you need help ;)11:03
*** sudipto has quit IRC11:13
*** thorst has joined #openstack-watcher11:35
*** jinquan has joined #openstack-watcher11:46
*** apoorv has quit IRC12:35
jed56hello sballe_13:00
*** alexchadin has joined #openstack-watcher13:03
acabothi alexchadin13:04
alexchadingood day, acabot!13:04
acabotthere are currently 24 open comments on your spec, when do you plan to add a new PS ?13:05
alexchadinupdated spec?13:05
acabota new patch set13:06
alexchadinI'm working on it, hope it will be done tomorrow or by friday.13:07
acabotgreat thx13:07
alexchadintrying to provide it in more clear and better form13:07
alexchadinI'll be on meeting in an hour anyway.13:09
*** alexchadin has quit IRC13:10
*** jwcroppe has quit IRC13:12
vtech_Hey guys, just a quick question, we noticed that in the decision engine model you represent VM state using string -
vtech_using enum.value13:28
vtech_but in hypervisor you use enum object directly13:29
vtech_is there a reason for that?13:29
vincentfrancoisehi vtech_13:30
jed56hello vtech_13:30
jed56there is not reasons13:31
vincentfrancoise+1 ^13:31
jed56we will fix that we the blueprint object-wrapper13:31
jed56sorry  cluster-model-objects-wrapper13:31
vtech_ok, then my question is: is it 100% sure the strategy recieves a model with VMs which states are str type?13:32
*** seanmurphy has joined #openstack-watcher13:33
vtech_I only found
vtech_which should be string13:35
vtech_well, in any case I will have to recheck the strategy for that.13:38
jed56we should use string13:41
jed56to be consistent13:41
jed56in my opinion13:41
jed56this is a error ( my in this case) to handle sometime with Enum sometime with string :)13:42
*** lrensing has joined #openstack-watcher13:46
vtech_ok then I will try to use resource.state == resource.STATE.value for both vms and hypervisors13:46
vtech_e.g. vm.state != vm_state.VMState.ACTIVE.value rather then vm.state != vm_state.VMState.ACTIVE13:47
vtech_it can be a bit misleading - if the types doesn't match it will produce False using the == operator rather then raising an exception13:50
jed56I agree13:51
jed56do you think we should check the state of the vm in the strategies ?13:51
jed56In my opinion, we can check that in the action or let nova manage that13:52
vtech_a possibility of checking VM state  in strategy allows strategies to adjust e.g. correct migration type, so generally I think it's a good idea to have this information there13:54
vtech_e.g. as watcher so far only supports live migration (and block live migration) it only can migrate VMs in the active state.13:55
vtech_and with regards to hypervisor state type, I am pretty sure it's a string in the strategy, but an enum object here
jed56In my opinion we don't want that the strategy have to manage this use cases. We should focus on the strategy itself. if the strategy says migrate this virtual machine nova have to manage handle case if possible ( enough place, constraints,ect)13:58
acabottime for weekly meeting13:59
jed56let's go :)14:00
*** hvprash has joined #openstack-watcher14:01
*** alexchadin has joined #openstack-watcher14:02
*** vtech_ has quit IRC14:03
*** vtech has joined #openstack-watcher14:04
*** openstack has joined #openstack-watcher14:21
*** aspiers has joined #openstack-watcher14:23
*** jed561 has quit IRC14:25
*** alexchadin has quit IRC15:04
*** jinquan has left #openstack-watcher15:04
*** sudipto has joined #openstack-watcher15:08
*** seanmurphy has quit IRC15:12
vtechjed56, to continue the conversation, I think the main point of strategy is not to only say migrate VM, but you should also specify where do yo want to migrate from many different reasons. More information in cluster model within strategy allows better control (and possibly better optimization) within the strategy itself.15:20
jed56I agree for the where but not for the "how"15:23
jed56can you give a example ?15:24
vteche.g. I saw the current implementation of live migrate action use try-fail-retry approach - try to live migrate a machine which fails if there is no shared storage between src and dst hypervisors and then try again with block-migration flag. The first failure could be avoided if there is an information whether the shared storage is available. but in this case i still agree it should be handled by nova since we are still talking about live migration,15:35
vtechthen there is a cold migration in nova which is not the same anymore.15:35
vtechbut yes if nova can choose the best type of migration on its own I agree that would be the best solution.15:36
vincentfrancoisevtech: the 'auto' option is now available in Nova15:37
vtechdoesn't mean that when you attempt to live migrate a machine which is not "live migratable" it will default to cold migration?15:38
vtech*does it15:39
vincentfrancoisethe auto is only between block and non-block15:40
vtechthat's the problem15:40
vtechit is still a live migration15:40
vtechif you have a shutdown VM you cannot move it with this operation.15:41
vincentfrancoiseOh ok that's why you want to know about the state15:41
vtechauto between block and nonblock is understandable15:41
vincentfrancoiseI guess that by default the migration action should deal with live/non-live by itself though we should still be able to force the former or the latter from the strategy15:43
vtechmy point is, watcher should also support cold migration to cover these cases. At least until nova starts to be smart enough to choose migration type on it's own. which would essentially meant to marge live- and cold- migration terms to one (e.g. migration).15:44
vincentfrancoiseif you want to do it, I would be more than happy to let you do so ;)15:45
vincentfrancoiseBut at least a whishlist bug or a BP should be created to mention this15:46
openstackgerritVojtech Cima proposed openstack/watcher: Integrated consolidation strategy with watcher
vtechvincentfrancoise: I quite busy with some other stuff now, but I will take a look15:52
openstackgerritJeffrey Augustine proposed openstack/watcher: Added oslo.context to requirements.txt
*** jaugustine has joined #openstack-watcher15:53
*** hvprash_ has joined #openstack-watcher16:06
*** hvprash has quit IRC16:06
*** hvprash has joined #openstack-watcher16:08
*** hvprash_ has quit IRC16:11
vincentfrancoisevtech: ok no problem16:19
*** brunograz has joined #openstack-watcher16:28
brunograzHi everyone16:29
vincentfrancoiseHi brunograz16:29
brunograzI'm getting the following error when trying to start an action-plan16:29
brunograzClient-side error: Couldn't apply patch '{'path': '/state', 'value': u'TRIGGERED', 'op': 'replace'}'. Reason: Invalid state: TRIGGERED format_exception /root/watcher/watcher_env/lib/python2.7/site-packages/wsme/
brunograzbut the action plan is in RECOMMENDED state16:30
brunograzcould someone help me out with this?16:30
vincentfrancoiseThere was a renaming recently16:30
vincentfrancoisethe TRIGGERED state was renamed as PENDING16:30
vincentfrancoiseso pull the latest version of python-watcherclient and you should be good to go16:31
*** jwcroppe has joined #openstack-watcher16:34
*** vincentfrancoise has left #openstack-watcher16:37
*** vincentfrancoise has joined #openstack-watcher16:37
brunograzthat worked16:37
*** brunograz has quit IRC16:58
*** vtech has quit IRC17:03
*** lrensing has quit IRC17:16
*** vtech has joined #openstack-watcher17:31
*** Kevin_Zheng has quit IRC17:32
openstackgerritVincent Françoise proposed openstack/watcher: Added Goal and Strategy into Watcher DB
openstackgerritVincent Françoise proposed openstack/watcher: Added Goal object
openstackgerritVincent Françoise proposed openstack/watcher: Added Goal in Strategy + Goal API reads from DB
openstackgerritVincent Françoise proposed openstack/watcher: Add strategy & goal fields in audit template
*** xenogear has joined #openstack-watcher17:47
*** xenogear has quit IRC17:47
*** vincentfrancoise has quit IRC17:49
*** mestery_ has joined #openstack-watcher18:28
*** mestery has quit IRC18:33
*** mestery_ is now known as mestery18:33
*** mestery_ has joined #openstack-watcher18:34
*** mestery_ has quit IRC18:46
*** openstack has joined #openstack-watcher19:07
*** openstack has joined #openstack-watcher19:20
*** hvprash_ has quit IRC19:21
sballe_please review:
*** hvprash has joined #openstack-watcher20:11
*** hvprash__ has quit IRC20:12
*** hvprash has quit IRC20:18
*** openstack has joined #openstack-watcher20:31
*** dtardivel has quit IRC21:08
*** thorst has quit IRC21:11
*** thorst has joined #openstack-watcher21:12
*** thorst_ has joined #openstack-watcher21:14
*** thorst__ has joined #openstack-watcher21:16
*** thorst has quit IRC21:17
*** thorst_ has quit IRC21:18
*** thorst__ has quit IRC21:21
*** thorst has joined #openstack-watcher21:34
*** thorst has quit IRC21:38
*** jaugustine has quit IRC23:04
*** openstack has joined #openstack-watcher23:22

Generated by 2.14.0 by Marius Gedminas - find it at!