HPEDBaaSusing VRE

Reference Architecture
HPE Reference Architecture for

Oracle Database as a Service using
VMware vCloud Suite on HPE Synergy
and HPE Nimble All-Flash Array
Contents
Executive summary ................................................................................................................................................................................................................................................................................................................................ 3
Introduction ...................................................................................................................................................................................................................................................................................................................................................4
Solution overview ..................................................................................................................................................................................................................................................................................................................................... 4
Solution components............................................................................................................................................................................................................................................................................................................................5
HPE Synergy Composer.............................................................................................................................................................................................................................................................................................................. 6
HPE Synergy Image Streamer ...............................................................................................................................................................................................................................................................................................6
HPE Synergy Gen10 Compute Modules ..................................................................................................................................................................................................................................................................... 6
HPE OneView for VMware vCenter (HPE OV4VC) ...........................................................................................................................................................................................................................................6
HPE OneView for VMware vRealize Orchestrator (vRO) ............................................................................................................................................................................................................................. 7
HPE Nimble All Flash Array .....................................................................................................................................................................................................................................................................................................7
VMware vCloud Suite ................................................................................................................................................................................................................................................................................................................ 12
Hardware............................................................................................................................................................................................................................................................................................................................................... 13
Software ................................................................................................................................................................................................................................................................................................................................................. 13
Application software ................................................................................................................................................................................................................................................................................................................... 13
Best practices and configuration guidance .................................................................................................................................................................................................................................................................. 14
HPE Synergy and VMware vSphere implementation best practices ............................................................................................................................................................................................. 14
VMware vRealize Suite component implementation best practices .............................................................................................................................................................................................. 14
HPE Nimble Storage – Oracle Database implementation in vSphere environment best practices ................................................................................................................... 14
HPE Nimble All-Flash Array configuration............................................................................................................................................................................................................................................................. 15
Installing VMware vCloud Suite components ...................................................................................................................................................................................................................................................... 15
Configuring VMware vRealize Automation (vRA)........................................................................................................................................................................................................................................... 16
Integrate and configure vRealize Business for Cloud (vRBC) .............................................................................................................................................................................................................. 18
Use Case 1: Deploying Gold, Silver and Bronze Service Catalog for single instance Oracle Database as a Service using VMFS
Datastore ............................................................................................................................................................................................................................................................................................................................................... 20
Use Case 2: Demonstrate single instance Oracle Database as a Service on Oracle Automatic Storage Management (ASM) Disk
groups ...................................................................................................................................................................................................................................................................................................................................................... 36
Use Case 3: Demonstrate Oracle Pluggable Database as a Service on an Oracle Container Database ........................................................................................................ 41
Use Case 4: Demonstrate Oracle Database as a Service provisioning on bare-metal HPE Synergy Compute Module using HPE
OneView Plug-in for vRO and HPE Synergy Image Streamer ............................................................................................................................................................................................................. 46
Downloading and importing Out of the Box (OOTB) blueprints from VMware Marketplace ................................................................................................................................. 49
Summary ...................................................................................................................................................................................................................................................................................................................................................... 50
Appendix A: Bill of Materials ...................................................................................................................................................................................................................................................................................................... 51
Resources and additional links ................................................................................................................................................................................................................................................................................................ 54
Reference Architecture Page 3
Executive summary
Today, large IT organizations have hundreds of Oracle database instances running with different versions and configurations with availability
requirements of both mission-critical production environments and non-mission critical test or development environments. The major challenge
for an application team in such an environment is the time to provision a new Oracle database, which currently could take days to weeks. Cloud
computing service models such as Database as a Service (DBaaS) enable organizations to overcome these challenges.
DBaaS allows application developers, testers and database administrators to request a virtual machine (VM) running a specific operating system
(OS), database software, and a particular database size via a self-service portal, without the need for setting up physical hardware, installing and
configuring the software themselves. Provisioning a VM running Oracle database takes minutes, compared to hours or days utilizing traditional
infrastructure. This document presents a reference architecture describing Oracle Database as a Service with solid reliability, performance and
availability on an HPE Synergy 480 2-socket system for low to medium intensive Oracle database workloads. This solution is deployed using
VMware® vCloud Suite with a highly available vSphere Cluster and utilizes vRealize Automation blueprints for Oracle database deployment. HPE
Nimble All Flash Array has been used as storage for management and workload VMs.
HPE Synergy composable infrastructure speeds up deployment as well as simplifies scaling up and scaling out to meet Oracle database workload
demands and reduces management complexity using HPE OneView for VMware vCenter and HPE OneView for VMware vRealize Orchestrator
integrations. In a private cloud environment, all of the administrative tasks and maintenance of databases are taken care of by the IT
organizations or corporate level database teams, with the option of requesting end users having more control over the database, if required.
This service model helps to achieve:
• Reduced operational cost by

– Reducing number of admins
– Centralized patching
– Shared license cost
– Avoiding underutilized dedicated hardware
• Database consolidation
• Higher levels of database security
• Database regulatory compliance
• Specific SLAs
• Simplified DBA tasks and advanced automation
• More efficient ways to track the compute resource consumptions and chargeback
There are four use cases presented in this document, describing various Oracle database deployment methods, including Oracle
database provisioning on HPE Synergy bare-metal compute modules using HPE OneView for VMware vRealize Orchestrator workflow
integrations. This integration enables Cloud administrators to automate Oracle deployment on bare-metal compute modules in a
repeatable and extensible manner.
Target audience: This Oracle Database as a Service reference architecture document is meant for IT directors, data center managers,
infrastructure architects and DBAs who are considering consolidation and automation of their database environments, streamlining lifecycle
management, and optimizing resource utilization.
Document purpose: The purpose of this document is to describe an Oracle Database as a Service reference architecture solution and its
components, highlighting recognizable benefits to technical audiences.
This Reference Architecture describes solution testing performed in October 2018.

Introduction
With the increasing adoption of agile application development practices within large enterprises, developers have the ability to quickly deploy or
undeploy development environments for their applications. Now, developers and business users have the same expectation of the databases
connected to the development environments. In a traditional approach to database provisioning, users request a database instance and the
request goes through an approval process that spans multiple teams, such as the database administrator (DBA) team, server infrastructure team,
and storage and network teams. First, the system and storage administrators need to identify a suitable server and storage as requested by
DBAs, and allocate it to the DBA team. Subsequently, the DBA will do the software installation of the requested database size and version. There
might be additional complexities such as application and operating system certifications along with backup and high availability requirements. All
of these factors contribute to an end-to-end cycle time of more than a week.
Administrators have to manually manage the resources used by the provisioned databases. It can be a tedious process to locate who is using the
databases, their effective usage, and when to decommission the resources.
This reference architecture demonstrates how HPE is enabling customers to address these challenges using the HPE Synergy platform and the
VMware vCloud Suite. This document demonstrates a few methods to deploy Oracle Database as a Service on VMware virtual machines running
the Red Hat® Enterprise Linux® (RHEL) OS and maintain its lifecycle. Additionally, customers can build their own automation workflows to
automate more tasks and operations.
Solution overview
This solution is comprised of HPE Synergy Gen10 Compute Modules running VMware ESXi hypervisor, HPE Synergy Composer for managing
the HPE Synergy hardware platform, HPE Synergy Image Streamer that enables ESXi host deployment in minutes, HPE Nimble All Flash Array
and VMware vCloud Suite for automated Oracle database instance deployment using a self-service portal. VMware vCloud Suite contains ESXi
and the vRealize Suite which includes vRealize Automation, vRealize Business for Cloud, and vRealize Operations Manager.
Note
The HPE Converged Architecture 750 was used as the reference platform for this testing. Customers can also customize their Oracle DBaaS
configuration based on their needs, without using the CA750 design and using individual components as provided in the BOM. Please, work with
your HPE Authorized Channel Partner to deploy a CA750 architecture if preferred.
Figure 1. HPE Synergy 12000 Frame with HPE Synergy 480 Gen10 Compute Modules and HPE Nimble All Flash Array – AF60
Note
For development and Proof of Concept environments, HPE Synergy Image Streamer may be deployed in a single HPE Synergy Frame
environment without redundancy. For production environments, HPE recommends deployment of a three-frame architecture, which allows you
to configure redundant HPE Image Streamers, providing high availability for the appliance and thus providing highly available boot volumes.
Solution components
This section briefly describes the key components of the solution. The solution can be scaled up based on capacity needs. Refer to Deploying
VMware vSphere on HPE Synergy Best Practice Guide for VMware cluster design, HPE Synergy scalable fabric design, and more.
HPE Synergy Composer

HPE Synergy Composer provides the enterprise-level management to compose and deploy system resources to match your application needs.
This management appliance uses software-defined intelligence with embedded HPE OneView to aggregate compute, storage and fabric
resources in a manner that scales to your application needs, instead of being restricted to the fixed ratios of traditional resource offerings.
HPE Synergy Image Streamer

HPE Synergy Image Streamer is a new approach to deployment and updates for composable infrastructure. This management appliance works
with HPE Synergy Composer for fast software-defined control over physical compute modules with operating system and application
provisioning. HPE Synergy Image Streamer enables true stateless computing combined with the capability for image lifecycle management. This
management appliance rapidly deploys and updates infrastructure.
HPE Synergy Image Streamer adds a powerful dimension to “infrastructure as code” – the ability to manage physical servers like virtual machines.
HPE Synergy Image Streamer supports a variety of operations for flexibility in how you handle your images. For example, you can capture golden
images for your use, import golden images from another location, or modify some of your “known good” images for re-use. This flexibility allows
you to easily establish your desired images for use. A variety of images can be used on HPE Synergy Image Streamer. Reference implementations
provide artifacts for recent versions of VMware ESXi (5.0, 6.0 and above), and application images based on Red Hat Enterprise Linux (RHEL 6.7
and above, 7.2 and above) and SUSE Linux Enterprise Server (SLES 12 SP1 and above) using ext3 and ext4 file systems. The sample artifacts
available for ESXi can be found at https://github.com/HewlettPackard/image-streamer-esxi. The set of Reference Architectures based on Image
Streamer, with their associated artifacts are available at https://github.com/HewlettPackard/image-streamer-reference-architectures.
HPE Synergy Gen10 Compute Modules

HPE Synergy Gen10 Compute Modules deliver choice for performance, capacity, efficiency, and flexibility to power most workloads with support
for the full range of Intel® Xeon® Scalable Family processors in 2-socket or 4-socket form factors. They provide a 25% performance increase over
prior generations. The compute modules are designed to create a pool of flexible compute capacity within a composable infrastructure. In
addition, Gen10 HPE Integrated Lights-Out (iLO) 5 and silicon root of trust are designed to meet challenges such as attacks on firmware,
ensuring effective security protections.
The HPE Synergy 480 Gen10 Compute Module comes in a two-socket, half-height form factor to support demanding workloads. Powered by the
latest Intel Xeon Scalable processors, HPE Synergy 480 Gen10 utilizes HPE DDR4 SmartMemory supporting up to 3TB. It has flexible storage
controller options with up to two internal SFF drives (four uFF drives) and/or up to two internal M.2 drives, and three I/O mezzanine slots. The
HPE Synergy 480 Gen10 Compute Module is an ideal platform for general-purpose enterprise workload performance now and in the future.
Figure 2. HPE Synergy 480 Gen10 Compute Module
HPE OneView for VMware vCenter (HPE OV4VC)

