Card
For 5G services, VNFs, and PNFs Day-1 and Day-n operation, user needs to be able to create configuration templates that will be used for service instantiation, configuration and update. (It is assumed that Day-0 configuration templates will be provided with the VNFD by vendor). Additionally, as part of service instantiation, the NFVO will require a set of inputs to trigger network service instantiation which will also be specified in a configuration file.
Those configuration templates will consist of arbitrary content and also of parameters. The parameters need have an option to accept value from service input parameters.
Configuration templates shall be stored in catalogue separately from services/VNFs/PNFs and used as part of those services/VNFs/PNFs composition.
Resulting CSAR shall contain the configuration templates associated to services/VNFs/PNFs.

Description:

User shall be able to onboard a configuration template file.
User shall be able to create a configuration template file.
User shall be able to modify a configuration template file.
User shall be able to delete a configuration template file.
User shall be able to tie configuration template parameters to input values of service/network service/VNF/PNF.
User shall be able to associate configuration template file to Service/network service/VNF/PNF.
Configuration template file shall be part of/associated with the CSAR file if it is associated to some service/network service/VNF/PNF.

Validations:
Application shall validate association of parameters to configuration templates
??
TOSCA:
??
Acceptance Criteria
1. UI behave as expected
2. TOSCA generated correctly
3. Application do not allow assigning value to un-existing parameter in configuration template
4. ??