f45d825324b84b880c69131f159f3941.ppt
- Количество слайдов: 21
Bullet proof your Amazon Cloud Deployment Ezhil Arasan Babaraj Director – CSS Corp Labs CSS Corp Twitter : @ezhilsathya Blog : http: //cloud 4 developers. com/
About CSS Corp § § Driving Technology Innovation and adoption § Technology Op. Ex Optimization § Transparency , Openness & Flexibility § Independent Centers of Excellence for R&D, Testing and Support § Passion for Advanced Technology Operations & Support § Dedicated CSS Labs for Technology Innovation § Business Operations and Technology Optimizer § Out-comes based pricing models § § 100% Referenceable Customers Top Mid Market ITO Provider 2007, 2008, 2009 – Data. Monitor § Privately held by investors including Goldman Sachs, SBAIF, Sierra Recognized leader in Technology Operations Management with Co. Es in Telecom, Saa. S, Cloud, RIM, Testing, Support and R&D § Strong Partner Ecosystem; AWS, Microsoft, IBM, HP § 150+ Long Term, Strategic and Profitable Customers § 5, 000+ Resources § Operations in USA, UK, Poland, India, Manila & Singapore § Market Validation – 100% Client Retention § Strong Tools Portfolio § Completed 3 acquisitions in 2010 © 2010 CSS Corporation Ventures Confidential 2
Cloud Services & Solution © 2010 CSS Corporation Confidential 3
Cloud Enablement Service & Phases S. No Phase Key Activity Breakdown § 1 Cloud Assessment § § 2 Cloud Architecture Development Application / Subsystem portfolio analysis and classification Technical Assessment Financial Assessment § CLIENT Cloud Deployment Architecture Private Cloud Deployment Architecture OSS Strategy (COTS Vs In-house Tools) § § 3 Proof of Concept § Build a pilot to validate technology 4 Application (& Data) Migration § AMI Creation Forklift / Hybrid Migration of applications § 5 Production Operations & Optimization © 2010 CSS Corporation § § § Tools Deployment Runbook Development Optimize usage based on demand Confidential 4
Context § § § Designing for Failure Testing for Failure § © 2010 CSS Corporation Cascading Failures § Prepare for failure Complex Systems Cloud Vs Traditional Confidential 5
What To Do? § § § Draft a Good backup strategy § Implement Monitoring & Alerting Ensure Effective Recovery Mechanisms § © 2010 CSS Corporation Appropriate use of Cloud Tools § Plan for Failure Understand the Cloud Provider Automate Provisioning Confidential 8
Compute Cloud Provider § § § Availability Zones § Machine Images(AMI) EBS Volumes § Security Groups § © 2010 CSS Corporation Multiple Regions § AWS EC 2: Elastic Compute Cloud Elastic IPs Confidential 9
Understanding AMI’s § § § Availability Zones § Machine Images(AMI) EBS Volumes § Security Groups § © 2010 CSS Corporation Multiple Regions § AWS EC 2: Elastic Compute Cloud Elastic IPs Confidential 10
AMI Type: EBS based § Ability to take Snapshots § Ability to stop instances Variable Root Disk Sizes § © 2010 CSS Corporation § § Why EBS Based? Quick boot up Ease of Bundling Confidential 11
AMI Choice & Customization § § § Customize Instance § Install Provisioning Agent Bundle the Instance=New AMI § © 2010 CSS Corporation Launch AMI § Machine Images Choose Trusted AMI Perform tasks on DR Regions Confidential 12
Application Deployment § Runtime choice § Easy to maintain deployment § Dynamic Configurations § Development knowledge § Not effective when creating public AMI's Script Provisioning § © 2010 CSS Corporation § Best when publicizing § An AMI for Every Version § Cumbersome to Maintain § Bundle into AMI Tested deployment Instance specific App Configs Confidential 13
Data Backup § § § Offsite / Remote Backups § Distributed / Replicated FS Remote Server Sync § © 2010 CSS Corporation Network File Sharing & Virtual SAN § Choice s S 3 Based backup EBS Snapshots Confidential 14
DR Setup § Needs a maintenance window § Would do with some data loss § Better cost benefit § Requires monitoring of the Primary Cold Setup site § © 2010 CSS Corporation § Higher cost of running § All updates and patch need to be applied § Warm Setup Needs a setup running all the time Needs data to sync at all times Confidential 15
Effective * DR Strategy § Track all the changes in live system § Keep 2 level redundant backups § Define maintenance windows § Monitor all at all times Do’s © 2010 CSS Corporation Run the DR setup in proximity § Run all the components § Back up all data frequently § Dont’ s § Not having fallback for DR setup Confidential 16
DR Demonstration CSS Corp Tools Used Infrastructure Monitoring Dashboard © 2010 CSS Corporation Confidential 17
DR Demonstration: Cold DR § § § Bring down the Live Environment § AMI with Cloud. Smart on DR Region Script Cloud. Smart for DR § © 2010 CSS Corporation Database Backup § Steps Keep script updated & versioned Bring up the Environment in DR Confidential 18
DR Demonstration Architecture © 2010 CSS Corporation Confidential 19
We managed to survive • The AWS US East Outage © 2010 CSS Corporation Confidential 20
Demo © 2010 CSS Corporation Confidential 21
Best Practices Build Using AWS Components § Storage of Images / Static files & Content Delivery – S 3 / Cloud. Front § Queue for storing messages – Simple Queue Service § Email sending service – Simple Email Service § Publish message / Subscription to messages - Simple Notification Service § Non-relational Data Store – Simple DB § Relational Database My. SQL / Oracle – Relational Database Service § Distribution of traffic – Elastic Load Balancing © 2010 CSS Corporation Confidential 22
Thank You! © 2010 CSS Corp – Copyright Notice: This presentation contains proprietary information of CSS Corp. No part of this presentation may be reproduced, stored, copied, or transmitted in any form or by means of electronic, mechanical, photocopying or otherwise, without the express consent of CSS. This presentation is for a specific intended audience circulation only and not meant for external distribution. Information is classified into 4 levels: Confidential: This is specifically restricted to the Senior Management and specific professional advisers. Restricted: This is restricted to Senior Management (PA’s and assistants an also access subject to respective reporting head’s approval). Private: This covers all information assets that have value but which do not need to fall within either of the other categories. Public: This is information which can be released outside the Organization.
f45d825324b84b880c69131f159f3941.ppt