EMC ENTERPRISE HYBRID CLOUD 2.5.1, FEDERATION SOFTWARE-DEFINED DATA CENTER EDITION: DEPLOYING ORACLE DATABASE AS A SERVICE

(1)

White Paper

EMC Solutions

Abstract

This white paper describes how to use the EMC Enterprise Hybrid Cloud architecture with the VMware vCloud Suite, EMC hardware, software, and services portfolio to provision and manage your Oracle Database as a Service offerings.

February 2015

EMC ENTERPRISE HYBRID CLOUD 2.5.1,

FEDERATION SOFTWARE-DEFINED DATA

CENTER EDITION: DEPLOYING ORACLE

DATABASE AS A SERVICE

EMC Enterprise Hybrid Cloud 2.5.1 with VMware, VMware vCloud

Application Services



Optimized self-service provisioning of Oracle Database

(2)

Copyright © 2014, 2015 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

(3)

3 EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition:

Deploying Oracle Database as a Service

Executive summary

This white paper describes how to use the EMC Enterprise Hybrid Cloud architecture with the VMware vCloud Suite, EMC hardware, software, and services portfolio to provision and manage Oracle Database as a Service (DBaaS) offerings.

EMC Enterprise Hybrid Cloud enables IT organizations to quickly deploy an on-premises private cloud or hybrid cloud that delivers infrastructure as a service (IaaS) to their business. EMC Enterprise Hybrid Cloud delivers IaaS to VMware vCloud Automation Center Application Services via VMware vCloud Automation Center. The following documents describe the reference architecture and the foundation solution on which all EMC Enterprise Hybrid Cloud add-on solutions are built:

 EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Reference Architecture

 EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Solution Guide

The following guides provide further information about how to implement specific capabilities or enable specific use cases within the EMC Enterprise Hybrid Cloud solution:

 EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Data Protection Continuous Availability Solution Guide

 EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Data Protection Backup Solution Guide

 EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Data Protection Disaster Recovery Solution Guide

 EMC Enterprise Hybrid Cloud 2.5 with VMware: Hadoop Applications Solution Guide

 EMC Enterprise Hybrid Cloud 2.5 with VMware: Pivotal CF Platform as a Service Solution Guide

 EMC Enterprise Hybrid Cloud 2.5 with VMware: Security Management Solution Guide

 EMC Enterprise Hybrid Cloud 2.5 with VMware: Public Cloud Solution Guide Each of these documents includes an overview of the EMC Enterprise Hybrid Cloud solution architecture and key components, and the validated hardware and software environment. In addition, the Foundation Infrastructure Solution Guide acts as an enablement reference to begin the planning and design of your hybrid cloud and to prepare for a successful implementation.

This document is intended for executives, managers, architects, cloud

administrators, system administrators, database administrators, and developers who want to implement a hybrid cloud IaaS platform and specifically want to deploy Document purpose

(6)

Oracle DBaaS. Readers should be familiar with the VMware vCloud Suite, storage technologies, general IT functions and requirements, and how a hybrid cloud infrastructure accommodates these technologies and requirements.

EMC Enterprise Hybrid Cloud enables EMC customers to build an enterprise-class, scalable, multitenant infrastructure that enables:

 Complete management of the infrastructure service lifecycle

 On-demand access to and control of network bandwidth, servers, storage, and security

 Provisioning, monitoring, and management of the infrastructure services by the line-of-business end users, without IT administrator involvement

 Maximum asset utilization

 Access to application services, such as Oracle DBaaS, from a single platform for both business-critical and next-generation cloud applications

This solution provides a basis for deploying Oracle DBaaS on EMC Enterprise Hybrid Cloud and references the architecture and best practice guidance necessary, as shown in Figure 1.

Figure 1. EMC Enterprise Hybrid Cloud solution stack

Business applications are becoming more integrated into a consolidated compute, network, and storage environment. Business leaders are looking to address the following fundamental challenges:

Solution purpose

Business challenge

(7)

Deploying Oracle Database as a Service While many organizations have successfully introduced virtualization as a core technology within their data centers, the benefits of virtualization have largely been restricted to the IT infrastructure owners. End users, application developers, database administrators (DBAs), and business units within customer organizations have not yet fully experienced many of the benefits of virtualization, such as increased agility, mobility, and control.

Transforming from the traditional IT model to an IaaS model involves overcoming the challenges of legacy infrastructure and processes, such as:

 Inefficiency and inflexibility

 Slow, reactive responses to customer requests

 Inadequate visibility of the requested infrastructure cost

 Limited choice of availability and protection services

The difficulty in overcoming these challenges has given rise to public cloud providers who have built technology and business models specifically catering to the

requirements of end-user agility and control. Many organizations are under pressure to provide these same service levels within the secure and compliant confines of the on-premises data center. As a result, IT departments need to create cost-effective alternatives to public cloud services that do not compromise enterprise features such as data protection, disaster recovery (DR), and guaranteed service levels.

These organizations must also manage a growing and fragmented database

infrastructure. As well as supporting an increased number of production databases, DBA and development teams require multiple database environments to meet business needs such as developing and testing application features, reporting, and application troubleshooting.

Traditional virtualized environments, while improving provisioning times compared to physical environments, have not delivered a mechanism to self-manage the

application development lifecycle using the IaaS model.

As IT organizations implement a hybrid cloud, they must consider the following factors:

 The infrastructure must be quick to deploy so that business value can be recognized quickly.

 The hybrid cloud infrastructure and operations must be designed to reduce costs through higher utilization and higher staff productivity.

 Risk of downtime must be controlled through disciplined change control and careful management of component compatibility.

 Support agreements must be established for all elements of the solution.

 Software license compliance must be managed during Oracle DBaaS deployment.

The EMC Enterprise Hybrid Cloud solution integrates the best of EMC and VMware products and services. The solution empowers IT organizations to accelerate

implementation and adoption of a hybrid cloud while still enabling customer choice Technology

(8)

for the compute and networking infrastructure within the data center. The solution caters to customers who want to preserve their investment and make better use of their existing infrastructure as well as to customers who want to build out new infrastructures dedicated to a hybrid cloud.

The EMC Enterprise Hybrid Cloud solution, developed by the EMC and VMware product and services teams, takes advantage of the strong integration between EMC technologies and the VMware vCloud Suite. The solution includes EMC scalable storage arrays, integrated EMC and VMware monitoring, and data protection suites to provide a foundation for cloud services within customer environments.

