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>
- local_storage:
node: MM_BlockStorage
relationship: Storage_attachesto
- - high_availability: MM_Passive
artifacts:
#the VM image of MM
vm_image: mm.image
min_instances: 1
max_instances: 126
default_instances: 1
- requirements:
- - high_availability: CM_Passive
artifacts:
#the VM image of CM
vm_image: cm.image
- local_storage:
node: MM_BlockStorage
relationship: Storage_attachesto
- - high_availability: MM_Passive
artifacts:
#the VM image of MM
vm_image: mm.image
min_instances: 1
max_instances: 12
default_instances: 1
- requirements:
- - high_availability: CM_Passive
artifacts:
#the VM image of CM
vm_image: cm.image