software emea performance tour 2013 - hewlett packard€¦ · upgrade csa from v3.0 to v3.1 •...

Software EMEA Performance Tour 2013 London, UK 2 July

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

HP & Automation Logic Partnering for success Journey to the cloud with a UK Bank and Automation Logic

Kris Saxton July 2, 2013

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 3

Customer Technology Stack

Platforms

z series, p series, x86, Unisys, VMware, IBM VIOS

Operating Systems

AIX (5.3, 7.1), Windows (2003, 2008), RHEL (5.5, 6)

Middleware

Oracle, MS SQL, DB2, IIS, WebSphere

Network

Cisco

Storage

HDS(USP/VSP), IBM (SCV/DS8xxx), NetApp (File)


The Challenge • Deliver an automated server provisioning mechanism

• Deliver an automated AIX and Linux patching mechanism

• Deliver a platform for future automation of routine tasks within the Bank

• Use existing hardware, patterns and standards where available

• Integrate with existing services where possible

Principles behind Automation

Standardise

Automate

Consumerise

• Hardware • Software Stacks • Operating Systems

• Processes • Service Offerings

• Server Deployment • Storage Provisioning • Database Deployment / Mgmt

• Patching • Network Provisioning • Server/Security Compliance

• Single Self Service Portal • Deployment Approval • Full Server Lifecycle Management

• End User Standard Service Catalogue


5

• April 2012 Project start

• July 2012 3 months to deliver a working PoC to showcase automated builds in development environments

• Dec 2012 CSA introduced to deliver a production ready service

- to deliver a limited set of x86 builds for Windows and Linux

Roll out SA agent to all AIX and Linux, 3000+ instances

• March 2013 Extend automated build service to include AIX builds

Extend x86 services to use ESX5 and expand catalogue offerings

Introduce automated patching using HPSA for AIX and Linux

• June 2013 Numerous improvements to services

Introduce server lifecycle management to enable decommissioning, rebuilds and flex

Introduce application installs via HP SA (Oracle/ WAS)

Upgrade CSA from v3.0 to v3.1

• Sept 2013 Project close and move services to business as usual

Delivery Dates


Toolset selection

6

HP OO and HP SA selected as the strategic tool for Automation • Proof of Concept successful • Met with security requirements • Support of AIX was a critical factor • Successfully implemented in other UK financial organisations

Portal Selection • POC used existing in-house ordering system and HP OO - very limited selection of offerings • Significant work required to develop a flexible portal • HP CSA v3 was just released in July

HP CSA selected in August

• No other suitable products in market place (Low cost, proven integration with HPOO/HPSA) • Quick POC demonstrated ease of installation, deployment and integration • Limited financial risk • Met with short – medium term requirements • Added value with the introduction of server lifecycle management functionality


Working together

7

Complex project with very aggressive timescales

Dedicated management team to define scope and delivery mythology. • Lead Programme Manager (Bank) • 2 Project Managers (HP and bank) • 3 Solution Architects (2 bank, 1 HP)

HP Professional Services worked closely with the bank • Size environments to specifications • Install and configure tool sets.

HP Project Team • Dedicated HP Service Management Consultant • Dedicated BSA Senior Consultant (Solution Architect) provided by Automation Logic • Specialist Consultants – to deliver, implement, and train

Direct interaction with HP product management Regular meetings with HP Exec and Product managers


Pre Automation deployment issues

• Manual

• Prone to error

• Highly customised– every build is slightly different

• 4 weeks to deliver server builds

• Reliant on tribal knowledge

• Reliant on platform teams availability

• Lack of visibility of process lifecycle

• Process lacked integration


Professional Services Approach

• Demonstrate toolset technical capability

• Provide process guidance

• Challenge legacy thinking

• Methodology used at previous customers

• Benefits driven – Investing in what delivers value

• Start with the minimum viable scope

• Demonstrate value delivered at regular intervals


Deciding what to automate (XKCD Style)


How to prioritise automation

• Time to completion (request to fulfillment)

• FTE Effort in hours – using a multiplier to allow for different levels of SME

• Probability of human error (lots of manual data entry)

• Re-Work as a result of unwanted variation

• MTTR – Level of service outages and frequency

• Manual process overhead


Collect Data

ROI Analysis