HPE OneView for VMware vCenter is a plug-in for VMware's vCenter management console which enables vSphere administrators to quickly
obtain context-aware information about HPE servers and HPE storage in their VMware vSphere environment directly from within vCenter. This
enables the VMware vSphere administrator to easily manage physical servers and storage, data stores and virtual machines, all from a single
familiar console. By providing the ability to clearly view and directly manage relationships between virtual machines, and HPE Infrastructure, the
VMware administrator's productivity increases, as does the ability to ensure quality of service.
The OV4VC storage plug-in supports HPE 3PAR, MSA and StoreVirtual arrays. Nimble arrays come with their own built-in plug-in for vCenter
and OV4VC does not support HPE Nimble storage as of writing this reference architecture.
One of the key capabilities of HPE OneView for VMware vCenter is to easily and consistently increase capacity on demand for provisioning and
deployment. It enables you to deploy ESXi hosts on bare-metal HPE ProLiant and HPE Synergy servers directly from VMware vCenter with a few
simple steps to expand an existing cluster, or easily deploy a new cluster. This capability is referred as the Grow Cluster feature. Refer to the HPE
OneView for VMware vCenter Grow Cluster White Paper for more information.
HPE OneView for VMware vRealize Orchestrator (vRO)

HPE OneView for VMware vRealize Orchestrator (vRO) helps you automate complex IT tasks in an extensible and repeatable manner. It provides
a predefined collection of HPE actions and workflows that you can use in VMware vRealize Orchestrator. With its easy-to-use, drag-and-drop
access, you can automate HPE OneView managed hardware deployments, firmware updates, and other lifecycle tasks. HPE OneView for VMware
vRO allows you to incorporate the advanced management features of HPE OneView into larger IT workflows. You can also integrate the HPE
OneView workflows and actions into VMware vRealize Automation through VMware vRealize Orchestrator.
All the workflows in the plug-in communicate with HPE OneView using a Management Instance. A Management Instance communicates with
HPE OneView through its REST API over SSL. You can configure a Management Instance with a user name, password, and an optional domain.
All workflow processes are executed using these HPE OneView credentials.
HPE OneView for VMware vRO is licensed as part of HPE OneView. Basic functionality and inventory are supported using HPE OneView
Standard licenses. Advanced functionality, such as the use of HPE OneView Server Profile Templates and firmware updates, requires HPE
OneView Advanced licenses.
With the combination of HPE OneView for VMware vRO and HPE Synergy Image Streamer, it is possible to provide Database as a Service on
bare-metal HPE Synergy Compute Modules as well. This is possible using a workflow called “Assign Server Profile from Template”. This is
discussed as one of the deployment use-cases of DBaaS in this document.
HPE Nimble All Flash Array

HPE Nimble Storage All Flash Arrays combine a flash-efficient architecture with HPE InfoSight predictive analytics to achieve fast, reliable access
to data and 99.9999% guaranteed availability. Refer to HPE Get 6-Nines Guarantee for more details. Radically simple to deploy and use, the
arrays are cloud-ready, providing data mobility to the cloud through HPE Cloud Volumes. HPE Nimble Storage All Flash Arrays include all-
inclusive licensing, easy upgrades, and flexible payment options – while also being future-proofed for new technologies, such as NVMe and
Storage Class Memory (SCM).
Figure 3. HPE Nimble All Flash Arrays
HPE Nimble Storage All Flash Arrays provide exceptional expandability through the use of additional drive shelves and expansion slots for
adding more I/O cards. Each HPE Nimble array can support up to 144 drives and six I/O cards. The additional drive shelves do not include
controllers, and simply add capacity to the drive array. The Nimble All Flash Arrays now scale up from 128TB in the AF20Q to 4PB in the AF80
using four expansion shelves.
Following are the features provided by HPE Nimble All Flash Array:
• HPE InfoSight predictive analytics automatically predict and resolve 86% of problems before you even know there is an issue and it simplifies
planning with prescriptive forecasts into capacity, performance, and bandwidth requirements.
• It scales up performance and capacity independently and non-disruptively, and scales out to four arrays managed as one for increased
flexibility.
• Up to 5X or more data reduction from variable block inline deduplication and compression and provides data reduction, snapshots, and
Triple+ Parity RAID with no performance impact.
• App-granular, FIPS-certified encryption provides data-at-rest and over-the-wire protection. Data shredding is built-in.
• Native application-consistent snapshots and replication, as well as integration with leading backup software.
• Supports FC, iSCSI, vSphere APIs for Storage Awareness (VASA) for Virtual Volume (VVol) implementation.
• With the vCenter plugin, create and manage datastores (volumes) on the HPE Nimble Storage array, directly from vCenter. You can create,
grow, clone, snapshot and delete datastores. In addition, you can see detailed information about the current level of performance and use of
space.
• The HPE Nimble Storage plugin for vCenter also offers array-level monitoring in the vCenter console. IOPS, latency, and bandwidth details are
displayed on the Performance tab in the Datastore view.
• HPE Nimble storage VVol integration into VMware’s SPBM (Storage Policy Based Management) simplifies common storage management
tasks like LUN provisioning and management. By using policies to automatically provision LUNs at the time of VM creation, no pre-
provisioning of datastores is required and hence administrative costs are reduced by eliminating tedious tasks. The applications directly
benefit from this new, fine-grain level of interaction with critical storage resources. Automatic space reclamation when VMs are deleted or
moved ensures that no space is wasted and the array maintains a thin footprint.
While basic management is configured through each array’s web interface (up to 4 arrays can be grouped together for management), each array
can be configured to send health, configuration, and performance data back to HPE InfoSight. Sending data back to HPE InfoSight connects your
storage environment to the predictive analytics engine that is the cornerstone of InfoSight’s unique proactive management system. Problems can
be automatically detected, corrected, and resolved before they impact operations or performance. Figure 4 below depicts the dashboard screen
in HPE InfoSight, being displayed is an overall status of the storage environment, including capacity, health, and performance.
Figure 4. HPE InfoSight – Operation Dashboard

Beyond the dashboard, detailed performance data is found at the storage pool, array, and volume level, allowing you to easily drill down into any
aspect of your storage environment. Figure 5 below shows a summary performance screen at the storage pool level. All storage pools are listed
and summary performance data is provided on a user defined timeline. Negative or positive performance trends can be spotted and plans can be
engaged to provide proactive performance or capacity expansion.
Figure 5. HPE InfoSight – Storage Pool List

HPE InfoSight Cross-Stack Analytics for VMware environments provides performance correlation analytics to help you identify the leading
factors affecting performance, while avoiding significant manual data collection and analysis. The Cross-Stack Analytics for VMware agentless
per-VM monitoring feature gives enterprise IT staff clear visibility into latency and performance across host, network, and storage layers of the
stack through intuitive graphical representations. Figure 6 and Figure 7 show VMware virtualization infrastructure and performance details within
HPE InfoSight.
Figure 6. HPE InfoSight – VMware Cluster view

Figure 7. HPE InfoSight – VMware VM view
VMware vCloud Suite

VMware vCloud Suite is an integrated offering that brings together vSphere hypervisor and VMware vRealize Suite, and it comes in three
editions, Standard, Advanced, and Enterprise. Each edition is targeted at a specific deployment use case. This reference architecture used
Enterprise Edition. VMware vRealize Suite is a multi-vendor hybrid cloud management platform that enables IT to quickly deliver infrastructure
and applications.
Figure 8. VMware vCloud Suite components

VMware vRealize Suite contains:
• vRealize Operations: Automate IT operations management, manage performance and gain visibility across physical, virtual and cloud
infrastructure.
• vRealize Automation: Self-service, policy-based infrastructure and application provisioning and lifecycle management for multi-vendor virtual,
physical, and public cloud environments.
• vRealize Business for Cloud: Automated cloud costing, cloud consumption analysis, and cloud comparison for your private, public, and hybrid
cloud suite.
Note
VMware NSX and vSAN are optional components and they are not validated in this reference architecture.
Hardware
The hardware components used in this reference architecture are as follows.
Table 1. Hardware components
Components Purpose
6 * HPE Synergy 480 Gen10 Compute Modules vSphere Management Cluster, Compute Cluster, Windows® AD and vCenter
HPE FlexFabric 5940 2-slot switch Network switch
HPE SN6000B 16Gb 48/48 Pwr Pk+ FC switch SAN switch connecting HPE Nimble storage and HPE Synergy
HPE Nimble Storage All Flash Array – AF60 Storage for VMFS and VVol based Datastore
Software
The software components used in this reference architecture are as follows.
Table 2. Software components
Components Version
Microsoft® Windows Server® 2016 Datacenter Edition 2016 – Windows Domain Controller and Active Directory Server
VMware vSphere ESXi HPE Custom Image for ESXi 6.5U2
VMware vRealize Automation with embedded version of 7.4

vRealize Orchestrator
VMware vRealize Business for Cloud 7.4
VMware vRealize Operations Manager 6.7
VMware vCenter Server Appliance 6.5 U2b
HPE OneView for VMware vRealize Orchestrator 1.0
HPE OneView for vCenter (OV4VC) 9.1
Application software
The application software components used in this reference architecture are as follows.
Table 3. Application software components
Components Version
Oracle 12c Database and Grid Software 12.0.*

Best practices and configuration guidance

HPE Synergy and VMware vSphere implementation best practices
1. Hosts participating in VMware HA cluster should be distributed across HPE Synergy Frames to have Frame level redundancy.
2. Clusters should be homogeneous with all components installed identically across all ESXi hosts. This is to promote a reduction of service
related events by making sure all firmware, drivers, and software are at the same revisions.
3. Use MC-LAG (Multi-Chassis Link Aggregation Group) with active/active uplinks to your ToR (Top of Rack) switch for optimal load balancing
and resiliency.
4. Consider segmenting datacenter management traffic from VM production traffic through separate uplink sets. For large dense virtualization
environments, consider segmenting FC (Fibre Channel) traffic from Ethernet using HPE Virtual Connect SE 16Gb FC modules for maximum
SAN storage I/O performance.
5. HPE Synergy 480 Gen10 Compute Modules have Workload Profile BIOS settings. This feature sets all the recommended BIOS settings for a
given workload by simply selecting a single choice. There are two workload profile choices for virtualization hosts: Virtualization – Power
Efficient or Virtualization – Max Performance. Choose the appropriate workload profile which meets your specific needs.
6. Define your VMware ESXi host best practice through HPE OneView’s Server Profile Template (SPT) and include firmware along with
standard settings for the servers. Set the Virtualization Workload Profile in the SPT so that every server gets those BIOS settings.
For more details, refer to Deploying VMware vSphere on HPE Synergy Best Practice Guide.
VMware vRealize Suite component implementation best practices

