1.2.1 Resource Management

The following functions are provided by Resource Orchestrator.

For details on the operational environment for Resource Orchestrator, refer to "1.4 Software Environment" and "1.5 Hardware Environment".

Table 1.2 List of Available Functions
Function	Functional Overview	Remarks
Resource pools	A function that enables you to use all resources effectively and efficiently.	For details, refer to "1.2.2 Resource Pool".
L-Server creation	A function that provides L-Servers, logical servers including physical and virtual servers, which are comprised of appropriate resources in a resource pool, such as servers, storage, OS images and network. Even if there are no resources to allocate to L-Servers, flexible configuration and operation, such as creating L-Server definitions in advance, is possible.	For details on L-Servers, refer to "1.2.3 L-Servers". For details on allocating and releasing resources to and from L-Servers, refer to "11.8 Allocating and Releasing Resources to L-Servers" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
L-Server templates	A function that enables pre-definition of L-Server specifications (number of CPUs, memory capacity, disk capacity, number of NICs, etc.) to simplify L-Server creation.	For details, refer to "1.2.5 Templates".
Resource visualization	A function that displays the total size and the free space of the resources in a resource pool.	For details, refer to "1.2.6 Resource Visualization".
Simplifying network settings	A function that provides automatic configuration of network settings used for connecting network devices or creating L-Servers.	For details, refer to "1.2.7 Simplifying Networks".
Simplifying storage settings	To use storage from a physical L-Server, configure storage units and storage networks.	For details, refer to "1.2.8 Simplifying Storage".
Changing physical server usage	This function enables effective use of server resources as the operating systems and software that are started on physical servers can be changed depending on the time and situation.	For details, refer to "11.9 Changing Physical Server Usage" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Linking L-Servers with configured physical servers or virtual machines	Enables uniform management of configured physical servers or virtual machines as L-Servers by linking them to an L-Server.	For details, refer to "Chapter 16 Linking L-Servers with Configured Physical Servers or Virtual Machines" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Managing multiple resources using resource folders	A function for managing clustered multiple resources.	For details, refer to "Chapter 13 Resource Folder and Tenant Operations" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Restricting access using roles	A function for configuring roles (a collection of available operations) and access scopes (resources which can be operated) for individual users. A large number of users can be configured as a single unit using user groups that manage multiple users.	For details, refer to "Appendix B Access Control by Roles" of the "Operation Guide CE".
Sharing and dividing resources between multiple departments using tenants	A tenant is a unit for division of management and operation of resources based on organizations or operations. This function enables secure operation of sharing and dividing resources between multiple departments.	Refer to "3.2 Tenant and Resource Pool Design" and "Chapter 3 Managing Tenants" in the "Operation Guide CE".
Managing and sharing user information using LDAP coordination	By using a directory service which supports LDAP, such as Active Directory, user information can be managed and shared with other services.	For details, refer to "Appendix G User Management Using Directory Service".
Realization of high availability	Functions to enable high availability systems, with features such as L-Server and admin server redundancy, server switchover for chassis failures, and storage switchover.	For details, refer to "3.4 High Availability and Disaster Recovery Design".
DR (Disaster Recovery)	Preparing a backup system (a backup site) at remote sites to handle fatal damage caused by disasters enables administrators to perform switchover when trouble occurs.	For details, refer to "Chapter 15 Disaster Recovery" in the "Operation Guide CE".
Monitoring	A function for monitoring resource statuses of servers and displaying if the status is normal or not by using the GUI.	For details, refer to "Chapter 10 Monitoring Resources" of the "Operation Guide CE".
Power control	A function for turning servers ON or OFF.	Refer to "11.1 Power Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Hardware maintenance	Functions to simplify hardware replacement. When connected with a SAN, it is not necessary to re-configure storage units by configuring the I/O virtualization settings. By using VIOM, it is not necessary to change the settings of software or network devices to refer to MAC addresses, as the MAC address, boot settings, and network settings are automatically changed. VM host maintenance can be easily performed, using VM Home Positions.	For details, refer to "Chapter 7 Hardware Maintenance" of the "Operation Guide CE".
Network device monitoring	A function for monitoring resource statuses of network devices and displaying if the status is normal or not on the GUI. Periodic or SNMP trap monitoring can be specified when network devices are registered or changed. Periodic monitoring Network devices are periodically monitored. Alive monitoring Executes the "ping" command to the network device, and determines the existence of the device based on the response. Status monitoring Collects MIB information for the device with SNMP, and determines the status from the MIB information. SNMP trap monitoring Status monitoring (SNMP monitoring) is performed for SNMP trap (issued by the network device) reception.	For details, refer to "10.2 Monitoring Networks" of the "Operation Guide CE" and "Chapter 1 User Interface" of the "User's Guide for Infrastructure Administrators (Resource Management) CE". For details on how to specify the monitoring method, refer to "2.6 Network Configuration Information" of the "Reference Guide (Resource Management) CE".
Network maintenance	A function for maintaining network devices.	For details, refer to "Chapter 7 Hardware Maintenance" of the "Operation Guide CE".
L-Server console screen	The L-Server console screen that displays the information of physical and virtual L-Servers can be opened with common, simple operations from the Resource Orchestrator screen.	For details, refer to "11.3 Using the L-Server Console" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Managed Resources