Map to Automation Capabilities

Validate in Proof of Value

Demonstrate Projected Value

Effort (minutes)

Frequency (per year)

FTE Cost (multiple of 20k)

Rework (of original TTD)

TTD (SLA)

Result (over 3 years)

Effort to Automate Automate?

Server Healthcheck (as a result of monitoring

alert)

10 1460 1.8 1.2 1.5 228 Days 15 Days

Legacy Builds (NT, Solaris etc.)

300 2 1.0 1.2 1.0 3.9 Days 30 Days

Automate .. or not to automate


Deliver Framework

Portal - HP CSA (Cloud Services

Automation)

Orchestration - HP OO –

(Operations Orchestration)

Automation - HP SA (Server Automation)

Patching - HP SA (Server

Automation)

Standardise hardware

Pre provision • Networks • X86 • P-series • Storage

Eliminate Bespoke Builds

Build towards just –in-time provisioning

Standardise Builds

Create catalogue

Create building blocks

Use standard processes

Eliminate customisation

Orchestrate Builds

Steam-line manual process

Automate manual

processes

Reduce hand-offs

Eliminate human error

Provide Portal

Build Service Catalogue

Build services

Contain choice

No technical knowledge

required

Foundation Building Blocks


Solution Overview

• Cloud Service Automation • Service Catalog

• Lifecycle Management

• Request Management

• Operations Orchestration • Centralised business and technical rules engine

• Encapsulates knowledge

• Integration to all existing management systems

• Server Automation • Multi-platform management

• Audit and compliance with SOX/PCI

• Automated patch management


Integration Touch Points

• Active Directory

• DNS (Infoblox)

• IBM Tivoli configuration manager

• Landesk

• VMware vCentre

• CBF, PADM, CMDB, VRM, Databases ( In-House Tools )

• HP Server Automation

• McAfee Vulnerability Manager

• IBM Netcool Omnibus/Impact

• HP Service Manager


Challenges

Challenge Solution

Data availability and integrity Migrated legacy spreadsheets to accessible data sources and made existing systems data programmatically available

Tool maturity Updated the toolsets ( where available ) to allow programmatic interaction. Tactical workarounds put in place for critical legacy toolsets.

Incumbent staff Education and communication is key. Strong CTO and programme leadership. Technically challenge platform, SME’s advertise the benefits.

Organisational Immaturity Re-structured displaced FTE headcount to form central automation function. Governance process and user-groups to engage.


17

Before Automation (Nov 2012) • 23 Day e2e Process to deliver servers • 180 processes and 248 hand offs between teams • Inefficient, time consuming and prone to error After Automation (today) Average build time reduced to 60 mins E2E server delivery times reduced by 82% Over 30 processes automated Consistent repeatable builds delivered

2012 Delivery • 1600 VM Guests delivered by SD • Equates to 36,800 Gross Man Days Effort

2013 Forecasted Delivery • 4800 VM Guests to be delivered Indirect Benefits • Process improvements have delivered a 66%

reduction for non-standard builds (77 days to 26 days)

Before and after Automation


Delivery Highlights

18

A production ready HP ecosystem to facilitate server automation HP CSA - Cloud Service Automation HP OO - Operations Orchestration HP SA - Server Automation Production ready ‘private cloud’ delivered for Windows, Linux, and AIX Implemented and in-use since Dec 2012 Standard builds hosted in Dev, Pre Production and Production Process improvements Review and make ‘Lean’ - ready for automation Automate processes where required Change the way we do things, to make automation easier Centralised management of the UNIX estate Build compliance Patching Inventory


What does that mean to the customer?

19

Time to market • Quick access to development environments • Faster delivery of servers • Consistent builds • Automated application deployment • Removal of infrastructure implementation delays

Reusable development environments

• Environments ready to spin up and use Currency

• Keep systems (platforms and applications) current always to the latest patch and security Secured Standard Build

• Delivers Builds to Bank’s Security Standards • Not offered by industry standard ‘public cloud’ offerings i.e. Amazon


Closing

Right toolset

Right people

Right structure

Right mindset


“Those who say it can't be done are usually interrupted by others doing it.”

- James Baldwin

software emea performance tour 2013 - hewlett packard€¦ · upgrade csa from v3.0 to v3.1 •...

Documents