CVC-SDC-FAQ

Owned by abdel.rabi
Last updated: Sept 23, 2019 by Lincoln Lavoie
3 min read

Discussion during ONS UE 2019 Un-conference sessions

Architecture

  • Is SDC the "right place" for a single entry point for VNF testing within ONAP?

    • There is already a tester role in SDC, the aim is to make this part of the test flow in SDC.

Query Certification Portal (OVP Portal)

  • What is the key or keys that SDC is expected to pass when looking up the certification for a VNF?  Where do those values come from in both the Heat and TOSCA scenario?

  • Is there a proposal for SDC to publish certification/compliance results from OVP?  If so, what are the proposed controls to restrict who can publish what?  For example, what prevents an operator from publishing results on a VNF Provider’s behalf?

  • Is OVP expected to play a role in storing 3rd party certification results?

  • It was discussed to focus the first outcome on this topic in Frankfurt around read only access to the portal, which avoids specific issues around access controls and submission of results from a 3rd party, etc.

Package Validation Testing

  • Can VTP execute the VVP test cases (Heat package validation) today (Dublin or El Alto) or is that proposed for Frankfurt?  If yes, what version of VVP does it execute and what validation profile does it use (i.e. which --category options does it select)? 

 

Live VNF Testing (Instantiation, Performance, etc.)

  • 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 VTP, execution, and expect output.  VTP can pass these requirements up to the SDC, which creates the user interface under validation to "collect" this input from the user.

  • 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:

o   Heat-based instantiation testing is part of ONAP testsuite which means that invoking these tests would make the robot test scripts a required component via OOM

o   The Heat-based tests have additional inputs required to execute (preload templates and a mapping file).  It’s unclear how such dependencies would be captured in the current proposal.  These inputs are what enable us to supplement the model and choose where the test will be executed to ensure instantiation will work.

  • As we move beyond instantiation (ex: control loop, monitoring, post-configuration instantiation, etc.), there will be additional setup, configuration, and inputs required.  What is the vision for how that setup and input will work if the tests are to be invoked from SDC?