| *** yuanying has quit IRC | 00:10 | |
| *** yuanying has joined #openstack-watcher | 00:15 | |
| openstackgerrit | YumengBao proposed openstack/watcher master: Use https to access git https://review.openstack.org/446253 | 01:01 |
|---|---|---|
| *** sanfern has quit IRC | 01:04 | |
| *** sanfern has joined #openstack-watcher | 01:05 | |
| openstackgerrit | YumengBao proposed openstack/watcher master: Use https to access git https://review.openstack.org/446253 | 01:34 |
| *** sanfern has quit IRC | 01:39 | |
| *** pshedimb has quit IRC | 01:56 | |
| *** pshedimb has joined #openstack-watcher | 02:02 | |
| *** karthikpr has joined #openstack-watcher | 02:15 | |
| *** karthikpr has quit IRC | 02:20 | |
| *** pshedimb has quit IRC | 02:45 | |
| *** yuanying has quit IRC | 03:06 | |
| *** zhurong has joined #openstack-watcher | 03:44 | |
| *** sanfern has joined #openstack-watcher | 04:03 | |
| *** adisky_ has joined #openstack-watcher | 04:17 | |
| *** yuanying has joined #openstack-watcher | 04:46 | |
| *** pshedimb_ has joined #openstack-watcher | 05:14 | |
| *** zhurong has quit IRC | 05:25 | |
| *** adisky_ has quit IRC | 06:18 | |
| *** adisky_ has joined #openstack-watcher | 06:18 | |
| *** hidekazu has quit IRC | 06:21 | |
| *** adisky_ has quit IRC | 06:30 | |
| openstackgerrit | Béla Vancsics proposed openstack/watcher master: Reduced the code complexity https://review.openstack.org/441873 | 06:45 |
| *** alexchadin has joined #openstack-watcher | 07:13 | |
| *** hidekazu has joined #openstack-watcher | 07:26 | |
| *** pshedimb_ has quit IRC | 07:33 | |
| *** adisky_ has joined #openstack-watcher | 08:05 | |
| *** vincentfrancoise has joined #openstack-watcher | 08:14 | |
| *** dtardivel has joined #openstack-watcher | 08:15 | |
| dtardivel | Yumeng: hi | 08:15 |
| *** yuanying has quit IRC | 08:19 | |
| adisky_ | alexchadin: hi | 08:22 |
| alexchadin | hi adisky_ | 08:22 |
| adisky_ | its about installation guide ine openstack manuals. | 08:23 |
| adisky_ | do we need make linux distro specific packages for watcher?? | 08:24 |
| alexchadin | adisky_: good question | 08:29 |
| adisky_ | alexchadin: :| | 08:30 |
| alexchadin | adisky_: I think yes, since there are different package management software: yum and apt-get | 08:32 |
| adisky_ | alexchadin: yes, i can make packages but dont know how to upload them | 08:32 |
| alexchadin | adisky_: being on your side, I would ask openstack-manuals team about it | 08:33 |
| alexchadin | adisky_: I think, they will give you good starting point here | 08:33 |
| adisky_ | alexchadin: thnx, i will try to search if there is a guide available. | 08:34 |
| alexchadin | adisky_: take a look https://docs.openstack.org/contributor-guide/ | 08:34 |
| adisky_ | alexchadin: ok | 08:36 |
| *** yuanying has joined #openstack-watcher | 08:55 | |
| Yumeng | dtardivel:hi | 09:27 |
| Yumeng | I was just having a meeting | 09:27 |
| dtardivel | Yumeng: yesterday, on IRC meeting, we wrote about splitting your spec in 3 different specs. Are you agree with this proposition ? | 09:29 |
| Yumeng | I am OK with that. | 09:30 |
| dtardivel | Ok, great :) | 09:30 |
| dtardivel | Yumeng: when you will write the spec about how to build a 'baremetal' data model, could you explain the prerequisite that, in Ironic, node should be created with the extra metadata hypervisor ID. | 09:33 |
| Yumeng | dtardivel: do we use ironic? and following this From a Watcher point of view, It comes down to this: . Implements a new Action to power off/on a physical server by using Ironic API . Build a new baremetal (ironic) data model . Implement a new strategy based on 'baremetal' and 'compute' data models, which could trigger 'compute' and 'baremetal' actions. | 09:33 |
| vincentfrancoise | Yumeng: we could also extend the current data model to add a baremetal dimension | 09:34 |
| dtardivel | vincentfrancoise: I not fan of your proposal. | 09:35 |
| vincentfrancoise | Yumeng: as suggested during the PTG (https://etherpad.openstack.org/p/pike-watcher-ptg line 253) | 09:35 |
| vincentfrancoise | dtardivel: ^ | 09:35 |
| dtardivel | I prefer to build different data models, and use some of them in strategy level | 09:36 |
| vincentfrancoise | I personally don't care but I was just referring to what seemed to have been decided during the PTG | 09:36 |
| Yumeng | dtardivel: ok. I will propose new specs. | 09:37 |
| alexchadin | hi | 09:37 |
| vincentfrancoise | alexchadin: hi | 09:38 |
| Yumeng | alexchadin:hi | 09:38 |
| alexchadin | here is brainstorming-etherpad: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming | 09:38 |
| alexchadin | I've also added it to Forum wiki: https://wiki.openstack.org/wiki/Forum/Boston2017#Project_Teams | 09:39 |
| alexchadin | feel free to share your thoughts and questions | 09:39 |
| dtardivel | Yumeng: vincentfrancoise: is the new unified data model will be a new plugin ? | 09:44 |
| vincentfrancoise | dtardivel: I don't really know what's been said on the matter at the PTG | 09:45 |
| vincentfrancoise | dtardivel: but the way Intel designed it is actually within the current CDM graph model | 09:46 |
| vincentfrancoise | dtardivel: I guess you would have some optional branches of the graph that would be built if the service is up | 09:47 |
| vincentfrancoise | dtardivel: but this is still unclear to me | 09:47 |
| *** alexchadin has quit IRC | 09:49 | |
| openstackgerrit | Pradeep Kumar Singh proposed openstack/watcher master: Prevent the migration of VM with 'optimize' False in VM metadata https://review.openstack.org/443070 | 09:54 |
| Yumeng | vincentfrancoise:dtardivel: I just quickly go over https://etherpad.openstack.org/p/pike-watcher-ptg we agreed that we should have a separate CDM for storage(line 239), and for other topics concerning CDM we just adding new data model into current CDM (line 243,253) | 09:59 |
| Yumeng | vincentfrancoise:dtardivel: and I got a question: when we add more and more data models into current CDM, it might get very large. Will this affect efficiency of watcher function? or any other impact? | 10:05 |
| vincentfrancoise | Yumeng: The model is maintain in the background, so this background processing will grow slower | 10:06 |
| dtardivel | Yumeng: yes it was one of my remarks during the PTG | 10:07 |
| vincentfrancoise | Yumeng: but the execution of a strategy only consist in cloning the current representation at execution time | 10:07 |
| vincentfrancoise | Yumeng: so the execution time of an audit should grow fairly linearly as compared to the size of the infra | 10:08 |
| vincentfrancoise | Yumeng: although that's a guess that is difficult to accurately assess | 10:09 |
| Yumeng | vincentfrancoise:dtardivel: I am interested in the unified model of the CDM, my only concern is the potential impact. dtardivel, you just mentioned "is the new unified data model will be a new plugin ?" do you have any ideas? Is there any way we might have to reduce this impact as much as possible? | 10:15 |
| vincentfrancoise | Yumeng: having multiple models just means splitting the problem in many graph which will all run in the background together | 10:16 |
| Yumeng | vincentfrancoise: so finally these two ways are expected to have same impact if there is any | 10:18 |
| vincentfrancoise | Yumeng: the same I don't know, but the same order of magnitude is probable | 10:18 |
| Yumeng | vincentfrancoise: Make sense to me. | 10:19 |
| vincentfrancoise | Yumeng: by making separate CDMs, you can play around with their refresh rate to slightly lower their maintenance cost but that would be at the expense of its correctness | 10:21 |
| vincentfrancoise | Yumeng: but I would guess that doing such a thing will only provide a slight gain | 10:21 |
| vincentfrancoise | Yumeng: codewise both approaches have advantages and drawbacks | 10:22 |
| vincentfrancoise | Yumeng: 1 CDM means that you can do CDM filtering more effectively because 1 graph = 1 filtering logic | 10:23 |
| vincentfrancoise | Yumeng: but splitting into many CDMs reduces the complexity of each model which eases the maintenance / the number of possible bugs | 10:24 |
| vincentfrancoise | that's a discussion to have with alexchadin too I guess | 10:25 |
| Yumeng | vincentfrancoise:dtardivel: Fair enough. Thx vincent. So currently, I will follow what has been agreed in https://etherpad.openstack.org/p/pike-watcher-ptg(line 253). | 10:27 |
| vincentfrancoise | Yumeng: what's important with supporting Ironic is to also find the notifications they emit, and listen to them to update the CDM | 10:29 |
| vincentfrancoise | Yumeng: because I personally will downvote any information that doesn't get updated via a notification | 10:30 |
| vincentfrancoise | Yumeng: because the risk of staleness would be too big | 10:30 |
| Yumeng | vincentfrancoise: I agree. Will you have more discussion with Alex about CDMs? next time when you discuss, please let me know. and BTW shall we put this into open discussion in our next irc meeting ? | 10:35 |
| vincentfrancoise | Yumeng: maybe the IRC open discussion is a good opportunity? | 10:37 |
| vincentfrancoise | Yumeng: if I see him and also have time, I willm but if you disuss with him too, that'd be good too :) | 10:38 |
| Yumeng | vincentfrancoise: I think so. but we usually don't have much time left for open discussion haha | 10:38 |
| Yumeng | vincentfrancoise: No problem, I will. | 10:40 |
| Yumeng | vincentfrancoise:see you! time to go home for dinner :) | 10:40 |
| vincentfrancoise | Yumeng: enjoy your meal | 10:41 |
| vincentfrancoise | :) | 10:41 |
| Yumeng | vincentfrancoise: :) | 10:41 |
| *** Yumeng has quit IRC | 10:41 | |
| *** sanfern has quit IRC | 10:48 | |
| *** sanfern has joined #openstack-watcher | 11:38 | |
| *** pkoniszewski has left #openstack-watcher | 13:54 | |
| *** vincentfrancois1 has joined #openstack-watcher | 13:55 | |
| *** vincentfrancois1 has quit IRC | 14:35 | |
| *** logan- has quit IRC | 14:46 | |
| *** pshedimb_ has joined #openstack-watcher | 14:46 | |
| *** logan- has joined #openstack-watcher | 14:46 | |
| *** danpawlik has quit IRC | 14:55 | |
| *** pshedimb_ has quit IRC | 14:57 | |
| *** karthikpr has joined #openstack-watcher | 15:04 | |
| *** vincentfrancois1 has joined #openstack-watcher | 15:53 | |
| *** pshedimb_ has joined #openstack-watcher | 16:00 | |
| *** karthikpr has quit IRC | 16:23 | |
| *** karthikpr has joined #openstack-watcher | 16:27 | |
| *** karthikpr has quit IRC | 16:38 | |
| *** vincentfrancois1 has quit IRC | 16:40 | |
| *** karthikpr has joined #openstack-watcher | 17:01 | |
| *** karthikpr has quit IRC | 17:12 | |
| openstackgerrit | Merged openstack/watcher master: Updated from global requirements https://review.openstack.org/445935 | 17:32 |
| *** sanfern has quit IRC | 17:45 | |
| *** karthikpr has joined #openstack-watcher | 17:57 | |
| *** aspiers has quit IRC | 18:23 | |
| *** pshedimb_ has quit IRC | 18:26 | |
| *** karthikpr has quit IRC | 18:31 | |
| *** aspiers has joined #openstack-watcher | 18:35 | |
| *** pshedimb_ has joined #openstack-watcher | 18:51 | |
| *** karthikpr has joined #openstack-watcher | 19:00 | |
| *** karthikpr has quit IRC | 19:06 | |
| *** dtardivel has quit IRC | 19:10 | |
| *** karthikpr has joined #openstack-watcher | 19:11 | |
| *** pshedimb_ has quit IRC | 19:40 | |
| *** pshedimb_ has joined #openstack-watcher | 19:50 | |
| *** karthikpr has quit IRC | 19:50 | |
| *** hidekazu has quit IRC | 20:25 | |
| *** karthikpr has joined #openstack-watcher | 20:26 | |
| *** karthikpr has quit IRC | 20:27 | |
| *** karthikpr has joined #openstack-watcher | 20:27 | |
| *** karthikpr has quit IRC | 21:28 | |
| *** pshedimb_ has quit IRC | 22:23 | |
| *** pshedimb_ has joined #openstack-watcher | 22:35 | |
| *** wootehfoot has joined #openstack-watcher | 22:57 | |
| *** pshedimb_ has quit IRC | 23:08 | |
| *** hidekazu has joined #openstack-watcher | 23:23 | |
| *** karthikpr has joined #openstack-watcher | 23:30 | |
| hidekazu | morning | 23:31 |
| *** pshedimb_ has joined #openstack-watcher | 23:36 | |
| *** pshedimb_ has quit IRC | 23:42 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!