Cloudamize Training

Cloudamize is a cloud infrastructure analytics platform

that provides data analysis and recommendations to
speed and simplify cloud assessment, migration, and
management.
Challenges in the Cloud Journey

• Is Azure is right for me and how much will it cost?

• Which applications should I move to the cloud and in what order
should I move them?
• What are all the applications we have and how are they connected?
• Which cloud configuration is best for us?
• How do I control our cloud costs?
• How can I ensure optimal performance of our cloud?
• How can I accurately plan capacity?
The Cloudamize Platform

• Powerful cloud infrastructure

analytics platform for the entire
cloud journey
• Automated discovery &
dependency mapping to ease
migration
• Ongoing performance analysis for
precise right-sizing and capacity
planning
• Clear visibility into cloud costs
 The Cloud Journey
Assess • Plan • Migrate • Validate • Manage
THE CLOUD JOURNEY

Assess
• Get precise TCO for Azure
• Identify your best fit configuration
• See projected performance with
recommended cloud
configuration
THE CLOUD JOURNEY

Plan
• Discover your infrastructure
• Map application dependencies
• Build move groups and design
your migration plan
• Identify optimal cloud
configuration for each workload to
migrate to
THE CLOUD JOURNEY

Migrate
• Import your migration plan to ASR
• View ASR Readiness Reports
• Migrate workloads to Azure
THE CLOUD JOURNEY

Validate
• Visualize connectivity between
infrastructures
• Compare new state to historical
state
• Validate application dependency
THE CLOUD JOURNEY

Manage
• Right-size cloud workloads
• Accurately plan capacity
• Analyze costs, filter billing data,
and build chargebacks
Value Drivers
 Key Benefits of Cloudamize

• Achieve your optimal cloud environment

• Control and lower cloud costs
• More quickly make accurate cloud decisions
• Accelerate time to cloud value
 Key Benefits to Partners

• Remove sales friction at the TCO conversations level

• Increase close rate by having data-driven sales cycle
• Reduce time to migrate to the cloud
• Scale migration team by enabling PS/SIs on a single platform
• Increase retention by helping customer realize promise of the cloud
• Build and scale managed services business by providing services on
top of Cloudamize Platform.
 Value Delivered
• 500+ assessments

• 65% - 80% average

reduction in planning
time

• 48% average cost savings

• $75mm estimated savings

Case Studies
 Customer Reference
Cloudamize reduces enterprise’s app migration cycle by over 75%

Background • In the previous year, Accenture’s IT group began a migration of several internal datacenters
to the public cloud
• Accenture spent nearly 6 months manually analyzing how to optimize the mapping of on-
premise infrastructure to the cloud
• The migration planning proved to be highly challenging and led to delays in the migration
execution

Challenge • We want to migrate ~1600 nodes and ~500 applications to either AWS or Azure. How do we
rapidly determine the right-sized cloud configuration to ensure that workload performance
doesn’t suffer and get the final migration settings to move workloads to AWS and Azure?

Solution • Accenture decided to evaluate multiple tools and ultimately picked Cloudamize to help
during migration planning.

Impact • Accenture IT leveraged Cloudamize to build a more automated process for migrating to the
cloud, shortening the migration cycle for a typical application from 3 months to 3 weeks
relative to the previous approach
• Prior to adopting Cloudamize, Accenture IT used a highly manual approach, relying on
workshops with application owners to map out dependencies and an internal tool to
determine the configuration of cloud machines

17
Challenge
With two data centers, 840 servers, and 180 applications, Brookfield was challenged to understand how
much it would cost to move to Azure, and how it could efficiently build a migration plan.
Solution
Leveraged Cloudamize to understand the cost of its right-sized environment in Cloudamize and to
quickly build move groups for migration.
Results
Brookfield signed an Azure contract for a $2.5 M annual Azure subscription within 2 months of using
Cloudamize.
How It Works
Analytics Engine
Data Collection
Data Collection Method

Infrastructure Data Collection Options

VMware Hypervisor via Cloudamize Proxy, agent, and agent-less

Hyper-V Agent on Hyper-V host, agent on individual VMs, and agent-less

Windows Physical Machine Agent and agent-less

Linux Physical Machine Agent and agent-less

Cloud Instances Agent and agent-less

Cloudamize Agents Data Flow
Firewall

VPN 1

Physical Virtual
Machine Machine Outbound 80
or 8080 / 443 Outbound
(TLS 1.2) 443 (TLS 1.2)

VPN 2 Corporate Cloudamize

