Mistral

Delivery model for particular task (at-most-once/at-least-once)

Registered by Renat Akhmerov

We need to be able to delivery model (at-most-once/at-least-once) for a particular task. It may be useful for advanced users who know all possible consequences. Based on knowledge of whether a task is idempotent or not user could make corresponding decision.

Blueprint information

Status:
Complete
Approver:
Renat Akhmerov
Priority:
Medium
Drafter:
Renat Akhmerov
Direction:
Approved
Assignee:
Dawid Deja
Definition:
Approved
Series goal:
Accepted for newton
Implementation:
Implemented
Milestone target:
milestone icon newton-3
Started by
Renat Akhmerov
Completed by
Renat Akhmerov

Related branches

Sprints

Whiteboard

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

Addressed by: https://review.openstack.org/336548
    Enable 'at-least-once' and 'at-most-once' delivery modes in RPC layer

Addressed by: https://review.openstack.org/339113
    Enable 'at-least-once' and 'at-most-once' delivery modes in Engine

Addressed by: https://review.openstack.org/340450
    Enable end user to use both delivery modes

Gerrit topic: https://review.openstack.org/#q,topic:bp/mistral-task-delivery-model,n,z

Addressed by: https://review.openstack.org/343788
    Create MistralContext from rpc context in kombu engine

Addressed by: https://review.openstack.org/343789
    Add param 'safe-rerun' to task

Addressed by: https://review.openstack.org/343790
    Pass 'safe-rerun' param to RPC layer

Addressed by: https://review.openstack.org/343791
    Executor fails actions if they are redelivered

Addressed by: https://review.openstack.org/349449
    Update docs and add release not for safe-rerun flag

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

Nearby

This blueprint contains Public information 
Everyone can see this information.