Skip to content

Commit 59273c9

Browse files
JuliaMongomongodb-docs
andauthored
(DOCSP-14276) (DOCSP-14275) Updated step 4 for opening the Live Migration UI in Atlas as part of new Live Migration from C/OM (#162)
* (DOCSP-14276) (DOCSP-14275) Updated step 4 for opening the Live Migration UI in Atlas as part of new Live Migration from C/OM * (DOCSP-14276) (DOCSP-14275) Updated step 4 for opening the Live Migration UI in Atlas as part of new Live Migration from C/OM * Fixed the build error about failure to download python by removing those lines Co-authored-by: mongodb-docs <mongodb-docs@mongodbdocs-VirtualBox>
1 parent 1dbc330 commit 59273c9

File tree

4 files changed

+43
-31
lines changed

4 files changed

+43
-31
lines changed

config/intersphinx.yaml

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,6 @@ name: mongodb
22
url: https://docs.mongodb.com/manual/
33
path: mongodb.inv
44
---
5-
name: pymongo
6-
url: https://api.mongodb.com/python/current/
7-
path: pymongo.inv
8-
---
95
name: motor
106
url: https://motor.readthedocs.io/en/stable/
117
path: motor.inv
@@ -21,4 +17,4 @@ path: objects.inv
2117
name: clouddocs
2218
url: https://docs.atlas.mongodb.com/
2319
path: cloud-docs.inv
24-
...
20+
...

source/images/atlas-deployment.png

-57.4 KB
Loading

source/includes/steps-migrate-compose.yaml

Lines changed: 31 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -38,11 +38,18 @@ content: |
3838
title: Begin the Atlas Live Migration process
3939
ref: begin-live-migration
4040
content: |
41-
Navigate to your Atlas cluster. Click the ellipsis (:guilabel:`...`)
42-
button and select :guilabel:`Migrate Data to this Cluster`.
41+
42+
a. In the left-side panel of your organization's page, click
43+
:guilabel:`Live Migration`.
44+
45+
#. In the :guilabel:`General Live Migration` card, click
46+
:guilabel:`Select Cluster for General Live Migration`.
47+
48+
#. Navigate to your Atlas cluster. Click the ellipsis (:guilabel:`...`)
49+
button and select :guilabel:`Migrate Data to this Cluster`.
4350
44-
.. figure:: /images/atlas-deployment.png
45-
:figwidth: 700px
51+
.. figure:: /images/atlas-deployment.png
52+
:figwidth: 700px
4653
---
4754
title: Review migration steps
4855
ref: review-steps
@@ -54,23 +61,26 @@ content: |
5461
title: Add IP address ranges to your Compose deployment whitelist
5562
ref: add-ip-ranges
5663
content: |
57-
For this step you'll need to have browser tabs open
58-
with both the Atlas Live Migration process dialog from the previous
59-
step and your Compose deployment dashboard.
64+
65+
a. Open two browser tabs:
66+
67+
- For the Atlas Live Migration process dialog from the previous step.
68+
- For your Compose deployment dashboard.
6069
61-
On your Compose deployment dashboard, click the :guilabel:`Security`
62-
link in the left-side navigation. The :guilabel:`Whitelist TCP/HTTP
63-
IPs` section displays a list of IP address ranges which are allowed
64-
to access your Compose deployment. Add the IP address range which is
65-
listed at the top of the Atlas Migration process dialog window.
70+
#. On your Compose deployment dashboard, click the :guilabel:`Security`
71+
link in the left-side navigation. The :guilabel:`Whitelist TCP/HTTP
72+
IPs` section displays a list of IP address ranges which are allowed
73+
to access your Compose deployment.
74+
#. Add the IP address range which is listed at the top of the
75+
Atlas Migration process dialog window.
6676
67-
.. figure:: /images/compose-add-ips.png
68-
:figwidth: 700px
77+
.. figure:: /images/compose-add-ips.png
78+
:figwidth: 700px
6979
70-
.. note::
80+
.. note::
7181
72-
Your Atlas migration IP address ranges may be different from
73-
those shown here.
82+
Your Atlas migration IP address ranges may be different from
83+
those shown here.
7484
---
7585
title: Add the hostname and port of your Compose deployment to the
7686
Atlas Live Migration dialog
@@ -89,19 +99,19 @@ content: |
8999
Enter the username and password for :guilabel:`oploguser` in the
90100
Atlas Live Migration dialog window.
91101
---
92-
title: Enter your Compose SSL Certificate data
102+
title: Enter your Compose TLS/SSL Certificate data
93103
ref: enter-cafile
94104
content: |
95-
If you don't have SSL enabled on your Compose deployment, skip this
105+
If you don't have TLS/SSL enabled on your Compose deployment, skip this
96106
step.
97107
98108
.. important::
99109
100-
In some Compose deployments, you can no longer view your SSL
110+
In some Compose deployments, you can no longer view your TLS/SSL
101111
certificate in the Compose UI. If this is the case for your
102112
deployment, you have two options:
103113
104-
- Contact Compose directly to request your SSL certificate.
114+
- Contact Compose directly to request your TLS/SSL certificate.
105115
- Use :atlas:`MongoMirror </import/mongomirror/>` to migrate
106116
your data to Atlas.
107117

source/includes/steps-migrate-to-atlas.yaml

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,17 @@ level: 4
2222
stepnum: 2
2323
content: |
2424
25-
On the Overview page of your new target cluster, click the ellipsis
26-
(...) button and select :guilabel:`Migrate Data to this Cluster`.
25+
a. In the left-side panel of your organization's page, click
26+
:guilabel:`Live Migration`.
27+
28+
#. In the :guilabel:`General Live Migration` card, click
29+
:guilabel:`Select Cluster for General Live Migration`.
2730
28-
.. figure:: /images/atlas-deployment.png
29-
:figwidth: 700px
31+
#. Navigate to your Atlas cluster. Click the ellipsis (:guilabel:`...`)
32+
button and select :guilabel:`Migrate Data to this Cluster`.
33+
34+
.. figure:: /images/atlas-deployment.png
35+
:figwidth: 700px
3036
---
3137
title: Click :guilabel:`I'm ready to migrate`.
3238
ref: click-ready-migrate
@@ -87,7 +93,7 @@ content: |
8793
#. Enter the MongoDB username and password from the AWS source cluster
8894
in :guilabel:`Username/Password`.
8995
90-
#. If SSL is enabled on the source cluster, toggle the :guilabel:`Is SSL enabled`
96+
#. If TLS/SSL is enabled on the source cluster, toggle the :guilabel:`Is TLS/SSL enabled`
9197
to :guilabel:`Yes` and upload the CA file that your source AWS cluster
9298
uses.
9399

0 commit comments

Comments
 (0)