Re: [openstack-dev] [vitrage] how to use mock driver

n only. It is never compiled into a `re` object. The actual values are generated in `static_info_parsers` from the `mapping`. The regular expression is neither used as a value template nor for value validation. Is that right? On Mon, Dec 12, 2016 at 8:47 PM Rosensweig, Elisha (Nokia - IL) <elish

Re: [openstack-dev] [vitrage] how to use mock driver

Hi, · In Vitrage Datasources, we can have a different input format for snapshots and updates. Thus, we need a different JSON file for each. · Also, as part of the Mock feature, we need to support (for each resource) things that will be static, such as it’s name, and things

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

uration [1] and the test currently fails. Not sure we need to update mock_sync or not. [1] https://review.openstack.org/#/c/362525/1/vitrage/tests/resources/static_datasources/switch_to_host_datasource.yaml On Tue, Aug 30, 2016 at 2:53 PM Rosensweig, Elisha (Nokia - IL) <elisha.rosensw

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

What is the problem you are running into with mock_sync? Elisha From: Yujun Zhang [mailto:zhangyujun+...@gmail.com] Sent: Tuesday, August 30, 2016 5:09 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [vitrage] relationship_type in

Re: [openstack-dev] [vitrage] reference a type of alarm in template

Hi, The "type" means where it was generated - aodh, vitrage, nagios... I think you are looking for"name", a field that describes the actual problem. We should add that to our documentation to clarify. Sent from Nine From: Yujun Zhang

Re: [openstack-dev] [vitrage] scenario evaluator not enabled by default

This is on purpose. When Vitrage is started, it first runs a "consistency" round where it gets all the resources from its datasources and inserts them into the entity graph. Once this initial phase is over, the evaluator is run over all the entity graph to check for meaningful patterns based

Re: [openstack-dev] [openstack-infra] [vitrage] branch marking policy

ited by Gerrit)" Is there a problem to retroactively mark liberty branches? Elisha From: Rosensweig, Elisha (Nokia - IL) Sent: Thursday, June 30, 2016 3:57 PM To: OpenStack Development Mailing List (not for usage questions) Subject: RE: [openstack-dev] [openstack-infra] [vitrage] branch marking poli

Re: [openstack-dev] [openstack-infra] [vitrage] branch marking policy

policy Hey Elisha, Have you looked at http://docs.openstack.org/infra/manual/drivers.html ? Cheers, Josh On Thu, Jun 30, 2016 at 9:16 PM, Rosensweig, Elisha (Nokia - IL) <elisha.rosensw...@nokia.com<mailto:elisha.rosensw...@nokia.com>> wrote: Hi, We've prepared a (local) branch

[openstack-dev] [openstack-infra] [vitrage] branch marking policy

Hi, We've prepared a (local) branch with Vitrage that is *Liberty-compatible*, and would like to mark (tag?) the branch. What is the standard way to do this? Thanks, Elisha Rosensweig, Ph.D. R Director CloudBand, Nokia T: +972 9793 3159

[openstack-dev] [telemetry] [ceilometer] [kilo] trouble reloading ceilometer pipeline

Hi All, I'm running with Kilo and I want to make changes to my ceilometer pipeline file (changing the rate of sampling, in this case). What I did was: (1) make the changes, (2) restart the ceilometer agents on the compute [service openstack-ceilometer-compute restart] (3) restart the nova

[openstack-dev] [vitrage] Design discussion for overlapping templates support & new section in Vitrage wiki

Hi all, I've added a new section in the Vitrage Wiki page where links to active design discussions will take place. You can find it here: https://wiki.openstack.org/wiki/Vitrage#Open_Design_Discussions Once a design has been finalized, it will be moved to the "Design Documents" section. The

Re: [openstack-dev] [Vitrage] questions about "relationships"

l be a big challenge per my understanding. :) Thanks again, Tony From: EXT Rosensweig, Elisha (Nokia - IL) [mailto:elisha.rosensw...@nokia.com] Sent: Wednesday, April 20, 2016 12:26 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Vitrage] quest

[openstack-dev] [keystone] Problem with WSGI on keystone

Hi All, Recently, I've been having trouble running stack.sh from scratch. With the default configuration I've been using for a while, I get the following error in /opt/stack/logs/key.log: 2016-04-19 16:05:26.630 22047 DEBUG keystone.common.controller [req-3d384c1f-8b9a-4ff0-aa30-a4aad73963fb

Re: [openstack-dev] [Vitrage] questions about "relationships"

rrences of a template graph in the "global" graph("NXAlgorithm.sub_graph_matching"). 3. If so, which graph will be applied by the actions by ScenarioEvaluator? For example, will "AddCausalRelationship" add "causes" edge to the "global graph" o

[openstack-dev] [Vitrage] putting overlapping-templates-basic-support on the back-burner

Hi All, Since * the overlapping templates BP (https://blueprints.launchpad.net/vitrage/+spec/overlapping-templates-basic-support) is a large one, which deserves a lot of design and discussion * there is a lot of focus on stability and clarity for the summit I'll be putting working on this BP

[openstack-dev] [vitrage] Pushed specification of Vitrage templates, for supporting Root Cause Analysis (RCA) and additional features

Hi All, Please see the following specification for the Vitrage Templates: https://review.openstack.org/#/c/272033/1/doc/source/vitrage-template-format.rst Vitrage Templates are used to support the RCA capabilities of Vitrage, as well as additional features such as deduced alarms and states.