1. A stable NTP server is critical for vRealize implementation.
2. Create DNS entries for all the vRealize appliances before beginning the installation.
3. Read and understand the VMware’s vRealize Automation 7.4 Reference Architecture documentation for best practices, various deployment
options such as Small, Medium, Large and Multi-Data Center deployment and decide the right deployment scenario to start with. This
document also provides the required hardware specification for each appliance, high availability options and server role.
4. Review VMware vRealize Foundations and Concepts documentation.
5. Use VMware vRealize Suite Lifecycle Manager (vRSLCM) to install vRealize appliances faster and more easily.
6. Create a separate Management vSphere HA Cluster in vCenter for hosting vRealize appliances and have a separate vSphere HA Cluster for
deploying workload VMs.
7. Before proceeding with installation of appliances and server roles, refer to the vRealize Automation Support Matrix document for the
supported operating system and software components.
HPE Nimble Storage – Oracle Database implementation in vSphere environment best practices
1. Use “VMware Paravirtual” SCSI adapter for VM disks (VMDK on VMFS). This adapter optimizes the guest OS for performance as compared to
an emulated adapter, which would spend more CPU cycles emulating the behavior of physical hardware. For Oracle databases, configure two
“VMware Paravirtual” SCSI adapters, one for Oracle Data files and another one for REDO logs.
2. Do not to overcommit virtual RAM to a point at which the Oracle SGA might be swapped out to disk. It is recommended to monitor the Oracle
Database performance for some period and make changes accordingly.
3. VMware recommends using VMFS for VMs, including database workloads, since the I/O performance is just as good as using Raw Device
Mapping (RDM) disks. Refer to VMware documentation to learn more about this.
4. Oracle Recovery Manager (RMAN) is a backup utility that most DBAs use to back up their databases. In addition to using RMAN, HPE
suggests that you implement HPE Nimble Storage snapshots as an extra layer for backups. In some cases, it might be easier to use an HPE
Nimble Storage snapshot than to use RMAN to perform the database restore or recovery.
5. Enable HPE Nimble Storage compression on Oracle data files and control files and disable any Oracle compression algorithms to save
additional license cost associated with Oracle compression methods.
6. Disable deduplication on Oracle-related volumes unless full copies of an Oracle database also exist on another volume on the storage device.
For more details on Oracle deployment on HPE Nimble storage, refer to HPE Nimble Storage Deployment Considerations for Oracle Database.
HPE Nimble All-Flash Array configuration

In this reference architecture, VMware VMFS (Virtual Machine File System) datastore using LUN presented from Nimble storage and VVol
(Virtual Volume) datastore using resizable container from Nimble storage were used as storage for vRealize Suite appliances and Oracle
database VMs.
VVols are unique in a way that each virtual disk in a Virtual Machine (VM) is implemented with its own volume on the Nimble storage array.
VVols consume storage from a resizable container on the array and it alleviates the requirement to manage, provision, and present multiple
LUNs for varying workloads. VVols allow you to take advantage of array-based snapshots, replication, application synchronization, and more.
VMware provides a default VM storage policy called “VVol No Requirements Policy”. This is the default policy applied to VVol-enabled VMs.
Create your own storage policies to take advantage of array-based snapshots, replication, application synchronization, and more. Refer to
VMware VVols on HPE Nimble Storage Implementation Guide for more information.
Installing VMware vCloud Suite components

VMware vCloud Suite Enterprise Edition contains the list of integrated products shown below. VMware vRealize Suite Lifecycle Manager
(vRSLCM) is a free product that comes with vRealize Suite, and it is the first virtual appliance that you would install in an existing vSphere
environment and then use it to deploy the vRealize suite of components. Alternatively vRealize components can be manually deployed, but
vRSLCM makes it easy to deploy, patch, upgrade, and provide configuration management of vRealize components.
• VMware vSphere (ESXi Hypervisor)

• vRealize Suite
– VMware vRealize Automation (vRA)
– VMware vRealize Operations (vROps)
– VMware vRealize Log Insight (vRLI)
– VMware vRealize Business for Cloud (vRBC)
– VMware vRealize Suite Lifecycle Manager (vRSLCM)
In this reference architecture, all of the above components are installed within a Management Cluster, which has two ESXi hosts participating in it.
vRealize Automation has been deployed using Small Deployment Architecture as mentioned in the vRealize Automation 7.4 Reference
Architecture document. The table below shows the overview of different deployment models.
Table 4. VMware vRealize Deployment Models
Deployment Model Managed Machines Catalog items Machine provisioning concurrency
Small Deployment 10,000 500 10
Medium Deployment 30,000 1000 50
Large Deployment 50,000 2500 100
In this reference architecture, the application authoring feature available in the Enterprise Edition of vCloud Suite was used for deploying Oracle
database software and database creation. Figure 9, below, shows the logical view of vSphere Cluster, hosts and VMs deployed in this reference
architecture. HPE Nimble All Flash Array, AF60, is configured as external FC storage, providing standard LUN access for creating a clustered
datastore and a VVol datastore in this configuration.
Figure 9. Oracle Database as a Service – Logical deployment diagram
Configuring VMware vRealize Automation (vRA)

After the vSphere administrator completed the installation of vRealize Suite components, the vRA deployment wizard needs to be executed
using the URL https://vra.dbaas.local:5480 and then the following steps need to be performed for creating and publishing self-service catalog
items.
Table 5, below, lists the various vRealize component’s DNS records that are referenced in this section.
Table 5. vRealize Component’s DNS Records
Components DNS Records
vRealize Automation appliance A Record: vra1.dbaas.local

CNAME Record: vra.dbaas.local
Infrastructure Web and Manager Server A Record: winiaasvm1.dbaas.local

CNAME Record: web.dbaas.local, manager.dbaas.local
Microsoft SQL DB Server for IaaS Component A Record: mssql.dbaas.local
vRealize Business for Cloud appliance A Record: vrb.dbaas.local
1. Create Active Directory (AD) user accounts for the users who will be using vRA self-service portal and group them based on their Business
Group and their Roles. Also, create AD accounts for cloud admins, application solution architects and infrastructure architect. These different
users will play a vital role for creating blueprint, software components and self-service catalog items. A blueprint contains specifications of
virtualization resources, how to provision and manage the lifecycle of resources in vRA.
2. Log in as “administrator” in https://vra.dbaas.local/vcac
Note
“administrator” is the SSO login credential, which was created in the vRA deployment wizard. This is the “default” Tenant Administrator and is
used to create new admin accounts, which can act as Tenant Administrator and/or IaaS Administrator in vRA perspective. Refer to VMware
documentation for more details on roles.
3. Select Administration  Tenants  click vsphere.local  select the Local users tab  click on New.
4. Create a local user account called “vraadmin” and click the Administrators tab  assign Tenant administrator and IaaS administrator role
to vraadmin.
5. Log out as “administrator” and log in as “vraadmin” or you can use the “configurationadmin” account, which was created by vRA deployment
wizard.
6. Corporate Active Directory needs to be integrated into vRA for single sign on purpose. Select Administration tab  Directories
Management tab  Directories and click on Add Directory and select Add Active Directory over LDAP/WA, and provide the following
information:
a. Directory Name, for example: dbaas.local and leave the default values for everything else.
b. In Base DN input, provide your Windows Domain’s Base DN, for example: DC=dbaas,DC=local
c. In Bind DN input, provide Domain Account which has AD access, for example: cn=Administrator,cn=users,dc=dbaas,dc=local and test
the connection.
d. Click Save & Next. Select the groups and users you want to sync and click Finish. Now, vRA is synced up with AD and AD users need to
be assigned vRA roles.
7. Select the Administration tab  Users & Groups tab  Directory Users and Groups. In the search input, enter the AD user account to
which you want to assign vRA Roles and search. Click on the search output and start assigning Roles to AD users accordingly. Refer to vRA
documentation on Roles and Custom Groups feature for more flexible ways of assigning roles.
8. Now, Infrastructure Endpoint needs to be added to vRA. Click on Infrastructure  Endpoints  Endpoints  New  Virtual 
vSphere(vCenter).
9. Enter a name (check below Note) in the Name text box and the URL for the vCenter Server as https://vcenter.dbaas.local/sdk.
Note
The Name must match the endpoint name provided to the vSphere proxy agent during vRA deployment wizard, or else data collection will fail.
10. Enter your vSphere administrator-level user name and password or use your vSphere integrated credentials. Select Use integrated
credentials to use the vSphere proxy agent's service account to connect to the vCenter Server.
11. Select Infrastructure  Endpoints  Fabric Groups and create a Fabric group, which will have selected Compute Resources from the
vSphere Endpoint, such as ESX Host or vSphere HA Cluster, etc. Also, add a user as Fabric administrators. For example, create “cloudadmin”
in AD and assign Fabric administrator role.
12. Create default machine prefix at Infrastructure  Administration  Machine Prefixes. This will be used as prefix for the name of VM
instance requested by a particular Business Group user.
13. Create Business Groups from Administration  Users & Groups  Business Groups tab and assign Group manager role, Support role,
Shared access role and User role to the AD users accordingly. Also set “Default machine prefix” for the Business Group.
14. Create Network Profiles at Infrastructure  Reservations  Network Profiles  New and provide the IP Address range, DNS, and
Gateway information for every network that is created and assign a name to it. These network profiles will be used in Reservations and
Blueprint creation. VMs created using the self-service portal will get static IPs allocated from this using VMware vRealize IPAM.
15. Create Reservations for Business Group users at Infrastructure  Reservations  Reservations  New. Here, infrastructure admin
defines what compute resources, such as number of machines (Machine quota), Memory, Storage, Network, are available to a particular
Business Group. For example, a reservation called “BG1Reservation” was created for the Business Group called “BG1”.
16. Create a blueprint at Design  Blueprints  New. You need IaaS architect privilege to create and publish a basic blueprint. Refer to the
Use Case sections in this document for more details on blueprint creation.
17. After a blueprint is published, other architects can reuse it as a component in new blueprints. To make this blueprint as Service Catalog item,
complete the following:
a. Create a Service at Administration  Catalog Management  Services  New.
b. Click on the published blueprint (also known as Published Catalog Item) from Administration  Catalog Items and associate the
Service which was created in the above step.
c. Create an Entitlement for a particular Business Group at Administration  Catalog Management  Entitlements  New and
associate the Service which was created in the above step. Now, the blueprint will be shown as a Catalog Item under Catalog tab for all
the users belonging to a Business Group.
Integrate and configure vRealize Business for Cloud (vRBC)

