Skip Headers
Oracle® Enterprise Manager Cloud Administration Guide
12c Release 3 (12.1.0.3)

E28814-10
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

23 Using Consolidation Planner

This chapter covers use of the Consolidation Planner feature provided with Oracle Enterprise Manager Cloud Control.

This chapter includes the following sections:

23.1 Overview of Consolidation Planner

Over the years, the typical enterprise data center will grow steadily due to the addition of servers required to satisfy the needs of the business. This growth typically results in excess servers that occupy rack space, consume a lot of power for cooling, and require system maintenance such as security and patching.

Depending on the procurement cycle or the specific hardware vendor agreement in effect, enterprises may acquire different types of server hardware and operating systems, inadvertently creating a confusing array of systems that administrators need to manage, administer, patch and upgrade. This in turn increases labor and ongoing maintenance and support costs against IT budgets. Enterprises look at consolidation as a way to migrate their disparate systems onto standardized operating systems and hardware, with the ultimate goal of reducing costs.

Enterprises also are increasingly investigating virtualization technologies such as Oracle Virtual Machine by moving from physical to virtual servers. This makes it possible to use the shared hardware infrastructure while getting the benefits of isolation that virtualization provides.

The goal of consolidation is to identify such under-utilized servers and find a way to consolidate them, enabling the enterprise to free up as many servers as possible while continuing to maintain service levels. Since servers have different levels of CPU capacity, Consolidation Planner uses computer benchmark data to normalize the CPU usage for a given hardware in the consolidation process. Specifically, Consolidation Planner uses the following CPU benchmarks for different classes of hardware:

  • SPECint®_base_rate2006 for database hosts, application hosts, or mixed-workload hosts

  • SPECjbb®2005 for middleware platforms

The Consolidation Planner feature enables you to match managed servers you want to consolidate with the generic physical machines, Oracle engineered systems (Exadata Database Machines or Exalogic Elastic Cloud systems), or Oracle Virtual Machine (VM) servers they can be consolidated to. By leveraging metric and configuration data collected from managed target servers by Enterprise Manager Cloud Control, Consolidation Planner helps you determine the optimum consolidation scenarios that also reflect business and technical constraints in the consolidation process.

23.1.1 Key Concepts

The following concepts are central to using Consolidation Planner.

Source Server

An existing server that will be considered for consolidation.

Destination Server

An existing or yet-to-be-purchased server that a source server will be consolidated to. Can also be thought of as the consolidation target. These may be individual machines, virtual server pools, or an engineered system such as the Oracle Exadata Database Machine or an Exalogic Elastic Cloud system.

Consolidation Project

Defines the scope of a potential consolidation effort, including:

  • The type of consolidation. In the current release, two types of consolidation schemes are supported:

    • P2V: From physical source servers to Oracle Virtual Machine (VM) destination servers

    • P2P: From physical source servers to physical destination servers

  • The preliminary set of candidate source servers to consider consolidating from

  • The preliminary set of candidate destination servers to consider consolidating to

  • The duration over which data used to generate consolidation scenarios will be collected for the source servers

  • The benchmark used to measure CPU capacities when determining how many source servers can be consolidated to a destination server

Consolidation Scenario

Each consolidation project contains one or more consolidation scenarios that are generated based on the inputs provided. Inputs provided to a scenario include:

  • The source server resource requirements that a destination server must meet, including one or more of the following: CPU, memory, disk I/O, network I/O, and disk storage

  • Any business, compliance or technical constraints that must be considered

  • The destination servers to consider in the scenario

A set of pre-configured consolidation scenarios are provided, representing conservative, aggressive, and medium consolidation schemes. Each scenario is generated based on inputs you provide. Alternatively, you can create your own custom scenarios that best suit your situation. Once created, you can compare the various scenarios to determine which consolidation strategy best meets your requirements.