This solution adds vCloud Automation Center Application Services to the EMC Enterprise Hybrid Cloud foundation architecture to enable automated deployment and management of Oracle DBaaS.

EMC Enterprise Hybrid Cloud is designed to deliver multitenancy and secure

separation of resources required in a cloud environment. Cloud computing requires the ability to isolate resources and deliver secure access. EMC Enterprise Hybrid Cloud is structured so that each tenant can be:

 Logically separated using vCloud Automation Center business groups. In this solution, the Oracle business group is assigned dedicated compute, storage, and network resources for software license compliance.

 Physically separated in a dedicated “resource pod.” In this solution, Oracle is restricted to a dedicated vSphere High Availability (HA)/Distributed Resource Scheduler (DRS) cluster with its own servers, network, and storage resources, separate from all other tenants.

These dedicated, physically separated tenant cluster resource pods are mapped to the compute resource available to the vCloud Automation Center business group. This improves service availability, and it ensures software license compliance by restricting where the virtual machines and software are running or installed.

VMware vCenter Orchestrator integrates with vCloud Automation Center and enables process automation when interfacing with third-party systems during machine provisioning. For this solution, when a Linux virtual machine is provisioned or destroyed, corresponding DNS records are added or deleted.

Using vCloud Automation Center Application Servicesaccelerates and automates the deployment of Oracle DBaaS for both business units and developers. Combined with vCloud Automation Center and vCenter Orchestrator, Application Services delivers a self-service lifecycle management framework to provide a secure, controlled, customizable, and repeatable process for the database service user.

Many Day 2 operations, such as changing vCPU, adjusting the size of memory, or allocating storage, can be managed using standard vCloud Automation Center functionality.

(9)

Deploying Oracle Database as a Service These actions may be scheduled or set to run immediately. Further, if vCloud

Automation Center optional approval policies are applied to an action, a task will not be executed until it is authorized.

vCenter Orchestrator workflows can be deployed as custom actions using the vCloud Automation Center Advanced Service menu. Like standard vCloud Automation Center actions, these custom actions can be requested, executed, or scheduled and are subject to the same approval policies.

Adding vCPU or memory using the standard vCloud Automation Center Edit action requires the virtual machine to be stopped and restarted. For this solution, to meet the elasticity and availability requirements of virtual machines during Day 2

operations, vCenter Orchestrator workflows were developed to hot-add vCPU without rebooting.

The addition of vCloud Automation Center Application Services to the EMC Enterprise Hybrid Cloud framework provides the database and development teams the ability to:

 Utilize a reusable repository of services, databases, and applications that use standard configuration properties to meet strict requirements for IT compliance.

 Deploy and promote the same application blueprint to and between different cloud providers and target virtual machine template configurations.

 Use existing SQL, shell scripting, and coding skills when building out complex application blueprints for deployment.

 Model virtual machine templates, services, and application components such as scripts, objects, and binaries. This is particularly useful for application architects and designers who can build deployment blueprints with a drag-and-drop interface to combine services and automate deployments of multitier applications.

(10)

Table 1 lists terminology used in this white paper. Table 1. Terminology

Term Definition

Application blueprint In vCloud Automation Center Application Services, a logical topology of an application for deployment. A blueprint captures the structure of an application with logical nodes, their corresponding services and operating systems, dependencies, default configurations, and network and storage topology requirements.

Business group A set of users, often corresponding to a line of business, department, or other organizational unit, that can be associated with a set of catalog services and infrastructure resources.

Cloud provider In vCloud Automation Center Application Services, a cloud instance for deployment. In this case, the cloud provider is a vCloud Automation Center business group.

Deployment profile In vCloud Automation Center Application Services, a collection of deployment settings for an application blueprint, including cluster size, CPU, memory, cloud templates, and networks.

Fabric group A collection of virtualization resources, compute resources, and cloud endpoints that is managed by one or more fabric administrators.

Logical template In vCloud Automation Center Application Services, a predefined virtual machine. A logical template can be mapped to a cloud template in the cloud catalog and supported services. Logical templates enable an application blueprint to remain cloud agnostic. vCloud Automation Center

Application Services service

Scripted software that can be installed on a virtual machine and reused in multiple applications.

vCloud Automation Center blueprint

A specification for a virtual, cloud, or physical machine that is published as a catalog item in the common service catalog.

vCloud Automation Center

Service Catalog A library that contains logical templates, which are pointers to cloud templates.

(11)

EMC Enterprise Hybrid Cloud solution overview

EMC Enterprise Hybrid Cloud is an engineered solution that offers IT organizations, developers, end users, and line-of-business owners a simplified approach to IT functionality. In addition to delivering baseline IaaS built on a software-defined data center architecture, the EMC Enterprise Hybrid Cloud delivers feature-rich capabilities to expand from IaaS to business-enabling IT as a service (ITaaS). Backup as a service (BaaS) and disaster recovery as a service (DRaaS) policies can be enabled with just a few clicks. End users and developers can quickly access a marketplace of resources for Microsoft, Oracle, SAP, EMC Syncplicity®_{, and Pivotal applications, and can add} third-party packages as required. Resources can be deployed on private cloud or EMC-powered public cloud services, including VMware vCloud Air.

The EMC Enterprise Hybrid Cloud solution uses the best of EMC and VMware products and services, and takes advantage of the strong integration between EMC and

VMware technologies to provide the foundation for enabling IaaS on new and existing infrastructure for the hybrid cloud.

The EMC Enterprise Hybrid Cloud solution includes the following features and functionality:

 Self-service and automation

 Multitenancy and secure separation

 Workload-optimized storage

 Security and compliance

 Monitoring and service assurance

 Modular add-on components

Figure 2 shows the key components of the EMC Enterprise Hybrid Cloud solution. For detailed information, refer to EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Solution Guide. For an

overview of EMC Enterprise Hybrid Cloud modular add-on components, which provide functionality such as continuous availability, platform as a service, and disaster recovery, refer to Modular add-on components on page 16.

(12)

Figure 2. EMC Enterprise Hybrid Cloud key components

The solution provides self-service provisioning of automated cloud services to both users and infrastructure administrators. It uses vCloud Automation Center, integrated with EMC ViPR®_{software-defined storage and VMware vCloud Networking and}

