R E C H E N Z E N T R U M 5. 3

Size: px

Start display at page:

Download "R E C H E N Z E N T R U M 5. 3"

Sarah Spencer
5 years ago
Views:

1 RECHENZENTRUM 5.3

2 HERZLICH WILLKOMMEN ZUR DOAG KONFERENZ 2017

3 Rechenzentrum 5.3 Christoph Münch Thorsten Wussow Slix Ralf Ernst Bundesagentur für Arbeit

4 AGENDA Intro Motivation Ideas behind the concept Working with passive/passive Software passive/passive ready Success story Links BEVOR WIR STARTEN

5 virtual7 GmbH Consulting- und Softwarepartner Unternehmergeführt 1996 gegründet 85 Mitarbeiter 1 Team aus Spezialisten WER WIR SIND

Development MÜNCHEN 18 Mitarbeiter Consulting Development Business - Development

6 KARLSRUHE 50 Mitarbeiter Consulting Development Infrastructure & Support Sales Marketing Finance Human Resources PFÄFFIKON Consulting Development Business - Development MÜNCHEN 18 Mitarbeiter Consulting Development Business - Development Sales TIMISOARA 17 Mitarbeiter Consulting Development Human Resources 85 EXPERTEN 4 STANDORTE 1 TEAM

7 WAS WIR MACHEN

ÜBER MICH: o Oracle WebCenter Content 11g Certified Implementation Specialist o Oracle Application Grid 11g Certified Implementation Specialist o Über 10

8 ÜBER MICH: o Oracle WebCenter Content 11g Certified Implementation Specialist o Oracle Application Grid 11g Certified Implementation Specialist o Über 10 Jahre Stellent/ UCM/WCC ERFAHRUNG o virtual7 SEIT 6 JAHREN o AKTUELLES PROJEKT: o APOK Bundesagentur für Arbeit CHRISTOPH MÜNCH / SENIOR TECHNICAL CONSULTANT

9 ÜBER MICH: o o o o THORSTEN WUSSOW

10 ÜBER MICH: o Senior- IT- Architect RALF ERNST

11 AGENDA o Intro o active/passive topology o active/active topology o Motivation o Ideas behind the concept o Working with passive/passive o Software passive/passive ready o Success story o Links

12 INTRO active/passive topology load balancer P A A C S T S I V I V E E Data Center One P A C S T S I I V V E E Data Center Two

13 INTRO active/passive topology Pros: High availability; if active side went down the passive side can take over Maintenance on one side of a cluster, while the other side is online Cons: No fail over during maintenance

14 INTRO active/active topology Data Center One load balancer A C T I V E Data Center Two A C T I V E

15 INTRO active/active topology Pros: High availability after failure on one side, directly response from the second side almost zero down time Cons: In case of failure of one node the performance of the whole cluster could go down The software has to be prepared for an active/active topology

16 AGENDA o Intro o active/passive topology o active/active topology o Motivation o Ideas behind the concept o Working with passive/passive o Software passive/passive ready o Success story o Links

17 MOTIVATION to think about a complete new and revolutionary concept o high management effort o high personnel effort o stable and redundant infrastructure o high monitoring mechanism o very cost intensive (hardware, licenses, employees, ) o

18 Need to think completely different

19 AGENDA o Intro o active/passive topology o active/active topology o Motivation o Ideas behind the concept o Working with passive/passive o Software passive/passive ready o Success story o Links

20 IDEAS BEHIND THE CONCEPT Brain storming Green IT no monitoring work life balance Infinity life cycle flexible working time almost flawless no documentation reducing costs data protection

21 Solution: passive/passive topology

22 DATACENTER TOPOLOGIES - WHAT DOES THE MARKET SAY? Magic Quadrant: Cloud Datacenter Topologies Passive-passive is seen as a strong contender (visionary) Active-passive Active-active Passive-passive Virtual Client Hope The Best (standalone)

23 AGENDA o Intro o active/passive topology o active/active topology o Motivation o Ideas behind the concept o Working with passive/passive o Software passive/passive ready o Success story o Links

24 WORKING WITH PASSIVE/PASSIVE/ STRICT MODE load balancer P A A C S T S I V I V E E Data Center One P A A C S T S I V I V E E Data Center Two

25 WORKING WITH PASSIVE/PASSIVE- PREEMPTIVE MODE load balancer P A A C S T S I V I V E E Data Center One S A T C A T N I D V B E Y Data Center Two

26 WORKING WITH PASSIVE/PASSIVE- ENFORCE PASSIVEWITH BPC ( BOOT PROTECTION CONTROLLER) load balancer P A A C S T S I V I V E E Data Center One Boot Protection Controller Boot State Quorum (Zookeeper) P A C S T S I I V E Data Center Two Boot Protection Controller Boot State Quorum (Zookeeper)

27 HISTORY OF PASSIVE/ PASSIVE Improvement ODA Outage-driven-architecture o Common ops-pattern o Passive-passive is ODA thought to the end o Endless vertical and horizontal scalability o Retroactive shutdowns Concept of NAZ (Non-availability-zones) o Multi-site passive-passive o Single-site passive-passive (it really doesn t matter that much ) o No-site passive-passive (run in a container)