Each scenario also includes initial mappings between each source server and the destination server it may be consolidated to. You can choose to create mappings manually, or allow Consolidation Planner to create them automatically. Once all inputs are specified, you can run the scenario and evaluate the results. Subsequently, you can rerun the scenario to re-evaluate the scenario based on the previously specified conditions with the latest available data. The results of the previous analysis will be over-written. You can also create a new scenario based on an existing scenario, where you tweak certain values to customize the new scenario.

23.2 Consolidation Constraints

Consolidation Planner allows you to specify various constraints that must be considered when creating consolidation projects and scenarios.

This section covers the following:

23.2.1 Source Server Constraints

For source servers, you define constraints on the basis of compatibility or exclusivity.

Compatible Servers

Servers are considered compatible if they match on certain property and configuration values.

Properties include the following:

  • Lifecycle Status

  • Department

  • Location

For example, there may be situations that mandate that specific servers remain within a specific location, such as data center location or geography.

Configuration items include the following:

  • Network Domain

  • System Vendor

  • System Configuration

  • CPU Vendor

  • CPU Name

  • Operating System

For example, there may be an accounting policy that the same system and CPU vendor be used.

You can choose to establish compatibility on none, some, or all of these target properties and configuration items.

Mutually Exclusive Servers

You can choose to exclude servers from consolidation scope because they violate certain Oracle best practices. Set either or both of the following conditions to exclude matching servers:

  • Nodes of a RAC Database–do not consolidate nodes of the same RAC database to a single destination server

  • Nodes of an Oracle Cluster–do not place nodes of an Oracle cluster in the same failure group

23.2.2 Destination Server Constraints

For destination servers, you can scope candidates to either new or existing candidates, but constraints are primarily expressed as a percentage of CPU and memory resource utilization; that is, how much of either resource type can maximally be used on a destination server.

23.3 Using Consolidation Planner

The steps in the consolidation planning process are:

  1. Create a consolidation project. See Section 23.3.1, "Creating a Consolidation Project".

  2. Define one or more consolidation scenarios within the project. You have two options:

  3. Evaluate your consolidation scenarios in the Consolidation Planner console to determine the consolidation strategy that best meets your needs. See Section 23.3.4, "Evaluating Consolidation Scenarios".

  4. Modify the settings of your scenarios to generate different results. Continue this process until you have the most optimal scenario(s) for your situation.

Note that in this release, consolidation scenarios can be created for planning purposes only. Execution of scenarios—that is, the actual movement of data from sources to destinations—is not supported.

When consolidating multiple sources to more than one destination, the resource requirements of sources are checked against the resource capacity of the destinations. To consolidate all identified sources to the least number of destinations, Consolidation Planner tries to identify a set of sources that have known resource requirements that will fit into a destination's corresponding available resources as tightly as possible.

For example, if the available memory in a destination server is 2 GB, Consolidation Planner will try to find a set of source candidate servers with a sum of required memory as close to 2 GB as possible then “fit” the source servers in the destination server. The goal is to “fit” the source servers into the least number of destination servers.

This section includes the following:

23.3.1 Creating a Consolidation Project

You create a consolidation project for each consolidation effort, then add individual consolidation scenarios within it. You can then compare consolidation scenarios to determine which consolidation strategy makes the most sense.

After the project is defined, a Cloud Control job is submitted to collect available data for the specified targets from the Management Repository. Once the job finishes, the project becomes an active project. As long as the project is in an active state, data collection will continue.

A wizard guides you through the creation process and involves the following steps:

23.3.1.1 Declaring the Consolidation Type

Specify general information about the consolidation project as follows:

  1. From the Enterprise menu, select Consolidation Planner.

  2. Click the Create Project button.

  3. Enter the consolidation project name and, optionally, a description.

  4. Select the host consolidation type: from physical source servers to Oracle VM servers (P2V), or from physical source servers to physical servers (P2P).

  5. Click Next to specify source candidates.

