HP Matrix Operating Environment 7.1 Infrastructure Orchestration User Guide Abstract This document provides an overview of infrastructure orchestration, which delivers advanced template-driven design, provisioning, and ongoing operations for multi-node, multi-tier infrastructure services.
© Copyright 2009 – 2012 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Introduction.............................................................................................10 Automated infrastructure design provisioning and management....................................................10 Matrix infrastructure orchestration and the Matrix Operating Environment solution...........................11 Matrix infrastructure orchestration users and groups.....................................................................
Hyper-V virtual machine management templates................................................................41 Microsoft System Center Virtual Machine Manager (SCVMM) templates....................................42 Configuring ESX memory oversubscription.............................................................................42 Using Sysprep to customize Windows systems........................................................................43 Installing Microsoft Sysprep tools...........................
Matrix OE infrastructure orchestration self service portal...............................................................87 Accessing the infrastructure orchestration self service portal.....................................................87 Self service portal interface overview....................................................................................88 4 Matrix infrastructure orchestration provisioning and allocation........................
Physical storage provisioning..................................................................................................146 Service template defines storage by Selecting a storage template...........................................146 Service template defines storage by Specifying desired attributes...........................................147 Virtual storage provisioning....................................................................................................
Error deploying logical server: Copy virtual machine failed: Unable to access file vmware-template-name.vmdk........................................................................................170 Start function on virtual machine failed: there are not enough licenses installed to perform the operation...................................................................................................................171 Select or create an empty folder as the target destination.............................
Networks tab does not retrieve network information..............................................................183 Request details displays allocated when a reservation process finishes....................................183 Users are not able to login to infrastructure orchestration after installation or after assigning the user to a different infrastructure orchestration group..............................................................
Create Service request does not complete successfully after CMS crash recovery.................192 Deactivate physical server does not complete successfully after CMS crash recovery.............193 Activate/deactivate virtual server does not complete successfully after CMS crash recovery....193 Create/delete virtual server does not complete successfully after CMS crash recovery..........193 Add Disk request for an ESX virtual server does not complete successfully after CMS crash recovery ...................
1 Introduction HP Matrix Operating Environment infrastructure orchestration extends HP Matrix Operating Environment to provide rapid provisioning and repurposing of infrastructure services from shared compute resource pools using a Self Service Portal.
A self service user or a self service user in an organization selects an existing template and then requests infrastructure provisioning from it, against an assigned pool of resources. A service provider administrator or organization administrator can approve or deny this request, and monitor its progress.
Matrix infrastructure orchestration users and groups Matrix infrastructure orchestration is integrated with Active Directory, which allows Windows Users Groups, as well as individual local users, to be given access to resources. When infrastructure orchestration is installed, three local User Groups (HPIO_Administrators, HPIO_Architects and HPIO_Users) are created.
Software deployment and service provisioning Matrix infrastructure orchestration supports a variety of mechanisms for operating system software deployment. Operating system software can be realized as an image derived from a virtual server, or as deployment software such as an Insight Control server deployment job, an Ignite-UX job, or an HP Server Automation (SA) job. Each subtype represents an approach for offering selectable software that can be installed on a physical or virtual server.
Content The content supplied with the limited version is a subset of the content that is available in the full version of Operations Orchestration and is related to Infrastructure-as-a-Service workflows. An upgrade to the full version of Operations Orchestration provides additional content. API and CLI support Matrix infrastructure orchestration supports an Application Programming Interface and a Command Line Interface (ioexec).
2 Installation and configuration Installing infrastructure orchestration Matrix infrastructure orchestration is installed through the HP Insight Management Installer. When using the installer, be sure to select all the required software and have the HP Insight Control and SMTP parameters available to use during installation. For more information, see HP Insight Management Installation and Configuration Guide on the HP Insight Management DVD.
instance at one service provider today and at another tomorrow, as long as the license is not used for both instances at the same time. For details on licensing, contact your HP sales representative. Configuring infrastructure orchestration users in Windows The Insight Management Installer adds the user who performed the installation to the HPIO_Administrators group.
At the Organization level, there are two roles: • Organization Users Have the privileges of _ Users group and have similar capabilities as the Service Provider HPIO_Users role. Can log into infrastructure orchestration self service portal (https://:51443/ssp/). • Organization Administrators Have the privileges of the _ Administrators group.
Matrix infrastructure orchestration access Group membership requirement1 HPIO_Architects Designer HPIO_Administrators, or HPIO_Architects Self service portal HPIO_Administrators HPIO_Users Organization administrator portal HPIO_Administrators2 HPIO_Users 1 2 A user who is not a member of one of those groups is not authorized to use infrastructure orchestration regardless of the authorizations configured in Systems Insight Manager.
NOTE: When infrastructure orchestration is upgraded to a new version, administrator modifications to individual properties in hpio.properties are migrated to the new version of the file unless the default value of the property changed in the new version. In that case, the value of the property is overwritten by the new default value included in hpio.properties. For example, in an earlier version of infrastructure orchestration, the value of timeout.get.
Manually enabling federated CMS in new installations Federated CMS is enabled by default in new installations. However, during the installation procedure, if the CMS IP address is not resolved to the Fully Qualified Domain Name (FQDN), one of the following errors is displayed: Failed to enable HP Insight Orchestration Federated mode. HP Matrix OE infrastructure orchestration was successfully installed but the federated CMS feature was not enabled.
• after federated CMS is enabled manually after a new Insight Management 7.1 installation that did not successfully enable federated CMS IMPORTANT: In a federated CMS environment, the Fully Qualified Domain Name (FQDN) of any participating CMS cannot be changed. If the IP address of the primary CMS is changed, reconfigure the trusted list of each secondary CMS (described in step 1 below). 1.
wrapper.java.additional.15=-Dfed.cms.name=CMS-blue.hp.com 6. Verify hostname and primary CMS FQDN a. On the primary CMS, open a prompt dialog b. Enter mxgethostname and note the hostname that is returned c. In Systems Insight Manager, select Options→Federated CMS Configuration…. The name of the primary CMS should be the same as the one returned by mxgethostname. Support for a rolling upgrade of a CMS federation Matrix OE infrastructure orchestration 7.
IMPORTANT: If you configured secondary CMSs for use in a federated CMS environment, ensure that each SAN storage volume is managed by only one HP Storage Provisioning Manager. (A storage array can be shared by multiple SPMs.) HP recommends that you select the HP Matrix Default Storage Template, and optionally define additional attributes, when configuring physical storage in a service template. Each CMS contains its own HP Matrix Default Storage Template, and these templates are independent of each other.
• Password: the Insight Management service account password specified during the installation If the the Insight Management service account password is subsequently changed using the Systems Insight Manager Reconfigure CMS Tools (mxreconfig), the changed the Insight Management service account password is not reflected in Operations Orchestration Studio and database. Manually change the Operations Orchestration Studio and database passwords as described in the HP Systems Insight Manager User Guide at www.
address. If you specify more than one address, use the semi-colon (;) as an address separator. Do not use a final semi-colon. For example, if you are configuring only one email address, specify email@address.com. If you configure more than one address, specify email1@address.com;email2@address.com. 6. 7. See “Specifying SMTP credentials and system properties” (page 25) for information about additional Operations Orchestration requirements.
Approval emails sent to the infrastructure orchestration administrator includes a URL to be followed for approval. The URL can be followed only once. However, to avoid running an Operations Orchestration workflow when approval is required, modify the ..\Program Files\HP\Matrix infrastructure orchestration\conf\hpio.properties file and change oo.service.approval.action.enabled=true to oo.service.approval.action.enabled=false.
Configuring a remote instance of Operations Orchestration Studio You can download Operations Orchestration Studio from a CMS where infrastructure orchestration and Operations Orchestration Central are installed, and then install Operations Orchestration Studio on another computer. NOTE: Only one instance of Operations Orchestration Studio can connect to the Operations Orchestration CMS at any time. Downloading Operations Orchestration Studio To download Operations Orchestration Studio: 1.
5. Specify Operations Orchestration information as described below, then click Next to complete the installation. • In the Host Name or IP Address field, enter the IP address of the Operations Orchestration CMS machine from which Operations Orchestration Studio was downloaded. • In the HTTP Port Number (usually 80 or 8080) field, change the value to 16080. • In the HTTPS Port Number (usually 443 or 8443) field, change the value to 16443.
3. 4. 5. Orchestration\Studio\conf\rc_keystore), overwriting the existing instance of that file. Restart Operations Orchestration Studio. In that same directory, open studio.properties and change the value in dharma.studio.ui.input.constant.max.chars to 65536. When launching Operations Orchestration Studio, enter “admin” as the user name and enter your CMS password. Copying keystore file after upgrading Operations Orchestration After upgrading Operations Orchestration from version 7.51 to 9.
NOTE: If you copy and paste these commands, be sure to enter the dash (minus) key. In some cases, copying and pasting results in characters that appear to be the same but are incorrect.
5. 6. To create a job folder for each required operating system, repeat this procedure. To enable adding computers to the domain during provisioning, configure the Insight Control server deployment domain authorization using Tools→Options→Domain Accounts. Enclosures are discovered by Systems Insight Manager through the iLO IP address of the enclosure. Be sure to use the iLO credentials of the Onboard Administrator enclosure as the WBEM credentials. 7. 8.
a. 32 Right-click the Erase ProLiant Hardware job under the HP Deployment Toolbox→ Hardware Configuration folder, and then select Copy from the menu.
b. Right-click the HP Deployment Toolbox→Hardware Configuration folder, and then select Paste from the menu. 2. Delete tasks 1, 3, 4, and 6 from the default Erase job: a. Double-click the Erase ProLiant Hardware job. The Job Properties window appears. b. In the Job Properties window, keep the Ctrl key pressed while selecting tasks 1, 3, 4, and 6 (the tasks become highlighted as shown), then click Delete. 3.
a. Select the Power Control task, and then click Modify. b. Select the Shut down (if available) option, and then click Finish.
c. In the Job Properties window, make sure that the modified Erase ProLiant Hardware job displays, then click OK to close the window. Configuring Ignite-UX Matrix infrastructure orchestration supports Ignite-UX version C.7.11.439 (HP-UX 11.31 1009) or later for HP-UX 11iv3 deployment. (HP-UX 11iv3 0709 or later is required for Integrity VM.) The Ignite server must have NFS configured and the tftp and bootps services enabled in /etc/ inetd.conf. a.
6. In Discovery, click Run Now. Integrity VM Guest Kit installation The HP-UX vPars and Integrity VM Guest Kit must be set up on the Ignite-UX server to properly ignite an HP-UX guest. Create a “golden image” that includes both the appropriate operating environment and Integrity VM Guest Kit software. Creating a “golden image” ensures you have a properly ignited VM as part of the automatic provisioning process with infrastructure orchestration.
4. 5. 6. 7. 8. 9. 10. 11. 12. Ensure that the Execute Objects Within Folder permission is selected. Select Users & Groups from the Navigation panel. Select the IO user for SA (typically hpiosa). Click Edit in the upper right corner. Select the Client Features tab. Scroll to the section OS Build Plan Management. Set the radio button Manage OS Build Plan to Read. Set the radio button Allow Execute OS Build Plan to Yes. Click Save at the top of the page.
For more information, see the HP BladeSystem Matrix How-To Guide: ESX Host Provisioning at Matrix Operating Environment Information Library. For virtual logical server provisioning to perform correctly, infrastructure orchestration limits the number of virtual logical servers that are sent concurrently to hypervisors for provisioning. The limit is determined by the value of the corresponding hypervisor max.concurrent.requests attribute in the hpio.properties file located in ..
• When vDS networks are discovered into the IO inventory, they can be selected and used when provisioning a service with one or more virtual servers. All additional configuration of vDS occurs outside of IO using vCenter, including configuring virtual machine rate limiting, security, and monitoring of the port runtime states. NOTE: Do not rename a network that is in use by IO services. If a network is renamed using a tool outside of IO, services shown by IO will appear to be using the old network.
2. Open Hyper-V Manager and choose the server to be connected. 1. In the Actions list on the right side of the panel, select Virtual Network Manager.... 2. Select New Virtual Network. 3. Under Connection Type, select External to configure a physical network. 4. Click Add. 5. In the Name field, enter the name of the network. 6. Under Connection Type, select the network interface from the External drop-down list.
Viewing VM templates with data disks VM templates that have data disks defined appear on the infrastructure orchestration console Software tab and can be used in infrastructure orchestration templates. If a VMware or Hyper-V VM template is selected on the Software tab, and that VM template has more than one data disk, a pie chart is displayed. The pie chart shows the relative sizes of the disk definitions in the VM template.
not display on the Software tab of the infrastructure orchestration console, preventing the successful creation of an IO template. Microsoft System Center Virtual Machine Manager (SCVMM) templates Matrix infrastructure orchestration enables the deployment of services using the Microsoft System Center Virtual Machine Manager (SCVMM) template library. This is accomplished by selecting an SCVMM Hyper-V template on the Software tab in an infrastructure orchestration service template.
when there are too many virtual machines in a specific VM Host, and the VM Host starts swapping the host memory to disk. If a more conservative memory oversubscription approach is desired, IO can be configured to use a more restrictive check of the available memory in the ESX host before provisioning a virtual machine. The default value of 2% for the required available host memory can be increased.
Create one Sysprep file for each version of Microsoft Windows, for example: • Copy Sysprep_sample.inf to Sysprep_w2k3_32bit.inf • Copy Sysprep_sample.inf to Sysprep_w2k3_64bit.inf • Copy Sysprep_sample.inf to Sysprep_w2k8.inf • Copy Sysprep_sample.inf to Sysprep_w2k8r2.inf • Edit the product key and any other needed customization in the file. • To cause IO to automatically join new virtual machines to a Windows domain, add the domain administrator credentials in clear text to the Sysprep.
provide disaster protection for recoverable services, see the HP Matrix Operating Environment Recovery Management User Guide available at http://www.hp.com/go/matrixoe/docs. The file dr.properties (installed in the default location at ..\Program Files\HP\Matrix infrastructure orchestration\conf) is used for mapping resources between the Primary and Replica sites. The Matrix recovery management administrator sets the properties in this file.
Operations Orchestration workflows provide system administrators with automatic email notification when operations are performed on recoverable IO services. Set the HPIODRServiceActionRecipients property in Operations Orchestration Studio with the email address(es) of administrators who will receive this notification. See “Configuring Operations Orchestration system properties” (page 23) for more information.
Configuring an environment for cloud provisioning In addition to provisioning with on-premise resources, Matrix OE infrastructure orchestration supports provisioning virtual servers to the following public cloud providers: HP Cloud Services, Savvis, and Amazon EC2. Public cloud bursting is a feature of Matrix infrastructure orchestration that enables enterprises to seamlessly provision public and private infrastructure resources.
A firewall is created as part of the Create Service operation and is uniquely associated with a single cloud server group within a service. An IO user can only change the rules for the firewalls associated with services that they own. Viewing the details of a firewall Details of a firewall associated with a template and service are shown on the Firewall Details pane at the bottom of the infrastructure orchestration console Templates and Services tabs.
Configuring a load balancer A load balancer distributes network traffic and enables optimal resource utilization across servers in a virtual or physical server group. Before beginning the configuration described in the following sections, the system administrator installs and configures a load balancer. A hardware load balancer is installed in an enclosure, and a software load balancer is installed on a physical server or virtual machine.
Optionally, a load balancer expert can customize the packaged Operations Orchestration workflows or develop new OO workflows for additional types of load balancers and add them to the OO repository. An administrator can then configure one or more of these load balancers and add them to the inventory (described in “Registering a load balancer” (page 50)).
and/or a certificate ID. These IDs are the keys to an actual password or certificate that is stored in IO. This allows more than one load balancer to use a common password or certificate. The IO administrator can manage passwords and certificates in IO using ioexec commands and the SOAP API. Typically, a load balancer has access to a private and a public network, and has an IP address on a management network.
At least one network must be selected. All networks in the server group are displayed. Only a load balancer that has access to the selected networks will be allocated. The attributes of a load balancer that you can select for a server group are as follows: High Availability Requests a load balancer in a redundant configuration. This means that there are two or more load balancers that back up and monitor each other.
Table 2 ioexec create and delete load balancer group commands ioexec command Description creategroup logicalloadbalancer Creates a group in a logical load balancer. A group describes a service to load balance deletegroup logicalloadbalancer Deletes a group from a logical load balancer, and removes all group members NOTE: The create logical load balancer operation using the SOAP API or the ioexec CLI requires administrator approval.
-s example-io-service IO service name in which to add the logical load balancer group -l LogicalLoadBalancer: Logical load balancer ID, located on the on the Services 00000000-0000-0000-0000-000000000000 tab. To view the ID, select a service and click Details, then select the Load Balance tab -g http-group Name of the group to be added to the load balancer. This is an arbitrary name specified by an administrator for easy recognition -P http Type of protocol the application service will use -a 10.1.
C:\> ioexec removegroupmember logicalloadbalancer -s example-io-service -l LogicalLoadBalancer:00000000-0000-0000-0000-000000000000 -g http-group -a 192.168.200.10 -u administrator Viewing details of a load balancer Details of a load balancer associated with a service are shown on the Services tab of the infrastructure orchestration console, self service portal, and organization administrator portal. Select a service and click Details, then select the Load Balance tab.
Table 4 Load Balance tab details (continued) Load Balance tab Description IP Address Virtual (external) IP address associated with the DNS name of the service. Members A comma separated list of IP address and port pairs. Each pair describes a server that serves the actual content of the service (website, ftp site, database, and so on). These are IP addresses of the servers in the server group.
Configuring infrastructure orchestration resources in Systems Insight Manager After installing infrastructure orchestration, a member of the HPIO_Administrators Windows group can log in to the infrastructure orchestration console through Systems Insight Manager. HPIO_Administrators can then set up resources to allow provisioning. To log in to the infrastructure orchestration console, in Systems Insight Manager, select Tools→Infrastructure orchestration.
Before using infrastructure orchestration, set up server pools and networks, and verify the Users and Software tabs using the infrastructure orchestration console.
Add information about the network and available IP resources on the Edit Networks page. Depending on your configuration, not all fields are required. The user interface helps guide you through the process. NOTE: 3. Matrix infrastructure orchestration supports IPv6 with the following restrictions. • Physical or virtual servers can be automatically provisioned using DHCP address pools. Automatic IPv6 address configuration using static assignment or an address range is not supported.
4. 5. After adding the appropriate information to the tabbed areas of the Edit Networks screen, add the IP ranges for use by infrastructure orchestration. • To add DHCP address space, click the up arrow in the DHCP Addresses area, or enter the number of DHCP addresses to make available to infrastructure orchestration. • To add static address space, click New. A dialog appears for the range. Enter a Start and End address (inclusive), and then click OK. When finished setting up a network, click Save.
adding the NICs to a vSwitch). This is best accomplished through naming conventions and customized Operations Orchestration workflow scripts to configure the OS networking. • A VLAN is carried by one or more Virtual Connect tunnel networks or other trunk networks in the environment. A VLAN cannot be a trunk network.
Following is an example of a Virtual Connect tunnel trunk configuration. Physical networks discovered from Virtual Connect are represented as a subnet whether they are a single network or a tunneled trunk network carrying multiple subnets. Matrix infrastructure orchestration represents Virtual Connect networks based on the VC network configuration.
• Cannot be mapped to a multi-network VC profile NIC port • Cannot be part of a shared uplink set Virtual Connect mapped trunk configuration A Virtual Connect mapped trunk configuration enables VC to play a more active role managing traffic on the VLANs, including designating one of the VLANs to handle untagged packets from the VM Host. This constitutes hybrid support for both tagged and untagged networks on the VM Host.
While a request is paused, the administrator can make the necessary modifications to the environment to make the network available for allocation. When the request continues, another attempt is made to allocate the network. The service request continues only when the network resources are available. VLAN carving allows a single template definition to be used by multiple organizations, each having its own VLAN that may not yet be defined until the request is submitted.
3. Define the VLANs that can be carried by one physical network. a. In the infrastructure orchestration console Networks tab, click Create Network. b. Specify a VLAN ID, and set Network Address, Network Mask, Default Gateway, MS Domain, and WINS Servers for that VLAN ID by clicking the appropriate tab and filling in the information. In a multi-home scenario where there are multiple default gateway options, IO determines the default gateway from the network connected to the NIC that is declared as primary.
Configuring trunk and VLAN networks to enable support for Hyper-V VLAN tagging VLAN tagging is the practice of inserting a VLAN ID into network data to identify the VLAN to which the data belongs. CAUTION: Combining tagged and untagged Hyper-V virtual machines on the same virtual network results in network failures. HP recommends that you maintain a homogenous network environment among cooperating Hyper-V VM Hosts.
Non-disruptive (workaround) method The non-disruptive method is a workaround that does not disrupt your existing configuration or existing VM guests. You can continue to use existing vNics created with HP Network Configuration Utility (NCU). (This is intended as a temporary workaround until you can migrate your environment using the disruptive method below.) 1.
resource pools are available for infrastructure orchestration to use to provision virtual machines on a standalone VM Host or in a cluster. They enable a cluster to be divided into logical pools of memory and CPU resources above the level of individual VM Hosts. ESX resource pools allow a VM Host or an ESXi cluster to be shared by multiple organizations. ESX resource pools are displayed in the infrastructure orchestration console Servers tab and are labeled as “ESX Resource Pools” in the Type column.
Resources in Virtual Connect Domain Groups Physical resources are only displayed on the console Servers tab and made available after a Virtual Connect Domain Group is created in VCEM. If you have more than one Virtual Connect Domain Group in your environment, as a best practice, make sure that all servers in a server group belong to the same VCDG. VM Hosts deployed on server blades A physical server blade appears as a compute resource in a resource pool.
3. To add a server to a pool, select a server in the list on the left, and then click the >> button. The server moves to the list on the right. NOTE: Unlicensed server blades or virtual machine hosts cannot be moved from the Unassigned pool. Resources can be moved to a pool only after the resource is licensed for use by infrastructure orchestration. For more information, see “Licensing infrastructure orchestration” (page 15). 4. After selecting the resources for the pool, click Save.
5. Assign users to the pool so that infrastructure orchestration can use the new pool. To assign users, select the pool in the list, and then click Modify Users. The Modify Pool Users page appears.
6. Select the user in the Unassigned Users/Groups list and then click >>. Repeat this process for each user. Click Save. The Servers page reappears. To verify that the users are assigned to the pool, select the pool. A list of the assigned users and groups appears at the bottom of the screen. Verifying infrastructure orchestration users and groups The Users tab contains a list of all users and groups authorized to use infrastructure orchestration.
NOTE: The Operations Orchestration workflow authoring tool (OO Studio) may be used to extend the functionality of the reference workflow to support additional management processors as required. Configuring ESA password in Matrix OE visualization Modify ..\Program Files\HP\Virtual Server Environment\conf\esa.properties to include the Operations Orchestration 'Admin' password: esa.oo.admin.password= After making the changes to the esa.
The “inventoryList.xml” file is read from the file system and its contents are then sent directly to the ESA web service. The ESA web service processes the returned XML document and hands it back to logical server management (LSM), which functions as the upper level inventory manager. LSM then makes a second workflow call for each server. serverInfo.xml The file ..\Program Files\HP\Matrix infrastructure orchestration\ esa_extensions\server\serverInfo.
1 68 1 nic0 00:1E:0B:CC:61:B0 vlan84-dhcp-pxe-sa true ProLiant DL380 G5
For each server in the inventoryList.xml file, the “Get Server Info” workflow is invoked. The workflow extracts the detailed server definition from serverInfo.xml, and then uses the server’s management processor to determine the current power state. The server management processor operations are invoked through additional workflows. The persisted power state is updated if required and the resulting server record is returned as an XML document to the ESA web service.
makes use of the serverInfo.xml record to determine the server’s model so that the correct power operation is performed. The same call back pattern is used. At the completion of the workflow, the terminal state of the operation and status information is returned to the ESA web service. Configure management credentials for power control An additional step is required to configure the management credentials for power control. The reference implementation ships with built-in system accounts.
a. b. Edit ..\Program Files\HP\Matrix infrastructure orchestration\conf\ blade_models.properties file. Add the new server model. The server model string is the string entered in the serverInfo.xml file. After making the changes to the blade_models.properties file, restart the HP Matrix infrastructure orchestration Windows service for the changes to take effect.
3 Using Matrix infrastructure orchestration applications Overview Matrix infrastructure orchestration applications support the roles of architect, service provider administrator, organization administrator, and user. • The designer enables an architect to plan and design multi-server, multi-tier infrastructures using a drag-and-drop interface.
Matrix infrastructure orchestration designer maintains a secure cache in the browser of changes made during a design session. If a session times out or the browser is closed, changes are preserved and are available the next time the architect launches infrastructure orchestration designer. Importing and exporting templates Matrix infrastructure orchestration designer allows you to import and export service templates.
Designer interface overview The template editor window contains three major frames: • The Components frame displays the icons for the logical objects used to design a template. • The Existing Templates frame provides a list of available templates. • The right hand frame is a template design area used to build the template by dragging and dropping components on to it. When saving a template, specify a name using letters (A-Z, a-z), numbers (0-9), space, period, underscore, and hyphen.
• Perform pool management • Create and manage organizations To accomplish these tasks the service provider administrator must: • Create resource pools for hosting services based on standardized templates and the business forecast. • Collaborate with the business units to register user accounts for access to the infrastructure orchestration self service portal.
Displays an overview of infrastructure orchestration operations providing statistics, resource usage, and links to access infrastructure orchestration tasks. • Templates Displays all the available templates and enables you to view the details of a template, edit a template, create a new template, delete a template, submit a template for provisioning, and assign users to a template. Displays the organizations to which the template has been assigned.
Console access to deployed servers Matrix infrastructure orchestration supports console access to deployed servers from the infrastructure orchestration console and infrastructure orchestration self service portal. Supported console types include Remote Desktop (RDP) and telnet. RDP and telnet access depend on network connectivity from the client to deployed servers. Servers deployed to non-routable networks cannot be accessed by RDP and telnet.
Accessing the infrastructure orchestration organization administrator portal Access the infrastructure orchestration organization administrator portal from a browser. Navigate to https://:51443/oap/. Users can belong to more than one organization. These users can be simultaneously logged in to one or more of the portals (organization and self service) belonging to different organizations.
For more information on using the infrastructure orchestration organization administrator portal, see the infrastructure orchestration organization administrator portal online-help system by clicking the ? button in the upper-right portion of the infrastructure orchestration organization administrator portal window.
Type in the Organization Title text box to update the name of the organization displayed in the center of the login screen, and on the left side of the title bar at the top of each screen in both portals. Updates can be undone using Restore Default. Changes take place immediately. Use the links to the self service portal and organization administrator portal login pages to verify changes.
Self service portal interface overview The infrastructure orchestration self service portal displays the following tabs: • Home Displays an overview of infrastructure orchestration operations providing statistics, resource usage, and links. • Templates Displays a list of the available templates and enables you to view the details of a template and submit a template for provisioning.
• My History Displays a list of system and important event notices, including the date and time of the event, the result, and description of the event result. For example, if a request fails, the event displays on the My History tab with an explanation of why the request failed. • My Calendar Enables you to search for and view utilization information of your services, graphically displaying usage and conflicts. The calendar displays content relevant to the search context.
4 Matrix infrastructure orchestration provisioning and allocation Matrix infrastructure orchestration lifecycle operations Matrix infrastructure orchestration covers the IT lifecycle, from the initial design of system configurations to the ultimate repurposing of assets. It enables IT resource requests to be handled in a systemic manner than leverages standard configurations, self service provisioning tools, and automated approval processes.
Delete service operation When deleting a service, the Delete operation automatically deprovisions an existing infrastructure and frees the resources for use in other services. To delete a service 1. 2. 3. Open the infrastructure orchestration console, self service portal, or organization administrator portal Select the Services or My Services tab Select a service and click Delete OR 4. 5.
• Creates virtual machine or blade server profile • Deploys the operating system and other software to boot disk • Configures the virtual hardware • Customizes the operating system (networking, Sysprep) • Allocates the physical data disks • Provisions the servers for data disks • Boots the servers • Executes custom actions • Sends notifications After successfully completing the operation, infrastructure orchestration provisions the additional servers into the infrastructure orchestration i
Add data disk to group operation The Add data disk to group operation adds private or shared data disks to an existing infrastructure service. Matrix infrastructure orchestration provisions and allocates the storage to their attached servers. NOTE: You can add a data disk based on the size of an existing data disk, or you can specify the size and other attributes of the data disk to add to the server group.
• Sends notifications When reallocating a server blade, infrastructure orchestration must find a server blade that matches the original logical server definition, and physical characteristics of the previously allocated server blade, including processor architecture and model. In addition, the new server blade must have at least the same number of processors, amount of memory, and processor speed. If infrastructure orchestration cannot find a server blade that meets these requirements, the request fails.
Power off servers To power off servers 1. 2. 3. 4.
During this operation, infrastructure orchestration: • Validates the request for a new lease period • Modifies servers (server blades or virtual machine hosts) allocation for a new lease period • Modifies network and IP addresses allocation for a new lease period • Modifies disk allocation for a new lease period • Obtains approval to extend a lease NOTE: Reducing a lease period does not require approval.
To edit a virtual server 1. 2. 3. 4. 5. 6. Open the infrastructure orchestration console, self service portal, or organization administrator portal Select the Services or My Services tab Select a service and click Details or View Details From the Actions or Server Actions list, select Edit virtual servers Expand the tree and select the virtual machine you want to edit Increase or decrease the number of processors by using the arrows in the Number of Processors field, up to the Maximum (shown in red).
Matrix infrastructure orchestration filters VM Hosts based on service template requirements, including: • Linked clone support (if applicable) • High availability (HA) support (if applicable) • VM template compatibility (if specified as Automatic OS deployment) • Sufficient number of processors • Sufficient available memory • Sufficient available disk space • Network connectivity From these candidates, infrastructure orchestration selects the VM Host that has the most: • Available disk space
• If linked clone provisioning is specified (by checking Deploy as Linked Servers in the server group configuration), all disks for all VMs in the server group are allocated to the same datastore. • If a Storage Volume Name is specified in the infrastructure orchestration template, all disks for all VMs in the server group are allocated to the datastore that matches the Storage Volume Name.
NOTE: Because the volume.exclusion.list values are treated as regular expressions, some characters are interpreted to have special meaning, for example, backslash (\), question mark (?), and brackets {}. To indicate that these characters should be treated as regular characters, they need to be escaped with a backslash. Because a backslash is a special character in the property file syntax, it has to be escaped as well.
◦ Defines the storage in Matrix OE logical server management. ◦ Continues the operation. When the operation continues, infrastructure orchestration reattempts to allocate the resources. This pause is always necessary when infrastructure orchestration is configured to perform manual storage provisioning and data disks are defined in the service template. It may or may not be necessary when multi-initiator NPIV storage features are enabled.
2. Drag one of each of the Physical Server Group (which includes Physical Storage), and Network components onto the working area. 3. Connect the Physical Server Group to the Network.
4. Set the attributes for each of the components. Right click on the Physical Server Group and select Edit Server Group Configuration. Note the Server Type is “Physical.” The Processor Architecture must match the storage pool entry. 5. Set the Networks attributes for the server group.
Specify a Hostname. There are three parts to the physical server's hostname. The first part is defined in this service template. The second part is specified by a user's service creation request. The third part is a numeric suffix based on the number of servers created for this server group. The "#" is used in this template as a replacement string indicating where to place the requestor's portion of the hostname.
When using active/active configuration, the Redundant flag must be left deselected, and you must explicitly wire two separate Virtual Connect networks to represent the same active/active network in the data center. 6. In the Software tab, select the OS and any additional software. 7. (Optional) On the Load Balance tab, request a load balancer containing the specified attributes to distribute network traffic across servers in a virtual or physical server group.
The setting for Redundant SAN paths to disk depends on how you configured your logical server storage pool entries. At least one matching storage pool entry is required for each service provisioned. Those entries may or may not be fully configured with redundant paths. 9. Finish by editing the Network component.
10. Select the appropriate network and (optional) specify a cost. Click Show All Network Details for more information about the selected network. 11. Click Customizable to allow certain attributes of the template to be changed. See “Customizing template attributes when a service is created” (page 117) for more information. (Note that the Recoverable checkbox is not supported for physical server groups.) 12. After you have completed these steps, note that the Validation Status is green.
13. Select the Published box, name the template, and then click Save. This template will now be available for deployment by authorized users. Creating a template with a physical VM Host or ESXi VM cluster The following figure shows the key features of a template that can be provisioned to a physical VM Host or ESXi VM cluster.
1. 2. 3. 4. Launch infrastructure orchestration designer at https://:51443/hpio/designer/ and click New to begin. Enter a template name and drag a Virtual Server Group (which automatically includes Virtual Storage), and a Network component onto the area where the instructions are displayed. Connect the Virtual Server Group to the Network. For each of the components, right click on the component and fill in the required attributes starting with the Virtual Server Group.
Select Deploy as Linked Servers to deploy the servers in the server group as linked, and adjust the maximum number of servers as required. When this option is checked, the first logical server in a linked clone logical server group is provisioned with both a parent VM and a clone (child) VM. The remaining logical servers in the logical server group are provisioned with only a clone VM. For more information about linked clones, see VMware: Understanding Clones. Notice the Server Type is Virtual.
DHCP Indicates that IP addresses are allocated dynamically to servers connected to the subnet using DHCP. Static Indicates that the architect assigns the IP addresses used by each server connected to the subnet. Using static IP addresses creates a template that can be provisioned only one time. Automatic Indicates that IO automatically selects the static IP addresses to be allocated from the static IP address range set for the network. NOTE: 7. For HP Integrity VM deployment, use Automatic.
When you use a Windows template, you can also choose a Sysprep file. The Sysprep files for you to select must be located in ..\Program Files\HP\Matrix infrastructure orchestration\conf\sysprep. When you click the Change button, all of the Sysprep files in the directory are displayed. 8. (Optional) On the Load Balance tab, request a load balancer containing the specified attributes to distribute network traffic across servers in a virtual or physical server group.
9. Set the attributes for the Virtual Storage. Note that the Storage Type must be Virtual. Check Disk is bootable to denote that the disk is the boot disk for the server group. • For bootable disks, you can assign a Storage Volume Name to match mounted volume names on a VM Host. Storage Volume Name(s) is an optional feature for the boot disk. Storage volume names are used for every virtual disk attached to the virtual server group. Enter the VM Host storage volume names separated by commas.
13. Select the Published box and then click Save. This template is now available for deployment by authorized users. Creating a template to provision at a cloud service provider In addition to provisioning with on-premise resources, Matrix OE infrastructure orchestration supports provisioning virtual servers to the following public cloud providers: HP Cloud Services, Amazon EC2, and Savvis.
NOTE: When Systems Insight Manager runs the discovery task, it changes the logical server hostname by prefixing the hostname with the VM Host name and the service template name. For example, if IO provisions a virtual machine named vm1 on a VM Host named VMhost1 using a template named mytemplate, after Systems Insight Manager runs the discovery, the virtual machine hostname is changed to VMhost1_mytemplate_vm1.
8. Enter email address(es) to be notified of progress. Separate multiple e-mail addresses with commas or semicolons. Do not use a final semicolon after the last email address. If an email address is not specified, email notifications are sent to the default email account used when infrastructure orchestration was installed. 9. Specify a Hostname. There are three parts to the virtual machine's hostname. The first part is defined in this service template.
Customizing template attributes when a service is created When you create a service, you can customize the amount of memory and processor count for a server group. You can also customize the network name, IP address assignment types of server group and network connections, and IP address. These customizations allow you to reduce the number of templates in your environment, because different types of services can be created based on one master template.
When you create a service from the template in infrastructure orchestration console, organization administrator portal, or self service portal, you specify the custom attributes on the Create Service Options dialog. These attributes must take the following form: subnet=, addressingType=,,DHCP | AUTOMATIC | STATIC [,...
Changes are highlighted in the “approve or reject” e-mail and in the Request Details pane. The Customizable attribute is shown on the Templates tab. You can also use the ioexec CLI or the SOAP API to customize attributes.
Modifying the create service timeout value By default, infrastructure orchestration sets a timeout of 180 minutes (logical) or 120 minutes (virtual) for server create requests in the ..\Program Files\HP\Matrix infrastructure orchestration\conf\hpio.properties file. Modify this value if needed. # Maximum number of minutes wait for a single physical # CreateLogicalServer operation timeout.create.physical.
2. Select the Create request in the queue, and click Approve. After the job has been approved, it will automatically proceed to be built and deployed with no further interaction required. 3. As provisioning proceeds, the requesting user can monitor progress of the deployment in the infrastructure orchestration self service portal My Requests tab. When the job completes, the requester receives an e-mail notification.
The virtual machine current status and resources can also be seen in the HP Matrix OE visualization view. (From Systems Insight Manager, select Tools→HP Matrix OE visualization.) As an Administrator, you might want to complete the recognition of the new virtual machine by initiating an Systems Insight Manager discovery operation on the IP address now in use by the new guest (follow the steps in “Managing new logical servers” (page 122)).
3. Use the Insight managed system setup wizard (MSSW) to configure the system to be managed. From Systems Insight Manager, select Configure→Managed system setup wizard. For more information, see the Insight Managed System Setup Wizard Getting Started Guide located at the Matrix Operating Environment Information Library. NOTE: Cross-technology logical servers are not supported by Matrix infrastructure orchestration.
to any other resource within the same VC Domain Group. However, connectivity between VC Domain Groups is uncertain. The infrastructure orchestration algorithm verifies VC Domain group boundaries by backtracking, incrementally building candidate solutions for allocation, and abandoning each partial candidate as soon as it determines that it cannot possibly complete the allocation.
Deploying an operating system to multi-path storage Matrix infrastructure orchestration can deploy an operating system to a multi-path storage volume. For Insight Control server deployment, Windows operating systems do not require any server deployment modifications. However, for Red Hat Enterprise Linux 5.4, 5.5, and 6.0, modify the default server deployment process by editing the Configure Boot Environment job. Edit the Configure Boot Environment job and add the export kernparm=mpath kernel parameter.
Specifying fixed costs for templates and services Matrix infrastructure orchestration allows a template architect to add a fixed cost to a template, in addition to server, network, and storage costs. Examples of fixed costs are power or setup costs. Enter a fixed cost in infrastructure orchestration designer by clicking the Cost tab in a template, and entering a value in the Fixed Cost text box. Select a value for Cost Frequency, which is the time interval for which a fixed cost is calculated.
Base Cost per Server Encompasses all of the costs for the server except CPU and memory cost. It may include availability characteristics and type characteristics (physical, virtual, cloud). This cost does not change during the lifecycle of the server. Cost per Processor Cost per CPU in the server. This cost pushes the server cost up and down during the lifecycle of the server based on the changes performed by the user. This allows the server cost to be adjusted together with the server configuration.
In infrastructure orchestration designer, right click on a virtual or physical disk to display the Config tab, where you can enter the cost per disk unit (MB or GB).
Specifying a global cost unit for all templates Convert the global cost unit for a template by right clicking in a blank area of the template design area and selecting Convert Template to use Global Cost Units. This menu selection is enabled only if the cost unit for the template is different from the global cost unit defined by the cost.units.global.value property in the ..\Program Files\HP\Matrix infrastructure orchestration\conf\hpio.properties file.
Table 6 Chargeback reported metrics Metric Value Allocation time Measured in minutes. Represents the time the resource was allocated to an infrastructure service. Collected for all resources inside an infrastructure, including services, logical servers, disks, and IP addresses, and for the infrastructure itself Allocation cost Measured in cost units. Represents allocation time multiplied by allocation cost in minutes.
Figure 2 Sample response from getServicesUsagePage API Using API extensions to retrieve chargeback data 131
Figure 3 Sample response from getServiceUsageDetailPage API 132 Matrix infrastructure orchestration provisioning and allocation
Figure 4 Sample response from getAggregateServiceUsage API Using the CLI to retrieve chargeback data Matrix infrastructure orchestration includes a command line tool to retrieve chargeback usage data. This tool generates an xml file containing chargeback data that can be opened in a browser or using Microsoft Excel. The chargeback.bat tool is found in the default location at C:\Program Files\HP\Matrix infrastructure orchestration\chargeback\bin.
(Enter chargeback --help to see information about the options.) For example, to see allocation usage data for April 23 with the results sent to output.xml, enter: chargeback get usage -S 4/23/2012 -E 4/23/2012 -o output 3. 4. From Windows Explorer, navigate to \chargeback\bin\reports, where the output.xml file is located. To view the results, do one of the following: a. Drag output.xml to your browser's URL bar to view the file in your browser. b.
5 Matrix infrastructure orchestration storage management Matrix infrastructure orchestration supports a range of storage provisioning capabilities to appropriately match the customer environment. Administrators can choose to manually define storage pool entries and manually provision storage, or can take advantage of the Matrix Operating Environment integration with HP Storage Provisioning Manager (SPM). SPM is automatically installed as part of Matrix OE.
Following are the types of storage provisioning available in infrastructure orchestration. The overall system may be used with any or all of the processes combined. • On-demand storage provisioning The storage administrator populates the SPM catalog with arrays and storage pools, then defines storage templates with various policies, including access to those pools. New volumes can be carved from existing pools (by an administrator or by infrastructure orchestration) through the use of storage services.
At service creation, infrastructure orchestration selects one or more storage pool entries from the storage pool. Existing storage pool entries visible to infrastructure orchestration are already associated with storage volumes (through manual fulfillment, or fulfillment though SPM). If there is no suitable storage pool entry and SPM is being used, infrastructure orchestration will create a storage pool entry and attempt to fulfill through SPM.
Manual storage provisioning Manual storage provisioning can be performed using the Matrix OE visualization logical server management Modify→Logical Server Storage Pools screen and SPM. Manual storage provisioning is used when no storage has been pre-provisioned or when only a subset of the storage has been pre-provisioned for a logical server. At service creation, infrastructure orchestration attempts to locate and allocate the storage resources.
b. Select Virtual Connect Enterprise Manager (VCEM) and Storage Pool Entries, and then click Refresh. 4. Click Modify→Logical Server Storage Pools. 5. Select the target Virtual Connect portability group from the Portability Group list.
For detailed instructions about how to add or modify storage pool entries, see the help for the Manage Storage Pool screen or the HP Matrix Operating Environment Logical Server Management User Guide at Matrix Operating Environment Information Library. Predefining storage pool entries in Matrix OE visualization The following example illustrates the selection of a Linux SAN volume to build a storage pool entry. Select Modify→Logical Server Storage Pools from Matrix OE visualization.
For more detailed information on the use cases and how storage is managed in Matrix OE visualization, see the HP Storage Provisioning Manager (SPM) User Guide, HP Matrix Operating Environment Logical Server Management User Guide, and the Faster storage provisioning in an HP BladeSystem Matrix and Insight Dynamics environment white paper at Matrix Operating Environment Information Library.
Populating the Storage Provisioning Manager catalog To use dynamic SAN volume automation, configure SPM for access to one or more arrays. To start SPM, open an internet browser to https://localhost:8000, where “localhost” is the name of the primary CMS. NOTE: By default, Matrix OE finds and communicates with the SPM service using the host specification of “localhost”. If you want to use SPM from Matrix OE in a clustered environment, edit the C:\Program Files\HP\Virtual Server Environment\conf\lsa\ lsa.
A managed array enables SPM to perform certain storage operations such as gathering property information, changing the hostmode, performing LUN masking, or on-demand provisioning. Unmanaged arrays do not support the automated mechanism to change hostmode and LUN masking or perform on-demand provisioning.
From the left navigation bar, select Volumes, then select volumes to import and press Import Volumes.
information, and those for which the HP Matrix Default Storage Template was chosen. Enabling on-demand provisioning is typically done in conjunction with a capacity constraint (for example, no more than 256 GB) and that constraint applies to all requests using the default template. This allows the constraint to be applied to only on-demand provisioned volumes and not pre-provisioned volumes. • By creating a new template and enabling on-demand provisioning for that new template (with a capacity constraint).
6. Select the Resource Existence requirement in the Template read-only requirements. 7. 8. Click Edit. Change the level from Required to Recommended. Verify that Use existing volume is selected. 9. Click OK to exit the Edit Requirement – Resource Existence dialog. 10. Click OK (or Apply). Physical storage provisioning Matrix infrastructure orchestration displays the storage volumes available for provisioning on the infrastructure orchestration console Storage tab.
These storage templates can be viewed and selected in infrastructure orchestration designer when defining a logical disk in a service template, or you can define logical disk attributes manually. In either case, the storage fulfilling the request might be pre-provisioned or newly created on-demand through SPM. The selected storage template requirements are combined with any user modified or added requirements to formulate the goal that the provisioning process meets.
For instructions about how to change “Resource Existence” to enable on-demand provisioning for all manually specified storage, see “Enabling on-demand storage provisioning in SPM” (page 144). NOTE: Any edits made to the HP Matrix Default Storage Template will apply to all manually specified storage.
The virtual storage requirements that can be manually defined are as follows: • Name of the disk. • Individual Disk Size is the size for the disk and specifies if it is in megabytes or gigabytes. For virtual disks, this value sets the actual size of the disk. (For virtual storage, MB x 1024 = GB.) • Cost per GB is the estimated cost per gigabyte in numeric form. • Disk is bootable specifies that the disk will be the boot disk for a server group.
4. If the boot disk reservation still cannot be satisfied, Matrix OE attempts to automatically create an SPE that will be automatically fulfilled though SPM, containing the boot disk and the private data disks. Result: If the boot disk is not fulfilled, the request pauses and raises an email alert (using an Operations Orchestration workflow) requesting manual storage provisioning for the boot and data disks.
6 Multi-tenancy in Matrix infrastructure orchestration Multi-tenancy allows data center resources to be dynamically and securely shared among separate tenants by providing each organization with a virtual infrastructure orchestration system. In Matrix infrastructure orchestration, tenants are known as organizations. For detailed information, see Multi-Tenancy in HP Matrix OE Infrastructure Orchestration and HP CloudSystem Matrix Step-by-Step Guide: Multi-tenancy at http://www.hp.com/go/matrixoe.
◦ Service provider user Can log into the infrastructure orchestration self service portal and initiate requests for provisioning using published templates • Organization The service provider administrator dynamically creates the organization and makes resources available to the organization using the infrastructure orchestration console. See “Creating an organization” (page 154) and “Adding resources to an organization” (page 156) for more information.
Table 9 Resources visible to service provider and organization administrators and users (continued) Resource Origination Service provider administrator controls Service provider user access Organization administrator access Organization user/group access service provider visible if user/group access published AND the template is assigned to the user/group administrator (published and unpublished) administrator (published only) Assign to one or more organizations1 No restrictions Visible if assig
Table 10 Information visible to service provider and organization administrators and users Organization administrator using Organization Administrator Portal Service provider administrator using Console Service provider user using Self Service Portal Users1 Windows users and groups associated with each organization Not visible: Other users Users and groups assigned to the organization Not visible: Other organizations Not visible: Other users Request messages Unrestricted Messages from user’s reque
2. 3. 4. 5. 6. In Organization Name, enter a name for the new organization. Click Add. (Optional) Add organization administrators. Enter the name of a local user, Windows Active Directory (AD) user, or Windows AD group, and click Add User or Add Group as appropriate. (Optional) Add organization users. Enter the name of a local user, Windows AD user, or Windows AD group, and click Add User or Add Group as appropriate. Click Close.
Assigning users to an organization Using the infrastructure orchestration console, the service provider administrator populates the _Administrators and _Users groups by adding pre-existing local Windows users. If the CMS is part of a Windows domain, pre-existing Active Directory users and groups can also be added to the _Administrators and _Users groups.
• A set of infrastructure orchestration templates. IO templates can be assigned to multiple organizations. To assign or unassign resources: 1. From the infrastructure orchestration console Organization tab, select an organization. The organization name is displayed in the right Organization list. 2. From the Service Provider list, select a compute resource, network, or template. Only compute resources that are in the service provider's Unassigned pool and are not in use are available to be moved. 3.
When a service is created for organization_1, the network will bind to organization_1_Production. When a service is created for organization_2, the network will bind to organization_2_Production. NOTE: If you specify a network by selecting “Specify desired attributes”, you cannot customize the network when the service is created. Network customization can be performed only on named networks.
7 Troubleshooting Verifying the CMS configuration Matrix infrastructure orchestration utilizes the vseassist tool and the Systems Insight Manager Diagnose menu to help identify and resolve any CMS configuration issues. The Check CMS Configuration task performs configuration checks on the CMS. To run this task, from the Systems Insight Manager menu, select Diagnose→Troubleshoot Matrix OE→Check CMS Configuration.
Assign a valid user or user group to the HPIO_Users group. (...
Name Description Cloud Capacity Pool Configuration Verifies that there are cloud capacity pools configured, and displays the number of pools. Software Images Available in Cloud Capacity Pools Verifies that there are cloud software images available, and displays the number of images. Cloud Servers No Longer Managed Checks for cloud servers that appear to have been created by IO but are no longer managed by IO, and displays the names of these unknown cloud servers.
Warning — HP Matrix infrastructure orchestration was successfully installed but the federated CMS feature was not enabled. Refer to the HP Matrix infrastructure orchestration User Guide for information about how to enable federated CMS. Possible cause The CMS IP address cannot be correctly resolved to the CMS FQDN during installation, so the Installer adds the CMS IP address to the managed_cms_list property. However, the managed_cms_list must be configured with the CMS FQDN.
At least one OS or software deployment has failed Failure message Task for logical server …. Failure: At least one OS or software deployment has failed. Check the deployment service to diagnose the details. Possible cause • Problem with a LUN allocated to server or firmware issue on server • Insight Control server deployment Erase ProLiant ML/DL/BL Array Configuration {LinuxPE} job has not been modified for infrastructure orchestration.
5. Increase the default timeout from 20 minutes (1,200,000 milliseconds) to 40 minutes (2,400,000 milliseconds). 6. Restart the HP Matrix infrastructure orchestration service. 7. Restart the HP Logical Server Automation service. 8. On the Templates tab, select the template and submit a new create service request. Task for logical server failed due to invalid UUID Failure message Task for logical server has failed. Logical server job (ID = …) completed with a failure status.
6, and 7 and 8. A non-natural pair of fabrics is tried only if there are only two fabrics in the VC Domain Group. Once a pair of fabrics is used for the first volume, all other volumes within the same storage pool entry must be found on the same pair of fabrics, or auto-provisioning fails. Action Use the Matrix OE visualization logical server management Modify→Logical Server Storage Pools screen to manually configure storage.
Cannot add servers to an existing service using a static IP address Issue Cannot add servers to an existing service using a static IP address. Possible cause Static IP allocation limitation. When a service contains multiple servers and the network is configured with static IP addresses, additional servers cannot be added to the provisioned service, even though the infrastructure orchestration interface enables you to create the request without a warning. When this type of request is processed, it fails.
Following are recommended minimums. Depending on the size of memory and number of HBA cards on each server blade, the values may need to be greater than the minimums. • Integrity BL860c and BL860c i2 blades: ◦ For infrastructure orchestration serverboot.physical.wait.seconds, use the default minimum of 360 seconds. ◦ For LSM INTEGRITY_POWERON_WAITTIME, use the default minimum of 360000 milliseconds. • BL870c and BL870c i2 blades: ◦ For infrastructure orchestration serverboot.physical.wait.
Service creation fails in the in the target reconfiguration phase Failure message Service creation fails in the target reconfiguration phase. Service creation intermittently fails when a service is created with RedHat Enterprise Linux 6 OS. Possible cause The target server fails to shut down due to an issue with the HP Health Agents versions 8.70 and older. Action 1. Identify the failed target servers in the Maintenance server pool. a. In infrastructure orchestration, select the Servers tab. b.
• Cancel the request, then resubmit it. NOTE: Use this option to prepare for future changes to the lease period before the service is provisioned. • Restart infrastructure orchestration, which will update the request status.
not match existing servers against memory size, disk space and processor count requirements. Possible cause Matrix infrastructure orchestration's Resource Manager has marked servers as “invalid” during resource discovery because of a communication error between logical server management and OA. Action Check the status of server blades within the enclosures. 1. In the infrastructure orchestration console, select the Servers tab and look at the Enclosures column.
In the message above, “/.../” represents the datastore allocated for the VM; [inactive-datastore-name]” represents the datastore on which the template resides. Possible cause The template selected for provisioning an ESX VM resides on an inactive datastore. Action Do one of the following: • Activate the datastore on which the selected VMware template resides. • In infrastructure orchestration designer, select a different VMware template for provisioning the ESX VM.
3. From the HP Server Automation (SA) “Devices” view, select the VMs. 4. Perform a “deactivate” and a “delete.” New servers do not appear in the Unassigned pool Issue New servers do not appear in the infrastructure orchestration Unassigned pool. Possible cause Resources are added to the Unassigned pool when infrastructure orchestration recognizes that they are available and are licensed and configured correctly.
for component [Microsoft-Windows-Shell-Setup]. The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click OK to restart the computer, and then restart the installation. Possible cause • The environment is not completely configured. • The virtual machine used in the virtual machine management template was not powered off properly. • The vCenter or vSphere is not configured properly for successful customization.
Service creation fails with a virtual machine customization error Issue Create Request fails with a virtual machine customization error. Possible cause • The environment is not completely configured • The virtual machine used in the virtual machine management template was not powered off cleanly If the environment is not completely configured, requests might fail when executing the virtual machine customization step.
{vm_host} may have more than one local disk visible as a target data store. Select a VM host with a single local disk, or update the selected VM host to have just one local disk." Possible cause This error is displayed when the number of concurrent requests for the virtualization type is too high. Action 1. Edit the ..\Program Files\HP\Matrix infrastructure orchestration\conf\ hpio.properties file. 2. Set the values of esx.max.concurrent.requests and/or hyperv.max.concurrent.requests to 5. 3.
Error getting DHCP address during add server request Issue A user cannot allocate DHCP addresses from a particular subnet during an add server request Possible cause This problem occurs when the following conditions are met: • Matrix OE is running in a federated CMS environment • Simultaneous changes are made on subnets (requests allocating IP addresses while the subnet is being edited) • After error messages, a backup/restore process is initiated Action To avoid this issue: • Do not edit a subnet that
Provisioning virtual machine failed with a VM must be powered off for customization error message Issue Provisioning a virtual machine failed with a VM must be powered off for customization error message. Possible cause The Insight Control virtual machine management template that is being used was created when the virtual machine was in a suspended state.
Task for logical server has failed: Service console load average on the source server is greater than the threshold value Failure message Task for logical server has failed. Failure: Service console load average on the source server is greater than the threshold value. Retry the operation later. Possible cause The load average on the source or target VM Host may be too high. Verify this issue by examining the Insight Control virtual machine management log file at: ..
If using Ignite-UX, the client has not been set up with permission to run the erase disk job in Systems Insight Manager. Action If using Insight Control server deployment, follow Step 9 in the Creating server deployment job folders procedure.
A delete request failed Issue A delete request has failed. The environment must be manually cleaned. Possible cause — Action For virtual logical servers, infrastructure orchestration creates a folder under the virtual machine Host with the same name as the infrastructure service provided by the user. This folder contains all the folders and files corresponding to the virtual logical servers. Delete this folder and all its contents.
and the infrastructure service was provisioned by infrastructure orchestration, check if its status is not standby. Possible cause The logical server had been deactivated. Action • If it is not a “clean-me” logical server then return to infrastructure orchestration and issue an Activate servers request for the logical server. • If it is a “clean-me” logical server then perform a manual clean-up process for the logical server. See “Manual clean-up process (physical)” (page 195).
3. 4. 5. 6. 7. 8. Click Groups. Right-click HPIO_Administrators, and select Add to Group. Click Add.... In the Enter the object names to select (examples) field, enter . Click OK. Click OK.
Users added to the HPIO_Administrators group cannot log in to infrastructure orchestration console Issue Users added to the HPIO_Administrators group cannot log in to infrastructure orchestration console. Possible cause The HPIO_Administrators group is not associated with the infrastructure orchestration toolbox in Systems Insight Manager.
Users are not able to login to infrastructure orchestration after installation or after assigning the user to a different infrastructure orchestration group Issue Users are not able to login to infrastructure orchestration after installation or after assigning the user to a different infrastructure orchestration group. Possible cause The CMS requires a reboot.
Check the hpio-controller.log file for warning messages of the form: ”Unable to get all VM Host data in the allotted time. The data from some hosts will not be returned.” and ”Unable to get VM Host data in the allotted time for host : .” Action Fix the environmental issues or increase the following timeout property settings.
Step in the Request Details fails Issue A step in the Request Details is shown as having failed. Possible cause When executing a request, infrastructure orchestration might report the failure of one or more steps on the Request Details page. After such an error occurs, infrastructure orchestration attempts to recover by retrying the tasks or re-allocating the resources. During a recovery allocation process, infrastructure orchestration uses the server pools selected in the initial request.
Self Service Portal operations Linux server does not list a recently added data disk Issue My Linux server does not list a recently added data disk. Possible cause The server was not rebooted. Action When adding a new data disk to an existing service, if the servers are physical Linux servers or the data disks are added manually (for example, Multi-initiator NPIV is not used), reboot the Linux server to make the disks available.
Create Request fails for published template Issue Create Request fails for my Published template. Possible cause Resources are unavailable. When a template is published, it is validated by infrastructure orchestration designer. However, if after publishing, resources are removed from the system (software, networks) the template might become invalid due to lack of resources.
Template access restrictions for users and architects Issue Template access restrictions for users and architects. Possible cause Template viewing and use for non-administrators (architects and users) may have been configured by an Administrator so that Architects and Users only view and use templates that each have assigned access to.
IO server. The Details tab may provide more information about which part of the template XML is invalid.” Cause For IO templates, backward compatibility is not supported. Forward compatibility is supported. Action Create and publish templates at the earliest IO version to which they are targeted.
Access error on infrastructure orchestration web pages from email notification using private network Issue Access error on infrastructure orchestration web pages from email notification using private network. Possible cause In some cases, the administrator cannot access the approve/reject web page (and other Matrix infrastructure orchestration pages) from the notification email that asks the administrator to continue or reject a user request.
7. Click Save to save the path, then check in and save the flow with the updated information. Matrix infrastructure orchestration Windows service Matrix infrastructure orchestration may time out while waiting for the server to be recognized Issue Matrix infrastructure orchestration may time out while waiting for the server to be recognized. Possible cause Long server post times, particularly when using the BL620c G7 or the BL680c G7. Action To avoid this issue on any server: 1. Edit ..
Deactivate physical server does not complete successfully after CMS crash recovery Issue Deactivate physical server does not complete successfully when resumed after CMS is recovered from a crash. Manual steps recommended by IO are inadequate to recover the logical server and re-issue the request successfully. Possible cause VCEM and VCM are out of sync due to a CMS crash that occurred while unassigning a server profile.
Log files How can I find out more details about an error? Issue How can I find out more details about an error? Possible cause — Action See the hpio-controller.log file located at ..\Program Files\HP\Matrix infrastructure orchestration\logs on the CMS. vCenter server is not configured in Systems Insight Manager or becomes unavailable Issue vCenter server is not configured in Systems Insight Manager or becomes unavailable.
Troubleshooting communication failures Issue Troubleshooting communication failures. Possible cause — Action • Verify that the vCenter credentials are correct on Systems Insight Manager.
The server profile and boot disk are preserved, enabling an administrator to determine the cause of the failure and perform any required maintenance before returning the server blade to a user pool. Manual clean-up of the failed server blade depends on the deployment server used to provision it. For Insight Control server deployment: 1. Power on the server blade. Cycle the power if the server blade is stuck. 2. 3. 4.
3. 4. Verify that the VC profile associated with the failed server blade exists in Virtual Connect Enterprise Manager. If the profile exists, unassign and delete the VC profile associated with the failed server blade from Virtual Connect Enterprise Manager. Move the server blade out of the infrastructure orchestration Maintenance pool. a. In the infrastructure orchestration console (accessed from Systems Insight Manager), select the original server blade pool and click Modify. b.
In this example, the storage pool entry name is “e5_win_BD_05”. The figure highlights the SAN which is being connected to, as well as the target, and the initiator WWNs. 2. Go to the storage fabric and create the zone. In this example, a switch which exists in “san3” above is connected. The zone should have the same name as the storage pool entry, as is shown by the highlighted entry.
3. Go to the disk array management interface (in this case CommandView managing an EVA) and create a host entry and present the LUN. In the first figure, the host entry that is created on the EVA uses the same name as the storage pool entry. The host entry is assigned the initiator WWN identified in the storage pool entry: 4.
In this example, only a single vdisk is required by the storage pool entry. The names are kept the same across the storage pool entry, the FC zone, the host entry on the array, and the vdisk. This approach supports a strong correlation of the resources in the different tools. It is also possible to define a storage pool entry with multiple LUNs. In this case, the naming of the vdisk could follow a pattern of a common prefix (for example, e10_vc_w2k_1, 2, 3, 4, and so on).
1. To correct this issue, press the CTRL+Q keys to launch the HBA Fast!UTIL utility. The following screen appears: 2. On this screen, press the Enter key. Pressing Enter corrects NVRAM and generates a new checksum. During this process and server reboot, Virtual Connect continues to supply the HBA configuration parameters preventing data loss. After pressing Enter the following screen appears, indicating that the NVRAM has been corrected.
3. Press the ESC key to exit the utility. The following screen appears: 4. Press the Enter key to reboot the system. When the system reboots, all the HBA configuration parameters are resupplied by Virtual Connect and the server returns to normal operation. Increasing VMware Service console memory and CPU shares The memory and CPU shares that are allocated to the VMware Service console may be increased to obtain better performance on the VM Host.
g. Click OK. The changes do not take effect until the ESX host is rebooted. For more information on rebooting an ESX host, see the following VMware KB article: http:// kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC& externalId=1003501. 2. Increase the number of CPU shares assigned to the ESX 3.X or ESX 4.X Service console: a. Log in to vCenter from the Virtual Infrastructure Client with a user that has administrative rights. b.
j. Click OK to apply the values. NOTE: Increasing the reservation value for console may affect the available CPU cycles for the virtual machines on the host.
8 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • See the Contact HP Worldwide website for contact options: htt
Warranty information HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management software products. HP authorized resellers For the name of the nearest HP authorized reseller, see the following sources: • In the United States, see the HP U.S. service locator web site: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide web site: http://welcome.hp.com/country/us/en/wwcontact.
Related information Documentation and support The latest versions of manuals and white papers for HP Matrix Operating Environment and related products can be downloaded from the HP Web. Documents for Matrix Operating Environment software can be found at http://www.hp.com/go/matrixoe.
Glossary administrator A user who manages users, resource pools, and self service requests through Matrix OE infrastructure orchestration console. allocation A request is assigned server, storage, and network resources based on the criteria defined in the template, resource pools assigned to the user, and the current reservations or allocations of resources completed by HP Matrix Operating Environment infrastructure orchestration.
HP Virtual Connect Enterprise Manager HP's enclosure-spanning hardware virtualization management software product. IE See Internet Explorer. infrastructure orchestration console A web application (Systems Insight Manager plug-in) that enables you to deploy, manage, and monitor the overall behavior of infrastructure orchestration and its users, templates, services, and resources.
request A self service user action requiring administrative approval. Requests are generated while performing other tasks such as a service instantiation or deletion. Requests are generated when a user wants to: • Create a service • Delete a service • Deactivate a server • Activate a server • Update a service to add servers • Update a service to add storage • Change the lease period resource pool A group of physical and virtual resources managed by Matrix Operating Environment.
including approvals, manual operating system deployment, manual storage provisioning, and sending notifications. You can also associate workflows with infrastructure orchestration templates. These service action workflows are executed before and after the associated request. They are intended to perform actions specific to the template and services created from it. Sample workflows are available in the folder Library/Hewlett-Packard/infrastructure orchestration/Service Actions/Samples.
A Customizable allocation process Overview Matrix infrastructure orchestration performs automated resource allocation using a built-in allocation mechanism, as described above. This built in allocator is the default allocation mechanism. In addition, a customizable allocation mechanism can be used instead of the built in allocator for some parts of the resource customizable allocation process.
The order in which the elements are declared is not important, except for the package name. If declared, the package name must be the first element in the rule file. Example: Rule to verify server memory criteria package com.hp.hpio.controller.policy; import java.util.List; import java.lang.Integer; import com.hp._2007.ess.sw.model.infrastructureutilityschema.LogicalServer; import com.hp._2007.ess.sw.model.infrastructureutilityschema.ComputeServer; import com.hp.hpio.controller.wrapper.
You can modify or delete existing rules, or add new custom rules. Rules are written in Java and the Drools syntax. Available hooks for customizing: • SubnetPolicyCheck.applyFitting • AttributeBasedSubnetPolicyCheck.applyFitting • SpecifiedSubnetPolicyCheck.applyFitting • AutomaticIpAddressPolicyCheck.applyFitting • StaticIpAddressPolicyCheck.applyFitting • DhcpIpAddressPolicyCheck.applyFitting • PhysicalServerPolicyCheck.applyFitting • PhysicalBootDiskPolicyCheck.
// in case of failure. eval(customRule1($logicalSubnet, $subnet, $pVO)); /* --------------- CUSTOM LOGIC ------------------ */ then /* // // // // // --------------- CUSTOM LOGIC ------------------ */ Since this is a custom rule/criteria construct HPIO message using ALLOCATION_CRITERIA_CUSTOM bundle key and providing allocation failure message (string) to be displayed. In case this rule fails. NOTE same information should be used while calling doesNotMatch in the custom function below. $pVO.
B HP Operations Orchestration communication security This appendix describes the security of the interaction between Matrix infrastructure orchestration and HP Operations Orchestration. Matrix infrastructure orchestration integrates with Operations Orchestration. Operations Orchestration provides customizable workflows that can be called at various points during the life of an infrastructure service.
• User Token – The security token to be used in calls back to infrastructure orchestration. • Date – Date and time at which the flow was triggered by infrastructure orchestration. NOTE: These parameters are required in the workflow definition even if the parameters are not used within the workflow.
• User Pool Notification • Service Lease Notification • Service Recovery • Service Fail Action Service actions Service actions are the stages of infrastructure service that may invoke an Operations Orchestration workflow.
Index A accessing infrastructure orchestration console, 82 infrastructure orchestration designer, 79 infrastructure orchestration organization administrator portal, 84 infrastructure orchestration self service portal, 87 Operations Orchestration, 26 Active Directory integration with Insight Management, 16 add disks, 93 add servers, 91 adding user accounts to groups, 17 administrator, 12 allocation, 100 allocation algorithm server, 97 storage, 98 allocation overview, 123 allocation rules, 212 Amazon EC2 clou
components, 81 disaster recovery protection for IO services, 44 disk array presentations configuring, 197 disk deletion, 101 disk scrubbing, 101 DR (disaster recovery protection) enabled services, 44 E edit virtual servers, 96 editing ESA flows, 191 ESA configuration, 72 ESA flows, referencing correct OO install path, 191 ESX cloud resources, 67 ESX resource pools, 67 ESXi cluster provisioning configuring, 56 resource pools, 67 ESXi support Insight Control server deployment, 30 F FC zones configuring, 197
Calendar tab, 89 customizing, 86 Home page, 88 My History tab, 89 My Pools tab, 88 My Requests tab, 88 My Services tab, 88 Templates tab, 88 inoperable storage pool entry, 164, 165 Insight Control, 10 Insight Control server deployment job folders, 31 Insight Control virtual machine management, 10 troubleshooting, 183 installation, 15 IO template creating cloud service provider, 114 ProLiant server, 101 ProLiant VM, 108 VM Host, 108 ioexec command line interface reference , 14 IP address of VM Host, 98 J jo
infrastructure orchestration self service portal interface, 88 integration, 11 lifecycle operations, 90 multi-tenancy, 151 operation, 11 product, 10 provisioning, 10 user, 12 users, 12 P physical disks number of supported, 146 physical provisioning, 56 physical servers provisioning using local disk, 97 physical shared disks number of supported, 146 physical storage provisioning, 146 physical to virtual logical servers support in Matrix infrastructure orchestration, 123 prerequisites, 79, 87 private disks (
trunk networking, 60 U uninstall, 15 user accounts to groups adding, 17 user groups, create on secondary CMS, 22 users configuration, 16 removing permissions from, 18 verifying, 72 users and groups in Matrix infrastructure orchestration, 16 V vDS network switch support in infrastructure orchestration, 38 verifying the CMS configuration, 159 Virtual Connect troubleshooting, 192 Virtual Connect Domain Groups resources in resource pools, 69 Virtual Connect Enterprise Manager, 10 virtual domain, 56 virtual ma
