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: Re: [tosca] Artifact property assingments


Hi Denes,

 

We discussed today in the WG the artifact property question below. The consensus is that only properties defined in the artifact type shall be assigned, and the example is wrong.

 

Actually in TOSCA v1.3 there in the âProperty assignmentâ description in section 3.6.11.2.1 it stated that:

property_name: represents the name of a property that would be used to select a property definition with the same name within on a TOSCA entity (e.g., Node Template, Relationship Template, etc.,) which is declared in its declared type (e.g., a Node Type, Node Template, Capability Type, etc.)

 

Best regards,

/Calin

 

 

From: <tosca@lists.oasis-open.org> on behalf of "Nemeth, Denes (Nokia - HU/Budapest)" <denes.nemeth@nokia.com>
Date: Tuesday, 26 January 2021 at 09:37
To: "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
Subject: [tosca] Artifact property assingments

 

Dear Tosca Community

 

Can you help us to clarify artifact property assignments in the Tosca specs 1.3 / 2.0 draft.

 

In both places the spec states that:

properties

no

map of 

property

assignments

The optional map of property assignments associated with the artifact.

 

It gives the following example

 

artifacts:

  sw_image:

    description: Image for virtual machine

    type: tosca.artifacts.Deployment.Image.VM

    file: http://10.10.86.141/images/Juniper_vSRX_15.1x49_D80_preconfigured.qcow2

    checksum: ba411cafee2f0f702572369da0b765e2

    version: 3.2

    checksum_algorithm: MD5

    properties:

      name: vSRX

      container_format: BARE

      disk_format: QCOW2

      min_disk: 1 GB

      size: 649 MB

 

however

 

tosca.artifacts.Deployment:

  derived_from: tosca.artifacts.Root

  description: TOSCA base type for deployment artifacts

tosca.artifacts.Deployment.Image:

  derived_from: tosca.artifacts.Deployment

tosca.artifacts.Deployment.Image.VM:

  derived_from: tosca.artifacts.Deployment.Image

  description: Virtual Machine (VM) Image

#no property definitions (or in any of the parents)

 

So the question would be is it allowed to assign properties that have not been defined.

 

Maybe it would be nice to add one of the following statements in the 2.0 specs.

  1. Only defined properties shall be assigned. (& fix example)
  2. Even non defined properties may be assigned

 

Cheers Denes



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