Whitepaper RackWare For AWS
Whitepaper RackWare For AWS
WHITE PAPER
2014 RackWare Inc., LLC All Rights Reserved
November 6, 2014
Contents
Use of AWS within Enterprises today ........................................................................................................... 4
How Enterprises can Leverage AWS as an Extension of their Internal Environments ............................. 4
AWS and RackWare Use Cases ..................................................................................................................... 4
1. Migration to AWS.................................................................................................................................. 4
2. Hybrid Elastic scaling into AWS ............................................................................................................. 4
3. Cloud DR to AWS ................................................................................................................................... 4
Rackware Features .................................................................................................................................... 4
integration with AWS feature ................................................................................................................... 4
Benefits ..................................................................................................................................................... 4
Customer Example: Company A.................................................................................................................... 5
Application Architecture ........................................................................................................................... 5
Motivation for Migration .......................................................................................................................... 5
Use Case 1 - RackWares AWS Migration Plan, Strategy, & Execution Steps for Company A ...................... 6
Cloud Assessment ..................................................................................................................................... 6
Discovery ................................................................................................................................................... 6
Capture...................................................................................................................................................... 7
Cloud Onboarding ..................................................................................................................................... 7
Assigning ................................................................................................................................................... 7
Replication and Sync ................................................................................................................................. 8
Phased Migration ...................................................................................................................................... 8
Cut Over .................................................................................................................................................... 8
Use Case 2 - RackWares Hybrid Elastic Scaling with AWS ........................................................................... 8
Use Case 3 - RackWares DR to AWS............................................................................................................. 9
Summary ..................................................................................................................................................... 11
Conclusion ................................................................................................................................................... 11
MIGRATION TO AWS
RACKWARE
FEATURES
Ability to migrate
any workload
modern or legacy to
AWS
INTEGRATION
WITH AWS
FEATURE
BENEFITS
HYBRID ELASTIC
SCALING INTO AWS
Auto-scaling into AWS
when internal capacity
is exceeded.
CLOUD DR TO AWS
Integrations with
Amazon EC2, S3 and
EBS
Migration steps
reduced from
hundreds to a few.
Migration time
reduced from several
weeks to a few
hours.
The use cases above will become clearer with the customer example below that highlights step
by step what the processes for cloud migration, DR and hybrid scaling to AWS are.
Application Architecture
Using a standard 3-tier application architecture, Company A deploys a frontend hardwarebased load balancer, which manages traffic across two Apache web servers. The application is
running behind a company firewall (DMZ) and uses standard SSL encryption. The backend
business logic is implemented in Java, and leverages Tomcat as the application container and
application server, and three Tomcat servers power the website. The application also has a
database layer which consists of one master MySQL server and a slave server for greater
performance.
Use Case 1 - RackWares AWS Migration Plan, Strategy, & Execution Steps
for Company A
Cloud Assessment
During the technical assessment, RMM software discovered that the entire CompanyA.com
technology stack was compatible with AWS and could run in Amazons Cloud.
Figure 1
Discovery
The migration team ran RMMs agentless discovery services to map the relationships
CompanyA.com ecosystem between firewalls, load balancers, web servers, application servers
and MySQL DB. The dependence mapping was able to show ports as well as the number of
connections between tiers. RackWares RMM discovery engine was able to monitor
performance over time to make recommendations on target sizing.
Capture
RMM has file capture technology, supporting Windows or Linux, application, web and DB x86
architectures, without an agent. The agentless live capture was achieved without taking the
workload off-line or installing software. RMM captured the complete operating system,
application stack and data in single or multiple images. During the capture, RMM removed all
source hardware dependences. By removing source dependences including network address
and hardware drivers, RMM allows the source workload to be migrated to any new target
environment.
Cloud Onboarding
RMM for AWS includes pre-built integrations with AWS to support automatically creating AWS
AMIs from the requirements gathered during the discovery of the target resources. RMM
gives users the option to modify the AMI prior to its creation. The automation removes all
manual steps with creating an Amazon shell AMI prior to migrations. Rackware can inherit the
target network addresses during the Onboarding processing. Inheriting target networks
addresses allows for rapid transition into AWS VPC. RMMs instrumentation can build Amazon
Load Balancers and security groups from within the RMM interface.
Assigning
RMM is a point to point migration technology. The technology only requires a single
configurable port to be used during migration. Once the target images have been assigned to
the AWS shell target, Rackware is able to overwrite the AMIs with the source Image. During
this overwrite RackWare is able to inject drives into the captured image and inherit target
network addresses. Rackware has pre and post plugins that can be executed to automate IPs
connections AWS elastic load balances and automate adding host names to AWS directory
services.
Phased Migration
During the migration phase Company A has migrated copies of web and application to AWS.
Company A has a phased migration strategy. The configuration on premise hardware load
balancer was modified to send traffic to send request to the new instances in the cloud. After
verifying that the servers in the cloud were performing at required levels. The onsite servers
were dismissed one by one.
Cut Over
With the nightly sync policy the final cutover was accomplished in a short change window. This
change window can be live with the source web site still operational or can be taken off line.
image should a failover occur. The cloud DR feature supports all of these. While OS updates are
more infrequent it is still important to ensure that kernel patches are kept in sync with the DR
Image. When updating the OS, an image refresh operation is done from the RMM first before
the sync to the AWS CloudImage. Should the product system be compromised or inoperable,
the CloudImage is automatically launched and is running with the latest synchronized changes.
After the production instance is repaired and operational, its easy to restore the origin site
with any up to date changes made to the CloudImage in the cloud. When the origin site is
restored to its operational state, the administrator can utilize the capture from cloud feature to
refresh the original Image and synchronize any changes that occurred during the outage.
Summary: AWS allows customers to migrate entire environments into their infrastructure.
RackWare allows these customers to build, configure and replicate these complex
environments easily and quickly. When these environments need to be customized, customers
can simply punch in those desired changes into the RMM tool during replication to allow
complex, yet customized migrations and expansions to occur.
Conclusion
By investing in RMM for AWS Company A was able to:
Successfully migrate an existing web application to the AWS cloud with zero downtime to their
current production environment and shaved weeks off their original manual schedule.
Set up an intelligent hybrid scaling deployment that automatically scales into the AWS when
traffic exceeds a pre-defined threshold.
Protect their crucial application using AWS as the secondary site at roughly 1/10th the price of
traditional DR solutions.
Using a phased approach, the development team was able to resolve all the financial, technical and
business concerns.
About RackWare
RackWare allows enterprises to use the public cloud as just another resource for their internal
infrastructure for disaster recovery, as well as scaling purposes. With its unique ability to be platform
and cloud agnostic, RackWares flagship solution, the RackWare Management Module (RMM), allows
workloads to be ported between any platform, virtual or physical, and any cloud. RackWare has moved
thousands of workloads for hundreds of customers and has partnerships with large Service Providers and
VARs. RackWare was founded in 2009 and is based in Santa Clara, California. For more information, go
to: www.rackwareinc.com.
For more information on RMM for AWS visit http://www.rackwareinc.com/rackware-managementmodule-aws/ or email [email protected]