After installing vRBC appliance, log on to https://<vrbc_fqdn>:5480/ using root credentials and configure NTP server settings under
Administration  Time Settings, and then select the Registration tab. In the Registration tab, for Hostname, enter the FQDN of the vRA
appliance; for SSO Default Tenant enter vsphere.local; for SSO Admin User/Password, enter “administrator”/password. Select the Accept
“vRealize Automation” certificate checkbox, and click Register. After successful registration, SSO Status will be shown as “Connected to
vRealize Automation”.
Figure 10. Registering vRealize Business for Cloud in vRealize Automation
After registration with vRA, log on to vRA as Tenant Administrator and select Administration  Business Management and click on vCenter
Server under Manage Private Cloud Connections. Then, click on the “+” icon to add the vCenter, and accept Certificates configuration prompt.
Now select Business Management tab and click Status with warning symbol and click on Update now for Cost Calculation, vCenter data
collection and vRealize Automation data collection. This will update all the cost and inventory data in vRBC.
Follow the steps below to configure cost for blueprints:

1. Select Business Management  Consumption  Pricing and Charges  Pricing  Edit Pricing.
2. Expand vRealize and click on Reservation (for example: BG1Reservation).
3. Set the cost for Compute Rates per vCPU daily and per GB RAM daily, and Storage Rate per GB daily. Also add additional charges, if any.
Figure 11. Configuring pricing in vRealize Business for Cloud
4. Now, when a user makes a request in the catalog, the user can click on the Update link to have the daily cost calculated, and can view cost
details by clicking View Price Details. These two items are highlighted by red arrows in Figure 12.
Figure 12. Viewing pricing details of requested catalog item

Figure 13. Viewing pricing details of requested catalog item
5. After cost is configured for the reservation, the current costs for requested items can be seen under Items. Items with zero cost were created
before cost was configured. If approval policies are used, an approver could determine if the cost exceeds a certain limit, and the approver
may reject the request.
The following section presents various methods of creating Oracle Database as a Service with different configuration and deployment options.
Use Case 1: Deploying Gold, Silver and Bronze Service Catalog for single instance Oracle Database as a Service
using VMFS Datastore
This use case demonstrates the creation of a blueprint for clone based VM deployment and Oracle Database creation using a vRA Application
Authoring feature called a Software Component. Following are the configuration steps to be followed:
1. Preparation of VM Template (commonly known as Golden Image preparation)

2. Developing a blueprint that deploys Cloned VMs from VM Template
3. Creation of Software Component for Oracle database creation
4. Creation of “Single Instance Oracle Database as a Service” Blueprint
Preparation of VM Template
vRA mainly uses either a clone or a linked clone deployment for a new VM and it is used as the base machine in the vRA blueprint. A clone
deployment creates an independent VM based on the VM template created in vCenter. A linked clone deployment uses a snapshot of a VM and
the original VM should always exist and cannot be deleted. In general, linked-clone deployments are not recommended for a production
environment. Below are the steps to create a VM Template in vCenter Server:
1. As a vSphere Administrator, create a new VM called OracleDB_RHEL74_x86, install RHEL 7.4 and configure the necessary network and
storage devices for an Oracle database server.
2. Complete all the standard procedures for installing an Oracle database, i.e., fulfilling all the prerequisite such as swap size, required RPM
packages, Oracle environment settings, Oracle user account, permissions, etc.
3. Now install the Oracle database software only and do not create a database, i.e., choose the “Install database software only” option as shown
below, while installing the Oracle database software.
Note
The VM Template will only have Oracle Database software installed. When a user requests a database instance via the self-service portal, vRA
will create a new clone of the VM Template and the Software Component of the blueprint will provision and configure the database, listener, etc.
on the cloned VM. For Oracle licensing on VMware, refer to Understanding Oracle Certification, Support and Licensing for VMware Environments
Figure 14. Oracle Database 12c Installation – selecting Install database software only option
4. Log on to the newly provisioned RHEL VM as root and install the VMware vRealize Guest agent and the Software bootstrap agent in it. The
agent installation script is available in your vRA appliance. Download it from there as shown below:
# wget --no-check-certificate https://vRealize_VA_Hostname_fqdn/software/download/prepare_vra_template.sh
Example: # wget --no-check-certificate https://vra.dbaas.local/software/download/prepare_vra_template.sh
# chmod +x prepare_vra_template.sh
# ./prepare_vra_template.sh
Provide the IaaS Web Manager FQDN, vRA FQDN and credentials as requested by the script.
Note
The guest agent and software bootstrap agent assist in software provisioning on the cloned VM, using scripts such as Bash shell and PowerShell
scripts. In our case, the Bash shell script will create the database on the cloned VM.
5. After installing the agents, you can convert the VM into a VM Template or use the “Clone to Template” option to create the template from the
clone of the VM. If you are planning to use linked clones for Dev/Testing purpose, you may leave the VM as it is and just create a snapshot of
the VM that will be used for creating linked clones in the blueprint.
6. Create a Customization spec for the RHEL VM at vCenter Home  Policies and Profiles  Customization Specification Manager and
name it RHEL74. Customization specifications are XML files that contain guest operating system settings for virtual machines and are used
for applying network settings and hostname. Figure 15 below shows the details of the RHEL74 Customization spec.
Figure 15. vCenter – Customization Specification Manager
Developing a blueprint that deploys cloned VMs

As an IaaS architect, you create and publish a basic blueprint that clones the vSphere virtual machine which is already installed and configured in
the vSphere environment. As a Software architect, reuse this blueprint as a component in a new blueprint and add a new “Oracle single instance
creation” software component to it. Finally publish it as a Database as a Service for Oracle Single Instance catalog item. You may need to create a
catalog item for every database size listed below and offer them to various business groups. The size may vary based on end-user requirements.
Table 6. Oracle Database as a Service – “T-shirt sizing”
DB Size vCPU Memory in GB Storage in GB
Bronze 2 16 100GiB – OS
300GiB – Oracle
Silver 4 32 100GiB – OS
600GiB – Oracle
Gold 8 64 100GiB – OS
1.2 TiB – Oracle
The steps below provide information about creating a single instance Oracle Database as a Service catalog item. You may need to change the
vCPU, memory and storage allocated to each DB Size category accordingly while creating a separate blueprint for each DB size listed above. Also,
you may create a VM storage policy in vCenter, which contains rules that deploy the storage level of service on each individual VM. For example,
Nimble allows you to create rules based on deduplication, application policy, all-flash, performance (IOPS), protection schedule, and data
encryption. For the Gold DB size, you may allocate storage from all-flash with higher IOPS.
1. Log in as IaaS architect and select Design  Blueprints.

2. Click on New icon.
3. Enter RHEL 7.4 on vSphere for Oracle Database Service in the Name text box.
4. Enter Base RHEL 7.4 machine for Oracle Database Service in the Description text box.
5. Enter 10 in the Deployment limit text box. This limits the number of deployments that can be requested per request by a user. For unlimited
deployment, leave it blank.
6. Configure Lease (days) range as required. For example, a minimum of 1 and maximum of 30 days. When the lease expires, the deployed VM
is destroyed or it can be archived.
7. Set the appropriate number of days for Archive (days) for the VMs that have lease expired. Finally press OK.
Figure 16. Blueprint creation – New Blueprint General tab

8. Now, the Design Canvas window will get launched. Click the Machine Types category in the left navigation pane and machine component
types appear in the lower panel. Drag and drop a vSphere machine component onto the canvas.
9. Click on Network & Security category and drag and drop Existing Network onto the canvas. Select the Existing Network and click on the
browse button of Network Profile text input in the General tab and select the network with VMware as IPAM endpoint and click Save
button. Please note that this network profile was created while configuring vRA.
10. Select vSphere Machine on the canvas and enter Base RHEL 7.4 machine for Oracle Database Service in the Description text box in the
General tab and select Use group default from the Machine prefix drop-down menu.
11. Set the required Reservation policy, if already configured or leave it blank. Usually a fabric administrator creates a reservation policy to
provide an optional and helpful means of controlling how resources at different service levels are allocated for provisioning requests.
12. Enter Minimum and Maximum instances that users can request for a deployment. If you don’t want to give users a choice, enter the same
value in the Minimum and Maximum fields.
Figure 17. Blueprint creation – vSphere(vCenter) Machine – General tab

13. Click on the Build Information tab and select Server from the Blueprint type drop-down menu. This information is for record-keeping and
licensing purposes only.
14. Select Clone from the Action drop-down menu and automatically CloneWorkflow gets selected in the Provisioning workflow drop-down
menu.
15. Click the Browse icon next to the Clone from text box and select OracleDB_RHEL74_x86 template to clone machines from the template you
created in vSphere, and then click OK. If OracleDB_RHEL74_x86 template is not visible in the Template list, you may need to resync
compute resources from Infrastructure  Compute Resources  Compute Resources and select Data Collection option by hovering
over compute resource configured over there.
16. Enter RHEL74 in the Customization spec text box to use the customization specification you created in vCenter. This value is case sensitive.
Figure 18. Blueprint creation – vSphere(vCenter) Machine – Build Information tab

17. Click on Machine Resources tab and specify CPUs, Memory (MB) and Storage (GB) settings as per DB size that you are configuring, and if
needed, add more capacity, which can be requested by the user as an extra resource in the catalog item. The minimum field for Storage is
automatically populated based on the storage configured in the VM Template.
Figure 19. Blueprint creation – vSphere(vCenter) Machine – Machine Resources tab

18. Select the Storage tab and add disk capacity based on DB size. Storage information of VM Template is already populated and you may add
additional storage, if required and optionally configure Storage Reservation policy, if some have already been defined. Usually a fabric
administrator creates storage reservation policy to allow Tenant Administrator and Business Group managers to assign the volumes from
different datastores. For example, OS volumes are placed on a less expensive datastore and database volumes are placed on a faster
datastore. Save the blueprint and click on the Network tab.
Figure 20. Blueprint creation – vSphere(vCenter) Machine – Storage tab

19. Click on the New icon and select the configured external network in the Network drop-down menu and press OK. You may now notice that
canvas components Network (shown as pramlab in the screen capture below) and vSphere machine are connected to each other. When a
new VM instance request is made through self-service portal, a static IP address from the IP address range configured in the Network Profile
will be applied on the newly created VM.
Figure 21. Blueprint creation – vSphere(vCenter) Machine – Network tab
20. Click Finish.

21. Select the row containing RHEL 7.4 on vSphere for Oracle Database Service and click Publish. Now, a catalog-ready blueprint has been
created to deliver cloned vSphere RHEL machines and it can be used by software architects to create blueprints for application ready
machines such as a single instance Oracle Database server.
Creation of Software Component for Oracle Database Creation

