Fix property inconsistency between tosca and xproto
Change-Id: I33f2838670cf92f91dfbf418df830a75802b5dc7
diff --git a/xos/tosca/custom_types/vmme.m4 b/xos/tosca/custom_types/vmme.m4
index 3b8133e..924445d 100644
--- a/xos/tosca/custom_types/vmme.m4
+++ b/xos/tosca/custom_types/vmme.m4
@@ -15,4 +15,16 @@
properties:
xos_base_props
xos_base_service_props
-
+ service_message:
+ type: string
+ required: true
+
+ tosca.nodes.MMETenant:
+ derived_from: tosca.nodes.Root
+ description: >
+ VMME Tenant
+ properties:
+ xos_base_tenant_props
+ tenant_message:
+ type: string
+ required: true
\ No newline at end of file
diff --git a/xos/tosca/custom_types/vmme.yaml b/xos/tosca/custom_types/vmme.yaml
index 766a1cb..be5ec1f 100644
--- a/xos/tosca/custom_types/vmme.yaml
+++ b/xos/tosca/custom_types/vmme.yaml
@@ -78,4 +78,23 @@
type: string
required: false
description: Version number of Service.
-
+ service_message:
+ type: string
+ required: true
+
+ tosca.nodes.MMETenant:
+ derived_from: tosca.nodes.Root
+ description: >
+ VMME Tenant
+ properties:
+ kind:
+ type: string
+ default: generic
+ description: Kind of tenant
+ service_specific_id:
+ type: string
+ required: false
+ description: Service specific ID opaque to XOS but meaningful to service
+ tenant_message:
+ type: string
+ required: true
\ No newline at end of file