HP DataCenter Automation at T-Systems Enterprise Services GmbH Using the example of the HP SA Project for one of our TOP 5 customers Beatrix Andres

Transcription

1 HP DataCenter Automation at T-Systems Enterprise Services GmbH Using the example of the HP SA Project for one of our TOP 5 customers Beatrix Andres T-Systems Enterprise Services GmbH Service Line Computing Services & Solutions, AL Customers North, AC DeS - Software Managementt Holzhauser Str. 4-8, Berlin (Tel.) (Fax.) Beatrix.Andres@t-systems.com 1

2 Project experiences with the Implementation of HP DataCenter Automation Agenda Motivation and Projektscope Architecture concept Utilization concepts especially in Software Management Situation and expected trends in 2009/2010 2

3 T-Systems the corporate customers arm of Deutsche Telekom and partner for the public sector. T-Systems ICT Leader in Europe Customer focus: 400 large-scale enterprises and corporations as well as the public and health sectors Sales: approx. EUR 11 billion Staff: currently 45,400 (26,400 national, 19,000 international) International presence: Branches in 22 countries, global delivery Solutions for at home Solutions for on the move ICT solutions Strategic partners: SAP, Intel, Microsoft, CISCO, EMC², Alcatel-Lucent 3

4 General requirements for IT service management service offering portfolio total cost of ownership ITIL standards SOX compliance data center service delivery service support ICT infrastructure management quality availability security reliability 4

5 General adjusting screws service offering portfolio total cost of ownership ITIL standards SOX compliance data center processes infrastructure organization tools quality availability security reliability 5

6 General roadmap for implementing IT services service offering portfolio total cost of ownership ITIL standards SOX compliance data center c b a) standardization a b) automation start c) integration quality availability security reliability 6

7 Project: Implementation of HP SA for one of our TOP 5 Customers IT Infrastructure 3600 servers Individual Servers or small series of identical configured systems OS: Solaris, AIX, RedHat Linux, SuSe Linux, W2K, W2K3, Windows Terminal Servers, Windows 2008 and virtualized environments desktops ~200 applications The starting situation of the IT-Management-Infrastructure Software Management: HP CA (RADIA) Configuration Management (HP Asset Center) Data is kept in HP Asset Center, Active Directory and HP CA Cosima Service Center 7

8 High-Level Business Goals for Server Automation in our IT Operations 1 Data Center Automation for all components (means cost reduction and improvement in efficiency) 2 Automatically updated Configuration Management Database as a basis of Change- and Release Management 3 Provisioning from the ground up across all disciplines (complete stack) managed by a workflow tool (HP Operations Orchestration) controlled by the Order process. HP OO project started in August September

9 Automation in Server Management Lifecycle Management for enterprise servers and applications Key Challenges: Long Cycles for provisioning, patching and implementing changes Lack of control caused by configuration drift (manual changes) Virtualized environments [AppCom (Dynamic Computing Platform at T-Systems), XenApp 5, Solaris Zoning, VMWare, ] Massive scale and complexity increasing errors, downtimes and costs HP Server Automation delivers: Server & Application Lifecycle Management Policy enforcement, Compliance Checks and Reports, vulnerability alerts Dependency Mapping across Applications using HP SA Network and storage (possible as soon as HP Network Automation and HP Storage essentials is implemented) Increased productivity and reduced costs 9

10 Project experiences with the Implementation of HP DataCenter Automation Agenda Motivation and Projektscope Architecture concept Utilization concepts especially in Software Management Situation and expected trends in 2009/

11 Information Flow between Main Processes product catalogue from manufacturer (signatures) order license management asset management actualization of CI input / guidelines for compliance configuration management CI compliance management verification & audit inventory data compliance report order request fulfillment "Golden Rules" data disjoint in tools whenever possible if conjoint data in tools cannot be avoided: definition of a "leading" tool data can only be created, changed and deleted in the leading tool other tools have real time and read only access to conjoint data no data replication between tools, exception: CMDB request fulfillment order release & deployment management order actualization of CI inventory data inventory order, order related data for report request fulfillment feedback order & report 11

