Action Providers

Registered by Dmitri Zimine on 2014-12-29

Currently, actions have to be registered in Mistral's SQL DB and has to have a corresponding class module installed as entry_points (regardless whether the class is a stub that serves as proxy or a class that does actual work). ActionProvider is an abstraction that allows a trusted third party system to extend Mistral with its own action catalog and action executor without the heavy lifting in keeping the action table in sync and in creating action generators and maintaining the class stubs. The high level architecture is attached for reference. The ActionProvider allows for action executions from specific providers to be isolated either for performance and security reasons. The architecture also allows ActionProvider to be independently scale up/down based on demand. With ActionProvider, Mistral can delegate the action catalog and action execution to the providers and focus primarily on managing the workbooks, conducting the overall workflow executions, and tracking execution state.

TODO: add link to the spec and more details

Blueprint information

Status:
Started
Approver:
Renat Akhmerov
Priority:
Medium
Drafter:
Dmitri Zimine
Direction:
Approved
Assignee:
Renat Akhmerov
Definition:
Approved
Series goal:
Accepted for victoria
Implementation:
Started
Milestone target:
milestone icon victoria-1
Started by
Renat Akhmerov on 2020-04-14

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/mistral-action-providers,n,z

Addressed by: https://review.openstack.org/570204
    [WIP] Initial API discussion for Action Providers

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.