Thursday, 2017-01-12

*** jwcroppe has joined #openstack-watcher00:22
*** zhurong has joined #openstack-watcher00:28
*** hanrong has left #openstack-watcher00:40
*** thorst_ has joined #openstack-watcher00:53
*** thorst_ has quit IRC00:58
*** thorst_ has joined #openstack-watcher01:17
*** hidekazu has joined #openstack-watcher01:30
openstackgerritlicanwei proposed openstack/watcher: check the state of action plan  https://review.openstack.org/39138301:56
*** thorst_ has quit IRC02:38
*** thorst_ has joined #openstack-watcher02:39
*** thorst_ has quit IRC02:43
openstackgerritlicanwei proposed openstack/python-watcherclient: Add param 'goal' and 'strategy' in list()  https://review.openstack.org/41779003:30
*** zhurong has quit IRC03:39
*** sferna1_ has joined #openstack-watcher04:00
*** diga has joined #openstack-watcher04:21
*** adisky_ has joined #openstack-watcher05:18
*** thorst_ has joined #openstack-watcher05:40
*** thorst_ has quit IRC05:44
*** absubram has quit IRC06:17
*** zhurong has joined #openstack-watcher06:23
*** thorst_ has joined #openstack-watcher06:40
*** Yumeng__ has joined #openstack-watcher06:44
*** thorst_ has quit IRC06:45
*** logan- has quit IRC07:47
*** logan- has joined #openstack-watcher07:56
*** vincentfrancoise has joined #openstack-watcher08:24
*** diga has quit IRC08:26
*** alexchadin has joined #openstack-watcher08:30
alexchadingood morning08:34
vincentfrancoisealexchadin: morning08:37
vincentfrancoisehow were your holidays?08:38
*** jwcroppe has quit IRC08:41
alexchadinvincentfrancoise: great:) 8 days in Prague and Wien08:41
*** thorst_ has joined #openstack-watcher08:41
*** jwcroppe has joined #openstack-watcher08:42
vincentfrancoiseWunderbar! I hope you enjoyed the beers they have in both places!08:42
*** jwcroppe has quit IRC08:46
*** thorst_ has quit IRC08:46
alexchadinvincentfrancoise: very tasty beer!08:50
*** tmetsch has joined #openstack-watcher08:54
*** hidekazu has quit IRC09:11
openstackgerritAlexander Chadin proposed openstack/watcher-specs: Add improvements to Applier to make it parallel  https://review.openstack.org/41307909:17
*** Yumeng__ has quit IRC09:21
vincentfrancoisealexchadin: did you have a look at the code I pushed following our discussion on the planner with validate_parents() ?09:37
alexchadinvincentfrancoise: not yet, I manage with my patches and then will take a look at yours09:38
vincentfrancoisealexchadin: ok, just give me your thoughts about it once you get to it ;)09:38
alexchadinvincentfrancoise: of course, there will be a lot of pings :D09:40
vincentfrancoisealexchadin: feel frree ;)09:40
*** dtardivel has joined #openstack-watcher09:44
*** zhurong has quit IRC09:44
openstackgerritAlexander Chadin proposed openstack/python-watcherclient: Add functional tests to watcherclient  https://review.openstack.org/38918109:51
openstackgerritAlexander Chadin proposed openstack/python-watcherclient: Support parents field along with planner changes  https://review.openstack.org/40912609:51
*** akuleshov has joined #openstack-watcher09:55
*** alexchadin has quit IRC09:56
*** alexchadin has joined #openstack-watcher09:56
akuleshovHi team! I've been digging through code of WorkloadBalance and WorkloadStabilization strategies and it seems that they use their own logic for choosing a host to migrate a VM to without leveraging nova scheduler. Are there any plans to use nova scheduler from watcher to get an initial list of eligible hosts for VM migration (so that availability zones are respected, for example)?10:03
vincentfrancoisehi akuleshov10:04
vincentfrancoisethis is a very good question10:05
vincentfrancoiseas of now nova does not provide any way to submit a VM candidate to the nova scheduler to see if it can be migrated to a given node10:07
vincentfrancoisethe nova guys know about this and that's why they are introducing a placement API10:08
vincentfrancoisethere was a spec submitted on our side explaining this problem (see https://review.openstack.org/#/c/329873/)10:09
akuleshovOh, I haven't heard about that, will look it up. I was thinking about using nova scheduler's RPC API directly or maybe extending nova's REST API. Thanks for the info! Will dig a bit more.10:10
vincentfrancoiseah the RPC API thing :)10:11
vincentfrancoisethis is a somewhat sensitive subject. Watcher should not use the RPC API of Nova to do this and we should only pass through their Rest API10:13
vincentfrancoisebut you can fork/extend Watcher to do so if you want but we cannot maintain this in the main repo10:14
*** zhurong has joined #openstack-watcher10:25
openstackgerritAlexander Chadin proposed openstack/watcher-specs: Add improvements to the planner and workflow mechanisms  https://review.openstack.org/38587110:30
*** alexchadin has quit IRC10:34
*** alexchadin has joined #openstack-watcher10:34
*** alexchadin has quit IRC10:38
*** alexchadin has joined #openstack-watcher10:38
*** thorst_ has joined #openstack-watcher10:42
*** thorst_ has quit IRC10:47
*** zhurong has quit IRC11:15
*** alexchadin has quit IRC11:50
*** alexchadin has joined #openstack-watcher12:06
*** alexchadin has quit IRC12:07
*** alexchadin has joined #openstack-watcher12:07
*** alexchadin has quit IRC12:07
*** alexchadin has joined #openstack-watcher12:08
*** alexchadin has quit IRC12:08
*** alexchadin has joined #openstack-watcher12:09
*** alexchadin has quit IRC12:09
*** sferna1_ has quit IRC12:32
akuleshovAnother question: are there any plans for implementing DRS in nova scheduler itself? I mean to make nova scheduler responsible not only for the initial placement of the VM, but for dynamic VM rescheduling? The reason I'm asking this is because I'm concerned about race conditions between watcher audits and new VM placements.12:35
*** alexchadin has joined #openstack-watcher12:41
*** thorst_ has joined #openstack-watcher12:46
vincentfrancoiseakuleshov: the question you are asking is again a matter of which project should do what12:51
vincentfrancoiseoverall, "vanilla" Watcher is only supposed to intervene after the initial placement which is handled by Nova12:52
vincentfrancoisehowever, you can implement a Nova scheduler plugin that would then call Watcher to handle all scheduling tasks if need be, although that's not our primary objective12:54
vincentfrancoiseas of now Watcher only focuses on compute resources12:54
vincentfrancoisebut the idea would be to extend it to storage and network resources as well12:55
vincentfrancoiseakuleshov: I personally wasn't the one handling most of these discussions with the other teams so that's pretty much the extent of my knowledge on the matter12:58
openstackgerritMatthew J Black proposed openstack/puppet-watcher: Allow python-memcache install from authtoken class  https://review.openstack.org/41920112:59
akuleshovMy primary concern is that currently watcher is not aware of new VM placements and action plans built by watcher will most likely become outdated if new VMs are created after the audit, so I'm interested to know what are the plans for handling these situations.13:04
akuleshovThe spec that you mentioned (Watcher should enforce the Nova policies) briefly mentions this and suggests validating each action against nova scheduler before execution, but that doesn't solve the problem of candidate host becoming an unsuitable target for VM migration because some new VMs were created on it after watcher has formed an action plan.13:05
*** tmetsch has quit IRC13:08
vincentfrancoiseakuleshov: ok so for the new VMs coming in, it's not currently handled but the idea will be to play it safe and mark as superseded all the action plans that are in the RECOMMENDED state13:12
vincentfrancoiseakuleshov: we now have the notifications handlers for nova notifications, we "just" need to enforce the rule13:12
vincentfrancoisewhat is about to be merged though is the fact that if an action plan is triggered, all the other action plans will be subsequently marked as SUPERSEDED13:14
alexchadinvincentfrancoise: ping13:15
vincentfrancoiseakuleshov: as for the second question you asked13:15
alexchadinvincentfrancoise: https://review.openstack.org/#/c/415505/2/watcher/decision_engine/planner/weight.py line 13213:16
vincentfrancoiseakuleshov: the problem is kind of shared between what should Watcher do and on the other hand, what should Nova do13:16
alexchadinvincentfrancoise: actions are list here?13:17
vincentfrancoisealexchadin: pong13:17
vincentfrancoisealexchadin: let me have a look13:17
vincentfrancoisealexchadin: yes, it's a list of dict coming from solution.actions13:19
vincentfrancoisealexchadin: oh no sorry13:20
alexchadinvincentfrancoise: but this is not full list of actions, right?13:20
vincentfrancoisealexchadin: it's a list of objects.Action()13:20
vincentfrancoisethat are built using solution.actions13:20
alexchadinvincentfrancoise: I mean, actions are separeted by weights13:20
alexchadinseparated*13:20
vincentfrancoisealexchadin: at line 20913:20
vincentfrancoiseyes that's a limitation to simplify the implementation13:21
vincentfrancoisealexchadin: does the code make sense to you?13:23
alexchadinIMHO it is more hard to understand code than my solution13:24
alexchadinI will continue to read it13:24
vincentfrancoisealexchadin: yes but we have no coupling between the decision engine and the applier13:24
vincentfrancoisealexchadin: this was something I also discussed with jed56 BTW13:24
alexchadinvincentfrancoise: line 112 and 11313:30
alexchadinvincentfrancoise: could you please describe it?13:31
vincentfrancoiseHow about:13:33
vincentfrancoiseSplit a flat list in a list of chunks of size n.e.g chunkify([0, 1, 2, 3, 4], 2) -> [[0, 1], [2, 3], [4]]13:33
edleafeakuleshov: Hi, I'm currently working on the placement API. The long-term plan is to provide an API that will allow you to specify an instance to be migrated and a list of potential hosts, and then return a list of those hosts that are "acceptable" for that instance13:49
edleafeakuleshov: "acceptable" meaning that the host satisfies not only the raw resource requirements, but also any higher stuff like affinity requirements13:50
edleafeakuleshov: We hope to have much of that done by the end of Pike, but nothing's guaranteed.13:51
*** absubram has joined #openstack-watcher13:51
akuleshovedleafe: Thanks for the info13:54
vincentfrancoiseedleafe: sounds good BTW :)13:54
edleafeakuleshov: you're welcome13:55
*** lamt has joined #openstack-watcher13:57
*** absubram has quit IRC14:00
*** absubram has joined #openstack-watcher14:00
openstackgerritDavid TARDIVEL proposed openstack/watcher: Add first alembic version for db migration  https://review.openstack.org/41903114:33
*** alexchadin has quit IRC14:52
*** Yumeng has joined #openstack-watcher14:52
*** alexchadin has joined #openstack-watcher14:52
*** Yumeng has quit IRC14:55
*** alexchadin has quit IRC14:57
*** tmetsch has joined #openstack-watcher14:58
*** lamt has quit IRC15:02
*** lamt has joined #openstack-watcher15:03
*** absubram has quit IRC15:08
*** alexchadin has joined #openstack-watcher15:15
*** jwcroppe has joined #openstack-watcher15:28
*** alexchadin has quit IRC15:32
openstackgerritVincent Françoise proposed openstack/watcher: Added Monasca Helper  https://review.openstack.org/34889115:43
openstackgerritVincent Françoise proposed openstack/watcher: Multi datasource support for Basic Consolidation  https://review.openstack.org/41461715:43
*** absubram has joined #openstack-watcher15:59
*** michaelgugino has joined #openstack-watcher16:04
openstackgerritVincent Françoise proposed openstack/watcher: Fix multinode tempest test failure  https://review.openstack.org/41954416:10
*** sferna1_ has joined #openstack-watcher16:17
akuleshovedleafe: Is there a blueprint for the API that you mentioned? (The long-term plan is to provide an API that will allow you to specify an instance to be migrated and a list of potential hosts...)16:26
edleafeakuleshov: not yet - that's still a ways off. We're focusing now on just getting the placement engine/API working and used by Nova16:26
akuleshovedleafe: Oh, I see. Thanks.16:29
edleafeakuleshov: I tried to push a change into Nova in Newton, but it was felt that it would be better to do it right in the placement API than to add a hack into the nova API16:30
akuleshovedleafe: Can I have a look at it anyway?16:32
edleafeakuleshov: sure. Spec: https://review.openstack.org/#/c/276840/16:33
edleafeakuleshov: Code: https://review.openstack.org/32780916:34
akuleshovedleafe: Thanks a lot!16:36
*** akuleshov has quit IRC16:41
*** akuleshov1 has joined #openstack-watcher16:42
openstackgerritVincent Françoise proposed openstack/watcher: Fix multinode tempest test failure  https://review.openstack.org/41954416:47
openstackgerritVincent Françoise proposed openstack/watcher: Added Monasca Helper  https://review.openstack.org/34889116:53
openstackgerritVincent Françoise proposed openstack/watcher: Multi datasource support for Basic Consolidation  https://review.openstack.org/41461716:53
openstackgerritVincent Françoise proposed openstack/watcher: Added tempest test for workload_balance  https://review.openstack.org/39335616:57
openstackgerritVincent Françoise proposed openstack/watcher: Added tempest test for workload_stabilization  https://review.openstack.org/39335516:58
*** akuleshov1 has left #openstack-watcher16:58
openstackgerritDavid TARDIVEL proposed openstack/watcher: Enable notification for vm task state update  https://review.openstack.org/41956217:04
openstackgerritDavid TARDIVEL proposed openstack/watcher: Enable, on DevStack, notifications for vm task state update  https://review.openstack.org/41956217:05
*** hvprash has quit IRC17:08
*** hvprash has joined #openstack-watcher17:10
*** vincentfrancoise has quit IRC17:55
*** tmetsch has quit IRC18:28
*** openstackgerrit has quit IRC18:33
*** tmetsch has joined #openstack-watcher19:06
*** tmetsch has quit IRC20:04
*** dtardivel has quit IRC20:14
*** wootehfoot has joined #openstack-watcher20:18
*** jwcroppe has quit IRC21:01
*** adisky_ has quit IRC21:19
*** thorst_ has quit IRC21:57
*** ss4 has joined #openstack-watcher22:03
*** wootehfoot has quit IRC22:06
*** absubram has quit IRC22:07
*** gabor_antal has quit IRC22:11
*** gabor_antal_ has joined #openstack-watcher22:11
*** gabor_antal_ has quit IRC22:23
*** gabor_antal has joined #openstack-watcher22:23
*** jwcroppe has joined #openstack-watcher22:26
*** thorst_ has joined #openstack-watcher22:32
*** thorst_ has quit IRC22:37
*** thorst_ has joined #openstack-watcher23:33
*** thorst_ has quit IRC23:37
*** openstackgerrit has joined #openstack-watcher23:43
openstackgerritHidekazu Nakamura proposed openstack/watcher: Add period input parameter to basic strategy  https://review.openstack.org/41643223:43
*** lamt has quit IRC23:55
*** ss4 has quit IRC23:56

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!