Features integrated with BMC Cloud Lifecycle Management

The following sections explain how you can troubleshoot the integration of TrueSight Capacity Optimization features with BMC Cloud Lifecycle Management.

The integration architecture

The following diagram summarizes the integration architecture and shows how the different components interact to provide data for BMC Cloud Lifecycle Management.

Architecture of the integration between TrueSight Capacity Optimization and BMC Cloud Lifecycle Management


The integration architecture comprises the following key steps, as shown in the figure:

  1. The TrueSight Capacity Optimization Cloud DB ETL, automatically created during the deployment of the CLM integration, connects to the CLM Cloud DB API and imports the cloud structure in TrueSight Capacity Optimization, creating a domain called Cloud Infrastructure in the Workspace section of the TrueSight Capacity Optimization Console.
    • After the execution of the ETL, a dedicated task creates scenarios and prepares data based on the cloud infrastructure to allow Capacity-aware Placement Advice calls. For more information on customizing the task settings, see Advanced settings for Placement Advice scenarios.
    • A task chain called CLM Placement Advice Chain is installed; for more information on this chain see Settings for CLM Placement Advice Chain.
  2. Performance data is imported in the TrueSight Capacity Optimization Data Warehouse using ETL connectors for the selected data sources. Out-of-the-box, TrueSight Capacity Optimization provides integrations for the following:
    1. Citrix XenServer
    2. VMware vCenter.
  3. The Capacity-aware Placement Advice service, that runs inside the TrueSight Capacity Optimization Data Hub, is called by CLM to advise on the provisioning of virtual machines based on the available capacity. To do so, CLM relies on the BCM Provider, that is an implementation of the CLM Advisor API.
Understanding Placement Advice statistics

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

These statistics are particularly useful to verify the correct deployment of the Capacity-Aware Placement Advice service after Steps 1 and 2 of the installation procedure described in Installing components for CLM, that is, when the service has been deployed on TrueSight Capacity Optimization and performance data has been imported, but the Capacity-aware Placement Advice service has not been registered on CLM yet (Step 3).

Clicking on 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 Component Status Checker 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 Capacity-Aware Placement Advice 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.

If the number of total errors is greater than zero, it may mean that the Capacity-Aware Placement Advice 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 completing Step 3 of the installation procedure described in Installing components for CLM, that is, when the Capacity-aware Placement Advice service is registered on CLM, 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.
  • 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

Troubleshooting the Capacity-Aware Placement Advice service

The Capacity-Aware Placement Advice service allows you to make choices for the placement and provisioning of virtual machines based on the available capacity. This service runs inside TrueSight Capacity Optimization Data Hub; for more information, see Viewing backend services.

To verify that it is working properly and is ready to be used in connection to with BMC Cloud Lifecycle Management for placement advice, access the TrueSight Capacity Optimization Console and navigate to Administration > Data Hub > Status; then, perform the following steps:

  1. Check the status of the API Providers - Capacity Aware Placement Advice service by looking at the color of the corresponding row:
    • Green: The service is active.
    • Red: The service is inactive due to deployment errors.
    • White: The service has not been deployed.
  2. Click the  icon at the end of the row to inspect the application log for the most recent executions of the service. Error messages are identified by a unique error code; for more information, see Troubleshooting TrueSight Capacity Optimization - error codes.
  3. Click API Providers - Capacity-Aware Placement Advice service in the Active services table to access the detail page for the service, where you can view statistics for the last three five minute execution intervals. 

    Capacity-Aware Placement Advice Statistics page

Using csm.log files present on the CSM PlatformManager server to debug CAPA

The csm.log files present on the CSM PlatformManager server (PlatformManager/log) also aid in debugging Capacity-Aware Placement Advice, and various integration and functionality issues. The data in the log file includes:

  • Placement advice calls generated by BMC Cloud Lifecycle management
  • Requests sent by BCMProvider and responses from Capacity-Aware Placement Advice API

Troubleshooting CLM Cloud

If your installation of the CLM Cloud view is showing incomplete data, or none at all, you must examine the logs of the following TrueSight Capacity Optimization components:

  • TrueSight Capacity Optimization view log: To view it, follow these steps:
    1. Log in to the TrueSight Capacity Optimization Application Server.
    2. Access the folder $BCO_HOME/web/log; for example, /opt/cpit/web/log.
    3. Open the file dash.log
  • Cloud Capacity ER Materializer task log: To view it, perform the following steps:
    1. Access the TrueSight Capacity Optimization Console and navigate to  Administration >ETL & SYSTEM TASKS> System tasks.
    2. Locate the Cloud Capacity ER Materializer task. 

      Locating the Cloud Capacity ER Materializer task


    3. Click the  icon at the end of the corresponding row to inspect the task log. 

      Viewing the Cloud Capacity ER Materializer task log


Was this page helpful? Yes No Submitting... Thank you

Comments