1. As a Software architect, log on to vRA and select Design  Software Components.
2. Click the New icon and in the General tab, enter OracleDB12c – Create Database in the Name text input box and enter Oracle12c
Database Creation Software Component in the Description text box.
3. Select Machine from the Container drop-down menu. This basically puts the restrictions onto the software architect not to use this on top of
other software components, because it can be used only on top of Machine. Click Next.
Figure 22. Software Component creation – New Software General tab

4. In the Properties tab, add new properties for the software, such as Database Instance Name db_name. The Value for this parameter can be
either requested from the end user or pre-populated. Here, the Value is not given and it will be requested while making an Oracle Database
server request in the self-service portal. Click Next.
Figure 23. Software Component creation – New Software Properties tab
Note
The properties defined here will be available as shell variables to a Bash shell script that will get executed after the deployed VM comes up. In the
above screen, only db_name is being collected from the end user. You may request as much information as you want from an end user and those
will be available as variables to the shell script which creates the database. For example, the SYS password can be requested from the end user.
5. Configure the Install Lifecycle Stage action script. Select Bash from the Script Type drop-down menu and click on Click here to edit.
Figure 24. Software Component creation – New Software Actions tab

6. In the Edit script for Install of Oracle 12c – Create Database text input window, copy and paste the script in Table 7 and select db_name
from Select a property to insert for use in the script.
Note
You can either use the script shown below or use a dbcA response file to create the database. Use case 2 demonstrates the use of a response file
based database creation. In the script below, the administrator can modify the parameter values as needed.
Table 7. Oracle 12c – Create Database Bash script

#!/bin/bash
#
# Create Oracle Database
# Following information has been collected from user
# db_name – Database instance name
# 1. Creating pfile based on the info received from Catalog Request
db_name_val=$db_name
pfilenm="init"$db_name_val".ora"
echo $pfilenm
db_name_svc=$db_name_val"XDB"
. /home/oracle/.bash_profile
su oracle -c "
cat <<EOF > $ORACLE_HOME/dbs/$pfilenm
$db_name_val.__data_transfer_cache_size=0
$db_name_val.__db_cache_size=7952400384
$db_name_val.__java_pool_size=33554432
$db_name_val.__large_pool_size=67108864
$db_name_val.__oracle_base='/oracle'
$db_name_val.__pga_aggregate_target=3388997632
$db_name_val.__sga_target=10099884032
$db_name_val.__shared_io_pool_size=536870912
$db_name_val.__shared_pool_size=1476395008
$db_name_val.__streams_pool_size=0
*.audit_file_dest='/oracle/admin/$db_name_val/adump'
*.audit_trail='db'
*.compatible='12.1.0.2.0'
*.control_files='/oracle/oradata/$db_name_val/controlfile/o1_mf_fpnzdp96_.ctl','/oracle/fast_recovery_area/$
db_name_val/controlfile/o1_mf_fpnzdpb5_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/oracle/oradata'
*.db_domain='dbaas.local'
*.db_name='$db_name_val'
*.db_recovery_file_dest='/oracle/fast_recovery_area'
*.db_recovery_file_dest_size=4560m
*.diagnostic_dest='/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=$db_name_svc)'
*.open_cursors=300
*.pga_aggregate_target=3201m
*.processes=300
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=9603m
*.undo_tablespace='UNDOTBS1'
EOF
# 2. Creating directories mentioned in the pfile
echo Creating directories...

mkdir -p /oracle/admin/$db_name_val/adump
mkdir -p /oracle/oradata/$db_name_val/controlfile/
mkdir -p /oracle/fast_recovery_area/$db_name_val/controlfile/
echo export ORACLE_SID=$db_name_val >> /home/oracle/.bash_profile
export ORACLE_SID=$db_name_val
# 3. Creating Database
sqlplus /nolog <<EOF

connect/as sysdba
STARTUP NOMOUNT;
define db_name_val='$db_name_val'
SELECT sys_context('USERENV','INSTANCE_NAME') FROM dual;
CREATE DATABASE &db_name_val

USER SYS IDENTIFIED BY Password1234
USER SYSTEM IDENTIFIED BY Password1234
LOGFILE GROUP 1 ('/oracle/oradata/&db_name_val/redo01.log') SIZE 100M,
GROUP 2 ('/oracle/oradata/&db_name_val/redo02.log') SIZE 100M
DATAFILE '/oracle/oradata/&db_name_val/system01.dbf' SIZE 325M
SYSAUX DATAFILE '/oracle/oradata/&db_name_val/sysaux01.dbf' SIZE 325M
DEFAULT TEMPORARY TABLESPACE temp TEMPFILE '/oracle/oradata/&db_name_val/temp01.dbf' SIZE 20M
UNDO TABLESPACE UNDOTBS1 DATAFILE '/oracle/oradata/&db_name_val/undotbs01.dbf' SIZE 200M;
@?/rdbms/admin/catalog.sql
@?/rdbms/admin/catproc.sql
@?/sqlplus/admin/pubbld.sql
EOF
echo '$db_name_val:/oracle/product/12.1.0/db_1:Y' >> /etc/oratab
"
echo "Database creation is done"
cat /etc/oratab
7. Click Finish and publish this Software component using the Publish button.
Figure 25. Software Component creation – Publishing
8. We have created the RHEL 7.4 on vSphere for Oracle Database Service blueprint and Software component called OracleDB12c – Create
Database and published them. The next step is to create another blueprint called Oracle Database 12c Single Instance and add the
software component blueprint and machine blueprint into it.
9. Select Design  Blueprints  New and enter Oracle Database 12c Single Instance as Name and description as Oracle Database 12c
Single Instance Service on VMFS datastore and fill in other details as required.
10. On the left pane, click on Blueprints under Categories and select RHEL 7.4 on vSphere for Oracle Database Service blueprint and drop it
in the canvas.
11. On the left pane, click on Software Components and select OracleDB12c – Create Database and drop it on top of RHEL 7.4 on vSphere
for Oracle Database Service.
Figure 26. Blueprint creation – Defining Software component properties

12. In the Properties tab of OracleDB12c – Create Database software component, click Edit and select Show in Request for the db_name property
and finish. Now, publish this newly created blueprint and optionally Edit and activate the custom form for the blueprint. The custom form
allows you to design the look and feel of vRA forms which will be presented to the end user at the time of catalog request.
13. As a Tenant Administrator, log on to vRA and select Administration  Catalog Management  Services and create a service called
Oracle Database as a Service. Then, go to Administration  Catalog Management  Catalog Items and select Oracle Database 12c
Single Instance and associate the newly created service Oracle Database as a Service in the Service drop-down menu. You may select an
appropriate logo for this offering.
14. After associating this service with the catalog item, configure the entitlement for the Business Group who will be using the service Oracle
Database as a Service. Select Administration  Catalog Management  Entitlements and click the New icon. Enter BG1Entitlement in
the Name text field, set the status to Active, and select the Business Group BG1 to whom you want to provide access to Oracle Database as
a Service. You may also selectively provide access to the Business group users using the Users & Group input. Click Next and search for
Oracle Database as a Service under Entitled Services and add it. Click Finish.
15. Now, Business Group users can log on to vRA portal, select the Catalog tab and click on the Request button located on Oracle Database 12c
Single Instance under Oracle Database as a Service.
Figure 27. Oracle Database as a Service – Catalog

16. Upon clicking Request, the user is presented with the window below and the user needs to supply the DB instance name as shown below and
click Submit.
Figure 28. Oracle Database as a Service – New Request
17. vRA will then provision a new VM and configure the Oracle Database on it, and it is ready to serve the application. The user can check the
provisioning status of the new Oracle DB instance request in Requests tab.
Use Case 2: Demonstrate single instance Oracle Database as a Service on Oracle Automatic Storage
Management (ASM) Disk groups
This use case demonstrates creation of a blueprint for a clone based VM deployment of Oracle Database on ASM disk groups. The following are
the overview of configuration steps to be followed:
1. Preparation of a VM Template
2. Developing a blueprint that deploys Cloned VMs from the VM Template
3. Creation of a Software Component for Oracle Database creation
4. Creation of a Single Instance Oracle Database on ASM blueprint
Preparation of VM Template
1. As a vSphere Administrator, create a new VM called OracleDBonASM_RHEL74_x86.
2. Install RHEL 7.4 on the newly installed VM.
3. Add 3 disks to the VM which will act as the CRS, DATA and FRA disks in ASM and create a single partition on each disk using fdisk command.
4. Complete all the standard prerequisites for bringing up the ASM instance and the Oracle Database, i.e., swap size, required RPM packages for
both ASM and the Oracle database, the Oracle environment settings, oracle user account, permissions, etc.
5. Bring up ASM instance as described below. This was tested using Oracle 12.1.0.2 release.
a. Configure ASM and Disks
# oracleasm configure -i
# /usr/sbin/oracleasm init
# oracleasm createdisk CRSDISK1 /dev/sdb1
# oracleasm createdisk DATADISK1 /dev/sdc1
# oracleasm createdisk FRADISK1 /dev/sdd1
b. Reboot and check ASM instance starts automatically and able to see all the disks.
# oracleasm listdisks
CRSDISK1
DATADISK1
FRADISK1
# oracleasm status
Checking if ASM is loaded: yes
Checking if /dev/oracleasm is mounted: yes
6. Create a snapshot of the VM and call it as OracleDBonASM_RHEL74_x86 snapshot with ASM disks configured
7. Install Grid infrastructure using Install and Configure Oracle Grid Infrastructure for a Standalone Server option and save the response
file in the name of grid.rsp for later use in blueprint. Use asmca to configure and mount the ASM Disks after grid infrastructure installation.
8. Now install the Oracle Database software only and save the response file in the name of dbswinst.rsp for later use in blueprint.
9. Create database template called testdbtemplate.dbc using DBCA, and make sure it uses ASM disks for data. Usually the template will be
created in $ORACLE_HOME/assistants/dbca/templates.
10. Create a directory called /home/oracle/bootstrap and copy testdbtemplate.dbc there. Set the ownership to oracle:oinstall for the directory
and the template file.
11. Optionally create a snapshot called OracleDBonASM_RHEL74_x86 snapshot taken after Grid and DB software installation.
12. Halt the VM, restore the snapshot OracleDBonASM_RHEL74_x86 snapshot with ASM disks configured.
13. Power on the VM, log on as root and install the Guest agent and the Software bootstrap agent on it. The agent installation script is available
on your vRA appliance. Download it from there as shown below:
# wget --no-check-certificate https://vRealize_VA_Hostname_fqdn/software/download/prepare_vra_template.sh
Example: # wget --no-check-certificate https://vra.dbaas.local/software/download/prepare_vra_template.sh
# chmod +x prepare_vra_template.sh
# ./prepare_vra_template.sh
Provide the IaaS Web Manager FQDN, vRA FQDN and credentials as requested by the script.
14. Create a VM template called OracleDBonASM_RHEL74_x86_Template using the Clone to Template option.
Note
The Guest agent and Software bootstrap agent assist in software provisioning on the cloned VM, using interpreters such as Bash shell and
PowerShell to execute the scripts. In our case, we used a Bash shell script which will create the database on the cloned VM.
Developing a Blueprint that deploys Cloned VMs from VM Template

