rob zoeteweij customer case configuration management
TRANSCRIPT
CUSTOMER CASE
CONFIGURATION MANAGEMENT
PROVISIONING & AUTOMATED PATCHING
Rob Zoeteweij
Agenda
• Case introduction
• Configuration Management
• Provisioning & Automated Patching
• Finally
• Q & A
Case introduction
• Too many incidents related to Configuration changes
– OS, Database / App Server Parameter changes
• Not sure what we have got
– What Database releases?
– What Patches have been applied?
• Not sure about compliancy
– Database Standards
• Configuration of the Database
• Security
– Where to improve?
Case introduction
• Any direct threads?
– Are there any known issues that might relate to one of our
databases and is a fix available?
Case introduction
• High demand for:
– Standardization
– Task automation
– Reduction of complexity
– Reduction of costs
– Improvement of Time to Market
• It takes too long to startup projects
• Configuration of Clusters, Databases, Application Servers
Case introduction
• Customer choice was implementation of:
– OEM GC – including:
• Configuration Management Pack
• Provisioning and Automated Patching Pack
Agenda
• Case introduction
• Configuration Management
• Provisioning & Automated Patching
• Finally
• Q & A
Configuration Management Pack
• Based on CMDB
(Configuration Management Database)
– SYSMAN schema
– Implicitly available after installation of OEM GC
– After discovery of Targets (Databases, Servers, Application
Servers, Listeners, Clusters, ASM, Hardware, Storage, etc.)
• Analytics & Reports
• Change detection
• Compliancy assessments
Configuration Management Pack
Configuration Management Pack
• Saved Configuration
– Take a “Picture” of current Configuration
– To be used as:
• Blueprint
• Baselines
– Base for detecting Configuration drifting
Configuration Management Pack
• Comparing Configurations
– One Configuration with another
– One Configuration with several others (Job)
Configuration Management Pack
Configuration Management Pack
• Compliancy
– SOX, Basel 2, etc.
– Company Security Rules
– Standards
– Categorized
• Configuration
• Storage
• Security
Configuration Management Pack
Configuration Management Pack
• Complete control on:
– all Configurations
– Licenses
– Changes
– History
• Compliancy
– Company Rules
– The Hague, Brussels, Dutch Bank
• Need for Role in Organization
– Weekly check of any Configuration Drift
– 15 minutes a week
Agenda
• Case introduction
• Configuration Management
• Provisioning & Automated Patching
• Finally
• Q & A
System LifecycleInstall Software
Patch
Configure
Monitor
Administer
Remove
Virtual
Machines
Operating
System
Databases
Middleware
Applications
Installing the software with OEM
Create Reference
System
Stage as Golden
Image in
Software Library
Deploy
Production
System
Patch Software with OEMStage Patch in
Software LibraryDownload
PatchDeploy on
multiple Systems
Configuring Systems with OEM
Identify
Systems
Create
Directives
and
Components
Deploy
Configuration
Stage in
Software Library
Software Library
Software Library
Directives
Scripts (Perl or Bash)
to be executed on the
target
Components
All kind of files
that can be used
by a directive
Deployment Procedures
Orchestration of Directives
and Components
Provisioning and Automated Patching
• Customer Case
– Provisioning of
• Operating System – Bare Metal Provisioning
• Cluster infrastructure
– Multiple Node Clusters
– Software installation and Cluster configuration
• ASM
– Software installation and ASM Instance creation on
each Node
• DB
– Software installation on each Node
• Creation of Cluster Database (RAC) – 1 – 3 Instances
Provisioning and Automated Patching
• Software Library
– Golden Images
• OS
• Oracle Software
– Cluster Infrastructure
– ASM Software
– DB Software
• Etc.
– Network specifications
– Etc.
Provisioning and Automated Patching
• Customer Case
– Oracle Clusterware / RAC Provisioning For UNIX
Provisioning and Automated Patching
Clusterware / RAC
Clusterware
ASM Software
Database Software
Shared Storage
Cluster
Configuration
ASM Instance
creation
(Optional)
Database
creation
(Optional)
Installed:- Clusterware
- ASM Software
- DB Software
Software Library
Provisioning and Automated Patching
• Customer Case
– Extending the Cluster
Provisioning and Automated Patching
Extending the Cluster
Clusterware
ASM Software
Database Software
Shared Storage
Installed:- Clusterware
- ASM Software
- DB Software
Cluster
Re-configuration
ASM Instance
creationDatabase
Instance
creationSoftware Library
Provisioning and Automated Patching
• WRAP UP
– Full configuration of Oracle Database Cluster
• Clusterware – ASM – DB
• ASM – Instance creation / DB Creation
– Fully operational
– Customers’ Project shows:
• Provisioning of a 3 node Cluster in only 2 hours
– OEL 5, CRS 11.1.0.7, ASM 11.1.0.7, DB 11.1.0.7
– HP Blade Servers
• Instead of several days
• Based on Best Practice (Oracle / Customer)
• Standardized
• Fully compliant to Customer rules
– Security (European Law, Dutch Law, Dutch National
Bank)
Provisioning and Automated Patching
• Patching as part of Release Management
• 4 / Year – CPU
– 4 x 400 DB x 1 hr = 1600 hrs per year (manually)
– 4 x 400 DB x 00:10 hr = 266 hrs per year (OEM GC)
• Patching thousands as one
• Based on connection between OMS and
updates.oracle.com
– Via Company proxy
• Patch advisories
• Patches downloaded in Patch Cache (Software
Library)
Provisioning and Automated Patching
Agenda
• Case introduction
• Configuration Management
• Provisioning & Automated Patching
• Finally
• Q & A
Finally
• http://otn.oracle.com
• Linkedin Groups:
– http://www.linkedin.com/groups?gid=1776007&trk=
hb_side_g
– http://www.linkedin.com/groups?gid=2688744&trk=
hb_side_g
• http://oemgc.wordpress.com
Q & A