Wednesday, 2017-04-19

*** vincentfrancoise has quit IRC00:00
*** vmahe has joined #openstack-watcher00:00
*** thorst has quit IRC00:25
*** hidekazu has joined #openstack-watcher00:29
*** vmahe has quit IRC01:00
*** vmahe has joined #openstack-watcher01:01
*** vmahe has quit IRC01:31
*** vmahe has joined #openstack-watcher01:31
*** openstackgerrit has joined #openstack-watcher01:40
openstackgerritHidekazu Nakamura proposed openstack/watcher-specs master: Add spec for Zone migration strategy  https://review.openstack.org/45783401:40
openstackgerritMerged openstack/puppet-watcher master: Add the setting log level  https://review.openstack.org/45745001:41
*** Yumeng_ has joined #openstack-watcher01:58
*** Yumeng has quit IRC01:58
*** thorst has joined #openstack-watcher02:00
*** vmahe has quit IRC02:00
*** vmahe has joined #openstack-watcher02:01
*** thorst has quit IRC02:16
*** vmahe has quit IRC02:30
*** Tamayo has joined #openstack-watcher02:53
*** sanfern has joined #openstack-watcher03:02
*** hidekazu has quit IRC03:10
*** thorst has joined #openstack-watcher03:13
*** thorst has quit IRC03:32
*** hidekazu has joined #openstack-watcher04:17
*** adisky_ has joined #openstack-watcher04:26
*** thorst has joined #openstack-watcher05:29
*** zhurong has joined #openstack-watcher05:42
*** thorst has quit IRC05:48
openstackgerritpraveenraj proposed openstack/watcher master: [WIP] Support workload fingerprint generation  https://review.openstack.org/44840205:52
*** thorst has joined #openstack-watcher06:45
*** thorst has quit IRC06:49
*** vmahe has joined #openstack-watcher06:52
*** Yumeng_ has quit IRC07:11
*** danpawlik has joined #openstack-watcher07:15
*** vincentfrancoise has joined #openstack-watcher07:29
*** vmahe has quit IRC07:30
*** Yumeng has joined #openstack-watcher07:39
*** thorst has joined #openstack-watcher07:46
*** thorst has quit IRC07:50
*** vmahe has joined #openstack-watcher07:51
*** vincentfrancoise has quit IRC08:00
*** alexchadin has joined #openstack-watcher08:02
*** vincentfrancoise has joined #openstack-watcher08:10
*** vmahe has quit IRC08:10
*** vmahe has joined #openstack-watcher08:11
*** efoley has joined #openstack-watcher08:27
*** efoley_ has joined #openstack-watcher08:27
*** efoley_ has quit IRC08:27
*** alexchadin has quit IRC08:34
*** alexchadin has joined #openstack-watcher08:43
*** thorst has joined #openstack-watcher08:47
*** thorst has quit IRC08:52
*** hidekazu has left #openstack-watcher08:59
*** vmahe has quit IRC09:00
*** vmahe has joined #openstack-watcher09:01
openstackgerritpraveenraj proposed openstack/watcher master: [WIP] Support workload fingerprint generation  https://review.openstack.org/44840209:01
*** vincentfrancoise has quit IRC09:30
*** vmahe has quit IRC09:31
*** vincentfrancoise has joined #openstack-watcher09:31
*** thorst has joined #openstack-watcher09:47
*** thorst has quit IRC09:52
*** vincentfrancoise has quit IRC10:00
*** vincentfrancoise has joined #openstack-watcher10:28
*** alexchadin has quit IRC10:32
*** zhurong has quit IRC10:34
*** vmahe has joined #openstack-watcher10:42
*** thorst has joined #openstack-watcher10:48
*** thorst has quit IRC10:53
*** sanfern has quit IRC10:55
*** vmahe has quit IRC11:00
*** thorst has joined #openstack-watcher11:42
*** thorst_ has joined #openstack-watcher11:42
*** thorst has quit IRC11:47
*** vmahe has joined #openstack-watcher11:53
*** vincentfrancoise has quit IRC12:00
*** vincentfrancoise has joined #openstack-watcher12:01
*** efoley_ has joined #openstack-watcher12:02
*** efoley has quit IRC12:05
*** alexchadin has joined #openstack-watcher12:09
*** sanfern has joined #openstack-watcher12:30
*** zhurong has joined #openstack-watcher12:31
openstackgerritMerged openstack/watcher master: [Doc]  messaging -> messagingv2  https://review.openstack.org/45743412:40
*** zhurong has quit IRC12:45
*** vmahe has left #openstack-watcher12:50
*** efoley__ has joined #openstack-watcher12:58
*** efoley_ has quit IRC13:01
*** vmahe has joined #openstack-watcher13:01
*** vmahe has quit IRC13:06
*** zhurong_phone has joined #openstack-watcher13:10
*** zhurong_phone has left #openstack-watcher13:11
openstackgerritMerged openstack/watcher-dashboard master: Updated from global requirements  https://review.openstack.org/45773713:20
openstackgerritMerged openstack/watcher-dashboard master: Fix exception error when creating audit without audit template  https://review.openstack.org/45567913:20
*** alexchadin has quit IRC13:21
*** vincentfrancoise has quit IRC13:30
*** vincentfrancoise has joined #openstack-watcher13:31
*** alexchadin has joined #openstack-watcher13:53
alexchadinhi, we will start in 5 minutes on #openstack-meeting-413:54
sballe_morning13:57
alexchadinhi sballe_13:58
sballe_hi :-) alexchadin13:58
*** vincentfrancoise has quit IRC14:00
*** vincentfrancoise has joined #openstack-watcher14:01
alexchadinYumeng: adisky_ chrisspencer vincentfrancoise sanfern we have meeting on #openstack-meeting-4 channel now14:04
alexchadinhvprash: ^14:07
*** pshedimb_ has joined #openstack-watcher14:16
*** vincentfrancoise has quit IRC14:30
*** vincentfrancoise has joined #openstack-watcher14:31
*** sanfern has quit IRC14:43
*** mkarsten has joined #openstack-watcher14:57
*** vincentfrancoise has quit IRC15:00
*** vincentfrancoise has joined #openstack-watcher15:08
mkarstenHello. aspiers recommended that I join this channel. I am an academic and interested in understanding the state of the art in cloud rebalancing. I am somewhat familiar with OpenStack nuts and bolts, but certainly no expert. I do know a fair bit about resource management and performance in general. I am trying to assess the viability of dynamic rebalancing, given the overhead and latency of migrations in comparison to the frequency of15:09
mkarstenworkload changes. For starters, the Watcher web page speaks about providing "out-of-box optimization routines for immediate value-add", so I was wondering whether these are documented somewhere and/or if there is other literature out there describing such optimization routines?15:09
aspierswelcome mkarsten :-)15:10
aspiersI'd suggest staying connected as long as possible - getting a reply sometimes takes hours, depending on the time of day and how busy people are with other stuff..15:11
alexchadingood day, mkarsten15:12
alexchadinmkarsten: first of all, you are welcome here15:12
aspiersor sometimes you only have to wait a few seconds ;-)15:13
alexchadinaspiers: +215:13
alexchadinmkarsten: if I understand right, you'd like to get deeper into Watcher workflow process15:13
alexchadinmkarsten: start from viewing our demo: https://www.youtube.com/watch?v=FJttohkf0sM15:16
alexchadinmkarsten: then I would suggest you to learn System Architecture here: https://docs.openstack.org/developer/watcher/architecture.html15:19
mkarstenThe workflow process is certainly part of it, but my first objective is getting a back-of-the envelope sense of:15:20
mkarsten- frequency and amplitude of workload changes15:20
mkarsten- overhead/latency of rebalancing actions (VM migrations?, other?)15:20
alexchadinmkarsten: the best way to get more familiar with something new is try to install it, so you can install devstack and follow Getting Started section: https://docs.openstack.org/developer/watcher/#getting-started15:20
mkarstenIn other words, assume for a moment that there is a infinitely fast/good algorithm and we have a perfect system to execute the outcome of the algorithm.15:20
alexchadinmkarsten: about frequency: we rely on some data sources (Ceilometer+Gnocchi, Monasca) which gather metrics.15:23
mkarstenI just want to size up the opportunity, having seen many a feedback-based resource allocation scheme not gaining much traction in the real world (for example, 20 years of "QoS routing" research for the Internet - and there's not much to show for).15:23
*** mkarsten has left #openstack-watcher15:23
*** mkarsten has joined #openstack-watcher15:23
mkarstenWhat are your assumptions about the scale of the system and the workload? What kind of demand swings do you expect? How much time do you budget for a VM migration? Does anyone have some (estimated) numbers?15:25
vincentfrancoise mkarsten: hi15:26
*** alexchadin has quit IRC15:27
*** vincentfrancoise has quit IRC15:31
*** vincentfrancoise has joined #openstack-watcher15:31
vincentfrancoisemkarsten: the case I was the most confronted with is the live migration and we usually consider its cost to be negligible because it is actually absorbed by the syncing of NFS underneath it15:32
vincentfrancoisemkarsten: when we say we have out-of-the-box routines, what can be easily shown is the before/after effect15:34
vincentfrancoisemkarsten: but I agree that we (my team) didn't spend much time on the interference cause by these re-organization actions (e.g. migration)15:35
mkarstenvincentfrancoise: Thanks, I see. Do you assume any latency at all? For example, after a live migration, a VM might also experience a ramp-up phase to get back up to speed?15:37
mkarstenvincentfrancoise: Is there any documentation about these routines? Or do I have to go to the source (code)?15:38
vincentfrancoisemkarsten: hum, I'll try to answer to the best of my knowledge though I am not the best qualified to answer that15:40
vincentfrancoisemkarsten: the ramp-up phase you describe is something we do not model because we reduced the scope of our tests to live-migrations which had very little impact with this regard, or at least not too bad unless the VM is actually under a high load15:42
vincentfrancoisemkarsten: at least not in the context of Watcher15:42
vincentfrancoisemkarsten: the problem with modeling this is that you need a testing protocol which simulates this workload to detect any perturbation and that's hard to do15:43
mkarstenRight, that's why I want to start with looking at algorithms that people have in mind and simply plug in cost estimates to assess their viability under certain circumstances.15:45
vincentfrancoisemkarsten: again, my team was mainly focused on producing a good before/after affect, and we didn't invest much time investigating the performance impact during the state transition15:45
vincentfrancoisemkarsten: the algorithms (we call then strategies) are lightly described in the online doc15:46
vincentfrancoisemkarsten: https://docs.openstack.org/developer/watcher/dev/plugins.html#strategies15:47
vincentfrancoisemkarsten: for the rest you can dig in their associated spec (sometimes the URL is referenced in the doc I gave you)15:47
mkarstenGreat, thanks, that's a good starting point! I'll take a look and will get back here with more questions...15:48
vincentfrancoisemkarsten: for the rest you have to read the code15:48
vincentfrancoisemkarsten: but any algorithm question starts to get outside of my "scope" so I may not be able to answer15:48
openstackgerritpraveenraj proposed openstack/watcher-specs master: Support visualizing workload fingerprints  https://review.openstack.org/44839415:48
*** sanfern has joined #openstack-watcher15:53
*** wootehfoot has joined #openstack-watcher16:26
*** vincentfrancoise has quit IRC16:32
*** ss4 has joined #openstack-watcher16:37
*** wootehfoot has quit IRC16:40
*** harlowja_ has quit IRC17:13
*** harlowja has joined #openstack-watcher17:15
*** harlowja has quit IRC17:17
*** harlowja has joined #openstack-watcher17:17
*** efoley__ has quit IRC17:18
*** mkarsten has left #openstack-watcher17:29
*** pshedimb_ has quit IRC17:48
*** mkarsten has joined #openstack-watcher17:52
*** adisky_ has quit IRC18:19
*** mkarsten has left #openstack-watcher18:36
*** mkarsten has joined #openstack-watcher18:38
*** pshedimb_ has joined #openstack-watcher18:46
*** pshedimb_ has quit IRC18:53
*** wootehfoot has joined #openstack-watcher19:02
*** ss4 has quit IRC19:06
*** pshedimb_ has joined #openstack-watcher19:12
*** wootehfoot has quit IRC19:27
*** wootehfoot has joined #openstack-watcher19:32
*** wootehfoot has quit IRC19:53
*** wootehfoot has joined #openstack-watcher19:55
*** wootehfoot has quit IRC19:59
*** wootehfoot has joined #openstack-watcher20:05
*** mkarsten has left #openstack-watcher20:13
*** thorst_ has quit IRC21:10
*** thorst has joined #openstack-watcher21:35
*** thorst has quit IRC21:40
*** wootehfoot has quit IRC22:33

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