Downstream test automation, with sanity check of UDN functionality (otherwise covered by OCP QE), and integration points with VMs (live migration, east-west connectivity, API/DNS server connectivity)
 

List of objectives under consideration

The full list of objectives is linked to this issue.

QE Workload Distribution for UDN Feature Development and testing

The interface between the tests and the infrastructure will serve as the critical link, ensuring that both components work seamlessly together. The initial step will involve creating an API specification document outlining the functions, data structures, configurations, and error-handling mechanisms the infrastructure will expose to the test cases layer. This document will be a collaborative effort between Shahaf & Anat, serving as the foundation for infrastructure development and the automated test cases. As the project progresses, this document will be iteratively refined to reflect any changes or updates required by either side.

Responsibilities

ysegev@redhat.com - defined here
rh-ee-awax - defined here
sbahar - defined here

Iterative Progress Towards Completion

Progress will be made iteratively, with regular reviews and updates to ensure all components are aligned and moving forward. The team will follow an agile approach, focusing on continuous integration and refinement of the infrastructure and test cases.

Parallel Development and API Specification

Shahaf and Anat do not need to wait for Yossi to complete the formal test design before beginning their work. They will start by establishing the first phase of the API specification document, which will outline the initial expectations and requirements from both sides. This document will be a living document, refined iteratively as the project progresses. Shahaf and Anat will actively update and review the document to ensure it accurately reflects the needs of the tests and the infrastructure.