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: 答复: Map of maps in TOSCA?


 

Hi Gabor

 

Interesting topic. I did not realize it when we discussed it the ETSI NFV SOL meeting.

I just check the definition of VduScalingDeltas in SOL001, it has

Table 6.10.6.2-1: properties

Name

Required

Type

Constraints

Description

initial_delta:

no

tosca.datatypes.nfv.VduLevel

 

Represents the initial minimum size of the VNF.

aspect_deltas

no

map to tosca.datatypes.nfv.VduLevel

 

Describes the Vdu.Compute scaling deltas to be applied for every scaling steps of a particular aspect.

 

Should it be defined as?

 

 

  tosca.policies.nfv.VduScalingDeltas:

    derived_from: tosca.policies.Root

    properties:

      initial_delta:

        type: tosca.datatypes.nfv.VduLevel

        required: false

      aspect_deltas:

        type: map # key: aspectId

        required: false

        entry_schema:

          type: map # key: scalingDeltaId

          entry_schema:

            type: tosca.datatypes.nfv.VduLevel

    targets: [ tosca.nodes.nfv.Vdu.Compute ]

 

regards

shitao

发件人: Marton, Gabor (Nokia - HU/Budapest) [mailto:gabor.marton@nokia.com]
发送时间: 2018710 0:15
收件人: tosca@lists.oasis-open.org
抄送: Nguyenphu, Thinh (Nokia - US/Irving) <thinh.nguyenphu@nokia.com>; Lishitao <lishitao@huawei.com>; Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>
主题: Map of maps in TOSCA?

 

Dear TOSCA Experts,

 

is the following type definition correct in TOSCA YAML v1.1?

 

  tosca.policies.nfv.VduScalingDeltas:

    derived_from: tosca.policies.Root

    properties:

      initial_delta:

        type: tosca.datatypes.nfv.VduLevel

        required: false

      aspect_deltas:

        type: map # key: aspectId

        required: false

        entry_schema:

          type: map # key: scalingDeltaId

          entry_schema:

            type: tosca.datatypes.nfv.VduLevel

    targets: [ tosca.nodes.nfv.Vdu.Compute ]

 

We currently have the above definition in the ETSI NFV VNFD specifiction (alias SOL001), where we intend to define the aspect_deltas property of the VduScalingDeltas policy to be a map of map of VduLevels:

 

The definition seems logical, but it is not obvious whether it does or does not conform to the property definition syntax in TOSCA YAML v1.1 (section 3.5.8.4) which is:

 

<property_name>:

  type: <property_type>

  description: <property_description>

  required: <property_required>

  default: <default_value>

  status: <status_value>

  constraints:

    - <property_constraints>

  entry_schema:

    description: <entry_description>

    type: <entry_type>

    constraints:

      - <entry_constraints>

 

The idea is to be able to write policies like this:

 

    - dbBackendCapacityVduScalingDeltas:

        type: tosca.policies.nfv.VduScalingDeltas

        properties:

          aspect_deltas:

            dbBackendCapacity:

              delta_1:

                number_of_instances: 2

              delta_2:

                number_of_instances: 1

        targets: [ dbBackend ]

 

Thanks a lot for your answer in advance, kind regards,

 

Gábor

 



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