Page tree

Unsupported content

   

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

This topic contains the following sections:

Verifying a successful integration with BMC Cloud Lifecycle Management

Before you can begin to use and leverage the features of CAPA in BMC TrueSight Capacity Optimization, you must ensure that ensure that integration of the product with BMC Cloud Lifecycle Management was successful.

To verify that the integration of the BMC Cloud Lifecycle Management completed successfully, do the following:

  1. In the console, navigate to the Additional Packages tab under Administration > System > Maintenance.
  2. Locate the Integration with BMC - Cloud Lifecycle Management component under the Item column. You can verify the integration status simply by looking at the color of the row:
    • Green: The task has ended correctly; in this case, BMC TrueSight Capacity Optimization is now correctly integrated with BMC Cloud Lifecycle Management.
    • Blue: The task is still running; in this case, wait for it to complete.
    • Yellow or red: The task execution failed due to errors; in this case, you can find out more about the errors by examining the deployment log that can be downloaded by clicking on the  icon.
  3. If necessary, examine the deployment log that can be accessed clicking on the  icon in the row corresponding to the Integration with BMC - Cloud Lifecycle Management component.

Using Placement Advice statistics to verify the correct deployment of the CAPA service

The Placement Advice Statistics table provides a list of statistics, including autodiagnostics.

These statistics are particularly useful to verify the correct deployment of the CAPA service after Configuring an ETL task to import data for BMC Cloud Lifecycle Management services, that is, when the service has been deployed on BMC TrueSight Capacity Optimization and performance data has been imported, but the CAPA service has not been registered on BMC Cloud Lifecycle Management yet.

Clicking Test Placement launches a test (autodiagnostic) placement advice request and refreshes the Placement Advice Statistics table, to help you verify and troubleshoot the status of the service. This type of request is also sent by the ComponentStatusChecker task, which runs every 5 minutes. The test call results in the following actions:

  1. A random placement advice scenario is selected among those created when deploying the CAPA service.
  2. A fake placement request is performed on the scenario, to verify that the placement can be performed successfully; at this time, no provisioning is applied.
  3. A message representing the output of autodiagnostic request is displayed, showing a possible failure reason in case of error.
  4. The affected counters in the Placement Advice Statistics table are incremented. For example, you can see the number of placement advice requests that completed successfully: overall ("Total Autodiagnostic Requests") and by scenario ("Total Autodiagnostic Requests By Scenario ID: <scenario_id>"); you can also see the total number of errors.

Note

If the number of total errors is greater than zero, it may mean that the CAPA service is unable to satisfy placement advice requests successfully; in this case, analyze the service log and the Data Hub log to investigate the issue.

After the CAPA service is registered on BMC Cloud Lifecycle Management, the Placement Advice Statistics table shows the following details for the last three 5-minute execution intervals:

Statistic

Description

Type

Insufficient Capacity

Targets capacity is not enough to host input candidates (error code BCO_PAS_003).

Errors

Estimated Insufficient Capacity

Targets capacity is estimated not to be enough to host input candidates (error code BCO_PAS_004).

Errors

Invalid Parameters

Incorrect input parameters to service calls, please check the log for more details (error code BCO_PAS_007).

Errors

Scenario Lookup Failed

Scenario Lookup using properties as parameters failed, please check that lookup inputs are correct (error code BCO_PAS_005).

Errors

Scenario Not Found

Scenario identifier has not been found, please check that requested scenario exists (error code BCO_PAS_006).

Errors

Total

Total number of errors occurred

Errors

Total

Total number of failures occurred; the possible failures are "Service Internal Error" (error code BCO_PAS_001) or Out of Memory error (error code BCO_PAS_002).

Failures

AVG Queue Time

Average waiting time per request

Total Autodiagnostic Requests / Total Requests

AVG Response Time

Average response time per request

Total Autodiagnostic Requests / Total Requests

AVG Throughput

Average request throughput

Total Autodiagnostic Requests / Total Requests

SUM Completed Requests

Total number of requests received and processed

Total Autodiagnostic Requests / Total Requests

SUM Errors

Total number of errors occurred (sum of Errors and Failures); this statistic is only available for statistics by scenario ID.

Total Autodiagnostic Requests

Statistics can be of one of the following types:

  • Errors: Errors that occurred during the execution of the service, listed by type (for example, "Scenario Not Found") or as sum ("Total"). All errors are mapped using a unique error code; for more information, see Error codes.
  • Failures: Service failures, for example "Out of Memory error".
  • Total Autodiagnostic Requests and Total Requests: Service statistics for test (autodiagnostic) requests and for all placement advice requests, respectively; overall or by scenario ID.

Managing advanced settings for Placement Advice scenarios

The BMC - Cloud Lifecycle Management - Placement Advice Preparation task performs the following actions:

  • Creates and updates placement advice scenarios based on the cloud infrastructure.
  • Periodically queries the BMC TrueSight Capacity Optimization Data Warehouse for performance data updates, to use in placement advice scenarios (by default, every 60 minutes).

