Fix bug 1731: backwards compatibility of relations
Change-Id: Iaf7059f7d6555a34216f1b31acd896806df83c61
Signed-off-by: David Garcia <david.garcia@canonical.com>
diff --git a/models/augments/common-augments.yang b/models/augments/common-augments.yang
index c365424..0467bc2 100644
--- a/models/augments/common-augments.yang
+++ b/models/augments/common-augments.yang
@@ -200,6 +200,31 @@
"Execution environment that uses the service provided by the provider";
uses relations-ee;
}
+ list entities {
+ description
+ "DEPRECATION NOTICE: use provider and requirer instead.
+ List of two elements to be related.
+ Elements to be related are identified by a pair (id, endpoint).
+ The relation will relate (id1, endpoint1) to (id2, endpoint2).";
+ key "id";
+
+ leaf id {
+ description
+ "A string, reference to the element id in the descriptor.
+ It could be a vnfd-id or a vdu-id in a VNFD,
+ or a nsd-id or member-vnf-index in a NSD.";
+ type string;
+ }
+
+ leaf endpoint {
+ description
+ "Endpoint name defining the relation.";
+ type string;
+ }
+ }
+ must 'not(entities) or (not(provider) and not(requirer))' {
+ error-message 'Cannot set both "entities" and "provider/requirer" fields.';
+ }
}
}