Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Planning the BMC Compact RDS deployment


This topic provides information that you can use to plan the installation, deployment, and configuration of the BMC Compact 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 Compact RDS image, you need the following items before you deploy the OVF:

Item

Purpose

Details

Windows client computer (x)

Hosts the BMC Server Automation Console and BMC Remedy Developer Studio

The Windows client is optional. If required, you can install this component on a jump box.

vCenter

Used with BMC Application Server and BMC Cloud Lifecycle Management solution

Used as a platform for creating a virtual image and hosting the VM appliance. vCenter version 5.x is required for installation.

ESX

Used with the vCenter as a hosting location for virtual machines

ESX versions 5.x is required for this installation.

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 VM. Your vCenter should have at least 100 GB available for deployment.
  • vCenter details before you start deployment 

 

Note

You must maintain the OS and security patches on the BMC Cloud Lifecycle Management 4.0 VM shipped on the BMC Compact RDS image.

 

Deployment architecture and sizing

BMC Compact RDS is a small production environment, as illustrated in the following deployment architecture diagram:

CLM_3_1_Deployment_Architecture_CloudExpress_v4.png

 

BMC Compact RDS is designed for 25 concurrent users and 5000 managed VMs.

BMC Compact RDS resources and placement planning

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

Name

Disk space (GB)

Guest OS

Memory size minimum (GB)

CPU count minimum

IP address/MAC address

Comment

BMC Compact RDS

100 GB

  • 40 GB for Thin provision
  • 60 GB for Thick provision

Red Hat Linux 6.3 64-bit

16 GB

8

 

BMC Compact RDS contains preconfigured BMC Cloud Lifecycle Management and Oracle Express

Note

If necessary, you can increase the CPU and memory. The values shown are the minimum prerequisite values for  BMC Cloud Lifecycle Management products.

Compact RDS product version matrix

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

Product

Version

BMC Cloud Lifecycle Management Core (PM)

4.0 (build:47)

ITSM SSI Linux stack (only installs BMC ITSM Foundation and BMC Service Request Management)

8.1.01-SSI_8.1-R_140227-064811

BMC Remedy AR System (Linux) 

8.1.01-AR-81SP1-RC2

BMC Atrium Core

8.1.01-AR-81SP1-RTM

BMC Server Automation Server

8.5.00-416

BMC Server Automation Client

8.5.00-416

BMC Atrium Orchestrator Server

7.6.02.04-FCS

BMC Atrium Orchestrator Content

4.0.00-2013112902.4

BMC Network Automation

8.5 Patch 1

Oracle Database

Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64-bit

vCenter

Version 5.x

ESX

Version 5.x

Hotfix and patch details

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

Component

Installation status

Hotfix or patch

Atrium hotfix

Already in the RDS image

atrium-dvm-AtriumWidget* files

Blueprint hotfix

Already in the RDS image

Onboard existing VM fixes

BMC Server Automation hotfix

Already in the RDS image

SUSE Physical Server SOIs failing

Quick Start Tenant and Add Server hotfix

Already in the RDS image

 

blcontent

Already in the RDS image

8.5.00.416

BMC Server Automation Compliance content

Already in the RDS image

8.5.01

 

Where to go from here

Installing-BMC-Compact-RDS-Single-VM

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*