3. Aria Migration to VMC on AWS
From Simon Momber
From VMware Cloud Services portal, we can launch Aria Migration services. Here in Aria hub dashboard, we can see all our managed accounts on-premises sites or VMC sites, or even native public clouds. Within a single dashboard, we can see resources consumption and the trends, snapshot of all the applications, their security vulnerabilities, governance and the cost of these resources. All this level of information is very critical to make the right decision before any migration efforts, Aria Migration Services, we can gather relevant information for migration and create assessment reports. Here we're showing information of the target companies whose resources need to be migrated. We can gather this information from a live environment or from offline data. It's critical to have current usage data in order to plan better migration information, like total number of virtual machines and applications snapshot of your current utilization. Therefore, total CPUs, memory and storage uses. Next step is the assessment report. Where are we going to gather information that can answer questions like, should we migrate all applications at once or migrate them in waves? What are the dependencies and cost implications of these applications? While creating this assessment report, we automatically grouped all the applications as per their storage uses. And this can be changed per CPU or memory usage. We can learn about an application's dependencies in terms of what other applications they're talking to. We may be able to plan to migrate them in a group all together at once. We can also see all the workloads that make up an application. If we plan to migrate applications in Waves, this report is very useful as we can get the resource information for just an application and the flexibility to include or exclude the dependent workloads. Let's look at a pre-created migration assessment report for all instances of a target company. In the report calculator, we can modify Mows, subscription terms, type of host, and even billing types. And instances it shows me the potential cost saving to move to VMC on AWS. As we already have the information on the current resources we will need and how many VMC on AWS hosts will require to run those workloads. Remember in VMC, on AWS public cloud, you never have to pay per instance. Instead per host. So you can utilize the host for its maximum capacity. For maximum savings. This report also provides the resources snapshot per application and can be easily exported.