Security or VMware NSX, to provide the compute, storage, network, and security virtualization platforms for the software-defined data center (SDDC). These platforms enable you to rapidly deploy and provision business-relevant cloud services across your hybrid cloud and physical infrastructure.

Cloud users can request and manage their own applications and compute resources within established operational policies. This can reduce IT service delivery times from days or weeks to minutes. Automation and self-service provisioning features include:

 Self-service portals—Provide a cross-cloud storefront that delivers a catalog of custom-defined services for provisioning workloads based on business and IT policies, as shown in Figure 3

 Role-based entitlements—Ensure that the self-service portal presents only the virtual machine, application, or service blueprints appropriate to a user’s role within the business

 Resource reservations—Allocate resources for use by a specific group and ensure that those resources are inaccessible to other groups

 Service levels—Define the amount and types of resources that a particular service can receive during initial provisioning or as part of configuration changes

 Blueprints—Contain the build specifications and automation policies that define the process for building or reconfiguring compute resources Self-service and

(13)

Deploying Oracle Database as a Service Figure 3. Self-service provisioning through the vCloud Automation Center portal

Multitenancy requirements in a cloud environment can range from shared, open resources to completely isolated resources, depending on the organization’s end-user requirements. The EMC Enterprise Hybrid Cloud solution provides the ability to enforce physical and virtual separation for multitenancy, offering different levels of security to meet business requirements. This separation can encompass network, compute, and storage resources, to ensure appropriate security and performance for each tenant.

The solution supports secure multitenancy through vCloud Automation Center role-based access control (RBAC), which enables vCloud Automation Center roles to be mapped to Microsoft Active Directory groups. vCloud Automation Center uses existing and appropriate authentication and business groupings. The self-service portal shows only the appropriate views, functions, and operations to the cloud user, based on the user’s role within the business. Further physical resource separation can be used in vCloud Automation Center to isolate tenant resources and contain compute resources for licensing purposes.

The EMC Enterprise Hybrid Cloud solution enables you to take advantage of the proven benefits of EMC storage in a hybrid cloud environment. Using EMC ViPR storage services and the capabilities of EMC VNX®_{, EMC VMAX}®_{, and EMC XtremIO™} storage arrays, the solution enables you to manage the policies of software-defined block- and file-based virtual storage.

With scalable storage architectures that use the latest flash and tiering technologies, VNX, VMAX, and XtremIO storage arrays enable you to meet any workload

requirements with maximum efficiency, performance, and cost-effectiveness. ViPR abstracts the storage configuration and presents it as a single storage control point. This enables cloud administrators to access all heterogeneous storage resources within a data center as if they were a single large array.

Multitenancy and secure separation

(14)

As a result, storage administrators can maintain control of their storage resources and policies while cloud administrators can automatically provision storage resources into the cloud infrastructure.

The EMC Enterprise Hybrid Cloud solution enables you to enhance security by establishing a hardened security baseline across the hardware and software stacks supporting your hybrid cloud infrastructure. The solution helps to reduce concerns around the complexities of the underlying infrastructure. The solution demonstrates how to tightly integrate an as-a-service solution stack with public key infrastructure (PKI) and a common authentication directory to provide centralized administration and tighter control over security.

The solution addresses the challenges of securing authentication and configuration management to aid compliance with industry and regulatory standards by:

 Securing the infrastructure by integrating with a PKI to provide authenticity, non-repudiation, and encryption

 Converging the various authentication sources into a single directory to enable a centralized point of administration and policy enforcement

 Using configuration management tools to generate infrastructure reports for audit and compliance purposes

In addition, you can use NSX for vSphere in the EMC Enterprise Hybrid Cloud solution to enable a richer networking and security feature set than that provided by

traditional solutions. VMware NSX for vSphere describes the enhanced networking and security features in NSX.

The EMC Enterprise Hybrid Cloud solution features automated monitoring and

management capabilities that provide IT administrators with a comprehensive view of the cloud environment to enable intelligent decision making for resource provisioning and allocation. These automated capabilities are based on a combination of EMC ViPR Storage Resource Management (ViPR SRM), VMware vCenter Log Insight, and VMware vCenter Operations Manager and use EMC plug-ins for ViPR, VNX, VMAX, and XtremIO to provide extensive additional storage detail.

You can create customized dashboards to provide at-a-glance views of application availability and utilization. This enables application teams to fine-tune applications to guarantee service levels across the various business groups configured on EMC Enterprise Hybrid Cloud. You can configure email notifications to ensure that the appropriate application teams are notified in the event of a key performance indicator (KPI) or threshold breach.

Cloud administrators can use ViPR SRM to understand and manage the impact that storage has on their applications and to view their storage topologies from

application to disk, as shown in Figure 4. Security and

compliance

Monitoring and service assurance

(15)

Deploying Oracle Database as a Service Figure 4. EMC ViPR Analytics with VMware vCenter Operations Manager

Capacity analytics and what-if scenarios in VMware vCenter Operations Manager identify over-provisioned resources so they can be correctly sized for the most efficient use of virtualized resources. In addition, for centralized logging,

infrastructure components can be configured to forward their logs to vCenter Log Insight, which aggregates logs from different sources for analytics and reporting. For this Oracle DBaaS solution, the service user has the option of using a stand-alone monitoring solution for the Oracle Database environment or installing the Oracle Enterprise Manager (OEM) Management Agent and registering the host, database, and listener with OEM Cloud Control 12c. Table 2 shows these monitoring options. Table 2. Oracle Database environment monitoring options

Database version Stand-alone Monitoring

Oracle Database 11g Y OEM Database Control on host

Oracle Database 12c Y OEM Database Express (EM Express) on host

Oracle Database 11g/12c N OEM Cloud Control 12c via Management Agent on host

(16)

The EMC Enterprise Hybrid Cloud solution provides modular add-on components for the following services:

 Application services

This add-on solution uses vCloud Automation Center Application Services to optimize application deployment and release management through logical application blueprints in vCloud Automation Center. Users can quickly and easily deploy blueprints for applications and databases such as Microsoft Exchange, Microsoft SQL Server, Microsoft SharePoint, Oracle, SAP, and Cloud Foundry.

 Data protection: Backup

