[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 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]
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
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: tosca.datatypes.nfv.VduLevel targets: [ tosca.nodes.nfv.Vdu.Compute ]
regards shitao åää:
Marton, Gabor (Nokia - HU/Budapest) [mailto:gabor.marton@nokia.com]
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]