OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

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

Recall that we allow any number of spaces between the scalar and unit so token function will still be an issue perhaps.

> 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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]