Page History

• API testing (2016-08)
• API backward compatibility - yes, same as Openstack, but not yet clearly defined in other areas
• tempest scenario (i.e. small nuggets of use patterns in system level) - included but optional.
  • Port security and security groups
  • VM life-cycle events
  • VM networking
  • VM resource scheduling
  • Forwarding packets in the data path
• VIM: Openstack only
• SDN: transparent mode only (e.g. ODL can be used as a Neutron plugin)
• Datapath: L3 level readability only - includes vPing, and ping tests on all networking datapath validations.
• VNF: VM for testing/ping.

• VIM: k8s test suite (see kubernetes certified.)
• VIM: define how to accommodate VIM choices in dovetail test framework
• Functest's proposed work on k8s

Candidates

• Patrole: testing OpenStack RBAC configuration using Tempest
  
  

• SDNVPN testing included in optional
• IPv6 testing included in optional
• SFC is not included due to upstream lack of maturity, or adoption
• SDN explicit north bound API not included - opnfv has not taken on this level of testing in large scale, upstream status unclear.

 Candidates

• Neutron trunk ports
  

• HA included as mandatory tests - supporting Openstack control service HA and resource overloads.
  • verify service continuity
  • verify control process recovery
• HA extensions needed.

•  Considered Bottleneck project proposal with a basic set, but it needed more testing experience in the community.
• More comprehensive set yet to be defined.

•  Is VM migration having a commonly accepted use pattern?

• Security: openstack features included in API and tempest scenario testing
  • virtual network isolation,
  • security groups,
  • port security
  • and role based access control 

• Discussing during the plugfest
• Domain expertise and contribution needed

Service Assurance, also include the tools for SA

• platform operational insights, e.g. telemetry, logging
• fault management

•  Not yet
• looking for contributions
• Doctor has a long list of dependencies

• looking for contributions

•  Net yet
• Some VNFs have been worked on in Functest, sampleVNF, discussion planned in plugfest how to proceed

•  Discussing methods to incorporate use case testing
  • Functest vIMS (cloudify orchestrated) - dependency to be analyzed, stable/mature?
  • alternatively, vIMS with Heat
  • other use cases in sampleVNF
  • other use cases in ONAP (e.g. vCPE) or other upstream projects

•  Not yet

• There will be a info session to discuss during plugfest at Portland

• Many good tools have been worked on in projects such as vsperf, and others, discussion planned in plugfest on how to address hardware dependency and methodology pitfalls, then decide if or how to proceed

•  Not yet

• There will be an info session to start the discussion in plugfest to think how we can collaborate

• ONAP just had the first release, related projects: VNFSDK, VVP
• Consider Fraser as a possible integration point

Multi-Site Federation

•  Not yet

•  Net yet
• Interesting area calling for contributions

• provide test result overview after a test run

• separation of test suite yaml spec file from the tool, so that the tool framework development/testing and the test suite spec can be cleanly decoupled

• developer's guide documentation

• 
  

• harmonization of log files
• tagging mechanism for test cases from all test projects
• LaaS support - dovetail should become a part of LaaS toolset, can be easily run any time by everyone