Planning the BMC Small RDS deployment

This topic provides information that you can use to plan the installation, deployment, and configuration of the BMC Small RDS solution. Before you install the solution, ensure that you carefully review the prerequisites, resources, product versions, and hotfix and patch details.

Before you begin

To install the BMC Small RDS image, you need the following items before you deploy the OVF:

In addition, you need:

• Sufficient IP addresses from DHCP or static IP. If the IP addresses are static, make the required changes in the DNS before deployment. If the IP of the servers is DHCP-enabled, ensure that you do not change it.
• Sufficient disk space to provision the VMs. Your vCenter should have at least 100 GB available for deployment.
• vCenter details before you start deployment.
•  Hardware required to host Oracle databases for BMC Cloud Lifecycle Management. 

Small RDS strategy

The Small RDS images deployment approach lets you easily move from Single node to HA RDS. Alias names like csm-ar, csm-mt, and so on, are used. so that you can easily use the same alias names as Load Balancer or Cluster virtual hostnames when you want to migrate to HA. As a result, this minimizes the downtime for HA-related configuration. Similarly for cluster support, there are installed and configured Platform and and BMC Network Administration products on the /gfs directory. 

Deployment and configuration of CLM 4.0 Small RDS is similar to earlier version of CLM RDS, except that all the integrations use csm-*** alias names –  instead of the clm-*** hostnames of the machines. All the product integrations use csm-*** names which you must add to the hosts file.

General information about the Small RDS production images

The BMC Cloud Lifecycle Management 4.0 production images are provided as OVF templates on a USB drive. These consist of 11 preconfigured virtual machines. The BMC Cloud Lifecycle Management 4.0 production images are built on Red Hat Enterprise Linux 6.3. The following images are installed as a part of the solution:

•  clm-bao – BMC Atrium Orchestrator
•  clm-bna – BMC Network Automation
•  clm-bsa – BMC Server Automation
•  clm-ar - Enterprise AR
•  clm-aws - BMC Atrium Web Services
•  clm-mt – Enterprise AR Mid-Tier
•  clm-bco – BMC Capacity Optimization
•  clm-pm - Cloud Platform Manager (OSGi)
•  clm-pxe - BMC Server Automation PXE server
•  clm-planner – BMC Planner Machine with auto deploy scripts
•  clm-autodeploy - Auto Deploy VM use for OVF and DB changes using automation.
•  Database backup files

Logical backups are also installed (for example, BCAN.dmp, BLADELOGIC.dmp, ARADMIN.dmp, BCO_DASH.dmp, BCO_OWN.dmp, and BCO_REP.dmp).

Prerequisites for Oracle 11g R2 database

• Database migration using logical backup files provides the flexibility of Oracle server. 
• You can use an 11g R2 Oracle server or an 11g R2 Oracle RAC
• Configure a database physical server with the following details:
  • Oracle an 11g R2 Oracle Server or an 11g R2 2-node Oracle RAC with two database instances for database migration.
  • 8 CPU, 16 GB RAM for each Instance total 16 CPU, 32 GB RAM for two database instances.
  • Oracle-certified database administrator must be present to help with the migration.

BMC Small RDS resources and placement planning

BMC Small RDS consumes the following resources. Use this information for placement planning.

Small RDS product version matrix

BMC Small RDS contains the products and versions listed in the following table: 

Hotfix and patch details

BMC Compact RDS contains the product hotfixes and patches listed in the following table: 

Where to go from here

Auto-deploying BMC Small RDS