Resource Orchestrator can be used to manage the resources described in the table below.

For details on management of chassis, servers, VM hosts, VM management software, and LAN switches (LAN switch blades), refer to "Chapter 4 Pre-setup Preparations".

Table 1.3 Managed Resources
Resource	Description
Chassis	A chassis is an enclosure used to house server blades. It can monitor the statuses of servers, display their properties, and control their power states.
Physical server	This is a general term for any physical server. This term is used to distinguish physical servers from virtual machines that are created using server virtualization software such as VMware or Hyper-V. The following usage methods are available for physical servers: Managing unused physical servers as L-Servers by registering them with Resource Orchestrator Managing configured physical servers by linking them to L-Servers VM hosts and physical OS's running on physical servers can be detected and registered as managed resources by Resource Orchestrator.
VM host	This refers to the server virtualization software running on a server to operate a virtual machine. For example, Windows Server 2008 R2, VMware ESX for VMware, domain 0 for RHEL5-Xen, VM hosts for RHEL-KVM, or Oracle VM Server with Hyper-V roles added. VM hosts can be managed by monitoring their statuses, displaying their properties, and performing operations such as HBA address rename and server switchover. When a VM host is registered, any VM guests on the VM host are automatically detected and displayed in the server tree. The power and migration operations of VM guests can be performed from the server tree, however, detected VM guests cannot perform operations as L-Servers.
VM management software	This software manages multiple server virtualization software. For example, for VMware, it is vCenter Server, for Hyper-V, it is SCVMM, and for Oracle VM, it is Oracle VM Manager. VM management software can be integrated (registered) into Resource Orchestrator to enable the use of functions for VM guests.
LAN switch (LAN switch blade)	The network switches that are mounted in a blade server chassis (LAN switch blades). Resource Orchestrator can monitor LAN switch blade statuses, display their properties, and manage their VLAN configurations. The following information is displayed in a comprehensive Network Map: Network configurations of physical servers and virtual machines (Virtual switches, VM Guests) Statuses of network connections between resources VLAN configuration status within physical servers and virtual machines
VM guest	This refers to the operating system running on a virtual machine. Resource Orchestrator can monitor VM guest statuses, display their properties, and control their power states. In addition to the functions of ROR VE, the following functions are available for use: Managing new VM guests as L-Servers Managing configured virtual machines by linking them to L-Servers
Virtual switch	This is a virtual switch used to manage a VM guest network on the VM host. In Hyper-V, it represents the concept of virtual networks. It supports virtual switches, which are standard Hyper-V virtual network and VMware functions. Cisco Nexus 1000V virtual switches are not supported.
Disk resources	This refers to a disk resource allocated to a server. For EMC CLARiiON and ETERNUS storage, this is a LUN, for NetApp storage it is a FlexVol, for EMC Symmetrix DMX or EMC Symmetrix VMAX storage it is a device, and for VM guests it is a virtual disk.
Virtual storage resources	This refers to a resource that can create a disk resource. Examples include RAID groups, aggregates, DSK groups, and file systems for creating VM (VMFS (datastore) of VMware, etc.). Disk resources can be created from RAID groups of ETERNUS storage, aggregates of NetApp storage, and file systems for creating VM.
Storage management software	Software to manage and integrate one or multiple storage units. For EMC CLARiiON storage, they are Navisphere, for EMC Symmetrix DMX storage or EMC Symmetrix VMAX storage, it is Solutions Enabler, for ETERNUS storage, it is ETERNUS SF Storage Cruiser, and for NetApp storage, it is Data ONTAP. Integration (registration) with Resource Orchestrator enables the use of functions for basic management of storage units.
Network resources	This refers to a resource that defines network information for use by an L-Server or a network device. By connecting the NIC for an L-Server to a network resource, the physical and virtual network switches are configured, enabling the L-Server to communicate. If an IP address range is set for a network resource, the IP address can be automatically set when deploying an image to an L-Server.
Network device resources	This refers to a resource that defines a network device. Firewalls and L2 switches (except for LAN switch blades) are included. It is possible to monitor the statuses of network devices, display their properties, and perform automatic configuration.
Address set resources	WWNs and MAC addresses. Necessary when creating physical L-Servers.
Virtual image resources	An image that is created using a template from a VM management software for VM guest creation, or that is collected as a cloning image from an L-Server.
Physical image resources	An image that is collected as a cloning image from an L-Server.