EMC Avamar®_{and EMC Data Domain}®_{systems provide a backup infrastructure} that offers features such as deduplication, compression, and VMware

integration. By using vCenter Orchestrator workflows customized by EMC, administrators can quickly and easily set up multitier data protection policies that users can assign when they provision their virtual machines.

 Data protection: Continuous availability

A combination of EMC VPLEX®_{virtual storage and VMware vSphere HA provides} the ability to federate information across multiple data centers over

synchronous distances. With virtual storage and virtual servers working together over distance, the infrastructure can transparently provide load balancing, realtime remote data access, and improved application protection.

 Data protection: Disaster recovery

This component enables cloud administrators to select DR protection for their applications and virtual machines when they provision their hybrid cloud environment. ViPR automatically places these systems on storage that is protected remotely by EMC RecoverPoint®_{continuous data protection. VMware} vCenter Site Recovery Manager automates the recovery of all virtual storage and virtual machines.

 Platform as a service

The EMC Enterprise Hybrid Cloud solution provides an elastic and scalable IaaS foundation for platform-as-a-service (PaaS) and software-as-a-service (SaaS) services. Pivotal CF provides a highly available platform that enables

application owners to easily deliver and manage applications over the

application lifecycle. The EMC Enterprise Hybrid Cloud service offerings enable PaaS administrators to easily provision compute and storage resources on demand to support scalability and growth in their Pivotal CF enterprise PaaS environments.

Modular add-on components

(17)

 Public cloud services

The EMC Enterprise Hybrid Cloud solution enables IT organizations to broker public cloud services. The public cloud solution has been validated with vCloud Air as a public cloud option that can be accessed directly from the solution's self-service portal by administrators and users. End users can provision virtual machines while IT administrators can use VMware vCloud Connector to perform virtual machine migration (offline) to vCloud Air from the on-premises

component of their hybrid cloud.

For further details about the EMC Enterprise Hybrid Cloud 2.5.1 modular add-on components and packages, contact your account representative.

(18)

Provisioning Oracle DBaaS on EMC Enterprise Hybrid Cloud

This section describes the structure and software requirements of EMC Enterprise Hybrid Cloud and the Oracle DBaaS solution we built on top of the structure.

This Oracle DBaaS solution has been built and validated on a number of iterations and configurations of the EMC Enterprise Hybrid Cloud solution. The underlying physical environment is abstracted from the application layer by virtual and software-defined components. Figure 5 is representative of EMC Enterprise Hybrid Cloud environments where vCloud Automation Center Application Services was deployed. Overview

EMC Enterprise Hybrid Cloud structure

(19)

Deploying Oracle Database as a Service vCloud Automation Center Application Services enables you to construct application blueprints that enable customers to quickly deploy Oracle DBaaS applications on an EMC Enterprise Hybrid Cloud. vCloud Automation Center Application Services blueprints are created and then published to vCloud Automation Center. These published blueprints contain virtual machine deployment information, as well as any application deployments and ancillary scripts for deploying services (OEM agents, for example) to a virtual machine.

Virtual machine and application blueprints can apply to single systems or multiple systems, covering both bare-metal server deployments and virtual machine

deployments. From predefined blueprints, you can easily deploy multitier enterprise applications requiring multiple application, database, and web components, and related services.

vCloud Automation Center Application Services integrates directly with vCloud Automation Center. It uses business groups configured in vCloud Automation Center and vCloud Automation Center authentication providers, that is, Active Directory through single sign-on. When vCloud Automation Center is registered with vCloud Automation Center Application Services, the business groups are synchronized. In this solution, the vCloud Automation Center business group called Oracle-Business-Group is registered as the vCloud Automation Center Application Services cloud provider, as shown in Figure 6.

Figure 6. vCloud Automation Center business group registered as vCloud Automation Center Application Servicescloud provider

(20)

Each application team—the Oracle team, for example—uses a vCloud Automation Center Application Services cloud provider with a dedicated business group. This means that all instances of that application service will be deployed within that same business group. Therefore, all instances of Oracle DBaaS will be deployed in the Oracle business group in vCloud Automation Center. Therefore, in addition, the primary users of the business group are the application owners who are responsible for the application deployment design in vCloud Automation Center Application Services, as well as the deployment of the application through vCloud Automation Center.

Specific users within actual business units, such as Finance and Human Resources, are given permission to request service deployments in vCloud Automation Center. The requests are then approved or denied by the application owners.

For this solution, the Tenant Resource Pod used by the Oracle business group is a dedicated vSphere ESXi HA cluster with its own compute, storage, and network resources, which improves service availability. Software license compliance is ensured by restricting where the virtual machines and software are running or installed.

The vCloud Automation Center Service Catalog shows only the appropriate Oracle Database services published from vCloud Automation Center Application Services. In addition, it gives end users access only to operations appropriate to their role within the business.

For this solution, an NFS share is used to serve the Oracle Database binaries and any custom scripts or component files required. In different EMC Enterprise Hybrid Cloud environments, this NFS share has been provided by:

 A virtual machine within the Oracle Tenant Resource Pod

 EMC Isilon®_{scale-out NAS storage}

 EMC VNX unified storage

Figure 7 shows the core EMC Enterprise Hybrid Cloud components and, for this solution, the vCloud Automation Center Application Serviceslayer, which integrates with vCloud Automation Center, enabling Oracle DBaaS. It also shows the optional OEM Cloud Control, external to the solution, which can be used for managing and monitoring the Oracle Database.

(21)

Deploying Oracle Database as a Service Figure 7. EMC Enterprise Hybrid Cloud key components with vCloud Automation Center

Application Services for Oracle DBaaS

For this solution, we concentrate on the Oracle DBaaS solution and its key touch points in the EMC Enterprise Hybrid Cloud. For a full description of the key

components of EMC Enterprise Hybrid Cloud, refer to EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Solution Guide.

Table 3 lists the EMC Enterprise Hybrid Cloud software specific to the Oracle DBaaS solution.

Note: For a list of all EMC Enterprise Hybrid Cloud software requirements, refer to EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Solution Guide. In addition, refer to the latest EMC Simple Support Matrix for EMC Enterprise Hybrid Cloud 2.5.1 (requires login) for any updates.

Table 3. Oracle DBaaS solution-specific software

Software Version Notes

VMware virtualization and cloud infrastructure

VMware vCloud Automation Center Application Services