23.3.1.2 Specifying Source Candidates

Proceed with source selection as follows:

  1. Select an appropriate benchmark from the drop-down menu.

    • Specify SPECint®_base_rate2006 for database hosts, application hosts, or mixed-workload hosts

    • Specify SPECjbb®2005 for middleware platforms

  2. Click Add Source Servers to select the source servers to be consolidated from a list of managed server candidates. Use the filtering criteria to refine your target search. Choose from the filtered results, then click Select.

    The targets you select appear in the table. Note that you can subsequently cull the list by removing selected source servers.

  3. Optionally set server I/O capacities for disk I/O request and network I/O volume capacities. Click Specify Server I/O Capacity to estimate these I/O capacities for all source involved in the consolidation project. Note that you can subsequently fine-tune these estimates by clicking a row and editing the values for the various capacities.

  4. Click Next to specify destination candidates.

23.3.1.3 Specifying Destination Candidates

Proceed with destination selection as follows:

  1. Optionally select one or more existing servers to consolidate the source servers to.

    • If you are consolidating from physical servers to Oracle Virtual Servers (P2V), click Add Existing Virtual Servers as Destinations to view a list of existing VM-based Exalogic Elastic Cloud systems and Oracle Virtual Machine destination servers to consolidate the source servers to. Use the target type filter to differentiate the two. Select the servers you want to add, then click Select.

      The targets you select appear in the table. Note that you can subsequently cull the list by removing selected destination servers.

    • If you are consolidating from physical servers to physical servers (P2P), click Add Existing Oracle Engineered System as Destinations to search for the Exadata Database Machine servers or Exalogic Elastic Cloud servers to consolidate the source servers to. Use the target type filter to differentiate the two. Select the servers you want to add, then click Select.

      The targets you select appear in the table. Note that you can subsequently cull the list by removing selected destination servers.

    Note:

    The consolidation will be either to new destination servers, or to the existing servers that were selected as source servers.
  2. Optionally edit estimated CPU capacity, I/O request, and network I/O volume by clicking in a row and changing the value. You can also edit the I/O value by clicking Specify Server I/O Capacity to estimate these I/O capacities for all destination servers involved in the consolidation project.

  3. Click Next to set up data collection.

23.3.1.4 Setting Data Collection Parameters

Specify the duration over which data used to generate consolidation scenarios will be collected for the source servers specified in the project in the Data Collection region. This data will be used to determine the resource requirements that a destination server must meet.

  1. Specify the minimum number of days to collect data. The default minimum value is 21 days. To use existing historical data to run and view consolidation scenarios immediately, set the minimum number of days to 0.

  2. Specify the maximum number of days to collect data. The default maximum value is 90 days.

  3. Specify when to begin the data collection process.

    Note that once data collection begins, you can elect to suspend and resume collecting at any time from the Actions menu in the Consolidation Planner console.

  4. Optionally select Continue Data Collection Over the Maximum Days to purge the oldest day's data when data for a new day is added.

  5. Click Next to choose a pre-configured scenario.

23.3.1.5 Choosing a Pre-configured Scenario

When creating a consolidation project, you can optionally choose to generate up to three pre-configured consolidation scenarios to add to the project. These out-of-the-box scenarios represent conservative, aggressive, and medium consolidation schemes.

These scenarios are generated using data collected for the source targets defined in the consolidation project at the time the project is created. If no data is available when the project is created, the pre-configured scenarios will be automatically generated once the minimum amount of data has been collected.

