Veritas™ Operations Manager LDom Capacity Management Add-on ...

Veritas <strong>Operations</strong> <strong>Manager</strong>
<strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong>
<strong>Add</strong>-on User's Guide
4.1
November 2011

Veritas <strong>Operations</strong> <strong>Manager</strong> <strong>LDom</strong> <strong>Capacity</strong>
<strong>Management</strong> <strong>Add</strong>-on User's Guide
The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.
Product version: 4.1
Documentation version: 4.1.0
Legal Notice
Copyright © 2011 Symantec Corporation. All rights reserved.
Symantec, the Symantec logo, Veritas, and Veritas Storage Foundation are trademarks or
registered trademarks of Symantec Corporation or its affiliates in the U.S. and other
countries. Other names may be trademarks of their respective owners.
This Symantec product may contain third party software for which Symantec is required
to provide attribution to the third party (“Third Party Programs”). Some of the Third Party
Programs are available under open source or free software licenses. The License Agreement
accompanying the Software does not alter any rights or obligations you may have under
those open source or free software licenses. Please see the Third Party Legal Notice Appendix
to this Documentation or TPIP ReadMe File accompanying this Symantec product for more
information on the Third Party Programs.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, display or disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com

Technical Support
Contacting Technical Support
Symantec Technical Support maintains support centers globally. Technical
Support’s primary role is to respond to specific queries about product features
and functionality. The Technical Support group also creates content for our online
Knowledge Base. The Technical Support group works collaboratively with the
other functional areas within Symantec to answer your questions in a timely
fashion. For example, the Technical Support group works with Product Engineering
and Symantec Security Response to provide alerting services and virus definition
updates.
Symantec’s support offerings include the following:
■
■
■
A range of support options that give you the flexibility to select the right
amount of service for any size organization
Telephone and/or Web-based support that provides rapid response and
up-to-the-minute information
Upgrade assurance that delivers software upgrades
■ Global support purchased on a regional business hours or 24 hours a day, 7
days a week basis
■
Premium service offerings that include Account <strong>Management</strong> Services
For information about Symantec’s support offerings, you can visit our Web site
at the following URL:
www.symantec.com/business/support/
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.
Customers with a current support agreement may access Technical Support
information at the following URL:
www.symantec.com/business/support/
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be
at the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
■
Product release level

■
■
■
■
■
■
■
Hardware information
Available memory, disk space, and NIC information
Operating system
Version and patch level
Network topology
Router, gateway, and IP address information
Problem description:
■ Error messages and log files
■ Troubleshooting that was performed before contacting Symantec
■ Recent software configuration changes and network changes
Licensing and registration
Customer service
If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
www.symantec.com/business/support/
Customer service information is available at the following URL:
www.symantec.com/business/support/
Customer Service is available to assist with non-technical questions, such as the
following types of issues:
■
■
■
■
■
■
■
■
■
Questions regarding product licensing or serialization
Product registration updates, such as address or name changes
General product information (features, language availability, local dealers)
Latest information about product updates and upgrades
Information about upgrade assurance and support contracts
Information about the Symantec Buying Programs
Advice about Symantec's technical support options
Nontechnical presales questions
Issues that are related to CD-ROMs or manuals

Support agreement resources
If you want to contact Symantec regarding an existing support agreement, please
contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan
Europe, Middle-East, and Africa
North America and Latin America
customercare_apac@symantec.com
semea@symantec.com
supportsolutions@symantec.com

Contents
Technical Support ............................................................................................... 4
Chapter 1
Overview of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
4.1 ...................................................................................... 9
About the Veritas <strong>Operations</strong> <strong>Manager</strong> <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong>
<strong>Add</strong>-on .................................................................................. 9
About Logical Domains (<strong>LDom</strong>s) ..................................................... 10
About organization entity .............................................................. 10
Features of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on ............................... 11
About the tasks for reserving <strong>LDom</strong>s ............................................... 12
Compliance violations in <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on ............. 12
Prerequisites for using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on ................ 13
Limitations of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on ........................... 13
Chapter 2 Using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on ................. 15
Enabling an organization entity for <strong>LDom</strong>s capacity planning .............. 15
Enable organization entity for capacity planning panel
options ........................................................................... 16
Disabling an organization entity for <strong>LDom</strong>s capacity planning ............. 17
Reserving <strong>LDom</strong>s on clusters of an organization entity ....................... 17
Reserve <strong>LDom</strong>s on clusters panel options ................................... 18
Index .................................................................................................................... 21

