HP Matrix Operating Environment 7.2 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, 2013 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....................................................11 Matrix infrastructure orchestration and the Matrix Operating Environment solution...........................12 Matrix infrastructure orchestration users and groups.....................................................................
Insight Control virtual machine management templates............................................................42 Viewing VM templates with data disks.............................................................................43 Hyper-V virtual machine management templates................................................................44 Microsoft System Center Virtual Machine Manager (SCVMM) templates....................................44 Configuring ESX memory oversubscription...........................
Accessing the infrastructure orchestration self service portal.....................................................93 Self service portal interface overview....................................................................................93 4 Matrix infrastructure orchestration provisioning and allocation........................95 Matrix infrastructure orchestration lifecycle operations..................................................................95 Create service operation...........................
Predefining storage pool entries in Matrix OE visualization....................................................149 Creating storage tags.......................................................................................................150 Populating the Storage Provisioning Manager catalog...............................................................152 Enabling on-demand storage provisioning in SPM................................................................154 Physical storage provisioning........
Server reservation and allocation fail even though servers exist in the assigned pool............180 Create request fails, but the service is still listed in the Service tab in “Reserved” state, and no resources are allocated................................................................................................181 Virtual service creation.....................................................................................................
The Matrix infrastructure orchestration tool cannot be displayed due to login failure..................194 The HP Matrix infrastructure orchestration tool cannot be displayed and User not authenticated messages........................................................................................................................194 The Matrix infrastructure orchestration tool cannot be displayed due to service contact failure....
Operations Orchestration..................................................................................................204 Operations Orchestration Studio installation fails with error Studio version: 9.00 does not match Central version: 2.0. Setup will exit......................................................................204 Editing ESA flows when Operations Orchestration is not installed in the default path............204 Matrix infrastructure orchestration Windows service..........................
C Documentation feedback.........................................................................234 Index.......................................................................................................
1 Introduction HP Matrix Operating Environment infrastructure orchestration extends HP Matrix Operating Environment to provide rapid provisioning and repurposing of infrastructure services from shared compute resource pools using a self service portal.
A self service user or a self service user in an organization selects an existing template and then requests infrastructure provisioning from it, against an assigned pool of resources. A service provider administrator or organization administrator can approve or deny this request and monitor its progress.
Matrix infrastructure orchestration users and groups Matrix infrastructure orchestration is integrated with Active Directory, which allows Windows users groups, as well as individual local users, to be given access to resources. When infrastructure orchestration is installed, three local user groups (HPIO_Administrators, HPIO_Architects, and HPIO_Users) are created.
Software deployment and service provisioning Matrix infrastructure orchestration supports a variety of mechanisms for operating system software deployment.
Workflows in the limited version of Operations Orchestration included with Matrix OE may only be triggered from the Matrix OE infrastructure orchestration interface in relation to preand post- provisioning tasks. An upgrade to the full version of Operations Orchestration allows the launch of workflows from outside of the Matrix OE interface. • The limited version of Operations Orchestration allows Matrix OE to be integrated with other management software.
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.
Configuring infrastructure orchestration users in Windows The Insight Management Installer adds the user who performed the installation to the HPIO_Administrators group. To integrate Active Directory with Insight Management: 1. Ensure that the server hosting the CMS belongs to the Active Directory domain (not a workgroup). 2. Create a non-administrator user in Active Directory that will be used to run all Insight Management services. 3. Give that Active Directory user Admin privileges on the CMS. 4.
At the Organization level, there are two roles: • Organization Users Have the privileges of _Users group and have similar capabilities as the Service Provider HPIO_Users role. Can log in to infrastructure orchestration self service portal (https://:51443/ssp/). • Organization Administrators Have the privileges of the _Administrators group.
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.
For example, if the administrator sets: allow.customize.template.network = truecustomize.template.network.inclusion.list = Service Provider,orgA, orgB Then only users from Service Provider, orgA, and orgB are allowed to customize networks. All others are prevented from making changes. Values can be either organization names or IDs. Using IDs will prevent the configuration from becoming incorrect when an organization is renamed.
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.2 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.
IMPORTANT: In a federated CMS environment, the Fully Qualified Domain Name (FQDN) of any participating CMS cannot be changed. If the IP address of the primary CMS is changed, reconfigure the trusted list of each secondary CMS (described in step 1 below). 1. Configure secondary CMSs.
a. b. c. On the primary CMS, open a prompt dialog. Enter mxgethostname and note the host name that is returned. In Systems Insight Manager, select Options→Federated CMS Configuration…. The name of the primary CMS should be the same as the one returned by mxgethostname. Support for a rolling upgrade of a CMS federation Matrix OE infrastructure orchestration 7.2 includes support for a rolling upgrade of a federated CMS environment.
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.
in the HP Systems Insight Manager User Guide at www.hp.com/go/foundationmgmt/docs, in the chapter about using the CMS Reconfigure Tools. 3. 4. After you log in, a tree appears in the left panel. Expand Configuration, and then expand System Properties. Double-click any of the system properties. This shows the details of the selected system property. To display a table with all System Properties, click the blue link named System Properties.
7. Click Save, and then click Check In before exiting Operations Orchestration. Specifying SMTP credentials and system properties Operations Orchestration Studio requires an SMTP server.
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.
Copying keystore file after upgrading Operations Orchestration After upgrading Operations Orchestration from version 7.51 to 9.0, Operations Orchestration Central and Studio have different certificate keys. Operations Orchestration Studio cannot access the URL https://:16443. 1. Make a backup of the rc_keystore file on the CMS. 2. Copy the rc_keystore file installed on the CMS (..
orchestration with server deployment options. However, infrastructure orchestration can be configured to use both deployment servers, but this configuration must be done after installation is complete. If you want to add a deployment server after infrastructure orchestration is installed, enter the following commands on the CMS. NOTE: If you copy and paste these commands, be sure to enter the dash (minus) key.
5. 6. To create a job folder for each required operating system, repeat steps 1 through 4. To enable adding computers to the domain during provisioning, configure the Insight Control server deployment domain authorization using Tools→Options→Domain Accounts. Enclosures are discovered by Systems Insight Manager through the iLO IP address of the enclosure. Be sure to use the iLO credentials of the Onboard Administrator enclosure as the WBEM credentials. 7. 8.
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. 34 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. 36 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 11iv3 deployment. (HP-UX 11iv3 0709 or later is required for Integrity VM.) The Ignite server must have NFS configured and the tftp and bootps services enabled in /etc/ inetd.conf. a. To set up NFS and export the directories Ignite needs, run: /opt/ignite/lbin/setup_server –n b.
4. 5. 6. 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.
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Log in to the SA web client as Admin. In the SA user interface, select By Folder. Right click on the OS Provisioning folder name. Ensure that the Execute Objects Within Folder permission is selected. Select Users & Groups from the Navigation panel. Select the IO user for SA (typically hpiosa). Click Edit in the upper right corner. Select the Client Features tab. Scroll to the section OS Build Plan Management. Set the radio button Manage OS Build Plan to Read.
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.
See the HP Insight Management Support Matrix at http://www.hp.com/go/matrixoe/docs for supported Linux guest operating systems. Setting up virtual machine networks Network names are correlated across hypervisor and Virtual Connect technologies to allow an infrastructure service to be provisioned with logical servers of different types configured on the same network. VMware vDS (vNetwork Distributed Switch) is supported in infrastructure orchestration.
Matrix infrastructure orchestration identifies Integrity VM virtual networks using vSwitch names, which are limited to eight characters. Network names are correlated across hypervisor and VC technologies to allow an infrastructure service to be provisioned with logical servers of different types configured on the same network. Employing this capability requires the eight-character limit to be extended to the other hypervisor and VC configurations in the managed environment.
6. 7. 8. To store the virtual machine management template, in the target folder, select Browse and select a virtual machine host datastore folder, or click Next to select the default choice. Click Next. The Step 4: Confirm Details screen appears. 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.
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.
When Matrix recovery management and IO are installed on a CMS and recoverable services have been configured, you can create DR protected IO services Recovery Groups using the Matrix recovery management UI. For more information about using Matrix recovery management to provide disaster protection for recoverable services, see the HP Matrix Operating Environment Recovery Management User Guide available at http://www.hp.com/go/matrixoe/docs. The file dr.properties (installed in the default location at ..
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 25) 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 CloudSystem, or HP Matrix KVM Private Cloud. Public cloud bursting is a feature of Matrix infrastructure orchestration that enables enterprises to seamlessly provision public and private infrastructure resources.
default cloud firewall blocks all inbound traffic. To allow inbound traffic, you must create one or more rules on this page that describe that traffic. The Optional setting makes the template flexible for use with different cloud software images when using the Custom Attributes feature to customize the operating system at service creation time. For more information, see “Customizing template attributes when a service is created” (page 128).
To allow all incoming traffic, specify 0.0.0.0/0. To allow SSH connections to a server, select the TCP protocol, specify a Start Port of 22 and an End Port of 22 and IP Sources of 0.0.0.0/0. d. 3. Click Add. (Optional) To remove the firewall rule, click the Trash icon. Viewing the details of a firewall Details of a firewall associated with a template and service are shown on the Firewall Details pane at the bottom of the infrastructure orchestration console Templates and Services tabs.
Configuring a load balancer A load balancer distributes network traffic and enables optimal resource utilization across servers in a virtual or physical server group. Before beginning the configuration described in the following sections, the system administrator installs and configures a load balancer. A hardware load balancer is installed in an enclosure, and a software load balancer is installed on a physical server or virtual machine.
Optionally, a load balancer expert can customize the packaged Operations Orchestration workflows or develop new OO workflows for additional types of load balancers and add them to the OO repository. An administrator can then configure one or more of these load balancers and add them to the inventory (described in “Registering a load balancer” (page 54)).
and/or a certificate ID. These IDs are the keys to an actual password or certificate that is stored in IO. This allows more than one load balancer to use a common password or certificate. The IO administrator can manage passwords and certificates in IO using ioexec commands and the SOAP API. Typically, a load balancer has access to a private and a public network, and has an IP address on a management network.
At least one network must be selected. All networks in the server group are displayed. Only a load balancer that has access to the selected networks will be allocated. The attributes of a load balancer that you can select for a server group are as follows: High Availability Requests a load balancer in a redundant configuration. This means that there are two or more load balancers that back up and monitor each other.
Table 2 ioexec create and delete load balancer group commands ioexec command Description creategroup logicalloadbalancer Creates a group in a logical load balancer. A group describes a service to load balance deletegroup logicalloadbalancer Deletes a group from a logical load balancer, and removes all group members NOTE: The create logical load balancer operation using the SOAP API or the ioexec CLI requires administrator approval.
-s example-io-service IO service name in which to add the logical load balancer group -l LogicalLoadBalancer: Logical load balancer ID, located on the on the Services 00000000-0000-0000-0000-000000000000 tab. To view the ID, select a service and click Details, then select the Load Balance tab -g http-group Name of the group to be added to the load balancer. This is an arbitrary name specified by an administrator for easy recognition -P http Type of protocol the application service will use -a 10.1.
C:\> ioexec removegroupmember logicalloadbalancer -s example-io-service -l LogicalLoadBalancer:00000000-0000-0000-0000-000000000000 -g http-group -a 192.168.200.10 -u administrator Viewing details of a load balancer Details of a load balancer associated with a service are shown on the Services tab of the infrastructure orchestration console, self service portal, and organization administrator portal. Select a service and click Details, then select the Load Balance tab.
Table 4 Load Balance tab details (continued) Load Balance tab Description IP Address Virtual (external) IP address associated with the DNS name of the service. Members A comma separated list of IP address and port pairs. Each pair describes a server that serves the actual content of the service (website, ftp site, database, and so on). These are IP addresses of the servers in the server group.
http://www.hp.com/go/matrixoe/docs Configuring infrastructure orchestration resources in Systems Insight Manager After installing infrastructure orchestration, a member of the HPIO_Administrators Windows group can log in to the infrastructure orchestration console through Systems Insight Manager. HPIO_Administrators can then set up resources to allow provisioning. To log in to the infrastructure orchestration console, in Systems Insight Manager, select Tools→Infrastructure orchestration.
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.
Add information about the network and available IP resources on the Edit Networks page. Depending on your configuration, not all fields are required. The user interface helps guide you through the process. NOTE: 3. Matrix infrastructure orchestration supports IPv6 with the following restrictions. • Physical or virtual servers (except for Integrity servers) can be automatically provisioned using DHCP address pools.
4. 5. After adding the appropriate information to the tabbed areas of the Edit Networks screen, add the IP ranges for use by infrastructure orchestration. • To add DHCP address space, click the up arrow in the DHCP Addresses area, or enter the number of DHCP addresses to make available to infrastructure orchestration. • To add static address space, click New. A dialog appears for the range. Enter a Start and End address (inclusive), and then click OK. When finished setting up a network, click Save.
adding the NICs to a vSwitch). This is best accomplished through naming conventions and customized Operations Orchestration workflow scripts to configure the OS networking. • A VLAN is carried by one or more Virtual Connect tunnel networks or other trunk networks in the environment. A VLAN cannot be a trunk network.
Following is an example of a Virtual Connect tunnel trunk configuration. Physical networks discovered from Virtual Connect are represented as a subnet whether they are a single network or a tunneled trunk network carrying multiple subnets. Matrix infrastructure orchestration represents Virtual Connect networks based on the VC network configuration.
• Cannot be mapped to a multi-network VC profile NIC port • Cannot be part of a shared uplink set Virtual Connect mapped trunk configuration A Virtual Connect mapped trunk configuration enables VC to play a more active role managing traffic on the VLANs, including designating one of the VLANs to handle untagged packets from the VM Host. This constitutes hybrid support for both tagged and untagged networks on the VM Host.
While a request is paused, the administrator can make the necessary modifications to the environment to make the network available for allocation. When the request continues, another attempt is made to allocate the network. The service request continues only when the network resources are available. VLAN carving allows a single template definition to be used by multiple organizations, each having its own VLAN that may not yet be defined until the request is submitted.
3. Define the VLANs that can be carried by one physical network. a. In the infrastructure orchestration console Networks tab, click Create Network. b. Specify a VLAN ID, and set Network Address, Network Mask, Default Gateway, MS Domain, and WINS Servers for that VLAN ID by clicking the appropriate tab and filling in the information. In a multi-home scenario where there are multiple default gateway options, IO determines the default gateway from the network connected to the NIC that is declared as primary.
Configuring trunk and VLAN networks to enable support for Hyper-V VLAN tagging VLAN tagging is the practice of inserting a VLAN ID into network data to identify the VLAN to which the data belongs. CAUTION: Combining tagged and untagged Hyper-V virtual machines on the same virtual network results in network failures. HP recommends that you maintain a homogenous network environment among cooperating Hyper-V VM Hosts.
Non-disruptive (workaround) method The non-disruptive method is a workaround that does not disrupt your existing configuration or existing VM guests. You can continue to use existing vNics created with HP Network Configuration Utility (NCU). (This is intended as a temporary workaround until you can migrate your environment using the disruptive method below.) 1.
ESX resource pools and cloud capacity pools In addition to physical servers and VM Hosts, infrastructure orchestration includes the following types of provisionable resources: • ESX resource pools ESX resource pools are a type of compute resource created using VMware vCenter or the virtual machine management CLI, and are discovered by infrastructure orchestration. ESX resource pools are available for infrastructure orchestration to use to provision virtual machines on a standalone VM Host or in a cluster.
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 16). 4. After selecting the resources for the pool, click Save.
5. 76 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.
To create infrastructure services: 1. Review the published templates and decide which template is appropriate for the current objectives. 2. Review the assigned pools and select the resources to use for your service. 3. Submit a request to provision the service. 4. After the administrator approves the request, monitor the service provisioning execution.
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. Architects and administrators can also use the Templates tab to launch infrastructure orchestration designer allowing them to create or edit templates.
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.
Before importing a server, check the networking configuration as follows. • Make sure that the IO network that corresponds to each network used by the existing virtual machine has a static range that includes the existing virtual machine’s IP address. • If the virtual machine is using an address that you do not want as part of the static IP ranges, create a DHCP range with at least one free IP address. The following are limitations of the Import VM feature.
7. 8. Enter a user name for the service owner. (Optional) Click Check to verify that the entered user name is a valid user defined in Windows Active Directory. 9. (Optional) Enter a billing code. For more information, see “Specifying a billing code for services” (page 139). 10. (Optional) Enter Notes about the service. 11. Click Submit to import the service. Click Cancel to cancel the action, or Back to return to the previous screen.
NOTE: IO manages a server group as a homogeneous entity, so custom template attributes are not available on an Add Server operation. Remove servers from group operation The Remove Servers operation deactivates the servers, deallocates them and removes them from the server group. To remove a server 1. 2. 3. 4. 5. Open the infrastructure orchestration console, self service portal, or organization administrator portal. Select the Services or My Services tab.
To add a data disk 1. 2. 3. 4. Open the infrastructure orchestration console, self service portal, or organization administrator portal. Select the Services or My Services tab. Select a service and click Details or View Details. From the Actions or Server Actions list, select Add disks.
After successfully completing the operation, the physical server blades are allocated and configured into existing server profiles, physical and virtual servers are powered on, and the servers return to normal operation. If the operation fails, the servers are not available to activate. Deactivate servers in group operation The Deactivate servers in group operation places the selected servers in standby and removes them from service. To deactivate servers 1. 2. 3. 4.
3. 4. Select a service and click Details or View Details. From the Actions or Server Actions list, select Power off servers. During this operation, infrastructure orchestration: • Validates the request • Checks that the servers to be powered off are in the state that is allowed to be stopped • Executes custom actions • Starts the PowerOff process for all the selected servers • Executes custom actions • Sends notifications Power cycle servers To power cycle servers 1. 2. 3. 4.
NOTE: Reducing a lease period does not require approval. • Executes custom actions • Sends notifications After successfully completing a Change Lease Period operation, infrastructure orchestration modifies the lease period for the infrastructure and updates the allocation of each resource for the new lease period. If a resource is not available or an administrator rejects the request, the Change Lease Period operation fails.
To edit a virtual server 1. 2. 3. 4. 5. 6. Open the infrastructure orchestration console, self service portal, or organization administrator portal. Select the Services or My Services tab. Select a service and click Details or View Details. From the Actions or Server Actions list, select Edit virtual servers. Expand the tree and select the virtual machine you want to edit. Increase or decrease the number of processors by using the arrows in the Number of Processors field, up to the Maximum (shown in red).
3. From the Actions list, select Manage floating IPs. The Manage Floating IP Addresses dialog appears. 4. Select from the following actions: a. To create a new floating IP address, expand the tree and select a logical server. Click Create new floating IP, and then click OK. b. To move an existing floating IP address, expand the tree and click Edit next to the NIC to which you want to move the address. Type the IP address, and then click OK. c.
6. To revert a VM to a snapshot, expand the tree, select a snapshot, and click Revert. The Revert to snapshot? dialog appears. Reverting a snapshot returns the virtual machine's memory (if selected when the snapshot was created), settings, and virtual disks to the state they were in when the snapshot was created. a. (Optional) Click to select Do not power on after revert to suppress powering on the virtual machine after reverting to a snapshot.
• Sufficient number of processors • Sufficient available memory • Sufficient available disk space • Network connectivity From these candidates, infrastructure orchestration selects the VM Host that has the most: • Available disk space If all VM Hosts have the same amount of free disk space (which is common with cluster shared volumes), infrastructure orchestration selects the VM Host based on processor number and available memory.
Linked clone provisioning can also require more space than is designated in the template. If you deploy only one server, the amount of disk space will be more than the template because you are provisioning a parent VM and a child VM. However, if you deploy more than one server, the total size might be less than the template because the space needed by the parent VM is deducted from the total. The parent VM is powered off and used to create the child VMs.
NOTE: Because the volume.exclusion.list values are treated as regular expressions, some characters are interpreted to have special meaning, for example, backslash (\), question mark (?), and brackets {}. To indicate that these characters should be treated as regular characters, they need to be escaped with a backslash. Because a backslash is a special character in the property file syntax, it has to be escaped as well.
◦ Works with a SAN administrator to create the storage. ◦ Defines the storage in Matrix OE logical server management. ◦ Continues the operation. When the operation continues, infrastructure orchestration reattempts to allocate the resources. This pause is always necessary when infrastructure orchestration is configured to perform manual storage provisioning and data disks are defined in the service template.
1. Launch infrastructure orchestration designer at https://:51443/hpio/designer/ and click New to begin. 2. Drag one of each of the Physical Server Group (which includes Physical Storage), and Network components onto the working area. 3. Connect the Physical Server Group to the Network.
4. 112 Set the attributes for each of the components. Right click on the Physical Server Group and select Edit Server Group Configuration. Note the Server Type is “Physical.” The Processor Architecture must match the storage pool entry.
5. Set the Networks attributes for the server group. Specify a Hostname. There are three parts to the physical server's 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.
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.
The setting for Redundant SAN paths to disk depends on the need for redundancy and any defined logical server storage pool entries. Matrix infrastructure orchestration will search for a matching storage pool entry for each service provisioned. If one is not found and the Storage Provisioning Manager is in use, Matrix infrastructure orchestration will auto-generate a storage pool entry and attempt to fulfill it through SPM.
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 128) 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. Procedure 2 1. 2. 118 Launch infrastructure orchestration designer at https://:51443/hpio/designer/ and click New to begin. Enter a template name and drag a Virtual Server Group (which automatically includes Virtual Storage), and a Network component onto the area where the instructions are displayed. 3.
Select Deploy as Linked Servers to deploy the servers in the server group as linked, and adjust the maximum number of servers as required. NOTE: When Deploy as Linked Servers is selected, the first logical server in a linked clone logical server group is provisioned with both a parent VM and a clone (child) VM. The remaining logical servers in the logical server group are provisioned with only a clone VM. For more information about linked clones, see the following website: www.vmware.
6. For the Network Interface Assignment Type, choose the appropriate setting depending on how you configured the IO environment: DHCP Indicates that IP addresses are allocated dynamically to servers connected to the subnet using DHCP. Static Indicates that the architect assigns the IP addresses used by each server connected to the subnet. Using static IP addresses creates a template that can be provisioned only one time.
When you use a Windows template, you can also choose a Sysprep file. The Sysprep files for you to select must be located in ..\Program Files\HP\Matrix infrastructure orchestration\conf\sysprep. When you click the Change button, all of the Sysprep files in the directory are displayed. 8. (Optional) On the Load Balance tab, request a load balancer containing the specified attributes to distribute network traffic across servers in a virtual or physical server group.
9. Set the attributes for the Virtual Storage. Note that the Storage Type must be Virtual. Select Disk is bootable to denote that the disk is the boot disk for the server group. • For bootable disks, you can assign a Storage Volume Name to match mounted volume names on a VM Host. Storage Volume Name(s) is an optional feature for the boot disk. Storage volume names are used for every virtual disk attached to the virtual server group. Enter the VM Host storage volume names separated by commas.
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 128) and “Configuring a disaster recovery (DR) service” (page 47) 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. This template is now available for deployment by authorized users. Creating a template to provision at a cloud service provider In addition to provisioning with on-premise resources, Matrix OE infrastructure orchestration supports provisioning virtual servers to an external cloud service, such as a supported CloudSystem bursting service provider, another CloudSystem, or an HP Matrix KVM Private Cloud.
By default, the custom host names feature is not enabled. Until it is enabled, the existing host name generation strategy is used. The following properties (set in the hpio.properties file) control the behavior of the new functionality: Property Description Default oo.enable.custom.hostnames When set to true, the custom host false names feature is enabled oo.custom.hostnames.flow Specifies the path to the OO workflow. This property is evaluated only when oo.enable.custom.
NOTE: When Systems Insight Manager runs the discovery task, it changes the logical server host name by prefixing the host name with the VM host name and the service template name. For example, if IO provisions a virtual machine named vm1 on a VM Host named VMhost1 using a template named mytemplate, after Systems Insight Manager runs the discovery, the virtual machine host name is changed to VMhost1_mytemplate_vm1.
7. Click Options. On the expanded Create Service From Template dialog, specify the Service Name, and set or enter other desired options. The service name is used by users, administrators, and in progress logs to identify this create service request. The service name can contain up to 15 characters using letters (A-Z, a-z), numbers (0-9), space, underscore, and hyphen. If the template is an ESX host or cluster, the resource pool selected is the name of the cluster. Optionally, specify a data center name.
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.
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. For more information, see “Modifying settings for use with customizable templates” (page 20).
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 133)).
3. Use the Insight managed system setup wizard (MSSW) to configure the system to be managed. From Systems Insight Manager, select Configure→Managed system setup wizard. For more information, see the Insight Managed System Setup Wizard Getting Started Guide located at the 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.
NOTE: The APIs and CLI command can retrieve data only for the last 365 days. Ensure that you save old data before it is more than one year old so that you can access the data, if needed. Specifying fixed costs for templates and services Matrix infrastructure orchestration allows a template architect to add a fixed cost to a template, in addition to server, network, and storage costs. Examples of fixed costs are power or setup costs.
Specifying per-unit costs for resources In infrastructure orchestration designer, right click on the server group to display the Config tab, where you can enter costs per number of servers in the server group, processors per server, and memory size. Costs for a server in an IO template is split into three values: Base Cost per Server Encompasses all of the costs for the server except CPU and memory cost. It may include availability characteristics and type characteristics (physical, virtual, cloud).
In infrastructure orchestration designer, right click on a virtual or physical disk to display the Config tab, where you can enter the cost per disk unit (MB or GB). Specifying costs for services deployed to public cloud providers A template that is deployed to a public cloud service provider can associate a cost value and a cost frequency to the external resources in the same way as for all other resources in a template.
NOTE: The billing code can be modified only on the console. It is read-only on the infrastructure orchestration self service portal and infrastructure orchestration organization administrator portal. Email messages sent for Paused for Approval, Add Servers, and Add Disks display billing code information. If the billing code is not supplied, None is shown.
Enter a value of 1 to convert the template to the global cost unit without changing the values. For example, if the global cost unit is euros and the information in the template contains the correct amounts in euros but is expressed as dollars, enter 1 to convert the template from dollars to euros. Chargeback metrics collected and reported The following table describes the report metrics and their values. Table 7 Chargeback reported metrics Metric Value Allocation time Measured in minutes.
Table 8 Chargeback CLI commands Operation Description get usage Returns usage and cost data for selected services. For daily infrastructure usage data, set the period.type flag to DAILY. To return summarized infrastructure for a period, set the period.type flag to PERIOD. Server, Disk and IP address data is consolidated per infrastructure. get detailedusage Returns detailed usage and cost data for selected services. For daily infrastructure usage data, set the period.type flag to DAILY.
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 154)) • 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.) • 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. • Storage Volume Name(s) is a comma-separated list that specifies the VM Host storage volume(s) used to allocate virtual storage for the attached server group. (This is analogous to specifying the storage volume used to allocate storage for physical servers using Physical Storage tags.
5. If the boot disk has been reserved, but the data disk reservation still cannot be satisfied, Matrix OE attempts to automatically create an SPE for the data disk(s) that will be fulfilled through SPM. Result: If data disk(s) are still not fulfilled, pause the request and raise an email alert (using an Operations Orchestration workflow) requesting manual storage provisioning for the 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 Service Provider and organizations ◦ Service provider user Can log into the infrastructure orchestration self service portal and initiate requests for provisioning using published templates •
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 167) 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.
template can call out a network by part of its name and the appropriate network for the organization is assigned during allocation of the service. For example: 1. On the infrastructure orchestration console tab, assign VLANs organization_1_Production and organization_2_Production to organization_1 and organization_2, respectively. 2. In infrastructure orchestration designer, create a template, and specify the network as follows: a. In the Configure Network tab, select “Specify desired attributes” b.
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.
Warning — HP Matrix infrastructure orchestration was successfully installed but the federated CMS feature was not enabled. Refer to the HP Matrix infrastructure orchestration User Guide for information about how to enable federated CMS. Possible cause The CMS IP address cannot be correctly resolved to the CMS FQDN during installation, so the Installer adds the CMS IP address to the managed_cms_list property. However, the managed_cms_list must be configured with the CMS FQDN.
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. • One or more servers considered available for use were actually in the maintenance pool. • At least one of the server blades in a referenced user server pool already has a profile assigned.
to enter Fast!UTIL and reset the adapter defaults. For more information, see “Correcting a checksum error” (page 214). 6. Perform a manual clean-up process for any affected logical server. See “Manual clean-up process (physical)” (page 209). To modify the Insight Control server deployment job: 1. Follow the steps in the Creating server deployment job folders procedure. The job must have only two steps: Task Details Run Script Wipe Disk Power Control Shutdown (if available) 2.
Storage pool entry status is “Presentation Completed with Errors – Inoperable” or “Presentation Completed – Inoperable” Issue After creating a storage pool entry from an array imported into SPM, the status of the storage pool entry on the Matrix OE visualization Manage Storage Pool screen is “Presentation Completed with Errors Inoperable” or “Presentation Completed Inoperable”.
groups are not online when the HP-UX host starts up. This results in existing guests being unable to access their storage, further causing any associated logical servers to become inoperable. Action Create a multi-node Serviceguard package for each of the SLVM volume groups to activate volume groups after a host reboot. This will enable the SLVM volume groups to be started when Serviceguard starts during HP Integrity VM Host start up. Follow the first two steps in section 10.5.
IP address sets. When static IP addresses are allocated to one network, they cannot be reallocated to a different network. Action Change static IP addresses in the template each time you use the template, or use automatic IP address allocation. Automatic allocation enables you to use the template multiple times for multiple infrastructures, each having a different set of IP addresses assigned to the service.
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.
{vm_host} may have more than one local disk visible as a target data store. Select a VM host with a single local disk, or update the selected VM host to have just one local disk." Possible cause This error is displayed when the number of concurrent requests for the virtualization type is too high. Action 1. Edit the ..\Program Files\HP\Matrix infrastructure orchestration\conf\ hpio.properties file. 2. Set the values of esx.max.concurrent.requests and/or hyperv.max.concurrent.requests to 5. 3.
Error getting DHCP address during add server request Issue A user cannot allocate DHCP addresses from a particular subnet during an add server request Possible cause This problem occurs when the following conditions are met: • Matrix OE is running in a federated CMS environment • Simultaneous changes are made on subnets (requests allocating IP addresses while the subnet is being edited) • After error messages, a backup/restore process is initiated Action To avoid this issue: • Do not edit a subnet that
Provisioning virtual machine failed with a VM must be powered off for customization error message Issue Provisioning a virtual machine failed with a VM must be powered off for customization error message. Possible cause The Insight Control virtual machine management template that is being used was created when the virtual machine was in a suspended state.
Task for logical server has failed: Service console load average on the source server is greater than the threshold value Failure message Task for logical server has failed. Failure: Service console load average on the source server is greater than the threshold value. Retry the operation later. Possible cause The load average on the source or target VM Host may be too high. Verify this issue by examining the Insight Control virtual machine management log file at: ..
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.
NOTE: When using the mxnode command, enter the root/ for the provisioned server into the global credentials for Systems Insight Manager (Options→Security→Credential→Global Credentials).
Subnet2 is associated with VmHost2 and no others. Based on subnet allocation criteria, Subnet1 is the best choice for LogicalSubnetA. However, if VmHost1 is unsuitable for the LogicalServerGroups associated with LogicalSubnetA, the reservation will fail without Subnet2 being evaluated.
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 Matrix infrastructure orchestration tool cannot be displayed due to service contact failure Issue When logging into infrastructure orchestration in Systems Insight Manager, an error page appears stating The Matrix infrastructure orchestration tool cannot be displayed. Cannot contact the infrastructure orchestration service running at: Possible cause The infrastructure orchestration service is not running on the CMS.
Networks tab does not retrieve network information Issue The Networks tab does not retrieve any network information, or IO allocation failure and provision failure occurs. Possible causes • VMware vCenter Server credentials are not configured or are lost during an Insight Control virtual machine management update. • VMware vCenter Server is unreachable. Action • Enter the VMware vCenter Server credentials in HP SIM. 1. 2.
Operation on servers under a VCDG did not complete the requested operation Issue An operation on servers under a VCDG did not complete the requested operation. Possible cause Server is not managed by Virtual Connect Enterprise Manager. Virtual Connect Domain Group status must display managed by Virtual Connect Enterprise Manager for infrastructure orchestration to correctly execute operations over its resources.
3. Rediscover Hyper-V VM hosts in Systems Insight Manager. 4. Check the device subtype of the VM hosts. If the subtype does not display “Microsoft Hyper-V Virtual Host”, restart the WMI Mapper service and rediscover the VM host. Server blades that are not in use are shown in infrastructure orchestration server pools but are not allocated for provisioning Issue Server blades that are not in use are shown in IO server pools, but IO does not allocate the blades for provisioning.
Request continues to process after being canceled Issue A request continues to process after being canceled. Possible cause Current task in progress. Action When a request is canceled, infrastructure orchestration has to allow the ongoing tasks in the managed environment to complete. No new tasks are started, however all in progress tasks must complete before the request can be canceled.
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.
IO server. The Details tab may provide more information about which part of the template XML is invalid.” Cause For IO templates, backward compatibility is not supported. Forward compatibility is supported. Action Create and publish templates at the earliest IO version to which they are targeted.
Access error on infrastructure orchestration web pages from email notification using private network Issue Access error on infrastructure orchestration web pages from email notification using private network. Possible cause In some cases, the administrator cannot access the approve/reject web page (and other Matrix infrastructure orchestration pages) from the notification email that asks the administrator to continue or reject a user request.
6. In the Inspector grid, click the arrow button on the right side and edit the path displayed in the Constant Value field to match the actual path. 7. Click Save to save the path, then check in and save the flow with the updated information. Matrix infrastructure orchestration Windows service Matrix infrastructure orchestration may time out while waiting for the server to be recognized Issue Matrix infrastructure orchestration may time out while waiting for the server to be recognized.
CMS crash recovery Create Service request does not complete successfully after CMS crash recovery Issue Create Service request 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 Virtual Connect Manager (VCM) are out of sync due to a CMS crash that occurred while assigning a server profile. Action • Perform VC Domain maintenance.
Add Disk request for an ESX virtual server does not complete successfully after CMS crash recovery Issue Add Disk request for an ESX virtual server does not complete successfully when resumed after CMS is recovered from a crash. Possible cause A CMS crash occurred while vCenter was creating a virtual disk, causing an incomplete disk creation. Action • Remove the partially created virtual disk file from vCenter. • Refresh server resources from logical server management. • Re-issue the Add Disk request.
Corrective procedures Manually updating the chargeback database Chargeback server is not running Issue If the chargeback server is not running for any reason, the chargeback database will be out of date. Possible cause — Action Execute the Update_Chargeback_DB.py command to force chargeback database population for a given day or sequence of days. Run Update_Chargeback_DB.py located in the default location at ..\Program Files\HP\ Matrix infrastructure orchestration\chargeback.
4. 5. Check the SPM job table for any failed jobs. In SPM, click No Running Jobs in the lower left portion of the screen, click the History tab, and then look for Activating Service jobs. If these locations do not provide the information needed to solve the problem, check the following log files: • C:\Program Files (x86)\HP\Storage Provisioning Manager\logs\ operational_log.txt • C:\Program Files\HP\Matrix infrastructure orchestration\logs\ hpio-controller.
pool. Manual clean-up of the failed server blade depends on the deployment server used to provision it. For Insight Control server provisioning: 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. Verify that the server blade is powered off after completing the above step. Manually power off the blade server, if needed. 5.
NOTE: Do not select the Unmanage Logical Server option. Doing so will cause the logical server storage pool entry to be modified to contain new WWNs without regard to presentation or zoning. Follow the procedure in “Configuring storage pool entries, FC zones, and disk array presentations” (page 211) to resolve this issue. 3. 4. Verify that the VC profile associated with the failed server blade exists in Virtual Connect Enterprise Manager.
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. 212 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.
HP Insight Rapid Deployment software See See HP Insight Control server deployment. . 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. HP Systems Insight Manager An HP systems and resources monitoring and management product. HP Virtual Connect Enterprise Manager HP's enclosure-spanning hardware virtualization management software product.
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 See HP Insight Control server deployment. Formerly HP Insight Rapid Deployment software.. recoverable Is the ability to restore your deployment to the point at which the failure occurred.
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. Windows Internet Name Service Microsoft's name server and service (similar to DNS for domain names) - mapping between host names and network addresses. WINS See Windows Internet Name Service.
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.
Figure 4 OO Studio custom hostname output parameters 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.
Example 1 Received XML (PropertyXML) LogicalServer:0577a0cc-8122-4802-8173-6161b2f8dcc4 LogicalServer:15d20b1d-abee-45bb-88d8-d951dc1495d9 The empty Value element is replaced by the host name creation workflow. See the returned XML example below.
Example 3 Received XML (PropertyXML) LogicalServer:0577a0cc-8122-4802-8173-6161b2f8dcc4 LogicalServer:15d20b1d-abee-45bb-88d8-d951dc1495d9 The RELEASE operation may be triggered by a create service or add server request.
/Library/Hewlett-Packard/Infrastructure orchestration/Custom Hostnames/samples/hostname powershell • A sample that implements a pool of host names by storing predefined values in a database. Whenever a server is created, a host name from the pool is consumed. The host name is released for reuse when the associated server is removed, and it is updated in the case where Matrix infrastructure orchestration detects an out-of-band host name change.
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, 87 infrastructure orchestration designer, 84 infrastructure orchestration organization administrator portal, 90 infrastructure orchestration self service portal, 93 Operations Orchestration, 28 Active Directory integration with Insight Management, 17 add disks, 99 add servers, 98 adding user accounts to groups, 18 administrator, 13 allocation, 109 allocation algorithm server, 106 storage, 107 allocation overview, 134 Amazon EC2 cloud provisioning, 50 A
delete service, 96 deployment, 109 Designer components, 86 disaster recovery protection for IO services, 47 disk array presentations configuring, 211 disk deletion, 110 disk scrubbing, 110 DR (disaster recovery protection) enabled services, 47 E edit virtual servers, 103 editing ESA flows, 204 ESA configuration, 77 ESA flows, referencing correct OO install path, 204 ESX cloud resources, 72 ESX resource pools, 72 ESXi cluster provisioning configuring, 60 resource pools, 72 ESXi support Insight Control serve
accessing, 90 customizing, 92 Home page, 90 Networks tab, 91 Organization tab, 91 Requests tab, 91 Servers tab, 91 Services tab, 91 Templates tab, 91 Users tab, 91 infrastructure orchestration self service portal access, 93 accessing, 93 Calendar tab, 94 customizing, 92 Home page, 94 My History tab, 94 My Pools tab, 94 My Requests tab, 94 My Services tab, 94 Templates tab, 94 inoperable storage pool entry, 175 Insight Control, 11 Insight Control server deployment job folders, 33 Insight Control server provi
creating, 164 identifer, 162 network sharing, 166 users and groups, 162 OS Build Plan Management permissions, 38 overview administrator, 13 architect, 13 automation, 11 console interface, 87 designing, 11 infrastructure orchestration console, 86 infrastructure orchestration organization administrator portal, 161 infrastructure orchestration organization administrator portal interface, 90 infrastructure orchestration self service portal, 92 infrastructure orchestration self service portal interface, 93 integ
in a federated CMS environment, 24 on-demand storage provisioning, 154 storage tags creating in logical server management, 150 support, 220 Support Matrix, 16 supported versions of products to use with infrastructure orchestration, 16 sysprep, 46 system properties, 25 Systems Insight Manager settings, 61 T Telnet Firefox 32-bit running on Windows 64-bit, 90 IE 32-bit running on Windows 64-bit, 89 templates, 42 timeout value, 131 troubleshooting adding servers to services, 193 Console operations, 194 flexin
