You must consider several core technologies when sizing a BMC Cloud Lifecycle Management environment. Sizing of each product in the value path is based on the individual load on each product's sample use case, as described in the following table. The following topics are covered in this section:
The following table explains the sizing requirements for each product in the solution.
Note
Some installations might have specific requirements and complexities that are not reflected here. You must account for these differences when designing a deployment.
| | | | |
|---|
Compact Deployment (if you use an external database) | | | | |
| | | | |
| | | | |
| | | | |
Note
The following table does not include sizing for Compact Deployment. You use a single VM for Compact Deployment to minimize hardware requirements.
The table below describes the number of nodes needed for each deployment size.
| Small
50 Peak Concurrent Users
10,000 VMs | Medium
250 Peak Concurrent Users
25,000 VMs | Large
500 Peak Concurrent Users
50,000 VMs |
|---|
BMC AR System Server – Cloud Portal and Database (Cloud Portal and Database)
RHEL 6.x (64-bit)
Oracle JDK/JRE 1.6.0_20
Apache 2.2 (32-bit)
Tomcat 6.0.26 (64-bit)
BMC Remedy AR System Server 8.1 SP1
BMC Remedy SRM 8.1 SP1
BMC Cloud Lifecycle Management 4.1 | 2 VCPU 2+GHz x1
8 GB RAM
60 GB Disk | 4 VCPU 2+GHz x2
8 GB RAM
60 GB Disk | 4 VCPU 2+GHz x3
8 GB RAM
60 GB Disk |
Cloud Portal and Database Mid Tier
RHEL 6.x (64-bit)
Oracle JDK/JRE 1.6.0_20
Apache 2.2 (32-bit)
Tomcat 6.0.26 (64-bit)
BMC Remedy AR System Mid-Tier 8.1 SP1 | 2 VCPU 2+GHz
x1
4 GB RAM
60 GB Disk | 2 VCPU 2+GHz
x2
4 GB RAM
60 GB Disk | 2 VCPU 2+GHz
x3
4 GB RAM
60 GB Disk |
Cloud Platform Manager
RHEL 6.x (64-bit)
Oracle JDK/JRE 1.6.0_20
BMC Cloud Lifecycle Management 4.1 | 4 VCPU 2+GHz x1
8 GB RAM
60 GB Disk | 8 VCPU 2+GHz x1
8 GB RAM
60 GB Disk | 8 VCPU 2+GHz x2
8 GB RAM
60 GB Disk |
Atrium Core - Web Registry Components
RHEL 6.x (64-bit)
Oracle JDK/JRE 1.6.0_20
BMC Atrium Core 8.1 SP1 | 4 VCPU 2+GHz x1
8 GB RAM
60 GB Disk | 4 VCPU 2+GHz x2
8 GB RAM
60 GB Disk | 4 VCPU 2+GHz x2
8 GB RAM
60 GB Disk |
BMC Server Automation Application Server
RHEL 6.x (64-bit)
BMC Server Automation 8.2.01 | 8 VCPU 2+GHz x1
8 GB RAM
60 GB Disk | 8 VCPU 2+GHz x2
8 GB RAM
60 GB Disk | 8 VCPU 2+GHz x3
8 GB RAM
60 GB Disk |
BMC Server Automation File Server
RHEL 6.x (64-bit)
BMC Server Automation 8.2.01 | 4 VCPU 2+GHz x1
8 GB RAM
200 GB Disk | 4 VCPU 2+GHz x2
8 GB RAM
200 GB Disk | 4 VCPU 2+GHz x2
8 GB RAM
200 GB Disk |
BMC Network Automation
RHEL 6.x (64-bit)
BMC Network Automation 8.2.02 | 2 VCPU 2+GHz x1
8 GB RAM
60 GB Disk | 2 VCPU 2+GHz x2
16 GB RAM
60 GB Disk | 4 VCPU 2+GHz x2
32 GB RAM
60 GB Disk |
BMC Atrium Orchestrator (CDP + CDP HA)
RHEL 6.x (64-bit)
BMC Atrium Orchestrator Platform 7.6.02
BMC Atrium Orchestrator Content 4.1 | 4 VCPU 2+GHz x1
8 GB RAM
60 GB Disk | 4 VCPU 2+GHz x2
8 GB RAM
60 GB Disk | 4 VCPU 2+GHz x3
8 GB RAM
60 GB Disk |
Note
BMC Server Automation sizing is based on our test that does not include compliance or auditing. Compliance jobs are CPU-intensive. For the use cases that include compliance, use the following table.
BMC Server Automation App Server
RHEL 6.x (64-bit)
BMC Server Automation 8.1 SP 1 | 8 VCPU2+GHz
x1
20 GB RAM
60 GB Disk | 8 VCPU2+GHz
x3
20 GB RAM
60 GB Disk | 8 VCPU2+GHz
x5
20 GB RAM
60 GB Disk |
Physical servers are required for the database servers. We do not recommend running databases on virtualized hardware.
Customers may choose to host product databases on single physical server or on separate servers. The decision is based on multiple factors, including, but NOT limited to H/W and Licensing cost, performance, administration & maintenance efforts and security requirements.
Note
The following table does not include sizing for Compact. You use a single database server for Compact Deployment to minimize hardware requirements.
If customers choose to host product databases on separate servers, see the sizing (and number of DB servers) mentioned below:
| | | |
|---|
Cloud Portal and Database Server +
Atrium Web Registry Database
RHEL 6.x (64-bit)
Oracle Enterprise Edition 11G R2 (64-bit) | 8 CPU-Cores 2+GHz
x1
16 GB RAM
Data Tablespace: 16 GB
Temp Tablespace: 1.5 GB
Redo Log: 500 MB x 3 | 16 CPU-Cores 2+GHz
x2
16 GB RAM
Data Tablespace: 26 GB Temp Tablespace: 1.5-2 GB
Redo Log: 500 MB x 3 | 32 CPU-Cores 2+GHz
x2
32 GB RAM
Data Tablespace: 41 GB Temp Tablespace: 2-4 GB
Redo Log: 500 MB x 3 |
BMC Server Automation Database
RHEL 6.x (64-bit)
Oracle Enterprise Edition 11G R2 (64-bit) | 4 CPU-Cores 2+GHz
x1
8 GB RAM Data Tablespace: 15 GB Temp Tablespace: 1 GB
Redo Log: 500 MB x 3 | 8 CPU-Cores 2+GHz
x2
8 GB RAM
Data Tablespace: 25 GB Temp Tablespace: 1-2 GB
Redo Log: 500 MB x 3 | 8 CPU-Cores 2+GHz
x2
16 GB RAM
Data Tablespace: 50 GB Temp Tablespace: 2 GB
Redo Log: 500 MB x 3 |
BMC Network Automation Database
RHEL 6.x (64-bit)
Oracle Enterprise Edition 11G R2 (64-bit) | 2 CPU-Cores 2+GHz
x1
4 GB RAM
Data Tablespace: 20 GB Temp Tablespace: Default | 4 CPU-Cores 2+GHz
x2
8 GB RAM Data Tablespace: 40 GB Temp Tablespace: Default | 4 CPU-Cores 2+GHz
x2
8 GB RAM
Data Tablespace: 80 GB Temp Tablespace: Default |
If customers choose to host product databases on a single server, see the sizing (and number of DB servers) mentioned below:
| | | | |
|---|
Database Server
RHEL 6.x (64-bit)
Oracle Enterprise Edition 11G R2 (64-bit)
3 separate database instances:
Cloud Portal and Database Server + Atrium Web Registry
BMC Server Automation Database
BMC Network Automation Database | 8 VCPU 2+GHz x1
16 GB RAM
60 GB Disk | 16 CPU-Cores 2+GHz x1
32 GB RAM
80 GB Disk | 32 CPU-Cores 2+GHz x2
32 GB RAM
120 GB Disk | 64 CPU-Cores 2+GHz x2+N
64 GB RAM
210 GB Disk |
Note
- The disk size mentioned above indicates disk space consumed by the data and indexes. Please include additional space for OS and other software installed. Below is approximate distribution between data and index space for reference purpose:
- For BMC Server Automation database: 40% Data , 60% Index
- For BMC Network Automation, Cloud DB and Enterprise AR server databases: 60% Data and 40% Index
- Atrium Web Registry database is not very transactional in nature and hence much smaller in size. For all Small, Medium and Large deployments, this database can be installed on the same Oracle server instance.
- The sizing above is based on benchmark tests for CLM specific use cases only
- Transaction Log sizing is mainly driven by two factors. Customers should size transaction log files based these factors:
- Database recovery model
- DB backup strategy and frequency