8 Contents

Chapter
1
Overview of <strong>LDom</strong> <strong>Capacity</strong>
<strong>Management</strong> <strong>Add</strong>-on 4.1
This chapter includes the following topics:
■
■
■
■
■
■
■
■
About the Veritas <strong>Operations</strong> <strong>Manager</strong> <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
About Logical Domains (<strong>LDom</strong>s)
About organization entity
Features of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
About the tasks for reserving <strong>LDom</strong>s
Compliance violations in <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
Prerequisites for using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
Limitations of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
About the Veritas <strong>Operations</strong> <strong>Manager</strong> <strong>LDom</strong> <strong>Capacity</strong>
<strong>Management</strong> <strong>Add</strong>-on
Veritas <strong>Operations</strong> <strong>Manager</strong> further extends its capabilities in virtual
infrastructure management by introducing support for Solaris Logical Domains
(<strong>LDom</strong>s). The Veritas <strong>Operations</strong> <strong>Manager</strong> <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
lets you manage the activities that are related to <strong>LDom</strong>s space allocation and
management. It lets you manage physical and virtual servers in the environment
that contains pools of physical servers. Using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on,
you can reserve space for <strong>LDom</strong>s on servers (cluster nodes) through Veritas
<strong>Operations</strong> <strong>Manager</strong> console. The clusters and nodes are managed by Veritas
Cluster Server (VCS), and the virtual machines are configured from a specific VCS

10
Overview of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on 4.1
About Logical Domains (<strong>LDom</strong>s)
cluster. Using the concept of organization entity, users can now group multiple
such VCS clusters into one organization entity, and reserve <strong>LDom</strong>s on the nodes
of these clusters.
Why do you need <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on?
In a typical datacenter, the task of capacity management for a large number of
physical servers is challenging. The administrator needs a tool that can assist in
<strong>LDom</strong>s provisioning in a pool of physical servers based on the resource
requirements of the <strong>LDom</strong>s and the high availability (HA) requirements of the
pool. The <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on allows the storage administrator
to reserve server space for <strong>LDom</strong>s in advance, and prevents them from
over-subscribing the available server resources.
Note: <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on 4.1 is supported only on Veritas
<strong>Operations</strong> <strong>Manager</strong> 4.0, and later.
See “About organization entity” on page 10.
See “Features of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on” on page 11.
See “Compliance violations in <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on” on page 12.
See “Limitations of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on” on page 13.
See “Prerequisites for using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on” on page 13.
About Logical Domains (<strong>LDom</strong>s)
Logical Domains (<strong>LDom</strong>s) is a technology that allocates resources such as
processors, memory, disks, or network devices to logical containers. It manages
these resources as logical domains within the physical host. The resulting <strong>LDom</strong>
has its own operating system, and it manages resources independently.
See “Reserving <strong>LDom</strong>s on clusters of an organization entity” on page 17.
About organization entity
In Veritas <strong>Operations</strong> <strong>Manager</strong>, an organization entity is a business entity of
organization type. It is a collection of servers that have similar characteristics.
The user needs to add the managed hosts to the organizational entity. The
associated clusters are inherited automatically. The clusters are managed by VCS
and you can reserve <strong>LDom</strong>s on these clusters. VCS manages each <strong>LDom</strong> as a
resource or an application, and not as a VCS node. The Veritas <strong>Operations</strong> <strong>Manager</strong>
lets you generate reports and enforce compliance criteria for the organizational

