by Craig Macfarlane.
As organizations look for ways to accelerate their migration process, TDS worked closely with solution architects at AWS to build an exciting new toolchain combining the power of our TransitionManager software with AWS CloudEndure.
The results? A solution that leverages automation and streamlining of many of the sequential tasks involved in a complex migration process. And that means a migration factory that works — quickly, efficiently and without risk.
Here is the original blog posted on the AWS Partner Network (APN):
As the adoption of Amazon Web Services (AWS) continues to grow, the need for highly reliable workload migrations at an accelerated pace is paramount. This is particularly true for enterprises turning to AWS to host mission-critical and legacy applications.
Organizations need a solution that expedites the migration process, without introducing further risk.
In this post, we will introduce an integration of TDS TransitionManager with CloudEndure Migration, an AWS solution that accelerates cloud migration projects to AWS while reducing risk through automated processes.
By automating and streamlining the sequential tasks of migration, we can create a factory-like production line, or “migration factory,” to achieve these goals.
Transitional Data Services (TDS) is an AWS Partner Network (APN) Advanced Technology Partner that provides the TransitionManager software-suite, a purpose-built software-as–service (SaaS) solution on top of the AWS platform.
TransitionManager is designed to improve the entire end-to-end process of data center and cloud migration projects.
As companies accelerate cloud adoption, key objectives must be accounted for during the migration:
Cloud migration factories can also benefit from a new solution which:
Migrations require a complex coordination of activities, performed in the proper sequence to assure overall project success. If one step is missed or performed out of sequence, it can result in a failed migration.
By integrating the cloud transport capabilities of CloudEndure Migration with the operational oversight of TransitionManager, users can move workloads more quickly, with less risk of rollbacks.
Let’s go through the steps for creating an automated migration pipeline, or migration factory, using TransitionManager and CloudEndure Migration.
During the assessment phase and planning/design phase, understanding the environment is the first step in creating a migration plan.
A core function of TransitionManager is the ability to import and extract, transform, load (ETL) data from multiple sources. Using TSO Logic, RVtools, Excel spreadsheets, CMDB databases, or other discover tools, these data sources can be imported to the TransitionManager database.
This allows you to:
First, we need an actionable data set from which to make migration decisions.
Let’s ingest key data elements from RVTools to describe our virtual infrastructure, a cost analytics platform like TSOLogic, and our CMDB to build our application to infrastructure relationships
It’s worth noting there is no development time required to create or alter these ETL scripts to your needs.
After you’ve completed the data aggregation and ingestion from all of your data sources, your end result is an actionable, visualized view highlighting key data elements required to make quick migration choices.
This interactive map within TransitionManager shows the high-level diagram of all servers and inter-dependencies from the import of the discovery data.
Figure 1 – Dependency Analyzer Map.
The dependency map in Figure 1 above is great for a high-level overview, but our initial goal is to segment the environment and find those highly portable workloads we can rehost in the cloud and show progress quickly.
Key properties to filter on can include both technical and business metrics, such as:
To get started, open the saved view called Highly Portable Rehost Candidates and view the results.
In this example, there are more than 300 rehost candidates identified based on just a few filterable parameters that we defined.
We took that massive environment map of our IT assets and created a segment from which we can focus and start to make progress towards the migration phase.
Figure 2 – Highly portable rehost candidates.
Looking at one of the servers by clicking on the workload name in the filter, we can see what data points were aggregated earlier to further evaluate if this is a good rehost candidate.
By right-clicking on any asset in the map, you can quickly see key data points that were aggregated to further evaluate whether you should rehost this workload to the cloud.
Figure 3 – Server detail when selecting “Show Asset” in the Dependency Analyzer Map.
After a quick discussion with the migration team and application owner, we will tag this workload with the “Rehost:CloudEndure” tag.
Because we have aggregated the right data in one place, we can streamline the workload selection and placement process without having to bounce around to multiple tools and attempt to re-organize massive data sets to make decisions.
As a final step, we will migrate this selected workload to the cloud by integrating TransitionManager with CloudEndure.
By tagging “TDS-Web024” with the Rehost:CloudEndure tag, we placed the workload in scope of the “Rehost with CloudEndure” workstream automation template.
Now, let’s browse to the template and review the workstream.
The red highlights in the Task Graph below indicate tasks that make API calls to a CloudEndure endpoint.
Figure 5 – Task Graph in TransitionManager.
The first task (the bubble filled in green) is a for a human to execute. The owner of the workload is notified to approve the workload for migration to AWS.
After the owner signs off, TransitionManager automatically installs the CloudEndure agent on our “TDS-Web024” in our source environment via API call.
The actual code snippet is:
Next, an automated task runs to check the status of the CloudEndure storage replication process from the source environment to your target Amazon Virtual Private Cloud (VPC).
In the CloudEndure console, the workload is showing fully replicated to AWS, and it’s now ready to be launched or test launched.
Figure 6 – CloudEndure console.
We complete the workstream by reaching out to CloudEndure via API to cutover the workload so that it’s running live in our VPC target, with an API call such as:
An engineer or app owner then tests the application running in the new AWS environment. Finally, we shut down the source workload and complete the migration activity.
Once you are comfortable with the automated process and approval steps, these tasks can be scheduled and repeated ad-infinitum, and run in parallel to create a high-volume, high success rate migration project with minimal manual interaction.
Each application can be assigned its own owner, approvers, dependent tasks, target environments within the AWS Cloud, and its own schedule for change management and approved move windows.
In this post, we walked you through a new approach to large-scale migrations to AWS that drives efficiency and significantly accelerates the process while reducing risk and uncertainty.
By using a central planning and orchestration platform, you can quickly aggregate your team knowledge and work more efficiently together to develop approaches consistent with your business needs and IT capabilities.
This integrated solution of TransitionManager and CloudEndure offers:
This blog, Creating a Migration Factory Using TransitionManager and CloudEndure Migration by By Craig Macfarlane, CTO at TDS, and Jon Keeter, Sr. Solutions Architect at AWS, originally appeared on AWS Partner Network (APN) Blog.
451 Research - 18 Jun, 2015 Analyst: Dan Thompson, Rick Kurtzbein, Rhonda Ascierto Transitional Data Services (TDS) has been helping customers with cloud migration, datacenter migration and consolidation since 2002.
Follow these key cloud migration best practices for successful cloud adoption in your organization.
Working with our partners at VMware, many customers across the globe have seen how TransitionManager can reduce risk, eliminate blind spots and complete migration projects faster with minimal disruption to operations.
Over the past few years, vendors from across IT have introduced “observability” tools or platforms. But what’s it really mean? And is it enough?
As IT environments continue to come increasingly complex, it is harder for teams to identify all interdependent assets and services that must be moved together to ensure business systems are not disrupted. This post will examine how TransitionManager helps teams get more value from tools they already have by integrating them to work together as a toolchain, and how leveraging automation to accelerate execution so teams can more quickly realize the benefits of cloud by migrating to AWS faster.
As many businesses rush to adopt cloud computing processes, it is not an easy initiative, it can be expensive and the migration process can be a drain on critical IT resources. But companies can keep costs low and make sure their team is working efficiently by implementing some key strategies.