Proxy Server
Physical Virtual
Machine Machine
 Cloudamize Agent-less Data Flow
Firewall

Subnet 1 Outbound 80
or 8080 / 443
Inbound SSH / WMI (TLS 1.2)
Physical Virtual
Machine Machine

Outbound 443
Cloudamize Agentless (TLS 1.2)
Data Collector 1

Subnet 2 Corporate Proxy

Inbound SSH / WMI Cloudamize
Server
Outbound 80
Physical Virtual
Machine Machine or 8080 / 443
(TLS 1.2)
Cloudamize Agentless
Data Collector 2
vCenter FAQ
• Read-only credentials must be created for each
vCenter
• Data travels via Cloudamize Proxy which can be
installed either directly on the vCenter machine or
different VM
• The Cloudamize Proxy is unique to each vCenter
• The proxy communicates on 443 to IP
184.73.183.154
 Agent-less vs Agent-based
Class Agent-based Agent-less

Data Collection Method Light-weight software on each end-point SSH, WMI

Ports will be open between the agent-less data collector and all endpoints on the
Traffic is encrypted via SSL between endpoints and the
Security Protection subnet. Data is sent from the collector to the Cloudamize servers and is encrypted
Cloudamize server with mutual end-point authentication.
via SSL.

Agents must be installed on physical and virtual machines as WMI services for each Windows endpoint and SSH will need to be configured for
Deployment Model well as Hyper-V hosts. The agent can easily be pushed out each Linux endpoint. One machine/VM will need to have the agentless data
via Active Directory, chef, puppet, SCCM, etc. collector installed.

Agentless Data collector installed locally on one machine per subnet. Ports 135,
445, and 1024-65535 will need to be open inbound on all Windows endpoints,
A single outbound port (TCP 443) to a 104.197.11.97 is
and open outbound on the machine with the data collector installed. Port 22 will
Ease of Deployment required. Generally this port is already open and no changes
need to be open inbound on all Linux endpoints. The machine with the data
are needed.
collector installed will communicate outbound on 443 to Cloudamize IP
184.73.183.154.

Data collection occurs locally and compressed data is sent

Increases network traffic as the raw performance data is transported over the
over the internet. Data collection is halted if CPU and
Resource Consumption network to a remote data collector. No throttling mechanism available on the end
memory thresholds are crossed. For example, CPU is
points.
throttled at 2%.

High frequency collection of performance metrics. Discovers Lower frequency data collection results in less accuracy and not all application
Accuracy
all applications and their dependencies in detail. dependencies are captured.

Server must handle process initiation and stream handling resulting in a limit to
Agent handles process initiation and stream handling
Scalability how many connections can be handled concurrently. Agent-less Data collector can
making this very easy to scale.
handle 500 endpoints per collector.
Feature Comparison- Application Discovery
and Migration Planning
Features Agent Based Agent-less

Application Discovery Yes Yes

Application Dependency Mapping Yes Yes

Auto-grouping applications based on Yes Yes

business rules and affinity mapping

Inter and Intra dependency analysis Yes Yes

Cloud Readiness Analysis Yes Yes

Cloud Suitability Analysis Yes Yes

Migration Group Builder Yes. Yes

Shadow IT Identification Yes Yes

Firewall Rules Generation Yes Yes

Feature Comparison- Right-Sizing and TCO

Features (TCO) Agent Based Agent-less

TCO Projection for move groups Yes Yes

Right-sizing based on performance

Yes Yes
profiles (compute, storage, network)

Projection Analysis (see current and

Yes Yes
projected cloud performance)

Planning and Forecasting – ability to

build custom designs based on the Yes Yes
need

Pre-build TCO Reports Yes Yes

Missing Features in Agent-less Approach
Metric Impact

Short-lived connections If the connections short-lived they are not captured and that may result in missed
inter-connectivity
Lower performance resolutions Monitoring window is at every 5 min rather than every 30-seconds. Likely to loose
short-term peaks
DNS traffic and analysis Mapping between IP address and DNS is not available

Installed list of applications List of installed applications and their CPU Usage will not be collected

SQL Editions Cost analysis will not include SQL editions and mapping

.NET version Limited ASR compatibility analysis

Performance Throttling Agentless-monitoring does not have performance controlling mechanism on the
monitored host
Supported Systems

Supported Window OSs Supported Linux OSs Chipsets

• Windows Server 2016 • Red Hat Enterprise Linux Server • Intel xeon
• Windows Server 2012 R2 release 5.0 or higher • AMD Opteron
• Windows Server 2012 • Ubuntu 10.04 or higher • Pentium 4
• Windows Server 2008 R2 • CentOS release 5 or higher • Pentium D
• Windows Server 2008 • Debian GNU/Linux 6.0 or higher • Pentium M
• Windows Server 2003 R2 • Amazon Linux AMI release 2013.03 • Some Intel core 2
• Windows Server 2003 or higher
• Fedora release 12 or higher
• Suse Linux 11 or higher
• Oracle Linux 6.5 or higher

*Typically desktop and laptop processors are not supported since they are not considered candidates to move to the
cloud.
Deploy Cloudamize vs Manual approach

Manual approach
• Generally start w/ incomplete CMDB
• Have to fill in gaps w/ interviews
• Create pivot tables and Vizio diagrams to make sense of and visualize data
• Time and resource intensive for both partners and clients (can take months)
• High likelihood of inaccuracies

Cloudamize
• In most cases, no changes to firewall policy is needed so no issues with security change policy there.
• Business policies of software (agent) change management is applied so it can take up to a week to install everywhere.
• Quicker due to having all the necessary metrics at your finger tips
• User interface enables building move groups based on specific criteria and TCO of that group enabling faster
migration roadmap
Supported Infrastructure
Supported Systems

Supported Window OSs Supported Linux OSs Chipsets

• Windows Server 2016 • Red Hat Enterprise Linux Server • Intel xeon
• Windows Server 2012 R2 release 5.0 or higher • AMD Opteron
• Windows Server 2012 • Ubuntu 10.04 or higher • Pentium 4
• Windows Server 2008 R2 • CentOS release 5 or higher • Pentium D
• Windows Server 2008 • Debian GNU/Linux 6.0 or higher • Pentium M
• Windows Server 2003 R2 • Amazon Linux AMI release 2013.03 • Some Intel core 2
• Windows Server 2003 or higher
• Fedora release 12 or higher
• Suse Linux 11 or higher
• Oracle Linux 6.5 or higher

*Typically desktop and laptop processors are not supported since they are not considered candidates to move to the
cloud.
Demo
 Partner Process and Timeline
Total 32 Days

2 Days 3 Days 14 Days 3 Days 3 Days 7 Days

1 2 3 4 5 6 7
Discussion on Start Assessment Working Session with Execute Migration
Business Drivers Client to Revise Plan Plan Using ASR
and Assessment
Scope

Install Cloudamize Review Results and Build Present/Finalize

Software Initial Plan Migration Plan
1 2 3 4 5 6 7
Discussion on Business Drivers and
Assessment Scope
Initial Conversations / Business Drivers

• Internal drivers - management / business units driving Azure adoption

• Hardware refresh or EOL for hardware
• Environment preferences e.g. DR, Production, Location
• Business policy/ Security/Compliance concerns that may not allow specific
workloads to move to Azure
• Benefits from Azure
• E.g. agility, elasticity, cost savings via auto scaling, automation, chargeback.

• Budget constraints
• Internal success metrics
1 2 3 4 5 6 7

Install Cloudamize Software

Set Up Infrastructure

Select Add VMWare

Install Agents
Infrastructure vCenter

VMware Create read-only credentials Linux

Hyper-V Open outbound port 443 • Command line
On-Premise Install Cloudamize proxy • via Proxy
• Linux HyperV Host/Windows
• Windows • Command line
• via Proxy
Select Infrastructure
Install Agents / Configure VMware
Agent Installation: vCenter
 Add vCenter

Create read-only credentials for Cloudamize application. View the Cloudamize Tutorial here.

43
Install vCenter Proxy

Cloudamize Proxy will need to be installed on a Windows VM to route the traffic to Cloudamize Server.
View the Cloudamize Tutorial here.
 How Does the vCenter Proxy Work?

Windows VM
or Cloudamize Cloudamize
vCenter NM SSL Port 443 Proxy SSL Port 443 Server

• The proxy can be installed either directly on the vCenter machine or on a separate
Windows virtual machine.
• The proxy is unique per vCenter and VM, if you have two vCenters, you will need two
unique proxies installed
• View the Cloudamize tutorial here.
Agent Installation: HyperV / Windows
Add HyperV/Windows Agent

• Export your customer key and install an agent

• Outbound firewall over SSL/443 port
• Data can be routed via internet proxy
• View the Cloudamize Tutorial here.
Agent Installation: Linux
Add Linux Agent

• Export your customer key and install an agent

• Outbound firewall over SSL/443 port
• Data can be routed via internet proxy
• View the Cloudamize tutorial here.
 Route Agent Traffic via Internet Proxy

• View the Cloudamize Tutorial here.

Agentless Installation
Minimum Hardware Requirements for
Agentless Collector (up to 500 hosts)

• 64 bit OS
• .NET 4.0
• 4 CPU Cores
• 5GB RAM
• 2GB HDD
Cloudamize Agentless Data Collector: Setup
Cloudamize Agentless Data Collector: Setup
Cloudamize Agentless Data Collector: Setup
Cloudamize Agentless Data Collector: Launch

Launch Cloudamize Agentless Data Collector Cloudamize Agentless Data Collector UI

2. Click to open Cloudamize Portal

1. Right click or double click on

the tray icon to open UI
Configure Agentless Data Collection

1. Add Hosts

2. Select a host

3. Change credentials
Identify Errors and Expedite Setup

Click this button to see an error message

Note that if a remote WMI connection

fails after clicking ‘Add host(s)’ button or
when changing credentials, this message
will be popped up. This will allow
customers to quickly debug
infrastructure issues and commence
data collection.
Change Credentials
Interpreting Configuration
Monitor Data Collection
• As the installation occurs, the nodes will appear on within few minutes at Settings -> Group
Configuration -> Instance Settings
• You can disable the nodes you do not wish to assess using “Enable/Disable” button
Create Asset Groups

• Group nodes into Assets to understand assessment and cost per group.
 Interpreting Assess / Configure Plan

• Note in the screenshot that the node “SQL108” appears under the Hyper-V host and is enabled
• This shows that we are collecting the system-level data necessary for Assess
• View the Cloudamize Tutorial here.
 Interpreting Assess / Configure Plan

• Here we see that in the node “SQL108” also appears under “Physical Infrastructure”
• This shows that we are also collecting the application-level data necessary for Plan
• View the Cloudamize Tutorial here.
1 2 3 4 5 6 7

Start Assessment
Start Assessment
Click
Click here
here once
once ready
ready to
to begin
begin
the
the assessment.
assessment.

Check each view to

ensure infrastructure is
setup correctly.

Include all of the nodes

that are desired for the
assessment and exclude
everything else.
Confirm Assessment Summary

Review and confirm your assessment

details before continuing.

Click “Start” to continue.

Option to cancel and

return to configuration
settings.
User Region Selection

Select Region that the

assessment will be
mapped to.

Click save to start the

assessment
Select Assessment Dates / Duration
1 2 3 4 5 6 7

Review Results and Build Initial Plan

Review Cloudamize Results

• Understand Cloudamize Results

• Infrastructure mapping
• Right-sizing recommendations
• Cost analysis and TCO
• Application dependencies
• Application complexity
• Move groups
• ASR readiness analysis
 Price and usage

Cost Analysis, TCO & Right-Sizing breakdown for physical

and virtual
infrastructure

View data observed from

your current
infrastructure next to the
related data from the
recommended instance
Application Dependencies
and complexity
View all applications
Visualize
Visualize application
application running in your
interconnectivity
interconnectivity between
between infrastructure and select
nodes.
nodes. applications to view
interconnectivity.
Move Groups & ASR Readiness Analysis
Create move groups,
expand and collapse
groups, and visualize
the migration

Easily view which nodes

and move groups are
ready for migration
Build Initial Plan

• Review results and initial pass of migration plan based on your

knowledge of client environment
• Revising plan generally includes:
• Apply business drivers learned from initial scoping session
• Reconcile dependencies based on earlier discussions
• Editing configuration, deep dive into specific applications
• Building move groups based on discussions using cost, hardware or
time as a driver
1 2 3 4 5 6 7

Working Session with Client to Revise Plan

Working Session with the Client

• Walk through of the initial findings

• Deep dive into proposed migration plan
• Working session around below:
• Editing business drivers (if needed)
• Reconcile dependencies based on the client applications
• Editing move groups based on customer’s initial constraints such as
• Workload type (DR, Dev/Test, Production etc)
• Budget constraints
• Application groups
• Business drivers

• Discuss Azure architecture, networking, security groups

• Revise Plan
Apply Business Drivers and Quickly Build
Move Groups Undo
Undo migration
migration planner
planner
Build machines-based
move groups – Filter on
changes machine names, OS types,
changes and
and rollback
rollback to
to saved
saved Advanced
Advanced filtering
filtering --
changes OS version, etc. Allows
changes Allows rule-based
rule-based
move
move group
group building
building
and
and CSV
CSV downloads
downloads

Build application-based
move groups – Filter on
application class, vendor
name, program name, etc.
Drill Down into Application Dependency
Mapping
Node and
Click on a node application
or edge to see details with
more firewall rules
information

See details about

each application
connectivity
Prioritize Your Applications based on Cloud
Readiness and Suitability
Outlines Application
Prioritization for a cloud
Suitability defines if migration based on cost
the applications are and cloud readiness
more suitable to
Readiness move to the cloud
defines the and will be more
application efficient from cost
complexity for and performance
moving to the perspective.
cloud
Cost by application
group
1 2 3 4 5 6 7

Present/Finalize Migration Plan

Finalize Migration Plan

• Based on the working session discussion, build final deliverables

• Lay out the migration phases and the timeline
• Deliverable template available at Sysgain microsite.
1 2 3 4 5 6 7

Execute Migration Plan Using ASR

ASR Readiness Analysis
Find optimal ASR targets by performing ASR compatibility checks

On-Premise Move Group Azure Instances

SUCCESS

ASR Readiness Checks

WARNING

CRITICAL
ASR Readiness Report
Validation against ~20 checks to see if the
target is ready for ASR migration and divides
outcome into Success/Warning/Critical.
Provides workaround for the machines that
are identified with “Warning”
Example checks:
• General Disk Requirements
• Windows OS Requirements
Disk’s
Disk’s performance
performance Work
Work around:
around: Use
Use P30
P30 and
and
requirement
requirement failed
failed but
but can
can be migrate
migrate to
to RAID
RAID 0
0 after
achieved
be after • Hypervisor Requirements
achieved by
by striping
striping data
data migration
migration
across
across several
several disks.
disks. • Disk Space Requirements

Download
Download
• .NET Version Requirements
detailed
detailed analysis
analysis
• Boot Software Requirements
• Linux System Requirements
ASR Readiness by Move Group

Use ASR Readiness in prioritizing move

groups.
Machines with “SUCCESS” – Migrate
SUCCESS WARNING them first.
Machines with “WARNING” - Use
CRITICAL recommended workaround to fix issue
and complete migration to Azure.
View the Cloudamize Tutorial here.
 Steps to Migrate with ASR

Setup
Prepare to
Configuration Migrate
Migrate
Server

• Select a Cloudamize • Select the machines to be • Perform migration testing

design and a set of move migrated on the configured
groups • Create new configurations machines
• Select a machine to setup or choose existing storage, • Execute the migration
as the Configuration network, and subnet
Server configurations
• Enter the Subscription ID
and Resource Group for
the Configuration Server
 1 2 3

Setup Configuration Server

 Setup the Configuration Server

1. Select the host to be

used as the
configuration server

2. Click “Setup”
 Specify the Configuration Server Details

1. Enter the subscription ID 2. Enter the Resource Group

or create a new one

3. Click “Save”
1 2 3

Prepare to Migrate
Select the Machines for Migration

1. Check the boxes

next to the hosts to
be migrated

2. Select “Prepare To
Migrate” from the
drop-down list
3. Click “Go”
Prepare the Selected Machines for Migration

1. Select existing
Storage, Network,
and Subnet
configurations or
create new ones

2. Click “Save”
1 2 3

Migrate
 Migrate the Selected Hosts

1. Select hosts to
migrate

3. Click “Go”
2. Select Migrate
Start/Stop Migration Testing and Disable Migration

1. Select hosts to
perform
additional actions
on 2. Select additional
actions to perform on the
selected servers
3. Click “Go”
Partner Dashboard
Partner Dashboard Benefits

• Available at: dashboard.cloudamize.com

• Deal registration
• Manage accounts on Cloudamize application
• View status of assessments
• Identify errors
• Access to knowledge base
• Launch Demo Account
 Managing Customers
• Manage your accounts • Launch Cloudamize application
• See assessment status progress
 Managing Customers
• Add account executives or solutions engineers on the dashboard
• Assign different roles
• Access to knowledge base
• View the Cloudamize Tutorial here.
Support
Support Tools:
Details
• Microsite – Content hub and
support ticket tracking system
used for handling ALL
business and technical
support issues (shown on
right).

Sysgain Service Level Agreement (Migration Program):

• Provide support services to MSP Partners.
• Initial response within 2 hours of submitting issue.
• 48-72 hour resolution time for normal issues.
• Critical issues escalated and monitored regularly until resolution.
Support Links
https://cspmigration.freshdesk.com/support/home
Or Email requests to: [email protected]
Promotion Offer
Thank you.

Adi Rao
Partner Development Manager
[email protected]