Overview of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on 4.1
Features of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
11
entity. If any cluster node in an organization entity does not comply with the
specified criteria, Veritas <strong>Operations</strong> <strong>Manager</strong> generates faults and risks.
Note: No separate user interface element is provided to create a new Organizational
Entity. You need to create a business entity of type organization, and mark it for
the <strong>LDom</strong>s reservation.
See “Enabling an organization entity for <strong>LDom</strong>s capacity planning” on page 15.
See “Disabling an organization entity for <strong>LDom</strong>s capacity planning” on page 17.
See “Reserving <strong>LDom</strong>s on clusters of an organization entity” on page 17.
Features of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
The <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on 4.1 provides you with the following
features to manage <strong>LDom</strong>s reservation:
■
■
■
Mark the organization entity for <strong>LDom</strong> reservation.
Reserve space for the <strong>LDom</strong>s on one, or more cluster of the selected
organization entity.
Define the compliance criteria when you mark an organization entity for the
<strong>LDom</strong> reservation. Three parameters are used for the organization entity:
■
■
Number of VCPUs or cores per server
Memory per server
■ Number of spare servers: It is the allowed number of nodes in a cluster that
can go offline without affecting the availability of <strong>LDom</strong>s on the cluster.
When any server fails, all the <strong>LDom</strong>s running on that server can failover
to one or more remaining nodes (including the spare server).
For an organization entity, all cluster nodes must meet the compliance criteria.
For example, all nodes must have same VCPU count in an organization entity.
■
Ability to select the best-fit cluster for the <strong>LDom</strong> reservation based on virtual
machine’s resource requirement, and the available capacity of the cluster.
When you allocate space for the <strong>LDom</strong>, the <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
provides you with the options to either completely exhaust the most consumed
node, or distribute the load equally across multiple nodes in the clusters.
The spare server option is important for mission-critical applications. It lets
you set number of servers in an organization entity that can be used for <strong>LDom</strong>
failover. This feature ensures that if a cluster node fails, all the <strong>LDom</strong>s
configured on that node can failover to one or more of the remaining nodes.

12
Overview of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on 4.1
About the tasks for reserving <strong>LDom</strong>s
■
■
■
■
Ability to reserve space for new virtual machine on a cluster so that it is
considered for any subsequent best fit calculations.
Ability to automatically associate the virtual machine with the original reserved
space on the cluster.
View compliance violations across the domain.
View virtual machine deployment report per organization entity.
See “About the tasks for reserving <strong>LDom</strong>s” on page 12.
See “Limitations of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on” on page 13.
About the tasks for reserving <strong>LDom</strong>s
This section lists the steps that you need to perform to reserve <strong>LDom</strong>s:
■
■
■
Create an Organizational Entity with the required Solaris servers.
Reserve the <strong>LDom</strong>s on the best-fit cluster based on the VCPU count and the
memory requirements. You can use either Pack or Balance method.
Provision the <strong>LDom</strong> and configure it as a Service Group in VCS with correct
values for Load attribute based on the VCPU value for the <strong>LDom</strong>.
Note: This step cannot be performed using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on.
■
■
After the VCS configuration, Veritas <strong>Operations</strong> <strong>Manager</strong> automatically detects
and correlates the <strong>LDom</strong> and its corresponding VCS Service Group with the
reserved space.
If there are compliance violations, you can see corresponding risks and faults
in Veritas <strong>Operations</strong> <strong>Manager</strong> console.
Compliance violations in <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong>
<strong>Add</strong>-on
This topic provides a list of scenarios that may cause compliance violations in
<strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on. The Veritas <strong>Operations</strong> <strong>Manager</strong> raises alert
for such violations.
■
When the number of VCPUs on any physical servers of an organization entity
is not same as count per server (CPS).

Overview of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on 4.1
Prerequisites for using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
13
■
■
When more <strong>LDom</strong>s are configured and reserved in the VCS cluster than
managed by Veritas <strong>Operations</strong> <strong>Manager</strong> to maintain high availability.
When the discovered <strong>LDom</strong>s are not configured in Veritas Cluster Server.
Prerequisites for using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong>
<strong>Add</strong>-on
This topic lists the prerequisites for using the <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on.
■
■
■
All cluster nodes must be the part of organization entity.
The <strong>LDom</strong> must be configured on all the nodes in a cluster.
There must not be any non-clustered <strong>LDom</strong> on the cluster nodes.
See “Limitations of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on” on page 13.
Limitations of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
This topic lists the limitation of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on.
■
■
You need to manually perform the operations that are related to <strong>LDom</strong> setup
and Veritas Cluster Server configuration.
The add-on is applicable only to those <strong>LDom</strong>s, which are configured as high
available (HA) using Veritas Cluster Server.

14
Overview of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on 4.1
Limitations of <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on

