1 tosca_definitions_version: tosca_simple_yaml_1_0
3 filename: tosca/nodes.yml
10 description: The TOSCA Root Node Type is the default type that all other TOSCA base Node Types derive from. This allows for all TOSCA nodes to have a consistent set of features for modeling and management (e.g., consistent definitions for requirements, capabilities and lifecycle interfaces).
14 description: A unique identifier of the realized instance of a Node Template that derives from any TOSCA normative type.
18 description: This attribute reflects the name of the Node 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.
22 description: The state of the node instance.
27 capability: tosca.capabilities.Node
28 node: tosca.nodes.Root
29 relationship: tosca.relationships.DependsOn
35 type: tosca.capabilities.Node
41 type: tosca.interfaces.node.lifecycle.Standard
42 tosca.nodes.ObjectStorage:
43 derived_from: tosca.nodes.Root
44 description: The TOSCA ObjectStorage node represents storage that provides the ability to store data as objects (or BLOBs of data) without consideration for the underlying filesystem or devices.
48 description: The logical name of the object store (or container).
52 type: scalar-unit.size
53 description: The requested initial storage size (default unit is in Gigabytes).
57 - greater_or_equal: 0 GB
59 type: scalar-unit.size
60 description: The requested maximum storage size (default unit is in Gigabytes).
64 - greater_or_equal: 0 GB
67 type: tosca.capabilities.Endpoint
72 derived_from: tosca.nodes.SoftwareComponent
73 description: The TOSCA DBMS node represents a typical relational, SQL Database Management System software component or service.
77 description: The optional root password for the DBMS server.
82 description: The DBMS server's port.
87 type: tosca.capabilities.Container
89 - tosca.nodes.Database
93 tosca.nodes.WebApplication:
94 derived_from: tosca.nodes.Root
95 description: The TOSCA WebApplication node represents a software application that can be managed and run by a TOSCA WebServer node. Specific types of web applications such as Java, etc. could be derived from this type.
99 description: The web application's context root which designates the application's URL path within the web server it is hosted on.
104 capability: tosca.capabilities.Container
105 node: tosca.nodes.WebServer
106 relationship: tosca.relationships.HostedOn
109 type: tosca.capabilities.Endpoint
114 derived_from: tosca.nodes.Root
115 description: The TOSCA Compute node represents one or more real or virtual processors of software applications or services along with other essential local resources. Collectively, the resources the compute node represents can logically be viewed as a (real or virtual) "server".
119 description: The primary private IP address assigned by the cloud provider that applications may use to access the Compute node.
123 description: The primary public IP address assigned by the cloud provider that applications may use to access the Compute node.
127 description: The list of logical networks assigned to the compute host instance and information about them.
130 type: tosca.datatypes.network.NetworkInfo
133 description: The list of logical ports assigned to the compute host instance and information about them.
136 type: tosca.datatypes.network.PortInfo
139 capability: tosca.capabilities.Attachment
140 node: tosca.nodes.BlockStorage
141 relationship: tosca.relationships.AttachesTo
147 type: tosca.capabilities.Container
149 - tosca.nodes.SoftwareComponent
154 type: tosca.capabilities.network.Bindable
159 type: tosca.capabilities.OperatingSystem
164 type: tosca.capabilities.Scalable
169 type: tosca.capabilities.Endpoint.Admin
173 tosca.nodes.network.Network:
174 derived_from: tosca.nodes.Root
175 description: The TOSCA Network node represents a simple, logical network service.
179 description: The IP version of the requested network.
189 description: The cidr block of the requested network.
194 description: The IP address to be used as the 1st one in a pool of addresses derived from the cidr block full IP range.
199 description: The IP address to be used as the last one in a pool of addresses derived from the cidr block full IP range.
204 description: The gateway IP address.
209 description: An Identifier that represents an existing Network instance in the underlying cloud infrastructure - OR - be used as the name of the new created network.
214 description: An Identifier that represents an existing Network instance in the underlying cloud infrastructure. This property is mutually exclusive with all other properties except network_name.
219 description: A segmentation identifier in the underlying cloud infrastructure (e.g., VLAN id, GRE tunnel id). If the segmentation_id is specified, the network_type or physical_network properties should be provided as well.
224 description: Optionally, specifies the nature of the physical network in the underlying cloud infrastructure. Examples are flat, vlan, gre or vxlan. For flat and vlan types, physical_network should be provided too.
229 description: Optionally, identifies the physical network on top of which the network is implemented, e.g. physnet1. This property is required if network_type is flat or vlan.
234 description: Indicates the TOSCA container to create a virtual network instance with or without a DHCP service.
240 type: tosca.capabilities.network.Linkable
244 tosca.nodes.WebServer:
245 derived_from: tosca.nodes.SoftwareComponent
246 description: This TOSCA WebServer Node Type represents an abstract software component or service that is capable of hosting and providing management operations for one or more WebApplication nodes.
249 type: tosca.capabilities.Endpoint
254 type: tosca.capabilities.Endpoint.Admin
259 type: tosca.capabilities.Container
261 - tosca.nodes.WebApplication
265 tosca.nodes.Container.Application:
266 derived_from: tosca.nodes.Root
267 description: The TOSCA Container Application node represents an application that requires Container-level virtualization technology.
270 capability: tosca.capabilities.Container
271 relationship: tosca.relationships.HostedOn
272 tosca.nodes.Container.Runtime:
273 derived_from: tosca.nodes.SoftwareComponent
274 description: The TOSCA Container Runtime node represents operating system-level virtualization technology used to run multiple application services on a single Compute host.
277 type: tosca.capabilities.Container
282 type: tosca.capabilities.Scalable
286 tosca.nodes.SoftwareComponent:
287 derived_from: tosca.nodes.Root
288 description: The TOSCA SoftwareComponent node represents a generic software component that can be managed and run by a TOSCA Compute Node Type.
292 description: The optional software component's version.
296 type: tosca.datatypes.Credential
297 description: The optional credential that can be used to authenticate to the software component.
302 capability: tosca.capabilities.Container
303 node: tosca.nodes.Compute
304 relationship: tosca.relationships.HostedOn
305 tosca.nodes.BlockStorage:
306 derived_from: tosca.nodes.Root
310 type: scalar-unit.size
311 description: The requested storage size (default unit is MB).
315 - greater_or_equal: 1 MB
318 description: ID of an existing volume (that is in the accessible scope of the requesting application).
323 description: Some identifier that represents an existing snapshot that should be used when creating the block storage (volume).
328 type: tosca.capabilities.Attachment
332 tosca.nodes.network.Port:
333 derived_from: tosca.nodes.Root
335 The TOSCA Port node represents a logical entity that associates between Compute and Network normative types.
336 The Port node type effectively represents a single virtual NIC on the Compute node instance.
340 description: Allow the user to set a fixed IP address. Note that this address is a request to the provider which they will attempt to fulfill but may not be able to dependent on the network the port is associated with.
345 description: 'The order of the NIC on the compute instance (e.g. eth2). Note:
346 when binding more than one port to a single compute (aka multi vNICs) and
347 ordering is desired, it is *mandatory* that all ports will be set with an
348 order value and. The order values must represent a positive, arithmetic
349 progression that starts with 0 (e.g. 0, 1, 2, ..., n).'
354 - greater_or_equal: 0
357 description: Set is_default=true to apply a default gateway route on the running compute instance to the associated network gateway. Only one port that is associated to single compute node can set as default=true.
363 description: Defines the starting IP of a range to be allocated for the compute instances that are associated by this Port. Without setting this property the IP allocation is done from the entire CIDR block of the network.
368 description: Defines the ending IP of a range to be allocated for the compute instances that are associated by this Port. Without setting this property the IP allocation is done from the entire CIDR block of the network.
374 description: The IP address would be assigned to the associated compute instance.
378 capability: tosca.capabilities.network.Linkable
379 relationship: tosca.relationships.network.LinksTo
381 capability: tosca.capabilities.network.Bindable
382 relationship: tosca.relationships.network.BindsTo
383 tosca.nodes.LoadBalancer:
384 derived_from: tosca.nodes.Root
385 description: The TOSCA Load Balancer node represents logical function that be used in conjunction with a Floating Address to distribute an application's traffic (load) across a number of instances of the application (e.g., for a clustered or scaled application).
388 capability: tosca.capabilities.Endpoint
389 relationship: tosca.relationships.RoutesTo
395 type: tosca.capabilities.Endpoint.Public
396 description: The Floating (IP) client's on the public network can connect to.
400 tosca.nodes.Database:
401 derived_from: tosca.nodes.Root
402 description: The TOSCA Database node represents a logical database that can be managed and hosted by a TOSCA DBMS node.
406 description: The logical database Name.
411 description: The port the database service will use to listen for incoming data and requests.
416 description: The special user account used for database administration.
421 description: The password associated with the user account provided in the 'user' property.
426 capability: tosca.capabilities.Container
427 node: tosca.nodes.DBMS
428 relationship: tosca.relationships.HostedOn
431 type: tosca.capabilities.Endpoint.Database