Server Workflows for HP Matrix Operating Environment Technical white paper April 2012 Contents Introduction ..................................................................................................................................2 Overview.....................................................................................................................................2 Extensible Server Adapter ......................................................................................................
Introduction This document is intended to provide information regarding usage and customization of the HP Matrix Operating Environment (Matrix OE) server workflows. The HP Matrix infrastructure orchestration User Guide contains basic information on using the server HP Operations Orchestration (OO) workflows delivered with Matrix OE.
Figure 1: Matrix OE component interactions Matrix OE with infrastructure orchestration Storage Provisioning Manager VCEM Extensible Server Adapter HP blades with Virtual Connect Operations Orchestration Server Workflows • Get Inventory • Get Server Information • Power ON • Power OFF iLO CLI The Extensible Server Adapter uses HP Operations Orchestration (OO) workflows to perform tasks (such as the server workflows shown in the diagram above and discussed below).
Figure 2: Reference OO workflow asynchronous implementation The following sections provide more details on the server OO workflows, configuration and use of the reference implementations included with Matrix OE, and information on how to customize the workflows for specific environments. Deploying Server Workflows The server workflows need to be deployed on Operations Orchestration (OO).
The sections below explain the details of installing ESA and setting up the server workflows with necessary configurations required on both ESA and OO. Installing ESA ESA is packaged with Matrix OE software. When Matrix OE is installed, ESA will be installed under C:\Program Files\HP\Virtual Server Environment\esa. The ESA service (HP Extensible Server Adapter) will start running immediately after successful installation of Matrix OE.
Note: The default OO port on the CMS server is 16443. This might be different on a remote standalone OO server. The user needs to configure the OO port appropriately. Configuring jetty.xml The jetty.xml file, located under C:\Program Files\HP\Virtual Server Environment\esa\etc, needs to be modified for ESA to interact with remote standalone OO server, as shown below: PAGE 7Installing on a remote standalone OO server The server workflows can be set up on a remote standalone OO server by installing the ESA-OO reference kit. The ESA-OO reference kit will be installed along with ESA on the CMS server and can be found under C:\Program Files\HP\Virtual Server Environment\esa\ref impl. The ESA-OO reference kit has a dependency on OO Extensions libraries, which implement the ESA callback IAction classes.
4. In the Import window, expand the items using the “+” button task bar. 5. Select the ESA folder from the items list, and make sure that “Upper Arrow” symbol is selected under “Action” column. The “Description” column will display “Modify in repository” against all the selected items. 6. Click the “Apply” button, which is the last icon on the task bar. This will start importing ESA server workflows into OO repository. 7. Click “OK” to close the import window. 8.
4. Save and close the Hpio_Install_Path property window. There are other configurations required specific to the server workflow operations., Details are given in the respective sections in this document. Upgrading the server workflows After upgrading from one version of HP Matrix Operating Environment to another, the administrator will typically also want to upgrade the server workflows. This step should be done after successful upgrade of Matrix OE itself.
After deleting the ESA folder, select the Hewlett-Packard folder, right click and select Repository -> Check-In Tree operation. This completes the deletion of existing server workflows from the OO repository. Note: The deletion of existing workflows is required if the CMS is upgrading to any Insight Dynamics release prior to 6.3. Note: The deletion of existing workflows is not required if the version of Insight Dynamics/Matrix OE being upgraded is 6.3 or later.
5. Select the ESA folder from the items list, and make sure that “Upper Arrow” symbol is selected under “Action” column. The “Description” column will display “Modify in repository” against all the selected items. Note: If the Insight Dynamics 6.3 release or later is being upgraded, then only the changed items will be selected for upgrade. The “Description” column will display “Modify in repository” for only those items. 6. Click the “Apply” button, which is the last icon on the task bar.
4. In the Import window, expand the items using “+” button task bar. 5. Select the ESA folder from the items list, and make sure that “Upper Arrow” symbol is selected under “Action” column. The “Description” column will display “Modify in repository” against all the selected items. Note: If the Insight Dynamics/Matrix OE 6.3 release or later is being upgraded, then only the changed items will be selected for upgrade. The “Description” column will display “Modify in repository” for only those items. 1.
Setting no default value (or setting default value to 0.0.0.0) for the jetty.host property will allow jetty server to listen requests from localhost as well as from remote servers. Note: For any reason if ESA is not running, the above configuration may lower the security level on the CMS server, as the ESA ports (52000 and 52001) will be available as “Open” ports.
Locations of XSD and WSDL files Once ESA is installed as part of Matrix OE, the WSDL is available at http://localhost:52000/esa/services/serverservice?wsdl. The XSD file (esa-server-model-1.0.xsd) can be found at C:\Program Files\HP\Virtual Server Environment\esa\etc\xsd\esa-server-model-1.0.xsd. Supporting servers not using Virtual Connect The Matrix OE solution provides support for a range of servers, including blades using Virtual Connect, blades not using Virtual Connect, and rack-mount HP servers.
ILOUser - This is the management console user credentials for HP servers not using Virtual Connect (servers using Virtual Connect are managed by Matrix OE using Virtual Connect). Figure 4: Configuring the system account Figure 4 shows the use of OO Studio to create the ILOUser. The credentials are stored in an encrypted form within Operations Orchestration. Note: Username and password are the server’s remote management interface user credentials.
A sample inventoryList.xml file is listed below. PAGE 17Figure 5: Get Inventory workflow Extensibility: 1. To add more servers not managed through Virtual Connect, edit the inventoryList.xml adding new as appropriate. 2. The Adding a new server type section summarizes the changes for a new server type across the workflows. Further Improvements: The reference implementation uses a file-based approach for inventory purposes.
A sample serverinfo.xml is shown below (containing one server). The format of serverInfo.xml should adhere to the schema defined in esa-server-model-1.0.xsd (located at C:\Program Files\HP\Virtual Server Environment\esa\etc\xsd). It provides details about permissible values and required formatting. Failing to adhere to the XML schema will result in failure of the Get Server Information operation.
PAGE 20Note: The Extended Attributes provide key-value pairs such as Enclosure and EnclosurePosition. If the attributes are set, infrastructure orchestration will read the information and report location information of the servers. Matrix OE will determine the LAN and SAN connectivity for the server based on the networkInterfaceName and sanFabric values from this file. Thus, it is key these values match what will be used when specifying resource requests which may be fulfilled by these servers (e.g.
Integrity c-Class blades not using Virtual Connect and rack-mount servers As noted earlier, Matrix OE is able to automatically gather information regarding (and perform power operations on) blades using Virtual Connect. OO workflows are needed for Integrity c-Class blades not using Virtual Connect, or Integrity rack-mount servers.
Figure 7: Subflow to get the power status of the server Extensibility: 1. To add new servers not managed by Virtual Connect (Matrix OE is able to gather information directly for servers using Virtual Connect), add its UUID in the inventoryList.xml, IP address of its remote management interface in the uuidHostMapper.xml and the server specific details in the serverinfo.xml file. 2.
Figure 8: Server power ON workflow Figure 9: Server power ON workflow: subflow 24
Figure 10: Server power ON workflow: subflow SSH command (“power on” for ProLiant) The OO workflow subflow for PowerOn invokes the appropriate iLO command via SSH. Figure 10 shows “power on” being used for ProLiant iLO2 servers; Integrity servers use the “PC –on” command. Extensibility: 1. Understand the Power ON OO workflow 2. Add a new check in the subflow for the corresponding server type; the Adding a new server type section summarizes the changes for a new server type across the workflows. 3.
Figure 11: Server power OFF workflow Figure 12: Server power OFF workflow: subflow 26
Figure 13: Server power OFF workflow: subflow SSH commands The OO workflow subflow for PowerOff invokes the appropriate iLO command via SSH. Figure 13 shows HP ProLiant servers using the iLO2 “power off” command for a standard power off, and “stop –force /system1” for a forced power off. Integrity servers use the “pc –graceful” and “pc –off” commands. Extensibility: 1. Understand the Power OFF OO workflow 2.
The details of the server-related IAction classes are listed below. Iaction Class Inputs Description IActionGetServerInventoryCallback esaMessageID inventory opStatus faultInfoList esaMessageID (reused from workflow input) List of servers in the inventory as XML. Status of OO Workflow (SUCCESS or FAILED). Error string from one or more workflow operations. opStatus is set to SUCCESS, the default value for faultInfoList should be set to “No fault”. replyToURI (reused from workflow input).
Once the information is collected, the following operations can be supported on the new server: Get Inventory Get Server Info Server Power ON Server Power OFF The following subsections explain implementation details of adding these operations for the new server. It is a summarization of information noted earlier in the Extensibility section of the discussion of each workflow.
After performing the above steps, the Get Server Info operation can be invoked from ESA by providing the new server’s UUID in the serverContextList parameter. The returned server details for the new UUID will contain the new server data along with the last known (if not most recent) power status data.
The following steps explain how to support the Power OFF operation on a new server: Implement the logic to execute a Power OFF operation on the server’s remote management interface into a new subflow.
On the - Debug window, select the “Play” button to execute the flow o During execution, provide appropriate values for the flow parameters o The flow execution can be paused and/or stopped any time for debugging the intermediate steps o The execution results can be monitored on the “Transition History” pane and the result can be viewed for each transition step “Step Result Inspector” pane o The flow can be re-executed by clicking the “reset” and “play” buttons For more information on
Note: ESA logs are enabled by default; no specific settings are required. The log file is located at: C:\Program Files\HP\Virtual Server Environment\logs\esa.log. ESA not calling OO A call from ESA to an OO workflow can fail for following reasons: o HP SIM service is not running or not responding o OO RSCentral service is not running or not responding o OO RSJRAS service is not running or not responding o ESA (esa.
o Ensure the network connectivity and accessibility of the remote server management interface o Check and ensure the user credentials configured in the OO System Account is valid for the remote server management interface (and appropriate use of the server UUID) o Check and ensure that the service being invoked through the workflow is enabled and running on the default port Unable to set/retrieve value from registry The OO Workflows may fail with the error “Unable to set/retrieve value from registr
Power ON is failing The Server Power ON workflow can fail for following reasons: Missing server data files – inventoryList.xml, serverInfo.xml and uuidHostMapper.
o Ensure that there is network connectivity and accessibility to connect to the remote server management interface o Ensure that valid user credentials are configured in the OO System Account o Ensure that the command being invoked on the remote server management interface is valid o Check the OO Central reports or central_wrapper.log file for any fatal errors during execution of the flow. In case of fatal errors in OO logs and/or Central reports, ESA would have sent a “Timeout” response to LSA.
For more information The following links provide additional information about HP Operations Orchestration: http://www.hp.com/go/oo http://support.openview.hp.com/selfsolve/manuals (select Operations Orchestration) Operations Orchestration Software Development Kit (SDK) available online at http://support.openview.hp.com/selfsolve/document/KM906363/binary/OO9.00_AuthorOOFlows.
