Affinity and anti-affinity rules for VNF deployment

Change-Id: Ibb151d860f362ae70129777946c4586b5e45e56f
Signed-off-by: garciadeblas <gerardo.garciadeblas@telefonica.com>

diff --git a/Release3/Affinity_and_anti-affinity_rules_for_VNF_deployment.md b/Release3/Affinity_and_anti-affinity_rules_for_VNF_deployment.md
new file mode 100644 (file)
index 0000000..1ad8038
--- /dev/null
+++ b/Release3/Affinity_and_anti-affinity_rules_for_VNF_deployment.md
@@ -0,0 +1,30 @@
+# Affinity and anti-affinity rules for VNF deployment #
+
+## Proposer ##
+- Gerardo Garcia (Telefonica)
+- Alfonso Tierno (Telefonica)
+- Francisco Javier Ramon (Telefonica)
+
+## Type ##
+**Feature**
+
+## Target MDG/TF ##
+SO, RO
+
+## Description ##
+OSM should provide means to specify that different VDUs of the same VNF should 
+be deployed in different availability zones of the same datacenter. This 
+behaviour is often required by VNFs that implement active-standby resiliency 
+strategies.
+
+Current OSM\92s IM might need to be extended to support this feature.
+
+## Demo or definition of done ##
+- Add a datacenter to OSM specifying more than one availability zone.
+- Add a second datacenter with only one zone.
+- Onboard a VNF with 2 VDUs, with a VNFD that mandates that these VDUs must be 
+deployed in different availability zones.
+- Onboard an NS which includes the VNF above.
+- Instantiate the NS in the datacenter with 2 availability zones and check that 
+the VDUs are deployed as expected.
+- Instantiate the NS in the datacenter with one zone and check that it fails.
\ No newline at end of file