6.1.1 VMware model-based application provisioning framework

Operating system software

Red Hat Enterprise Linux 6.4 (64 bit) 6.4 Red Hat Enterprise Linux 6.4 (64 bit)

Application software

Oracle Database 11g Release 2 11.2.0.4 Oracle Database software including Oracle Enterprise Manager Database Control

Software requirements

(22)

Software Version Notes

Oracle Database 12c Release 1 12.1.0.2.0 Oracle Database software including Oracle Enterprise Manager Database Express 12c Application monitoring software

Oracle Enterprise Manager Cloud Control 12c

Release 2 12.1.0.2 Oracle integrated enterprise IT management solution

vCloud Automation Center enables customized, self-service provisioning and lifecycle management of cloud services that comply with established business policies. vCloud Automation Center provides a secure portal where authorized administrators, developers, and business users can request new IT services and manage existing computer resources from predefined user-specific menus.

vCloud Automation Center Application Services, formerly VMware vCloud Application Director, automates application provisioning in the cloud, including deploying, configuring, and updating the application's components and dependent middleware platform services on infrastructure clouds. vCloud Automation Center Application Services simplifies complex deployments of custom and packaged applications on infrastructure clouds.

vCenter Orchestrator is an IT process automation engine that helps automate the cloud and integrates the vCloud Suite with the rest of your management systems. vCenter Orchestrator enables administrators and architects to develop complex automation tasks in the workflow designer. The vCenter Orchestrator library of prebuilt activities, workflows, and plug-ins helps accelerate the customization of the standard capabilities of vCloud Automation Center.

vCenter Orchestrator is included with:

 VMware vCloud Automation Center

 VMware vCloud Suite

 VMware vCenter Server

vCenter Orchestrator can be deployed as a shared service within the vCloud

Automation Center Appliance or VMware vCenter Server. It can also be deployed as a stand-alone appliance dedicated to a single tenant. EMC recommends using the vCenter Orchestrator Appliance instead of the embedded vCenter Orchestrator service in vCloud Automation Center.

Before deploying a vCenter virtual machine with an Oracle Database from the vCloud Automation Center Service Catalog, complete the following prerequisite tasks: VMware vCloud Automation Center VMware vCloud Automation Center Application Services VMware vCenter Orchestrator Preparing to publish an application

(23)

Deploying Oracle Database as a Service b. If the guest OS is Linux, create a customized specification to assign the

hostname and IP address.

2. In vCloud Automation Center, create and configure a blueprint, as shown in Figure 8.

Figure 8. Creating a vCloud Automation Center blueprint 3. In vCloud Automation Center Application Services:

a. Map the cloud template.

b. Import and configure the application blueprint.

c. Publish the deployment profile to the vCloud Automation Center Service Catalog.

4. Assign the vCloud Automation Center Service Catalog. Figure 9 shows a detailed workflow for the full process.

(24)

* Virtual machine templates, vCloud Automation Center blueprints, and vCloud Automation Center Application Services cloud/logical templates are mapped in Table 4.

Figure 9. Preparing an vCloud Automation Center Application Services service to be published in vCloud Automation Center Service Catalog

Table 4 shows how the virtual machine template maps through the layers of abstraction to the vCloud Automation Center blueprint and the vCloud Automation Center Application Services cloud template.

Table 4. Mapping and abstraction of a vCenter virtual machine with vCloud Automation Center and vCloud Automation Center Application Services

vCenter vCloud Automation Center vCloud Automation Center _{Application Services}

Virtual machine template Blueprint Cloud template/logical template(s)

Separate application blueprints were created for this solution to support Oracle Database 11g Release 2 and Oracle Database 12c. These blueprints were developed from the Oracle Database 11g (Service) blueprint available from VMware Cloud

Management Marketplace on the VMware Solutions Exchange site. The required

Oracle Database binaries were held on an NFS share within the Oracle Tenant Resource Pod. The NFS share and software filenames were defined within the application blueprint as variables.

(25)

 Virtual machine template and version number

 OS version

Importing an application blueprint using the CLI

The screen shot in Figure 10 shows an application blueprint for Oracle 12c being imported and shared. In this case a suffix of EHC is used, as shown in the command listing in Figure 10, in the event that the package is already defined.

C:\darwincli>type run_darwin_cli.bat @echo off

set JAVA_HOME="C:\Program Files (x86)\Java\jre7\bin" c:

cd C:\darwincli

%JAVA_HOME%\java -jar darwin-cli.jar C:\darwincli>run_darwin_cli.bat

login --serverUrl https://<vCloud Automation CenterAS61.xxx.xxx.local>:8443/darwin --username

[email protected] --password XXxxxxx --tenantId Oracle- Business-Group

import-package --importFilePath C:\darwin-cli\AppSBPs\oracle12c_D3.xml --targetGroup Oracle- Business-Group --conflictResolutionAction

IMPORTASNEW --suffix "EHC"

Figure 10. Listing of commands to import a blueprint via vCloud Automation Center Application Services

The Darwin CLI client can be run on the vCloud Automation Center Application Services appliance, but for this solution and improved security, it was run on a desktop client with Java Runtime Environment 1.7.0_45 (minimum) installed. Here the Darwin CLI was called from a simple Windows batch file, run_darwin_cli.bat, as shown in Figure 10.

Customizing an application blueprint

Editing and versioning of an application blueprint are carried out through the vCloud Automation Center Application Services web application. Figure 11 shows the elements that can make up an application blueprint—logical templates, vCloud Automation Center Application Services service, and application components.

(26)

Figure 11. Customized application blueprint with OEM 12c Management Agent

Logical templates

Logical templates are an abstraction of a cloud provider's machine deployment, as shown in Table 4.

vCloud Automation Center Application Services

A vCloud Automation Center Application Service is a component-scripted software service such as an Oracle database or Apache web server that can be installed on a virtual machine and reused by multiple applications. Editable properties enable services to be parameterized and customized at deployment. Services can include OS-dependent scripts such as Bash/Python or Perl scripts for Linux and PowerShell for Windows.

Application components

Application components can be simple OS or database scripts, or even a full Java web application deployed as a WAR file along with database and application server

services.

Amend the compute, network, and storage resources to match the requirements. Assign a hostname using the Name property shown in Figure 11 as a prefix and a randomly generated suffix. Configure properties as secure string (for password), give them default values, and set them to be overridden at deployment. For Oracle Database, assign tags to disks to identify their purpose, as shown in Table 5. Table 5. Assigned disk tags