Follow the same procedure described in Use Case 1 for creating a blueprint that deploys the VM Template, using an appropriate blueprint name,
and use OracleDBonASM_RHEL74_x86_Template in the blueprint.
Creation of Software Component for Oracle Database Creation

Follow the same procedure described in Use Case 1 for creating the software component blueprint that creates the database and name it
uniquely. In the Install Lifecycle Stage action script, copy and paste the script in Table 8 below.
Table 8. Oracle 12c – Create database using response files and DB template script
#!/bin/bash
#
# NOTE: It is assumed that /home/oracle/bootstrap has already been created
# and db template has been copied there.
# For example: /home/oracle/bootstrap/testdbtemplate.dbc with oracle:oinstall as ownership of the file
# $db_name has been used in DB creation using DBCA command in below script.
mkdir -p /home/grid/bootstrap
# grid.rsp content has been used below and set password parameters for SYSASM and SNMP monitor accordingly
echo "Creating /home/grid/bootstrap/grid.rsp"
cat <<EOF > /home/grid/bootstrap/grid.rsp

oracle.install.responseFileVersion=/oracle/install/rspfmt_crsinstall_response_schema_v12.1.0
ORACLE_HOSTNAME=`hostname`.dbaas.local
INVENTORY_LOCATION=/u01/app/oraInventory
SELECTED_LANGUAGES=en
oracle.install.option=HA_CONFIG
ORACLE_BASE=/u01/app/grid
ORACLE_HOME=/u01/app/grid/12.1.0.2/grid
oracle.install.asm.OSDBA=asmdba
oracle.install.asm.OSOPER=asmoper
oracle.install.asm.OSASM=asmadmin
oracle.install.crs.config.gpnp.scanName=
oracle.install.crs.config.gpnp.scanPort=
oracle.install.crs.config.ClusterType=STANDARD
oracle.install.crs.config.clusterName=
oracle.install.crs.config.gpnp.configureGNS=false
oracle.install.crs.config.autoConfigureClusterNodeVIP=true
oracle.install.crs.config.gpnp.gnsOption=CREATE_NEW_GNS
oracle.install.crs.config.gpnp.gnsClientDataFile=
oracle.install.crs.config.gpnp.gnsSubDomain=
oracle.install.crs.config.gpnp.gnsVIPAddress=
oracle.install.crs.config.clusterNodes=
oracle.install.crs.config.networkInterfaceList=
oracle.install.crs.config.storageOption=
oracle.install.crs.config.sharedFileSystemStorage.votingDiskLocations=
oracle.install.crs.config.sharedFileSystemStorage.votingDiskRedundancy=NORMAL
oracle.install.crs.config.sharedFileSystemStorage.ocrLocations=
oracle.install.crs.config.sharedFileSystemStorage.ocrRedundancy=NORMAL
oracle.install.crs.config.useIPMI=false
oracle.install.crs.config.ipmi.bmcUsername=
oracle.install.crs.config.ipmi.bmcPassword=
oracle.install.asm.SYSASMPassword=Password1234
oracle.install.asm.diskGroup.name=CRS
oracle.install.asm.diskGroup.redundancy=EXTERNAL
oracle.install.asm.diskGroup.AUSize=1
oracle.install.asm.diskGroup.disks=ORCL:CRSDISK1
oracle.install.asm.diskGroup.diskDiscoveryString=
oracle.install.asm.monitorPassword=Password1234
oracle.install.asm.ClientDataFile=
oracle.install.crs.config.ignoreDownNodes=false
oracle.install.config.managementOption=NONE
oracle.install.config.omsHost=
oracle.install.config.omsPort=0
oracle.install.config.emAdminUser=
oracle.install.config.emAdminPassword=
EOF
echo "Setting permission for /home/grid/bootstrap/grid.rsp"

chmod 777 /home/grid/bootstrap/grid.rsp
# Download grid sw and unzip it at /home/grid/source/grid

echo "Executing grid runInstaller in silent mode using grid.rsp"
su - grid -c "/home/grid/source/grid/runInstaller -silent -responseFile /home/grid/bootstrap/grid.rsp"
echo "sleeping for 300 Seconds.. So that grid gets installed"

sleep 300
echo "Executing orainstRoot.sh ..."

/u01/app/oraInventory/orainstRoot.sh
echo "Executing root.sh ..."

/u01/app/grid/12.1.0.2/grid/root.sh
echo "Creating gridcfgrsp.properties..."

cat <<EOF > /home/grid/bootstrap/gridcfgrsp.properties
oracle.assistants.asm|S_ASMPASSWORD=Password1234
oracle.assistants.asm|S_ASMMONITORPASSWORD=Password1234
EOF
echo "Setting read access for gridcfgrsp.properties..."

chmod 777 /home/grid/bootstrap/gridcfgrsp.properties
echo "Executing configToolAllCommands..."

su - grid -c "/u01/app/grid/12.1.0.2/grid/cfgtoollogs/configToolAllCommands
RESPONSE_FILE=/home/grid/bootstrap/gridcfgrsp.properties"
# Below script creates and mounts ASM diskgroups DATA and FRA
echo "Creating asmdgcreate.sh..."
cat <<EOF > /home/grid/bootstrap/asmdgcreate.sh

#!/bin/bash
# Grid installation has already created CRS diskgroup and mounted it.
# We just need to create DATA and FRA diskgroup.
/u01/app/grid/12.1.0.2/grid/bin/asmca -silent -oui_internal -configureASM -diskGroupName DATA -diskList

ORCL:DATADISK1 -redundancy EXTERNAL -au_size 1 -sysAsmPassword Password1234 -asmsnmpPassword Password1234
/u01/app/grid/12.1.0.2/grid/bin/asmca -silent -oui_internal -configureASM -diskGroupName FRA -diskList

ORCL:FRADISK1 -redundancy EXTERNAL -au_size 1 -sysAsmPassword Password1234 -asmsnmpPassword Password1234
EOF
echo "Setting execution permission for asmdgcreate.sh..."

chmod 777 /home/grid/bootstrap/asmdgcreate.sh
echo "Executing asmdgcreate.sh..."

su - grid -c "/home/grid/bootstrap/asmdgcreate.sh"
echo "Creating /home/oracle/bootstrap"

mkdir -p /home/oracle/bootstrap
chown oracle:oinstall /home/oracle/bootstrap
echo "Creating dbswinst.rsp..."

cat <<EOF > /home/oracle/bootstrap/dbswinst.rsp
oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v12.1.0
oracle.install.option=INSTALL_DB_SWONLY
ORACLE_HOSTNAME=`hostname`
UNIX_GROUP_NAME=oinstall
INVENTORY_LOCATION=/u01/app/oraInventory
SELECTED_LANGUAGES=en
ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/db_1
ORACLE_BASE=/u01/app/oracle
oracle.install.db.InstallEdition=EE
oracle.install.db.DBA_GROUP=dba
oracle.install.db.OPER_GROUP=oper
oracle.install.db.BACKUPDBA_GROUP=backupdba
oracle.install.db.DGDBA_GROUP=dgdba
oracle.install.db.KMDBA_GROUP=kmdba
oracle.install.db.isRACOneInstall=false
oracle.install.db.rac.serverpoolCardinality=0
oracle.install.db.config.starterdb.type=GENERAL_PURPOSE
oracle.install.db.ConfigureAsContainerDB=false
oracle.install.db.config.starterdb.memoryOption=false
oracle.install.db.config.starterdb.installExampleSchemas=false
oracle.install.db.config.starterdb.managementOption=DEFAULT
oracle.install.db.config.starterdb.omsPort=0
oracle.install.db.config.starterdb.enableRecovery=false
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
DECLINE_SECURITY_UPDATES=true
EOF
echo "Setting execution permission for dbswinst.rsp..."

chmod 777 /home/oracle/bootstrap/dbswinst.rsp
chown oracle:oinstall /home/oracle/bootstrap/dbswinst.rsp
# Download Oracle DB sw and unzip it at /home/oracle/source/oracle
echo "Executing runInstaller for installing db sw..."

su - oracle -c "/home/oracle/source/database/runInstaller -silent -responseFile
/home/oracle/bootstrap/dbswinst.rsp"
echo "Sleeping for 150 Sec.."

# Sleeping time can be customized based on time taken for oracle db software installation.
sleep 150
/u01/app/oracle/product/12.1.0.2/db_1/root.sh
# Create Database template and copy it in the golden image in the directory below
# By default, DB template will be at /u01/app/oracle/product/12.1.0.2/db_1/assistants/dbca/templates
# This script uses template called /home/oracle/bootstrap/testdbtemplate.dbc
echo "Setting up ownership for testdbtemplate.dbc..."

chown oracle:oinstall /home/oracle/bootstrap/testdbtemplate.dbc
echo "Creating dbca.sh..."

cat <<EOF > /home/oracle/bootstrap/dbca.sh
#!/bin/bash
dbca -silent -createDatabase -templateName /home/oracle/bootstrap/testdbtemplate.dbc -gdbname
"$db_name".dbaas.local -sid $db_name -emConfiguration LOCAL -sysPassword Password1234 -systemPassword
Password1234
EOF
echo "Setting execution permission for asmdgcreate.sh..."

chmod 777 /home/oracle/bootstrap/dbca.sh
echo "Executing dbca..."

su - oracle -c "/home/oracle/bootstrap/dbca.sh"
Creation of “Single Instance Oracle Database on ASM” Blueprint

Follow the same procedure described in Use Case 1 for creating a blueprint that offers Single Instance Oracle Database. Name the blueprint as
Single Instance Oracle Database on ASM.
Use Case 3: Demonstrate Oracle Pluggable Database as a Service on an Oracle Container Database
Oracle Multitenant Architecture helps you to run an Oracle database as a multitenant container database (CDB) and a CDB can have zero, one or
more pluggable databases (PDBs) in it. A PDB does not have its own instance, rather it uses the CDB’s instance. Refer to Oracle documentation
for more details on Oracle Multitenant Architecture. In this use case, a business group user will be able to request an Oracle pluggable database
on an already existing Oracle container database.
Figure 29. Oracle container database and pluggable database architecture
This use case demonstrates creation of a vRealize Orchestrator (vRO) workflow that will connect to an already existing CDB using SSH and
create a PDB. The user just needs to provide a name for the PDB in the catalog request. The following are the brief overview of configuration
steps required to complete this task:
1. Preparation of the CDB on VM or bare-metal HPE Synergy Compute Module

2. Develop a vRealize Orchestrator (vRO) workflow called Create Oracle PDB
3. Create an XaaS blueprint called Oracle Pluggable Database as a Service using Create Oracle PDB workflow
Preparation of CDB on VM or bare-metal HPE Synergy Compute Module

