*** hvprash_ has quit IRC | 00:37 | |
*** hvprash has joined #openstack-watcher | 00:37 | |
*** hvprash has quit IRC | 01:21 | |
*** hvprash has joined #openstack-watcher | 01:21 | |
*** esberglu has joined #openstack-watcher | 03:11 | |
*** esberglu has quit IRC | 03:11 | |
*** hvprash has quit IRC | 04:10 | |
*** hvprash has joined #openstack-watcher | 04:11 | |
*** hvprash has quit IRC | 04:44 | |
openstackgerrit | Tomasz Kaczynski proposed openstack/watcher: Add Scoring Module implementation https://review.openstack.org/351577 | 04:50 |
---|---|---|
*** hvprash has joined #openstack-watcher | 04:58 | |
*** hvprash has quit IRC | 05:55 | |
*** ecelik has joined #openstack-watcher | 06:01 | |
sballe_ | Morning | 06:31 |
sballe_ | When will we know what talks will be accepted? | 06:31 |
*** acabot_ has joined #openstack-watcher | 07:15 | |
acabot | sballe_ : August 25th | 07:17 |
*** danpawlik has joined #openstack-watcher | 07:27 | |
*** alexchadin has joined #openstack-watcher | 07:39 | |
*** alexchadin has quit IRC | 07:51 | |
sballe_ | Ok thx | 08:06 |
sballe_ | I will be home by then 😀 | 08:07 |
*** acabot_ has quit IRC | 08:08 | |
*** acabot_ has joined #openstack-watcher | 08:09 | |
*** alexchadin has joined #openstack-watcher | 08:17 | |
*** openstackgerrit has quit IRC | 08:18 | |
*** openstackgerrit has joined #openstack-watcher | 08:18 | |
*** alexchadin has quit IRC | 08:32 | |
*** alexchadin has joined #openstack-watcher | 08:32 | |
openstackgerrit | Antoine Cabot proposed openstack/watcher-specs: Add ocata folders and template for specs https://review.openstack.org/353320 | 08:47 |
*** jed56 has joined #openstack-watcher | 09:03 | |
*** alexchadin has quit IRC | 09:06 | |
*** alexchadin has joined #openstack-watcher | 09:07 | |
*** acabot_ has quit IRC | 09:16 | |
*** acabot_ has joined #openstack-watcher | 09:35 | |
*** acabot_ has quit IRC | 09:36 | |
*** acabot_ has joined #openstack-watcher | 09:38 | |
*** acabot_ has quit IRC | 09:50 | |
*** acabot_ has joined #openstack-watcher | 10:01 | |
alexchadin | jed56: hi | 10:02 |
jed56 | alexchadin: hi | 10:05 |
jed56 | how are you ? | 10:05 |
alexchadin | I'm great, especially after the vacation:) | 10:05 |
jed56 | :p | 10:06 |
alexchadin | how are you? | 10:06 |
jed56 | very well, especially because my holidays are coming soon | 10:06 |
alexchadin | jed56: great:) | 10:07 |
alexchadin | jed56: could we discuss audit scope before or after the meeting? | 10:07 |
jed56 | after the meeting this is good for me | 10:07 |
alexchadin | I'm leaving my work place right | 10:07 |
alexchadin | ok, cool | 10:07 |
alexchadin | see you later:) | 10:07 |
jed56 | perfect, enjoy your meal | 10:08 |
alexchadin | thanks! | 10:08 |
*** acabot_ has quit IRC | 10:11 | |
*** alexchadin has quit IRC | 10:12 | |
*** acabot_ has joined #openstack-watcher | 10:14 | |
openstackgerrit | Tomasz Kaczynski proposed openstack/watcher: Add Scoring Module implementation https://review.openstack.org/351577 | 10:16 |
*** acabot_ has quit IRC | 10:26 | |
*** alexchadin has joined #openstack-watcher | 11:35 | |
*** jiteka has joined #openstack-watcher | 11:40 | |
jiteka | hello :) | 11:40 |
jiteka | ahah odyssey4me I got my answer | 11:41 |
jiteka | odyssey4me: was about to ask you if you heard about watcher and if you already added it in OSA | 11:41 |
jiteka | hey bauzas_off :) | 11:53 |
*** alexchadin has quit IRC | 12:00 | |
*** alexchadin has joined #openstack-watcher | 12:00 | |
*** acabot_ has joined #openstack-watcher | 12:11 | |
alexchadin | vincentfrancoise: ping | 12:13 |
vincentfrancoise | alexchadin: hello | 12:21 |
alexchadin | vincentfrancoise: how are you? | 12:22 |
vincentfrancoise | good, you? | 12:22 |
alexchadin | great | 12:22 |
alexchadin | May I ask you about cluster data collecting? | 12:22 |
vincentfrancoise | yeah go for it | 12:23 |
vincentfrancoise | which part of it BTW ? | 12:23 |
alexchadin | As I understand, we now have decision scheduler, that calls collectors to gather data | 12:24 |
vincentfrancoise | yes | 12:24 |
alexchadin | and when audit launch itself to create action plan, it copies last data from collectors, right? | 12:25 |
alexchadin | to gain ability to use cluster data | 12:25 |
vincentfrancoise | yes | 12:26 |
vincentfrancoise | and also because they may alter the cluster data model | 12:26 |
vincentfrancoise | so it should not affect the main cluster data model | 12:27 |
alexchadin | yeah, I got it | 12:27 |
alexchadin | hm | 12:27 |
alexchadin | I think about audit scope architecture | 12:27 |
alexchadin | that's why I started to investigate this mechanism | 12:28 |
alexchadin | I think we should create subset of AZ and HA when audit is launched | 12:29 |
alexchadin | Not to store it in memory | 12:30 |
jiteka | I've got a question too | 12:30 |
jiteka | but I can wait :D | 12:30 |
alexchadin | hi jiteka | 12:30 |
vincentfrancoise | hi jiteka | 12:30 |
alexchadin | feel free to ask:) | 12:30 |
vincentfrancoise | +1 ^ | 12:31 |
jiteka | thx so I heard about watcher and I would like to try, do you have some demo cluster where people can play a bit with it ? | 12:31 |
alexchadin | I could always try it in devstack | 12:31 |
jiteka | next step will be to setup a small Openstack cluster upstream via Openstack Ansible (I want to try it too) | 12:32 |
vincentfrancoise | alexchadin: when you say you want to create a subset, do you mean creating another copy and apply some AZ and HA filtering on it? | 12:32 |
jiteka | well I'm more interested to try it on a small cluster than on a all in one box | 12:32 |
jiteka | I'm more on the Operation/Fleet management side | 12:32 |
vincentfrancoise | jiteka: no, we do not have a live cluster | 12:32 |
jiteka | than dev side :) | 12:32 |
alexchadin | vincentfrancoise: I mean to make a new copy and change it according with subset | 12:32 |
vincentfrancoise | jiteka: what we do have is a devstack plugin that would allow you de deploy watcher fairly easily | 12:33 |
vincentfrancoise | jiteka: and also some puppet recipes as well | 12:33 |
alexchadin | jiteka: you can also try RDO | 12:34 |
vincentfrancoise | jiteka: oh, is it craton related? | 12:34 |
alexchadin | vincentfrancoise: offtop: will we have demo cluster on Summit? | 12:35 |
vincentfrancoise | jiteka: so if that's what you want, I would recommend you deploy Watcher using the Devstack instructions http://docs.openstack.org/developer/watcher/dev/devstack.html | 12:36 |
vincentfrancoise | alexchadin: good question, I guess it's not decided yet, but we probably will have one yes | 12:37 |
jiteka | vincentfrancoise: only puppet modules ? no ansible role yet ? | 12:37 |
jiteka | vincentfrancoise: do you know if someone close to OSA project is working to integrate watcher in it ? | 12:37 |
alexchadin | vincentfrancoise: I will have a couple of vms with openstack onboard | 12:38 |
vincentfrancoise | jiteka: there's no ansible playbook yet | 12:41 |
vincentfrancoise | in https://github.com/b-com/watcher-tools/ you have some outdated attempt to provide ansible playbooks | 12:42 |
vincentfrancoise | so I clearly don't know if it's worth using it | 12:43 |
jiteka | I will take a look | 12:43 |
jiteka | :) | 12:43 |
jiteka | vincentfrancoise: b-com is one of the 8 IRT in france right ? | 12:44 |
jiteka | vincentfrancoise: that's nice to see one of them involved in Opensource and cloud projects :) | 12:44 |
vincentfrancoise | jiteka: yup you got it | 12:46 |
jiteka | vincentfrancoise: are you in contact with some INRIA research team in Lyon (France) ? | 12:47 |
jed56 | hi jiteka | 12:47 |
jiteka | hi jed56 | 12:47 |
jed56 | We are working with some peoples from INRIA ;-) | 12:48 |
jed56 | s/peoples/people | 12:48 |
jiteka | maybe I know some of them | 12:48 |
jed56 | okay | 12:49 |
vincentfrancoise | jiteka: it's a small world :) | 12:49 |
jiteka | clearly | 12:49 |
jed56 | are you working for INRIA ? | 12:49 |
jiteka | I was | 12:49 |
jiteka | 2 years ago | 12:49 |
jiteka | and I was working in CompatibleOne project and XLCloud project | 12:50 |
jiteka | both on Energy efficiency applied in cloud environment | 12:50 |
jed56 | interesting | 12:50 |
jiteka | I'm curious to know if some of the works made in watcher is close to what we designed/tested in those project :) | 12:51 |
jiteka | did you heard about KWapi ? | 12:51 |
jiteka | https://github.com/openstack/kwapi | 12:51 |
jed56 | yes ! | 12:51 |
jiteka | so it's somehow related | 12:51 |
jiteka | :D | 12:51 |
jiteka | maybe | 12:51 |
jed56 | okay! | 12:52 |
jed56 | if you have any ideas which can improve Watcher don't hesitate ;) | 12:53 |
jiteka | I want to try it first :) | 12:53 |
*** acabot_ has quit IRC | 12:53 | |
jiteka | I'm want to continue my "research" on that topic | 12:53 |
jiteka | at scale :) | 12:53 |
jed56 | cool | 12:54 |
jiteka | back in time I was playing with a really small cluster in INRIA | 12:54 |
jiteka | Openstack folsom with 2 controller and 6 compute node | 12:54 |
jiteka | got more to play with now | 12:54 |
jiteka | nice I see that energy based scheduling is using affinity/anti-affinity custom filters | 12:56 |
jiteka | did you know if nova-scheduler is still part of nova project or if it was splitted since liberty ? | 12:56 |
alexchadin | jiteka: still part of | 12:57 |
jiteka | I lost track about it since | 12:57 |
jiteka | do you have somewhere the list of devices/driver currently available to gather power consumption metrics ? | 12:58 |
jiteka | alexchadin: thx | 12:59 |
openstackgerrit | Antoine Cabot proposed openstack/watcher-specs: Move Mitaka specs to Newton cycle https://review.openstack.org/353454 | 12:59 |
*** hvprash has joined #openstack-watcher | 12:59 | |
vincentfrancoise | jiteka: all metrics are the one available in the Ceilometer project, so you can always refer to their documentation | 13:00 |
alexchadin | jiteka: take a look at Ceilometer IPMI | 13:00 |
*** hvprash_ has joined #openstack-watcher | 13:00 | |
jiteka | oh ok so watcher is not responsible to gather metrics but rely on Ceilometer | 13:00 |
alexchadin | yeap | 13:01 |
vincentfrancoise | jiteka: lately, we are thinking about relying on another project called Monasca to gather metrics since the queries are faster | 13:01 |
jiteka | few years ago I also heard about gnocchi that was supposed to address ceilometer performance issue | 13:02 |
jiteka | but I don't know if it overtake ceilometer, if both coexist, or if someone else replaced them | 13:02 |
vincentfrancoise | ceilometer is still not quite there yet | 13:02 |
vincentfrancoise | but monasca seems to be a better replacement | 13:02 |
jiteka | it was one of the first question I asked when I joined Rackspace | 13:02 |
jiteka | to know if ceilometer was in production | 13:03 |
jiteka | I will check monasca then, I never heard about it | 13:03 |
*** hvprash has quit IRC | 13:04 | |
*** acabot_ has joined #openstack-watcher | 13:05 | |
jiteka | many thanks guys :) | 13:05 |
*** acabot_ has quit IRC | 13:05 | |
vincentfrancoise | jiteka: if you have any feedback to share on watcher, please do share it with us | 13:06 |
jiteka | vincentfrancoise: yes I will | 13:06 |
vincentfrancoise | cheers | 13:06 |
jiteka | vincentfrancoise: do you have a list of user/tester already ? | 13:07 |
*** grumpycatt has joined #openstack-watcher | 13:07 | |
jiteka | hey grumpycatt | 13:07 |
grumpycatt | hi guys | 13:07 |
jiteka | grumpycatt: stay calm plz | 13:07 |
grumpycatt | I'm always | 13:08 |
jiteka | grumpycatt: ok good | 13:08 |
jiteka | grumpycatt: I have a good news for you | 13:08 |
jiteka | grumpycatt: if you want to try watcher, you will be able to rely on ceilometer metrics | 13:09 |
jiteka | grumpycatt: and because you have at disposale an awesome ceilometer cluster, it shouldn't be an issue :) | 13:09 |
grumpycatt | *sight* ceilometer | 13:10 |
jiteka | brb | 13:11 |
*** jiteka is now known as jiteka-away | 13:11 | |
vincentfrancoise | grumpycatt: hence we're trying to also provide monasca support | 13:11 |
jiteka-away | it's time to stop flooding official projects room now | 13:11 |
grumpycatt | jiteka just told me about Watcher, I'm discovering the service with interest | 13:12 |
vincentfrancoise | grumpycatt: good :) | 13:13 |
*** harlowja has quit IRC | 13:23 | |
*** Zucan has joined #openstack-watcher | 13:26 | |
*** alexchadin has quit IRC | 13:33 | |
*** esberglu has joined #openstack-watcher | 13:42 | |
*** hvprash_ has quit IRC | 13:50 | |
*** hvprash has joined #openstack-watcher | 13:50 | |
*** thorst_ has joined #openstack-watcher | 13:53 | |
*** ecelik has quit IRC | 14:00 | |
*** alexchadin has joined #openstack-watcher | 14:07 | |
*** vmahe has joined #openstack-watcher | 14:09 | |
*** vmahe has left #openstack-watcher | 14:10 | |
*** michaelgugino has joined #openstack-watcher | 14:29 | |
*** Zucan has quit IRC | 14:31 | |
*** alexchadin has quit IRC | 14:59 | |
acabot | michaelgugino : hi Michael, it seems you are 1h late ;-) | 14:59 |
michaelgugino | hehe, I know. In another meeting :) | 15:00 |
hvprash | he he | 15:00 |
*** alexchadin has joined #openstack-watcher | 15:00 | |
hvprash | michaelgugino dtradivel, if you both want to sync on the ansible scripts | 15:01 |
alexchadin | jed56: I have some questions and propositions regarding audit scope | 15:01 |
jed56 | yes | 15:01 |
acabot | michaelgugino : dtardivel will be back from vacancies next tuesday | 15:02 |
acabot | s/vacancies/vacations | 15:03 |
alexchadin | jed56: If we use only AZ and HA to specify scope, there is no need to use Heat naming | 15:03 |
jed56 | +2 | 15:03 |
jed56 | Agree | 15:03 |
alexchadin | next: what if our AZ contains vm1-vm5 and we want to exclude vm3 from that list? I think, we can add "Exclude" field, where we can list some resources that will be ignored | 15:05 |
alexchadin | exclude field to the json or yaml audit scope file when we create audit template | 15:06 |
jed56 | so just before to clone the cluster state you will remove the excluded Vms | 15:06 |
jed56 | just after | 15:06 |
alexchadin | yes | 15:07 |
jed56 | this is a good way to do it. let me think, if I have another idea | 15:07 |
alexchadin | no problem:) | 15:07 |
jed56 | I don't another idea for now :p | 15:10 |
jed56 | you think that you will probably apply the same logic for the hosts | 15:10 |
alexchadin | next: if we have "exclude" section, where we can list vms, then it would be good to include vms to "include" section too | 15:11 |
alexchadin | so we can operate 3 types of resources: hosts, AZ, HA | 15:11 |
jed56 | I don't understand why we need "include" | 15:12 |
alexchadin | hm | 15:12 |
alexchadin | maybe it is wrong naming | 15:12 |
jed56 | IMHO, we have the cluster state and which we apply the filters based on the "exlcude" | 15:12 |
jed56 | on | 15:12 |
alexchadin | hm | 15:12 |
alexchadin | ok, sorry:D | 15:13 |
alexchadin | you are right, we just can exclude ones we don't need | 15:13 |
jed56 | https://ru.wikipedia.org/wiki/%D0%A2%D0%B5%D0%BE%D1%80%D0%B8%D1%8F_%D0%BC%D0%BD%D0%BE%D0%B6%D0%B5%D1%81%D1%82%D0%B2 | 15:14 |
jed56 | :) | 15:14 |
alexchadin | :) | 15:14 |
alexchadin | one question is left | 15:15 |
jed56 | :p | 15:15 |
alexchadin | Do we need scope class? | 15:15 |
alexchadin | I'm not sure about it | 15:16 |
alexchadin | https://review.openstack.org/#/c/339456/2/specs/newton/approved/define-the-audit-scope.rst | 15:16 |
alexchadin | 281 line | 15:16 |
jed56 | we don't need that | 15:17 |
jed56 | we need just a class that can filtred_cluster_state = apply(current_cluster_state) | 15:17 |
vincentfrancoise | alexchadin: BTW we need to be able to access both the scoped CDM and the global CDM | 15:17 |
jed56 | cluster_data_model | 15:18 |
alexchadin | cool, will think about it | 15:18 |
alexchadin | well, I suppose that all I wanted to discuss:) | 15:19 |
alexchadin | that's | 15:19 |
alexchadin | thank you, jed56 and vincentfrancoise! | 15:20 |
jed56 | alexchadin: just to clarify don't take into account the last sentence of vincentfrancoise :) | 15:25 |
vincentfrancoise | +1 ^ | 15:25 |
jed56 | alexchadin: thanks you | 15:25 |
alexchadin | I'm out, have a nice evening:) | 15:25 |
vincentfrancoise | we keep it simple and only provide the CDM after applying the scope filters | 15:26 |
vincentfrancoise | see you :) | 15:26 |
*** alexchadin has quit IRC | 15:26 | |
*** jiteka-away is now known as jiteka | 15:31 | |
jiteka | hey guys, I've got another question on top of my mind about watcher | 15:32 |
jiteka | in a context of heterogeneous fleet of hypervisor/compute nodes with different kind of hardware type and capabilities, did watcher can be used to audit the whole fleet periodically and run some "silent" benchmark and apply a score on each that can be use to compare hosts efficiency at the scheduling step (new build or migration) | 15:34 |
jiteka | I will maybe need to read a little bit more the documentation as I probably ask really dumb question right now | 15:35 |
vincentfrancoise | jiteka: watcher can has continuous audits which can produce action plans with some actions and some efficacy indicators | 15:36 |
vincentfrancoise | so score computations are usually done within the execution of a strategy | 15:37 |
vincentfrancoise | so the idea here would be to add a new efficacy indicator that would contain the computed scores | 15:38 |
jiteka | so the only limits of those indicators | 15:39 |
vincentfrancoise | but it's not exposed straight out-of-the-box since a score is relative to a given strategy | 15:39 |
jiteka | are the metrics you get from ceilometer ? | 15:39 |
vincentfrancoise | yes | 15:40 |
vincentfrancoise | did I answer your question? | 15:40 |
*** danpawlik has quit IRC | 15:50 | |
*** vincentfrancoise has quit IRC | 16:00 | |
jiteka | yes you did | 16:01 |
jiteka | but you're not here to see it | 16:01 |
jiteka | :D | 16:01 |
*** thorst_ has quit IRC | 16:58 | |
*** jwcroppe has quit IRC | 17:16 | |
*** jwcroppe has joined #openstack-watcher | 17:16 | |
*** harlowja has joined #openstack-watcher | 17:27 | |
*** thorst_ has joined #openstack-watcher | 17:32 | |
*** thorst_ has quit IRC | 17:37 | |
*** thorst_ has joined #openstack-watcher | 17:40 | |
*** thorst_ has quit IRC | 18:12 | |
*** thorst_ has joined #openstack-watcher | 18:14 | |
*** wootehfoot has joined #openstack-watcher | 18:27 | |
*** Zucan has joined #openstack-watcher | 19:50 | |
*** thorst_ has quit IRC | 20:02 | |
*** thorst_ has joined #openstack-watcher | 20:08 | |
*** thorst_ has quit IRC | 20:08 | |
*** thorst_ has joined #openstack-watcher | 20:08 | |
*** Zucan has quit IRC | 20:44 | |
*** tri2sing_ has joined #openstack-watcher | 21:15 | |
*** tri2sing_ has left #openstack-watcher | 21:17 | |
*** tri2sing has joined #openstack-watcher | 21:19 | |
*** hvprash has quit IRC | 21:21 | |
*** hvprash has joined #openstack-watcher | 21:21 | |
*** jwcroppe has quit IRC | 21:28 | |
*** jwcroppe has joined #openstack-watcher | 21:28 | |
*** jwcroppe has quit IRC | 21:29 | |
*** michaelgugino has quit IRC | 21:37 | |
*** esberglu has quit IRC | 21:48 | |
*** hvprash_ has joined #openstack-watcher | 22:27 | |
*** jwcroppe has joined #openstack-watcher | 22:29 | |
*** hvprash has quit IRC | 22:31 | |
*** hvprash_ has quit IRC | 22:32 | |
*** thorst_ has quit IRC | 22:32 | |
*** hvprash has joined #openstack-watcher | 22:32 | |
*** wootehfoot has quit IRC | 22:34 | |
*** jwcroppe has quit IRC | 22:34 | |
*** hvprash has quit IRC | 22:37 | |
*** thorst_ has joined #openstack-watcher | 22:49 | |
*** thorst_ has quit IRC | 22:54 | |
*** jwcroppe has joined #openstack-watcher | 23:00 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!