Written by Porus Homi Havewala

We introduced the Oracle Enterprise Manager concept of Consolidation Planning in Part I of this article series. This is Part II.

On the Host Consolidation Manager’s Opening screen, there are no projects defined. Click on Create Project to start a new consolidation project. Figure 1-2 shows the project being created.

Figure 1-2: Creating a new Consolidation project.

Specify the appropriate Project Name. There are two types of Consolidation possible. You can either consolidate from physical servers to Oracle Virtual servers (P2V), or from physical servers to physical servers (P2P). This depends on the consolidation strategy being adopted by your enterprise.

Select the Consolidation Type as "From physical servers to physical servers (P2P)". This means we are planning to consolidate to actual physical target servers, and not to virtual machines in this project. Click on Next.

Figure 1-3: Specifying the Source Candidates.

In the next step (Figure 1-3), select the servers to be involved in the consolidation. Do this via the “Add Servers” button. These servers need to be what are known as “managed targets” in the Enterprise Manager system, i.e., the Enterprise Manager Agent has been previously promoted to these servers and they are being monitored and managed in Enterprise Manager.

When the servers have been added, the resource and usage data for each server are displayed on the screen, such as CPU utilization, Memory utilization, Disk storage and so on. Note that certain fields in the list are editable, such as CPU Capacity, Disk I/O Capacity and Network I/O Capacity so you can put in your own figures as needed.

The CPU capacity is based on the SPECint specification, which is a benchmark for a CPU’s processing power. The SPECint®_base_rate2006 benchmark is used by Consolidation planner for database or application hosts, or hosts with a mixed workload. The SPECjbb®2005 benchmark is used for middleware platforms.

The Consolidation Planner relies on the SPECint library that's available from SPEC.org, which covers the majority of CPUs in the market. If a particular CPU's SPEC rate is available in the SPECint library, that rate will be used. If by chance a particular CPU is not available in the SPECint library, it means the CPU specifications may not have been published by the manufacturer or a benchmark is not available for it (if it is a very old CPU or a brand new CPU). In this case, the Planner estimates the CPU's spec rate based on the CPU configuration details Enterprise Manager has collected. In this case the word “(Estimated)” will appear in the CPU Capacity (SPECint) column.

In such a case, it is the normal practice to use the estimated rate. However, based on your experience and if you have compared this particular CPU to other systems and believe there is a better rate than the one that has been estimated, it is fine for you to change the rate by editing it.

You can also specify the Server I/O Capacity by clicking on the button above the table. The Server I/O signifies Disk I/O and Network I/O, and can be estimated by multiplying their average usages with some factors or set as a specific value. If you click on the Server I/O capacity button, you can specify the multiplier factors (defaulted to 3) or absolute values to update the capacities for all selected servers. After this is done, click on Next.

Figure 1-4: Specifying the Destination Candidates.

In this step (Figure 1-4), you can add existing destination candidates such as normal servers or even existing engineered systems which already have the Enterprise Manager agent installed and are seen as targets. However, this step is optional. You can skip this step if you intend to use new (phantom) targets that you have not yet purchased and installed. Leave the table blank, and click on Next.

Figure 1-5: Data Collection Details.

As seen in Figure 1-5, at this point you can specify the Minimum Days and Maximum Days for data collection for all the targets. The defaults are 21 and 90 days respectively. If you specify 0 for the minimum days, the collection results will be available immediately (for quicker results such as a test), otherwise Enterprise Manager will wait until it has collected data for the specified minimum days before making it available.

For the purpose of a trial run, we can change the minimum days to 0. Specify the data collection starting time as “immediately”, or you can use a later date and time. Click on Next.

Figure 1-6: Addition of Pre-Configured Scenarios.

Three Pre-Configured Scenarios - Conservative, Medium or Aggressive are available for selection (Figure 1-6), or later on in the process you can use your own custom scenario.

We will continue this article series in Part III.

(This article is an excerpt from Chapter I of the new book by the author titled “Oracle Database Cloud Cookbook with Oracle Enterprise Manager Cloud Control 13c” published by Oracle Press in August 2016. For more information on the book, see here.)