Chapter
2
Using <strong>LDom</strong> <strong>Capacity</strong>
<strong>Management</strong> <strong>Add</strong>-on
This chapter includes the following topics:
■
■
■
Enabling an organization entity for <strong>LDom</strong>s capacity planning
Disabling an organization entity for <strong>LDom</strong>s capacity planning
Reserving <strong>LDom</strong>s on clusters of an organization entity
Enabling an organization entity for <strong>LDom</strong>s capacity
planning
You can enable an existing organization entity for <strong>LDom</strong>s capacity planning. An
organization entity is a collection of Solaris servers that share some characteristics.
After you have enabled the organization entity, you can reserve <strong>LDom</strong>s on the
clusters that belong to the selected organization entity.
To enable an organization entity for <strong>LDom</strong>s capacity planning
1 In the Veritas <strong>Operations</strong> <strong>Manager</strong> console, click Manage>BusinessEntities.
2 Under BusinessEntities, select the required business entity, and click Actions
> Enable Organization Entity for <strong>Capacity</strong> Planning.

16
Using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
Enabling an organization entity for <strong>LDom</strong>s capacity planning
3 In Enableorganizationentityforcapacityplanning panel, enter the required
information.
See “ Enable organization entity for capacity planning panel options”
on page 16.
4 Click Finish.
After you have marked the organization entity for <strong>LDom</strong> reservation, you
need to reserve space for the required <strong>LDom</strong>s on the servers that are part of
the selected organization entity.
See “Reserving <strong>LDom</strong>s on clusters of an organization entity” on page 17.
See “Disabling an organization entity for <strong>LDom</strong>s capacity planning” on page 17.
Enable organization entity for capacity planning panel options
Use this panel to view and edit the parameters that are required to enable an
organization entity for <strong>LDom</strong>s reservation. You can view VCPU count, and the
allocated memory. The VCPU count and memory determine the computing power
of server, and they are also used as a compliance criteria. You can enter spare
servers per cluster for the organization entity.
Table 2-1
Fields
Enable organization entity for capacity planning panel options
Description
Organization Entity
Displays the name of the organization entity
that you have selected for <strong>LDom</strong>s
reservation.
Specify attributes
VCPU count per server
Memory per server
Displays the number of virtual CPU (VCPU)
counts per server in the organization entity.
Displays the memory allocated per server in
the organization entity.

Using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
Disabling an organization entity for <strong>LDom</strong>s capacity planning
17
Table 2-1
Fields
Enable organization entity for capacity planning panel options
(continued)
Description
Spare Servers per Cluster
Select the number of spare servers per
cluster for the organization entity.
It indicates the allowed number of nodes in
the cluster that can go offline without
affecting the availability of <strong>LDom</strong>s on the
cluster. When any server fails, all the <strong>LDom</strong>s
running on the server can failover on the
spare server.
Since for mission-critical applications, you
need more resilient infrastructure, you can
have more number of spare servers per
cluster. However, in that scenario, you can
configure less number of <strong>LDom</strong>s on the
server.
See “Enabling an organization entity for <strong>LDom</strong>s capacity planning” on page 15.
Disabling an organization entity for <strong>LDom</strong>s capacity
planning
Use this page to disable <strong>LDom</strong> capacity planning for a selected organization entity.
Once disabled, you cannot use the server that is associated with the organization
entity for <strong>LDom</strong> reservation.
To disable an organization entity for <strong>LDom</strong>s capacity planning
1 In the Veritas <strong>Operations</strong> <strong>Manager</strong> console, click Manage>BusinessEntities.
2 Under BusinessEntities, select the required business entity, and click Actions
> Disable Organization Entity for <strong>Capacity</strong> Planning.
3 In Disable capacity planning for Organization Entity panel, click OK to
confirm.
See “Enabling an organization entity for <strong>LDom</strong>s capacity planning” on page 15.
Reserving <strong>LDom</strong>s on clusters of an organization entity
Use this page to reserve <strong>LDom</strong>s on the clusters of the selected organization entity.
You can either use the provided VCPU and memory combinations, or enter custom

