| *** zhurong has joined #openstack-watcher | 01:13 | |
| *** zhurong has quit IRC | 02:15 | |
| *** zhurong has joined #openstack-watcher | 02:19 | |
| *** necuser__ has quit IRC | 02:38 | |
| *** necuser__ has joined #openstack-watcher | 02:50 | |
| *** thorst has quit IRC | 03:08 | |
| openstackgerrit | Merged openstack/watcher-dashboard master: [Fix gate]Update test requirement https://review.openstack.org/440493 | 03:29 |
|---|---|---|
| openstackgerrit | Merged openstack/watcher master: [Fix gate]Update test requirement https://review.openstack.org/440485 | 03:30 |
| *** luyao has quit IRC | 04:16 | |
| *** thorst has joined #openstack-watcher | 04:28 | |
| *** thorst has quit IRC | 04:28 | |
| *** karthikpr has quit IRC | 05:04 | |
| *** thorst has joined #openstack-watcher | 05:29 | |
| *** thorst has quit IRC | 05:34 | |
| *** Yumeng has joined #openstack-watcher | 05:36 | |
| *** alexchadin has joined #openstack-watcher | 06:26 | |
| *** thorst has joined #openstack-watcher | 06:30 | |
| *** thorst has quit IRC | 06:34 | |
| *** aovchinnikov has joined #openstack-watcher | 06:55 | |
| aovchinnikov | Hello everyone | 07:02 |
| aovchinnikov | I have a question regarding watcher's behaviour. How does it handle nova scheduling rules when deciding where to migrate a VM during cloud optimization? | 07:03 |
| aovchinnikov | For example, consider two VMs booted with SameHostFilter. Is it guarantied that such rule won't be optimized? | 07:03 |
| alexchadin | hi aovchinnikov | 07:24 |
| alexchadin | aovchinnikov: Watcher doesn't respect nova scheduling filters for now. There is no API for Nova Scheduler so we rely only on Watcher Audit scope currently | 07:26 |
| aovchinnikov | alexchadin ok, so what are the plans to mitigate this in the future? | 07:29 |
| aovchinnikov | because there are many real-world scenarios where both optimization and respect for nova rules are highly desirable | 07:29 |
| alexchadin | aovchinnikov, I agree, but Nova team doesn't know what to do with requests from Watcher, Congress. There are plans (based on latest info from PTG) to get rid of Scheduler and make scheduling process decentralized (maybe, using Placement API), but it is only plans for future. | 07:32 |
| aovchinnikov | well, that sounds like a very distant future to me | 07:33 |
| aovchinnikov | does nova team have any estimates on when something will be done to address this issues? | 07:34 |
| aovchinnikov | because till there is no way to tell which hosts are forbidden for a particular instance watcher will be somewhat limited in its usability | 07:36 |
| alexchadin | aovchinnikov maybe Pike, maybe Queens :) This problem didn't appear yesterday, we have a long discussion with them | 07:36 |
| alexchadin | aovchinnikov you can use Audit Scope, but it is more applicable for small clouds | 07:36 |
| aovchinnikov | have you considered any alternative routes to follow while there is no Queens? | 07:37 |
| aovchinnikov | like peeping into nova's DB or something? | 07:38 |
| alexchadin | aovchinnikov: there is always a downstream way to modify it by yourself and share it somewhere. We are not nova-related project so we have to use common ways to communicate with Nova services | 07:38 |
| alexchadin | aovchinnikov, I had worked on Nova LoadBalancer (experimental project of Servionica) before I came to Watcher and we respected filters by modifying source code of Nova | 07:39 |
| aovchinnikov | >Audit Scope... well, there is a good chance that I'll have to run it on a medium-sized cloud with somewhat intricate rules applied to VMs, so I was hoping for some sort of a direction which is somewhat aligned with community's one | 07:40 |
| aovchinnikov | yes, downstream changes was one of options we've considered, but that is not a very good solution for long-term | 07:41 |
| alexchadin | aovchinnikov: Here is example of scope https://github.com/openstack/watcher/blob/ebc70a46db2ba513160f96a03c1ce3de6d1c28e1/watcher/tests/decision_engine/scope/fake_scopes.py#L17 | 07:43 |
| aovchinnikov | alexchadin: have you considered reusing parts of nova scheduler inside watcher? that has a potential of solving this problem | 07:44 |
| aovchinnikov | while bringing in a plethora of others, but anyway | 07:44 |
| aovchinnikov | alexchadin: thank you for the link, I'll give scopes a try | 07:45 |
| alexchadin | aovchinnikov: we don't want to multiply entities. We would need to copy almost all scheduler code base and then we need to be synced with nova filters | 07:46 |
| aovchinnikov | yes, those are some of aforementioned other issues | 07:46 |
| aovchinnikov | alexchadin: thank you for your help! | 07:47 |
| alexchadin | aovchinnikov: there would be a lot of new changes only for a while and cutting it in future... It doesn't make me sense | 07:47 |
| alexchadin | aovchinnikov you are welcome! | 07:47 |
| *** alexchadin has quit IRC | 07:59 | |
| *** alexchadin has joined #openstack-watcher | 08:00 | |
| openstackgerrit | Santhosh Fernandes proposed openstack/watcher master: Add gnocchi support in basic_consolidation strategy https://review.openstack.org/440293 | 08:20 |
| *** sanfern has joined #openstack-watcher | 08:31 | |
| *** thorst has joined #openstack-watcher | 08:32 | |
| *** thorst has quit IRC | 08:36 | |
| *** vmahe has joined #openstack-watcher | 08:37 | |
| *** vincentfrancoise has joined #openstack-watcher | 08:40 | |
| *** thorst has joined #openstack-watcher | 09:33 | |
| *** thorst has quit IRC | 09:37 | |
| *** pksingh has joined #openstack-watcher | 09:53 | |
| *** alexchadin has quit IRC | 10:11 | |
| *** alexchadin has joined #openstack-watcher | 10:30 | |
| pksingh | vincentfrancoise: Hello | 10:33 |
| *** openstackgerrit has quit IRC | 10:33 | |
| vincentfrancoise | pksingh: hi | 10:33 |
| *** karthikpr has joined #openstack-watcher | 10:33 | |
| pksingh | vincentfrancoise: i was looking at https://github.com/openstack/watcher/blob/d45ab136194bd1da4b66a85b762d1ad5007cc0d7/watcher/decision_engine/strategy/strategies/basic_consolidation.py#L141, | 10:33 |
| *** thorst has joined #openstack-watcher | 10:34 | |
| pksingh | vincentfrancoise: can we create some conf file and move this to that file? | 10:34 |
| vincentfrancoise | pksingh: no we cannot because these configs are dynamically loaded | 10:34 |
| vincentfrancoise | pksingh: all plugins have this dynamic config system | 10:35 |
| pksingh | vincentfrancoise: so if i need to use datasource at different points in different strategies then do i need to add them to all places? | 10:35 |
| vincentfrancoise | pksingh: as of now, yes | 10:36 |
| vincentfrancoise | pksingh: this is why the abstraction layer for datasources was discussed at the PTG | 10:36 |
| pksingh | vincentfrancoise: can't i define in oslo_config at common place under conf directory and access it here? | 10:37 |
| vincentfrancoise | pksingh: because right now both the configuration and the implementation are defined within each and every plugin | 10:37 |
| *** karthikpr has quit IRC | 10:38 | |
| *** thorst has quit IRC | 10:38 | |
| vincentfrancoise | pksingh: the thing you might do is to use string interpolation | 10:39 |
| vincentfrancoise | pksingh: you define a datasource parameter as a static parameter and use string interpolation as default value in the strategies | 10:39 |
| pksingh | vincentfrancoise: and they are loaded by plugin.py in conf directory? | 10:39 |
| vincentfrancoise | pksingh: the dynamic config options you mean? yes | 10:41 |
| pksingh | vincentfrancoise: so if i add more config options in future then adding them to each plugin/strategy would cause a lot of duplicate work | 10:41 |
| pksingh | vincentfrancoise: yes i mean dynamic config options, | 10:42 |
| vincentfrancoise | pksingh: it's not duplicate work because plugins are not just strategy plugins so it will only feel duplicated for the "strategies" subset | 10:43 |
| pksingh | vincentfrancoise: yes i mean if that config is applicable only for strategies, then i have to add that to each strategy in get_config_opts? | 10:44 |
| vincentfrancoise | pksingh: and also, how would you make the difference between a parameter that is specific to a strategy and one that is actually shared with other? | 10:45 |
| vincentfrancoise | pksingh: ah | 10:45 |
| vincentfrancoise | pshedimb: codewise you don't actually need to duplicate the code | 10:45 |
| vincentfrancoise | just add the common parameter to https://github.com/openstack/watcher/blob/master/watcher/decision_engine/strategy/strategies/base.py#L120-L126 | 10:47 |
| pksingh | vincentfrancoise: that's what i wanted, thanks | 10:47 |
| *** alexchadin has joined #openstack-watcher | 10:48 | |
| vincentfrancoise | pksingh: then make sure you do a get_config_opts(cls): return super(cls, MyStrategy) + [other params] | 10:48 |
| vincentfrancoise | in **ALL** the subclasses | 10:48 |
| vincentfrancoise | otherwise, some parameters will be ignored | 10:48 |
| pksingh | vincentfrancoise: yes you are right | 10:49 |
| *** openstackgerrit has joined #openstack-watcher | 10:52 | |
| openstackgerrit | Béla Vancsics proposed openstack/watcher master: Reduced the code complexity https://review.openstack.org/441873 | 10:52 |
| *** pksingh has quit IRC | 10:55 | |
| *** sanfern has quit IRC | 11:19 | |
| *** alexchadin has quit IRC | 11:28 | |
| *** alexchadin has joined #openstack-watcher | 11:44 | |
| *** zhurong has quit IRC | 11:58 | |
| *** alexchadin_ has joined #openstack-watcher | 12:07 | |
| *** alexchadin_ has quit IRC | 12:07 | |
| *** sanfern has joined #openstack-watcher | 12:13 | |
| *** karthikpr has joined #openstack-watcher | 12:16 | |
| *** alexchadin has quit IRC | 12:17 | |
| *** karthikpr has quit IRC | 12:20 | |
| *** alexchadin has joined #openstack-watcher | 12:21 | |
| *** thorst has joined #openstack-watcher | 12:44 | |
| *** aovchinnikov has quit IRC | 13:04 | |
| edleafe | aovchinnikov: alexchadin: Small steps: https://review.openstack.org/#/c/440580/ | 13:42 |
| alexchadin | thank you, edleafe, I will take a look | 13:45 |
| *** pksingh has joined #openstack-watcher | 14:20 | |
| *** pksingh has quit IRC | 14:41 | |
| *** alexchadin has quit IRC | 15:01 | |
| pshedimb | vincentfrancoise, Yeah. Not codewise. But I meant metric collection in the beginning. | 15:06 |
| *** karthikpr has joined #openstack-watcher | 15:12 | |
| *** karthikpr has quit IRC | 15:16 | |
| *** alexchadin has joined #openstack-watcher | 15:16 | |
| *** karthikpr has joined #openstack-watcher | 15:16 | |
| *** karthikpr has quit IRC | 15:18 | |
| *** alexchadin has quit IRC | 15:34 | |
| *** danpawli1 has quit IRC | 16:13 | |
| *** vmahe has left #openstack-watcher | 16:23 | |
| *** karthikpr has joined #openstack-watcher | 17:18 | |
| *** vincentfrancoise has quit IRC | 17:21 | |
| *** karthikpr has quit IRC | 17:44 | |
| *** Guest89812 has joined #openstack-watcher | 18:19 | |
| *** wootehfoot has joined #openstack-watcher | 18:19 | |
| *** Guest89812 has quit IRC | 18:24 | |
| *** karthikpr has joined #openstack-watcher | 18:42 | |
| *** sanfern has quit IRC | 18:46 | |
| *** karthikpr has quit IRC | 18:46 | |
| *** karthikpr has joined #openstack-watcher | 19:04 | |
| *** wootehfoot has quit IRC | 20:59 | |
| *** karthikpr has quit IRC | 21:49 | |
| *** karthikpr has joined #openstack-watcher | 21:55 | |
| *** wootehfoot has joined #openstack-watcher | 21:58 | |
| *** thorst has quit IRC | 22:04 | |
| *** thorst has joined #openstack-watcher | 22:05 | |
| *** karthikpr has quit IRC | 22:08 | |
| *** thorst has quit IRC | 22:09 | |
| *** sanfern has joined #openstack-watcher | 22:34 | |
| openstackgerrit | Chris Spencer proposed openstack/watcher-specs master: Define grammar for workload characterization https://review.openstack.org/377100 | 23:05 |
| *** wootehfoot has quit IRC | 23:14 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!