OEM Provisioning Concepts and Example

Transcription

1 OEM Provisioning Concepts and Example Rob Zoeteweij Zoeteweij Consulting The Provisioning and Patch Automation Pack automates the deployment of software, applications, and patches. This paper will focus on the concepts and give an example of how to do your own customization on "Out of the Box" Deployment Procedures. Concepts When talking about the OEM "Provisioning and Patch Automation" Pack we are actually talking about the opportunity to: Reduce complexity Instead of having a DBA performing written instructions to perform tasks like database creation, cluster configuration etc., the DBA now can execute an intuitive wizard that will guide him/her through the whole process of... (database creation, cluster configuration etc.). By this reduction of complexity is highly reduced. Reduce costs Because of the fact that many daily tasks are automated and simple wizard guided, organizations will be able to assign these tasks to less expensive DBO's (Database Operators) instead of highly trained expensive DBA's. Shorten Time to Market Because time consuming tasks like cluster configuration can now be performed as an automated task, Time to Market is dramatically shortened (for example the configuration of a 3 node Linux Cluster with CRS, ASM (+ ASM instance creation) and DB, might be performed in 2-3 hours instead of several days). Achieve a high level of standardization As the provisioning of clusters, databases etc. is automated in deployment procedures, execution of each of these procedures is performed exactly the same way time after time. By this each created database or configured cluster will meet the same company standards. Software Library As the center of the Provisioning and Patch Automation Pack, OEM includes the software library that contains all components necessary to support the deployment procedures. The software library resides partially within the OEM repository database and partially on the OMS file system. When multiple OMS servers are used, a shared file system is needed to be used.

2 Software library in the repository database As part of the software library, the repository contains several MGMT_PAF_... and MGMT_SWLIB_... tables. Figure 1 MGMT_PAF tables in repository database Figure 2 MGMT_SWLIB tables in repository Software library on OMS file system As part of the software library a specific formatted file system is created on the OMS file system. If multiple OMS servers are used, this file system must be a shared file system. This to make all components available.

3 Figure 3 OMS file system As the figure shows, the directories created are named numeric and even the directory contents contain hexadecimal naming, which makes it impossible to relate to a named component within for instance the OEM console. The software library directories are located on a file system and configured through the OEM "Provisioning Administration" page. Software library in the OEM console Within the OEM console the software library is presented as a page divided in several tabs:

4 Figure 4 Software library presented in OEM console Tab Page Contents Purpose Components Files Deployment procedures Golden images Baselines (Ingredients) Directives Logic Deployment procedures o Scripts - Shell, Perl What to do with... (Recipes) Networks Network definitions Bare Metal Provisioning Images Bundle of Components, Directives Bare Metal Provisioning Suites Collection of heterogeneous components grouped together Bare Metal Provisioning Example: Oracle Collaboration Suite (database, application server, web server, identity server) Suite Instances Group of hardware servers that will run each of these suites Bare Metal Provisioning Assignments Provisioning of an image or a suite of Bare Metal Provisioning images on a server Hardware Hardware specification Bare Metal Provisioning Cluster Specification of hardware servers in a cluster Bare Metal Provisioning Administration Configuration of software library Configuration of software library Before starting to work with the Provisioning and Automated Patching Pack, the Administration tab needs to be completed to configure the software library.

5 Framework The framework of the Provisioning and Automated Patching Pack is based on the software library and the OEM deployment procedures. Figure 5 Provisioning framework Deployment procedures are constructed out of components and directives, both included in the software library. Each deployment procedure consists out of multiple procedure steps and each of the steps are related to a specific error logic. This error logic defines what to do in case of an error occurs: Stop on error Continue on error Skip target This is how a deployment procedure looks like in the OEM console:

