Sizing chart and guidelines for the BMC Cloud Lifecycle Management integration

Consult the following topics for information on sizing an Infrastructure Management environment that is integrated with BMC Cloud Lifecycle Management. When planning your deployment, consider factors such as your end-user community, network infrastructure, and security issues. The values provided represent the maximum values recommended for the tested parameter.

Sizing chart for BMC Cloud Life Cycle Management

The following table can help you determine the number of required Central Servers, Child Servers, Data Collection Hosts, and BMC Server Automation Servers. The table also shows the maximum number of devices, monitor instances, and attributes for a proof of concept (POC), small, medium and large environment in BMC Cloud Lifecycle Management.

Characteristic	POC	Small Environment	Medium Environment	Large Environment
Number of monitored devices	500	10 K	30 K	50 K
Number of monitor instances	4.5 K	50 K	150 K	250 K
Number of attributes	8 K	100 K	300 K	500 K
Duration RAW data retention	8 days	8 days	8 days	8 days
Duration RATE retention	3 Months	3 Months	3 Months	3 Months
Adapter type	BMC PATROL	BMC PATROL	BMC PATROL	BMC PATROL
Polling frequency, in minutes (stats, auto-sync)	5, 5	5, 5	5, 5	5, 5
Required number of Central Servers	1 ^*	1	1	1
Required number of Child Servers	1 ^*	1	3	5
Required number of Infrastructure Management Data Collection Hosts	1 ^*	1	3	5
Required number of BMC BladeLogic Automation Servers	N/A	1	1	1
Total number of computers required	1	3	7	11
Total number of processors	2	8	20	32
Total memory required (in GB)	8	31	80	128

^ In a POC deployment, all of the components for BMC Cloud Life Cycle Management, such as the Central Server, Child Server, and Data Collection Host, are on the same computer.^

End user considerations

The way you build your cloud environment is determined, in part, by the number and distribution of the tenants and end users that you support. Answering the following questions will help you understand the number, type, and distribution of the infrastructure resources that you need to build your cloud:

How big is your user community?
How is your user community distributed geographically?
If you represent a service provider organization, how many tenants will you support and how many users are associated with each tenant?
How will you manage end user and administrator access to your cloud?
How will you manage access to the My Services Portal?

Network infrastructure considerations

At the heart of your cloud planning is your network infrastructure. You must decide how to organize the pods, network containers, and resource pools in your cloud.

Much of your network infrastructure planning will be consumed by BMC Cloud Lifecycle Management as service blueprints to enable automated delivery of resources that support services that your end users request:

How many pods do you need to support your tenants and end users?
How should your pods be distributed geographically? Consider whether you will have staff to support those pods on-site or whether you will provide support remotely.
How many network containers do you need in each pod?
How will you assign resources in network containers? For example, will you assign resources to specific tenants or level of service?
How will you build resource pools? For example, will resources be grouped according to performance, geographic location or some other criteria?
How many physical and virtual servers do you need?
How will you address failover and availability concerns?
How should you build your preproduction environment? Before making the cloud available to your end users you need an environment in which to develop and test your cloud. Do you need only environments for development, testing and production? If you represent a service provider organization, should you make a preproduction environment available to your tenants?

BMC Cloud Lifecycle Management sizing recommendations

BMC Cloud Lifecycle Management provides an end-to-end workflow that helps you to build a successful cloud implementation. The workflow provides guidelines for building your cloud, preparing services to be requested and delivered in that cloud, keeping your cloud operational and retiring services and resources. Examine the guidelines for each environment to determine which size fits your requirements.

The BMC Cloud Lifecycle Management Install Planner allocates components based on predefined templates that provide a streamlined approach to sizing and configuring your deployment. Based on your requirements you will select a template when you launch the Install Planner that closely matches your planned deployment scenario.

Small deployment

A small template with up to 10,000 virtual devices can collect up to 100,000 attributes.
If you use the BMC PATROL Adapter for data collection, install the Integration Service on a dedicated computer.
If you collect data across networks or firewalls, use an Integration Service to minimize the number of connections to manage across the networks or firewalls.
(SAP SQL Anywhere only) To improve I/O throughput, use separate disks for the operating system on which BMC TrueSight Infrastructure Management Server is deployed, and the database. Ensure that each disk has its own disk controllers.

Medium deployment

A medium template with up to 30,000 virtual devices can collect up to 300,000 attributes.
If you use the BMC PATROL Adapter for data collection, install the Integration Service on a dedicated computer.
If you collect data across networks or firewalls, use an Integration Service to minimize the number of connections to manage across the networks or firewalls.
(SAP SQL Anywhere only) To improve I/O throughput, use separate disks for the operating system on which Infrastructure Management Server is deployed, and the database. Ensure that each disk has its own disk controllers.

Large deployment

A large template with up to 50,000 virtual devices can collect up to 500,000 attributes.
If you use the BMC PATROL Adapter for data collection, install the Integration Service on a dedicated computer.
If you collect data across networks or firewalls, use an Integration Service to minimize the number of connections to manage across the networks or firewalls.
(SAP SQL Anywhere only) To improve I/O throughput, use separate disks for the operating system on which BMC TrueSight Infrastructure Management Server is deployed, and the database. Ensure that each disk has its own disk controllers.

Page tree