Initiative Overview (mandatory - Complete while in New status)

Our NFV dataplane performance tests has multiple stages that are manually done. Like building environment with ci-framework, creating vms on DUT compute, preping environment for dataplane automation (installing & configuring crucible, configuring vms), running respective test. 

These steps should be automated for standard NFV designs like SRIOV & OVN-DPDK. The predefined workloads should be configurable via automation. The results should be available on dashboard and comparable to previous runs.

This reduces the manual efforts of building and testing NFV with tools for common workloads and architecture which we have validated on a certain environment.

As an initial effort, we would like to build this for specific lab/environment.

Goals (mandatory - Complete while in New status)
Provide high-level goal statement, providing user context and expected user outcome(s) for this Initiative

• PerfScale Team benefits from the time saved.
• Stakeholders can revisit previous and current results on dashboard.
• Easier regression detection.
• At a later stage this effort can be extended to support performance-lab and can be reused by DFG to run more custom workload and push data to same backend for comparison.

Done - Acceptance Criteria (mandatory - Complete while in Refinement status):
Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Initiative. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view

• Automation can deploy SRIOV or OVN-DPDK environment on NFV perf-lab.
• Automation should take inputs on which workloads needs to be run.
• The results are stored in common backend ES.
• Dashboards can represent data from the current or past results.

Out of Scope __(Initial completion while in Refinement status):
High-level list of items or persona’s that are out of scope.
<your text here>

• Currently no other arch design than SRIOV & OVN-DPDK.
• CPT or prow integration is not covered but will be considered for future scope based on the success and usability of this automation for identified environments on which it can run.