Consolidation Planner ships with three out-of-the-box scenarios that represent conservative, aggressive, and medium consolidation schemes.

  1. Choose whether to use a pre-configured scenario by clicking the appropriate radio button. Choosing the option displays a list of the out-of-the-box consolidation scenarios available. By default, the scenarios are designated by the method used to aggregate daily source target resource usage:

    • Aggressive: Aggregate data based on average daily usage per hour.

      This typically results in a high consolidation (source:destination) ratio, because more sources will “fit” into each destination. But because more sources are involved, the odds that one or more will not meet the resource requirements are higher.

    • Conservative: Aggregate data based on maximum daily usage per hour.

      This typically results in a lower source:destination ratio, because fewer sources will “fit” into each destination.

    • Medium: Aggregate data based on the 80 percentile usage.

      This typically results in a source:destination ratio somewhere between Aggressive and Conservative aggregations.

  2. Select the pre-configured scenario you want to use. Note that you can select any or all scenarios.

  3. Select whether to factor new or existing destinations in the scenario. If you choose a new (phantom) server, provide resource metric estimates.

  4. Click Next to review the consolidation project.

The pre-configured scenarios will be generated when the project is created using data collected for the source servers defined in the consolidation project.

You can also opt to create your own custom scenario once the consolidation project has been completed.

23.3.1.6 Reviewing and Saving the Consolidation Project

Review the specifics of the consolidation project. Use the Back button to return to a given step to make changes. If satisfied, click Submit. A message confirms that the project has been created and the job has been submitted.

Once the project is created, it will show up in the Consolidation Planner console. Consolidation scenarios can then be defined for this project.

23.3.2 Creating a Custom Consolidation Scenario

You can create custom consolidation scenarios instead of or in addition to using the pre-configured scenarios. Multiple scenarios can be created within a project, enabling you to compare different scenarios before deciding on a solution. New consolidation scenarios are created within an existing consolidation project.

A wizard guides you through the creation process and involves the following steps:

23.3.2.1 Specifying Scenario Parameters

Specify the general parameters of the scenario as follows:

  1. From the Enterprise menu, select Consolidation Planner.

  2. Click the consolidation project for which the scenario is intended.

  3. Click the Create Scenario button.

  4. Specify the scenario details, such as scenario name.

  5. Specify the source resources to consider. Consolidation Planner will aggregate the specified resources to determine the total requirements.

    • Resource Type: The server requirements, such as CPU, memory (GB), and I/O capacity that must be considered.

    • Scale Factor: Provide room for growth on the destination for each source. The resource requirement estimate uses the scale factor to pad the estimate for consolidation. So, for example, if the estimated requirement for a given source, based on usage data, is 2 GB of memory, which equates to a scale factor of 1, and you specify a scale factor of 1.1, 2.2 GB will be required to consolidate that source.

    • Applicable Days: The days of the week on which resource usage metrics are collected.

    • Resource Allocation: The method used to aggregate daily source server resource usage. Values are:

      • Aggressive: Aggregate data based on average daily usage per hour.

        This typically results in a high consolidation (source:destination) ratio, because more sources will “fit” into each destination. But because more sources are involved, the odds that one or more will not meet the resource requirements are higher.

      • Conservative: Aggregate data based on maximum daily usage per hour.

        This typically results in a lower source:destination ratio, because fewer sources will “fit” into each destination.

      • Medium: Aggregate data based on the 80 percentile usage. This typically results in a source:destination ratio somewhere between Aggressive and Conservative aggregations.

    • The date ranges should define a period of time that is typical of standard resource requirements.

  6. Click Estimated Requirements to view the estimated total resource requirements.

    Resource requirements are shown based on the averaged hourly requirement. The displayed requirements reflect the scale factor (if any) specified for the resource. The 24-hour requirement pattern will be used as the minimum requirements that must be met by consolidation targets.

  7. Click Next to define consolidation constraints.

23.3.2.2 Defining Consolidation Constraints

