| Table of Contents |
|---|
1.1.1.
...
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.
1.1.1.1.1 Keynames
The Group Type is a TOSCA Entity and has the common keynames listed in section Error! Reference source not found. TOSCA Entity Schema.
In addition, the Group Type has the following recognized keynames:
...
Keyname
...
Required
...
Type
...
Description
...
attributes
...
no
...
list of
...
An optional list of attribute definitions for the Group Type.
...
properties
...
no
...
list of
...
An optional list of property definitions for the Group Type.
...
members
...
no
...
string[]
An optional list of one or more names 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 from the listed members nodes to the group, 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 “MemberOf” (group).
...
requirements
...
no
...
list of
...
An optional sequenced list of requirement definitions for the Group Type.
...
capabilities
...
no
...
list of
...
An optional list of capability definitions for the Group Type.
...
interfaces
...
no
...
list of
...
An optional list of interface definitions supported by the Group Type.
1.1.1.1.2 Grammar
Group Types have one the following grammars:
derived_from: <parent_group_type_name> version: <version_number> metadata: description: <group_description> properties: members: [ <list_of_valid_member_types> ] requirements: capabilities: interfaces: |
...
2 SDC Group Type Metadata
conformance level 8.0 | invariantUUID: | type: string description: Constant identifier of the resource model. Ex.: AA97B177-9383-4934-8543-0F91A7A02836 |
conformance level 8.0 | uuid: | type: string description: Versioned identifier of the resource model (this uuid is changed for every major version of the resource) Ex.: b8ff69ca-786d-479e-9f9c-217a90ee0ebc |
conformance level 8.0 | version: | type: string description: The resource version in SDC catalog. Two digit blocks separated by a dot (“.”). Ex. : “2.0” |
conformance level 8.0 | name: | type: string description: The name of the group. |
...