Disk tag Contents description

(27)

Deploying Oracle Database as a Service Review the Oracle 12c vCloud Automation Center Application Service properties and scripts, as shown in Figure 12, and add or edit components such as the OEM Cloud Control component. Figure 38 on page 42 provides more details about this

component.

Figure 12. Properties and actions for Oracle 12c_V1.0 vCloud Automation Center Application Service

Creating a deployment profile

This section describes how to create a deployment profile and give it a meaningful name, map the correct logical and cloud templates, map networks, and assign any required storage. The deployment wizard guides the process. After the process is complete, we publish the application blueprint to vCloud Automation Center.

Storage is populated from the vCloud Automation Center storage reservation policies that are applied to datastores. In this solution and for the purposes of illustration, storage reservation policies can be aligned to a specific purpose or based on a storage service offering and assigned to datastores as in Figure 14. In the deployment wizard, a disk can be assigned to these storage reservation policies and aligned to a purpose as shown in Figure 13, where the redo log disk is assigned to the

(28)

Figure 13. Deployment profile resource mapping

Figure 14. vCloud Automation Center storage reservation policy and datastores

For detailed information on workload-optimized ViPR storage-as-a-service offerings, refer to EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Solution Guide.

(29)

Deploying Oracle Database as a Service The Step 4: Review tab of the deployment wizard, shown in Figure 15, provides a summary of the virtual machine, the available datastores, and the application blueprint properties. On this page, click Publish, as highlighted in the figure.

Figure 15. Deployment wizard review screen

After the application is published from vCloud Automation Center Application Servicesto vCloud Automation Center, it appears in the catalog items under the Administration tab in Catalog Management. As shown in Figure 16, we activate the item and assign it to the service Oracle and the entitlement Oracle.

Figure 16. Activating the catalog item Oracle 12c Full OEM

In vCloud Automation Center, services are used to organize catalog items into related offerings to make it easier for users to browse for them. In this solution we have created a service called Oracle and assigned it to our catalog item.

vCloud Automation Center Service Catalog

(30)

Entitlements are specific to a business group and determine which users and groups can:

 Request specific services

 Request specific catalog items

 Perform specific actions on provisioned machines

Entitlements also control whether an approval is required for a catalog item or action, as shown in Figure 17.

Figure 17. Editing an entitlement to add an approval policy to a catalog item

The catalog item Oracle 12c Full OEM is now published to the vCloud Automation Center Service Catalog, as shown in Figure 18.

(31)

Deploying Oracle Database as a Service Use the vCloud Automation Center Service Catalog to provision a specific Oracle database. Complete the New Request form, shown in Figure 19, editing the properties as required before submitting the form. These properties set up the environment variables for the OEM 12c Agent and Oracle 12c Database.

As shown in Figure 19, the application blueprint offers a choice of which edition of Oracle Database to install. The install_edition property can have one of the following values:

 EE—Oracle Database Enterprise Edition

 SE—Oracle Database Standard Edition

 SEONE—Oracle Database Standard Edition ONE

The choice of the edition to be used depends on required functionality, organizational policy, and licensing and hardware restrictions.

Figure 19. New request to provision Oracle 12c Full OEM service

The request will not be addressed until approval is given based on the approval policy set shown in Figure 20.

Provisioning an Oracle Database

(32)

Figure 20. Change of request status before and after approval

The machine and application deployment is now complete. Figure 21 shows the status of the virtual machine and database as displayed in VMware vCenter and Oracle Cloud Control. You can also check the database connectivity using Oracle SQL Developer.

(33)

Deploying Oracle Database as a Service Figure 21. Oracle Database and virtual machine status

After the Oracle Database and virtual machine are provisioned, environmental and configuration changes are required. These activities, which are known as Day 2 operations, include routine maintenance tasks and changes to the virtual

infrastructure. These activities can be as simple as restarting the virtual machine, but they may also include changes that can affect the availability or cost of the service, such as adding vCPU, memory, or disks.

All of these machine actions can be run or scheduled from the Items tab in vCloud Automation Center, assuming the correct entitlements have been assigned. If an approval policy has been created against a specific action, then that change will not be applied until approval has been given.

Using vCloud Automation Center Advanced Services, customized vCenter

Orchestrator workflows can be deployed as resource actions. These resource actions extend the functionality of the standard machine actions to deliver complex

automated processes against the deployed virtual machine. As shown in Figure 22, the Actions menu contains both standard and custom resource actions.

Provisioning Oracle Database Day 2 operations

(34)

Figure 22. Managing the vCloud Automation Center machine under the Items tab When adding vCPU or memory using the standard Edit action, the virtual machine must be stopped, amended, and restarted. Storage resources can be added without rebooting using the standard Edit action.

So that Day 2 operations meet the elasticity and availability requirements of this solution, we must:

 Create a vCenter Orchestrator workflow, Add vCPU, to add a vCPU without rebooting.

 Create a vCenter Orchestrator workflow, Add Memory, to add memory without rebooting.

 Enable hot add for both vCPU and memory in the virtual machine template mapped to the vCloud Automation Center blueprint, as shown in Figure 23.

(35)

Deploying Oracle Database as a Service Figure 23. Enabling memory/CPU hot plug for a virtual machine.

Adding vCPU

We add the simple vCenter Orchestrator workflow Add vCPU, shown in Figure 24, as a resource action via vCloud Automation Center Advanced Services and publish it for use. We also add it to any required entitlements as an entitled action and assign any applicable approval policy.

Figure 24. vCenter Orchestrator Add vCPU workflow

To hot-add vCPU to a virtual machine in vCloud Automation Center:

1. In the Items tab, select the machine to which you want to add the new vCPU. 2. From the Action menu, select Add vCPU.

(36)

3. From the list box, select the number of vCPUs to be added, as shown in Figure 25, and then click Submit.

Figure 25. Adding vCPU to a machine

The preceding steps reconfigure the virtual machine with the new vCPU count, as shown in Figure 26.

Figure 26. vCPU count before and after Add vCPU action

The Oracle Database instance recognizes the change and reflects the new value of the initialization parameter CPU_COUNT.

Adding memory

Figure 27 shows the vCenter Orchestrator workflow to add memory to an active virtual machine.

