[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-170) WD02 - Explicit textual mention, and grammar support, for adding (extending) node operations
[ https://issues.oasis-open.org/browse/TOSCA-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Moshe Elisha updated TOSCA-170:
-------------------------------
Description:
Node template operations can override operations specified in its node type, including overrides of type operations to NoOps. Can node templates also add operations not specified in their types? March 18 call consensus was that it would be good to make this explicit in the text where "overrides" are discussed, and Matt thought the grammar should explicitly allow extensions to operations.
An example of all the possibilities regarding operations and derivation:
```
tosca_definitions_version: tosca_simple_yaml_1_0_0
node_templates:
server1:
type: custom.nodes.Compute
properties:
# Omitted
interfaces:
tosca.interfaces.node.lifecycle.Standard:
create: # Override an operation defined in the type (even adds inputs)
implementation: scripts/custom_create.sh
inputs:
some_input: hard_coded
configure: scripts/custom_configure.sh # Adds an operation that is not implemented in the type
start: null # Override the type operation with No-Op
# The postconfigure is defined in the type and is not overridden
node_types:
custom.nodes.Compute:
derived_from: tosca.nodes.Compute
interfaces:
tosca.interfaces.node.lifecycle.Standard:
create: scripts/create.sh
start: scripts/start.sh
postconfigure: scripts/postconfigure.sh
```
was:Node template operations can override operations specified in its node type, including overrides of type operations to NoOps. Can node templates also add operations not specified in their types? March 18 call consensus was that it would be good to make this explicit in the text where "overrides" are discussed, and Matt thought the grammar should explicitly allow extensions to operations.
> WD02 - Explicit textual mention, and grammar support, for adding (extending) node operations
> --------------------------------------------------------------------------------------------
>
> Key: TOSCA-170
> URL: https://issues.oasis-open.org/browse/TOSCA-170
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: Bug
> Components: Profile-YAML
> Affects Versions: CSD1
> Environment: grammar support for yaml extensions of operations.
> Reporter: Dale Moberg
> Assignee: Moshe Elisha
> Priority: Minor
> Fix For: CSD2
>
>
> Node template operations can override operations specified in its node type, including overrides of type operations to NoOps. Can node templates also add operations not specified in their types? March 18 call consensus was that it would be good to make this explicit in the text where "overrides" are discussed, and Matt thought the grammar should explicitly allow extensions to operations.
> An example of all the possibilities regarding operations and derivation:
> ```
> tosca_definitions_version: tosca_simple_yaml_1_0_0
> node_templates:
> server1:
> type: custom.nodes.Compute
> properties:
> # Omitted
> interfaces:
> tosca.interfaces.node.lifecycle.Standard:
> create: # Override an operation defined in the type (even adds inputs)
> implementation: scripts/custom_create.sh
> inputs:
> some_input: hard_coded
> configure: scripts/custom_configure.sh # Adds an operation that is not implemented in the type
> start: null # Override the type operation with No-Op
> # The postconfigure is defined in the type and is not overridden
> node_types:
> custom.nodes.Compute:
> derived_from: tosca.nodes.Compute
> interfaces:
> tosca.interfaces.node.lifecycle.Standard:
> create: scripts/create.sh
> start: scripts/start.sh
> postconfigure: scripts/postconfigure.sh
> ```
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]