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


Hi Gabor,

 

Why should tosca.datatypes.nfv.VduAspectDeltaDetails be derived from map? It should be a map of VduLevel, right?

 

 

  tosca.datatypes.nfv.VduAspectDeltaDetails:

    type: map # key scaleDelta

    entry_schema:

      type: tosca.datatypes.nfv.VduLevel

 

 

 

 

  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: tosca.datatypes.nfv.VduAspectDeltaDetails

 

BR,

Arturo

 

 

From: Marton, Gabor (Nokia - HU/Budapest) <gabor.marton@nokia.com>
Sent: Thursday, July 12, 2018 2:56 PM
To: Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>; Lishitao <lishitao@huawei.com>; tosca@lists.oasis-open.org
Cc: Nguyenphu, Thinh (Nokia - US/Irving) <thinh.nguyenphu@nokia.com>
Subject: RE: Map of maps in TOSCA?

 

Hi Arturo,

 

I cannot see a way in TOSCA to derive a data type from map. We would need something like:

 

  tosca.datatypes.nfv.VduAspectDeltaDetails:

    derived_from: map

    entry_schema:

      type: tosca.datatypes.nfv.VduAspectDeltaDetails

 

  tosca.datatypes.nfv.VduAspectDeltaDetails:

    derived_from: tosca.datatypes.Root

 

But even the âderived_from: mapâ line seems invalid in TOSCA (e.g. OpenStack tosca-parser says: âType "map" is not a valid typeâ), not to mention the âentry_schemaâ line.

 

We could have one more level in the hierarchy, which would be syntactically correct in TOSCA:

 

  tosca.datatypes.nfv.VduAspectDeltaDetails:

    derived_from: tosca.datatypes.Root

    properties:

      details:

        type: map

        entry_schema:

          type: tosca.datatypes.nfv.VduAspectDeltaDetails

 

  tosca.datatypes.nfv.VduAspectDeltaDetails:

    derived_from: tosca.datatypes.Root

 

But it is not what we would like.

 

What do you think?

 

Greetings,

 

GÃbor

 

 

From: Arturo Martin De Nicolas [mailto:arturo.martin-de-nicolas@ericsson.com]
Sent: Thursday, July 12, 2018 2:27 PM
To: Marton, Gabor (Nokia - HU/Budapest) <gabor.marton@nokia.com>; Lishitao <lishitao@huawei.com>; tosca@lists.oasis-open.org
Cc: Nguyenphu, Thinh (Nokia - US/Irving) <thinh.nguyenphu@nokia.com>
Subject: RE: Map of maps in TOSCA?

 

Hello Gabor,

 

I agree that type of aspect_deltas,  âmap of tosca.datatypes.nfv.VduLevelâ , is wrong in the table, it is not even aligned with the yaml definition which is map of map.

 

I think we should define a new datatype tosca.datatypes.nfv.VduAspectDeltaDetails which would be a map of tosca.datatypes.nfv.VduLevel.

 

Then the property aspect_deltas should be map of tosca.datatypes.nfv.VduAspectDeltaDetails.

 

Comments?

 

Best regards,

Arturo

 

 

From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org> On Behalf Of Marton, Gabor (Nokia - HU/Budapest)
Sent: Wednesday, July 11, 2018 12:28 PM
To: Lishitao <lishitao@huawei.com>; tosca@lists.oasis-open.org
Cc: Nguyenphu, Thinh (Nokia - US/Irving) <thinh.nguyenphu@nokia.com>; Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>
Subject: [tosca] RE: Map of maps in TOSCA?

 

Hi Shitao,

 

in fact, the âmap to tosca.datatypes.nfv.VduLevelâ Type in Table 6.10.6.2-1 is wrong: it should be âmap of map of tosca.datatypes.nfv.VduLevelâ, because by IFA011, one can define a VduLevel per scalingDelta per ScalingAspect (one VDU may participate in multiple ScalingAspects in principle).

 

As a plan âBâ, in case it turns out that the map of maps construct is invalid in TOSCA, we could tear the VduScalingDeltas policy apart along two directions: (1) separate policy types for initial delta and aspect deltas, and (2) separate policy templates for aspect deltas per aspect. I.e.:

 

  tosca.policies.nfv.VduInitialDelta:

    derived_from: tosca.policies.Root

    properties:

      initial_delta:

        type: tosca.datatypes.nfv.VduLevel

        required: true

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

 

  tosca.policies.nfv.VduScalingAspectDeltas:

    derived_from: tosca.policies.Root

    properties:

      aspect:

        type: string

        required: true

      deltas:

        type: map # key: scalingDeltaId

        required: true

        entry_schema:

          type: tosca.datatypes.nfv.VduLevel

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

 

  # .. same separation for VirtualLinkBitrateScalingDeltas

 

Resulting in policies like these ones:

 

    - dbBackendCapacityVduInitialDelta:

        type: tosca.policies.nfv.VduInitialDelta

        properties:

          initial_delta:

            number_of_instances: 1

        targets: [ dbBackend ]

 

    - dbBackendCapacityVduScalingAspectDeltas:

        type: tosca.policies.nfv.VduScalingAspectDeltas

        properties:

          aspect: dbBackendCapacity

          deltas:

            delta_1:

              number_of_instances: 2

            delta_2:

              number_of_instances: 1

        targets: [ dbBackend ]

 

Con: too many policies (we already have quite a few).

 

Letâs first see what TOSCA experts respond to the original question.

 

Greetings,

 

GÃbor

 

 

From: Lishitao [mailto:lishitao@huawei.com]
Sent: Tuesday, July 10, 2018 9:47 AM
To: Marton, Gabor (Nokia - HU/Budapest) <gabor.marton@nokia.com>; tosca@lists.oasis-open.org
Cc: Nguyenphu, Thinh (Nokia - US/Irving) <thinh.nguyenphu@nokia.com>; Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>
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]
åéæé: 2018å7æ10æ 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]