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-289) Invalid definition for tosca.capabilities.Compute.Container.Architecture

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

Chris Lauwers commented on TOSCA-289:

That works, but there is still one more issue with this definition in the latest version: the entry_schema clause for the numa_nodes property doesn't have the type keyword. The correct syntax is:

    derived_from: tosca.capabilities.Container
        type: scalar-unit.size
        required: false
          - greater_or_equal: 4 kB
        type: tosca.datatypes.compute.Container.Architecture.CPUAllocation
        required: false
        type: map
          type: tosca.datatypes.compute.Container.Architecture.NUMA

> Invalid definition for tosca.capabilities.Compute.Container.Architecture
> ------------------------------------------------------------------------
>                 Key: TOSCA-289
>                 URL: https://issues.oasis-open.org/browse/TOSCA-289
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Bug
>          Components: Profile-NFV
>    Affects Versions: CSD03
>            Reporter: Chris Lauwers
>            Assignee: shitao li
> The latest NFV profile document includes a definition for tosca.capabilities.Compute.Container.Architecture. This capability has a property called mem_page_size that is defined as follows:
>     properties:
>       mem_page_size: 
>         type: scalar-unit.size
>         required: false
>         constraints:
>           - [normal, huge]
> There are at least 2 issues with the constraints on this property:
> - there is no constraint "operator" defined (it looks like what's intended here is a "valid_values" constraint)
> - 'normal' and 'huge' are strings and as a result are not valid values for scalar-unit.size

This message was sent by Atlassian JIRA

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