Bug 1759912 - [Docs] Document procedure for installing CAM via OLM as a source cluster
Summary: [Docs] Document procedure for installing CAM via OLM as a source cluster
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Migration Tooling
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.2.0
Assignee: Avital Pinnick
QA Contact: Zhang Cheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-09 12:00 UTC by John Matthews
Modified: 2019-10-23 07:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-23 07:46:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot with ui and controller options set to false. (84.64 KB, image/png)
2019-10-09 12:35 UTC, Jason Montleon 		no flags Details
View All

Description John Matthews 2019-10-09 12:00:11 UTC 
Jason,

Please help document the steps needed for installing Migration Operator via OLM with migration_ui and migration_controller set to false so the cluster is ready to act as a source.  (Assume we are looking at OCP 4 -> OCP 4 migration).

Avital needs help to know exactly what to put in docs for this step.

Please include a few screenshots to illustrate.
Comment 1 John Matthews 2019-10-09 12:01:23 UTC 
Once we have the info captured I'll reassign this to Avital to make the updates in official docs.
Comment 2 Jason Montleon 2019-10-09 12:35:00 UTC 
There's almost no difference. When creating the MigrationController CR just change the ui and controller to false. Screenshot attached.
Comment 3 Jason Montleon 2019-10-09 12:35:35 UTC 
Created attachment 1623792 [details]
Screenshot with ui and controller options set to false.
Comment 22 Xin jiang 2019-10-11 06:15:23 UTC 
Reviewed.
Note You need to log in before you can comment on or make changes to this bug.