Affects Version/s: None
Fix Version/s: Dublin Release
To eliminate the manual step of creating a dummy non-base module during the scale-out scenario, some pre-configuration needs to be done during the instantiation of base vf module itself - such that scale-out can happen multiple number of times without any manual steps involved.
The current approach discussed till now is -
Scenario: The policy currently needs a dummy scale-out instance (non base) to be pre-created in AAI, before processing any scale-out request.
Desired Outcome: The SO is able to instantiate the scale-out VF module with only knowing the scale out model name
- How do we fetch the scale out VNF model parameters such as “modelInvariantId”, “modelVersionId”, “modelCustomizationId” and “modelVersion”? These parameters are currently sent by Policy to SO in the scale out scenario (Please refer sample highlighted text below).
- Would the CLAMP be able to fetch the scale out VNF model parameters and pass the same to policy?
- The policy would then transparently pass these scale out VNF parameters to SO?
- The SO work flow for scale out would be able to fetch the other scale out VNF parameters, knowing the "modelName" parameter and then create the scale out VF module?
- What would be the best design and among the components CLAMP, Policy and SO – which of the VNF scale out parameters would be fetched to ensure that SO is able to create a scale out VF module?
Sample Policy to SO Payload: