Define parameter values for scaling actions

Proposers

• Pedro Escaleira (IT)

Description

At the moment, when we want some config primitive to be executed when a scaling operation happens, we can define in the VNFD the primitive to be called within the scaling aspect information, as follows (where VDU_SCALE_INFO is auto-populated automatically by OSM with information related to the scaling operation):

vnfd:
  df:
  - id: default
    scaling-aspect:
    - id: scale-kdu
      name: scale-kdu
      max-scale-level: 10
      scaling-config-action:
        - trigger: pre-scale-in
          vnf-config-primitive-name-ref : scaled
        - trigger: pre-scale-out
          vnf-config-primitive-name-ref : scaled
    lcm-operations-configuration:
      operate-vnf-op-config:
        day1-2:
        - id: mp1_test
          config-primitive:
          - name: scaled
            execution-environment-ref: mtd-ee
            parameter:
            - name: scale_info
              mandatory: true
              hidden: true
              read-only: true
              default-value: <VDU_SCALE_INFO>

However, an user might to execute the same primitive both for scale out and scale in operations, as demonstrated in the VNFD snippet, but he may want to send distinct parameter values to the same primitive for each different scale operation i.e., when the trigger is pre-scale-in, the user may want to pass a value to a param test-param different from the value that he wants to be passed to post-scale-in.

The user may also want to pass this values in a static way i.e., using the VNFD, within each scaling-config-action, or may want to pass them dynamically when scaling the VNF (through the API request).

Demo or definition of done

When an OSM user can define a parameter value in the VNFD for each scaling-config-action and when an user can define a scaling-config-action parameter value when sending a scaling request to OSM.