Remove the cyclic dependencies in vRNC definition 63/19163/1
authorshangxdy <shang.xiaodong@zte.com.cn>
Mon, 22 Aug 2016 07:34:10 +0000 (15:34 +0800)
committershangxdy <shang.xiaodong@zte.com.cn>
Mon, 22 Aug 2016 07:34:10 +0000 (15:34 +0800)
commit1a0bd86750c00b06b2161426c5154dee557c3e70
treec7b1d7bf0d3444a59c8ea5e3cc5b3a0f8a9d53cc
parent6fecb729f550f4f543739375df8148ab9de38668
Remove the cyclic dependencies in vRNC definition

Current the high_availability definition in vRNC about active MM/CM VDUs
and passive MM/CM VDUs is cyclic dependencies, and the consequence is
deployment of  vRNC may fall into a infinite loop.
The correct definition is passive VDU depend on the active VDU, but the
active VDU doesn't depend on the passive VDU.

JIRA:PARSER-95

Change-Id: I3f2fb8c0ce959878b12d7da49e2dc81596b4b528
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
docs/parser_docs/tosca2heat/examples/Simple_RNC.yaml
tosca2heat/tosca-parser/toscaparser/extensions/nfv/tests/data/vRNC/Definitions/vRNC.yaml