12 How are we integrating BSA products Configuration, Reporting Control Event flow Customer Layer Customer Order System Contractdata Systems Locations AC Contracts Relations Systems and Contractdata 1 HP SA 5 Monitoring Events Incidents Business Information BISON Internal order system Systems 4 Hardware Inventory Monitoring HP OVO Contractdata INM SC 2 Customer CMDB Customer Reports System and Contractdata Hardware/ Software Inventory Order Mgmt Config Mgmt Software Mgmt Operations Incident Mgmt Reporting 3 12

13 HP SA - Integration Configuration Management (AC) und HP SA Systems Locations AC Contracts Relations Systems and Contractdata 1 HP SA control loop between HP Asset Center and HP SA. HP SA provides possibilities to setup information per server that are already used in Asset Center as the leading system. To avoid manually work and to keep this data identically there is to setup an interface from AC to HP SA The target software configuration of a server is considered as a set of configuration items (to-be data) The configuration which is deduced from orders related to the server is administrated within Asset Center and used to control the compliance within HP SA 13

14 HP SA - Integration Configuration Management (AC) und HP SA 14

15 HP SA - Capacity Reporting, Customer CMDB, internal needs Business Information AC HP SA BISON 4 2 System and Contractdata Customer CMDB Hardware Inventory 3 Hardware/ Software Inventory Installed Software, Policies an their relations to packages have to be presented to our customer via reports and via customer-oriented CMDB based on contractual requirements Presentation of some hardware information (especially file system data) to fulfill the requirements of Capacity Reporting To provide information on installed software products there is to setup a link to the customer-oriented CMDB A subset of inventory data collected by the HP SA Inventory is written back to Asset Center 15

16 HP SA - Integration Configuration Management (AC) und HP SA 16

17 HP SA Integration in Change und Configuration Management Analyses Customer Systems Installed Packages Inventory (e.g. Installed Packages) HP SAR Reference Configuration Asset Center Paketverwaltung Distribution and Installation HP SA Server CI, Reference Configuration Change Number and approval Change Management Change- Review Change- Planning Change- Implemen- tation RfC- Initializatio n RfC- Analysis Change- Approval 17

18 HP SA Monitoring Integration HP SA 5 Monitoring Events Monitoring via HP Operations Manager Unix to observe the health of the central HP SA infrastructure including SAS and SAR Monitori ng HP OVO INM SC Monitoring via HP Operations Manager Unix to observe the health of the agent components of HP SA on target systems Interface from HP OMU (OVO) to Service Center Incident Management Module 18

19 Audit & Compliance to support ITIL processes Audit&Compliance tool kit (inklusive workflow description) supports current ITIL-Processes. At the moment there are no plans to define explicite Audit&Compliance"- Processes or Organization units. 19

20 Project experiences with the Implementation of HP DataCenter Automation Agenda Motivation and Projektscope Architecture concept Utilization concepts especially in Software Management Situation and expected trends in 2009/

21 Software Management as a part of Release Management Process (ITIL) Change Management Release Management Planning The Release Management has to supply new releases of hardware and software products in our customer s production environment, including the planning and supply of new or changed software and hardware components, the quality assurance (QA) process as well as the planning, control and monitoring of rollouts. Supply QA Distribution & Installation Software Management Definitive Software Library Configuration Management Database Rolloutplanning & preparation Rolloutcontrol & monitoring Configuration Management The Software Management of T-Systems in the capacity of Release Management is responsible for the controlled and comprehensible distribution and installation of Software products or/and components according to Change Management specifications. The Software Management supports as well the supply and QA process for new software as well as the planning, control and monitoring of rollouts. The complete software is stored in the definitive software library. Information about the managed hardware- und software inventory is exchanged with the Configuration Management.

22 Achieving the goals with SA Functions needed to support Business Processes packaging deployment of software packages on server store in, distribute and installation/deinstallation of SW packages handling of dependencies handling of response files (Solaris) and support of MST files for Windows platforms scope of deployment and installation of software on server: applications, middleware products, systems management products, hardware related products, products related to operating system delta release, full release, package release (definition according to ITIL V3) major / minor release, emergency fix release (patch, hot fix) (definition according to ITIL V3) Windows, HP UX, Sun Solaris, LINUX, AIX,... support for virtual servers OS native packages (= MSI, MSP, PKG, SD, RPM files) deployment of software archives (e. g. tar files, zip files,...) and single files (e. g. configuration files, price lists,...) collecting of inventory information (hardware & software) and provision of data for SLA reporting

