Bug 1619540

Summary:	[Docs][OVN] Document migration tool from ML2/OVS to OVN
Product:	Red Hat OpenStack	Reporter:	Lucy Bopf <lbopf>
Component:	documentation	Assignee:	James Smith <jamsmith>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Joanne O'Flynn <joflynn>
Severity:	high	Docs Contact:
Priority:	high
Version:	14.0 (Rocky)	CC:	dcadzow, ekuris, jamsmith, sclewis, srevivo
Target Milestone:	beta	Keywords:	Documentation, FutureFeature
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-15 17:27:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1546994, 1925290
Bug Blocks:

Description Lucy Bopf 2018-08-21 07:18:49 UTC

Name of function:
Productize a migration tool from ML2/OVS to OVN

User story:
As an installer, I need to be able to migrate my data from ML2/OVS to OVN because I want to be able to use OVN, OpenStack, and OpenShift in the future and because I want to be able to have better avenues for better scalability, usability, etc.

Purpose of function:
In this RFE, the migration tool that moves existing deployments from ML2+OVS to OVN (preserving configuration, minimal downtime, automated, ...) will be productized (fully supported).

Work required (from detail plan):
Procedural 
------
How to install the migration tool
(by director)
Migration step: OVS to OVN
How to configure the migration tool
How to migrate the data
No particular test to validate (may change by development)
------

Conceptual 
------
What is being migrated?
Why do we need to migrate?
What happens during the process
What is OVN/ OVS/ ODL
------

Reference
------
N/A
------

Comment 3 Lucy Bopf 2018-08-21 07:22:49 UTC

Accepting into RHOSP 14 documentation program.

Comment 4 Lucy Bopf 2018-08-28 04:24:35 UTC

Assigning to James for review, and targeting at 14-Beta.

James, can you review the requirements in the detail plan, and add a baseline estimate for how many hours of effort this BZ needs?