1. Create a new VM in vCenter or provision a bare-metal HPE Synergy Compute Module using HPE OneView.
2. Install and configure the OS and Oracle 12c container database as documented in Oracle documentation and make sure the CDB is up and
running. Take note of the hostname or IP address of the Oracle CDB server.
3. Create a bash shell script called /home/oracle/bootstrap/createPDB.sh on the CDB server as the oracle user and paste the content from
Table 9 below.
Table 9. Oracle 12c – Create pluggable database script
#!/bin/bash
# $1 is collected from catalog request and fed into this script as newpdb.
# For every PDB request, an admin user “<pdbname>adm” is created and its password is Password1234
# Please update the environment parameter as per your setup
newpdb=$1
admin=$newpdb"adm"
export ORACLE_UNQNAME=cdb
export ORACLE_SID=cdb
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOSTNAME=oracle12asmvm
export ORACLE_TERM=xterm
export ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/db_1
/u01/app/oracle/product/12.1.0.2/db_1/bin/sqlplus /nolog <<EOF

connect/as sysdba
show con_id
select con_id,name,open_mode,open_time from v\$pdbs;
CREATE PLUGGABLE DATABASE $newpdb

ADMIN USER $admin IDENTIFIED BY Password234
ROLES = (connect)
DEFAULT TABLESPACE users
DATAFILE '+DATA' SIZE 500M AUTOEXTEND ON
STORAGE (MAXSIZE 10G)
PATH_PREFIX = '+DATA';
alter pluggable database $newpdb open read write;
show con_id
select con_id,name,open_mode,open_time from v$pdbs;
set linesize 500

set pagesize 100
col name format a20
col db_file_name format a80
select b.con_id,b.name,a.name as db_file_name from v\$datafile a, v$pdbs b
where a.con_id= b.con_id;
EOF
4. Make sure the file execution permission is set for oracle user and ownership belongs to oracle:oinstall.
Developing a vRealize Orchestrator (vRO) workflow called Create Oracle PDB

1. Log on to vRO and create a new folder called DBaaS_demo and create a new workflow.
2. Name the workflow Create Oracle PDB and add the following Attributes and customize the values for your environment as shown in Figure
30 below in the General tab.
Figure 30. New workflow General tab – Adding attributes

