Bug 1284903 - [RFE] Command Infrastructure - support flows
Summary: [RFE] Command Infrastructure - support flows
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.0.0-beta
: 4.0.0
Assignee: Moti Asayag
QA Contact: Moti Asayag
URL:
Whiteboard:
Depends On: 1302293
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-24 12:35 UTC by Oved Ourfali
Modified: 2016-08-11 08:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-11 08:44:58 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.0.0+
mgoldboi: planning_ack+
oourfali: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 41699 0 None None None 2016-05-04 07:58:51 UTC
oVirt gerrit 52961 0 master NEW engine: Support events in CoCo 2016-05-09 21:44:38 UTC

Description Oved Ourfali 2015-11-24 12:35:29 UTC 
Command’s Flow should allow the developer to introduce a sequence of actions in the system (Command, task, event) which will be executed conditionally (or not) depending on the result of the former action in that flow.
Comment 1 Oved Ourfali 2016-04-07 12:50:02 UTC 
This is an ongoing effort, partially implemented in 4.0.
Putting devel-ack.
Comment 2 Sandro Bonazzola 2016-05-02 10:03:22 UTC 
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Comment 3 Pavel Stehlik 2016-05-05 11:00:25 UTC 
QE - CodeChange, just sanity (various storage operations will work).
Comment 4 Gil Klein 2016-08-11 08:44:58 UTC 
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA
Note You need to log in before you can comment on or make changes to this bug.