Affinity and antiaffinity implementation. 71/2071/8
authormirabal <leonardo.mirabal@altran.com>
Thu, 27 Jul 2017 10:21:22 +0000 (12:21 +0200)
committermirabal <leonardo.mirabal@altran.com>
Mon, 28 Aug 2017 16:18:52 +0000 (18:18 +0200)
commit2935631c49a315fb078d05380569f7e1ca21fcde
treeeca84b45800f10f7a3a5846e45315c14d05c13ec
parent994a29db7a227e56a0575b72e8107df5505a4e57
Affinity and antiaffinity implementation.

- RO descriptor now support "availability_zone" tag in the VNFC descriptor.
- RO database extend table vms table to include availability_zone.
- In case a VNF requires more  zones than available in the datacenter, an error message of instantiation failure will be issued and the usual rollback procedure will  start.
- In case a VDU does not include availability tag, it will be treated as normal, following the default scheduling policy in the VIM.

Change-Id: I335a0db6fa232953f655a598351dd7e7bbb97785
Signed-off-by: mirabal <leonardo.mirabal@altran.com>
database_utils/migrate_mano_db.sh
openmanod
osm_ro/nfvo.py
osm_ro/nfvo_db.py
osm_ro/openmano_schemas.py
osm_ro/vimconn.py
osm_ro/vimconn_openstack.py
test/RO_tests/afiinity_vnf/scenario_simple_2_vnf_afinnity.yaml [new file with mode: 0644]
test/RO_tests/afiinity_vnf/vnfd_linux_2_vnfc_affinity.yaml [new file with mode: 0644]