Specify business, corporate or technical constraints that must be enforced. These constraints will be used to:

  • Guide the allocation process during automatic source-to-destination mapping; or

  • Calculate violations if manual mapping between sources and destinations is used

  1. Select compatible server criteria.

    Servers are considered compatible if they have the same specified target properties and configurations. If you are consolidating multiple source servers to a single target server, only compatible servers can be consolidated together on the same target server.

  2. Specify mutually exclusive server criteria.

    Certain types of source servers are mutually exclusive and should not be consolidated together on the same destination server due to various reasons. For example, nodes of an Oracle cluster should not be placed in the same failure group.

  3. Click Preview Effect of Constraints to view a list of source servers that are not compatible based on the defined constraints.

  4. Click Next to specify destination server candidates.

23.3.2.3 Specifying Destination Candidates

Determine the destination candidates needed to meet your requirements. Proceed according to the project type.

  • Physical Server to Virtual Server Project

  • Physical Server to Physical Server Project

Physical Server to Virtual Server Project

For a P2V project:

  1. Choose destination server candidates using either of the following options:

    • Click Use New (Phantom) Servers if you plan to use target servers that have yet to be provisioned or purchased, then select either of the following options:

      • Use Oracle Engineered System and click the search icon to select an appropriate configuration type for an Exalogic Elastic Cloud system.

      • Use Generic Servers and provide the estimated CPU capacity if available; otherwise, click the search icon next to the CPU capacity input field, then select a server configuration that most closely matches your needs.

        Adjust the memory and storage estimates as necessary.

        In a virtual environment, you can also specify a quantity of the resource to be set aside (reserved) for use by supervisory software in the database machine. This quantity is subtracted from the total capacity of the destination before consolidating source servers into the remaining resource. For example, if your estimated memory requirement is 12 GB and you specify a reserve of 2 GB, only 10 GB is available for consolidation.

        Consolidation Planner will determine how many destination servers are required as part of the consolidation results.

    • Click Use Existing Servers to specify a set of existing managed servers to use as targets.

      These are the servers you specified when defining the scope for the consolidation project. Consolidation Planner will determine the available hardware resources based on collected usage data.

      By default, the consolidation process will try to use as few target servers as possible. If you prefer, choose to balance the source load across all destinations.

  2. Accept the defaults or edit the percentages for Maximum Allowed Resource Utilization on Destination Servers. Contrast these allowances, which provide headroom on destination servers, with the scale factor, which provides headroom for individual source servers.

  3. Click Next to map the source servers to the destination servers.

Physical Server to Physical Server Project

For a P2P project:

  1. Choose destination server candidates using either of the following options:

    • Click Use New (Phantom) Servers if you plan to use destination servers that have yet to be provisioned or purchased, then select either of the following options:

      • Use Oracle Engineered System and select either Exadata Database Machine or Exalogic Elastic Cloud. Click the search icon and select a configuration type appropriate to either choice.

      • Use Generic Servers and provide the estimated CPU capacity if available; otherwise, click the search icon next to the CPU capacity input field, then select a server configuration that most closely matches your needs.

        Adjust the memory and storage estimates as necessary.

    • Click Use Existing Servers to specify a set of existing managed servers to use as destinations for the project.

      These are the servers you specified when defining the scope for the consolidation project. Consolidation Planner will determine the available hardware resources based on collected usage data. If you did not explicitly specify destination candidates, all source servers are potential destinations for consolidation.

      By default, the consolidation process will try to use as few destination servers as possible. If you prefer, choose to balance the source load across all destinations.

  2. Accept the defaults or edit the percentages for Maximum Allowed Resource Utilization on Destination Servers. Contrast these allowances, which provide headroom on destination servers, with the scale factor, which provides headroom for individual source servers.

  3. Click Next to map the source servers to the destination servers.

23.3.2.4 Mapping Sources to Destinations

Next, map the sources to the destinations they will be consolidated to. The objective is to fit source requirements with each destination's available resources as tightly as possible.

It is recommended that you allow Consolidation Planner to perform this mapping automatically. This will allow the tool to maximize resource utilization of destinations based on resource capabilities and the various consolidation constraints specified.

