[CORD-3100] Upgrading TOSCA to new ONOS Service format
Change-Id: I0863881a305a78fe918d3558f4475a90c7d3b966
diff --git a/xos-services/vtn-service/templates/_tosca.tpl b/xos-services/vtn-service/templates/_tosca.tpl
index 49f0ba8..32f765d 100644
--- a/xos-services/vtn-service/templates/_tosca.tpl
+++ b/xos-services/vtn-service/templates/_tosca.tpl
@@ -18,7 +18,10 @@
tosca_definitions_version: tosca_simple_yaml_1_0
imports:
- - custom_types/vtnservice.yaml
+ - custom_types/servicedependency.yaml
+ - custom_types/serviceinstance.yaml
+ - custom_types/serviceinstanceattribute.yaml
+ - custom_types/vtnservice.yaml
description: Configures the VTN ONOS service
@@ -43,4 +46,23 @@
vtnAPIVersion: 2
controllerPort: onos-cord-openflow:6653
resync: false
+
+ vtn_service_instance:
+ type: tosca.nodes.ServiceInstance
+ properties:
+ name: VTN config
+ requirements:
+ - owner:
+ node: service#vtn
+ relationship: tosca.relationships.BelongsToOne
+
+ vtn_config:
+ type: tosca.nodes.ServiceInstanceAttribute
+ properties:
+ name: autogenerate
+ value: vtn-network-cfg
+ requirements:
+ - service_instance:
+ node: vtn_service_instance
+ relationship: tosca.relationships.BelongsToOne
{{- end -}}