congress

asynchronous action execution

Bug #1670529 reported by Eric K on 2017-03-07

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	congress	Fix Released	Undecided	Masahito Muroi	congress pike-1

Bug Description

trigger action executions asynchronously to avoid long delays in triggering new action, while waiting for other actions to complete.

One potential implementation is to modify ExecutionDriver so that each action execution spawns a new greenthread.

Tags:

Eric K (ekcs) on 2017-03-07

tags:

added: pike-goal

Revision history for this message

Eric K (ekcs) wrote on 2017-03-07:

Targeting early in the dev cycle because it's a relatively simple change that may be unexpected consequences we'd like to have plenty of time to discover.

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-04-19: Fix proposed to congress (master)

Fix proposed to branch: master
Review: https://review.openstack.org/458038

Changed in congress:
status:	New → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-05-19: Fix merged to congress (master)

Reviewed: https://review.openstack.org/458038
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=02ff94adb9bc433549f5b3483f36b2ede19b3614
Submitter: Jenkins
Branch: master

commit 02ff94adb9bc433549f5b3483f36b2ede19b3614
Author: Masahito Muroi <email address hidden>
Date: Tue Apr 18 04:22:24 2017 +0900

Parallel execution in DataSource Driver

    Datasource driver calls datasource's API serially when Policy Engine sends
    execution requests. It could take long time number of execution targets is
    a lots.

This patch changes datasource driver calls datasource's API in parallel.

Closes-Bug: #1670529
Change-Id: I065bd625004401a1bb78c6d56d929bdaf76d37f0