6 Figure 6 Example of deployment procedure in OEM console As this figure shows, each deployment procedure consists out of procedure steps, that have a Name, a Type, a Description, a Run Privilege and am Error Handling Mode. Two different types of deployment procedures There are two different types of deployment procedures: Type 1 Based on RAC Provisioning Procedures This type of procedure includes a static GUI. If you create a new procedure based on this type, you will not have any control on what the GUI will look like. Therefore it is not a good idea to base a custom deployment procedure on this type. Type 2 Based on Database Patching Procedure This type of procedure includes a more flexible GUI. If you create a new procedure based on this type, you will have control on what the GUI will look like. Therefore this type of deployment procedure is suitable to base custom deployment procedures on. Type 1 Based on RAC Provisioning Procedures This type of procedure includes a status GUI, which means that if you create a new procedure based on this type, you will not have any control on what the GUI will look

7 like. Therefore it is not a good idea to base custom deployment procedures on this type. Type 2 Based on Database Patching Procedure This type of procedure includes a more flexible GUI, which means that that if you create a new procedure based on this type, you will have control on what the GUI will look like. Out of the box procedures Before discussing the customization of procedures it is now time to take a look at the deployment procedures that are included "Out of the Box". OEM GRID Control includes several "Out of the Box" deployment procedures: Database provisioning Application Server provisioning RAC Provisioning Patching Figure 7 OEM Deployment Procedure Manager Figure 8 RAC Provisioning procedures Overview of "Out of the box" procedures AS Provisioning 4

8 RAC Provisioning 4 Patching Solaris Hosts 1 Patching Windows Hosts 1 Patching Linux Hosts -1 Patch Pre-Requisites 4 BPEL Process Provisioning 1 Linux Staging Server Setup 1 Database Provisioning 2 Forms and Reports Provisioning 1 Coherence Node Provisioning 1 Patch Oracle Software 6 Virtualization Provisioning 11 Oracle Service Bus Resource Provisioning 1 Working with the Out of the Box procedures When starting to work with the "Provisioning and Automated Patching" it makes sense to starting testing with the procedures that were delivered by Oracle as part of the OEM product. After testing the "Out of the Box" procedures, you might want to start customizing them to make sure they fully comprise to you requirements. Customization therefore is necessary. Customization Let's assume the following use case: Setup of a cluster: Based on best practice the Operating System needs to be installed on the available hardware and the Management Agent should be installed to make the cluster visible within the OEM console. Setup of Oracle Software: The CRS software will be installed and configured, OCR and Voting Disk will be created based on all nodes that are included. The ASM software will be installed on each of the cluster nodes and an ASM instance needs to be created on each of the cluster nodes. The Database software will be installed on each of the cluster nodes. Creation of RAC Database A RAC database should be created using TCP/IP port 39000, using a at runtime specified Diskgroup within the ASM instance. After the database is created, the following actions should be performed: o Application of the most recent CPU (Critical Patch Update) o Company specific settings should be applied o Several standard RAC Services should be created o The database needs to be registered within OEM

9 o The database needs to be registered within the OID o Privilege for the database should be assigned to administrators via a role o Monitoring templates needs to be applied (< ) o Configuration of the TMS needs to be performed to be able to run backups o A first backup of the database needs to be performed Problems when running the "Out of the Box" procedure "Oracle Clusterware / RAC Provisioning" This procedure does include the creation of a database but: A RAC Database with an Instance on each Node will be created The created database will listen to port 1521 and the use case requires port The use case requires the possibility to enter the Diskgroup to be used Etc. The solution to this problem is: To modify the "Out of the Box" procedure "Oracle Clusterware / RAC Provisioning" so that the procedure will only perform the roll out of CRS software (+ configuration), ASM software (+ ASM instance creation) and the DB software. To create a custom procedure that will take care of the database creation and meet all requirements as described in the use case.

10 Kontaktadresse: Name Rob Zoeteweij Zoeteweij Consulting Lijndonk XG Oosterhout Netherlands Telefon: +31(0) Fax: Internet: