| *** pshedimb_ has joined #openstack-watcher | 01:11 | |
| *** pshedimb_ has quit IRC | 02:34 | |
| *** sanfern has joined #openstack-watcher | 02:51 | |
| *** Yumeng has joined #openstack-watcher | 03:24 | |
| *** zhurong has joined #openstack-watcher | 03:25 | |
| openstackgerrit | licanwei proposed openstack/watcher master: exception when running 'watcher service list' https://review.openstack.org/447354 | 03:41 |
|---|---|---|
| *** zhurong has quit IRC | 04:16 | |
| *** zhurong has joined #openstack-watcher | 04:59 | |
| *** zhurong has quit IRC | 05:14 | |
| *** adisky_ has joined #openstack-watcher | 05:23 | |
| openstackgerrit | ChangBo Guo(gcb) proposed openstack/watcher master: Remove old oslo.messaging transport aliases https://review.openstack.org/447369 | 05:25 |
| *** karthikpr has quit IRC | 05:47 | |
| *** karthikpr has joined #openstack-watcher | 06:25 | |
| *** karthikpr has quit IRC | 06:29 | |
| *** alexchadin has joined #openstack-watcher | 07:19 | |
| *** Yumeng has quit IRC | 08:45 | |
| *** vincentfrancois1 has joined #openstack-watcher | 08:51 | |
| *** openstackgerrit has quit IRC | 09:02 | |
| *** vincentfrancois1 has quit IRC | 09:11 | |
| *** alexchadin has quit IRC | 09:27 | |
| *** alexchadin has joined #openstack-watcher | 09:58 | |
| *** sanfern has quit IRC | 10:49 | |
| *** Yumeng has joined #openstack-watcher | 10:49 | |
| *** karthikpr has joined #openstack-watcher | 10:57 | |
| *** karthikpr has quit IRC | 11:01 | |
| *** alexchadin has quit IRC | 11:04 | |
| *** vmahe has joined #openstack-watcher | 11:10 | |
| *** zhurong has joined #openstack-watcher | 11:18 | |
| *** alexchadin has joined #openstack-watcher | 11:33 | |
| *** zhurong has quit IRC | 11:37 | |
| alexchadin | hi vincentfrancoise | 11:41 |
| *** alexchadin has quit IRC | 12:07 | |
| *** sanfern has joined #openstack-watcher | 12:10 | |
| *** alexchadin has joined #openstack-watcher | 12:12 | |
| Yumeng | alexchadin:hi | 12:33 |
| alexchadin | hi Yumeng | 12:34 |
| Yumeng | alexchadin:Based on what has been agreed in our last irc meeting, I have spilted add-power-on-off (https://review.openstack.org/#/c/435436) into three sub-features, so there are two more specs which need your approval. | 12:34 |
| Yumeng | Can you please have a look and give any feedback so that I can start update related specs? | 12:35 |
| Yumeng | here are the links | 12:35 |
| Yumeng | https://blueprints.launchpad.net/watcher/+spec/build-baremetal-data-model-in-watcher | 12:35 |
| Yumeng | https://blueprints.launchpad.net/watcher/+spec/strategy-to-trigger-power-on-and-power-off-actions | 12:35 |
| Yumeng | only these two needs approval | 12:35 |
| Yumeng | https://blueprints.launchpad.net/watcher/+spec/add-power-on-off this one is already approved and I just updated | 12:36 |
| alexchadin | Yumeng: let me take a look | 12:37 |
| Yumeng | alexchadin: Thanks! you can do it any time at your convenience. if any questions email me at bao.yumeng@zte.com.cn or ping me tomorrow? | 12:39 |
| alexchadin | Yumeng: it looks good, but you need to link all these three BP with dependencies | 12:39 |
| alexchadin | Yumeng: Strategy depends on Action, Action depends on Ironic Data Model | 12:40 |
| Yumeng | alexchadin: OK. Done! you can see the dependencies now | 12:42 |
| alexchadin | Yumeng: now it looks perfectly ;) | 12:43 |
| *** andreaf has joined #openstack-watcher | 12:44 | |
| Yumeng | alexchadin::Thanks Alex! I have updated them as approved. | 12:44 |
| Yumeng | alexchadin: see you then | 12:45 |
| andreaf | hello folks - could I have reviews on https://review.openstack.org/#/c/442756/ please? | 12:45 |
| alexchadin | Yumeng: have a nice day | 12:45 |
| alexchadin | hi andreaf | 12:45 |
| andreaf | alexchadin: hi | 12:45 |
| andreaf | alexchadin: see http://lists.openstack.org/pipermail/openstack-dev/2017-February/112938.html | 12:46 |
| *** Yumeng has left #openstack-watcher | 12:46 | |
| andreaf | alexchadin: we want refactor scenario tests on Tempest side, so I would ask you to keep what you need of it the watcher tempest plugin - at least until we are able to offer a stable interface around that | 12:47 |
| alexchadin | andreaf: I see, thank you for your work, I will review it now | 12:47 |
| andreaf | alexchadin: cool, thank you! | 12:48 |
| alexchadin | andreaf: is it just a copy of tempest.scenario.manager? | 12:49 |
| andreaf | alexchadin: yeah pretty much | 12:49 |
| andreaf | the original scenario.manager module includes 4 classes but you only use the first one, so I removed the 3 unused ones | 12:49 |
| alexchadin | andreaf: Have you tried to launch functional tests with it? | 12:50 |
| andreaf | alexchadin: I only relied on what runs in the gate | 12:50 |
| andreaf | alexchadin: there's a failure on gate-watcher-dsvm-multinode-ubuntu-xenial-nv, but it seems definitely unrelated | 12:51 |
| andreaf | the job is non voting, because of failures I suppose? | 12:51 |
| alexchadin | andreaf: yeah, it fails time by time | 12:51 |
| alexchadin | andreaf: +1 | 12:51 |
| alexchadin | andreaf: I'm ok with this patch | 12:53 |
| andreaf | alexchadin: cool, thanks for reviewing | 12:53 |
| alexchadin | andreaf: +2 from me | 12:53 |
| alexchadin | hi adisky_ | 12:54 |
| adisky_ | hi alexchadin | 12:54 |
| alexchadin | I've had a discussion with dims about Debian-related packages | 12:55 |
| alexchadin | adisky_: ^ | 12:55 |
| alexchadin | adisky_: as you can see, there is a thread that reveals the problem: http://lists.openstack.org/pipermail/openstack-dev/2017-February/112220.html | 12:56 |
| alexchadin | adisky_: no one have taken this work | 12:56 |
| adisky_ | alexchadin: ohh | 12:57 |
| adisky_ | alexchadin: so as of now, i will write only for rpm distros | 13:01 |
| *** adisky_ has left #openstack-watcher | 13:01 | |
| alexchadin | adisky_: I will contact zigo to gather info about managing packages in Debian. I hope we can do it by ourselves | 13:02 |
| vincentfrancoise | andreaf: Hi, I just merged your PS | 13:05 |
| alexchadin | vincentfrancoise: hi | 13:08 |
| *** openstackgerrit has joined #openstack-watcher | 13:10 | |
| openstackgerrit | Merged openstack/watcher master: Local copy of scenario test base class https://review.openstack.org/442756 | 13:10 |
| vincentfrancoise | alexchadin: hi | 13:11 |
| vincentfrancoise | alexchadin: since you are here, I want to discuss with you about the ironic integration with Watcher | 13:12 |
| alexchadin | vincentfrancoise: I wanted to discuss Py3.5, but ok | 13:12 |
| alexchadin | vincentfrancoise: let's discuss Ironic firstly ;) | 13:13 |
| vincentfrancoise | alexchadin: as you wish | 13:13 |
| vincentfrancoise | alexchadin: did you see the discussion I had with licanwei at the end of last week? | 13:13 |
| alexchadin | vincentfrancoise: yeap | 13:13 |
| vincentfrancoise | alexchadin: cool so no need for me to re-explain it then :) | 13:14 |
| alexchadin | vincentfrancoise: you propose to extend current CDM? | 13:15 |
| vincentfrancoise | alexchadin: what option do you prefer ? Separate CDM for ironic or integrate ironic into the current CDM? | 13:15 |
| vincentfrancoise | alexchadin: I personally don't mind either way since there's no silver bullet I guess | 13:16 |
| vincentfrancoise | alexchadin: dtardivel if in favour of the separate CDM and I can't remember which one licanwei was preferring | 13:17 |
| vincentfrancoise | alexchadin: yumeng I mean* | 13:17 |
| alexchadin | vincentfrancoise: I re-read your conversation | 13:18 |
| vincentfrancoise | alexchadin: but she was about to carry on with option 2 and add it to the current CDM | 13:18 |
| vincentfrancoise | alexchadin: you have the link? I can give it to you | 13:18 |
| alexchadin | vincentfrancoise: on the one hand, if we add Ironic to the current CDM, we will extremely raise count of objects in graph | 13:19 |
| *** gabor_antal_km is now known as gabor_antal | 13:20 | |
| alexchadin | vincentfrancoise: it may bring a lot of problems with debugging it and maintaining | 13:20 |
| *** karthikpr has joined #openstack-watcher | 13:22 | |
| alexchadin | vincentfrancoise: on the other hand, having two CDM (or more?) will affect on background mechanism | 13:23 |
| vincentfrancoise | alexchadin: yes that's about it | 13:23 |
| vincentfrancoise | alexchadin: the more I think about it, the more I reckon we should go for a separate CDM but that's only a gut feeling | 13:24 |
| *** karthikpr has quit IRC | 13:26 | |
| alexchadin | vincentfrancoise: the easier we make it, the easier our life will be | 13:26 |
| vincentfrancoise | alexchadin: if you don't have an answer yet it's not a problem but maybe that's something we need to discuss in priority on wednesday | 13:26 |
| vincentfrancoise | alexchadin: I agree but both will make our life harder | 13:27 |
| alexchadin | vincentfrancoise: we have two ways to update CDM, right? Using notifications and background job | 13:27 |
| vincentfrancoise | alexchadin: but with N different CDMs, if one goes wrong, it doesn't break everything | 13:27 |
| vincentfrancoise | alexchadin: which is why I would probably go for option 22 | 13:27 |
| vincentfrancoise | 2* | 13:28 |
| vincentfrancoise | alexchadin: yes | 13:28 |
| alexchadin | vincentfrancoise: actually, I would prefer to leave notifications only way, cause it allows Watcher to be as synced as possible | 13:29 |
| alexchadin | vincentfrancoise: in this case, I would vote for separating CDM | 13:30 |
| vincentfrancoise | alexchadin: the background job can be useful if the notifications do not contain and/or cover all data | 13:31 |
| alexchadin | vincentfrancoise: Doesn't Nova notifications provide all necessary data? | 13:32 |
| vincentfrancoise | alexchadin: but if all the needed info are here (which is the case for nova), then we just need the job once to create the initial CDM and let the notifications handle the rest | 13:32 |
| alexchadin | vincentfrancoise: most of primary OpenStack projects are going to support full-notifications actions. | 13:33 |
| alexchadin | vincentfrancoise: in case of problems, we can contact project developers to ask them for adding some specified infos if it is possible | 13:34 |
| vincentfrancoise | alexchadin: in that case, maybe we can make the background job optional | 13:35 |
| vincentfrancoise | alexchadin: and disable it by default | 13:35 |
| alexchadin | vincentfrancoise: +1 | 13:35 |
| vincentfrancoise | alexchadin: then create as many CDMs as we want (such as Ironic) | 13:36 |
| vincentfrancoise | alexchadin: the other issue we have with having many CDMs is that the audit scope wouldn't work properly I think | 13:36 |
| alexchadin | vincentfrancoise: what's the issue? | 13:37 |
| vincentfrancoise | alexchadin: well imagine someone creating a new nova model with a slightly different data structure | 13:38 |
| vincentfrancoise | alexchadin: then the scope will not be able to filter a data structure it doesn't know | 13:38 |
| vincentfrancoise | alexchadin: so it would break I think | 13:38 |
| vincentfrancoise | alexchadin: the get_scoped_model() method is strongly related to the CDM we want to scope | 13:40 |
| vincentfrancoise | alexchadin: so maybe we should make it a requirement to implement a "CDM Scoper" for every new CDM we create | 13:41 |
| vincentfrancoise | alexchadin: and say that the one you did is specific to the compute CDM | 13:41 |
| alexchadin | vincentfrancoise: our current scope is based on Nova CDM. Why can't developer write its own Scope for new CDM? | 13:42 |
| *** karthikpr has joined #openstack-watcher | 13:42 | |
| alexchadin | vincentfrancoise: you want to bind scope to CDM? | 13:43 |
| vincentfrancoise | alexchadin: +1, we just need to say it in the docs and refactor the codebase to make it simple to implement a new one | 13:43 |
| vincentfrancoise | alexchadin: yes | 13:43 |
| vincentfrancoise | alexchadin: but the scope schema should always be the same | 13:44 |
| alexchadin | vincentfrancoise: why can't developer extend it in CDM boundaries? | 13:45 |
| vincentfrancoise | alexchadin: A single audit scope schema structure for all CDMs, but one scoping implementation per CDM | 13:45 |
| *** edleafe- is now known as edleafe | 13:45 | |
| vincentfrancoise | alexchadin: ah sorry I wasn't precise enough | 13:46 |
| vincentfrancoise | alexchadin: The developer should be able to add new options | 13:46 |
| vincentfrancoise | alexchadin: but the operator should only see a unified schema that collected all the extra options | 13:46 |
| vincentfrancoise | alexchadin: or something like this | 13:46 |
| alexchadin | vincentfrancoise: one more BP, please ;D | 13:50 |
| vincentfrancoise | alexchadin: i.e. a core schema structure onto which we add extra sections | 13:50 |
| vincentfrancoise | alexchadin: :D | 13:51 |
| alexchadin | We will rejoice Yumeng, once she returns | 13:51 |
| *** exploreshaifali has joined #openstack-watcher | 13:57 | |
| vincentfrancoise | alexchadin: yes :p | 13:57 |
| vincentfrancoise | alexchadin: what about python 3.5 now? | 13:57 |
| *** vmahe has left #openstack-watcher | 13:57 | |
| alexchadin | vincentfrancoise: Supporting of Py3.5 in OS projects is one of the main goals for Pike cycle | 13:58 |
| alexchadin | vincentfrancoise: I've seen this PS this morning: https://review.openstack.org/#/c/446189/ | 13:58 |
| alexchadin | vincentfrancoise: and here is Completion Criteria: https://governance.openstack.org/tc/goals/pike/python35.html | 13:59 |
| alexchadin | vincentfrancoise: I propose to test our functional tests and try to make Py3.5 default interpreter for Watcher | 14:00 |
| vincentfrancoise | alexchadin: do we have to keep python 2.7? | 14:01 |
| alexchadin | vincentfrancoise: for now yes | 14:01 |
| vincentfrancoise | alexchadin: because if so we should have 2 separate tempest jobs I'd say | 14:01 |
| sballe_ | morning | 14:02 |
| alexchadin | sballe_: morning | 14:02 |
| alexchadin | vincentfrancoise: is there version-related issues? | 14:02 |
| vincentfrancoise | alexchadin: but the py27 one could run only a subset of the lot | 14:02 |
| vincentfrancoise | alexchadin: no, it's just that most companies still prefer py27 so we shouldn't make sure we don't break anything because we switched to py35 | 14:04 |
| vincentfrancoise | sballe_: hi | 14:04 |
| vincentfrancoise | alexchadin: but the py27 one would not have to be a multinode job I'd say | 14:04 |
| alexchadin | vincentfrancoise: EOL of 2.7 is 2020 | 14:04 |
| alexchadin | vincentfrancoise: I will add it to open discussions | 14:06 |
| vincentfrancoise | alexchadin: I agree, we can remove it in 1 or 2 years then | 14:06 |
| alexchadin | vincentfrancoise: since there are a lot of things to discuss on Wednesday, I will take 30 minutes for Open Discussions | 14:07 |
| vincentfrancoise | alexchadin: IMHO, move the open discussion before the code reviews | 14:07 |
| alexchadin | vincentfrancoise: good proposal :) | 14:08 |
| andreaf | vincentfrancoise: thank you! | 14:27 |
| *** alexchadin has quit IRC | 15:04 | |
| *** exploreshaifali has quit IRC | 15:08 | |
| *** exploreshaifali has joined #openstack-watcher | 15:23 | |
| *** pshedimb_ has joined #openstack-watcher | 15:37 | |
| *** shaifali has joined #openstack-watcher | 16:45 | |
| *** exploreshaifali has quit IRC | 16:48 | |
| openstackgerrit | Vincent Françoise proposed openstack/watcher master: Added tempest test for workload_stabilization https://review.openstack.org/393355 | 16:59 |
| *** danpawlik has quit IRC | 17:07 | |
| openstackgerrit | Vincent Françoise proposed openstack/watcher master: Added Actuator Strategy https://review.openstack.org/425110 | 17:15 |
| *** pshedimb_ has quit IRC | 17:18 | |
| *** shaifali has quit IRC | 17:34 | |
| *** brunograz has quit IRC | 17:37 | |
| *** brunograz has joined #openstack-watcher | 17:39 | |
| *** shaifali has joined #openstack-watcher | 17:49 | |
| *** vincentfrancoise has quit IRC | 17:50 | |
| *** sanfern has quit IRC | 18:03 | |
| *** shaifali has quit IRC | 18:19 | |
| *** pshedimb_ has joined #openstack-watcher | 18:22 | |
| *** shaifali has joined #openstack-watcher | 18:27 | |
| openstackgerrit | Chris Spencer proposed openstack/watcher master: Adding tempest test that executes outlet_temp_control strategy. https://review.openstack.org/439184 | 18:28 |
| *** wootehfoot has joined #openstack-watcher | 18:42 | |
| *** shaifali has quit IRC | 18:44 | |
| *** shaifali has joined #openstack-watcher | 18:46 | |
| *** pshedimb_ has quit IRC | 20:07 | |
| *** pshedimb_ has joined #openstack-watcher | 20:20 | |
| openstackgerrit | Chris Spencer proposed openstack/watcher master: Adding tempest test that executes outlet_temp_control strategy. https://review.openstack.org/439184 | 20:29 |
| *** shaifali has quit IRC | 20:32 | |
| *** pshedimb_ has quit IRC | 21:14 | |
| *** pshedimb_ has joined #openstack-watcher | 21:21 | |
| openstackgerrit | Chris Spencer proposed openstack/watcher master: Adding tempest test that executes outlet_temp_control strategy. https://review.openstack.org/439184 | 22:14 |
| *** wootehfoot has quit IRC | 23:14 | |
| *** hidekazu has joined #openstack-watcher | 23:24 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!