When you have chosen existing destinations, you can optionally map each source and destination manually:

  1. Click a source in the list.

  2. Click the flashlight icon to select the destination to map to the source. Note that you can map a single source to a destination or multiple sources to a destination, but a source can be mapped to only one destination.

    The resulting consolidation report will show any resource and/or constraint violations due to such manual mapping.

  3. Click Next to review the consolidation scenario.

23.3.2.5 Reviewing and Saving the New Scenario

Finally, review the various parameters set in the new scenario. Note that you can optionally save the scenario as a template. Use the Back button if you need to make changes; otherwise, proceed as follows:

  • Optionally, you can save the scenario as a template, which can then be shared with other users. If you want to do this, click Save Scenario as a Template. In the dialog that opens, browse to a location in the local file system and save the template as an XML file.

  • Click Submit. A message appears confirming that a job has been submitted for further analysis of the scenario. Results appear at the bottom of the Consolidation Planner page when done.

23.3.3 Other Scenario Creation Options

You can also create a consolidation scenario based on an existing scenario. Select an applicable scenario under a consolidation project and then select Create Like Scenario from the Actions menu. Modify the scenario as desired, provide a meaningful name, and submit for analysis as usual.

If you saved a scenario as a template, you can subsequently import the scenario into another environment.

  1. On the Consolidation Planner home page, select Create Scenario from Template from the Actions menu.

  2. Browse to a saved template XML file in the local file system. Click Open.

  3. Indicate the extent to which you want replicate the saved template; that is, in terms of the resources, constraints, and targets planning represented by the template. Click Update if you make any changes.

  4. Click OK to import the saved template.

    The imported scenario opens in the wizard where you can edit and save it in Consolidation Planner.

23.3.4 Evaluating Consolidation Scenarios

You can view details for your consolidation scenarios using the Consolidation Planner console. After evaluating the consolidation scenario results, you can define different plans as well as rerun existing scenarios to re-evaluate them based on the previously specified conditions with the latest available data. The results of the previous analysis will be over-written. You can also create a new scenario based on an existing scenario, where you tweak certain values to customize the new scenario. This iterative process helps you obtain the optimized consolidation scenario which is generated by compromising various factors and weighing different trade-offs.

Compare the consolidation scenarios you create to determine which consolidation strategy best meets your requirements.

Your objective is to:

  • Match source resource requirements with destinations best able to meet those requirements.

  • Fit source requirements with each destination's available resources as tightly as possible, so you can get maximum usage of destination capacity.

  • Provide room for growth on destinations by allowing for headroom as a factor of resource requirements.

  • Optionally balance the source workload across all available destinations.

In the current release, consolidation scenarios can be created for planning purposes only. Consolidation scenarios cannot be executed using Consolidation Planner.

  1. From the Enterprise menu, select Consolidation Planner.

  2. First, examine the project containing the scenario you want to view.

    • The Status column indicates the status of data collection, based on the minimum and maximum collection days specified for the project.

    • The General tab summarizes the project in terms of type, collection details, number of sources, and so forth.

    • Click the Sources tab to view various usage data collected for the sources defined in the project. Data can include utilization rates for CPU, memory, storage, and disk and network I/O, depending on the project type.

    • Click the Source Workload tab to view a graph showing source resource usage data collected. Data is shown for each 24 hour period across a monthly span. You can filter the view by source, resource type, and month.

    • Click the Destination Candidates tab to view a breakdown of hardware details and projected resource utilization by destination candidate, based on the sources to be consolidated.

    • Click the Report button above the table when the project is selected to view summarized information and more details.

  3. Next, view the data for a specific scenario. For a completed analysis, click any metric in the row to view details. Clicking the Sources metric takes you to the General tab where you can view a summary of the scenario. Clicking the remaining metrics takes you to the respective tab, as follows:

    • Destinations: The list of destinations to which the sources will be consolidated. Resource configuration and calculated utilization are shown for each destination.

    • Ratio: The ratio of sources to destinations. By default, Consolidation Planner will try to “fit” sources into as few destinations as possible.

    • Mapping: The destinations to which specific sources will be mapped. The analysis includes estimated CPU and memory requirements and utilization, enhanced by suggested CPU and memory allocation figures to consider. These suggestions represent a reasonable compromise between requirements and destination server capacity.

    • Confidence: The percentage of the data collected for sources that meet the source usage requirements defined in the scenario. This value is aggregated for all sources defined with the project.

    • Violations: The number of violations of technical or business constraints defined in the scenario.

    • Exclusions: The number of sources that do not have a qualified mapping to a destination. These are sources that exceed the capacity of available destinations. This metric is applicable only if auto-mapping of sources to destination is used.