3. In the Inputs tab, create a Parameter called pdbname.
Figure 31. New workflow Inputs tab – Adding parameters
4. In the Schema tab, drag and drop the Scriptable Task from Generic task and name it Create Oracle PDB.
5. Select the Scriptable Task and click on Visual Binding.
6. Make the connections between the In Parameters and IN values of the Create Oracle PDB as shown in Figure 32 below. If needed, OUT
parameters may be added as well.
Figure 32. New workflow Schema tab – Scriptable task’s visual binding of parameters
7. Add the following content in the Scripting tab and click Save and Close.
Table 10. Oracle 12c – Create pluggable database – workflow Java code
var session = null;
var encoding = null;
try {
session = new SSHSession(cdbhostNameOrIP, username);
session.connectWithPasswordOrIdentity(true , passwword);
System.log("Connected!");
cmd = "/home/oracle/bootstrap/createPDB.sh " + pdbname;

System.log("Executing '" + cmd + "' using encoding '" + (encoding ? encoding : "Default System
Encoding") + "'");
session.setEncoding(encoding);
session.executeCommand(cmd, true);
output = session.getOutput();
error = session.getError();
exitCode = session.exitCode;
System.log("Output: '" + output + "'");

System.log("Error: '" + error + "'");
System.log("Exit code: '" + exitCode + "'");
} catch (e) {
throw "Unable to execute command: " + e;
} finally {
if (session) {
session.disconnect();
}
}
8. Execute and verify that the workflow is working as expected.
Creation of the XaaS blueprint – Oracle Pluggable Database as a Service

1. Log on to vRA and select Design  XaaS  XaaS Blueprints and click New.
2. Select the workflow Create Oracle PDB as shown in Figure 33 below and click Next.
Figure 33. New XaaS Blueprint creation – selecting vRO workflow

3. In the Name input text field of the General tab, enter Oracle Pluggable Database as a Service and click Next.
4. In the Blueprint Form tab, select the parameter and in the Label input text field, type Enter PDB Name, click Apply, click Next twice and
Finish.
Figure 34. New XaaS Blueprint creation – Blueprint form design
5. Publish the blueprint and select Administration  Catalog Management  Catalog Items  Oracle Pluggable Database as a Service
and associate it with the service Oracle Database as a Service.
6. Now, business group users can request a new PDB and it will be created in seconds.
Use Case 4: Demonstrate Oracle Database as a Service provisioning on bare-metal HPE Synergy Compute
Module using HPE OneView Plug-in for vRO and HPE Synergy Image Streamer
With the combination of HPE OneView for VMware vRO and HPE Synergy Image Streamer, it is possible to provide Database as a Service on
bare-metal HPE Synergy Compute Modules. This is possible using the workflow called Assign Server Profile from Template. Below are the
configuration steps that need to be followed.
Note
If you are using the embedded version of vRealize Orchestrator in vRA, you will need to manually start the Orchestrator Control Center service by
logging into vRA console and then installing the plug-in. Refer to VMware documentation for more details.
1. Download, install, and configure HPE OneView for VMware vRO in vRealize Orchestrator. Refer to HPE OneView for VMware vRealize
Orchestrator User Guide for more details.
2. After configuring the plug-in in vRO, you should be able to see HPE OneView resources listed down under the vRO Inventory tab. Figure 35
below depicts the same.
Figure 35. HPE OneView resources listed down under vRO Inventory
3. In the Workflow tab, you will notice that HPE OneView-related workflows have been added under Library  HPE OneView and are shown
below in Figure 36.
Figure 36. HPE OneView workflows
4. Let’s create an Anything as a Service (XaaS) blueprint that will utilize the workflow Assign Server Profile from Template for provisioning a
bare-metal HPE Synergy Compute Module as an Oracle Database server. The following are the assumptions made with respect to HPE
OneView and HPE Synergy Image Streamer configuration.
a. HPE Image Streamer has been configured and a deployment plan has been created which will install the OS, Oracle Database server, and
customize the OS and Oracle instance using plan scripts.
Note
Refer to HPE Reference Architecture for deploying Oracle 12c with HPE Synergy Image Streamer for details on creating a deployment plan
which will install the OS, Oracle Database server and customize the OS and Oracle instance using plan scripts.
b. An HPE OneView Server Profile Template (SPT) has been created and it includes the above mentioned deployment plan, and all the user
input, such as IP address for the server, SAN disk assignments, etc., have been prefilled using default custom values in the deployment
plan.
c. The server hardware should be powered off and should not have a server profile assigned.
Note
By default, the Assign Server Profile from Template workflow accepts only the server profile template name, server hardware, new server
profile name and Boolean value for ignoring server hardware health warnings, while applying the profile via a blueprint. Therefore, it is mandatory
that SPT should not ask for any other input other than listed above. If it asks, the workflow will fail to deploy the server profile. All the values other
than what is listed here should be prepopulated using custom default values in the Deployment Plan.
5. To create a blueprint, log on as Software Architect in vRA and select Design  XaaS  XaaS Blueprints.
6. Click on the New icon and select Assign Server Profile from Template from Orchestrator  Library  HPE OneView  Server
Hardware and click Next.
Figure 37. New XaaS Blueprint creation using Assign Server Profile from Template
7. Enter Oracle12c on HPE Synergy Compute Module in the Name input text box under the General tab and click Next.
8. Leave the default settings in the other tabs and click Finish.
9. Publish the blueprint and go to Administration  Catalog Management  Catalog Items.
10. Click on Oracle12c on HPE Synergy Compute Module and select Oracle Database as a Service under the Service drop-down list and
press OK. Now, the service is available to the end user and they can request Oracle Database 12c provisioning on selected HPE Synergy
server hardware. Figure 38 below, shows the catalog request form that will be presented to the end user, when requested through the self-
service portal.
Figure 38. New catalog request – Oracle Database as a Service on bare-metal HPE Synergy Compute Module
11. As shown in Figure 38 above, use the Select link to browse through OneView inventory and select SPT, Server Hardware and enter the new
profile name. Submit the request. In a matter of minutes, a bare-metal HPE Synergy Compute Module will be provisioned with the Oracle
database software.
Downloading and importing Out of the Box (OOTB) blueprints from VMware Marketplace
There are readily available blueprints from VMware Marketplace and they can be imported into vRA and vRO for use by infrastructure and
software architects. For example, you can download OOTB blueprints that add and delete DNS entries in a Windows DNS server.
1. Download VMware vRealize CloudClient 4.5 or later from https://code.vmware.com/tool/cloudclient and unzip it. This tool helps you to upload
the OOTB Blueprint into vRA and vRO using vRA APIs.
2. Download Add DNS Record blueprint, install and use the blueprint as described in the VMware documentation.
Download Delete DNS Record blueprint, install and use the blueprint as described in the VMware documentation.
Summary
This document described how to build a private cloud and demonstrated several different ways to implement Oracle Database as a Service using
VMware vCloud Suite on HPE Synergy Compute Modules with HPE Nimble All Flash AF60 array. HPE Nimble Storage delivers a unique set of
storage data services that are ideal for virtualized environments. The combination of HPE Synergy composable infrastructure, HPE Nimble All
Flash Arrays and VMware vCloud Suite delivers the following benefits.
• HPE Synergy’s unique built-in software intelligence, auto discovery capabilities, fluid resource pools and programmable infrastructure
foundation eliminates the operational overhead of traditional deployments and helps to manage the complete lifecycle management of private
cloud platforms.
• HPE Synergy Image Streamer is a new approach to deployment and updates for composable infrastructure. This management appliance
works with HPE Synergy Composer and enables software-defined control over physical compute modules with operating system provisioning.
• Hybrid cloud management platform – vRealize Suite (included in VMware vCloud Suite) allows customers to quickly build an Oracle database
using a pre-defined blueprint in a private cloud environment with secure and consistent operations. vRealize Orchestrator workflows and
vRealize Automation’s Software Authoring enables solution architects to design and automate the deployment of all kinds of applications with
the click of a button.
• HPE OneView for VMware vRealize Orchestrator enables cloud-admins to integrate HPE OneView workflows into other automation workflows,
creating end-to-end automation from server hardware to application provisioning.
• HPE Nimble Storage All Flash Arrays combine a flash-efficient architecture with HPE InfoSight predictive analytics to achieve fast, reliable
access to data and 99.9999% guaranteed availability for private cloud environments. Data deduplication and compression reduces data
footprint and overall storage cost.
• HPE Nimble storage VVol integration into VMware’s Storage Policy Based Management (SPBM) simplifies common storage management
tasks like LUN provisioning and management. By using policies to automatically provision LUNs at the time of VM creation, no pre-
provisioning of datastores is required, reducing administrative costs by eliminating tedious, repetitive tasks. Applications directly benefit from
this new, fine-grained level of interaction with critical storage resources. Automatic space reclamation when VMs are deleted or moved ensures
that no space is wasted and the array maintains a thin footprint.
Appendix A: Bill of Materials

This reference architecture used the following bill of materials (BOM) for testing and configuration.
Note
Part numbers are as of time of testing and subject to change. The bill of materials does not include complete support options or other rack and
power requirements. If you have questions regarding ordering, consult with your HPE Reseller or HPE Sales Representative for more details at
http://hpe.com/us/en/services/consulting.html.
Table A-1. Rack Infrastructure

Qty Part Number Description
1 P9K40A HPE 42U 600x1200 Ent G2 Shock Rack
2 P9S15A HPE G2 Metered/Switched 4.9kVA/L6-30P 24A/208V Outlets (20) C13, (4) C19/Vertical NA/ JP PDU
Table A-2. Management Cluster servers (HPE Synergy 480 Gen10 Compute Modules)
4 871942-B21 HPE SY 480 Gen10 CTO Prem Cmpt Mdl
4 872138-L21 HPE SY 480/660 Gen10 Xeon-G 6142 FIO Kit
4 872138-B21 HPE SY 480/660 Gen10 Xeon-G 6142 Kit
64 815098-B21 HPE 16GB 1Rx4 PC4-2666V-R Smart Kit
8 872475-B21 HPE 300GB SAS 10K SFF SC DS HDD
4 875242-B21 HPE 96W Smart Storage Battery 260mm Cbl
4 871573-B21 HPE SAS Cable for P416ie-m SR G10 Ctrlr
4 777430-B21 HPE Synergy 3820C 10/20Gb CNA
4 777452-B21 HPE Synergy 3830C 16G FC HBA
4 804428-B21 HPE Smart Array P416ie-m SR Gen10 Ctrlr
Table A-3. HPE Synergy 12000 Frame

1 797740-B21 HPE Synergy12000 CTO Frame 1xFLM 10x Fan
2 794502-B23 HPE VC SE 40Gb F8 Module
2 779227-B21 HPE Virtual Connect SE 16Gb Fibre Channel Module for Synergy
1 798096-B21 HPE Synergy 12000F 6x 2650W AC TiFIO PS
2 804353-B21 HPE Synergy Composer
1 804942-B21 HPE Synergy Frame Link Module
1 804943-B21 HPE Synergy 12000 Frame 4x Lift Handle
1 804938-B21 HPE Synergy 12000 Frame Rack Rail Option
4 817040-B21 HPE Synergy 40 / 4 x 10GbE / 4 x 8GBFC QSFP XCVR
2 N3R43A HPE Synergy 8Gb FC License Upgrade
4 K2Q46A HPE MPO to 4x LC 5m Cable

Table A-4. Compute servers (HPE Synergy 480 Gen10 Compute Modules)
2 871942-B21 HPE SY 480 Gen10 CTO Prem Cmpt Mdl
2 872138-L21 HPE SY 480/660 Gen10 Xeon-G 6142 FIO Kit
2 872138-B21 HPE SY 480/660 Gen10 Xeon-G 6142 Kit
32 815098-B21 HPE 16GB 1Rx4 PC4-2666V-R Smart Kit
4 872475-B21 HPE 300GB SAS 10K SFF SC DS HDD
2 875242-B21 HPE 96W Smart Storage Battery 260mm Cbl
2 871573-B21 HPE SAS Cable for P416ie-m SR G10 Ctrlr
2 777430-B21 HPE Synergy 3820C 10/20Gb CNA
2 777452-B21 HPE Synergy 3830C 16G FC HBA
2 804428-B21 HPE Smart Array P416ie-m SR Gen10 Ctrlr
Table A-5. HPE Nimble Storage – All Flash Array – AF60
1 Q8H42A HPE NS AF60 All Flash CTO Base Array
1 Q8B91B HPE NS 4x16Gb FC 2p FIO Adptr Kit
1 Q8G27B HPE NS NOS Default FIO Software
1 Q8H46A HPE NS AF60/80 11.52TB FIO Flash Bndl
2 Q8J27A HPE NS C13 to C14 FIO Power Cord
Table A-6. Common Ethernet cabling (adjust lengths to meet the distance requirements of Customer provided 1Gb network infra)
10 C7536A HPE Ethernet Cable 14ft CAT5 RJ45 M/M
Table A-7. HPE FF 5940 2-slot Switch with HPE 5930 8-Port QSFP+ Module
2 JH397A HPE FF 5940 2-slot switch
4 JG552A HPE X711 Frt(prt) Bck(pwr) HV Fan Tray
4 JC680A HPE 58x0AF 650W AC Power Supply
4 JC680A-B2B INCLUDED: Jumper Cable – NA/JP/TW
2 JH183A HPE 5930 8-Port QSFP+ Module
4 JG327A HPE X240 40G QSFP+ QSFP+ 3M DAC Cable

Table A-8. HPE SN6000B SAN Switch

2 QR481B HPE SN6000B 16Gb 48/48 Pwr Pk+ FC Swch
48 QK724A HPE B-series 16Gb SFP+SW XCVR
32 QK734A HPE Premier Flex LC/LC OM4 2f 5m Cbl

Resources and additional links

HPE Reference Architectures, hpe.com/info/ra
HPE Servers, hpe.com/servers
HPE Storage, hpe.com/storage

HPE Networking, hpe.com/networking
HPE Technology Consulting Services, hpe.com/us/en/services/consulting.html
HPE OneView for VMware vCenter Grow Cluster White Paper,

https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00036306en_us&docLocale=en_US
HPE Reference Architecture for deploying Oracle 12c with HPE Synergy Image Streamer,
https://h20195.www2.hpe.com/v2/getdocument.aspx?docname=a00001298enw
HPE Nimble Storage Deployment Considerations for Oracle Database,

https://infosight.hpe.com/InfoSight/media/cms/active/public/tmg_HPE_Nimble_Storage_Deployment_Considerations_for_Oracle_Database_doc_v
ersion_family.pdf
VMware VVols on HPE Nimble Storage Implementation Guide,

https://h20195.www2.hpe.com/V2/GetDocument.aspx?docname=a00044881enw
vRealize Automation Support Matrix,

https://docs.vmware.com/en/vRealize-Automation/7.0/vrealize-automation-6x7x-support-matrix.pdf
vRealize Automation 7.4 Reference Architecture,

https://docs.vmware.com/en/vRealize-Automation/7.4/vrealize-automation-74-reference-architecture.pdf
Understanding Oracle Certification, Support and Licensing for VMware environments,

vmware.com/content/dam/digitalmarketing/vmware/en/pdf/whitepaper/solutions/oracle/understanding_oracle_certification_support_licensing_v
mware_environments-white-paper.pdf
VMware vRealize Automation Foundations and Concepts,

https://docs.vmware.com/en/vRealize-Automation/7.4/vrealize-automation-74-foundations-and-concepts.pdf
To help us improve our documents, please provide feedback at hpe.com/contact/feedback.
Sign up for updates
© Copyright 2018 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice.
The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard
Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
VMware is a registered trademark or trademark of VMware, Inc. and its subsidiaries in the United States and other jurisdictions. Oracle
and Java are registered trademarks of Oracle and/or its affiliates. Red Hat is a registered trademark of Red Hat, Inc. in the United States
and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Microsoft, Windows Server, and
Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
a00058269enw, October 2018

HPEDBaaSusing VRE

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

HPEDBaaSusing VRE

Caricato da

Copyright:

Formati disponibili

Reference Architecture

HPE Reference Architecture for

• Reduced operational cost by

This Reference Architecture describes solution testing performed in October 2018.

HPE Synergy Composer

HPE Synergy Image Streamer

HPE Synergy Gen10 Compute Modules

Figure 2. HPE Synergy 480 Gen10 Compute Module

HPE OneView for VMware vCenter (HPE OV4VC)

HPE OneView for VMware vRealize Orchestrator (vRO)

HPE Nimble All Flash Array

Figure 3. HPE Nimble All Flash Arrays

Figure 4. HPE InfoSight – Operation Dashboard

Figure 5. HPE InfoSight – Storage Pool List

Figure 6. HPE InfoSight – VMware Cluster view

Figure 7. HPE InfoSight – VMware VM view

VMware vCloud Suite

Figure 8. VMware vCloud Suite components

VMware vRealize Suite contains:

HPE FlexFabric 5940 2-slot switch Network switch

VMware vSphere ESXi HPE Custom Image for ESXi 6.5U2

VMware vRealize Automation with embedded version of 7.4

VMware vRealize Business for Cloud 7.4

VMware vRealize Operations Manager 6.7

VMware vCenter Server Appliance 6.5 U2b

HPE OneView for VMware vRealize Orchestrator 1.0

HPE OneView for vCenter (OV4VC) 9.1

Oracle 12c Database and Grid Software 12.0.*

Best practices and configuration guidance

VMware vRealize Suite component implementation best practices

HPE Nimble All-Flash Array configuration

Installing VMware vCloud Suite components

• VMware vSphere (ESXi Hypervisor)

Small Deployment 10,000 500 10

Medium Deployment 30,000 1000 50

Large Deployment 50,000 2500 100

Figure 9. Oracle Database as a Service – Logical deployment diagram

Configuring VMware vRealize Automation (vRA)

Components DNS Records

vRealize Automation appliance A Record: vra1.dbaas.local

Infrastructure Web and Manager Server A Record: winiaasvm1.dbaas.local

Microsoft SQL DB Server for IaaS Component A Record: mssql.dbaas.local

vRealize Business for Cloud appliance A Record: vrb.dbaas.local

Integrate and configure vRealize Business for Cloud (vRBC)

Figure 10. Registering vRealize Business for Cloud in vRealize Automation

Follow the steps below to configure cost for blueprints:

Figure 11. Configuring pricing in vRealize Business for Cloud

Figure 12. Viewing pricing details of requested catalog item

Figure 13. Viewing pricing details of requested catalog item

1. Preparation of VM Template (commonly known as Golden Image preparation)

Figure 15. vCenter – Customization Specification Manager

Developing a blueprint that deploys cloned VMs

DB Size vCPU Memory in GB Storage in GB

1. Log in as IaaS architect and select Design  Blueprints.

Figure 16. Blueprint creation – New Blueprint General tab

Figure 17. Blueprint creation – vSphere(vCenter) Machine – General tab

Figure 18. Blueprint creation – vSphere(vCenter) Machine – Build Information tab

Figure 19. Blueprint creation – vSphere(vCenter) Machine – Machine Resources tab

Figure 20. Blueprint creation – vSphere(vCenter) Machine – Storage tab

Figure 21. Blueprint creation – vSphere(vCenter) Machine – Network tab

20. Click Finish.

Creation of Software Component for Oracle Database Creation

Figure 22. Software Component creation – New Software General tab

Figure 23. Software Component creation – New Software Properties tab