Wednesday, 2017-07-26

*** yujunz has joined #openstack-vitrage00:24
openstackgerritxupeipei proposed openstack/vitrage-specs master: add snmp-parsing-service.rst  https://review.openstack.org/48681201:33
*** zengjianfang has quit IRC01:40
*** yujunz has quit IRC02:17
*** yujunz has joined #openstack-vitrage02:36
*** yujunz has quit IRC03:40
*** ifat_afek has joined #openstack-vitrage05:56
openstackgerritIfat Afek proposed openstack/vitrage master: Doc Migration: move the developer guide documents under the "contributor" folder  https://review.openstack.org/48692706:28
openstackgerritIfat Afek proposed openstack/vitrage master: Doc Migration: move the developer guide documents under the "contributor" folder  https://review.openstack.org/48692706:32
openstackgerritIfat Afek proposed openstack/vitrage master: Doc Migration: move the developer guide documents under the "contributor" folder  https://review.openstack.org/48692706:35
openstackgerritIfat Afek proposed openstack/vitrage master: Doc Migration: move the developer guide documents under the "contributor" folder  https://review.openstack.org/48692706:38
openstackgerritRajat Sharma proposed openstack/python-vitrageclient master: Replaces yaml.load() with yaml.safe_load()  https://review.openstack.org/48729906:43
openstackgerritEylon Malin proposed openstack/vitrage master: listener_service - enable listen to multiple topics + specify exchange name  https://review.openstack.org/48696707:01
*** yujunz has joined #openstack-vitrage07:36
openstackgerritIfat Afek proposed openstack/vitrage master: DO NOT MERGE - Disable swift services in Vitrage devstack  https://review.openstack.org/48731107:41
*** yujunz has quit IRC07:54
*** yujunz has joined #openstack-vitrage08:01
*** efoley has joined #openstack-vitrage08:23
*** efoley_ has joined #openstack-vitrage08:24
*** efoley has quit IRC08:24
*** efoley_ is now known as efoley08:35
yujunzifat_afek it seems some implemented blueprint are not marked in Pike series. e.g. https://blueprints.launchpad.net/vitrage/+spec/not-operator-support08:42
yujunzI'm trying to get an overview of the Pike release for downstream development in ZTE08:42
ifat_afekYou are right, thanks!08:42
ifat_afekI went over that list more than once, and somehow missed it…08:43
ifat_afekyujunz: makes sense08:44
ifat_afekLet me know if you have any other questions, or find other mismatches…08:44
yujunzSure08:45
ifat_afekyujunz: I’m trying to see the effect of your healthcheck change in my environment. Before the change I had: passed=True, status_code=200.08:49
yujunzYes08:49
ifat_afekAfter the change I get: detailed=False, reasons=[]08:49
ifat_afekWhy is it better?08:49
ifat_afekTo me it sounds like a “False” healthcheck, i.e. indicates a problem...08:50
yujunzOK. That it what returned from healthcheck api...08:51
ifat_afekDo other projects have something else? is there a standard?08:52
yujunzNo, I think it is up to the client for the display08:53
ifat_afekSo why do you think that displaying the original message is better? to me it doesn’t look so clear08:54
yujunzI think the main difference is when you have an error08:55
yujunzBecause "details" and "reasons" will be hidden from user08:55
yujunzAnd you don't get enough information on the health status08:55
ifat_afekWhat chould be written in details, other than false?08:56
ifat_afekcould08:56
yujunzdetails: True, reasons=[..., ...]08:56
yujunzWhen you have details, the reasons will be filled08:56
ifat_afekSo, you are saying there could be three cases:08:57
ifat_afek1. All is ok, details = False08:57
ifat_afek2. problem, details=blabla, reasons=blabla208:57
ifat_afek3. exception08:57
ifat_afekSo why not write “pass”=True and also the details and reasons? or write the details and reasons if not passed?08:58
ifat_afekI just think it’s confusing this way, to call healthcheck and see “False”08:58
yujunzOK, that make sense.08:59
yujunzI'll check oslo.middleware.healthcheck again and update the patch09:00
yujunzIt supposed to give "OK" in reasons as described in https://github.com/openstack/oslo.middleware/blob/master/oslo_middleware/healthcheck/__init__.py#L9009:03
yujunzNot sure why an empty array is returned, ifat_afek09:03
ifat_afekCould be a problem in my env then09:04
ifat_afekmy devstack is a bit old09:05
ifat_afekIs it running well in your env?09:05
yujunzNo, I mean it could be an issue in oslo.middleware.healthcheck09:05
yujunzSo I'll try to dig and let you know what could be the best solution.09:05
ifat_afekOk, thanks09:05
ifat_afekAnd again, if it is working in your env then I’m fine with it09:06
yujunzOK, got it. If it is an upstream issue, I'll try to propose a patch in oslo before changing in vitrage.09:06
openstackgerritMerged openstack/vitrage-dashboard master: Update the documentation link for doc migration  https://review.openstack.org/48689709:06
yujunzAn empty reason does look confusing09:07
openstackgerritMerged openstack/vitrage-dashboard master: Doc Migration: move the developer guide under doc/source/contributor folder  https://review.openstack.org/48695709:07
ifat_afekThanks09:07
yujunzYou are welcome09:08
*** zengjianfang has joined #openstack-vitrage09:11
*** zengjianfang has quit IRC09:12
openstackgerritMerged openstack/python-vitrageclient master: Move osprofiler help message to the end of output  https://review.openstack.org/48696009:12
*** yujunz has quit IRC09:14
*** ifat_afek has quit IRC09:21
openstackgerritYujun Zhang proposed openstack/vitrage master: Add osprofiler support for RPC, api controllers and handlers  https://review.openstack.org/48548609:46
*** ifat_afek has joined #openstack-vitrage09:58
*** ifat_afek has quit IRC10:04
*** XueFeng has joined #openstack-vitrage11:17
openstackgerritYujun Zhang proposed openstack/vitrage master: Add default backend for healthcheck  https://review.openstack.org/48738812:06
openstackgerritOpenStack Proposal Bot proposed openstack/python-vitrageclient master: Updated from global requirements  https://review.openstack.org/48588812:34
*** efoley has quit IRC12:47
*** ifat_afek has joined #openstack-vitrage12:48
*** efoley has joined #openstack-vitrage12:50
*** ifat_afek has left #openstack-vitrage13:01
*** ifat_afek has joined #openstack-vitrage13:01
openstackgerritIfat Afek proposed openstack/vitrage master: DO NOT MERGE - Disable swift services in Vitrage devstack  https://review.openstack.org/48731113:34
*** aasmith has joined #openstack-vitrage13:43
openstackgerritMerged openstack/vitrage master: Add osprofiler support for RPC, api controllers and handlers  https://review.openstack.org/48548614:04
openstackgerritOpenStack Proposal Bot proposed openstack/vitrage master: Updated from global requirements  https://review.openstack.org/48643814:09
openstackgerritMerged openstack/python-vitrageclient master: Doc Migration: move the developer guide docs under contributor folder  https://review.openstack.org/48699314:10
openstackgerritOpenStack Proposal Bot proposed openstack/python-vitrageclient master: Updated from global requirements  https://review.openstack.org/48588814:23
openstackgerritYujun Zhang proposed openstack/vitrage master: Add default backend for healthcheck  https://review.openstack.org/48738814:54
openstackgerritIfat Afek proposed openstack/vitrage master: DO NOT MERGE - Disable swift services in Vitrage devstack  https://review.openstack.org/48731115:22
openstackgerritIfat Afek proposed openstack/vitrage master: Doc Migration: move the developer guide documents under the "contributor" folder  https://review.openstack.org/48692716:05
*** ifat_afek has quit IRC16:55
openstackgerritMatthew Thode proposed openstack/vitrage master: don't merge this  https://review.openstack.org/48756719:25
*** aasmith has quit IRC20:34
*** efoley has quit IRC21:24

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