28 WORKING WITH PASSIVE/ PASSIVE Improvement Backup and recovery o almost everytime backup o almost everytime recovery o Order of backup / recovery doesn t really matter any more! Software and Hardware live cycle o almost everytime life cycle for hard and software o Life cycle activities do not need to be moved to the weekend any longer à99.9% offline (hard to reach but assured) àoffline-status needs to be monitored

29 WORKING WITH PASSIVE/ PASSIVE Improvement Performance o Less data needs less band width o The amount of maximum application servers on each machine is based on the capacity of the harddrive not on CPU or RAM No admin frustrations o Less installation o Less bug fixing o Less maintenance o dump your config-management solutions o à freely adapted from Bob Marley: No user no cry

30 WORKING WITH PASSIVE/ PASSIVE Improvement Content strategy; big data? o This concept does not need solutions like nosql à nodata! o nodata = maxsecurity! o ISO = no problem Everyone talks about Green IT, passive/passive is based on this idea o less hardware à less power consumption o uninterrupted power supply unit is not needed o matches with virtual7 CD color J

31 WORKING WITH PASSIVE/ PASSIVE Failover Continuous Failover o Fully automated Failover-Pipeline o Keep things passive o Rolling shutdowns o How many succesful failovers do you have a day? New skillsets needed o Downtime Ensurance Engineer o Accidental Boot Prevention Supervisor o CDO à Chief Chief Downtime Officer

32 AGENDA o Intro o active/passive topology o active/active topology o Motivation o Ideas behind the concept o Working with passive/passive o Software passive/passive ready o Success story o Links

33 MEDUSA BUSINESS ADMIN CONSOLE 12P PASSIVE EDITION

34 MEDUSA BUSINESS ADMIN CONSOLE 12P PASSIVE EDITION

35 MEDUSA BUSINESS CONTROL 12P PASSIVE EDITION

36 MEDUSA BUSINESS CONTROL 12P PASSIVE EDITION

37 AGENDA o Intro o active/passive topology o active/active topology o Motivation o Ideas behind the concept o Working with passive/passive o Software passive/passive ready o Success story o Links

38 SUCCESS STORY1 I run a small hosting provider with more or less 1535 customers and I use Ansible to automate some operations to be run on all servers. Last night I accidentally ran, on all servers, a Bash script with a rm -rf {foo}/{bar} with those variables undefined due to a bug in the code above this line. All servers got deleted and the offsite backups too because the remote storage was mounted just before by the same script (that is a backup maintenance script)

39 SUCCESS STORY2 o Migration with integrated systems to passive-passive is as easy as that: o o o Daher bitte folgende Steckdosen ab :00 Uhr stromlos schalten, die Systeme werden vorab TEC1: Auch die Management-Switche e & OPS1-CC: Bitte ab :00 Uhr Power OFF nehmen und lassen o Rack 124 in K037: o M SL1 2.4, M SL3 2.4, M SL1 2.3, M SL3 2.3, M SL1 2.2, M SL M SL7 1.4, M SL5 1.4, M SL7 1.3, M SL5 1.3, M SL7 1.2, M SL5 1.2, M SL1 2.1, M SL3 2.1, M SL7 1.1, M SL M SL1 1.3, M SL M SL6 1.2, M SL4 1.2, M SL2 1.4, M SL4 2.4, M SL6 1.4, M SL4 1.4, M SL4 2.3, M SL M SL4 1.3, M SL6 1.3, M SL2 1.2, M SL4 2.2 o o Rack 957 VDT2 o M SL1 2.4, M SL3 2.4, M SL1 2.3, M SL3 2.3, M SL1 2.2, M SL3 2.2, M SL5 2.4, M SL1 1.4, M SL5 2.3, M SL1 1.3, M SL5 2.2, M SL1 1.2, M SL5 1.4, M SL3 1.4, M SL5 1.3, M SL3 1.3, M SL5 1.2, M SL3 1.2, M SL2 1.3, M SL4 2.3, M SL6 2.4, M SL4 2.4, M SL2 1.4, M SL4 1.4, M SL4 1.3, M SL6 2.3, M SL4 1.2, M SL6 2.2, M SL2 1.2, M SL

40 AGENDA o Intro o active/passive topology o active/active topology o Motivation o Ideas behind the concept o Working with passive/passive o Software passive/passive ready o Success story o Community & Links

41 COMMUNITY & LINKS Community International Passive-Passive User Group Links

42 Special Thanks to: Ralf Downtime Ernst Sturmius OfflineMostSecure Rippert Hans WhoNeedsMonitoring Mehl Thorsten NoContent Wussow Florian ClosedGate Stoll

43 Q U E S T I O N S A N S W E R S

High Availability for Enterprise Clouds: Oracle Solaris Cluster and OpenStack

High Availability for Enterprise Clouds: Oracle Solaris Cluster and OpenStack Eve Kleinknecht Principal Product Manager Thorsten Früauf Principal Software Engineer November 18, 2015 Safe Harbor Statement