18
Using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
Reserving <strong>LDom</strong>s on clusters of an organization entity
values. Based on the <strong>LDom</strong> allocation methodology, you can use one of the
following options:
■
■
Pack: When you use this option, Veritas <strong>Operations</strong> <strong>Manager</strong> attempts to
reserve the <strong>LDom</strong> on the cluster with the maximum resource utilization. It
helps you use the full storage capacity of the current server. After it is
exhausted completely, next available cluster is used for the <strong>LDom</strong> reservation.
Balance: In this option, Veritas <strong>Operations</strong> <strong>Manager</strong> uses all resources evenly.
To reserve <strong>LDom</strong>s on the clusters of an organization entity
1 In the Veritas <strong>Operations</strong> <strong>Manager</strong> console, click Solutions.
2 Under the Server capacity planner for <strong>LDom</strong>s section, click Organization
entities enabled for server capacity planning.
3 In Organization Entities marked for capacity planning section, select the
organization entity, which you want to use for <strong>LDom</strong>s reservation.
4 Click Actions > Reserve <strong>LDom</strong>s.
5 In Reserve <strong>LDom</strong>s on clusters panel, enter the required information.
Note: To delete a reserved <strong>LDom</strong>, or to move it to other clusters, click the
desired <strong>LDom</strong> name under Reserved <strong>LDom</strong>s column, and use appropriate
options.
See “Reserve <strong>LDom</strong>s on clusters panel options” on page 18.
6 Click Finish.
See “Enabling an organization entity for <strong>LDom</strong>s capacity planning” on page 15.
See “Disabling an organization entity for <strong>LDom</strong>s capacity planning” on page 17.
Reserve <strong>LDom</strong>s on clusters panel options
Use this panel to reserve <strong>LDom</strong>s on one or more clusters of a selected organization
entity.
Table 2-2
Fields
Name
Reserve <strong>LDom</strong>s on clusters panel options
Description
Enter the name of the <strong>LDom</strong> that you want
to reserve.

Using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
Reserving <strong>LDom</strong>s on clusters of an organization entity
19
Table 2-2
Fields
Select Size
Reserve <strong>LDom</strong>s on clusters panel options (continued)
Description
Select the <strong>LDom</strong> size. It is the combination
of VCPU count and the allocated memory.
Select the required value from the
drop-down list. Select Custom option to enter
other values of VCPU count and memory.
Reserve
After you have selected VCPU count and
memory, click Reserve to reserve the <strong>LDom</strong>.
You can choose one of the options:
■
■
Pack: In this option, the most loaded
cluster is used first. Once that cluster is
exhausted completely, Veritas <strong>Operations</strong>
<strong>Manager</strong> starts using the next available
cluster for <strong>LDom</strong> reservation.
Balance: In this option, Veritas
<strong>Operations</strong> <strong>Manager</strong> keeps all clusters
equally loaded. In this option, clusters
resources are consumed evenly.
The reserved <strong>LDom</strong>s are displayed under
Reserved <strong>LDom</strong> column.
Cluster
Available <strong>Capacity</strong>
Reserved <strong>LDom</strong>s
Displays all the clusters that belong to the
selected organization entity.
Displays the available capacity of clusters.
Displays the <strong>LDom</strong>s that are already
reserved. You can perform two more
operations on the reserved <strong>LDom</strong>s.
■
■
Delete the <strong>LDom</strong> reservation: Click the
desired <strong>LDom</strong>, and select Delete this
reservation option.
Move the <strong>LDom</strong> to another cluster: Click
the <strong>LDom</strong> and select Move to cluster.
Select the new cluster from the
drop-down list.
Comments
Provide additional information about the
<strong>LDom</strong> space reservation.
See “Reserving <strong>LDom</strong>s on clusters of an organization entity” on page 17.

20
Using <strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
Reserving <strong>LDom</strong>s on clusters of an organization entity

Index
C
Compliance criteria
Memory per server 11
Number of spare servers 11
Number of VCPUs 11
L
<strong>LDom</strong> <strong>Capacity</strong> <strong>Management</strong> <strong>Add</strong>-on
Compliance violations 12
Features 11
Limitations 13
Overview 9
Prerequisites 13
<strong>LDom</strong>s reservation
Balance 18
Pack 18
Logical Domains 10
O
Organization Entity 10
Disable <strong>LDom</strong>s capacity planning 17
Enable <strong>LDom</strong>s capacity planning 15
Reserve <strong>LDom</strong>s 17