Changing sdc directory to unzipped_sdc_csar
[integration/csit.git] / plans / so / integration-etsi-testing / config / distribution-test-unzipped / unzipped_sdc_csar / v1 / catalog / services / Manualdistributiontestservice / 1.0 / resourceInstances / manualdistributiontestvnf0 / artifacts / relationships.yml
1 #
2 # Licensed under the Apache License, Version 2.0 (the "License");
3 # you may not use this file except in compliance with the License.
4 # You may obtain a copy of the License at
5 #
6 #      http://www.apache.org/licenses/LICENSE-2.0
7 #
8 # Unless required by applicable law or agreed to in writing, software
9 # distributed under the License is distributed on an "AS IS" BASIS,
10 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
11 # See the License for the specific language governing permissions and
12 # limitations under the License.
13 #
14 tosca_definitions_version: tosca_simple_yaml_1_1
15 imports:
16 - capabilities.yml
17 - data.yml
18 - interfaces.yml
19 relationship_types:
20   tosca.relationships.Root:
21     description: This is the default (root) TOSCA Relationship Type definition that all other TOSCA Relationship Types derive from.
22     attributes:
23       tosca_id:
24         description: A unique identifier of the realized instance of a Relationship Template that derives from any TOSCA normative type.
25         type: string
26       tosca_name:
27         description: This attribute reflects the name of the Relationship Template as defined in the TOSCA service template. This name is not unique to the realized instance model of corresponding deployed application as each template in the model can result in one or more instances (e.g., scaled) when orchestrated to a provider environment.
28         type: string
29       state:
30         description: The state of the relationship instance.
31         type: string
32         default: initial
33     interfaces:
34       Configure:
35         type: tosca.interfaces.relationship.Configure
36   tosca.relationships.ConnectsTo:
37     derived_from: tosca.relationships.Root
38     description: This type represents a network connection relationship between two nodes.
39     valid_target_types:
40     - tosca.capabilities.Endpoint
41     properties:
42       credential:
43         type: tosca.datatypes.Credential
44         required: false
45   tosca.relationships.RoutesTo:
46     derived_from: tosca.relationships.ConnectsTo
47     description: This type represents an intentional network routing between two Endpoints in different networks.
48     valid_target_types:
49     - tosca.capabilities.Endpoint
50   tosca.relationships.AttachesTo:
51     derived_from: tosca.relationships.Root
52     description: This type represents an attachment relationship between two nodes. For example, an AttachesTo relationship type would be used for attaching a storage node to a Compute node.
53     valid_target_types:
54     - tosca.capabilities.Attachment
55     properties:
56       location:
57         description: 'The relative location (e.g., path on the file system), which
58           provides the root location to address an attached node. e.g., a mount point
59           / path such as ''/usr/data''. Note: The user must provide it and it cannot
60           be "root".'
61         type: string
62         constraints:
63         - min_length: 1
64       device:
65         description: The logical device name which for the attached device (which is represented by the target node in the model). e.g., '/dev/hda1'.
66         type: string
67         required: false
68     attributes:
69       device:
70         description: 'The logical name of the device as exposed to the instance. Note:
71           A runtime property that gets set when the model gets instantiated by the
72           orchestrator.'
73         type: string
74   tosca.relationships.HostedOn:
75     derived_from: tosca.relationships.Root
76     description: This type represents a hosting relationship between two nodes.
77     valid_target_types:
78     - tosca.capabilities.Container
79   tosca.relationships.DependsOn:
80     derived_from: tosca.relationships.Root
81     description: This type represents a general dependency relationship between two nodes.
82     valid_target_types:
83     - tosca.capabilities.Node
84   tosca.relationships.network.LinksTo:
85     derived_from: tosca.relationships.DependsOn
86     description: This relationship type represents an association relationship between Port and Network node types.
87     valid_target_types:
88     - tosca.capabilities.network.Linkable
89   tosca.relationships.network.BindsTo:
90     derived_from: tosca.relationships.DependsOn
91     description: This type represents a network association relationship between Port and Compute node types.
92     valid_target_types:
93     - tosca.capabilities.network.Bindable
94   org.openecomp.relationships.AttachesTo:
95     derived_from: tosca.relationships.AttachesTo
96     description: This type represents an attachment relationship
97     properties:
98       location:
99         description: The relative location (e.g., path on the file system), which provides the root location to address an attached node.
100         type: string
101         status: SUPPORTED
102         required: false
103   org.openecomp.relationships.VolumeAttachesTo:
104     derived_from: org.openecomp.relationships.AttachesTo
105     description: This type represents an attachment relationship for associating volume
106     properties:
107       volume_id:
108         description: The ID of the volume to be attached
109         type: string
110         status: SUPPORTED
111         required: true
112       instance_uuid:
113         description: The ID of the server to which the volume attaches
114         type: string
115         status: SUPPORTED
116         required: true
117     attributes:
118       show:
119         description: Detailed information about resource
120         type: string
121         status: SUPPORTED
122   org.openecomp.relationships.ForwardsTo:
123     derived_from: tosca.relationships.Root
124     valid_target_types:
125     - org.openecomp.capabilities.Forwarder
126   org.openecomp.relationships.AssignsTo:
127     derived_from: tosca.relationships.Root
128   org.openecomp.relationships.RoutesTo:
129     derived_from: tosca.relationships.RoutesTo
130     description: This type represents an intentional network routing between internal and external network
131   tosca.relationships.nfv.VirtualBindsTo:
132     derived_from: tosca.relationships.DependsOn
133     description: Represents an association relationship between Vdu.Compute and VduCp node types
134     valid_target_types:
135     - tosca.capabilities.nfv.VirtualBindable
136   tosca.relationships.nfv.VirtualLinksTo:
137     derived_from: tosca.relationships.DependsOn
138     description: Represents an association relationship between the VduCp and VnfVirtualLink node types
139     valid_target_types:
140     - tosca.capabilities.nfv.VirtualLinkable
141   tosca.relationships.nfv.AttachesTo:
142     derived_from: tosca.relationships.Root
143     description: Represents an association relationship between the Vdu.Compute and one of the node types, Vdu.VirtualBlockStorage, Vdu.VirtualObjectStorage or Vdu.VirtualFileStorage
144     valid_target_types:
145     - tosca.capabilities.nfv.VirtualStorage
146   tosca.relationships.nfv.Vdu.AttachedTo:
147     derived_from: tosca.relationships.DependsOn
148     valid_target_types:
149     - tosca.capabilities.nfv.VirtualStorage