A different set of constraints may result in a different optimal scenario. Modify the constraints to come up with different scenario results.

Share Reports with Others

Select a report in the table and click Publish Report to make report contents public. This action integrates with BI Publisher, where you can:

  • Save reports in a variety of formats (Excel, PowerPoint, HTML, PDF)

  • Distribute generated reports to e-mail lists (users who do not have access to Enterprise Manager, for example) on a defined schedule

23.3.5 Analyzing a Consolidation Scenario

To analyze a consolidation scenario, Consolidation Planner follows a defined process.

First, Consolidation Planner estimates the hourly and overall resource requirements for each of the consolidation sources. Using metric data collected by Enterprise Manager, Consolidation Planner calculates the requirement for each hour and for all hours (in the specified collection days), selecting the average, 80th percentile, or maximum value, depending on the selected resource allocation style (Aggressive, Medium, or Conservative). Consolidation Planner adjusts this value if a scale factor is specified. The resource requirement displayed for the source is the overall requirement determined by the resource allocation style and adjustments.

If the consolidation scenario includes existing destinations, Consolidation Planner performs a similar calculation to determine the hourly and overall usage values for each destination. Consolidation Planner does not scale or otherwise adjust these values, but calculates them using average, 80th percentile, or maximum values depending on the resource allocation style.

To consolidate sources into new or existing destinations, Consolidation Planner matches the hourly requirements for each source against the available hourly capacity of a destination. (Existing destinations start this process populated with their existing hourly workloads; new destinations start in an empty state.) If the destination can accommodate all hourly requirements for all resources, a success consolidation occurs. If any requirement cannot be consolidated, Consolidation Planner tries the next destination until one is found with sufficient capacity. If the consolidation is to existing destinations and none have sufficient remaining capacity, the source is excluded from the consolidation. For consolidation to new destinations, another destination is created to accommodate the source. By default, Consolidation Planner consolidates sources to the fewest possible destinations. However, for scenarios with multiple existing destinations, you can choose to spread the workload across all destinations instead.

The scenario Mapping page displays the results of the consolidation. The contents of this page vary depending on the project type and the resources selected for consolidation, but in general displays the following:

  • Projected destinations, and the sources consolidated to each destination.

  • For each resource, the capacity of the destination, together with the percentage and amount of that resource that will be consumed by the sources consolidated to it and existing workload, if any. Consolidation Planner estimates this amount by finding the largest hourly usage for the resource on the destination. The source line shows the percentage of the destination's resources that will be used by that source.

23.3.6 Managing Data Collections

Manage data collections by viewing the status of your projects.

  1. On the Consolidation Planner home page select View Data Collection from the Actions menu.

  2. The view lists source targets within a project where you can perform the following tasks:

    • View the latest collection status by project.

    • Select a target to see its collection history and troubleshoot potential problems with the collection.

    • Click the link under Data Collection Jobs to go to the job activity page where you can view and administer the latest data collection job.

    • Update the latest SPECint rates by following the instructions to download a CSV file with the latest rates. After downloading the file, click Browse to locate the file in the local file system and click Load to update the rates in Consolidation Planner.