(37)

Deploying Oracle Database as a Service Figure 27. vCenter Orchestrator Add Memory workflow

To hot-add memory to a virtual machine in vCloud Automation Center:

1. In the Items tab, select the machine that you want to add memory to. 2. From the Action menu, select Add Memory.

3. Select the new vMemory value, as shown in Figure 28, and then click Submit.

Figure 28. Adding vCPU to a machine

The preceding steps reconfigure the virtual machine with the new memory, as shown in Figure 29.

(38)

Figure 29. Memory value before and after Add Memory action Adding storage

The following steps show how to add storage using the standard vCloud Automation Center Edit action.

1. In the Items tab, click the machine that you want to add storage to. 2. From the Action menu, select Edit and then click the Storage tab for the

virtual machine.

3. Click the green cross for New Volume.

4. Under Capacity (GB), select a value for the disk and select a Storage Reservation Policy, as shown in Figure 30.

Figure 30. Adding a disk using the Edit action

(39)

Deploying Oracle Database as a Service Figure 31. Virtual machine properties before and after adding a new disk

As shown in Figure 32, you can track the status of your Day 2 operations in the vCloud Automation Center Request tab.

Figure 32. Request list and status of configuration change actions

Because of the potential impact of the actions on service availability and/or cost, an approval policy is applied to the Add vCPU, Add Memory, and Edit actions, as shown

(40)

Monitoring the Oracle Database environment

This section describes the monitoring of the Oracle Database environment, including stand-alone and extended solutions for monitoring the Oracle Database 11g and 12c, the guest OS, and the full stack for the Oracle Tenant Resource Pod.

OEM Database Control is the primary stand-alone tool for managing your Oracle Database 11g. It can be installed as part of the database creation process. Use Database Control to perform administrative tasks such as managing schema objects, controlling user security, managing database memory and storage, backing up and recovering databases and, if licensed, viewing performance and diagnostic information for your database. Figure 33 shows the OEM Database Control Login and Home page.

Figure 33. OEM Database Control Login and Home page

Database Control was configured as part of the Oracle Database 11g deployment, with some simple scripting in the application blueprint and service, as shown in Figure 34.

Overview

Monitoring Oracle Database 11g stand-alone

(41)

Deploying Oracle Database as a Service Oracle Enterprise Manager Database Express 12c (EM Express) is a web-based tool for managing Oracle Database 12c. It is built into the database and runs in the XDB schema inside the database. EM Express is easy to configure and offers support for basic database administration tasks such as storage and user management. If licensed, it provides comprehensive solutions for performance diagnostics and tuning. Figure 35 shows the EM Express Database Home and Login windows.

Figure 35. EM Express Login screen and Database Home window

For this solution, we enabled EM Express as part of the Oracle Database 12c

deployment with some simple scripting in the application blueprint and service, as shown in Figure 36.

Figure 36. Extract from the Oracle 12c service install script enabling EM Express

OEM Cloud Control 12c is Oracle’s integrated enterprise IT management product line, which is widely used for managing and monitoring the Oracle Database estate. It is highly configurable and has a number of partner plug-ins such as the EMC VMAX and VNX storage plug-ins for Oracle Enterprise Manager 12c.

The vCenter Operations Management Pack for Oracle Enterprise Manager from Blue Medora leverages Oracle OEM data to monitor Oracle environments and workloads via vCenter Operations Manager.

For this solution, we registered our host and database as targets with an existing environment featuring OEM Cloud Control 12c Release 2 (version 12.1.0.2), as shown in Figure 37. Monitoring Oracle Database 12c stand-alone Oracle Enterprise Manager Cloud Control 12c

(42)

Figure 37. Screen shot showing host, database, and listener targets after deployment We configured the OEM Management Agent as a scripted component in an

application blueprint and included it as part of the Oracle Database deployment, as shown in Figure 38.

(43)

Deploying Oracle Database as a Service VMware vCenter Operations Manager is the main operations management component of the EMC Enterprise Hybrid Cloud solution. It provides a simplified approach to operations management of physical and cloud infrastructures. vCenter Operations Manager includes operations dashboards to provide insights and visibility into the health, risk, and efficiency of your infrastructure, and to provide performance management and capacity optimization capabilities.

vCenter Operations Manager provides prebuilt and configurable dashboards for realtime performance, and capacity and configuration management. It abstracts performance data to health, risk, and efficiency measurements that enable IT to quickly identify evolving performance problems. Integrating vCenter Operations Manager with EMC ViPR Analytics enables full end-to-end visibility of the entire infrastructure, from virtual machine to LUN and every point in between. Figure 39 shows an example of the Details screen under the Operations tab in vCenter Operations Manager.

Figure 39. vCenter Operations Manager Details screen for a virtual machine deployed with Oracle DBaaS

The vCenter Operations Manager custom interface presents the ViPR Analytics and EMC Storage Analytics (ESA) packs. This enables administrators to quickly visualize the health of ViPR virtual arrays as well as physical VMAX and VNX arrays (both block and file) using customized EMC dashboards for vCenter Operations Manager, such as the EMC ViPR dashboard.

Capacity analytics in vCenter Operations Manager identify over-provisioned resources so they can be right-sized for the most efficient use of virtualized resources. What-if scenarios eliminate the need for spreadsheets, scripts, and rules of thumb.

ViPR SRM offers comprehensive monitoring and reporting for this hybrid cloud solution that helps IT visualize, analyze, and optimize their software-defined storage VMware vCenter

Operations Manager

(44)

infrastructure. Cloud administrators can use ViPR SRM to understand and manage the impact that storage has on their applications and view their storage topologies in their hybrid cloud from application to storage. They can view capacity and

consumption of ViPR software-defined storage and identify service-level agreement (SLA) issues via realtime dashboards or reports to meet the needs of the wide range of hybrid cloud users. Figure 40 shows the ViPR Performance dashboard.

Figure 40. ViPR Performance dashboard

In addition, for centralized logging, infrastructure components can be configured to forward their logs to VMware vCenter Log Insight, which then aggregates the logs from all the disparate sources for analytics and reporting. When integrated with vCenter Log Insight, EMC content packs for Avamar, VNX, and VMAX provide dashboards and user-defined fields specifically for those EMC products, which enables administrators to conduct problem analysis and analytics on their storage array and backup

