DOCSP-6113: Ensure that all Atlas data import prerequisites are in sync (#136)

steveren · web-flow · commit 5dc60b0e61cd · 2019-10-31T15:11:51.000-07:00
diff --git a/source/cloud/migrate-from-compose.txt b/source/cloud/migrate-from-compose.txt
@@ -12,7 +12,7 @@
 
    time: 20
    prerequisites:
-     .. include:: /includes/steps/migrate-compose-pr.rst
+     .. include:: /includes/migration-pr-compose.rst
 
    check_your_environment:
 
@@ -25,4 +25,4 @@
      You created an Atlas cluster, migrated data from your old Compose cluster, and
      updated your applications to use the new Atlas Cluster. Congratulations and
      welcome to MongoDB Atlas!
-   whats_next:
+   whats_next:
diff --git a/source/includes/migration-pr-compose.rst b/source/includes/migration-pr-compose.rst
@@ -0,0 +1,59 @@
+* Your data is currently in a MongoDB database.
+
+  This guide focuses on migrating to Atlas from an existing MongoDB deployment
+  on Compose.
+
+* Your current MongoDB database is running MongoDB 2.6 or higher.
+
+  Atlas supports the latest versions of MongoDB: 3.4, 3.6, and 4.0.
+  If you're running MongoDB version 2.6 or greater, the Atlas Live Migration
+  Service can move your data directly into a newer database version.
+  Update your `MongoDB drivers <https://docs.mongodb.com/ecosystem/drivers>`_
+  and make any necessary code changes at the application level to ensure
+  compatibility. If you're running a version older than 2.6, see 
+  `Upgrade MongoDB to 2.6 <https://docs.mongodb.com/v2.6/release-notes/2.6-upgrade/index.html>`_
+  for upgrade instructions.
+
+* Your current deployment is a MongoDB replica set or sharded cluster.
+
+  If your deployment is currently a standalone instance, you must first
+  :manual:`convert it to a replica set </tutorial/convert-standalone-to-replica-set>`.
+  Live migration of data from sharded clusters is not supported.
+
+* (Optional) Enabled authentication on your source deployment.
+
+  The migration process requires that authentication is enabled on your
+  source cluster. See :manual:`Enable Auth </tutorial/enable-authentication>`
+  for instructions on enabling authentication.
+  You can verify that authentication is enabled on your source cluster
+  using the :manual:`mongo </reference/program/mongo/>` command:
+
+  .. code-block:: sh
+
+     mongo <mongodb-connection-string> -u <mongodb-username> -p --authenticationDatabase admin
+
+* The database user from your source cluster that you will use to perform the migration has the required MongoDB roles.
+   
+  The user must have the :authrole:`clusterMonitor` and :authrole:`backup` roles. To verify
+  that the database user that you intend to use for migration has the appropriate
+  roles, run the :manual:`db.getUser() </reference/method/db.getUser>` command against the admin database.
+
+  .. code-block:: javascript
+
+     use admin
+     db.getUser("admin")
+     {
+       "_id" : "admin.admin",
+       "user" : "admin",
+       "db" : "admin",
+       "roles" : [
+         {
+           "role" : "backup",
+           "db" : "admin"
+         },
+         {
+           "role" : "clusterMonitor",
+           "db" : "admin"
+         }
+       ]
+     } ...
diff --git a/source/includes/migration_pr.rst b/source/includes/migration_pr.rst
@@ -1,11 +1,11 @@
-* **Your data is currently in a MongoDB database.**
+* Your data is currently in a MongoDB database.
 
   This guide focuses on migrating to Atlas from an existing MongoDB deployment
   on AWS. If you have data in other database systems, such as MySQL, PostgreSQL, or
   DynamoDB, please `contact us <https://mongodbcom-node-staging-2.corp.mongodb.com/contact>`_
   for help with your migration.
 
-* **Your current MongoDB database is running MongoDB 2.6 or higher.**
+* Your current MongoDB database is running MongoDB 2.6 or higher.
 
   Atlas supports the latest versions of MongoDB: 3.4, 3.6, and 4.0.
   If you're running MongoDB version 2.6 or greater, the Atlas Live Migration
@@ -16,13 +16,13 @@
   `Upgrade MongoDB to 2.6 <https://docs.mongodb.com/v2.6/release-notes/2.6-upgrade/index.html>`_
   for upgrade instructions.
 
-* **Your current deployment is a MongoDB replica set or sharded cluster.**
+* Your current deployment is a MongoDB replica set or sharded cluster.
 
   If your deployment is currently a standalone instance, you must first
   :manual:`convert it to a replica set </tutorial/convert-standalone-to-replica-set>`.
   Live migration of data from sharded clusters is not supported.
 
-* **(Optional) Enabled authentication on your source deployment.**
+* (Optional) Enabled authentication on your source deployment.
 
   The migration process requires that authentication is enabled on your
   source cluster in AWS. See :manual:`Enable Auth </tutorial/enable-authentication>`
@@ -34,28 +34,28 @@
 
      mongo <mongodb-connection-string> -u <mongodb-username> -p --authenticationDatabase admin
 
-* **The database user from your source cluster on AWS that you will use to perform the migration has the required MongoDB roles.**
+* The database user from your source cluster on AWS that you will use to perform the migration has the required MongoDB roles.
    
-   The user must have the :authrole:`clusterMonitor` and :authrole:`backup` roles. To verify
-   that the database user that you intend to use for migration has the appropriate
-   roles, run the :manual:`db.getUser() </reference/method/db.getUser>` command against the admin database.
-
-   .. code-block:: javascript
-
-      use admin
-      db.getUser("admin")
-      {
-        "_id" : "admin.admin",
-        "user" : "admin",
-        "db" : "admin",
-        "roles" : [
-          {
-            "role" : "backup",
-            "db" : "admin"
-          },
-          {
-            "role" : "clusterMonitor",
-            "db" : "admin"
-          }
-        ]
-      } ...
+  The user must have the :authrole:`clusterMonitor` and :authrole:`backup` roles. To verify
+  that the database user that you intend to use for migration has the appropriate
+  roles, run the :manual:`db.getUser() </reference/method/db.getUser>` command against the admin database.
+
+  .. code-block:: javascript
+
+     use admin
+     db.getUser("admin")
+     {
+       "_id" : "admin.admin",
+       "user" : "admin",
+       "db" : "admin",
+       "roles" : [
+         {
+           "role" : "backup",
+           "db" : "admin"
+         },
+         {
+           "role" : "clusterMonitor",
+           "db" : "admin"
+         }
+       ]
+     } ...
diff --git a/source/includes/steps-migrate-compose-pr.yaml b/source/includes/steps-migrate-compose-pr.yaml
