Vitrage Resource Processor

Registered by Alexey Weyl

When Vitrage initializes we need to create the entity graph on which the Vitrage will run it’s algorithms (sub graph matching, BFS, DFS etc.) and perform the actions (RCA, deduced alarms etc.). After the initialization of the graph, the resources changes are being processed and pushed to the entity graph.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Essential
Drafter:
Alexey Weyl
Direction:
Needs approval
Assignee:
Alexey Weyl
Definition:
Approved
Series goal:
Accepted for mitaka
Implementation:
Implemented
Milestone target:
milestone icon mitaka-2
Started by
Alexey Weyl
Completed by
Alexey Weyl

Related branches

Sprints

Whiteboard

https://review.openstack.org/#/c/243424/

Gerrit topic: https://review.openstack.org/#q,topic:bp/vitrage-resource-processor,n,z

Addressed by: https://review.openstack.org/254062
    vitrage processor implementation Implements: blueprint vitrage-resource-processor

Addressed by: https://review.openstack.org/261821
    vitrage processor code review and documentation Implements: blueprint vitrage-resource-processor

Addressed by: https://review.openstack.org/262015
    bug fixes in nova transformer

Addressed by: https://review.openstack.org/262166
    Integration of Synchronizer + Processor + Transformer Implements: blueprint vitrage-resource-processor

Addressed by: https://review.openstack.org/262391
    Integration of Synchronizer + Processor + Transformer Implements: blueprint vitrage-resource-processor

Addressed by: https://review.openstack.org/262538
    processor code review comments Implements: blueprint vitrage-resource-processor

Addressed by: https://review.openstack.org/262556
    processor code review comments Implements: blueprint vitrage-resource-processor

Addressed by: https://review.openstack.org/262702
    code changes Implements: blueprint vitrage-resource-processor

Addressed by: https://review.openstack.org/263009
    1. code integration of Synchronizer + Processor + transformer 2. Create Entity graph service + Synchronizer service

Addressed by: https://review.openstack.org/263024
    1. code integration of Synchronizer + Processor + transformer 2. Create Entity graph service + Synchronizer service

Addressed by: https://review.openstack.org/263209
    Create ServiceLauncher that launches the services: 1. Entity graph 2. api_handler 3. synchronizer 4. Graph consistency

Addressed by: https://review.openstack.org/264147
    Adding new actions for processor

Addressed by: https://review.openstack.org/264153
    Adding new actions for processor

Addressed by: https://review.openstack.org/264746
    vitrage-graph service integration

Addressed by: https://review.openstack.org/266422
    vitrage-graph integration 1. with host transformer 2. with zone transformer 3. create graph test Implements: blueprint vitrage-resource-processor

Addressed by: https://review.openstack.org/269113
    bug fixes

Addressed by: https://review.openstack.org/270085
    basic rpc api

Addressed by: https://review.openstack.org/280794
    infrastructure changes for synchronizers and consistency

Addressed by: https://review.openstack.org/283058
    Change api mocks + rename 'node' to 'openstack.cluster'

Addressed by: https://review.openstack.org/283113
    bug fix for LOG

Addressed by: https://review.openstack.org/283970
    Static physical configuration documentation

Addressed by: https://review.openstack.org/284029
    Static physical configuration changes

Addressed by: https://review.openstack.org/289903
    rpc api handler configuration

Addressed by: https://review.openstack.org/290024
    rpc api service fix

Addressed by: https://review.openstack.org/292104
    rpc api config fix

Addressed by: https://review.openstack.org/292379
    rpc api context

Addressed by: https://review.openstack.org/293916
    small fixes

Addressed by: https://review.openstack.org/302159
    Show only non deprecated elements

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.