Top
ServerView Resource Orchestrator Cloud Edition V3.1.0 User's Guide for Infrastructure Administrators (Resource Management)

17.8.2 Operations

This section explains how to allocate resources to, and release resources from, L-Servers and how to modify configuration definition information.


17.8.2.1 Allocating Resources

When an L-Server is started, resources are allocated to it.

For details on how to start an L-Server, refer to "17.1.1 Starting an L-Server".

Server and disk resources are allocated to the L-Server, when an L-Server is first started. When cloning images are specified, deployment of images is also performed.

When server resources of L-Servers have been released, server resources will be allocated.


17.8.2.2 Releasing Resources

When stopping an L-Server, server resources will be released.

For details on how to stop an L-Server, refer to "17.1.2 Stopping an L-Server".

Methods for releasing server resources differ depending on whether the server is a physical L-Server or virtual L-Server.

17.8.2.3 Modifying Configuration Definition Information

To modify an L-Server for which a configuration definition has been created (defined), use the following procedure.

When changing the L-Server deployed when creating an L-Platform, use the rcxadm lserver modify command to modify the configuration for alive monitoring.

  1. Right-click the target L-Server in the orchestration tree, and select [Change Settings]-[Definition] from the popup menu.

    The [Modify L-Server's definition] dialog is displayed.

  2. Change the items to modify.

    For details on setting values in the [Modify L-Server's definition] dialog, refer to "Chapter 16 Creating L-Servers".

  3. Click <OK>.

    The L-Server configuration definition information is modified.

From the command-line, execute rcxadm lserver modify.
For details on the rcxadm lserver modify command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE".

Note

When modifying the configuration definition for an already defined L-Server that has been updated from an earlier version, alive monitoring is disabled. When enabling alive monitoring, modify the configuration of the L-Server again.