(45)

Conclusion

EMC Enterprise Hybrid Cloud enables customers to build an enterprise-class, scalable, multitenant platform for complete infrastructure service lifecycle management.

The solution uses the best of EMC and VMware products and services to deliver on the following principles:

 Self-service and automation

 Multitenancy and secure separation

 Workload-optimized storage

 Security and compliance

 Monitoring and service assurance

In addition, the solution supports the use of modular add-on components, including one for application services such as vCloud Automation Center Application Services and vCenter Orchestrator.

This solution enables the deployment of Oracle DBaaS in a dedicated business group running on EMC Enterprise Hybrid Cloud. The key findings of this solution are as follows:

 Designing EMC Enterprise Hybrid Cloud with a dedicated Tenant Resource Pod for Oracle DBaaS improves management of Oracle licensing compliance.

 Application developers and service users can provision an Oracle Database directly from the vCloud Automation Center Service Catalog for Day 1 operations.

 The solution offers elasticity and support for Day 2 operations. The addition of resources—for example increasing vCPU or memory, or allocating storage—can be managed from vCloud Automation Center and applied or scheduled in line with defined approval policies. vCenter Orchestrator workflows can extend Day 2 operations to deliver custom actions managed in vCloud Automation Center.

 vCenter Orchestrator enables process automation throughout the machine provisioning lifecycle in vCloud Automation Center from build to disposal.

 Using vCloud Automation Center Application Services, DBAs and application architects can quickly build and publish blueprints with a drag-and-drop interface to automate the deployment of simple and multitier applications. Summary

(46)

References

For additional information on EMC Enterprise Hybrid Cloud, see the following documents:

 EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Reference Architecture

 EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Foundation Infrastructure Solution Guide

 EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Data Protection Continuous Availability Solution Guide

 EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Data Protection Backup Solution Guide

 EMC Enterprise Hybrid Cloud 2.5.1, Federation Software-Defined Data Center Edition: Data Protection Disaster Recovery Solution Guide

 EMC Enterprise Hybrid Cloud 2.5 with VMware: Security Management Solution Guide

 EMC Enterprise Hybrid Cloud 2.5 with VMware: Pivotal CF Platform as a Service Solution Guide

For additional information, see the following VMware product documentation. VMware vCloud Automation Center documentation

 Foundations and Concepts

 Installation and Configuration

 System Administration

 IaaS Configuration for Virtual Platforms

 Application Services

 Tenant Administration

 Advanced Service Design

 Extensibility

 Custom Properties Reference

IT Business Management Standard Edition documentation

 IT Business Management Standard Edition Installation and Administration Guide

 IT Business Management Standard Edition User's Guide VMware vCenter Orchestrator documentation

EMC

documentation

VMware documentation

(47)

Deploying Oracle Database as a Service Blog

 Manage your SDDC: Add/remove vCAC IaaS VMs to/from DNS by Yuval

Tenenbaum

Oracle Enterprise Manager Cloud Control documentation

 Advanced Installation and Configuration Guide Oracle Database documentation

 Database Installation Guide for Linux—Oracle Database 12c Release 1 (12.1)

 Database Installation Guide for Linux—Oracle Database 11g Release 2 (11.2) My Oracle Support

 Doc ID 1543773.1 : How to create an emcli script to add databases via emcli Oracle

(48)

Appendix A: Adding and deleting a DNS entry for a vCloud Automation

Center blueprint

Virtual machines provisioned in vCloud Automation Center have a lifecycle with a fixed number of states. You can assign vCenter Orchestrator workflows to run and make customizations at every state.

For this solution, we have vCenter Orchestrator workflows for each of the following activities, as shown in Figure 41:

 Adding a DNS record when provisioning a machine

 Deleting the DNS record when disposing of a machine

Figure 41. DNS management vCenter Orchestrator workflows

To add these workflows to the vCloud Automation Center blueprint, follow these steps:

1. From the vCloud Automation Center Library, run the vCenter Orchestrator workflow Assign a state change workflow to a blueprint and its virtual machines, as shown in Figure 42.

(49)

Deploying Oracle Database as a Service Figure 42. Assign a state change workflow to a blueprint and its virtual machines

2. For the Add VM to DNS with Optional PTR –vCAC IaaS workflow, select

MachineProvisioned for vCAC workflow stub to enable, as shown in Figure 43.

Figure 43. Selecting a vCloud Automation Center workflow stub 3. For the Delete record from DNS- IaaS vCAC workflow, select

(50)

4. Select the vCloud Automation Center host and select the blueprint to apply the DNS workflow to, as shown in Figure 44.

Figure 44. Select the blueprint to automate DNS registration

5. Select the vCenter Orchestrator workflow to add, as shown in Figure 45, and then click Submit.

Figure 45. Select the vCenter Orchestrator workflow to add

6. Verify that the custom properties have been created in the vCloud Automation Center blueprints, as shown in Figure 46.

(51)

Deploying Oracle Database as a Service Figure 46. Custom properties for machine provisioning and disposing

When a machine is provisioned or disposed of, verify that the appropriate DNS workflow runs by reviewing the Recent Events screen on the Infrastructure tab of the vCloud Automation Center, as shown in Figure 47.

(52)

Appendix B: Configuring the Linux virtual machine template

To configure the Linux virtual machine template for vCloud Automation Center and vCloud Automation Center Application Services, follow these steps:

1. Create a new virtual machine with the following attributes, as shown in Figure 48.

 2 x vCPU

 8,192 MB of memory

 40 GB virtual hard disk

 1 VMXNET3 vNIC on the required network

 Hot Plug vCPU and Hot Add Memory enabled

Figure 48. Settings for virtual machine template 2. Install RHEL 6.4 from the OS:

a. Configure disk so that the swap partition is at least 8 GB. b. Assign a temporary IP address to access network services. c. Temporarily set up DNS in /etc/resolv.conf.

3. Ensure that the Oracle installation meets the following prerequisites:

a. If you are preinstalling the Oracle binaries, follow the appropriate Oracle installation guide:

 Oracle Database Installation Guide 12c Release 1 (12.1) for Linux

 Database Installation Guide for Linux 11g Release 2 (11.2) for Linux

After the install is complete, detach Oracle Home from the inventory:

[oracle]$ $ORACLE_HOME/oui/bin/detachHome.sh