[engine] Destruction dependencies broken by object model merge process

[Nikolay Starodubtsev]

As far as we merged https://github.com/openstack/murano/commit/01b3ac3161903d16e5b1e4836d768ce0afff6645 destruction dependencies can't work with the subscriber object from ObjectsCopy, which can establish dependency in init method. We need to persist destruction dependencies in the target objects and properly deserialize it from object model.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Nikolay Starodubtsev (<email address hidden>) on branch: master
Review: https://review.openstack.org/362987

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/366563
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=2b57eb3fca54bccb254e04594349f99d29752a1e
Submitter: Jenkins
Branch: master

commit 2b57eb3fca54bccb254e04594349f99d29752a1e
Author: Stan Lagun <email address hidden>
Date: Wed Sep 7 00:37:42 2016 -0700

    Serialization of destruction dependencies

    If the object was deleted through the API between deployments
    the only way for those who used to subscribe to its destruction
    to be notifyed upon next deployment is to persist destruction
    dependencies to the object model.

    This commit adds such serialization and deserialization.

    Also move GC class from engine to dsl

    Targets-blueprint: dependency-driven-resource-deallocation
    Closes-Bug: #1619248
    Change-Id: Icd2e882be5770244aa1ecafe265aff1439ebec9e

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/murano 3.0.0.0rc1 release candidate.