Joshua Harlow e6a04193e7 Avoid trying to copy tasks results when cloning/copying ...

It is not always safe to copy task results so instad of
trying to copy.copy them just retain the existing results
in the clone (and avoid copying any users results if
they exist).

This appeared to be causing sqlalchemy weak references to
get garbage collected prematurely in cinder.

Fixes bug 1452978

Change-Id: I75e4ad0e9eb50284ff09179565b6d146a8da3d92

2015-05-07 21:21:38 -07:00

..

backends

Speed up memory backend via a path -> node reverse mapping

2015-05-05 23:17:03 -07:00

__init__.py

Removed copyright from empty files

2014-02-22 17:16:29 +08:00

base.py

lazy loading for logbooks and flowdetails

2015-03-11 15:57:07 -05:00

logbook.py

Avoid trying to copy tasks results when cloning/copying

2015-05-07 21:21:38 -07:00

path_based.py

By default use a in memory backend (when none is provided)

2015-03-23 05:33:39 +00:00