Bug 1082498

Summary: [RFE][vdsm] Provide a new tasks infrastructure without Master File-System persistency
Product: Red Hat Enterprise Virtualization Manager Reporter: Federico Simoncelli <fsimonce>
Component: vdsmAssignee: Federico Simoncelli <fsimonce>
Status: CLOSED DEFERRED QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: bazulay, gklein, iheim, lpeer, mkalinin, oourfali, rhodain, ybronhei, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: sherold: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-04 09:35:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1080379, 1082502, 1151374    

Description Federico Simoncelli 2014-03-31 07:59:59 UTC 
Description of problem:
Provide a new tasks infrastructure that is not relying on the master file-system persistency.
Comment 1 Federico Simoncelli 2014-04-15 21:40:32 UTC 
It is possible to reuse the current task infrastructure disabling the persistency:

task: support scheduleJob without persistency
http://gerrit.ovirt.org/26771

And allow engine to pass a task uuid using a special "TaskID" http header in the requests:

task: support task id in client request
http://gerrit.ovirt.org/26809

This allows a behavior that is very similar to the one we'll jave with JSON-RPC (every requests can carry an id).

At the moment it seems that these two patches (and the few other they're based on) would provide enough functionalities for bug 1082502 ([RFE][vdsm] Provide new Storage API without Master File-System persistency)