PROPOSAL FOR MIGRATING A Sourav Biswas PGPM-18-060

SET OF WEBSITES TO MS Sutirtha Choudhury PGPM-18-067

Vishwajeet Sinha PGPM-18-072
Sajid Ali PGPM-18-126
AZURE Shubhayan Roy PGPM-18-131
Sourav Basak PGPM-18-133
GROUP 9
CONTENT
Introduction
Our understanding of the Problem
Assumption and Scope
Solution Approach
Anticipated Risk
Financial Proposal
Timelines
Pricing
Risk
Executive summary
INTRODUCTION
 TWC is planning to migrate 5 websites to Azure cloud.
They sought for a proposal outlining the roadmap of migration.
XYZ Infosystems has conducted similar migrations for top
Fortune 500 clients across domains.
XYZ Infosystems would like to partner with TWC during this
migration process.
The proposal document contains the tentative plan for migration
along with pricing details.
The document also highlights the key assumptions and probable
risks identified.
 UNDERSTANDING OF THE PROBLEM
• Migration 5 websites from Century Link Data Center to Azure
• 16x5 support + on-call support during non support hours
• Leverage the existing ticketing tool for IT service management
• Existing system Landscape -
Components Details
SERVER 4 Apache Webservers (2 Prod, 1 Stage,
(Linux) DR)
4 MySQL Database servers (2 Prod, 1
Stage, DR)
Forward Proxy Varnish
Application/Framework PHP (Drupal Content Management
Framework)
Administration tool Drush
Versioning tool Git
Other tools Memcached (cache), Google Search
ASSUMPTIONS
 Existing system architecture document, functional document are
available.
Proper access to existing application across all platform as well as
ITSM tool will be provided upon request.
 Knowledge transfer session to be provide to our associates to
understand the existing system better.
 TWC to provide a reliable hi-speed internet connection for the
migration activity
 Contract with TWC and Century Link datacentre permits the
migration activity
 The licences for the Racemi migration tool to be provided by TWC.
IN SCOPE
 Re-Hosting and re-platforming the existing system landscape
 Providing Warranty support of 2 weeks post migration
 Providing dedicated 16x5 support(L1, L2, L3) post Warranty
support.
 Providing 24x7 on-call support for any exigency
 Debugging and fixing of issues arising due to the migration
activities.
 Configuring any upstream system if required.
 End-to-end documentation to be provided for the migration
activity
OUT OF SCOPE
 Any modification to the system code which is not related to Azure
migration
 Refactoring of existing architecture for performance improvement
 Any application software upgrade/update activity such as updating
Drupal 7 to Drupal 8, PHP 5 to PHP 7 etc.
 Any bandwidth intensive optimisation and performance improvement
work to be done on the system
 Debugging and fixing of existing application issues and functionality
 Performing performance testing, acceptance testing etc.
 Configuring any downstream system which consumes data from TWC
servers.
OUR APPROACH – SOLUTION
ARCHITECTURE
FUTURE ROADMAP
 Performance improvement initiatives by adding the app
servers as a part of autoscaling groups.
Eliminate the need for maintaining a DR instance along with
database with help of automated snapshots.
 Capacity planning to ensure high efficiency across the system
 Reduction of 15% FTE Y-o-Y after the project has reached steady
state.
ANTICIPATED RISK
 Any ad-hoc change in requirement may result in delay in the
timeline and rework.
 Change in specification of 3rd party tools and Azure public cloud
 Delay in getting approvals from TWC stakeholders
 Quality and compatibility issue at on-prem and public cloud
instance.
 Dependency on uninterrupted connectivity and speed of the
internet connection
 Mutually agreed cutover downtime to change DNS from on-
prem to cloud servers
Unfulfilled financial commitment at respective milestones.
 FINANCIAL PROPOSAL
 30% reduction on monthly cost and 25% savings on Y-o-Y spending.
 Provision to scale up in the future with minimum investment.
 8 member offshore (16 x 5) application support team post-migration.
On CenturyLink Datacentre Quantity Price($) Monthly Cost ($) On Azure Cloud Quantity Price($) Monthly Cost ($)
Elecricity - Compute (per kWh) 8 0.1 288 Compute node 4 0.05 144
Elecricity - Cooling (per kWH) 4 0.1 518.4 MySql Server 4 0.175 504
DBA 2 100 35200 Storage (GB) 5000 0.1 500
Network Administrator 2 80 28160 Redis Cache (1GB Standard) 4 0.138 397.44
Total 64166.4 Azure Serach (Basic) 4 0.1 288
Load Balancer (per 1M requests) 50 0.54 27
Support analyst (Offshore) 8 30 42240
Total 44100.44
TIMELINES
Week 1 Week 2 Week 3 Week 4 Week 5
Activities 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Review Security
Pre Migation Analysie system architecture
Compare Costs
Cloud Environment Setup
Development Cofigure tools
Migration code changes
Functionality Testing
QA
Performance Testing
Production Data/VMs migarion
Migration
Cutover - Go/No-Go
Post Migration Warranty Support
PRICING
Week 1 Week 2 Week 3 Week 4 Week 5
Resource 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Cloud architect (on shore) 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Developer 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
Tester 2 2 2 2 2 2 2 2 2 2
Offshore Lead 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Resource FTE Rate(per hour) Days Total
Cloud architect (on shore) 1 100 20 16000
Developer 2 30 25 12000
Tester 2 30 10 4800
Offshore Lead 1 50 25 10000
Sub-Total (USD) 42800
License Fee Quantity Rate
Racemi 4 299 1196
Total (USD) 43996
ADMINISTRATIVE DETAILS
The proposal is valid till 7th August, 2019.
 Customer will be billed bi-weekly and the payment must be paid
before 14 days on receiving the invoice.
Local taxes to be added to the invoice.
Payment must be done through demand draft, or bank
transfer only.
All disputes to be subject to jurisdiction courts at Mumbai.
EXECUTIVE SUMMARY
 Azure migration will take 3 weeks, post which warranty support
and dedicated support will take over
 30% reduction on monthly cost and 25% savings on Y-o-Y
spending.
 Provision to scale up in the future with minimum investment.
 Mutually agreed cutover downtime to change DNS from on-prem
to cloud servers
 End-to-end documentation to be provided for the migration
activity
THANK YOU GROUP 9