...
- Background: SDC is generally assumed to create and store an abstract model of a VNF suitable for deployment to multiple environments. As such, there should be key information missing from the SDC model that is required for instantiation: IP addresses, VM names, env-specific settings, etc. SDC also does not control where the VNF will be deployed as that is selected in VID. As we move forward with tests that would require a live VNF, this presents some challenges which I’m unclear on how they are being addressed.
- When a test case is on-boarded into VTP (i.e. from VVP or VNFSDK), the test model (in YAML) must define the expect inputs from
- How are per instance values planned to be provided to instantiate the VNF for testing? In the Heat scenario, a preload JSON must be registered with SDNC for each VF Module and environment combo, which SO will look up to instantiate a VNF in a selected environment. Even if you specify all property values in SDC, the preload itself is still required. It would also be inadvisable to specify all values in SDC as it would severely restrict your ability to deploy your modeled VNF across multiple environments.
- Generally speaking an ONAP instance will have multiple regions and tenants available for deployment. How would a user specify which environment a given test should be conducted in?
- In the demo, the validations are shown to be initiated at the VSP level, but during VSP creation the model is not yet complete and instantiable. Is the expectation that the user complete modeling of the Service and VFs, then come back to the VSP to conduct the certifications?
- Is it assumed that VTP would invoke the test cases we wrote in El Alto for Heat-based Instantiation testing? If so, what are the supported options by for registering and invoking tests? Couple things to keep in mind in this scenario:
...