HP Matrix Operating Environment 7.3 and 7.3 Update 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, 2014 Hewlett-Packard Development Company, L.P. 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.............................................................................................11 Automated infrastructure design provisioning and management....................................................12 Matrix infrastructure orchestration and the Matrix Operating Environment solution...........................12 Matrix infrastructure orchestration users and groups.....................................................................
Configuring an environment for virtual provisioning.....................................................................44 Provisioning a Linux VM on Hyper-V.....................................................................................44 Skipping automated OS customization.............................................................................45 Setting up virtual machine networks......................................................................................45 Using static IPv6 addresses.
Matrix OE infrastructure orchestration console............................................................................96 Accessing the console........................................................................................................97 Console interface overview.................................................................................................97 Console access to deployed servers.....................................................................................
Deploying an operating system to multi-path storage.................................................................153 Matrix Operating Environment support of IO accelerators..........................................................153 Assigning and retrieving cost and billing information (chargeback)..............................................153 Specifying fixed costs for templates and services .................................................................154 Specifying per-unit costs for resources.
Auto-provisioning storage fails with “No matching storage found” error..............................194 Logical servers are inoperable if they are associated with guests that use SLVM file-based storage......................................................................................................................195 Could not find server serial number or task for logical server failed....................................
IO provisioning and linked clone provisioning fails when using a Windows 2012 OS template....................................................................................................................209 Failure to add a service to a Matrix recovery management Recovery Group........................210 Matrix infrastructure orchestration times out while concurrently provisioning Integrity VMs......210 Service provisioning, logical server VM creation or reactivation fails.................................
VMs fail to reconfigure after editing memory or processor settings on a running VM.................221 Self Service Portal operations.................................................................................................221 Linux server does not list a recently added data disk.............................................................221 Entering a host name in the network WINS setting causes a Windows customization to fail.......
The browser requires acceptance of a self-signed certificate to access Matrix infrastructure orchestration...................................................................................................................231 Wrong behavior of Operations Orchestration content after conversion to version 10.01.............232 Corrective procedures...........................................................................................................232 Manually updating the chargeback database.............
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.
Automated infrastructure design provisioning and management Matrix infrastructure orchestration supports four main activities to automate the deployment of infrastructure services: Design An architect uses the graphical designer to create simple and complex infrastructure templates that, when tested, can be published for users to create infrastructure services.
• The designer enables an architect to plan and design multi-server, multi-tier infrastructures using a drag-and-drop interface. • The console enables a service provider administrator to deploy, manage, and monitor the overall behavior of infrastructure orchestration and its users, templates, services, and resources.
NOTE: It is possible to view and assign only explicitly named users and groups that are included in the HPIO_* Windows groups (described in “Matrix infrastructure orchestration roles” (page 18)). Users or subgroups within these named groups are not visible, nor can they be directly assigned to resources. • Architect Uses infrastructure orchestration designer (a graphical designer) to design and publish infrastructure service templates which capture the requirements to provision the infrastructure service.
resources that reflects the original template design. Running infrastructure services can be modified in many ways, including by adding servers and data disks. NOTE: HP Insight Control server provisioning is the replacement for HP Insight Control server deployment. Insight Control server deployment is still available for installation and upgrade. Insight Control server provisioning is the recommended HP ProLiant deployment solution.
allows the use of Operations Orchestration Central to launch and schedule the launch of Operations Orchestration workflows from outside of Matrix OE/Insight Control. • The version of Operations Orchestration that is included in Matrix OE supports remote use of an external Operations Orchestration server running the full version of Operations Orchestration.
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.
If you purchase Matrix OE as a standalone system, you must obtain a Matrix OE Public Cloud Managed Instance license to provision a public cloud instance. This license allows you to manage one public cloud instance hosted at an HP-supported public cloud service provider for a term of one year from the date of registration. Multiple licenses can be used together under a concurrent use model. (For example, if you purchase 10 licenses, you can manage up to 10 public cloud instances at any one time.
Can log in to infrastructure orchestration designer and the infrastructure orchestration self service portal. Can log in to the infrastructure orchestration organization administrator portal for any organization, and the infrastructure orchestration self service portal for any organization. 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.
Matrix infrastructure orchestration access Group membership requirement1 Console HPIO_Administrators HPIO_Architects Designer HPIO_Administrators 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.
7.3 and later releases, but can be re-enabled. For more information, see “Re-enabling the telnet link” (page 22). You can define these custom console links in the hpio.properties file using two properties: one to specify the link and one to specify the link display name. When a user clicks a console link, the browser uses the registered URL protocol handler to launch the appropriate console tool to access the server. The following example shows the default values used in the hpio.
location at C:\Program Files\HP\Matrix infrastructure orchestration\conf\ hpio.properties: • software.access.restricted = true If this property is set to true, the user must have access to any software specified as a customized attribute when the service is created. If this property is set to false, software selection is not restricted during customization. NOTE: This property affects only software specified as a customized attribute. No authorization is needed for software specified in the template.
• oo.custom.server.action.display.name.2= Enable VPN • oo.custom.server.action.display.name.3= Sync database NOTE: The workflows you specify must be valid, existing OO workflows. If they are not, the menu options will not appear. For more information, see “Custom OO workflow menu items do not appear on Server Actions menu” (page 227). Execute custom server actions by selecting Run custom server action from the Server Actions menu, and then selecting the desired action.
If you performed a new installation of Insight Management, and if federated CMS was not successfully enabled during the installation, configure a federated CMS environment. WARNING! Do not manually enable federated CMS if you are upgrading to Insight Management 7.3 or 7.3.1 from an earlier release. If your environment contains existing infrastructure orchestration services, enabling federated CMS after an upgrade will cause these existing services to fail.
1. Configure secondary CMSs. When complete, this step configures Systems Insight Manager's federated CMS list on the primary CMS, exchanges certificates between the primary and secondary CMSs, configures the primary CMS as trusted on the secondary CMSs, and displays the newly added CMSs in Systems Insight Manager. a. On the primary CMS, in Systems Insight Manager, select Options→Federated CMS Configuration…. b. Click Add CMS…. c. In CMS name, enter the secondary CMS FQDN and then click Next. d.
Support for a rolling upgrade of a CMS federation Matrix OE infrastructure orchestration supports a rolling upgrade of a federated CMS environment. A rolling upgrade temporarily allows a federation containing CMSs running different versions of Matrix OE during the upgrade process. During a rolling upgrade, a CMS running a later version of Matrix OE supports basic operations against a secondary CMS running an earlier version of Matrix OE.
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 (SPM). 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.
2. Log in to the Operations Orchestration administrator account using the following credentials: • User name: admin • Password: the Insight Management service account password specified during the installation If the Insight Management service account password is subsequently changed using the Systems Insight Manager Reconfigure CMS Tools (mxreconfig), the changed Insight Management service account password is not reflected in Operations Orchestration Studio and database.
Orchestration system properties screen displays all the classes of email sent by infrastructure orchestration (Hpio*Sender and Hpio*Recipients). You can configure each to go to a different 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.
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.
Pruning history data for Operations Orchestration Central systems The Operations Orchestration Central database stores information about every flow execution step. This data is used for OO reporting purposes. The database administrator can prune historical data from the database to keep the database at a reasonable size. Regular database pruning will minimize the disruption of disk space depletion or pruning large databases.
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.
IMPORTANT: User-defined properties will be included in the Request XML and passed to Operations Orchestration workflows. Security should be considered before including sensitive information in custom attributes. HP suggests indirectly indicating sensitive information. For example, instead of specifying external system credentials, the credentials could be stored in a script and determined inferred by the FQDN or IP address of the server, such as the following pseudo-code: IF ip=’11.22.33.
Configuring Insight Control server deployment Creating server deployment job folders Create Insight Control server deployment job folders for each operating system that infrastructure orchestration uses to deploy physical servers. NOTE: ESXi deployment is not supported in Matrix infrastructure orchestration using Insight Control server deployment. Modifying the Erase ProLiant Hardware job After installing Insight Control server deployment software, modify the default Erase ProLiant Hardware job.
1. Save a copy of the default Erase job: a. Right-click the Erase ProLiant Hardware job under the HP Deployment Toolbox→ Hardware Configuration folder, and then select Copy from the menu. b. 38 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, press and hold the Ctrl key while selecting tasks 1, 3, 4, and 6 (the tasks become highlighted as shown), then click Delete.
3. 40 Modify the Power Control task to shut down instead of reboot in the default Erase job: 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 11i v3 deployment. (HP-UX 11i v3 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. To set up NFS and export the directories Ignite needs, run: /opt/ignite/lbin/setup_server –n b.
3. 4. 5. 6. In Ping inclusion ranges, system (hosts) names, and/or hosts files, enter the IP address or FQDN. In Credentials..., specify the user name and password, and then confirm the password. Click Save. 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.
Infrastructure orchestration requires the SA OS Build Plan Management permissions to be enabled. If these permissions are not set, IO will not retrieve the SA software list. Enable OS Build Plan permissions in SA: 1. Log in to the SA web client as Admin. 2. In the SA user interface, select By Folder. 3. Right click on the OS Provisioning folder name. 4. Ensure that the Execute Objects Within Folder permission is selected. 5. Select Users & Groups from the Navigation panel. 6.
5. In infrastructure orchestration designer, create or edit a template, and edit the network configuration to select the network from step 2. Default memory setting The default minimum memory setting for templates that use the SA server to deploy software is 512 MB. This value can be changed in the ..\Program Files\HP\Matrix infrastructure orchestration\conf\hpio.properties file. Search for the following lines: # Template Config minimum MB "Memory size:" for SA agent install sa.minimum.
Skipping automated OS customization By default, after infrastructure orchestration deploys an OS to a server, it automatically customizes (personalizes) the OS by setting the host name, IP addresses, netmask, default gateway, and other attributes as appropriate. Automatic OS customization can be skipped by performing the actions noted below.
An administrator can configure a network with IPv4, IPv6, or dual stack (IPv4 and IPv6) and also define static ranges for IPv6 addresses. During the process of IPv6 network configuration, you must define the prefix and the prefix length for IPv6. Optionally, an administrator can also configure the gateway and DNS using IPv6. For more information, see the IPv6 in Insight Management white paper, available at http://www.hp.com/go/insightmanagement/docs.
Setting up a Hyper-V virtual machine network To add a network for use by the virtual machines provisioned through infrastructure orchestration, perform the following steps for each Hyper-V VM Host. For more information, see “Configuring trunk and VLAN networks to enable support for Hyper-V VLAN tagging” (page 78) . 1. Connect to the Hyper-V host using Remote Desktop. 2. Open Hyper-V Manager and choose the server to be connected. 1.
8. Click Run Now. The task results appear. Insight Control virtual machine management template creation might take from 5 minutes up to 30 minutes to complete. The resulting ESX VM template is discovered and displayed in the Software tab in the infrastructure orchestration console, and can be selected as the software when configuring a server group in an IO template in infrastructure orchestration designer.
Hyper-V virtual machine management templates A Hyper-V VM template is not automatically discovered. Hyper-V templates must be imported into HP Insight Control virtual machine management before they appear in IO on the Software tab as VM templates. Matrix infrastructure orchestration uses a Hyper-V virtual machine as the source material for a Hyper-V virtual machine management template without any additional steps.
◦ Multi-server (SCVMM service) templates are excluded. ◦ No explicit indication is given when a template is filtered from view. • When using SCVMM 2012 with a Windows 2012 template, you must add the CDKEY to the template. The CDKEY can be changed during the customization process if you add a new key in the sysprep file. If the SCVMM is registered as a VME, then Insight Management uses SCVMM only to deploy its templates.
The following table shows some examples of how changing this configuration will affect the minimum available memory required in ESX VM hosts. Figure 1 Example of minimum required ESX VM Host free memory Using Sysprep to customize Windows systems Matrix infrastructure orchestration relies on Windows Sysprep to enable customization of Microsoft Windows systems. Customization includes operations such as changing the host name, applying the Windows license key on first boot, and setting the IP address.
encrypted passwords for VMware VM guests must be the same one used by the infrastructure orchestration CMS for the VM guest deployment. • To cause IO to automatically join new virtual machines to a Windows domain, add the clear text domain administrator credentials to the Sysprep.inf file. IO cannot automatically join a new virtual machine to a Windows domain if EncryptedAdminPassword is set to yes. If the credentials are not provided in the Sysprep.
Requirements for High Availability Hyper-V virtual machines with RDM/pass-through disks Matrix supports High Availability (HA) Hyper-V VMs with RDM/pass-through disks, with various constraints based on Hyper-V requirements: • Only HA VMs can have pass-through cluster disks attached, and HA VMs can only have pass-through cluster disks attached (can attach standard pass-through disks to non-HA VMs) • Before provisioning an HA VM using a pass-through cluster disk, it is necessary to turn on maintenance mode
A template containing these server group types can be marked recoverable: • ESX and Hyper-V (with manual and automatic OS deployment, private and shared disks) • ESX and Hyper-V linked servers A template containing these server group types cannot be marked recoverable: • Integrity VM virtual server groups • Cloud server groups • Physical server groups In the infrastructure orchestration console Templates tab, the recoverable template will be marked Enabled in the Recoverable column.
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 28) 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 an external cloud service, such as a supported CloudSystem bursting service provider, another Matrix OE system, HP CloudSystem Foundation (starting with Matrix OE version 7.3.1), or HP Matrix KVM Private Cloud.
NOTE: This tab is enabled only when a software image with a Cloud source type is selected on the Software tab. Images for any external cloud provider, including HP CloudSystem Foundation and KVM Private Cloud, have Cloud listed as their source type. The Required selection (the default) defines a firewall that must be in effect when a service is created. With this option, the server group cannot be deployed to a provider that does not support firewalls. The default cloud firewall blocks all inbound traffic.
Configuring a firewall 1. 2. Select either Required or Optional according to the requirements of your provider. Complete the following steps to set up a firewall rule: a. Select the Protocol (TCP, UDP, ICMP) for which the firewall rule applies. b. Enter a Start Port (0–65535) and End Port (0–65535) to specify the port range to which the rule applies. NOTE: When the Protocol is set to ICMP, the Start Port and End Port fields are replaced by Type and Code fields. c.
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 60)).
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.
For more information about Matrix infrastructure orchestration IPv6 support, see the IPv6 Support in Insight Management white paper available at http://www.hp.com/go/matrixoe/docs. Requesting a load balancer for a service Load balancing servers in one or more server groups is done by selecting the Load Balance tab in each server group configuration screen in infrastructure orchestration designer. Only one load balancer can be specified per server group.
Requesting a load balancer for an organization Load balancers can be “reserved” for use by a particular organization or user by: • Specifying a tag in the ioexec add loadbalancer command, and specifying that tag on the Load Balance tab in infrastructure orchestration designer • Ensuring that all networks visible to a load balancer are assigned to a specific organization.
Following are examples of commands that create and delete a logical load balancer group. When creating a logical load balancer group, a service IP address is usually on a public network. C:\> ioexec creategroup logicalloadbalancer -s example-io-service -l LogicalLoadBalancer:00000000-0000-0000-0000-000000000000 -g http-group -P http -a 10.1.100.
command, except for the IP address (–a option). Note that each addgroupmember command specifies a different IP address. A logical load balancer group should have at least two members. C:\> ioexec addgroupmember logicalloadbalancer -s example-io-service -l LogicalLoadBalancer:00000000-0000-0000-0000-000000000000 -g http-group -a 192.168.200.
The following table describes the information shown in the Load Balance tab in the Details pane. In addition, the model of the load balancer, its version, and the logical ID of the load balancer is shown. (The logical ID is used to configure load balancing using the CLI and SOAP API.) Table 4 Load Balance tab details Load Balance tab Description Group Name Name of the logical load balancer group, which is an abstract concept that describes a service that is to be load balanced.
• Available VC domain groups in HP Virtual Connect Enterprise Manager (VCEM) • Configuring server deployment platforms including Insight Control server provisioning, Insight Control server deployment, Ignite-UX, or HP Server Automation (SA) • Creating SAN-backed storage See “Matrix infrastructure orchestration storage management” (page 163) for more information. • Creating job folders (this is specific to Insight Control server deployment; see “Creating server deployment job folders” (page 37)).
The infrastructure orchestration console initially displays the Home tab with summary information. NOTE: When the Requests tab is first displayed, no requests are displayed until an administrator or user has submitted a request and the request is in-progress or completed. Before using infrastructure orchestration, set up server pools and networks, and verify the Users and Software tabs using the infrastructure orchestration console.
To view and configure physical and virtual networks, the infrastructure orchestration administrator must perform the following steps. NOTE: Matrix infrastructure orchestration also offers API support to create and configure an IO network. For more information, see the HP CloudSystem Matrix/Matrix Operating Environment Integration Interfaces API and CLI Operations Reference Guide available at http://www.hp.com/ go/matrixoe/docs. 1. In the infrastructure orchestration console, select the Networks tab.
NOTE: Networks can be configured with IPv4, IPv6, or dual stack (IPv4 and IPv6). Gateway and DNS can be configured using IPv6. During the process of IPv6 network configuration, prefix and prefix length for IPv6 must be defined, as well as static ranges for IPv6 addresses. Matrix infrastructure orchestration can manage up to one IPv4 and one IPv6 for each network interface in a created service. Matrix infrastructure orchestration supports IPv6 with the following restrictions: 3.
5. When finished setting up a network, click Save. The network is now ready to use with infrastructure orchestration. Trunk and VLAN networks Cloud deployment environments and multi-tenancy environments require segmented networks for customer data separation. VLAN tags in network packets can be used for network segmentation for data separation.
Matrix infrastructure orchestration contains VLAN tagged network support to meet the following objectives: • • Enable IO to be used to deploy a VM Host with a multi-network trunk connected to a server blade network port ◦ Allow an IO administrator to manage and present trunk networks to be used in IO physical provisioning ◦ Allow an architect to create a physical service template that designates a trunk network ◦ Provision physical server blades with a trunk connected to at least one of the availabl
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.
Installation and configuration
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.
NOTE: NCU (HP Network Configuration Utility) is only supported through Hyper-V 2008 R2. For Hyper-V 2012 and later, use the Network Teaming functionality that is available on the Windows Server Manager page. 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 NCU.
1. Determine whether your DIO card is DLA or FLA using the hpvmhwmgmt -l -p dio command. 2. An Administrator must add the DIO cards to the hpvm pool and then label the cards with the name of the network using the following commands: hpvmhwmgmt -p dio -a 0/0/0/4/0/0/0 hpvmhwmgmt -p dio -m 0/0/0/4/0/0/0 —L 3. Any number of ports can be labeled with the same name. Each of these can be used for different virtual servers. NOTE: Do not label two ports for DLA cards.
4. 5. Refresh the Networks tab in the infrastructure orchestration console. A new network appears named the same as the DIO network ports label you used on the VM host. Click Edit Networks to edit the network configuration parameters. NOTE: Because DIO cards do not support PXE booting, the Boot Network and the Deployment Server options are unavailable.
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. The parent of an ESX resource pool is shown in the Servers tab Group column.
The following server pools are automatically generated and cannot be used for infrastructure service creation. • Unassigned pool contains all resources previously discovered by HP Matrix Operating Environment. You can move resources from the Unassigned pool to another pool only after the resource is licensed for use by infrastructure orchestration. Matrix infrastructure orchestration automatically populates the Unassigned pool after installation with the resources identified by Systems Insight Manager.
Creating a pool 1. To create a new pool, click Create Pool on the Servers tab. 2. In New pool name, enter a descriptive name. Select servers from any pool. Remember, during initial infrastructure orchestration configuration, only the Unassigned pool displays resources. IMPORTANT: To be assigned to an organization, a compute resource must be in the service provider Unassigned pool, and cannot be in use.
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 17). 4. After selecting the resources for the pool, click Save.
5. 86 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 frame on the right 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.
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. • Create an organization before an organization administrator can log in to the infrastructure orchestration organization administrator portal.
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.
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. In addition, for deployed servers that use DHCP, the server host name must be resolvable for a console connection to succeed. To change the screen size for all clients that initiate an RDP session through an instance of IO, change the defaults for desktopwidth and desktopheight in the file ..
2. 3. 4. 5. Execute the file by double-clicking it, which enables IE execution of the telnet protocol on the client. Copy the 64-bit version of telnet.exe from %windir%\System32 to %windir%\ SysWOW64. Copy %windir%\system32\en-US\telnet.exe.mui to %windir%\SysWOW64\en-US. Restart IE if it is already running. Enabling telnet for Firefox Telnet console is supported for Firefox clients running on Linux and Windows 2008.
Displays an overview of the infrastructure orchestration organization operations providing statistics, resource usage, and links. • Templates View the templates available to the organization, both published and unpublished, and assign users to a template. Published templates can be used by all organization users. Submit create service requests using a template and the resources assigned to the organization. • Requests View a list of requests and the details of a request submitted by organization users.
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.
Matrix OE infrastructure orchestration self service portal The infrastructure orchestration self service portal enables you to create infrastructure services from published templates. The infrastructure orchestration self service portal can be customized by the service provider administrator with an application title and logo. See “Customizing the organization administrator and self service portals” (page 102) for more information.
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 that 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. IMPORTANT: Deleting a service deprovisions all servers in the service, and deletes the association of servers, disks, and networks with the service. Any users logged in to any server in the service will be logged off. To delete a service 1. 2. 3.
NOTE: A new SSID must be generated for each Windows installation. If the vCenter server or Hyper-V manager has more than one VM being managed with the same SSID, Matrix infrastructure orchestration will list only one VM (usually the first VM listed by VMM). To avoid this behavior, create a VM using a fresh installation of Windows, or ensure that the option to generate a new SSID is selected during the VM import. Linux VMs are not affected by this behavior.
NOTE: Conditions that cause a non-Valid status include: • Server is missing host name. • Server is missing OS type. • The server cannot be imported because its name contains special characters. Only A-Z, a-z, 0-9, - or _ are supported. • Servers with a virtualization type other than ESX or Hyper-V cannot be imported. • Virtual network interface is not defined. • Network is missing ID. • Server IP address was not found. • VM Host is not defined. • VM Host IP address is missing. 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
• Runs custom OO flows for the selected servers • Runs custom OO flows for the service NOTE: Service or server deletion may fail if the network is reassigned after provisioning. For example, an Insight Control server deployment or an Insight Control server provisioning deployment might need to run an Erase Disk job during de-provisioning. For more information, see “Manual clean-up process (physical)” (page 234).
The operation fails when: • Resources are not available to allocate. • SAN disks cannot be created (by HP Storage Provisioning Manager or SAN administrator) • Matrix infrastructure orchestration administrator rejects the request. Activate servers in group operation The Activate servers in group operation restarts the server. To activate servers 1. 2. 3. 4. Open the infrastructure orchestration console, self service portal, or organization administrator portal. Select the Services or My Services tab.
After successfully completing the operation, infrastructure orchestration deallocates the physical server blades, making them available for other uses. Matrix infrastructure orchestration retains the server profiles, SAN disks, virtual disks, and powers off the virtual servers. If the operation fails, infrastructure orchestration powers off the servers. Power on servers To power on servers 1. 2. 3. 4. Open the infrastructure orchestration console, self service portal, or organization administrator portal.
3. 4. Select a service and click Details or View Details. From the Actions or Server Actions list, select Power cycle servers.
except for physical servers, which are freed for other uses. Deactivating a service is the default policy for handling a lease expiration. The administrator can change this policy to: • ignore the lease expiration • de-provision the infrastructure service on lease expiration The lease end policy can be changed in the ..\Program Files\HP\Matrix infrastructure orchestration\conf\hpio.properties file. # # # # # Specifies the lease period end policy.
6. Increase or decrease the number of processors by using the arrows in the Number of Processors field, up to the Maximum (shown in red). The initial and maximum values are specified on the infrastructure orchestration designer Configure Server Group Config tab, in Processors Per Server. 7. Enter a new value in the Memory Size field, up to the Maximum (shown in red).
The lifecycle of a floating IP address is independent from the server to which it is added, allowing it to be moved between servers. A floating IP address should be removed explicitly when it is no longer needed. NOTE: Floating IP address operations can be performed only on logical servers deployed to a cloud provider. Create, move, or remove a floating IP address 1. 2. 3. From the tab in infrastructure orchestration console, select the service you want to modify.
d. Click Create to complete the request, or Cancel to cancel the action. 5. To delete a snapshot, expand the tree, select a snapshot, and click Delete. The Delete snapshot? dialog appears. a. (Optional) Click to select Also delete snapshot children to delete any children of the snapshot. The relationship between snapshots is similar to that of a parent to a child. b. Click Delete to complete the request, or Cancel to cancel the action. 6.
Provisioning physical servers using local disk Matrix infrastructure orchestration includes support for Virtual Connect logical servers using a local disk for boot. (Local disk is also referred to as DAS, or Direct Attached Storage.
To see the IP address of the VM Host where a virtual machine was provisioned, in the infrastructure orchestration console Services tab, select the service and click Service Details. Select the server group, and select the Resource Details tab in the lower pane. The rightmost column is labeled Resource Binding ID, and contains the IP address of the ESX host where the VM was ultimately created.
Excluding disks on a VM Host from the storage pool For VM guests, use shared storage instead of storage that is only local to the host. This enables efficient movement when the VM guest is moved to another VM Host. It is also a best practice to isolate the backing storage for virtual machines on a separate drive from any storage containing hypervisor system files, which results in greater performance. Infrastructure orchestration services can be configured with the devices to be used for provisioning VMs.
Unregister a VM host A Matrix infrastructure orchestration Administrator can use the IO CLI to unregister an unused VM host. The following limitations apply: • The host must not have any guests registered with Matrix infrastructure orchestration or Matrix OE logical server management. • The host must not have an associated Matrix OE logical server. • The host must be in the service provider Unassigned pool. You must specify the -C attribute to unregister a host in a cluster.
• Data disk allocation When LUNs with the required attributes are not available for a Create Service, Add servers to group, or Add data disk to group operation, disk allocation is blocked and the infrastructure orchestration administrator is notified. The infrastructure orchestration administrator: ◦ Works with a SAN administrator to create the storage. ◦ Defines the storage in Matrix OE logical server management. ◦ Continues the operation.
Creating infrastructure orchestration templates Creating a template with a physical ProLiant or Integrity server Perform the following steps to create a service template for deploying a physical server on a ProLiant or Integrity system. 1. Launch infrastructure orchestration designer at https://:51443/hpio/designer/ and click New to begin. 2. 124 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. 126 Set the Networks attributes for the server group.
Specify a Hostname. There are three parts to the physical server's host name. 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 host name.
NOTE: For Integrity deployment, always select Automatic or Static. IO does not support DHCP for HP-UX OS deployment. You can specify a network connection as requiring redundancy. When selected, IO automatically configures NICs to the same network. The VC Profile is constructed such that the NICs are distributed across alternate VC-Ethernet modules. IO only assigns auto/static IP addresses to the primary NIC of the redundant pair. The failover NIC will not have an IP address allocated or assigned.
8. Configure the Physical Storage component. The Storage Type is FC-SAN. Select Select a storage template or Specify desired attributes. See “Physical storage provisioning” (page 175) for a description of these options. Select the Disk is bootable check box. Leave the RAID Level set to Any. The setting for Redundant SAN paths to disk depends on the need for redundancy and any defined logical server storage pool entries.
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 145) for more information. (Note that the Recoverable check box 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.
Creating a template with a ProLiant or Integrity virtual machine Creating a service template for deploying a VM is similar to the steps for a physical server. 1. Launch infrastructure orchestration designer at https://:51443/hpio/designer/ and click New to begin. 2. 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. 3. Connect the Virtual Server Group to the Network.
NOTE: Matrix infrastructure orchestration supports online memory addition and deletion for Integrity vPars. When you create a vPars virtual server, you can specify Base Memory and Float Memory options to appear on this screen. This feature is supported for HP Integrity Server Blade logical servers only. For more information, about creating vPars virtual servers, see “HP-UX vPars support” (page 139).
NOTE: Non-High Availability (HA) VMs with non-cluster Disk Pass-Through are supported without limitations. High Availability VMs are only supported with pass-through cluster disks if Maintenance Mode is turned on for those disks (using Microsoft Failover Cluster Manager) before any provisioning or deactivate/reactivate operations. Maintenance Mode can be turned off after successful provisioning, OS installation, and activation (or reactivation). 5. Fill in the Networks tab for the Virtual Server Group.
Automatic Indicates that IO automatically selects the static IP addresses to be allocated from the static IP address range set for the network. NOTE: For HP Integrity VM deployment, use Automatic. NOTE: Matrix infrastructure orchestration does not support DHCP for HP-UX OS deployment. None/External Indicates that infrastructure orchestration will allow provisioning of a server with no IP address so that IP address preferences can be chosen later.
NOTE: Matrix infrastructure orchestration now supports HP-UX Virtual Partitions (vPars) as a dedicated guest for virtual logical servers of Integrity VM virtualization. For more information, see “HP-UX vPars support” (page 139). 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. For more information about configuring load balancers, see “Configuring a load balancer” (page 59).
10. Set the attributes for the Network. You should only need to select an appropriate network; there are no other attributes to specify. You can optionally include the cost values shown.
11. Click Customizable to allow certain attributes of the template to be changed, and click Recoverable to mark the template for disaster recovery. See “Customizing template attributes when a service is created” (page 145) and “Configuring a disaster recovery (DR) service” (page 53) for more information. 12. After you have completed these steps, note that Validation Status is green. If it is not green, click Show Issues and resolve those items. 13. Select the Published box and then click Save.
HP-UX vPars support Matrix infrastructure orchestration now supports HP-UX Virtual Partitions (vPars) as a dedicated guest for virtual logical servers of Integrity VM virtualization. HP-UX vPars is a soft partitioning technology within HP-UX that adds finer core granularity to nPartitions, as well as the flexibility of dynamic resource migration. Each virtual partition is assigned a subset of hardware, runs a separate instance of HP-UX, and hosts its own set of applications.
2. On the Software tab, select GUEST or DEDICATED from the Guest Type menu. The Guest Type menu appears in the following configurations: • When Automatic software deployment is selected and the OS Type is set to HP-UX. • When Manual OS provisioning is selected, the OS Type is set to HP-UX, and the Virtualization Type is set to Integrity VM.
The server group icon then displays the corresponding value in the template. Setting user-defined properties Click Properties to define your own properties to be used by workflows and scripts. Properties can be set for templates, servers, networks, and storage in their respective Configure dialog boxes. The Properties configuration consists of the following fields and controls: Table 6 Properties tab fields and controls Field or control Description Name Specify a name for the property.
The OO workflow is invoked whenever a host name needs to be assigned or updated, and is triggered by the following events: • Create service/add server: Host names are allocated to newly created servers. • Delete service/remove server: Host names from removed servers are released. • Out-of-band host name update: If VM guest tools are installed in the target operating system, host name changes are detected and the OO workflow is notified. Otherwise, the workflow is not aware of the host name update.
Creating a service request The infrastructure orchestration self service portal enables you to create infrastructure services from published templates. 1. From the CMS desktop, double-click the Self Service Portal icon, or open a browser to https://:51443/hpio/portal/. Or, from Systems Insight Manager, open the infrastructure orchestration console by selecting Tools→Infrastructure orchestration. 2. 3. 4.
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 host name. The first part is defined in this service template.
12. Select the My Requests tab (or the Requests tab in the infrastructure orchestration console) to view status of the request. After initial validation has completed and resources have been reserved, the request is paused in the queue for approval.
NOTE: Trunk networks (mapped or tunnel) cannot be customized. A trunk network configured in a service template cannot be replaced with another network, nor can a trunk network be used to replace another network. 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. Customizations affect only the service being created. The template is not changed.
NOTE: Customizing the network assignment type of Integrity VMs to DHCP is not supported. 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.
For more information, see the HP CloudSystem Matrix/Matrix Operating Environment Integration Interfaces API and CLI Operations Reference Guide available at http://www.hp.com/go/matrixoe/ docs. NOTE: Customization can be disabled, even if the Customizable option is selected in the template. To disable some customization options, edit settings in the hpio.properties file located in the default location at C:\Program Files\HP\Matrix infrastructure orchestration\ conf\hpio.properties.
Approving and automating deployment 1. To approve the service request, connect to Systems Insight Manager and log in using an account that is a member of the HPIO_Administrators group. Select Tools→Infrastructure orchestration, then select the Requests tab to view the pending request queue. 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.
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 150)).
3. Use the HP 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 following website: http://www.hp.com/go/matrixoe/docs NOTE: Cross-technology logical servers are not supported by Matrix infrastructure orchestration.
A Virtual Connect Domain Group defines the boundaries for a set of resources, specifically servers, networks, and SAN volumes. Any resource within a VC Domain Group is visible to or connected to any other resource within the same VC Domain Group. However, connectivity between VC Domain Groups is uncertain.
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.
• • • Cost for network customization – Consists of the following customization types: ◦ IP Assignment Type – displays the change in cost per IP address for a given assignment type. ◦ Network – displays the change in cost per IP address for each network in the template. Cost for OS customization – Consists of the following customization types: ◦ OS Type – displays the change in cost per server of the chosen OS. ◦ Virtualization Type – displays the change in cost per server for virtualization.
To specify cost deltas for making template customizations, click the Customizations tab. Values entered are the cost deltas applied for customization. A value of zero means no adjustment to cost, while a positive value increases the cost and a negative value decreases the cost.
For example, the template might specify a Windows 2008 OS image, but the user can customize to Windows 2012 (with a cost increase of 1.00) or customize to Linux (with a cost decrease of 2.00). Similarly, the template might specify a cost of 1 per IP address for DHCP, but if the IP Assignment type is changed to Static the cost is increased by 1 (to 2 per IP address); or if the network is changed to 26_net, there is a reduction of 0.25.
In infrastructure orchestration designer, right click on a network or trunk to display the Config tab, where you can enter the cost per IP address. NOTE: The cost per IP address will be modified appropriately if cost deltas have been specified for network customization and the user customizes at the time of service creation. For more information, see “Assigning and retrieving cost and billing information (chargeback)” (page 153).
NOTE: Matrix infrastructure orchestration allows an administrator to change the cost of deployed services using the modifyService CLI. This allows and administrator to change any value set by an architect after the service is provisioned.
Specifying a billing code for services When creating a service, you can add a billing code, which allows IO chargeback or other data mining solutions using the API or database to extract information about which organization to bill. Enter a billing code by clicking the Options button on the Create Service from Template dialog, and entering a value in the Billing Code text box. Deactivated logical servers are counted as logical servers when cost information is calculated.
On the Convert Template to use Global Cost Units dialog, enter a Conversion Factor, which is a positive decimal or integer value. For example, if the cost information in a template is expressed in euros (€) and the global cost unit set in the hpio.properties file is dollars ($), convert the template from euros to dollars by entering a Conversion Factor equal to the current exchange rate, such as 1.3358.
cost frequency value must be specified for the existing services. This can be done by running the modify service command from the Matrix OE CLI. For more information about this command, enter ioexec modify service –help on the command line on a Matrix OE 7.3 or 7.3.1 CMS. After an upgrade to 7.3 or 7.3.1, server costs are updated to reflect the server cost assignment. Existing total cost is assigned to base cost, and CPU unit cost and memory unit cost are assigned to 0.
4. 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. Run Microsoft Excel, and open output.xml. c. Edit the output.xml file with information from a downloaded xsl file to create a report. Sample xsl files are available for download from HP Developer Resource Center for CloudSystem. Following is an example of the output using the downloaded xsl file to display getServiceUsageDetail.
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.
NOTE: Storage pool entries can be created manually, or infrastructure orchestration can create storage pool entries automatically. In both cases, the storage pool entries can be fulfilled through SPM using pre-provisioned volumes or on-demand provisioning (based on customer need reflected in the storage templates defined in SPM).
Pre-provisioned storage provisioning cannot be used if: ◦ SPM is not configured ◦ the environment contains a combination of private and shared disks without NPIV ◦ boot disks and other private disks are contained in separate storage pool entries Storage requests can be created manually by the user or automatically by Matrix infrastructure orchestration and submitted to SPM for storage service fulfillment.
In the pre-provisioned use case, SAN volumes are pre-created within SPM but are not yet masked to one or more initiator WWNs. Zoning must be pre-configured. The SAN volumes are made available within the SPM storage catalog and are visible in Matrix OE visualization’s storage pool as storage pool entries (either in advance for manually created storage pool entries, or at service provisioning when infrastructure orchestration automatically generated the storage pool entries).
Manually creating SAN-backed storage in Matrix OE visualization To manually create SAN-backed storage pool entries in Matrix OE visualization, perform the following steps. 1. Verify that the target enclosures have been successfully discovered by Systems Insight Manager. 2. Create a Virtual Connect domain group that includes the target enclosures in VCEM. 3. Refresh Matrix OE, synchronizing it with VCEM. To refresh Matrix OE: a. Using Systems Insight Manager, select Tools→HP Matrix OE visualization.
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 the following website: http://www.hp.com/go/matrixoe/docs 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.
Specify the port and volume information on the screen, and save the storage pool entry. It can then be used for future service provisioning requests. If the SPM catalog entry authorizes it, infrastructure orchestration is able to dynamically adjust the LUN masking and, if necessary, the host mode for the storage pool entry.
4. Add storage tags and an optional description. Storage tags are displayed in the Tag List for all Storage Pool Entries. Click Modify next to the storage pool entry, then click to select the check box next to a tag name to associate the tag with the storage pool entry.
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.
Select one or more arrays for import. Once the array has been imported, view and select the SAN volumes that are visible on the array and select the volume(s) to be included in the catalog. For each array, select the settings. IMPORTANT: Select the Matrix Security Group for the security group. From the left navigation bar, select Volumes, then select volumes to import and press Import Volumes.
After the SPM catalog has been populated, you can do the following: • Continue to use pre-provisioned storage (no additional steps are needed) • Allow infrastructure orchestration to automatically generate storage pool entries (no additional steps are needed) • Enable on-demand storage provisioning (see “Enabling on-demand storage provisioning in SPM” (page 173)) • Predefine storage pool entries using the Matrix OE visualization’s storage pool entry screens and build one or more storage pool entries
2. 3. Select Templates under Storage Services. Search for and select HP Matrix Default Storage Template in the list of templates, or click Create Template to create a new template. 4. 5. 6. Click Edit Template. In the Edit Template dialog, select the Read-Only Requirements tab. Select the Resource Existence requirement in the Template read-only requirements. 7. Click Edit.
8. 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. The volumes that are also storage pool entries are also visible on the Matrix OE visualization – Modify Logical Server Storage Pools page.
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.
The storage requirements that you can manually define are as follows: • Name of the disk. • Individual Disk Size is the size for the disk in gigabytes (GB). For physical (SAN) disks, this attribute is used to find a SAN disk that is at least as large as the value specified. (For physical storage, MB x 1000 = GB.)For virtual SAN disks, this value sets the actual size of the disk. • Cost per GB is the estimated cost per gigabyte in numeric form. • RAID Level is a specific RAID level, or Any.
• Disk is shared across servers specifies that the disk is a data disk (non-boot disk) and it is shared between all of the servers in the group. • Provisioning Type is a drop down list with the following options: ◦ Unspecified will inherit the default setting of the hypervisor. ◦ Thick allocates the full size of the disk. ◦ Thin allocates only the amount of storage space actually used. As more data is store, the disk automatically expands up the full size.
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.
◦ – Is responsible for creating organizations in the infrastructure orchestration console and assigning resources to them – Can create pools and assign service provider users to them Service provider architect Can access the infrastructure orchestration designer to create, modify, and publish templates for the and organizations ◦ Service provider user Can log into the infrastructure orchestration self service portal and initiate requests for provisioning using published templates • Organization The
A service provider administrator assigns service provider users to templates. However, an organization administrator cannot assign organization users to templates. An organization user has access to all of the templates assigned to that organization. A Windows user may be both a service provider user and an organization user. In this case, if the Windows user logs into the self service portal, the user will have access to the templates to which he/she is assigned.
Only the service provider administrator can log in to the infrastructure orchestration CMS to access other technologies such as logical server management and Systems Insight Manager, and detailed infrastructure orchestration logs.
1. From the infrastructure orchestration console Organization tab, click Create. The Create new Organization page appears. 2. 3. 4. 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.
4. Delete the organization from the infrastructure orchestration console Organization tab. 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.
See “Assigning networks to organizations for VLAN separation” (page 187) for more information. • A set of infrastructure orchestration templates. An IO template can be assigned to multiple organizations and multiple users within an organization. To make a template accessible to a specific user within an organization, assign the template to both the organization and the user. Template access restrictions do not apply at the individual user level unless template.access.restricted=true is set in the hpio.
Assigning networks to organizations for VLAN separation Assigning different Matrix infrastructure orchestration networks to each organization provides VLAN separation for provisioning of either physical or virtual hosts. When an IO template is defined, networks can be specified using attributes instead of by selecting a specific networks. One of the attributes is the network name.
7 Troubleshooting Verifying the CMS configuration Matrix infrastructure orchestration uses 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.
Manually enabling federated CMS A federated CMS environment contains one primary CMS running infrastructure orchestration, and one or more secondary CMSs running Matrix OE. Issue Matrix infrastructure orchestration federated CMS is enabled by default during new installations. At the end of a new installation, the Insight Management installer displays: Warning — HP Matrix infrastructure orchestration was successfully installed but the federated CMS feature was not enabled.
Service creation Physical service creation Unable to allocate servers and networks in the same Virtual Connect Domain Group Failure message Unable to allocate servers and networks in the same Virtual Connect Domain Group. Either more available servers are required, or could not match existing servers against memory size, disk space and processor count requirements. Possible cause Reservation failed because: • There were insufficient suitable servers in the server pools referenced in the Create Request.
1. Use Remote desktop and log into the server deployment server. 2. Verify that the server deployment console for the enclosure bay for the logical server XYZ. The message should state RDeploy: The disk was not found. 3. From the request messages, identify the LUN that has been allocated to the logical server. 4. If the message indicates a possible server WWN issue with the LUN, see “Configuring storage pool entries, FC zones, and disk array presentations” (page 236). 5.
not have the specified system UUID recorded. Deployment Service Connector cannot confirm the system UUID provided by the caller. Possible cause The deployment server cannot bootstrap the server. This issue can occur if the LUN attached to the server already has an OS deployed to it so that the server is booting from the presented LUN rather than booting into the designated deployment server. Action 1. Locate the Provisioning logical server message that identifies the server blade in use. 2.
Logical servers are inoperable if they are associated with guests that use SLVM file-based storage Issue After starting an HP Integrity VM Host, logical servers are inoperable if they are associated with guests that use SLVM file-based storage. Possible cause HP Integrity guests can use SLVM storage, referred to as file-based storage in Matrix OE logical server management. These volumes are created in HP-UX LVM volume groups. By default, the volume groups are not online when the HP-UX host starts up.
Provisioning a service from a template can only be done once if the template defines a server group with statically defined IP addresses and an auto allocated network. Typically, static IP addresses are used together with an explicitly defined network in the template. Matrix infrastructure orchestration does not support multiple infrastructures divided into separate networks and VLANs with duplicate IP address sets.
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.
Request with a future start date stays at 10% with status of Reserved Issue A request with a future start date stays at 10% (Progress field), with status of Reserved (rather than Scheduled). Possible cause The request is scheduled, but its status is not updated. Action Do one of the following. • Wait until the selected start date; the request should then start provisioning automatically. • Cancel the request, then resubmit it.
available targets to provision the service. Check if the targets in the selected pools are in maintenance. • Unable to allocate servers and networks in the same Virtual Connect Domain Group. Either more available servers are required, or could not match existing servers against memory size, disk space and processor count requirements.
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.
Service creation fails with “Unable to locate boot disk path” Issue A Create Service request fails on ESX or Hyper-V with an error similar to the following: “Unable to locate boot disk path H:\VSE_VirtualMachines for logical server {logical_server}_ls. VM host {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.
235=Tokyo Standard Time 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: •
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: ..
ID: 802, Detailed Error: ) Wait for the object to become available, and then try the operation again. Possible cause VM already existing in SCVMM database with the same name on the same host as requested for deployment. This could be due to: 1. A VM of the same name may have been deployed to the same host as part of a prior Service request 2. A user may have manually created a VM with the same name on the same host. 3.
Failure to add a service to a Matrix recovery management Recovery Group Issue An attempt to add a service to a Recovery Group fails and the following error message displays: Two or more services have the same name in different Organizations. Service-ids are unique across organizations but service-names are not. Possible cause The service name is not unique across all organizations. Action Make sure that your service name is unique before trying to add the service to a Recovery Group.
Service creation fails using RDM disk with high availability Hyper-V template Issue When creating a service request using RDM disks with high availability, properties must be enabled in the Matrix OE logical server management and Matrix infrastructure orchestration properties files, or service creation fails and the following message appears: The specified configuration is not supported. A physical disk cannot be connected to a High Availability Hyper-V template.
Service deletion Physical service deletion Matrix infrastructure orchestration Delete Service request leaves “clean-me” logical servers Issue Matrix infrastructure orchestration Delete Service request leaves “clean-me” logical servers Possible cause If using Insight Control server deployment, the job “Erase ProLiant ML/DL/BL Array Configuration {LinuxPE}” has not been modified for infrastructure orchestration.
For virtual logical servers, verify that all the virtual machines and the infrastructure folder name are removed from the vCenter Server. Locate the infrastructure orchestration folder under the virtual machine Host with the same name as the infrastructure provided by the user. Matrix infrastructure orchestration creates the virtual machines under this folder. If these still exist, remove the virtual machines and the infrastructure folder.
Adding servers to services Add data disk request fails Issue Add data disk request fails. Possible cause Server deactivated Action This error might occur if attempting to add a data disk for logical servers that are deactivated. To continue to add the data disk, initiate an Activate servers request, and after restoring the service, add the disks to the Logical Server Group. Provisioning of Matrix OE service fails in customization Issue Provisioning of Matrix OE service fails in customization.
Deactivate, activate, power off, or power on operations Messages displayed when a paused boot disk deployment is cancelled by an administrator Issue What messages are displayed when a paused boot disk deployment is cancelled by an administrator? Possible cause — Action When an administrator cancels a boot disk allocation that is paused, infrastructure orchestration may display two messages on the Request page: • The first message indicates that the boot disk deployment was canceled by an administrator,
The HP Matrix infrastructure orchestration tool cannot be displayed and User not authenticated messages Issue Matrix OE infrastructure orchestration console in Systems Insight Manager displays the following message: The HP Matrix infrastructure orchestration tool cannot be displayed and the error dialog displays: User not authenticated.
Operating system information does not display on the Service Details page Issue Operating system information does not display on the Service Details page. Possible cause If a server or a service is in an UNKNOWN state, an issue has occurred on that server or service. Action If the operating system is not deployed, the operating system information does not display on the Service Details page.
Extending the lease period fails without stating a specific reason or error message Issue When extending the lease period, the operation fails without stating a specific reason or error message. Possible cause There are insufficient resources.
The value of timeout.get.vmhost should always be less than the value of timeout.get.serverpools. Hyper-V VM hosts sometimes disappear from the IO server pool in large scale environments Issue Hyper-V VM hosts sometimes disappear from the IO server pool in large scale environments Possible cause An occasional communication issue between Windows server WMI data and Hyper-V VM hosts can cause the VM hosts to disappear from the server resources pool on the IO Servers tab.
Memory resources allocated to a virtual machine host are not available after using the Deactivate servers operation Issue The memory resources allocated to a virtual machine host are not available after using the Deactivate servers operation. Possible cause When virtual infrastructures or individual servers are deactivated, infrastructure orchestration does not recognize the memory previously allocated to the logical servers as available to allocate to other virtual machines.
The infrastructure orchestration Server pools tree was not removed from Systems Insight Manager during infrastructure orchestration uninstallation Issue The infrastructure orchestration Server pools tree was not removed from Systems Insight Manager during the infrastructure orchestration uninstallation process. Possible cause Systems Insight Manager was not available when infrastructure orchestration was being uninstalled. Action • Stop the HP Matrix infrastructure orchestration service.
Resources do not appear in the infrastructure orchestration Unassigned pool Issue My resources do not show up in infrastructure orchestration Unassigned Pool. Possible cause Resources are added to the infrastructure orchestration Unassigned Pool when infrastructure orchestration recognizes they are available, licensed, and configured correctly. Action To display VM Hosts: 1. In Insight Control virtual machine management, register the VM Host. 2.
Designer operations After period of inactivity, the template appears available to edit, until saving the template is attempted Issue After period of inactivity, the template appears available to edit, until saving the template is attempted. Possible cause The infrastructure orchestration designer session service has expired. Action Matrix OE infrastructure orchestration designer logs you out, but preserves the changes. To save the template, login, recover the modifications, and then save the template.
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.
Importing a template XML file that was created in a later release of IO into a previous release and backward compatibility Issue Importing a template XML file that was created in a later release of IO into a previous release of IO displays the error: “The template is invalid and could not be read by the 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.
Miscellaneous issues Email and notification Infrastructure orchestration email messages such as approval and notification are not sent Issue The infrastructure orchestration email messages such as approval and notification are not sent. Possible cause • SMTP configuration parameters are not correct. • SMTP credentials are not correct. • SMTP server is not responding. • CMS is not able to communicate with SMTP server. Action • Make sure that the SMTP configuration parameters and credentials are correct.
6. Update the property value to the host name of the CMS. 7. Click Save and Check in. Operations Orchestration Operations Orchestration Studio installation fails with error Studio version: 9.00 does not match Central version: 2.0. Setup will exit Issue Cannot install Operations Orchestration Studio. The following error is displayed: Studio version: 9.00 does not match Central version: 2.0. Setup will exit.
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 ..\Program Files\HP\Matrix infrastructure orchestration\conf\ hpio.properties and set the retry.count.ares.
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.
Migrating from one CMS to another using Operations Orchestration Issue If you are using Matrix with Operations Orchestration (OO) workflows, you may experience workflow failures after migrating from one CMS to another CMS. These failures have two sets of possible causes and actions: Possible causes and Actions 1. Duplication of values The Run ID values from one CMS are not migrated via the DMT (Data Migration Tool) when moving from one CMS to another.
c. Click Permanently store this exception. d. Click Confirm Security Exception. 4. Return to the Systems Insight Manager tab and refresh the screen, or open a new tab and go to the HP SIM web address. 5. Launch the infrastructure orchestration console. Wrong behavior of Operations Orchestration content after conversion to version 10.01 Issue Matrix infrastructure orchestration customers should not use OO 10.00, but ensure the remote instance of OO is using OO 10.
Troubleshooting communication failures Issue Troubleshooting communication failures. Possible cause — Action • Verify that the vCenter credentials are correct on Systems Insight Manager.
For large numbers of Software Automation (SA) or deployment images, the property is timeout.get.images. Other timeout properties available to configure are the following: • timeout.get.storagepools • timeout.generate.storage.entry • timeout.get.vmtemplates • timeout.get.deployment.services For example, to increase fetch subnets timeout from the default value of 5 minutes to 15 minutes, modify the line: timeout.get.subnets = 5 to: timeout.get.subnets = 15.
For Ignite-UX 1. Power on the server blade and allow it to boot the operating system. 2. From the CMS, run the mxtool Ignite Erase Disks by typing this command into a Windows command prompt: * mxexec –t “Ignite Erase Disks” –n * where is the IP address of the Ignite server being cleaned For HP Server Automation (SA): 1. Power on the server blade. 2. Press F9, and select Advanced Options, Erase Boot Disk. 3. Boot again, and press F9 again, and select the NIC as the first boot device. 4.
1. 2. 3. 4. 5. 6. In Matrix OE visualization, select Tools→ Logical Servers→Refresh. In the Logical Server perspective, verify that the logical server no longer exists. If it exists, delete it using Delete→Delete Logical Server. Use the vCenter client to browse the ESX server's datastore. Delete the VM, if it exists. Browse to the ESX server's datastore. Navigate to the directory and delete the offending directory and directory contents. For Hyper-V: 1.
1. Create a storage pool entry within the Matrix Operating Environment using the storage pool management screen from Matrix OE. In this example, the storage pool entry is defined as follows: 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.
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.
4. Create the vdisk on the EVA and present it to the host above: 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.
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.
1. Increase the amount of RAM 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. NOTE: b. c. d. e. f. If you do not have vCenter, log in directly to the ESX host as root. From the Inventory select the ESX Server host. Select the Configuration tab. Click Memory. Click Properties. On the Memory window enter a value between 256MB and 800MB for the service console parameter.
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. Select the VM Host from the left-hand side tree browser c. Select Configuration. d. From the Software panel, select System Resource Allocation. e. Select Advanced. f. From the System Resource Pools, select console. g. Select Edit Settings. h. Adjust the Shares: to High. i. If the Reservation value is less than 0.
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: • In the United States, see the Customer Service / Contact HP U
With this service, Insight Management software customers benefit from expedited problem resolution as well as proactive notification and delivery of software updates. For more information about this service, see the following website: http://www.hp.com/services/insight Registration for this service takes place following online redemption of the license certificate.
• Ignite-UX Documentation at http://www.hp.com/go/ignite-ux-docs • HP Server Automation (SA) Documentation at http://support.openview.hp.com/selfsolve/ documents Matrix infrastructure orchestration documentation For more information regarding HP Matrix Operating Environment infrastructure orchestration, see the following sources which are available for the current release on the following website: http://www.hp.
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.
http://www.hp.com/go/insightcontrol/docs As of Matrix infrastructure orchestration 7.3, HP Insight Control server deployment has been removed from the DVD media and is only available as a separate download and purchase. HP Insight Control virtual machine management HP's virtualization management technology. HP SIM See HP Systems Insight Manager. HP Storage Provisioning Manager An optional software solution bundled with Matrix OE that provides a service-centric management interface to storage.
service and infrastructure orchestration searches its inventory allocating the computing resources to all logical resource definitions in the template. public A subnet that is accessible to the Internet and cannot contain IP addresses in the 192.x.x.x or 10.x.x.x address ranges. RDP See Remote desktop protocol.. recoverable Is the ability to restore your deployment to the point at which the failure occurred.
VCEM See Virtual Connect Enterprise Manager. vCenter VMware's enterprise-level virtualization management product. Virtual Connect HP's hardware virtualization product, primarily for blade servers. virtual interface An IP address that is used as the single network address to multiple clustered servers executing an application package. A virtual interface is also known as a service IP.
A 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.
Service action workflows must receive the following parameters: • Request XML – The XML that represents the infrastructure; for example: • 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.
• Global Service End Action • User Notification • 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.
B Creating custom host name workflows The OO workflow implemented to work with the custom host names feature must define the following input parameters: Parameter Description HostnameOperationTypeEnum Defines the operation mode. Possible values; RESERVE, RELEASE, UPDATE InfrastructureServiceXML The service XML representation PropertyXML A list of server ID / hostname pairs NOTE: A return parameter is required.
HostnameOperationTypeEnum RESERVE option The HostnameOperationTypeEnum RESERVE is used during create service and add server requests. Configure the workflow parameters as follows: • PropertyXML contains the name/value pairs representing the server IDs of all servers for a create service request, and only the IDs of the added servers for an add server request. The value field of each pair is empty.
HostnameOperationTypeEnum RELEASE option The HostnameOperationTypeEnum RELEASE is used during the delete service and remove server requests. Configure the workflow parameters as follows: • PropertyXML contains the name/value pairs representing the IDs of the server(s) being removed or deleted. The value field of each pair is empty. • The workflow must find the appropriate logical servers in the InfrastructureServiceXML based on the specified server IDs.
Example 4 Received XML (PropertyXML) LogicalServer:0577a0cc-8122-4802-8173-6161b2f8dcc4 new-hostname-01 LogicalServer:15d20b1d-abee-45bb-88d8-d951dc1495d9 new-hostname-02 The Value elements are updated with host names.
C Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Index A accessing infrastructure orchestration console, 97 infrastructure orchestration designer, 94 infrastructure orchestration organization administrator portal, 100 infrastructure orchestration self service portal, 103 Operations Orchestration, 31 Active Directory integration with Insight Management, 18 add disks, 111 add servers, 109 adding user accounts to groups, 19 administrator, 14 allocation, 123 allocation algorithm server, 119 storage, 120 allocation overview, 151 Amazon EC2 cloud provisioning,
defining, 23 Customizable templates modifying settings, 22 customization, 51 cost of, 160 customizing infrastructure orchestration organization administrator portal, 102 D DAS provisioning physical servers, 119 data disk, 123 excluding, 121 VM Host, 121 delete service, 107 deployment, 122 Designer components, 96 DIO networking configuring, 79 disaster recovery protection for IO services, 53 disk array presentations configuring, 236 disk deletion, 123 disk scrubbing, 123 DR (disaster recovery protection) en
features, 11 infrastructure orchestration applications, 94 infrastructure orchestration console access, 97 Calendar tab, 98 Home page, 97 Networks tab, 98 Organization tab, 98 overview, 96 Requests tab, 98 Servers tab, 98 Services tab, 98 Software tab, 98 Storage tab, 98 tasks, 96 Templates tab, 97 Users tab, 98 infrastructure orchestration designer accessing, 95 navigation to, 94 prerequisites, 94 infrastructure orchestration organization administrator portal accessing, 100 customizing, 102 Home page, 100
memory, 241 memory oversubscription, 50 Microsoft SCVMM templates, 49 Modifying settings customizable templates, 22 multi-path storage, 153 multi-tenancy, 100, 180 overview, 180 infrastructure orchestration self service portal, 103 infrastructure orchestration self service portal interface, 104 integration, 12 lifecycle operations, 106 multi-tenancy, 180 operation, 12 product, 11 provisioning, 12 user, 14 users, 13 N name changed by Systems Insight Manager, 143 network adding network interfaces, 118 remov
SCVMM templates, 49 troubleshooting, 220 security group configuring, 56 Security groups HP Storage Provisioning Manager, 181 self service user, 14 server floating IP address, 116 snapshot, 117 server allocation algorithm, 119 Server Automation (SA) configuring, 42 server customization Insight Control server customization, 35 server deployment configuring, 37 server pools, 81 service import, 107 service addition, 210 service provisioning, 14 service request approving, 149 creating, 143 service request fails
ESX, 46 Hyper-V, 47 Integrity, 46 virtual private disks number of supported, 44 virtual provisioning, 44 Virtual servers attaching physical disks, 118 virtual shared disks number of supported, 44 virtual storage provisioning, 177 virtual to physical logical servers support in Matrix infrastructure orchestration, 151 VLAN tag configuring, 78 VM cluster provisioning federated CMS environment, 66 VM host unregister, 122 VM Hosts data disk, 121 data disk names, 120 deployed on server blades appear twice in Serv
