Bankwest s Next-generation Data Centre Infrastructure. Mike Laytham

Transcription

1 Bankwest s Next-generation Data Centre Infrastructure Mike Laytham

2 Tips for upgrading your data centres

3 Challenges we faced

4 Too many mouths to feed $ CONTESTABILITY x Lots of different suppliers and contracts Differing SLA s Lots of Management points Low Capex cost Increasing operating costs Alerts/Logs/Patch/upgrades etc all different CAPEX OPEX

5 Stranded resources CPU <10% utilization Memory <20% 70% of the servers/week with zero network traffic 95% Virtualized 5% utilized Project focused not everyone could come or wanted to come to the party Very segmented physically & logically Couldn t share things lots of waste ~5-10% compute usage across all data centres

6 Siloed focus Hardware Huggers! Focused on Assets (Storage, compute, network etc) No cross team cohesion or skills transfer Operational processes long with lots of handoffs Complicates collaboration Doesn t support cloud service model Doesn t support Service broker model

7 Value of infrastructure Hardware Features Resiliency Cost + Risk + Agility Management Capabilities Integration API s Less importance on hardware features We built for this! More focus on this in the future

8 What we are doing

9 Play (nicely) to stay Flash Stack Flexpod Replaced technology stack Network, Compute, Storage, Firewalls, LB s Standardised simple reference architecture Tech partners that work well together Less Integration points Defined build guides Guaranteed SLA s Same operational processes

10 Waste not, want not DC1 DC2 Prod (Core applications) Storage Replication Production/DR Moved from 21 individual resource pools to ~3 Network segmentation managed at logical level (F5 + Checkpoint) rather than physical. Utilization 5% -> Target State of 60% + Footprint reduction minimum 50-60% Pre-Production Flex Capacity in case of DR

11 Customers are our assets Not interested in Network link down Network links down PRDU001 to BWDU002 Interested in the customer & the impact to the business service Cultural shift from Asset focus to Service focus ATM Outage 12:02pm 12:28pm Customer impact

12 C is for cookie Repeatable Reusable Profile & policy based Why invent the wheel again every time Compute network storage built from Self service / API layer Invest time Little or no time Define the Service Profile Network Security Compute Storage Policy Framework Provision the Service (Automated)

13 You can have your cake and eat it Tribes & Squads Differentiating capabilities Analytics Payments Content Network Compute Storage Consumable capabilities (Platforms Self Service) Infrastructure

14 Keep your head in the cloud Legacy and Traditional Applications Cloud Native Applications ( Re-provision not Repair ) APP APP APP APP APP APP APP API s Apps are changing HW HW HW HW Cloud aware HW HW HW HW HW HW HW HW HW Reprovisioning not rebuild or repair Silos Physical Clusters Virtualized Scale Out -Elastic New gen apps require new gen infrastructure

15 Experiment with experimenting Testing and Learning helps us get closer to the needs of our customers Small defined Proof of Concepts Quick time Fail fast LEARN fast

16 No pain, (no brain), no gain Automation is difficult but worth it!! Software development skills required Wish I d learnt python earlier!! Invest in a skills transformation programme. Talent matrix Identify skills now and for the future Decommission skills as needed is just as important Job Rotations, Mentors

17 Get the software built in - SDDC (Software Defined Data Centre) Composible Infrastructure API driven Abstraction = Simplicity Pooling = Efficient Abstraction + Pooling = Policy Based Automation of dynamic infrastructure

18 Always be available Always on, Always available - is the norm Failure isn t an exception it s a rule Design for failure Dependency mapping of a service is key Build the resiliency in at higher levels to develop self healing services Defined SLA s & XLA s

19 Support growth Granular metrics = Greater insights Greater insights = Informed decisions Cost, Capacity + Performance We need to not just store our data, but learn how we exploit it and transform it. Monitor trends & patterns in the market place New flexible licensing models (PAYG)

20 Manage the older ones Legacy will likely be still here for the next 10 years (Mainframe, AIX) Design for integration (API) Update existing contracts where possible (SLA s, QoS) Experience counts Troubleshooting is hard

21 Be prepared Enterprise Architecture is vital Needs to move towards an outside in rather than inside out approach (new technologies out there impact business models rapidly) Look at whole lifecycle Vision, Design, Build + Run Next steps 2/5 year + horizons Hybrid Cloud Capability Consider Cloud First not necessarily Cloud First API s, API s, API s.. Sustainable Models As a Service (Commodity)

22 Play by the rules Enterprise Architecture Function Guardrails, Principles and Standards All are required but manage cost/risk against agility, innovation and business growth Improved Service Management maturity (ITIL) The right governance is important requirement for Mode1 as well as Mode 2 (Traditional/Agile/DevOps

23 Looking to the future

24 Year 1, Year 3, Year 5 (Past, Present, Future)

25 Every day is a school day The customer is at the heart of everything we do!! Twice as good at half the cost in 3 years Reliability, performance, cost, skills Intelligent Workload Placement Edge Computing/IoT Foster a learning culture Continuous improvement

26 Questions?