Examples mycompanytypes.myrelationships.AppDependency: derived_from: valid_target_types: [ mycompanytypes.mycapabilities.SomeAppCapability ] Type A Group Type defines logical grouping types for nodes, typically for different management purposes. Groups can effectively be viewed as logical nodes that are not part of the physical deployment topology of an application, yet can have capabilities and the ability to attach policies and interfaces that can be applied (depending on the group type) to its member nodes. Conceptually, group definitions allow the creation of logical relationships to nodes in a service “membership” template that are not a part of the application’s explicit requirement dependencies in the topology template (i.e. those required to actually get the application deployed and running). Instead, such logical membership allows for the introduction of things such as group management and uniform application of policies (i.e., requirements that are also not bound to the application itself) to the group’s members. Keynames The following is the list of recognized keynames for a Group Type definition: Keyname Required Type Description derived_from no An optional parent Group Type name the Group Type derives from. version no An optional version for the Group Type definition. description no The optional description for the Group Type. properties no list of An optional list of property definitions for the Group Type. no [] An optional list of one or more of Node Types that are valid (allowed) as members of the Group Type. Note: This can be viewed by TOSCA Orchestrators as an implied relationship nodes, but one that does not have operational lifecycle considerations. For example, if we were to name this as an explicit Relationship Type we might call this (group). “” interfaces no list of An optional list of interface definitions supported by the Group Type. Grammar Types have one the following grammars: <>: derived_from: <> version: <> description: <>
Examples mycompanytypes.myrelationships.AppDependency: derived_from: valid_target_types: [ mycompanytypes.mycapabilities.SomeAppCapability ] Type A Group Type defines logical grouping types for nodes, typically for different management purposes. Groups can effectively be viewed as logical nodes that are not part of the physical deployment topology of an application, yet can have capabilities and the ability to attach policies and interfaces that can be applied (depending on the group type) to its member nodes. Conceptually, group definitions allow the creation of logical “membership” relationships to nodes in a service template that are not a part of the application’s explicit requirement dependencies in the topology template (i.e. those required to actually get the application deployed and running). Instead, such logical membership allows for the introduction of things such as group management and uniform application of policies (i.e., requirements that are also not bound to the application itself) to the group’s members. Keynames The following is the list of recognized keynames for a Group Type definition: Keyname Required Type Description derived_from no An optional parent Group Type name the Group Type derives from. version no An optional version for the Group Type definition. description no The optional description for the Group Type. properties no list of An optional list of property definitions for the Group Type. no [] An optional list of one or more of Node Types that are valid (allowed) as members of the Group Type. Note: This can be viewed by TOSCA Orchestrators as an implied relationship nodes, but one that does not have operational lifecycle considerations. For example, if we were to name this as an explicit Relationship Type we might call this “” (group). interfaces no list of An optional list of interface definitions supported by the Group Type. Grammar Types have one the following grammars: <>: derived_from: <> version: <> description: <>
TOSCA-Simple-Profile-YAML-v1.0-wd06-PublicCommentReview-Draft-3.docx