To modify the task settings and the properties of the scenarios it creates, follow these steps:

  1. Access the Console and navigate to Administration > ETL & System Tasks > System Tasks.
  2. Locate and click on the BMC - Cloud Lifecycle Management - Placement Advice Preparation task to access its detail page.
  3. Edit the active run configuration for the task. You can customize the scheduling options and general configuration for the scenarios managed by the task:
    • In the General configuration tab, you can set the following properties:
      • Name: Name of the run configuration.
      • Environment: Environment that must be set for the run configuration; you can select either Production or Test.
      • Description: Additional information that you want to add for the run configuration.
    • In the Defaults and thresholds tab, you can set the default values and threshold settings to be used by the placement advice algorithm. You can set host-level and cluster-level thresholds for candidates and targets by specifying the following properties:
      • CPU:
        • Candidate default CPU: The default CPU usage (in megahertz) for each virtual machine (VM) candidate. By default, this value is set to 1000.
        • Candidate default CPU utilization: The default CPU utilization (in percentage) for each VM candidate. By default, this value is set to 80.
        • Target CPU cluster-level threshold: The cluster level threshold setting (in percentage) for the target CPU usage. By default, this value is set to 75. 
        • Target default CPU utilization: The default CPU utilization (in percentage) for the target. By default, this value is set to 50.
        • Target CPU threshold: The threshold setting (in percentage) for the target CPU. By default, this value is set to 75.
      • Memory:
        • Candidate default memory utilization: The default memory utilization (in percentage) for each VM candidate. By default, this value is set to 33.
        • Target cluster-level memory threshold: The cluster level threshold setting (in percentage) for the target memory usage. By default, this value is set to 95. 
        • Target default memory utilization: The default memory utilization (in percentage) for the target. By default, this value is set to 50.
        • Target memory threshold: The threshold setting (in percentage) for the target memory. By default, this value is set to 95.
      • Disk:
        • Candidate default disk size: The default disk size (in gigabytes) for each VM candidate. By default, this value is set to 1.
        • Candidate default disk transfer rate: The default disk transfer rate (in megabytes per second) for each VM candidate. By default, this value is set to 0.
        • Target datastore transfer rate cluster-level threshold: The cluster level threshold setting (in percentage) for the target datastore transfer rate. By default, this value is set to 90. 
        • Target datastore transfer rate default: The default datastore transfer rate (in megabytes per second) for the target. By default, this value is set to 0.
        • Target datastore transfer rate threshold: The datastore transfer rate (in percentage) for the target. By default, this value is set to 90.
        • Target datastore space used threshold: The threshold setting (in percentage) for the target datastore space usage . By default, this value is set to 75.
        • Target datastore provisioning ratio: The target provisioning ration (in percentage) to be used for thin provisioning. By default, this value is set to 100.
        • Disk PPA multiplier number: The multiple of disk size used for Pending Provisioning Actions (PPA). By default, this value is set to 10.
      • Network:
        • Candidate default network utilization: The default network utilization (in megabits per second) for each VM candidate. By default, this value is set to 0.
        • Target network transfer rate cluster-level threshold: The cluster level threshold setting (in percentage) for the target network transfer rate. By default, this value is set to 75.
        • Target network transfer rate default: The default network transfer rate (in megabits per second) for the target. By default, this value is set to 0.
        • Target network transfer rate threshold: The threshold setting (in percentage) for the target network transfer rate. By default, this value is set to 75.
    1. In the Placement advice algorithms tab, you can manage Affinity settings and configure placement options for Compute and Storage resources.

      Placement Advice Preparation Task - 
      Placement advice algorithm tab

Note

Only the following parameters are used for BMC Cloud Lifecycle Management integration in BMC TrueSight Capacity Optimization:

  • CPU Mhz candidate default utilization
  • CPU candidate default utilization
  • CPU target default utilization
  • CPU threshold
  • Memory candidate default utilization
  • Memory target default utilization
  • Memory threshold

The rest are useful only if a program is calling the CAPA API.

Manage settings for BMC Cloud Lifecycle Management Placement Advice Chain

The BMC - Cloud Lifecycle Management - Placement Advice Chain task periodically performs the following actions:

  • Executes the BMC TrueSight Capacity Optimization Cloud DB ETL
  • Runs the BMC Cloud Lifecycle Management Placement Advice Preparation task

The default execution frequency for this chain is 5 minutes. To modify the task chain settings, follow these steps:

  1. Access the BMC TrueSight Capacity Optimization Console and navigate to Administration > ETL & System Tasks > System tasks.
  2. Select BMC - Cloud Lifecycle Management - Placement Advice Chain, accessing its detail page.
  3. Edit the task configuration, where you can customize the scheduling options.

    BMC Cloud Lifecycle Management Placement Advice Chain scheduling options - edit task

Use cases for the CAPA service

The CAPA service finds application in the following use cases:

  1. BMC Cloud Lifecycle Management: The CAPA service can be used by BMC Cloud Lifecycle Management to provide advice on capacity-aware placement for the provisioning of virtual machines in a cloud environment.
  2. External providers: You can use the service to provide advice on capacity-aware placements in other contexts with help from the exposed Placement Advice API to manage different types of IT infrastructures. For more information, refer to CAPA API.