[OASIS Issue Tracker] (TOSCA-231) Scalar units and get_property

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/TOSCA-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59344#comment-59344 ] 

Matthew Rutkowski  commented on TOSCA-231:
------------------------------------------

perhaps we create a rule for the token function that if the token treats multiple occurrences of one or more token characters as a single token (ignores extra adjacent space characters). 

OR

we make orchestrators either 
1) remove extra whitespace for scalar-unit type so token function can always be used on scalar-units

OR
2) create built in keynames for the 2 parts of scalar-unit that the orchestrator will recognize

e.g.,: 
properties
    disk_size: 10 GB

would have built-in keynames to access both parts like:

interfaces:
   Standard:
       inputs:
          # use built in keynames "scalar" and "unit" to get parts independently for scripts:
           local_storage_size: { get_property[ SELF, disk_size.scalar ] }
           local_storage_unit: { get_property[SELF, disk_size.unit ] }




> Scalar units and get_property
> -----------------------------
>
>                 Key: TOSCA-231
>                 URL: https://issues.oasis-open.org/browse/TOSCA-231
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>            Reporter: Luc Boutier
>
> Currently in the spec we manage all the scalar units as others values and I believe that a get_property usage on a scalar unit will return a scalar unit to the script e.g. 1 Gb, 1 MHz.
> I wonder if it won't be easier for users if the orchestrator have the responsibility of scalar unit parsing and provides value as a scalar using a defined root unit (B, ms, Hz)
> If not this means that any script that uses scalar unit will have to mange parsing by itself, it may not be very complicated but as a user I feel that it's always better when you don't have to manage it.
> What do you think ?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)