23 Requirements for Software Management for Servers functional requirements administration of policies definition of software items (software item := all components, e. g. packages, scripts, files,..., that are needed to install a versioned software product) definition of reference configurations (reference configuration := list of software items that describes to-be configuration for a specific platform, e. g. windows 2003 web sever / the corresponding ITIL term is "baseline configuration") administration of relationships between reference configurations and servers selection and grouping (static/dynamic) by different criteria, e. g. operation system platform / release / patch level software product software product version customer contract manual selection of servers (the content of a dynamic group is determined at the time of use) apply installation orders to groups

24 Requirements for Software Management for Servers functional requirements queries & reports to gather individual and predefined information, e. g. monitoring of installation orders (progress of successful installations) software & hardware inventory for software rollout planning Key Performance Indicators (KPIs) server can change their role (servers for test quality assurance production) installation on test servers will be done by T-Systems and by customer versioned packages once stored in cannot be changed afterwards multi client capability the solution must integrate with the T-Systems current environment T-Systems tool environment [HP OMU (OVO), Asset Center,...] Customer oriented tools (Customer oriented CMDB, Customer Reporting,...) migration of HP CA (Radia) services (resources and configuration) takeover of already installed software into HP SA control without reinstallation

25 Requirements for Software Management for Server nonfunctional requirements introducing definition of terms - leading time - path through time - reaction time leading time (overall) path through time path through time making package available for deployment path through time deployment path through time installation versioned package available incoming order start of publishing package available for deployment package available for installation package is installed make packages available deployment installation initiating installation max delay time start of installation

26 Non functional requirements for Software Management for Servers availability of software deployment 7 * 24 h 98 % exclusive maintenance windows for HP SA pass through time for making packages available for deployment software packages with a size equal or less than 50 MB have to be ready to deploy in all relevant environments within 2 hours after handover of software package on transfer share. in all other cases 2h+ data transfer time pass through time for deployment depends on network bandwidth and capacity of HP SA infrastructure pass through time for installation depends on installation procedure (out of project scope) maximum delay time the time from initiation (scheduled or direct) a installation in HP SA up to the actual beginning of the installation on the server is less than 5 min 26

27 Standardizing in Software Management Provisioning of binding rules and conventions Naming conventions Authorization and Role concept Packaging Guidelines Package protocols / Install Guides Userguide Test-concepts for Quality Assurance (test plans, test data, ) Central provisioning of templates and tools Templates for standardized Software Packaging (MSI/PKG/RPM/SD) Delivers: Fast and cost-efficient processes (Best Practice) and corporate standards Basis for continous process improvement Companywide unified standards for internal and external supplier and interfaces 27

28 Standardizing in Software Management Automation Release and Software Management Automation of the packages handover process Central handover share (SFTP) / transfer share for SW-packages to import in HP CA & HP SA Central Package Management system Contains information about all imported packages into HP CA and HP SA (e.g. the status in the lifecycle process like new, tested, QAed, productive) Auditing acceptability Package protocols with plausibilty checks against faulty insertions Interface between Package Management system and HP SA. This interface uses information stored in PV (based on the packages protocols) to load packages from the handover share into HP SA and create software policies for the packages. Delivers: Reduction of necessary manual interactions Reduction of sources of errors (human errors) Acceleration of Order Management Processes (time to market) 28

29 Project experiences with the Implementation of HP DataCenter Automation Agenda Motivation and Projektscope Architecture concept Utilization concepts especially in Software Management Situation and expected trends in 2009/

30 Situation and expected trends 2009/2010 Rollout of the HP SA Agent 7.02/7.5 (W2K8, HPUX 11.31) ongoing Migration of several Server Applications from HP CA (RADIA) to HP SA Update to HP SA 7.8 (Support Itanium) 4th quarter 2009 Lifecycle Management Automatic Provisioning of Test and Development Systems Sourcecode Management Use Cases for Global Shell Integration with RBA (Runbook Automation) HP OO (HP Operations Orchestration) Project already started Network Management (HP Network Automation) planned Storage Management (HP Storage Essentials) planned 30

31 Thank you for your attention. Questions? 31