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
6 # http://www.apache.org/licenses/LICENSE-2.0
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.
15 tosca_definitions_version: tosca_simple_yaml_1_0
18 # filename: tosca/capabilities.yml
25 tosca.capabilities.Root:
26 description: This is the default (root) TOSCA Capability Type definition that all other TOSCA Capability Types derive from.
28 tosca.capabilities.Node:
29 derived_from: tosca.capabilities.Root
30 description: The Node capability indicates the base capabilities of a TOSCA Node Type.
32 tosca.capabilities.Container:
33 derived_from: tosca.capabilities.Root
34 description: The Container capability, when included on a Node Type or Template definition, indicates that the node can act as a container for (or a host for) one or more other declared Node Types.
37 description: Number of (actual or virtual) CPUs associated with the Compute node.
43 description: Specifies the operating frequency of CPU's core. This property expresses the expected frequency of one (1) CPU as provided by the property "num_cpus".
44 type: scalar-unit.frequency
47 - greater_or_equal: 0.1 GHz
49 description: Size of the local disk available to applications running on the Compute node (default unit is MB).
50 type: scalar-unit.size
53 - greater_or_equal: 0 MB
55 description: Size of memory available to applications running on the Compute node (default unit is MB).
56 type: scalar-unit.size
59 - greater_or_equal: 0 MB
61 tosca.capabilities.Endpoint:
62 derived_from: tosca.capabilities.Root
63 description: This is the default TOSCA type that should be used or extended to define a network endpoint capability. This includes the information to express a basic endpoint with a single port or a complex endpoint with multiple ports. By default the Endpoint is assumed to represent an address on a private network unless otherwise specified.
66 description: 'The name of the protocol (i.e., the protocol prefix) that the
67 endpoint accepts (any OSI Layer 4-7 protocols). Examples: http, https, ftp,
73 description: The optional port of the endpoint.
74 type: tosca.datatypes.network.PortDef
77 description: Requests for the endpoint to be secure and use credentials supplied on the ConnectsTo relationship.
82 description: The optional URL path of the endpoint's address if applicable for the protocol.
86 description: The optional name (or ID) of the network port this endpoint should be bound to.
90 description: 'The optional name (or ID) of the network this endpoint should
91 be bound to. network_name: PRIVATE | PUBLIC | <network_name> | <network_id>.'
96 description: The optional indicator of the direction of the connection.
106 description: The optional map of ports the Endpoint supports (if more than one).
109 type: tosca.datatypes.network.PortSpec
115 description: 'Note: This is the IP address as propagated up by the associated
116 node''s host (Compute) container.'
119 tosca.capabilities.Endpoint.Public:
120 derived_from: tosca.capabilities.Endpoint
122 This capability represents a public endpoint which is accessible to the general internet (and its public IP address ranges).
123 This public endpoint capability also can be used to create a floating (IP) address that the underlying network assigns from a pool allocated from the application's underlying public network. This floating address is managed by the underlying network such that can be routed an application's private address and remains reliable to internet clients.
131 tosca.capabilities.Endpoint.Admin:
132 derived_from: tosca.capabilities.Endpoint
133 description: This is the default TOSCA type that should be used or extended to define a specialized administrator endpoint capability.
136 description: Requests for the endpoint to be secure and use credentials supplied on the ConnectsTo relationship.
142 tosca.capabilities.Endpoint.Database:
143 derived_from: tosca.capabilities.Endpoint
144 description: This is the default TOSCA type that should be used or extended to define a specialized database endpoint capability.
146 tosca.capabilities.Attachment:
147 derived_from: tosca.capabilities.Root
148 description: This is the default TOSCA type that should be used or extended to define an attachment capability of a (logical) infrastructure device node (e.g., BlockStorage node).
150 tosca.capabilities.OperatingSystem:
151 derived_from: tosca.capabilities.Root
152 description: This is the default TOSCA type that should be used to express an Operating System capability for a node.
155 description: 'The Operating System (OS) architecture. Examples of valid values
156 include: x86_32, x86_64, etc.'
160 description: 'The Operating System (OS) type. Examples of valid values include:
161 linux, aix, mac, windows, etc.'
165 description: 'The Operating System (OS) distribution. Examples of valid values
166 for a "type" of "Linux" would include: debian, fedora, rhel and ubuntu.'
170 description: The Operating System version.
174 tosca.capabilities.Scalable:
175 derived_from: tosca.capabilities.Root
176 description: This is the default TOSCA type that should be used to express a scalability capability for a node.
179 description: This property is used to indicate the minimum number of instances that should be created for the associated TOSCA Node Template by a TOSCA orchestrator.
183 description: This property is used to indicate the maximum number of instances that should be created for the associated TOSCA Node Template by a TOSCA orchestrator.
187 description: 'An optional property that indicates the requested default number of instances that should be the starting number of instances a TOSCA orchestrator should attempt to allocate. Note The value for this property MUST be in
188 the range between the values set for "min_instances" and "max_instances"
193 tosca.capabilities.network.Bindable:
194 derived_from: tosca.capabilities.Node
195 description: A node type that includes the Bindable capability indicates that it can be bound to a logical network association via a network port.
197 tosca.capabilities.network.Linkable:
198 derived_from: tosca.capabilities.Node
199 description: A node type that includes the Linkable capability indicates that it can be pointed by tosca.relationships.network.LinksTo relationship type.
201 tosca.capabilities.Container.Docker:
202 derived_from: tosca.capabilities.Container
206 entry_schema: version
214 entry_schema: PortSpec
218 entry_schema: PortSpec
224 org.openecomp.capabilities.attachment.DeploymentFlavor:
225 derived_from: tosca.capabilities.Attachment
226 description: The Node capability indicates the base capabilities of a TOSCA Node Type.
230 description: Deployment flavors instance
234 type: org.openecomp.datatypes.DeploymentFlavor
236 org.openecomp.capabilities.metric.SnmpTrap:
237 derived_from: org.openecomp.capabilities.Metric
238 description: A node type that includes the Metric capability indicates that it can be monitored using snmp trap.
241 description: Object Id of the metric
246 org.openecomp.capabilities.AllottedResource:
247 derived_from: tosca.capabilities.Root
249 org.openecomp.capabilities.metric.SnmpPolling:
250 derived_from: org.openecomp.capabilities.Metric
251 description: A node type that includes the Metric capability indicates that it can be monitored using snmp polling.
254 description: Object Id of the metric
259 org.openecomp.capabilities.metric.Ceilometer:
260 derived_from: org.openecomp.capabilities.Metric
261 description: A node type that includes the Metric capability indicates that it can be monitored using ceilometer.
264 description: Ceilometer metric type name to monitor. (The name ceilometer is using)
269 org.openecomp.capabilities.Metric:
270 derived_from: tosca.capabilities.Endpoint
271 description: A node type that includes the Metric capability indicates that it can be monitored.
274 description: Unit of the metric value
279 description: Description of the metric
284 description: Type of the metric value, for an example, Cumulative, Delta, Gauge and etc.
289 description: Category of the metric, for an example, compute, disk, network, storage and etc.
295 description: Runtime monitored value