Met je hoofd in de wolken. Ard-Jan Glas

Transcription

1

2 Met je hoofd in de wolken Ard-Jan Glas

3

4 Trend Hogere availability 24 uur per dag global customers Van mainframe naar distributed Omzet verlies door downtime Klanten stellen hogere eisen

5 De volgende IT bubble? IDC Gartner Merrill AMI 2010 $16B naar 2014 $56B 2013 $150B 2011 $160B 2014 $100B

6 De volgende IT bubble? IDC 2010 $16B naar 2014 $56B 2013 $150B 2011 $160B 2014 $100B

7 Cloud voordelen Kosten veelal naar gebruik Gebruik van specialisten Onderhoud en continuiteit Schaalbare oplossing Afspraken over de performance

8 Cloud nadelen Revenue stream impact Afhankelijkheid van leverancier Beperkt in maatwerk Data en privacy protection Service level agreements

9 Type gebruikers Mobile Browse,Media, Games Home Consumer applications Retail Shopping cart and sales Manufacturing Productie besturing Finance Brokerage, Visa, ideal Overheid Politie, Brandweer Medish Life support

10 Kosten van downtime APPLICATION INDUSTRY Brokerage Finance Credit Card Sales Finance Pay-Per-View Media Home Shopping Retail Catalog Sales Retail Airline Reservations HOURLY COST $6.45 Million $2.60 Million $150,000 $150,000 $150,000 $150,000

11 Hoe bepalen van kosten Revenue Productivity Reputation Customer claims Financial valuation Incident recovery

12 Uptime Availability % 90% ("one nine") 99% ("two nines") 99.9% ("three nines") 99.99% ("four nines") % ("five nines") % ("six nines") Downtime per year 36.5 days 3.65 days 8.76 hours minutes 5.26 minutes 31.5 seconds

13 Test zwaarte bepalen Verlies door downtime Kosten voor het aantal 9 s Test zwaarte

14 Cloud customer Deployment Test Release Development Design Requirements End users

15 Er zijn grofweg 3 soorten clouds IAAS PAAS SAAS Infrastructure as a service Platform as a service Software as a service

16 Cloud provider

17 Cloud provider Service Agreement Test Users Response Load agv. Load max. Connections Security Disasters Downtime Application Deployment Configure Install Environment Loadtest Stresstest Environment Redundancy Failover Mirroring Replication Security Disaster Recovery Monitoring Reference application People & Documents

18 Infrastructuur Testen Test scheduler Interface TestDB Set Case Script simuleren monitoren

19 Software testen Test scheduler TestDB Set Case Script

20 Redundancy testing Leveranciers garanderen uptime Betrouwbaarheid componenten Referentie architectuur Combinatie van componenten Exact volgens design Simuleren van failures Hardware Platform Software

21 Failover binnen datacenter Hot swappable componenten Hot swappable systemen Power supply vervangen Netwerk componenten Bekabeling en layout daarvan Labeling en identificatie binnen datacenter

22 Active-Active datacenter failover New York Bangalore Mirroring or replication

23 Active-Active datacenter failover New York Bangalore failover

24 Active-Passive datacenter failover New York Bangalore Mirroring or replication

25 Active-Passive datacenter failover New York Bangalore failover

26 Environment testing June 2009 Amazon and Microsoft 4 uur downtime Jan 2010 Navisite downtime after lightning May 2011 No downtime at Fibernet after lightning strike

27 flooding 2009 Vodafone datacenter flooding

28 Fire In March of 2008, a Wisconsin data centre was wiped out in a fire, leaving many business web sites offline. Servers, routers, and switches were destroyed at Camera Corner, a Green Bay business that offered web hosting and other IT services. Unluckily, it took 10 days to get customer web sites back online. The company did not have a backup plan in case of a fire and the customers suffered as a consequence.

29 Fire 2008 Winsconsin datacenter fire

30 Earthquake

31 Environment testing Locatie Voldoen aan standaarden Fire Earthquakes Flooding Connections

32 Environment testing Datacenter in een container

33 De 3 P s en hun root cause Oorzaak van uplanned downtime Product People Process 20 % 40 % 40 % Test zwaarte

34 People Zorg dat dit perfect is geregeld; Training Documentatie Checklists Security en toegang tot datacenter Beschikbaarheid

35 Process En dit ook; Changed control/management proces Release proces Deployment process Traceability Housekeeping and cleanness

36 Disaster recovery plan Failover stappen plan Crisis centrum en team Communicatie Beslisbevoegdheid Alternatieve productie en kantoren Personeel Oplossen van de problemen