Integration [683] - CDA & Operations Manager for UNIX Integration

The HP Operations Agent (HP OA) is modeled as platform software in HP CDA and the deployment of the agent is triggered along with the deployment of the platform software. Additionally, based on the Application layers, the corresponding OM monitoring policies are deployed and configured, and you can configure the appropriate thresholds and alerts in HP OMX.

The HP OA reports monitoring data to the OM server. HP CDA receives events in XML format over HTTP from the HP OMX Server, when any of the threshold values configured are violated. You can view the monitoring status on the HP CDA user interface based on the events received.

The deployment of HP OA and the reception of events from the HP OMX Server are supported in hybrid cloud environments based on Amazon EC2 or HP Cloud.

The current personas / use cases for integration are as defined below. Integration of monitoring polices are limited to Infrastructure SPI, Weblogic Application SPI, Oracle Database SPI.

The Integration is limited to OM Linux (OML) only.

• As a platform designer, I can use the HP OA as platform software which will cause it to be deployed when the platform is created. This implies that it will also be un-deployed and removed from the OML Server when the platform is torn down.
• As a platform designer, I can use a machine image that has the HP OA pre-installed. When the  machine is created from this image, I can automate configuring the agent to connect to my OML Server. This implies that the agent will also be removed from the OML server when the machine is torn down.
• As a application designer, I change configuring monitoring policies to deploy / un-deploy as application are deployed and undeployed. For example, I can deploy my database monitoring policy when a database is created and remove it when the database is deleted.
• As a user, I can see the status of deployed monitors in my CDA UI. This implies that the monitoring tool (in this case OML) can send monitor status events to CDA.
• When monitors are deployed within a policy we require the monitoring tool to provide a unique identifier (as a String) for each instantiated monitor. This identifier can be composed by concatenating enough information to provide a unique identity but it must also appear in the events we receive as a custom attribute.
  • As a user, I can drill down from the CDA UI into the OM UI in the context of a deployed monitor.
  • As a user, I can modify the OM monitors (add or remove) that have already been deployed.

Currently we are following an approach that is not platform independent and to make it independent will have to write two different methods in the Monitoring Adapter one for UNIX and one for Windows.

• CDA post infrastructure provisioning will invoke the ignite script which will generate the certificate and establish the communication between managed node and server (HP OML).
• CDA user will pass the HP OMU server information and policy information to CDA and CDA OM groovy file has two methods deploy and undeploy which will create the SSH connection to OML server and it will execute the necessary OM server commands.
• OML server will deploy the policy on the managed node
• Agent will send the monitor event response back to the OML server
• OML server will forward these responses to the CDA using integration point