You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reports/reports/cloud-endure-device42.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ sidebar_position: 5
6
6
importThemedImagefrom'@theme/ThemedImage'
7
7
importuseBaseUrlfrom'@docusaurus/useBaseUrl'
8
8
9
-
After you have performed your HyperVisors / \*nix/ Windows scans and associated your business applications to your devices using the Device42 Business Application functionality, you are ready to prepare for your migration to AWS using CloudEndure.
9
+
After you have performed your HyperVisors / \*nix/ Windows scans and associated your business applications with your devices using the Device42 Business Application functionality, you are ready to prepare for your migration to AWS using CloudEndure.
10
10
11
11
Device42 has streamlined the process of conducting cloud migrations to AWS by integrating with the CloudEndure Blueprint. With a few short clicks, Device42 users can assess which workloads have the CloudEndure agent loaded as well as export blueprints for CloudEndure migrations.
12
12
13
13
## Here's How It Works
14
14
15
-
When performing a migration with CloudEndure, the first step is to ensure the CloudEndure agent is installed on the workloads in scope. This can be easily viewed from the built-in **CloudEndure Prep** report.
15
+
When performing a migration with CloudEndure, the first step is to ensure the CloudEndure agent is installed on the workloads in scope, which you can easily view from the built-in **CloudEndure Prep** report.
16
16
17
17
- Select **Analytics > Advanced Reporting**.
18
18
@@ -44,9 +44,9 @@ After ensuring the workloads in scope have the CloudEndure agent installed, down
44
44
45
45
Once you have generated the CloudEndure **CSV** file from **Advanced Reporting**, you must make sure to download the [Mass Blueprint Setter](https://docs.cloudendure.com/Content/Scripts/CloudEndure%20mass%20blueprints%20setter.zip) script.
46
46
47
-
This script requires **Python2.7** to run, and in order to have the blueprint set in CloudEndure, the devices in the **CSV** file must have the CloudEndure agent installed and connected to your chosen project.
47
+
This script requires **Python2.7** to run, and in order to have the blueprint set in CloudEndure, the devices in the **CSV** file must have the CloudEndure agent installed and be connected to your chosen project.
48
48
49
-
Before running the script, in the CloudEndure CSV file you must add the project name in the first column (**projectName**) for each device. Include the relevant name of the matching project for each listed machine.
49
+
Before running the script, you must open the CloudEndure CSV file and add the project name in the first column (**projectName**) for each device. Include the relevant name of the matching project for each listed machine.
50
50
51
51

52
52
@@ -73,9 +73,9 @@ optional arguments:
73
73
```
74
74
</details>
75
75
76
-
When ready to run, supply all of the above parameters. If there are any issues when running the script a `.log`file will be created in the same directory.
76
+
When ready to run, supply all of the above parameters. If there are any issues when running the script, a `.log`file will be created in the same directory.
77
77
78
-
Once completed, all machines in the CSVfile that match machines in CloudEndure will have their respective blueprints updated.
78
+
Once completed, allthe machines in the CSVfile that match machines in CloudEndure will have their respective blueprints updated.
0 commit comments