Sizing Windows
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 the sample use case of each product. The following topics are covered in this section:
Sizing by deployment type
The following table explains the sizing requirements for each product in the solution.
Note
Deployment type | Number of managed devices | Rate of Change (VM Create, Update, Retire) | Concurrent Cloud Admins | Concurrent Cloud End Users |
|---|---|---|---|---|
Compact Deployment (if you use an external database) | 5,000 | 50 per hour | 5 | 25 |
Small | 10,000 | 50 per hour | 10 | 50 |
Medium | 25,000 | 100 per hour | 50 | 250 |
Large | 50,000 | 250 per hour | 250 | 500 |
Application tier hardware sizing
Note
The table below describes the number of nodes needed for each deployment size.
Product | Small | Medium | Large |
|---|---|---|---|
BMC AR System Server – Cloud Portal and Database (Cloud Portal and Database) | 2 VCPU 2+GHz x1 | 4 VCPU 2+GHz x2 | 4 VCPU 2+GHz x3 |
| Cloud Portal and Database Mid Tier Windows 2008 R2 (64-bit) Oracle JDK/JRE 1.7 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 | 4 VCPU 2+GHz x1 | 8 VCPU 2+GHz x2 | 8 VCPU 2+GHz x2 |
Atrium Core - Web Registry Components | 4 VCPU 2+GHz x1 | 4 VCPU 2+GHz x2 | 4 VCPU 2+GHz x2 |
BMC Server Automation App Server | 8 VCPU 2+GHz x1 | 8 VCPU 2+GHz x2 | 8 VCPU 2+GHz x3 |
BMC Server Automation File Server | 4 VCPU 2+GHz x1 | 4 VCPU 2+GHz x2 | 4 VCPU 2+GHz x2 |
BMC Network Automation | 2 VCPU 2+GHz x1 | 2 VCPU 2+GHz x2 | 4 VCPU 2+GHz x2 |
BMC Atrium Orchestrator (CDP + CDP HA) | 4 VCPU 2+GHz x1 | 4 VCPU 2+GHz x2 | 4 VCPU 2+GHz x3 |
Note
Product | Small | Medium | Large |
|---|---|---|---|
BMC Server Automation App Server Windows 2008 R2 (64-bit) | 8 VCPU 2+GHz | 8 VCPU 2+GHz | 8 VCPU 2+GHz |
Database tier hardware sizing
You might want to host product databases on single physical server or on separate servers. The decision is based on multiple factors, including, but not limited to hardware and licensing cost, performance, administration & maintenance efforts and security requirements.
This section discusses the sizing factors for hosting product databases on single versus separate servers.
Note
Sizing for separate database servers
Note
The following table provides the sizing guidelines for scenarios where you want to host product databases on separate servers.
Database Instance | Small | Medium | Large |
|---|---|---|---|
Cloud Portal and Database Server + | 8 CPU-Cores 2+GHz | 16 CPU-Cores 2+GHz | 32 CPU-Cores 2+GHz |
BMC Server Automation Database | 4 CPU-Cores 2+GHz | 8 CPU-Cores 2+GHz | 8 CPU-Cores 2+GHz |
BMC Network Automation Database | 2 CPU-Cores 2+GHz | 4 CPU-Cores 2+GHz | 4 CPU-Cores 2+GHz |
Sizing for single database server
The following table provides the sizing guidelines for scenarios where you want to host product databases on single servers.
Database Instance | Compact | Small | Medium | Large |
|---|---|---|---|---|
Database Server | 8 VCPU 2+GHz x1 | 16 CPU-Cores 2+GHz x1 | 32 CPU-Cores 2+GHz x2 | 64 CPU-Cores 2+GHz x2+N |
Note
- The disk size mentioned above indicates disk space consumed by the data and indexes. Include additional space for OS and other software installed.
- Atrium Web Registry database is not very transactional in nature and hence much smaller in size. For all Small, Medium and Large deployments, you can install this database on the same SQL 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 on the following factors:
- Database recovery model
- DB backup strategy and frequency.
Comments
Log in or register to comment.