[openstack-dev] 答复: [tripleo] Blueprints for Rocky

Hi all, I proposed a BP about the integration with Vitrage: https://blueprints.launchpad.net/tripleo/+spec/tripleo-vitrage-integration And I posted a spec patch to the gerrit: https://review.openstack.org/#/c/552425/ Please help to review, any comments are welcome. Thanks~ BR,

[openstack-dev] 答复: [tripleo][vitrage] Draft schedule for PTG

Hi EmilienMacchi, I added a topic about 'support Vitrage(Root Cause Analysis project) service' in the etherpad for PTG. Can you please help to schedule a time slot? Maybe after the topic of 'Upgrades and Updates', half an hour is enough. We want to support the feature in the TripleO

[openstack-dev] [vitrage] send notification when update vertex

Hi dan, I use Vitrage master branch to test 'host_down' scenario.. When scenario_evaluator match the ''host_down_alarm_on_host" scenario and Do 'mark_down' action, Process update the vertex in entity graph and then should send the notification. But currently, it didn't send the

[openstack-dev] 答复: RE: [vitrage] some error in Aodh datasource

Hi Idan, Sorry, maybe it's the issue of my OpenStack env. I'll check it later. Thanks~ BR, dwj 原始邮件 发件人：董文娟00101742 收件人： ; 抄送人： ; 日 期 ：2017年10月30日 08:59 主 题 ：答复: RE: [openstack-dev][vitrage] some error in Aodh

[openstack-dev] [vitrage] some error in Aodh datasource

Hi Idan Kinory, I deploy Vitrage with devstack using master branch. Currently I found a error in Aodh datasource when I change the Aodh alarm state(alarm_state_transition notification). The error log is as follows: Oct 27 07:30:50 dwj-vitrage vitrage-collector[9880]: 2017-10-27

[openstack-dev] [Vitrage] Integration with doctor

Hi, For the integration Vitrage with doctor, I have some issues which need to be confirmed~ :) 1. Notification strategies: conservative (nova->Aodh) @Ifat In the host_down_scenarios.yaml[1], we only set the host state as error. But in doctor current use case, we need to call nova

Re: [openstack-dev] Suspected SPAM - Re: [vitrage] about  "is_admin" in ctx

Hi Alexey, Currently we use 'is_admin' as 'is_admin_project'[1], right? I think the 'is_admin_project' represent the tenant , not be related to user. So why 'is_admin_project' alaways return 'True' with all of the user and tenants is the issue. What about a user which is not ＇admin' but have

Re: [openstack-dev] [vitrage] about  "is_admin" in ctx

Hi Alexey, Sorry for reply with a delay. I just saw this mail. It's OK, not a emergency issue. :) BR, dwj Original Mail Sender: ＜alexey.w...@nokia.com＞ To: ＜openstack-dev@lists.openstack.org＞ Date: 2017/04/25 21:09 Subject: Re: [openstack-dev] [vitrage] about

[openstack-dev] [vitrage] about  "is_admin" in ctx

Hi all, I'm a little confused about the "is_amdin" in ctx. From the hook(https://github.com/openstack/vitrage/blob/master/vitrage/api/hooks.py#L73), "is_admin" means admin user,. But we define the macro as "admin project"(

Re: [openstack-dev] [ALU] Re: [vitrage] vitrage Resource API

Hi Alexey, Thanks for letting me know. I'll continue to implement the API if there is nobody works on it. :) BR, dwj Original Mail Sender: ＜alexey.w...@nokia.com＞ To: ＜openstack-dev@lists.openstack.org＞ ＜trinath.soman...@nxp.com＞ Date: 2017/03/21 14:17 Subject: Re:

Re: [openstack-dev] [vitrage] vitrage Resource API

No, in the implemention of these APIs． see https://github.com/openstack/vitrage/blob/master/vitrage/api/controllers/v1/resource.py#L47 Original Mail Sender: ＜trinath.soman...@nxp.com＞ To: ＜openstack-dev@lists.openstack.org＞ ＜openstack-dev@lists.openstack.org＞ Date:

[openstack-dev] [vitrage] vitrage Resource API

Hi All, I noticed that the APIs of `resource list` and `resource show` were mocked. Is there any backgroud for the mock or the API is not necessary? BR, dwj__ OpenStack Development Mailing List (not for usage

[openstack-dev] 答复: RE: Re: [ALU] [Vitrage] vitrage tempest job config

Hi Alexey, Sorry, I saw the configuration. Need to click the 'raw' button in github to see the whole layout.yaml file. Sorry to trouble you again and again. :-) BR, dwj 原始邮件 发件人：Weyl,Alexey(Nokia-IL) 收件人：董文娟00101742 抄送人：＜openstack-dev@lists.openstack.org＞ 日 期

[openstack-dev] 答复: RE: Re: [ALU] [Vitrage] vitrage tempest job config

Hi, I know. Why only python-vitrageclient and puppet-vitrage register in the zuul/layout.yaml? They also register in the jeknins/jobs/projects.yaml. And other vitrage projects only register in the jeknins/jobs/projects.yaml. I'm confused if i want to add a new jenkins job, which file should

[openstack-dev] 答复: Re: [ALU] [Vitrage] vitrage tempest job config

Hi Alexey, As far as i know, every project needs to register in the zuul/layout.yaml[1], so zuul can submit the job to jenkins via gearman. So the jenkins knows which jobs need to run and then run the job which defined in the jenkins/jobs/XXX.yaml. Did i missing something? Or the job

[openstack-dev] [Vitrage] vitrage tempest job config

Hi all, I didn't find any vitrage project jenkins jobs registered in zuul/layout.yaml. Where does all the jobs configed?Thanks~ BR, dwj__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: