Cloud Migration

22
Simplifying Cloud Migration Planning Using RISC Networks CloudScape

Transcript of Cloud Migration

Page 1: Cloud Migration

Simplifying Cloud Migration PlanningUsing RISC Networks CloudScape

Page 2: Cloud Migration

O v e r v i e w o f P r o c e s s

Discover, Analyze, Migrate

Create or Modify Application / Service Groups•Use advanced Visualization

•Understand complex dependencies

•Segment by location and function

•Patent Pending Intelligent Application Grouping

Analyze Apps / Services for Migration Drivers•See Asset and Performance Issues

•Rank and Sort to help prioritize

Optimize Price and Provision Cloud Resources•Understand costs for over 15 different cloud vendors

•See application / service level pricing as well as workload pricing

•Storage and Network I/O factored in for true cost

Export Migration Plans and Migrate•Use RiverMeadow to execute migrations

•See full Network Connectivity Requirements for WAN / VPN / Firewall / Security rules

Page 3: Cloud Migration

Discovery MethodologyRISC Networks approach and process

Page 4: Cloud Migration

1-7+ Days

D i s c o v e r y

Discovery Methodology

Discovery Stage

ICMP Sweep (covers only opt-in

subnets)

Select Port Scans (Listed in Ops & Security Guide)

Match Credentials with Devices

(Credentials input during bootstrap)

Inventory Stage

Revisit Interesting Devices

Gather Workload Specific Data

(windows OS vs. Linux vs. VM, etc)

Interface with vCenter

(credentials required)

Performance Stage

Collect ongoing Dependency and Performance Data

Continues until Assessment is

ended

May be repeated multiple times as scope is refined

Ongoing

Page 5: Cloud Migration

Technical Architecture OverviewWhat information do we collect?

Page 6: Cloud Migration

Network Equipment

Windows Servers

Linux / Unix Servers (via SNMP)

VMware Infrastructure

RISC Networks Data Dictionary

Inventory – Hardware / Software / Operational Information Performance - Hardware Information

Page 7: Cloud Migration

RISC Networks Data DictionaryNetwork EquipmentInventoryHardware Information•Serial Number•Line Cards•Flash Size•Memory Size•Interface Information•ENTITY-MIB informationSoftware Information•Software version•Flash file listOperational Information•Routing Table•ARP Table•L2 Forwarding Table•Neighbor Information (CDP, FDP, LLDP, etc)•Spanning Tree Topology•SAN Switch Forwarding Information (WWN Names, etc)•SCSI Lun Information (FC Switches only)•Quality of Service Configuration•Cisco IP SLA Configuration•Cisco Netflow ConfigurationPerformance•Statistical Information

• Interface Utilization and Error Statistics• CPU and Memory Utilization Statistics• Cisco MQC Statistics• IP SLA Statistics (SLA Module)• Netflow flow information (Traffic Analytics

Module)

Windows ServersInventoryHardware Information•Serial Number (Dell Service Tag, etc)•Physical Memory•Physical CPU•Physical Hard Drive•HBA Information•Network Card informationSoftware Information•OS Version•Installed Applications and versions with process ID information•Windows Services and status•Logical Disks•Windows SharesOperational Information•Windows Event Log information (3 days of Errors and Warnings is pulled. This is optional and can be excluded)•Citrix Metaframe Server InventoryPerformance•CPU Performance•Process specific Performance metrics (CPU, Swap, etc)•Memory Performance (bytes used / % used )•Disk (Logical and Physical) performance (i/o per sec, i/o bytes, latency, etc)•Windows Network Interface Utilization (bytes in/out, etc)•Windows Process Information•Windows NetStat Connectivity Information (opt-in only)

Linux/Unix Servers (via SNMP)InventoryHardware Information•Physical Memory•Physical CPU•Physical Hard DriveSoftware Information•OS Version•Installed Applications and versions with process ID information•Logical DisksPerformance•CPU Performance•Memory Performance (bytes used / % used )•Disk (Logical and Physical) utilization (% utilized)•Socket Connectivity Information (uses TCP-MIB / prefers RFC 4022 version)•MIBS•HOST-RESOURCES-MIB•UC-Davis MIB Family

VMWareInventoryHardware Information•Server Model•Network Connectivity•Physical Memory•CPU•Disk Information (size and configuration)Software Information•Guest Inventory

• OS Version• ESX Location

•Host Inventory• OS Version

•DataStore mapping to hosts and guestsOperational Information•Virtual Switch configurationPerformance•CPU Utilization (wait time, ready time, etc)•Memory Utilization (usage MB, etc)•Disk Utilization (I/O / sec, bytes/sec, etc)•Network Utilization (bytes in/out)

Page 8: Cloud Migration

Technical Architecture OverviewHow do we collect this information?

Page 9: Cloud Migration

Collect Data with Scalable Virtual Appliance

• Scales to Infinite Subnets• Vmware Performance and Inventory

(vSphere API)• Network Infrastructure Performance

and Inventory (SNMP Read Only)• Microsoft Windows Performance and

Inventory (WMI Used)• Traffic Simulation (Opt in only)• Traffic Capture (Socket & Flow based

– see next slide)

On-Customer Premise

Secure Web Service**

**On-Premise Data Storage and Analytics Also Available

Analytics Layer Collaboration Platform

• Comparative Analytics across 6,000+ Customers

• Multiple Filed Patents

• Solve Client Problems• Migrate Data Centers / Cloud • Simulate App Traffic in the

cloud• Have meaningful, data driven

conversations with your customer

• Interactive Reporting

Agentless Architecture

Page 10: Cloud Migration

On-Customer Premise

On-Premise Analytics Layer Also Available

RN150RN50Socket Based Dependencies

• NetStat Collection must be enabled

• VA installs a service on machines, collects netstat information and deletes service – each time

• Collects socket based dependencies every five minutes during the engagement

Flow Dependencies (Optional)

• Collects data via Netflow from network devices, Vmware promiscuous mode, and port spanning if needed

• Can accept 10 simultaneous flow sources per RN50

• Gives rate information for building dependencies and network impact analysis

• Great for more advanced stage planning

Analytics Layer

V i r t u a l A p p l i a n c e s

Two Methods of Dependency Data Collection

Page 11: Cloud Migration

Technical Architecture OverviewWhere is this data stored?

Page 12: Cloud Migration

On-Premises Deployed

• Current implementation of CloudScape

• Runs entirely in the cloud• Data collector deployed as a VM in

the clients network infrastructure• Presentation Layer and Analysis

Layer both run in the RISC Networks infrastructure

• Most economical and fastest delivery of the CloudScape service

• No additional cost

• Available Early Q2 2015• For clients with high regulatory

requirements (Federal Government, Healthcare, Financial Services, etc. )

• Presentation and Analysis Layer runs in the customers data center, all orchestration (licensing, etc. ) runs in the RISC Networks infrastructure

• No data leaves the clients environment• Priced as an node-unit add-on

SaaS Delivered

Flexible Deployment Options: CloudScape FlexDeploy

Page 13: Cloud Migration

Flexible Deployment Options: CloudScape FlexDeploy

Page 14: Cloud Migration

Reporting and AnalysisUnderstanding your environment from an Application Perspective

Page 15: Cloud Migration

Requires URL or IP Address to discover dependencies (entry-point) and then it collects data on associated workloads

What happens if a client has 6000 apps?

http://db.app.com

Competition: Top Down Requires entry point

Discovery or Probe

Socket Based Dependencies• Agent-Based (a lot of cases)• Not Scalable for Large Enterprises• Time Consuming• Requires Entry Point for Each App• Error Prone

Agent Install

Page 16: Cloud Migration

CloudScape: Bottom Up

CloudScape collects and analyzes ALL workload data, applications, services,

performance, etc. FIRST

CloudScape automatically groups like applications

See Dependencies by Group or Globally including the potential network impact between dependent apps

Auto-Asset Discovery, Uncovers Migration Drivers

AD Grouping

ERP Group

• Reduces manual tasks• Improves project efficiency• Improves visibility for IT• Lower risk of missing something

Page 17: Cloud Migration

S e r v i c e s O r i e n t e d A r c h i t e c t u r e

Intelligent Application Grouping

Build or Modify Application Stacks for network impact analysis

Export Groups to Migration Platform

Page 18: Cloud Migration

A p p l i c a t i o n D e p e n d e n c y M a p p i n g

Visualizations Built for Migrations

Application and Service Grouping• Visualize complex communication between

different resourcesRate and Performance Detail• Understand Latency and even Loss % of

traffic between resourcesBuild Capacity by Location• Plan network capacity by understanding

location to location network requiresCreate a Services Oriented Architecture• Explore your network and understand the

different services that are being delivered for proper migration planning

Communication Density between

dependent workloads

Dependent Server & Communication Protocol

Page 19: Cloud Migration

C o m p l e t e C l o u d L i f e c y c l e R e a d i n e s s P l a n n i n g

Optimized Workload Pricing

Page 20: Cloud Migration

Network Impact Analysis

Details of all 8 of the total flows for the specific location

Page 21: Cloud Migration

O v e r v i e w o f P r o c e s s

Discover, Analyze, Migrate

Create or Modify Application / Service Groups•Use advanced Visualization

•Understand complex dependencies

•Segment by location and function

•Patent Pending Intelligent Application Grouping

Analyze Apps / Services for Migration Drivers•See Asset and Performance Issues

•Rank and Sort to help prioritize

Optimize Price and Provision Cloud Resources•Understand costs for over 15 different cloud vendors

•See application / service level pricing as well as workload pricing

•Storage and Network I/O factored in for true cost

Export Migration Plans and Migrate•Use RiverMeadow to execute migrations

•See full Network Connectivity Requirements for WAN / VPN / Firewall / Security rules

Page 22: Cloud Migration

Thank you