One of the key before Adopting to RHOSO 18, customers who are on ml2/ovs needs to migrate to ml2/ovn. we would like build a Proof of Concept (PoC) or end-to-end system validation. So that we can validate that the architecture meets our non-functional requirements (configured features, inter-components relationship, stability, performance etc) and mitigate technical risks before customer see them in their lab.

Acceptance Criteria (Definition of Done):
Integration Verification: 
1. The core architectural components are successfully adopted and remains functional as in previous release 
2. A single VM's life cycle flow successfully executed from the user with a appropriate response.
System scale/performance verification: 
1. Create reasonable stress on adopted RHOSO 18.0 to test the baseline architecture for networking services i.e Neutron, NFV, Designate, Octavia
Documentation/Report completion: 
1. Document all finds from this validation exercise, documenting why specific technologies or patterns were chosen, result and mitigation
2. Document working templates/repo 

Glimpse of customer environment:
Current deployment: RHOSP17.1
1. ml2/ovs 
2. Workloads are NFV (mostly dpdk datapath) 
3. Neutron trunk ports
4. VxLAN tunnel
5. Most traffic is east-west 
Future Deployment: RHOSO18 or later