Preface
This preface contains the following sections:
•
Audience, page xi
•
Conventions, page xi
•
Related Documentation, page xiii
•
Documentation Feedback, page xiii
•
Obtaining Documentation and Submitting a Service Request, page xiii
Audience
This guide is intended primarily for data center administrators who use Cisco UCS Director and who
have responsibilities and expertise in one or more of the following:
•
Server administration
•
Storage administration
•
Network administration
•
Network security
Conventions
Table 1
Conventions Used in this Document
Text Type
Indication
GUI Elements
GUI elements such as tab titles, area names, and field labels appear in
this font.
Main titles such as window, dialog box, and wizard titles appear in this
font.
Document titles
Document titles appear in this font.
TUI elements
In a Text-based User Interface, text the system displays appears in this
font.
System output
Terminal sessions and information that the system displays appear in
this font.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
xi
Table 1
Conventions Used in this Document
Text Type
Indication
CLI Commands
CLI command keywords appear in this font.
Variables in a CLI command appear in this font.
[]
Elements in square brackets are optional.
{x | y | z}
Required alternative keywords are grouped in braces and separated by
vertical bars.
[x | y | z]
Optional alternative keywords are grouped in brackets and separated by
vertical bars.
string
A nonquoted set of characters. Do not use quotation marks around the
string or the string will include the quotation marks.
<>
Nonprinting characters such as passwords are in angle brackets.
[]
Default responses to system prompts are in square brackets.
!, #
An exclamation point (!) or a pound sign (#) at the beginning of a line
of code indicates a comment line.
Note
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
document.
Tip
Means the following information will help you solve a problem. The tips information might not be
troubleshooting or even an action, but could be useful information, similar to a Timesaver.
Caution
Timesaver
Warning
Means reader be careful. In this situation, you might perform an action that could result in equipment
damage or loss of data.
Means the described action saves time. You can save time by performing the action described in the
paragraph.
IMPORTANT SAFETY INSTRUCTIONS
This warning symbol means danger. You are in a situation that could cause bodily injury. Before you
work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar
with standard practices for preventing accidents. Use the statement number provided at the end of
each warning to locate its translation in the translated safety warnings that accompanied this device.
SAVE THESE INSTRUCTIONS
Cisco UCS Director Administration Guide, Release 4.0
xii
OL-30149-02
Related Documentation
Cisco UCS Director Documentation Roadmap
For a complete list of Cisco UCS Director documentation, see the Cisco UCS Director Documentation
Roadmap available at the following URL:
http://www.cisco.com/en/US/docs/unified_computing/ucs/ucs-director/doc-roadmap/b_UCSDirectorD
ocRoadmap.html
Cisco UCS Documentation Roadmaps
For a complete list of all Cisco UCS B-Series documentation, see the Cisco UCS B-Series Servers
Documentation Roadmap available at the following URL:
http://www.cisco.com/en/US/docs/unified_computing/ucs/overview/guide/UCS_roadmap.html
For a complete list of all Cisco UCS C-Series documentation, see the Cisco UCS C-Series Servers
Documentation Roadmap available at the following URL:
http://www.cisco.com/en/US/docs/unified_computing/ucs/overview/guide/UCS_rack_roadmap.html
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your
comments to [email protected]. We appreciate your feedback.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What's New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation.
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a
free service and Cisco currently supports RSS version 2.0.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
xiii
Cisco UCS Director Administration Guide, Release 4.0
xiv
OL-30149-02
CH A P T E R
1
Overview
This chapter contains the following sections:
•
Information About Cisco UCS Director, page 1-1
•
Physical and Virtual Management Features, page 1-4
•
Physical and Virtual Management Features, page 1-4
•
Recommended Order of System Setup, page 1-6
Information About Cisco UCS Director
Cisco UCS Director (formerly Cisco Cloupia) is a 64-bit appliance that uses the standard OVF template.
Cisco UCS Director delivers unified, highly secure management for leading converged infrastructure
solutions, which are based on the Cisco UCS and Cisco Nexus platforms.
Cisco UCS Director extends the unification of computing and network layers through Cisco UCS to
provide data center administrators with comprehensive visibility and management capability. It supports
NetApp FlexPod and ExpressPOD, EMC VSPEX, and Virtual Computing Environment (VCE) vBlock
systems, based on the Cisco UCS and Cisco Nexus platforms.
Cisco UCS Director automates the provisioning of resource pools across physical, virtual, and
bare-metal environments. It delivers native, automated monitoring for health, status, and resource
utilization. For example, you can do the following tasks using Cisco UCS Director:
•
Create, clone, and deploy service profiles and templates for all servers and applications
•
Monitor organizational usage, trends, and capacity across a converged infrastructure on a continuous
basis, such as by viewing heat maps that show VM utilization across all your data centers
•
Deploy and add capacity to ExpressPod and FlexPod infrastructure in a consistent, repeatable
manner
•
Manage, monitor, and report on Cisco UCS domains and their components
•
Extend virtual service catalogs to include physical infrastructure services
•
Manage secure multitenant environments to accommodate virtualized workloads running alongside
non-virtualized workloads
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
1-1
Chapter 1
Overview
Information About Cisco UCS Director
Features and Benefits
Features
Central management
Benefits
•
Single interface for administrators to
monitor, provision, and manage the system
across physical, virtual, and bare-metal
environments
•
Unified dashboards, reports, and heat maps,
which reduce troubleshooting and
performance bottlenecks
Self-service catalog
•
End users can order and deploy new
infrastructure instances following
IT-prescribed policies and governance.
Adaptive provisioning
•
Real-time available capacity, internal
policies, and application workload
requirements can be used to optimize the
availability of the right resources
Dynamic capacity management
•
Continuous monitoring indicates real-time
infrastructure consumption to improve
capacity planning and managemen
•
Underutilized and overutilized resources are
identified
Multiple hypervisor support
•
Support for VMware ESX, Microsoft
Hyper-V, and Red Hat hypervisors
Computing management
•
Monitors, manages, and provisions physical,
virtual, and bare-metal servers, as well as
blades.
•
End users can implement virtual machine
lifecycle management and business
continuance through snapshots.
•
Administrators can access server utilization
trending analysis.
•
Policy-based provisioning of physical and
virtual switches and dynamic network
topologies
•
Administrators can configure VLANs, virtual
network interface cards (vNICs), port groups
and port profiles, IP and Dynamic Host
Control Protocol (DHCP) allocation, and
access control lists (ACLs) across network
devices.
Network management
Cisco UCS Director Administration Guide, Release 4.0
1-2
OL-30149-02
Chapter 1
Overview
Information About Cisco UCS Director
Features
Storage management
Cisco CloudGenie
Benefits
•
Policy-based provisioning and management
of filers, virtual filers (vFilers), logical unit
numbers (LUNs), and volumes
•
Unified dashboards give administrators
comprehensive visibility into organizational
usage, trends, and capacity analysis details.
•
Mobile management from Apple iPad and
iPhone and Android devices
•
Mobile self-service provisioning, virtual
machine management, and viewing of
administrative dashboards
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
1-3
Chapter 1
Overview
Information About Cisco UCS Director
Physical and Virtual Management Features
Physical Server Management
Virtual Computing Management
•
Discover and collect configurations and
changes
•
Discover, collect, and monitor virtual
computing environments
•
Monitor and manage physical servers
•
•
Perform policy-based server provisioning
Perform policy-based provisioning and
dynamic resource allocation
•
Manage blade power
•
Manage the host server load and power
•
Perform server use trending and capacity
analysis
•
Manage the VM lifecycle and snapshots
•
Perform analytics to assess VM capacity and
sprawl, and host utilization
•
Perform bare-metal provisioning using
preboot execution environment (PXE) boot
management
Physical Storage Management
•
Discover, collect, and monitor storage filers
•
Perform policy-based provisioning of vFilers
•
Provision and map volumes
•
Create and map LUN and iGroup instances
•
Perform SAN zone management
•
Monitor and manage network-attached
storage (NAS) and SAN-based storage
•
Implement storage best practices and
recommendation
Physical Network Management
•
Discover, collect, and monitor physical
network elements
•
Provision VLANs across multiple switches
•
Configure ACLs on network devices
•
Implement dynamic network topologies
Virtual Storage Management
•
Discover, collect, and monitor storage vFilers
and storage pools
•
Perform policy-based storage provisioning
for thick and thin clients
•
Create new data stores and map them to
virtual device contexts (VDCs)
•
Add and resize disks to VMs
•
Monitor and manage organizational storage
use
•
Perform virtual storage trend and capacity
analysis
Virtual Network Management
•
Add networks to VMs
•
Perform policy-based provisioning with IP
and DHCP allocation
•
Configure and connect vNICs to VLANs and
private VLANs
•
Create port groups and port profiles for VMs
•
Monitor organizational use of virtual
networks
Model-Based Orchestration
The turnkey solution in UCSD that allows rapid creation of workflows and templates includes a task
library containing over 400 tasks, as well as out-of-the-box workflows.
Model-based orchestration and a workflow designer enable you to customize and automate infrastructure
administrative and operational tasks. You can extend and customize the system to meet individual needs.
Cisco UCS Director Administration Guide, Release 4.0
1-4
OL-30149-02
Chapter 1
Overview
Initial Login
Included in the task library are Day 1 through Day 3 maintenance and update activities, as shown in the
following table:
Day-1
Day-2
Day-3
•
Add tenants
•
Monitor performance
•
Add/upgrade hardware
•
Migrate or add applications
•
Start metering and billing
•
Repurpose
•
Integrate with enterprise
systems
•
Manage tenant changes
•
Self-service IaaS
•
Use self-service portal
Initial Login
Log in to Cisco UCS Director by hostname or IP address with the following credentials:
•
Username: admin
•
Password: admin
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
1-5
Chapter 1
Overview
Recommended Order of System Setup
Note
We recommend that you delete the startup admin account after you create the first admin account or, at
least, change the default password. To access the self-service portal, you must have a valid email address.
Recommended Order of System Setup
Name
Chapter
Description
Initial Set Up
2, 3, and 4
These steps are required after Cisco UCS Director installation
and initial login. In these chapters you are shown how to apply
a license, set up the Admin profile, create groups, and create
users. You will learn how to access language support, apply
portal customization, and system settings.
Physical Infrastructure
This chapter describes how to optionally add a data center, a
physical account, add network elements, test the connections,
and verify account discovery.
Note
You can create the virtual infrastructure before the
physical infrastructure if you want.
Virtual Infrastructure
5
This chapter describes how to create a cloud, verify cloud
discovery and connectivity, test the connections, and view
vCenter plug ins.
Policies
6
This chapter describes how to create and manage computing
policies, storage policies, network policies, and system
policies. You will also be shown how to add OS licenses for
Microsoft Windows catalogs.
Virtual Data Centers
7
This chapter describes how to set up vDCs to manage specific
environments for groups. policies, and cost models, and how
resource limits are configured and managed at the vDC level.
Catalogs
8
This chapter describes how to set up catalog items, attach
groups with access to a catalog, and publish catalog items.
Self-Service
Provisioning
9
This chapter covers how you can create and manage
provisioning service requests.
Multi-Disk
Provisioning
10
This chapter describes how to configure VM disk provisioning
on a preferred single datastore or multiple datastores. It also
provides instructions on how to configure individual disk
policies for each additional disk in a template.
Chargeback
11
This chapter describes how to create chargeback summary
reports, detailed reports, and resource accounting reports. It
shows how cost models are defined and assigned to policies
within departments and organizations.
Cloud Management
12
This chapter describes how you can get complete cloud
visibility, monitor resource usage, and manage the cloud
stack—clouds, clusters, host servers, and virtual machines.
Life Cycles
13
Administrators can perform post provisioning life cycle
management actions on VMs. Such as VM power
management, VM resizing, VM snapshot management, and
other VM actions.
Cisco UCS Director Administration Guide, Release 4.0
1-6
OL-30149-02
Chapter 1
Overview
Recommended Order of System Setup
Name
Chapter
Description
CloudSense
14
This chapter describes the analytical reports about the
underlying physical and virtual infrastructure that Cisco UCS
Director can generate.
Macros
15
This chapter describes how to use the Macros feature to
customize VM names and VM hostnames using variables
provided by the application.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
1-7
Chapter 1
Overview
Recommended Order of System Setup
Cisco UCS Director Administration Guide, Release 4.0
1-8
OL-30149-02
CH A P T E R
2
Managing Users and Groups
This chapter contains the following sections:
Note
•
Managing User Types, page 2-1
•
Administration Profile, page 2-7
•
Managing User Access Profiles, page 2-9
•
Managing Groups, page 2-11
•
Authentication and LDAP Integration, page 2-15
•
Branding, page 2-19
You must be logged in to the appliance before you can run any of the following procedures.
Managing User Types
As the system administrator, you have full privileges to manage Cisco UCS Director, including adding
users, viewing users and user permissions, and modifying individual user read/write permissions for
different system components.
Most users will view and use the Administrative Portal when they log in, which is described in this guide.
User Types
Cisco UCS Director supports a number of user types:
•
All Policy Admin
•
Billing Admin
•
Computing Admin
•
Group Admin - An end user with the privilege of adding users. This user can use the Self-Service
Portal.
•
IS Admin
•
Network Admin
•
Operator
•
Service End User - This user only views and uses the Self-Service Portal.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
2-1
Chapter 2
Managing Users and Groups
Managing User Types
•
Storage Admin
•
System Admin
Default User Permissions
Each user type has a default set of system permissions.
All Policy Admin
Task
Permission
Computing Clouds
Read-only
Storage Clouds
Read-only
Network Clouds
Read-only
Group Service Request
Read/write
Approver Service Request
Read/write
Chargeback
Read-only
Catalog
Read-only
vDC
Read-only
Computing Policy
Read/write
Storage Policy
Read/write
Network Policy
Read/write
Service Delivery Policies
Read/write
System Admin
Read-only
Users and Groups
Read-only
Budgeting
Read-only
Cloud Accounts
Read-only
Resource Accounting
Read-only
Resource Limit Report
Read-only
Group Users
Read-only
Task
Permission
Computing Clouds
Read-only
Storage Clouds
Read-only
Network Clouds
Read-only
Group Service Request
Read-only
Approver Service Request
Read/write
Chargeback
Read-only
Catalog
Read-only
Billing Admin
vDC
Read-only
Computing Policy
Read-only
Cisco UCS Director Administration Guide, Release 4.0
2-2
OL-30149-02
Chapter 2
Managing Users and Groups
Managing User Types
Task
Permission
Storage Policy
Read-only
Network Policy
Read/write
Service Delivery Policies
Read-only
System Admin
Read-only
Users and Groups
Read-only
Budgeting
Read-only
Cloud Accounts
Read-only
Resource Accounting
Read-only
Resource Limit Report
Read-only
Group Users
Read-only
Task
Permission
Computing Clouds
Read-only
Storage Clouds
Read-only
Computing Admin
Network Clouds
Read-only
Computing Infrastructure
Read/write
Group Service Request
Read-only
Approver Service Request
Read/write
Chargeback
Read-only
Catalog
Read-only
vDC
Read-only
Computing Policy
Read/write
Storage Policy
Read-only
Network Policy
Read-only
Service Delivery Policies
Read-only
System Admin
Read-only
Users and Groups
Read-only
Budgeting
Read-only
Cloud Accounts
Read-only
Resource Accounting
Read-only
Resource Limit Report
Read-only
Group Users
Read-only
Task
Permission
Computing
Cloud write only
Group Service Request
Read/write
Approver Service Request
Read/write
Group Admin
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
2-3
Chapter 2
Managing Users and Groups
Managing User Types
Task
Permission
Chargeback
Read-only
Catalogs
Read-only
vDC
Read-only
Resource accounting
Read-only
Resource limit report
Ready only.
VM label
Write only.
Group users
Read/write
Task
Permission
IS Admin
Computing Clouds
Read-only
Storage Clouds
Read-only
Network Clouds
Read-only
Computing Infrastructure
Read-only
Group Service Request
Read-only
Approver Service Request
Read/write
Chargeback
Read-only
Catalog
Read/write
vDC
Read/write
Computing Policy
Read-only
Storage Policy
Read-only
Network Policy
Read-only
Service Delivery Policies
Read/write
System Admin
Read-only
Users and Groups
Read-only
Budgeting
Read-only
Cloud Accounts
Read-only
Resource Accounting
Read-only
Resource Limit Report
Read-only
Group Users
Read-only
Cisco UCS Director Administration Guide, Release 4.0
2-4
OL-30149-02
Chapter 2
Managing Users and Groups
Managing User Types
Network Admin
Task
Permission
Computing Clouds
Read-only
Storage Clouds
Read-only
Network Clouds
Read-only
Group Service Request
Read-only
Approver Service Request
Read/write
Chargeback
Read-only
Catalog
Read-only
vDC
Read-only
Computing Policy
Read-only
Storage Policy
Read-only
Network Policy
Read/write
Service Delivery Policies
Read-only
System Admin
Read-only
Users and Groups
Read-only
Budgeting
Read-only
Cloud Accounts
Read-only
Resource Accounting
Read-only
Resource Limit Report
Read-only
Group Users
Read-only
Task
Permission
Computing Clouds
Read-only
Storage Clouds
Read-only
Operator
Network Clouds
Read-only
Group Service Request
Read/write
Approver Service Request
Read/write
Chargeback
Read-only
Catalog
Read-only
vDC
Read-only
Computing Policy
Read-only
Storage Policy
Read-only
Network Policy
Read-only
Service Delivery Policies
Read-only
System Admin
Read-only
Users and Groups
Read-only
Budgeting
Read-only
Cloud Accounts
Read-only
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
2-5
Chapter 2
Managing Users and Groups
Managing User Types
Task
Permission
Resource Accounting
Read-only
Resource Limit Report
Read-only
Group Users
Read-only
Task
Permission
Computing Cloud
Write-only
Group Service Request
Read/write
Approver Service Request
Read/write
Chargeback
Read-only
Service End User
Catalogs
Read-only
vDC
Read-only
Resource accounting
Read-only
Resource limit report
Read-only
Task
Permission
Computing Clouds
Read-only
Storage Clouds
Read-only
Network Clouds
Read-only
Storage Admin
Group Service Request
Read-only
Approver Service Request
Read/write
Chargeback
Read-only
Catalog
Read-only
vDC
Read-only
Computing Policy
Read-only
Storage Policy
Read/write
Network Policy
Read-only
Service Delivery Policies
Read-only
System Admin
Read-only
Users and Groups
Read-only
Budgeting
Read-only
Cloud Accounts
Read-only
Resource Accounting
Read-only
Resource Limit Report
Read-only
Group Users
Read-only
Cisco UCS Director Administration Guide, Release 4.0
2-6
OL-30149-02
Chapter 2
Managing Users and Groups
Administration Profile
System Admin
Task
Permission
Computing Clouds
Read/write
Storage Clouds
Read/write
Network Clouds
Read/write
Group Service Request
Read/write
Approver Service Request
Read/write
Chargeback
Read-only
Catalog
Read/write
vDC
Read/write
Computing Policy
Read/write
Storage Policy
Read/write
Network Policy
Read/write
Service Delivery Policies
Read/write
System Admin
Read/write
Users and Groups
Read/write
Budgeting
Read/write
Cloud Accounts
Read/write
Resource Accounting
Read-only
Resource Limit Report
Read-only
Resource Limit
Write-only
Group Users
Read-only
Administration Profile
You must first configure your system administrator profile before you can configure groups and their
users.
Creating the admin Profile
Step 1
Click Administration > Users and Groups.
Step 2
Choose the Login Users tab.
Step 3
Click Add.
Step 4
In the Add User dialog box,complete the following fields:
Name
Description
User Type drop-down list
Choose the administrator’s user type. The system administrator has
full privileges.
User Group drop-down list
Choose the administrator’s user group.
Login Name field
The login name. The default is admin.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
2-7
Chapter 2
Managing Users and Groups
Administration Profile
Name
Description
Password field
Enter the admin password.
Confirm Password field
Enter the admin password again to confirm it.
User Contact Email field
The administrator’s email address.
First Name field
The administrator’s first name.
Last Name field
The administrator’s last name.
Phone field
The administrator’s phone number.
Address field
The administrator’s address.
Changing the admin Password
Step 1
Click Administration > Users and Groups.
Step 2
Choose the Login Users tab.
Step 3
In the Login Name column, choose admin.
Step 4
Click Change Password.
Step 5
In the Change Password dialog box, enter a new password for the admin user and confirm it.
Step 6
Click Save.
Step 7
In the Add User dialog box, complete the following fields:
What to Do Next
Configure groups and customer organizations.
Adding Users
Before You Begin
Create the group to which the user will belong.
Step 1
Click Administration > Users and Groups.
Step 2
Choose the Login Users tab.
Step 3
Click Add (+).
Step 4
In the Add User dialog box, complete the following fields:
Name
Description
User Type drop-down list
Choose the user type.
User Group drop-down list Choose the group or customer organization to which the user belongs.
Login Name field
The user's login name.
Cisco UCS Director Administration Guide, Release 4.0
2-8
OL-30149-02
Chapter 2
Managing Users and Groups
Managing User Access Profiles
Name
Description
Password field
The user's password.
Note
If the Lightweight Directory Access Protocol (LDAP) authentication is
configured for the user, the password is validated only at the LDAP
server, not at the local server.
Confirm Password field
Confirm the user password.
User Contact Email field
The user's email address.
Note
The email address is used to notify the group owner about service request
status and to request approvals.
First Name field
The user's first name.
Last Name field
The user's last name.
Phone field
The user's phone number.
Address field
The user's address.
Step 5
Click Add.
What to Do Next
After choosing a user from the main page and then clicking Manage Profiles, you can optionally assign
multiple roles for that user.
Viewing Current Online Users
Step 1
Click Administration > Users and Groups.
Step 2
Choose the Current Online Users tab to view online user details.You can view the user name, IP
address, session start time, last data access, and client.
Managing User Access Profiles
Multi-Role Access Profiles
A user can be assigned to more than one role, which is reflected in the system as a user access profile.
For example, a user might log into Cisco UCS Director as a group administrator and an all-policy
administrator, if both types of access are appropriate.
Note
One of the profiles can be set as the default user access profile.
Note
The Manage Profiles feature enables you to add, log into, edit, or delete a user access profile.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
2-9
Chapter 2
Managing Users and Groups
Managing User Access Profiles
Creating a User Access Profile
Step 1
Click Administration > Users and Groups.
Step 2
Choose the Login Users tab.
Step 3
Choose a user from the list.
Step 4
Click Manage Profiles.
Step 5
In the Manage Profiles page, click Add (+).
Step 6
In the Add Entry to Access Profiles dialog box, complete the following fields:
Name
Description
Name field
The profile name.
Description field
The description of the profile.
Type drop-down list
Choose the user role type.
Group drop-down list
Choose the user’s group.
Default Profile check
box
Check the check box if this is the default user access profile. Uncheck the check box
if it is not the default.
Step 7
Click Submit.
What to Do Next
Create additional user access profiles as needed.
Editing A User Access Profile
Step 1
Click Administration > Users and Groups.
Step 2
Choose the Login Users tab.
Step 3
Choose a user from the list.
Step 4
Click Manage Profiles.
Step 5
In the Manage Profiles page, choose a user from the list.
Step 6
Click Edit.
Step 7
In the Edit Access Profiles Entry dialog box, edit the Name, Description, Type, Group, or the Default
Profile fields, as needed.
Step 8
Click Submit.
Deleting a User Access Profile
Step 1
Click Administration > Users and Groups.
Cisco UCS Director Administration Guide, Release 4.0
2-10
OL-30149-02
Chapter 2
Managing Users and Groups
Managing Groups
Step 2
Choose the Login Users tab.
Step 3
Choose a user from the list.
Step 4
Click Manage Profiles.
Step 5
In the Manage Profiles page, choose a user from the list.
Step 6
In the Manage Profiles dialog box, click Delete.
Logging in to a Profile
Step 1
In the Cisco UCS Director login dialog box, in the Username field, enter your username in the format
Username:Access Profile Name.
Note
For example, Alex:GrpAdmin
Step 2
In the Password field, enter your password.
Step 3
Click Login.
Default Profile
The default profile is the first profile that you created in the system. You can change the default to
another profile. Using the new default profile, you log in by entering the username and password.
Changing the Default Profile
Step 1
At the upper right of the page (to the left of logout), click the user name.
Step 2
In the User Information page, click the Access Profiles tab.
Step 3
Choose a user profile, and click Set as Default Profile.
Note
A profile can also be set as default while adding or editing a profile.
Managing Groups
Creating a Group or Customer Organization
Step 1
Click Administration > Users and Groups.
Step 2
Choose the User Groups tab.
Step 3
Click Add.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
2-11
Chapter 2
Managing Users and Groups
Managing Groups
Step 4
In the Add Group dialog box, complete the following fields:
Name
Description
Name field
The a name of the group/customer organization.
Description
field
The description of the group/customer organization if required.
Code field
Enter a shorter name or code name for the group. This name is used in VM and hostname
templates.
Cost Center
field
(Optional) The cost center name or number if required. This name or number represents a cost
center a group is associated with. This name can be used in a VMware System policy for the
VM naming convention.
Note
For more information about using Cost Center for naming conventions, see Chapter
6 “Managing Policies”.
Contact Email
field
The contact email address. This email is used to notify the group owner about the status of
service requests and request approvals if necessary.
First Name
field
The contact’s first name.
Last Name
field
The contact’s last name.
Phone field
The contact’s phone number.
Address field
The contact’s address.
Step 5
Click Add.
What to Do Next
Repeat this procedure if you want to add more groups.
Group Password Policy
The password policy for a group is enforced when you add a user or change the password for all user
types. This policy enables the following password constraints:
•
Password length
•
Whether the password can be the same as the username
•
Whether a user can reset the current password as a new password
•
Regular expressions that are disallowed in a password.
Creating A Password Policy
Step 1
Click Administration > Users and Groups.
Step 2
Choose the Password Policy tab.
Cisco UCS Director Administration Guide, Release 4.0
2-12
OL-30149-02
Chapter 2
Managing Users and Groups
Managing Groups
Step 3
In the Password Policy pane, complete the following fields:
Name
Description
Minimum Password Length
drop-down list
Choose the minimum number of characters for the password.
Maximum Password Length
drop-down list
Choose the maximum number of characters for the password.
Minimum Character Classes
drop-down list
Choose the minimum number of character classes such as upper case, lower
case, numbers, and special characters.
Disallow Login in Password
check box
Check the check box to disallow passwords, which are the same as the login
ID.
Disallow Previous Password
check box
Check the check box to disallow a change of passwords.
Disallow Passwords that match
regular expression field
The regular expressions (one per line) that are not allowed for passwords.
For example, .*abc.* specifies that a given password cannot contain the
string “abc”.
Step 4
Click Submit.
Group Budget Policy
Resources are accounted for by using the Chargeback feature. For resource usage by a group or customer
organization, you associate the entity with a budget policy.
You can configure a group or customer organization with a budget watch, as well as configure a group
or customer organization to stay within or exceed the provisioned budget.
Viewing and Editing a Group Budget Policy
Step 1
Click Administration > Users and Groups.
Step 2
Choose the User Groups tab.
Step 3
Choose a group from the list.
Step 4
Click Budget Policy.
Step 5
In the Budget Policy dialog box, complete the following fields:
Name
Description
Enable Budget Watch
check box
Check the check box to monitor the groups budget usage. Uncheck the check box to
ignore all budget entries for this group.
Allow Over Budget
check box
Check if the group members are allowed over the provisioned budget. Uncheck the
check box to reject all requests, once the budget is exhausted, until a new budget is
added.
Step 6
Click Save.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
2-13
Chapter 2
Managing Users and Groups
Managing Groups
Resource Limits
You can configure resource limits for a group or customer organization to help manage group resource
utilization. You can specify limits on the following:
•
Virtual resources
•
Operating system resources
•
Physical resources
Viewing Resource Limits
Step 1
Click Organizations > Summary.
Step 2
Click a group to view.
Step 3
Click the Resource Limits tab to view the current limit, usage, pending SR usage, and status of the
resources for the selected group.
Editing Resource Limits
Step 1
Click Administration > Users and Groups.
Step 2
Choose the User Groups tab.
Step 3
Choose a group and click Edit Resource Limits.
Step 4
In the Resource Limit dialog box appears.
Step 5
In the Resource Limit dialog box, check the Enable Resource Limits check box and complete the
following fields:
Name
Description
Group display-only field
The group name.
Enable Resource Limits check box
Check the check box to enable the resource limits, uncheck the
check box to disable the resource limits. If checked the user is
provided with the option to set resource limits for a group and all
nonzero resource limits are applied.
Maximum Active VM Count field
The maximum number of active VMs.
Maximum Total VM Count field
The total number of VMs.
Provisioned vCPUs Limit field
The maximum number of provisioned vCPUs.
Provisioned Memory (GB) Limit field
The provisioned CPU limit, in gigahertz.
Provisioned CPU (GHz) Limit field
The provisioned memory limit, in gigabytes.
Provisioned Disk (GB) Limit field
The provisioned limit for disks, in gigabytes.
Reserved CPU (GHz) Limit field
The reserved limit of CPUs, in gigahertz.
Reserved Memory (GB) Limit field
The reserved memory limit, in gigabytes
Maximum Snapshot (GB) Limit field
The maximum limit for snapshots, in gigabytes.
Cisco UCS Director Administration Guide, Release 4.0
2-14
OL-30149-02
Chapter 2
Managing Users and Groups
Authentication and LDAP Integration
Name
Description
Count CPU and Memory for Inactive
VMs check box
Check the checkbox to include the group's inactive VM CPU or
memory data in the computation of resource limits. Uncheck the
check box to exclude inactive VMCPU or memory data from the
computation of resource limits.
OS Resource Limits
CentOS field
The maximum number of CentOS (Community Enterprise
Operating System) servers.
Windows Server 2003 field
The maximum number of Windows 2003 servers.
Windows Server 2008 field
The maximum number of Windows 2008 servers.
Windows 7 field
The maximum number of Windows 7 machines.
Windows XP field
The maximum number of Windows XP machines.
Red Hat field
The maximum number of Red Hat machines.
Ubuntu field
The maximum number of Ubuntu machines.
FreeBSD field
The maximum number of FreeBSD machines.
Other Linux field
The maximum number of other Linux OS.
Other field
The maximum number of other OS.
Physical Resource Limits
Maximum Physical Server Count field
The maximum number of servers.
Maximum Physical Server Memory (GB) The maximum amount of server memory.
field
Maximum Physical Server CPU Count
field
The maximum number of server CPUs.
Maximum vFiler Count field
The maximum number of vFilers.
Maximum Physical Storage Space (GB)
field
The maximum amount of storage space.
Step 6
Click Save.
Authentication and LDAP Integration
You can configure a preference with or without a fallback choice for local authentication and a
preference with a fallback for the LDAP. You can also configure a preference with no fallback for
Verisign Identity Protection (VIP) authentication.
Name
Description
Local Authentication
Authentication is local only (Cisco UCS Director), and not through the
LDAP server.
Local First, fallback to LDAP
drop-down list option
Authentication is done first at the local server (Cisco UCS Director). If the
user is unavailable at the local server, the LDAP server is checked.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
2-15
Chapter 2
Managing Users and Groups
Authentication and LDAP Integration
Name
Description
LDAP First, fallback to Local
drop-down list option
Authentication is done first at the LDAP server. If the user is unavailable at
the LDAP server, the local server is checked (Cisco UCS Director).
Verisign Identity Protection
drop-down list option
VIP Authentication Service (two-factor authentication) is enabled.
Configuring Authentication Preferences
Step 1
Click Administration > Users and Groups.
Step 2
Choose the Authentication Preferences tab.
Step 3
In the Authentication Preferences pane, complete the following fields:
Name
Description
Authentication Preferences
drop-down list
Choose the Authentication Preference.
If you chose Local Authentication, continue to Step 4.
If you chose VIP, continue to Step 5.
User Name field
The user name.
Password field
The user password.
Port Number field
The port number.
Server field
The IP address of the server.
Domain Name field
The domain name.
LDAP Sync Interval drop-down
list
Choose the LDAP synchronization interval.
Enable LDAP Sync check box
Check the check box if you want to enable LDAP synchronization. Uncheck
the check box if you do not want LDAP synchronization.
Modify Existing Users and
Groups check box
Check the check box if you want to enable modification of existing users and
groups.
Test LDAP
Check the check box if you want to test LDAP connectivity to Cisco UCS
Director.
Step 4
(Optional) For local authentication, click Save.
Step 5
(Optional) In the VIP Certificate field, browse to the VIP Certificate file and choose it.
Step 6
Enter the Password.
Step 7
Click Save.
What to Do Next
If you configured LDAP first as the authentication preference, you must configure the LDAP credentials.
Cisco UCS Director Administration Guide, Release 4.0
2-16
OL-30149-02
Chapter 2
Managing Users and Groups
Authentication and LDAP Integration
LDAP Integration
You can use LDAP integration to synchronize the LDAP server’s groups and users with Cisco UCS
Director. LDAP authentication enables synchronized users to authenticate with the LDAP server. You
can synchronize LDAP users and groups automatically or manually.
Note
Users that do not belong to a group or a domain users group display in LDAP as Users with No Group.
These users are added under the domain users group in Cisco UCS Director.
You cannot choose users and groups that exist locally or are synchronized externally in Cisco UCS
Director.
LDAP Integration Rules and Limitations
Group Synchronization Rules
•
If a chosen LDAP group already exists in Cisco UCS Director and the source is type Local, the
group is ignored during synchronization.
•
If a chosen LDAP group already exists in Cisco UCS Director and the group source is type External,
the group’s description and email attributes are updated in the Cisco UCS Director.
•
A maximum of 1000 Users (subject to availability) are displayed for selection in manual search
when you use the advanced search option. This option is available by clicking Request Manual
LDAP Sync.
User Synchronization Rules
•
If a chosen LDAP user already exists in Cisco UCS Director and the source is type Local, the user
is ignored during synchronization.
•
If a chosen LDAP user already exists in Cisco UCS Director and the source type is External, the
user’s name, description, email, and other attributes are updated for the user.
User Synchronization Limitations
•
A user password cannot be retrieved from the LDAP server. Instead, a random password is generated
for the user during LDAP synchronization.
•
If a user has multiple group membership, that user has single group membership in Cisco UCS
Director.
Note
Be sure that the user is assigned to the correct group after the LDAP synchronization process.
Note
Cisco UCS Director currently supports a single domain.
Managing LDAP Integration
Step 1
Click Administration > Users and Groups.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
2-17
Chapter 2
Managing Users and Groups
Authentication and LDAP Integration
Step 2
Choose the LDAP Integration tab to view the status of LDAP server synchronization.
Step 3
(Optional) Choose a server and click the following buttons, as needed, to manage LDAP integration:
Name
Description
Search BaseDN button
Enables you to choose a distinguished domain name to search. All users and groups
from the chosen organization units are fetched into Cisco UCS Director when the
Enable LDAP Sync check box is checked in the Authentication Preferences tab. This
action is also considered to be an automatic sync process.
Request LDAP Sync
Enables on-demand synchronization of the LDAP server. This
action syncs the
users/groups from the selected organization in “Search Base DN”. Groups
and users added from LDAP appear as type External. Groups and users added by
Cisco UCS Director appear as type Local.
Click Submit to synchronize the server.
LDAP user changes are immediately reflected.
Note
Make sure that the user is assigned to the correct group after the LDAP Sync
is processed.
Continue to Step 4.
Request Manual LDAP
Sync
Displays a dialog box that enables you to specify either basic or advanced search
criteria to fetch LDAP users and groups.
Continue with Step 6.
Step 4
(Optional) For LDAP synchronization request, verify the IP address/domain name, and click Submit.
Step 5
(Optional) If you chose LDAP Manual Server Sync, complete the following fields:
Name
Description
Basic Search field
Check the check box to enable Basic Search by organization unit.
If checked, continue to Step 6.
Advanced Search field
Check the check box to enable Advanced Search.
If checked, continue to Step 8.
Step 6
For basic search, click Select.
Step 7
Choose the distinguished name to search, and click Select.
Step 8
For advanced search, in the Select Users and Groups pane, add or edit attribute names for User Filters
and Group Filters.
Step 9
Click Next.
Step 10
Choose the LDAP Groups and LDAP Users.
Step 11
Click Submit to synchronize the LDAP server.
Single Sign-On
Cisco UCS Director provides a single sign-on using One Login. Single sign-on prevents a user from
having to enter a password multiple times to access the application.
When Single Login is enabled, a user can log into that portal to access Cisco UCS Director.
Cisco UCS Director Administration Guide, Release 4.0
2-18
OL-30149-02
Chapter 2
Managing Users and Groups
Branding
Note
A single sign-on is available for Cisco UCS Director after you register a One Login certificate.
Enabling a Single Sign-On
Step 1
Click Administration > Users and Groups.
Step 2
Click the Single Sign-On tab.
Step 3
In the Single Sign-On pane, check the Enable Single Sign On check box.
Step 4
In the Select a File for Upload field, browse to the One Login certificate file and choose it.
Step 5
Click Upload.
Step 6
When the upload is complete, click Submit.
Branding
For a group or customer organization, the branding options are as follows:
•
Logo image in PNG, JPG, or GIF format
•
Customized application labels
•
URL to forward the Self-Service Portal to upon logout
•
Custom links with labels and URLs specified
•
Login page background and logo.
Branding Groups and Customer Organizations
Step 1
Click Administration > Users and Groups.
Step 2
Choose the User Groups tab.
Step 3
Choose the group to brand.
Step 4
Click Branding.
Step 5
In the Group Branding dialog box, complete the following fields: check the Logo Image check box and
Name
Description
Logo image check box
Check the check box to upload a logo image.
Continue to Step 6.
Application Labels check box
Check the check box to customize an application
label to appear in the application header.
Continue to Step 8.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
2-19
Chapter 2
Managing Users and Groups
Branding
URL Forwarding on Logout check box
Check the check box to forward to a specific URL
upon logout.
Continue to Step 9.
Custom Links check box
Check the check box to brand custom links.
Continue to Step 10.
Step 6
In the Select a File for Upload field, browse to the logo image file and choose it.
Note
Make sure that the logo image is in PNG, JPG, or GIF format. The optimal image size is 200
pixels in width and 100 pixels in height. We recommend that you use a small file size to enable
faster download.
Step 7
Click Upload.
Step 8
(Optional) For application labels, enter at least one application label in the Label 1 and Label 2 fields.
Step 9
(Optional) In the URL field, enter the URL to direct the user to upon logout.
Step 10
(Optional) Complete at least the first two fields:
Name
Description
Custom Link 1 Label field
Enter the label for custom link 1.
Custom Link 1 URL field
Enter the URL for custom link 1.
Custom Link 2 Label field
Enter the label for custom link 2.
Custom Link 2 URL field
Enter the URL for custom link 2.
Step 11
Click Submit.
Login Page Branding
A login page can be configured to display a logo that is associated with a domain name. When the end
user logs in from that domain, the user sees the custom logo on the login page. The optimal image size
for a logo is 890 pixels wide and 470 pixels high, with 255 pixels allowed for white space. We
recommend that you keep the image size small to enable faster downloads.
Note
The group or customer organization login page must first be configured (enabled) for branding.
Configuring a Custom Domain Logo
Step 1
Click Administration > Users and Groups.
Step 2
Choose the Login Page Branding tab.
Step 3
Click Add.
Cisco UCS Director Administration Guide, Release 4.0
2-20
OL-30149-02
Chapter 2
Managing Users and Groups
Branding
Step 4
In the Domain Branding dialog box, complete the following fields:
Name
Description
Domain Name field
Enter the domain name to brand.
Custom Domain Logo check box Check the check box to enable login page branding from a specified domain
name.
Select a file for upload field
Upload the logo file.
Note
Step 5
The optimal image size for a logo is 890 pixels wide by 470 pixels
high, with 255 pixels for white space. We recommend that you keep
the image size small to enable faster downloads.
Click Submit.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
2-21
Chapter 2
Managing Users and Groups
Branding
Cisco UCS Director Administration Guide, Release 4.0
2-22
OL-30149-02
CH A P T E R
3
Managing System Administration Settings
This chapter contains the following sections:
Note
•
Outgoing Mail Server, page 3-1
•
Configure System Parameters (Optional), page 3-2
•
Verifying License Utilization, page 3-3
•
Edit Application Categories, page 3-4
•
Portal Customization, page 3-5
•
Support Information, page 3-7
•
Advanced Configuration Properties, page 3-8
•
User Menus, page 3-9
•
User Permissions, page 3-9
•
System Tasks, page 3-10
•
Customizing Reports, page 3-10
•
Managing Icons, page 3-11
You must be logged in to the appliance before you can run any of the following procedures.
Outgoing Mail Server
All outgoing emails from Cisco UCS Director require an SMTP server.
Setting up the Outgoing Mail Server
Step 1
Click Administration > System Administration.
Step 2
Choose the Mail Setup tab.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
3-1
Chapter 3
Managing System Administration Settings
Configure System Parameters (Optional)
Step 3
In the Mail Setup pane, complete the following fields:
Name
Description
Outgoing Email Server (SMTP)
field
The outgoing SMTP server address.
Outgoing SMTP Port field
The outgoing SMTP server port number.
Outgoing SMTP User field
The user ID.
Outgoing SMTP Password field
The user password.
Outgoing Email Sender Email
Address field
The sender’s email address.
Cloupia Server IP address field
The IP address or DNS name of the Cisco UCS Director virtual appliance.
This field is used to create proper links in emails for user workflow actions.
Send Test Email check box
Check this check box to test the current email settings.
Step 4
Click Save.
Configure System Parameters (Optional)
Configuring System Parameters (Optional)
This procedure is optional. You should edit the system parameters only if you need to change the
defaults.
Step 1
Click Administration > System Administration.
Step 2
Choose the System Parameters tab.
Step 3
In the System Parameters pane, complete the following fields:
Name
Description
Cloud Polling Interval
field
The frequency (in minutes) at which all clouds added to Cisco UCS Director are
polled for status information.
Note
Once a cloud is added, all the inventory details are gathered.
Note
A polling event can be initiated immediately through the Polling tab at the
cloud level.
Number of Days to
The user defined number of days that the system retains VM data.
Keep Deleted VMs Data
field
Number of Days to
Keep Events field
Number of Days to
Keep Trend Data field
The user defined number of days that the system retains all events.
Note
Events older than the mentioned time period are deleted.
The user defined number of days that the system retains trend data or historical data
of the inventory (such as CPU, storage, and memory usage).
Note
This data is used for reporting.
Cisco UCS Director Administration Guide, Release 4.0
3-2
OL-30149-02
Chapter 3
Managing System Administration Settings
Verifying License Utilization
Name
Description
Number of Days to
Keep Metering Data
drop-down list
Choose the number of days that the system retains VM metering records.
Note
This data is specific to VMs and their resources.
Download VM Locking VM locking controls from the specified URL.
Controls from URL
Note
The file must be in XML format.
field
Currency drop-down
list
Choose the type of currency to use. Available currencies are US, EURO, GBP, KRW,
CAD, CHF, CLP, NR, JPY, AUD, NZD, SGD, HKD, MYR, MXN, BRL, AED, DKK,
SEK, KWD, CYN, RUB, ZAR, and Other.
Other Currency field
This field appears when Other is chosen under Currency. Enter the currency name
(one only).
Currency Precision
drop-down list
Choose the currency precision in decimal points. Available precision is from 0 to 5
decimal points.
Step 4
Click Save.
Verifying License Utilization
The License Utilization page shows the licenses in use, and details about each license, including license
limit, available quantity, status, and remarks.
You can run license audits and update PAK licenses.
Step 1
Click Administration > System Administration.
Step 2
Choose the License Utilization tab.
Step 3
Choose a Cisco UCS Director (CUIC) appliance.
Step 4
(Optional) To run a license audit, click Run License Audit.
Step 5
In the Run License Audit dialog box, click Submit. It will take several minutes to run.
Step 6
(Optional) To update a PAK license, click Update License.
Step 7
In the Update PAK license dialog box, complete one of the following fields:
Name
Description
Select a file for upload field
Browse to and upload the PAK license file for this account.
Enter license text field
If you did not upload the license file, check the checkbox. In the License
Text field, copy and paste the license text.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
3-3
Chapter 3
Managing System Administration Settings
Edit Application Categories
Edit Application Categories
Any VM provisioned using Cisco UCS Director is categorized based on its type. This could be a web
server, database, application server, and other VM types. Cisco UCS Director also has a separate
category for discovered VMs.
There are twelve application categories for you to use or edit:
•
Discovered VM
•
Generic VM
•
Web Server
•
Application Server
•
Database
•
App - CPU Intensive
•
App - Memory Intensive
•
App - Disk Intensive
•
App - Network Intensive
•
Other App 1
•
Other App 2
•
Other App 3
Editing Application Categories
Step 1
Click Administration > System Administration.
Step 2
Choose the Application Categories tab.
Step 3
Choose an Application Category.
Step 4
Click Edit.
Step 5
In the Edit Category dialog box, complete the following fields..
Name
Description
Category ID display-only field
The numerical value given to the category by the system,
Category Label field
Defines the category type.
Category Code field
Used in VM and host naming.
Description display-only field
A description of the category.
Category Enabled display-only
check box
The check box default is checked.
Default Smart Allocation
Algorithm drop-down list
Choose an algorithm.
Step 6
Click Submit.
Cisco UCS Director Administration Guide, Release 4.0
3-4
OL-30149-02
Chapter 3
Managing System Administration Settings
Portal Customization
Portal Customization
Organizations can customize self-service portals. The logo, login page, home page, and so on can be
customized for branding and user interface-related changes.
Customizing the Login Page and Background Images
The login page and background images can be changed by uploading custom images.
Step 1
Click Administration > User Interface Settings.
Step 2
Click Login Page.
Step 3
Check the Use customizable Login page check box.
Step 4
In the Logo Images and Background Images pane, choose an item from one or both panes.
Step 5
Click Submit.
Customizing the Application Logo
The application logo on the home page can be customized by uploading a custom image.
Step 1
Click Administration > User Interface Settings.
Step 2
Choose the Application Logo tab.
Step 3
In the Images pane, choose the image, or click Add to add a new image not listed.
Step 4
Click Submit.
Customizing Favicons
You can customize a favorites icon (Favicon) that is displayed in the browser’s address bar or next to the
page name if bookmarked.
Step 1
Click Administration > User Interface Settings.
Step 2
Choose the Favicon tab.
Step 3
In the Images pane, choose the image, or click Add to add a new image not listed.
Step 4
Click Submit.
Note
The Favicon image size must be 16 x 16 and in PNG format.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
3-5
Chapter 3
Managing System Administration Settings
Portal Customization
Customizing the Application Header
You can customize the self-service portal labels, next to the customer logo, by modifying existing labels.
Step 1
Click Administration > User Interface Settings.
Step 2
Choose the Application Header tab.
Step 3
In the Application Header pane, complete the following fields:
Name
Description
Hide Entire Header check Check the check box to hide the header section. If checked, the header that contains
box
the logo image, application name, and links, such as Logout, are hidden.
Product Name field
The product name.
Product Name 2nd Line
field
Continuation of the product name.
Enable About Dialog
check box
Check the check box to enable the About link in the header. Uncheck the check box
to disable the About link in the header.
Administrator Portal
Custom Link 1 Label field Enter the custom link label 1 for the administrator portal.
Custom Link 1 URL field Enter the custom link URL 1 for the administrator portal.
Custom Link 2 Label field Enter the custom link label 2 for the administrator portal.
Custom Link 2 URL field Enter the custom link URL 2 for the administrator portal.
End-user Portal
Custom Link 1 Label field Enter the custom link label 1 for the end user portal.
Custom Link 1 URL field Enter the custom link URL 1 for the end user portal.
Custom Link 2 Label field Enter the custom link label 2 for the end user portal.
Custom Link 2 URL field Enter the custom link URL 2 for the end user portal.
Step 4
Click Save.
Customizing the Date Display
Numerous data display formats are supported.
Step 1
Click Administration > User Interface Settings.
Step 2
Choose the Date Display tab.
Step 3
Edit the date format.
Step 4
If required, click Hide Timezone to hide the time zone display from the user interface.
Step 5
Click Save.
Cisco UCS Director Administration Guide, Release 4.0
3-6
OL-30149-02
Chapter 3
Managing System Administration Settings
Support Information
Customizing the Color Theme
Step 1
Click Administration > User Interface Settings.
Step 2
Choose the Color Theme tab.
Step 3
From the drop-down list, choose a Theme Style.
Step 4
Click Save.
Customizing Logout Redirect
Step 1
Click Administration > User Interface Settings.
Step 2
Choose the Logout Redirect tab.
Step 3
Enter the URL.
Step 4
Click Save.
Support Information
Cisco UCS Director support provides basic and advanced system information, including the license
status, database tables, version, resource usage, logs, and debugging processes for troubleshooting.
Viewing Support Information
Step 1
Click Administration > System Administration.
Step 2
Choose the Support Information tab.
Step 3
Click the System Information and Logs Link Page link.
Viewing System Information
You can view basic system information, including version, uptimes, service status, system license status,
usage, compute accounts status, compute servers status, storage accounts status, system catalogs,
network devices status, and clouds status.
The advanced system information includes basic system information, as well as database tables
summary, product configuration, top process information, and information on processors, memory,
disks, log files, network, login. You can also view system tasks status, and cloude inventory and
monitoring status.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
3-7
Chapter 3
Managing System Administration Settings
Advanced Configuration Properties
Showing Logs
You can choose one of the log files from the drop-down list. Clicking Show Log lets you view the last
few lines of the log.
Downloading All Logs
You can click Download All Logs to download all of the log files in a zip format.
Starting the Debug Log
Debug logging allows you to record a maximum of 30 minutes debug logging to a log file.
Step 1
Click Start Debug Logging.
Step 2
After the debug is finished, click Stop Debug Logging.
Step 3
Click Download Debug Logs from HH.MM.SS (time) to download the files.
Advanced Configuration Properties
The advanced configuration lets you enable or disable certain properties of Cisco UCS Director.
Enabling Advanced Configuration Properties
Step 1
Click Administration > System Administration.
Step 2
Choose the Advanced Configuration tab.
Step 3
Complete the following fields:
Name
Description
Performance
Monitoring check box
Check the check box to enable virtual infrastructure monitoring, physical
infrastructure monitoring, and external cloud monitoring.
Check all additional check boxes under this category, as needed.
Resource Metering
check box
Check the check box to enable monitoring of VM metering functions.
Note
If the VM metering function is disabled, chargeback will not work.
Event Monitoring check Check the check box to enable event monitoring.
box
Auto Support check box Check the check box to enable automatic support.
Heat Map Report
Computing check box
Check the check box to enable generation of heat map reports for the virtual
infrastructure.
Automatic Assessment
check box
Check the check box to enable generation of assessment reports every 4 hours. This
task runs the assessments for VMware clock, ESX hosts, templates, clusters, and
other properties, according to the rules and best practice recommendations provided
by VMware for virtualization.
Cisco UCS Director Administration Guide, Release 4.0
3-8
OL-30149-02
Chapter 3
Managing System Administration Settings
User Menus
Name
Description
Adaptive Provisioning
Indexing check box
Check the check box to enable and compute the load indices for hosts for various host
parameters every four hours. These indices are used in adaptive provisioning of the
catalogs. A lower index indicates a better chance for the host being chosen for
provisioning. This works according to the computing policy of a specific vDC.
Delete Inactive VM’s
Based on vDC Policy
check box
Check the check box to enable and the inactive (powered off) VM’s under a vDC are
deleted after a time specified by the administrator. This property is associated with
the Delete after inactive VM days field in a vDC.
Note
Step 4
By default the property box is unchecked (disabled).
Click Submit.
User Menus
Apart from the default menu operations available for the typical user roles, you can allow customized
menu operations for individual user roles.
Note
The menu settings that you can use depends upon your user permissions. For example, you can view or
perform the operations on menus, only if you are given read and write permission.
Setting User Menus
Step 1
Click Administration > System Administration.
Step 2
Choose the Menu Setting tab.
Step 3
From the drop-down list, choose the User Role.
Step 4
Check or uncheck the menu check boxes to allow menus for that role, or check the Reset to Defaults
check box.
Step 5
Click Submit.
User Permissions
You can control read and write permissions for individual user roles.
Setting User Permissions
Step 1
Click Administration > System Administration.
Step 2
Choose the User Permissions tab.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
3-9
Chapter 3
Managing System Administration Settings
System Tasks
Step 3
From the drop-down list, choose User Role.
Step 4
In the Allowed Operations dialog box, you can view the read and write operations for the chosen user
role.
Step 5
Check or uncheck the check boxes to allow read and write operations for an individual role, or check the
Reset to Defaults check box.
Step 6
Click Submit.
System Tasks
System tasks displays the list of system tasks with their frequency of execution.
You can execute a task by clicking on it and then clicking Run Now. This action triggers the chosen
task(s) to update its information.
Executing System Tasks
Step 1
Click Administration > System Administration.
Step 2
Choose the System Tasks tab.
Step 3
Choose a task from the list.
Step 4
Click Run Now.
Customizing Reports
Report customization allows you to make a custom label or hide the available reports.
Step 1
Click Administration > System Administration.
Step 2
Choose the Reports Customization tab.
Step 3
Choose a report.
Step 4
Click Edit.
Step 5
In the dialog box, complete the following fields:
Name
Description
Hide Report check box
Check the check box to hide the report. Uncheck the check box to show
the report.
New Label field
Specify a new label for the report if required.
Step 6
Click Save.
Cisco UCS Director Administration Guide, Release 4.0
3-10
OL-30149-02
Chapter 3
Managing System Administration Settings
Managing Icons
Managing Icons
Cisco UCS Director supports customization and management of catalog icons. Each icon set contains
many images. The images in each icon set correspond to the icons that are available in the catalog
creation form.
There are four prepopulated icon sets:
•
Container Catalog Icon Set
•
Advanced Catalog Icon Set
•
Standard Catalog Icon Set
•
VDI Catalog Icon Set
Adding an Icon
Step 1
Click Administration > System Administration.
Step 2
Choose the Icon Management tab.
Step 3
Choose an icon set category.
Step 4
Click Icon Images.
Step 5
In the Manage Icon Images page, click Add (+).
Step 6
In the Add entry to Icon Images dialog box, complete the following fields:
Name
Description
Image Label field
The new label for the image. The label is used to populate the drop-down list for the
icon during catalog creation.
Description field
The description of the image.
Select a file for Upload
upload field
The file that you browse to and upload.
Step 7
Click Upload.
Step 8
When the uploading is finished, click Submit.
Editing an Icon
Step 1
Click Administration > System Administration.
Step 2
Choose the Icon Management tab.
Step 3
Choose an icon category.
Step 4
Click Icon Images.
Step 5
In the Manage Icon Images page, choose an icon image to edit.
Step 6
Click Edit (pencil).
Step 7
In the Edit Icon Images Entry dialog box, edit the Description.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
3-11
Chapter 3
Managing System Administration Settings
Managing Icons
Step 8
Choose a replacement file to upload by clicking Browse and browsing to an image.
Step 9
Click Upload.
Step 10
When the upload is finished, click Submit.
Deleting an Icon
Step 1
Click Administration > System Administration.
Step 2
Choose the Icon Management tab.
Step 3
In the Manage Icon Images page, choose an icon image to delete.
Step 4
Click Delete (X).
Previewing an Icon
Step 1
Click Administration > System Administration.
Step 2
Choose an icon category.
Step 3
Click Icon Images.
Step 4
In the Manage Icon Images page, choose an icon image to preview
Step 5
Click Information.
Cisco UCS Director Administration Guide, Release 4.0
3-12
OL-30149-02
CH A P T E R
4
Managing Integration Settings
This chapter contains the following topics:
Note
•
Configuration Management Database Integration, page 4-1
•
Metering Data Export, page 4-2
•
Change Records, page 4-2
•
System Logs, page 4-3
•
Storage and OVF Upload, page 4-3
•
Multiple Language Support, page 4-4
You must be logged in to the appliance before you can run any of the following procedures..
Configuration Management Database Integration
The Configuration Management Database (CMDB) is used to track and manage changes in the system.
CMDB typically displays ADD, DELETE or MODIFY event types on resources such as VM, service
requests, groups, and so on.
Setting up CMBD Integration
Step 1
Click Administration > Integration.
Step 2
Choose the CMDB Integration Setup tab and complete the following fields:
Name
Description
Export to FTP Server
check box
Check the check box to export change records to an FTP server.
Export Format
drop-down list
Choose the type of export format: CSV or XML.
FTP Server field
The FTP server address.
FTP Port field
The FTP server port number.
FTP User field
The FTP user ID.
FTP Password field
The FTP user password.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
4-1
Chapter 4
Managing Integration Settings
Metering Data Export
Name
Description
FTP Export Frequency
drop-down list
Choose the frequency that the change records are exported to the FTP server.
FTP File Name field
The filename for the exported change records. The following variable can be used to
create new filenames each time that a file is exported to the target FTP server:
MONTH, WEEK, DAY, YEAR, HOUR, MIN, SEC, MLLIS.
Example: XYZ-$DAY-$HOUR-$MIN-$SEC
Test FTP check box
Step 3
Check the check box to test FTP settings.
Click Save.
Metering Data Export
You can export trend data such as VM resource usage and resource accounting details to a server by
setting up a metering data export.
Setting Up Metering Data Export
Step 1
Click Administration > Integration.
Step 2
Choose the Metering Data Export Setup tab. and complete the fields that are used in setting up the
CMDB.
Step 3
Click Save.
Change Records
Change records display the current resources and any resource changes. The resources include VM,
service request, groups, and so on.
Viewing Change Records
Step 1
Click Administration > Integration.
Step 2
Choose the Change Records tab.
Note
You can display maximum of 1000 records.
Cisco UCS Director Administration Guide, Release 4.0
4-2
OL-30149-02
Chapter 4
Managing Integration Settings
System Logs
System Logs
You can forward system log (syslog) information to configured servers. Each system message is
associated with a severity and a minimum severity level.
Setting up System Logs
Step 1
Click Administration > Integration.
Step 2
Choose the Syslogs tab.
Step 3
Check the Enable Syslog Forward check box and complete the following server fields:.
Field
Description
Enable Syslog Forward
check box
Check the check box to enable the syslog.
Minimum Severity
drop-down list
Choose the minimum severity level to filter any less severe system messages from
being forwarded to the syslog server.
Primary Syslog Server
Server Address field
The primary server address.
Protocol drop-down list Choose the protocol: UDP or TCP.
Port field
The port number.
Syslog Message Format Choose the message format: XML or plain text.
drop-down list
Secondary Syslog Server
Server Address field
The secondary server address.
Protocol drop-down list Choose the protocol: UDP or TCP.
Port field
The port number.
Syslog Message Format Choose the message format: XML or plain text.
drop-down list
Step 4
Click Save.
Storage and OVF Upload
You can configure the storage location for files uploaded by the administrator, group administrator, or
the end user. The uploaded files can either be stored locally or configured to an external NFS share mount
point. The administrator configures the NFS location.
The Upload files feature provides an option for admin, group admin, or the end-user (service end user
portal) to upload Open Virtualization Format (OVF) files to the local storage or to an external NFS share
mount point. The NFS location is configured by the administrator. For more details, see the OVF Upload
Guide.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
4-3
Chapter 4
Managing Integration Settings
Multiple Language Support
Multiple Language Support
Cisco UCS Director supports multiple languages for concurrent display and input. It supports any
language based on a double byte character set. All input fields support entering text in the user’s
language of choice.
Cisco UCS Director Administration Guide, Release 4.0
4-4
OL-30149-02
CH A P T E R
5
Managing Physical Infrastructure
This chapter contains the following sections:
Note
•
About Managing Physical Infrastructure, page 5-1
•
Testing Connectivity, page 5-4
•
Verifying Device Discovery, page 5-5
You must be logged in to the appliance before you can run any of the following procedures.
About Managing Physical Infrastructure
Cisco UCS Director lets you manage both physical and virtual infrastructure.
Cisco UCS Director discovers all components in the newly created physical account. Typically, the
discovery process takes about 5 minutes.
You can add a data center, or use the default data center. A physical account can be associated with the
default data center or to one that you add.
Note
You can add either type of infrastructure first (physical or virtual). A physical account in Cisco UCS
Director has no dependency on a virtual (cloud) account.
Adding a Data Center
Step 1
Click Administration > Physical Accounts.
Step 2
Choose the Data Centers tab.
Step 3
Click Add (+).
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
5-1
Chapter 5
Managing Physical Infrastructure
About Managing Physical Infrastructure
Step 4
In the Add Datacenter dialog box, complete the following fields:
Name
Description
Name field
A descriptive name for the data center.
Type drop-down list
Choose the Type that you want to add. A Pod Type is a logical grouping of specific
devices based on device type, vendor, and model. You can choose one of the
following Pod types:
•
FlexPod
•
GenericPod
•
ExpressPod Medium
•
ExpressPod Small
•
VSPEX
•
Vblock
Note
You can typically only add only device types that belong to
that Pod Type. The exception is GenericPod, which allows any
device.
Note
You must have a small or medium pod license to add a
compatible device into ExpressPod Small or ExpressPod
Medium. For all other Pod Types, only device type
compatibility is enforced.
Description field
(Optional) The description of the data center.
Address field
The physical location of the data center. For example this field could include the city
or other internal identification used for the data center.
Step 5
Click Add.
Adding a Physical Account
Step 1
Click Administration > Physical Accounts.
Step 2
Choose the Physical Accounts tab.
Step 3
Click Add (+).
Step 4
In the Add Account dialog box, complete the following fields:
Name
Description
Data Center drop-down Choose the data center to which this physical account belongs.
list
Category drop-down list Choose the category type (Computing or Storage).
If you chose Storage, continue to Step 5.
Cisco UCS Director Administration Guide, Release 4.0
5-2
OL-30149-02
Chapter 5
Managing Physical Infrastructure
About Managing Physical Infrastructure
Name
Description
Account Type
drop-down list
Choose the account type for this physical account. his can be one of the following:
Authentication Type
drop-down list
•
UCSM
•
HP ILO
•
Cisco Rack Server (CIMC)
•
IPMI
Choose the authentication type to be used for this account. This can be one of the
following:
•
Locally Authenticated—A locallay authenticated user account is authenticated
directly through the fabric interconnect, and can be enabled or disabled by
anyone with admin or AAA privileges.
•
Remotely Authenticated—A remotely authenticated user account is any user
account that is authenticated through LDAP, RADIUS, or TACACS+.
Account Name field
A unique name that you assign to the physical account that you want to add.
Server Address field
The IP address of the server.
User ID field
The user name for accessing this account.
Password field
The password associated with the user name.
Transport Type
drop-down list
Choose the transport type that you want to use for the account. This can be one of the
following:
•
http
•
https
Port field
The server port number.
Description field
(Optional) The description of the account.
Contact Email field
(Optional) The contact email address for the account.
Location field
(Optional) The location.
Service Provider field
(Optional) The service provider’s name, if any.
Step 5
If this account is Storage, choose the appropriate account type: NetApp ONTAP, NetApp
OnCommand, EMC VNX, or EMC VMAX Solutions Enabler.
Step 6
Click Add.
Adding a Network Element
Step 1
Click Administration > Physical Accounts.
Step 2
Choose the Managed Network Elements tab.
Step 3
Click Add Network Element.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
5-3
Chapter 5
Managing Physical Infrastructure
Testing Connectivity
Step 4
In the Add Network Element dialog box, complete the following fields:
Name
Description
Data Center drop-down The data center to which the network element belongs.
list
Device Category
drop-down list
The device category for this network element.
Device IP field
The IP address for this device.
Protocol drop-down list The protocol to be used. This can be one of the following:
•
telnet
•
ssh
Port field
The port to use.
Login field
The login name.
Password field
The password associated with the login name.
Enable Password field
The enable password for this network element.
Step 5
Click Submit.
Step 6
Enabling DHCP Logging
Step 1
Click Administration > Physical Accounts.
Step 2
Choose the Network Service Agents tab.
Step 3
Click Embedded Network Services.
Step 4
In the Embedded Network Services dialog box, check the Enable DHCP Logging check box.
Testing Connectivity
Step 1
Click Administration > Physical Accounts.
Step 2
Choose the Physical Accounts tab.
Step 3
Choose the account that you want to test.
Step 4
Click Test Connection.
Cisco UCS Director Administration Guide, Release 4.0
5-4
OL-30149-02
Chapter 5
Managing Physical Infrastructure
Verifying Device Discovery
Verifying Device Discovery
Step 1
Click Administration > Physical Accounts.
Step 2
Click on an account for which you want to verify device discovery.
Step 3
Choose the Discovered Devices tab.
Step 4
Click Setup Discovery.
Step 5
In the Setup Discovery dialog box, verify the following fields:
Step 6
Name
Description
Enable Discovery check box
The checkbox is checked by default to enable
device discovery for this account.
IP Range
The IP address range for device discovery.
TCP Timeout (ms)
TCP timeout (ms).
SNMP Timeout (ms)
SNMP timeout (ms).
SNMP Community Strings
The SNMP community string (default is public).
Click Submit.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
5-5
Chapter 5
Managing Physical Infrastructure
Verifying Device Discovery
Cisco UCS Director Administration Guide, Release 4.0
5-6
OL-30149-02
CH A P T E R
6
Managing Virtual Infrastructure
This chapter contains the following sections:
Note
•
About Managing VMware, page 6-1
•
Verifying Cloud Discovery and Connectivity, page 6-3
•
Viewing vCenter Plug-ins, page 6-3
You must be logged in to the appliance before you can run any of the following procedures.
About Managing VMware
Cisco UCS Director upports VMware through vCenter (ESX 3.5, ESX/ESXi 4.x & 5.x).
Cisco UCS Director automatically discovers all existing VMs and images in the newly created cloud
account. Typically, the discovery process takes about 5 minutes.
You can add VMware clouds as well as PowerShell agents.
Note
The term “cloud” refers to one vCenter installation.
Creating a Cloud
Step 1
Click Administration > Virtual Accounts.
Step 2
Choose the Virtual Accounts tab.
Step 3
Click Add (+).
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
6-1
Chapter 6
Managing Virtual Infrastructure
About Managing VMware
Step 4
In the Add Cloud dialog box, complete the following fields:
Name
Description
Cloud Type drop-down
list
Choose VMware.
Cloud Name field
The cloud name.
The following fields display when VMware is chosen. Other cloud types display
fields that are specific to that cloud type.
Note
Each cloud requires a unique name in Cisco UCS Director. Once a cloud has
been added, all reports refer to the cloud using the Cloud Name.
Server Address field
The vCenter server address.
Server User ID field
The vCenter server user name.
Server Password field
The vCenter server password.
Server Access Port field The server port number.
VMware Datacenter
field
The datacenter name on the vCenter account. This name allows you to discover,
monitor, and manage the specified datacenter's resources. Leave the field blank if the
entire vCenter account is managed by Cisco UCS Director.
Server Access URL
The URL for server access.
Description field
The description of the cloud.
Contact Email field
The contact email address for the cloud.
Location field
The location.
Physical Datacenter
drop-down list
Choose the converged infrastructure datacenter. By choosing a datacenter name, the
VMware cloud account appears in the converged infrastructure stack.
Service Provider field
The service provider’s name.
Step 5
Click Add.
Creating a PowerShell Agent
Step 1
Click Administration > Virtual Accounts.
Step 2
Choose the PowerShell Agents tab.
Step 3
Click Add (+).
Step 4
In the Add Agent dialog box, complete the following fields:
Name
Description
Agent Name field
The agent name.
Agent Address field
The agent address.
Agent Access Port field The agent access port number.
Access Key field
The access key.
Description field
The description of the agent.
Cisco UCS Director Administration Guide, Release 4.0
6-2
OL-30149-02
Chapter 6
Managing Virtual Infrastructure
Verifying Cloud Discovery and Connectivity
Verifying Cloud Discovery and Connectivity
Testing the Connection
Step 1
Click Administration > Virtual Accounts.
Step 2
Choose the Virtual Accounts tab.
Step 3
Choose the VMware account that you want to test.
Step 4
Click Test Connectivity.
Note
After you add one or more cloud accounts to Cisco UCS Director, you can verify that the cloud
and its data has been collected by using the Summary tab.
Step 5
Click Virtual > Compute.
Step 6
Choose the Summary tab.
Note
It can take few minutes to complete auto-discovery and populate the data. Choose the cloud name
to view its status details.
Viewing vCenter Plug-ins
Step 1
Click Administration > Virtual Accounts.
Step 2
Choose the Plugins tab.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
6-3
Chapter 6
Managing Virtual Infrastructure
Viewing vCenter Plug-ins
Cisco UCS Director Administration Guide, Release 4.0
6-4
OL-30149-02
CH A P T E R
7
Managing Policies
This chapter contains the following sections:
Note
•
Policies, page 7-1
•
Storage Policies, page 7-3
•
Network Policies, page 7-6
•
System Policies, page 7-8
You must be logged in to the appliance before you can run any of the following procedures.
Policies
Cisco UCS Director provides a self-service portal where virtual machines are provisioned from a pool
of assigned resources using predefined policies set by administrators.
A policy is a group of rules that determine where and how a new VM is provisioned within the
infrastructure based on the availability of system resources.
Cisco UCS Director requires the set up of four policies to provision VMs: computing, storage, network,
and system.
Computing Policies
Computing policies determine the computing resources used during provisioning that satisfy group or
workload requirements.
Administrators can define advanced policies by mixing and matching various conditions in the
computing policy.
Note
We recommend that you thoroughly understand all the fields in the computing policy because
combinations of conditions can result in no host machines during self-service provisioning.
Creating a Computing Policy
Step 1
Click Policies > Computing.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
7-1
Chapter 7
Managing Policies
Policies
Step 2
Choose the VMware Computing Policy tab.
Step 3
Click Add (+).
Step 4
In the Add Computing Policy dialog box appears, complete the following fields:
Name
Description
Policy Name field
The name of the policy.
Note
This name is used during catalog definition.
Policy Description field
The description of the policy.
Cloud Name drop-down list
Choose the cloud where resource allocation occurs.
Host Node/Cluster Scope
drop-down list
Choose the scope of deployment.
Resource Pool drop-down list
Choose the resource pool.
ESX Type drop-down list
Choose the ESX installation type: ESX, ESXi, or both.
ESX Version drop-down list
Choose the version of ESX.
Minimum Conditions check
boxes
Check the check boxes for one or more conditions that should match. Any
hosts that do not meet these criteria are excluded from consideration. If more
than one condition is chosen, all of the chosen conditions must match.
Note
You can narrow the scope of deployment by specifying whether to
use all, include chosen, or exclude chosen options. Depending on the
choices, a new field appears where the required hosts or clusters can
be chosen.
Deployment Options
Override Template check box
Check the check box to override the template properties. You are provided
with options to enter custom settings for CPU and memory.
Number of vCPUs field
To provide a custom number of vCPUs.1 The specified number of vCPUs for
a VM should not exceed the total cores for the chosen scope of host nodes or
clusters.
CPU Reservation (MHz) field
The CPU reservation for the VM.1 The reservation depends upon the number
of vCPUs specified.
CPU Limit (MHz) field
The CPU limit for the VM.1 The CPU limit is based on the chosen scope of
host nodes or clusters.
CPU Shares drop-down list
Choose the CPU shares: low, normal, or high.1 The CPU shares determine
which VM will get CPU resources when there is competition among VMs.
Memory field
The custom memory for the VM.1
Memory Reservation (MB)
field
The memory reservation for the VM.1 The reservation depends upon the
memory specified.
Memory Limit (MB) field
The memory limit for the VM.1 The memory limit is based on the chosen
scope of host nodes or clusters.
Memory Shares drop-down list Choose the memory shares: low, normal, or high.1 Memory shares determine
which VM gets memory resources when there is competition among VMs.
Resizing Options
Allow Resizing of VM check
box
Check the check box to allow VM resizing before provisioning or to resize
an existing VM..
Cisco UCS Director Administration Guide, Release 4.0
7-2
OL-30149-02
Chapter 7
Managing Policies
Storage Policies
Name
Description
Permitted Values for vCPUs
field
The range of vCPUs to use while provisioning a VM or resizing an existing
VM.2 A range of more than 8 is visible during VM provisioning or resizing
only if the chosen cloud (vCenter) is 5 or above and has VM version 8. Only
the values specified in the box are visible,
Permitted Values for Memory
in MB field
The range of memory to use while provisioning a VM or resizing an existing
VM. 2
For example: 512, 768, 1024, 1536, 2048, 3072, 4096, and so on. Only the
values specified in the box are visible.
Deploy to Folder field
VMs created using this policy can be deployed into a custom folder. Cisco
UCS Director allows automatic creation of folder names from group names.
By specifying ${GROUPNAME}, folders are created from the group name
which uses this policy. You can specify a new folder name or existing folder
name.
1. This option appears if you choose Override Template.
2. This option appears if you choose Allow Resizing of VM.
Step 5
Click Add.
Storage Policies
A storage policy defines resources such as the datastore scope, type of storage to use, minimum
conditions for capacity, latency, and so on.
The storage policy also provides options to configure additional disk policies for multiple disks, and to
provide datastore choices for use during a service request creation.
Storage Policies for Multiple VM disks
Cisco UCS Director supports VM provisioning with multiple disks on multiple datastores.
Disks are classified into five types: system, data, database, swap, and log. The system disk policy is
configured first, and the other disks can be configured depending on requirements. You can configure
the disk policy individually for each disk type or choose the default system disk policy for each disk.
Note
For creating storage policy for a template with multiple disks, see Chapter 10 “Multiple Disk VM
Provisioning”.
Cisco UCS Director supports datastore choice during a service request creation for VM provisioning.
You have the option to enable or disable datastore choices for the end user during service request
creation. The datastores listed depend upon the scope conditions specified in the storage policy that is
associated with the vDC during the service request creation.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
7-3
Chapter 7
Managing Policies
Storage Policies
Adding and Configuring a Storage Policy
Step 1
Click Policies > Storage.
Step 2
Choose the VMware Storage Policy tab.
Step 3
Click Add (+).
Step 4
In the Add Storage Resource Allocation Policy dialog box, complete the following fields:
Name
Description
Policy Name field
The name of the policy. This name is used during catalog definition.
Policy Description field
The description of the policy.
Cloud Name drop-down list
Choose the cloud in which resource allocation occurs.
System Disk Scope
Data Stores Scope drop-down list If you want to narrow the scope of deployment, choose whether to use all,
included selected data stores, or exclude selected data stores.
Use Shared Data Store Only check Check the check box to use shared datastores only.
box
Storage Options
Use Local Storage check box
Check the check box to use local storage. By default, the field is checked.
Use NFS check box
Check the check box to use NFS storage. By default, the field is checked.
Use SAN check box
Check the check box to use SAN storage. By default, the field is checked.
Minimum Conditions check boxes Choose one or more conditions that should match. Any datastores that do
not meet these criteria are excluded from the consideration. If more than
one condition is chosen, then all conditions must match.
Override Template check box
Check the check box to override the template properties. You are
provided with options to enter custom settings such as using thin
provisioning and custom disk size.
Resizing Options for VM Lifecycle
Allow Resizing of Disk check box Check the check box to provide the end user with an option to choose VM
disk size before provisioning.
Permitted Values for Disk in GB
field
The custom range of disk size values that are chosen while provisioning
a VM. For example, 1, 5, 10, 50, 100, 500, 1024, 5120, 10240, and so on.1
Allow user to select datastore
from scope
Check the check box to provide the end user an option to choose the data
store during the service request creation.
1. This option appears if Allow Resizing of Disk is checked.
Step 5
Click Next.
Step 6
In the Additional Disk Policies pane, choose a disk type to configure.
Step 7
Click Edit (pencil) to edit the disk type.
Note
By default, the disk policy for the disk is the same as in the System Disk Policy.
Step 8
In the Edit Disk Policies Entry dialog box, uncheck the Same as System Disk Policy check box to
configure the disk policy.
Step 9
Click Submit.
Cisco UCS Director Administration Guide, Release 4.0
7-4
OL-30149-02
Chapter 7
Managing Policies
Storage Policies
Step 10
In the Edit Entry dialog box, configure additional disk policies.
Note
Step 11
This step is similar to the way the Storage Resource Allocation Policy is configured.
Click Submit.
Note
To use the storage policy created with additional disk policies, you need to associate the policy
with the vDC that is used for the VM provisioning.
Note
When using the Additional disks policies configured in a policy, make sure to uncheck the
Provision all disks in a single datastore option during catalog creation for the multiple disk
template. For more information about catalog creation, see Chapter 8 “Managing Catalogs”.
Virtual Storage Catalogs
You can use a virtual storage catalog to customize storage policies.
Using the virtual storage catalog, you can choose more than one storage policy and give it a custom
storage entry name.
You map a storage catalog to a catalog by enabling it during catalog creation. When you raise a service
request using the catalog, you are provided with the Storage Tier choice.
Configuring a Virtual Storage Catalog
Step 1
Click Policies > Storage.
Step 2
Choose the Virtual Storage Catalog tab.
Step 3
Click Add (+).
Step 4
In the Virtual Storage Catalog dialog box, complete the following fields;
Name
Description
Catalog Name field
The name of the catalog. This name is used during catalog custom actions
definition.
Catalog Description field
The description of the catalog.
Cloud Name drop-down list
Choose the cloud account.
Choose No of Entries drop-down
list
Choose the number of entries, the range is from 1 to 10. Depending on
the choice, storage entry options are provided in the next dialog box.
Step 5
Click Next.
Step 6
In the Add Entries pane, complete the following fields:
Name
Description
Storage Entry #1
Storage Entry Name field
The storage entry name.
Storage Policy drop-down list
Choose the storage policy.
Storage Entry #2
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
7-5
Chapter 7
Managing Policies
Network Policies
Step 7
Name
Description
Storage Entry Name field
The storage entry name of the second policy.
Storage Policy drop-down list
Choose the storage policy.
Click Submit.
Note
To map the virtual storage catalog during catalog creation, see Chapter 8 “Managing Catalogs”.
Note
To view the storage tier options during Service request creation, see Chapter 9 “Using
Self-Service Provisioning”.
Network Policies
The network policy includes resources such as network settings, DHCP, or static IP, and the option to
add multiple vNICs for VMs provisioned using this policy.
Adding a Network Policy
Step 1
Click Policies > Network.
Step 2
Choose the VMware Network Policy tab.
Step 3
Click Add (+).
Step 4
In the VM Network Policy dialog box, complete the following fields:
Name
Description
Policy Name field
The name of the network policy.
Policy Description field
The description of the policy
Cloud Name drop-down list
Choose the cloud account that the policy applies to.
Port Group Type drop-down list
Choose the port group type.
Port Group Name check list
Click Select and choose a port group. The list changes depending on the
port group type choice.
Copy Adapter from Template
check box
Check the check box if you do not need custom settings. Uncheck for
custom settings.
Adapter Type drop-down list
Choose the adapter type.1
Use DHCP check box
Uncheck the check box to provide static IP address configuration details.
By default, the check box is checked.
Static IP Pool field
The static IP address or static IP address pool by the specifying the range
of IP addresses.2
Subnet Mask field
The IP subnet mask for the VM.2
Gateway List field
Configure the IP addresses of the default gateway on the VM. 2
1. This option is not visible if Copy Adapter from Template is chosen.
2. This option appears if Use DHCP is left unchecked.
Cisco UCS Director Administration Guide, Release 4.0
7-6
OL-30149-02
Chapter 7
Managing Policies
Network Policies
Step 5
Click Next.
Step 6
In the VM Networks pane, you can add and configure multiple vNICs. These vNICs are applicable to
the VM that are provisioned using this policy.
Note
To add or replace vNICs for provisioned or discovered VMs using VM actions, you must
configure the vNICs.
Step 7
(Optional) Click Add (+).
Step 8
In the Add Entry to VM Networks dialog box, complete the following fields:
Name
Description
NIC Alias field
The name for the new NIC.
Port Group Type drop-down list
Choose the type of port group.
Port Group Name check list
Click Select and choose a port group. The list changes depending on the
port group type choice.
Copy Adapter from Template
check box
Check the check box if you do not need custom settings. Uncheck for
custom settings.
Adapter Type drop-down list
Choose the adapter type.1
DHCP check box
Check the check box if you want the IP address assigned using DHCP.
Static IP Pool field
A static IP or static IP pool.
Network Mask field
The network mask.
Gateway IP Address field
The gateway IP address.
1. This option is not visible if Copy Adapter from Template is chosen.
Step 9
Click Submit.
Network Provisioning Policies
A network provisioning policy is used during orchestration workflow tasks. This policy defines Layer 2
network configuration and access control lists (ACL) for switches in the network.
Configuring a Network Provisioning Policy
Step 1
Click Policies > Network.
Step 2
Choose the Network Provisioning Policy tab.
Step 3
Click Add (+).
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
7-7
Chapter 7
Managing Policies
System Policies
Step 4
In the Add Network Resource Allocation Policy dialog box, complete the following fields:
Name
Description
Policy Name
The name of the network policy.
Policy Description
The description of the policy
Cloud Name
Choose the cloud account that the policy applies to.
Port Group Type
Choose the port group type.
Port Group Name
Click Select and choose a port group. The list changes depending on the
port group type choice.
Copy Adapter Type from
Template
Check the check box if you do not need custom settings. Uncheck for
custom settings.
Adapter Type drop-down list
Choose the adapter type.1
Use DHCP
Check the check box if you want the IP address assigned using DHCP.
1. This option is not visible if Copy Adapter from Template is chosen.
VLAN Pool Policies
A VLAN pool policy defines the VLAN range for a data center. This policy is used in orchestration
workflow for generating a free VLAN ID from the defined range specified in the policy.
Configuring a VLAN Pool Policy
Step 1
Click Policies > Network.
Step 2
Choose the VLAN Pool Policy tab.
Step 3
Click Add (+).
Step 4
In the Add Policy dialog box, complete the following fields:
Name
Description
Data Center drop-down list
Choose the data center.
Policy Name field
The policy name. This policy name is used in orchestration workflows.
Policy Description field
The description of the policy.
VLAN Range field
The VLAN range. For example 1,3, 5-15.
Step 5
Click Submit.
System Policies
A system policy defines the system specific information such as the template to use, time zone, OS
specific information, and so on.
Cisco UCS Director Administration Guide, Release 4.0
7-8
OL-30149-02
Chapter 7
Managing Policies
System Policies
Configuring a System Policy
Step 1
Click Policies > Service Delivery.
Step 2
Choose the VMware System Policy tab.
Step 3
Click Add (+).
Step 4
In the Add Policy dialog box, complete the following fields:
Name
Description
Policy Name field
The name of the policy. This name is used during catalog definition.
Policy Description field
The description of the policy.
VM Name Template field
Enter the VM name template to use.
Note
Step 5
Cisco UCS Director allows automatic creation of VM names. VM
names can be automatically created using a set of variable names.
Each variable must be enclosed in ${VARIABLE_NAME}.
Example: vm-${GROUP_NAME}-SR${SR_ID}
Choose the optional VM Name Template features:
Name
Description
End User VM Name Prefix check Check the check box to allow (during creation of a service
box
request-deployment configuration) the addition of a VM name prefix.
Power On after deploy cheek box Check the check box to automatically power on all VMs deployed using
this policy.
Host Name Template field
Cisco UCS Director allows automatic creation of VM hostnames.
Hostnames can be auto created using set of variable names. Each variable
must be enclosed in ${VARIABLE}.
Step 6
Choose the Host Name Template variable names. Example: ${VMNAME}
Step 7
Complete the remaining fields:
Name
Description
DNS Domain field
The IP domain to use for the VM.
Time Zone drop-down list
Choose the time zone.
DNS Suffix List field
The DNS suffixes to configure for the DNS lookup. If there is more than
one suffix, each may be separated by a comma.
DNS Server List field
The list of DNS server IP addresses. Use a comma to separate more than
one server.
VM Image Type drop-down list
Choose the OS of the image that is installed on the VM. Choose Windows
and Linux or Linux Only.
Windows
Product ID field
The Windows product ID or license key. The product ID or license key
can be provided here or at the OS license pool. The key entered in OS
license pool overrides the key provided here.
License Owner Name field
The Windows license owner name.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
7-9
Chapter 7
Managing Policies
System Policies
Name
Description
Organization field
The organization name to configure in the VM.
License Mode drop-down list
Choose the per-seat or per-server.
Number of License Users
The number of license users or connections.
WINS Server List field
The WINS server IP addresses. Multiple values are separated with a
comma.
Auto Logon check box
Check the check box to enable auto log on.
Auto Logon Count field
The number of times to perform auto log on.
Administrator Password field
The password for the administrators account.
Domain/Workgroup drop-down
list
Choose either Domain or Workgroup.
Workgroup field
The name for the workgroup. 1
Domain field
The name of the Windows domain.2
Domain Username field
The Windows domain administrator’s username.2
Domain Password field
The Windows domain administrator’s password.2
1. This option appears if Workgroup is chosen.
2. This option appears if Domain is chosen.
Step 8
Click Add.
OS Licenses
Cisco UCS Director provides an option for users to add Windows OS licenses under the OS License.
These licenses are mapped to Windows images during the creation of a catalog.
You have an option to provide the Windows OS license for a Windows image in VMware System Policy
or choose the key from the OS version field during catalog creation.
Note
The Windows key from the OS version field in the catalog overrides the Windows license key that is
provided in the VMware system policy.
Adding an OS License
Step 1
Click Policies > Service Delivery.
Step 2
Choose the OS License tab.
Step 3
Click Add (+).
Step 4
In the Add License Details dialog box, complete the following fields:
Name
Description
Windows Version Name field
The Windows version name.
Cisco UCS Director Administration Guide, Release 4.0
7-10
OL-30149-02
Chapter 7
Managing Policies
System Policies
License field
The Windows product ID or license key. This field accepts KMS client
set-up keys.
License Owner Name field
The Windows license owner name.
Organization field
The organization name to configure in the VM.
License Mode drop-down list
Choose the per-seat or per-server.
Number of Licensed Users field
The number of license users or connections.
Step 5
Click Submit.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
7-11
Chapter 7
Managing Policies
System Policies
Cisco UCS Director Administration Guide, Release 4.0
7-12
OL-30149-02
CH A P T E R
8
Managing Virtual Data Centers
This chapter contains the following sections.
•
About Managing vDCs, page 8-1
•
vDC Actions, page 8-1
•
vDC Service Profiles, page 8-4
About Managing vDCs
A virtual data center (vDC) is an environment that combines virtual resources, operational details, rules,
and policies to manage specific group requirements.
A group or organization can manage multiple virtual data centers. images, templates, and policies.
Organizations can allocate quotas and assign resource limits for individual groups at the virtual data
center level.
You can also define approvers specific to a vDC. The approver for a particular vDC must approve the
request from users for VM provisioning.
Note
There is a default vDC in Cisco UCS Director and all discovered VMs are part of this default vDC.
Discovered VMs are VMs that are created outside of Cisco UCS Director or were already created on
vCenter before Cisco UCS Director was installed. Cisco UCS Director automatically discovers such
VMs and adds them to the default vDC.
A VM that is provisioned using a service request can be associated with a vDC. When you are creating
a service request, you can choose the vDC on which this VM is provisioned. You can view a list of vDCs
available for a particular group and choose the required vDC when provisioning VMs.
vDC Actions
Adding a vDC
Step 1
Click Policies > Virtual Data Centers.
Step 2
Choose the vDC tab.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
8-1
Chapter 8
Managing Virtual Data Centers
vDC Actions
Step 3
Click Add (+).
Step 4
In the Add vDC dialog box, complete the following fields:
Name
Description
vDC Name field
The name of the vDC.
vDC Locked check box
Check the check box to deny the use of the vDC for any further deployments.
Actions on existing VMs, within this vDC, are disabled. Uncheck the check box
to allow the use of the vDC for further deployments.
vDC Description field
The vDC specific description.
Group drop-down list
Choose the group for which the vDC is being set up.
Cloud Name drop-down list
Choose the cloud on which the vDC is being set up.
Approvers and Contacts
First Approver User Name
field
The user who must approve the service request.
Second Approver User Name The second user who must approve the service request.
field
Provider Support Email
Address field
The contact or user’s email address. The person who is notified about VM
provisioning using this vDC.
Copy Notifications to Email
Address field
The second contact’s email for copying notifications about vDC.
Policies
System Policy drop-down list Choose the system policy applicable to the vDC.
Computing Policy
drop-down list
Choose the computing policy applicable to the vDC.
Network Policy drop-down
list
Choose the network policy applicable to the vDC.
Storage Policy drop-down
list
Choose the storage policy applicable to the vDC.
Cost Model drop-down list
Choose the cost model applicable to the vDC.
Disable displaying cost in the Check the check box to disable displaying cost in the SR summary and email
SR summary and email page page for this vDC.
check box
User Action Policy
drop-down list
Choose the policy that is used for execution of orchestration workflow postprovisioning of the VMs. The chosen workflow appears as an action button for
VMs within the vDC.
End User Self-Service Policies
VM Power Management
check box
Check the check box to enable all VM power management actions for VMs
belonging to this vDC.
VM Resize check box
Check the check box to enable VM resize action for VMs in this vDC.
VM Snapshot Management
check box
Check the check box to enable all storage snapshot actions for VMs in this vDC.
VM Deletion check box
Check the check box to enable VM delete action for VMs in this vDC.
VM Disk Management check Check the check box to enable VM disk management for VMs in this vDC.
box
Cisco UCS Director Administration Guide, Release 4.0
8-2
OL-30149-02
Chapter 8
Managing Virtual Data Centers
vDC Actions
Name
Description
VM Network Management
check box
Check the check box to enable network management for VMs belonging to this
vDC.
Delete after Inactive VM
days drop-down list
Choose the number of days to wait before deleting an inactive VM. The VM in
the inactive state is when it is not in the power-on state.
Step 5
Click Add.
Viewing a vDC
Step 1
Click Policies > Virtual Data Centers.
Step 2
In the All User Groups pane, choose the vDC group that contains the vDC to view.
Step 3
Choose the vDC tab.
Step 4
In the main viewing pane, choose the vDC to view.
Step 5
Click View to open the vDC Details page.
Editing a vDC
Step 1
Click Policies > Virtual Data Centers.
Step 2
In the All User Groups pane, choose the vDC group that contains the vDC to edit.
Step 3
Choose the vDC tab.
Step 4
In the main viewing pane, choose the vDC to edit.
Step 5
Click Edit to open the Edit vDC dialog box.
Note
Step 6
Modify the vDC as needed.
Note
Step 7
The editing categories are the same as Add vDC.
The vDC name cannot be edited.
Click Save.
Deleting a vDC
Step 1
Click Policies > Virtual Data Centers.
Step 2
In the All User Groups pane, choose the vDC group that contains the vDC to delete.
Step 3
Choose the vDC tab.
Step 4
In the main viewing pane, choose the vDC to delete.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
8-3
Chapter 8
Managing Virtual Data Centers
vDC Service Profiles
Step 5
Click Delete.
Cloning a vDC
Step 1
Click Policies > Virtual Data Centers.
Step 2
In the All User Groups pane, choose the vDC group that contains the vDC to clone.
Step 3
Choose the vDC tab.
Step 4
In the main viewing pane, choose the vDC to clone.
Step 5
Click Clone to open the Clone vDC dialog box.
Step 6
Add a new vDC name and description and edit any other properties of the cloned vDC.
Note
Step 7
The categories for cloning are the same as Add vDC.
Click Save.
Managing Application Categories in a vDC
Step 1
Click Policies > Virtual Data Centers.
Step 2
In the All User Groups pane, choose the vDC group that contains the vDC.
Step 3
Choose the vDC tab.
Step 4
In the main viewing pane, choose the vDC to edit .
Step 5
Click Manage Categories to open the Edit App Category dialog box.
Step 6
Edit any fields that apply to optionally change the system policy, computing policy, network policy, or
stroage policy. You can also change the cost model and the smart allocation policy.
Step 7
Click Save.
vDC Service Profiles
This feature is similar to Adding a vDC, but the vDCs created under vDC Service Profiles are used
during orchestration workflows. With this feature you can create Gold, Silver, and Bronze vDCs that can
be used when you create vDCs during a workflow task.
Adding vDC Service Profiles
Step 1
Click Policies > Virtual Data Centers.
Step 2
Choose the vDC Service Profile tab.
Step 3
Click Add (+).
Cisco UCS Director Administration Guide, Release 4.0
8-4
OL-30149-02
Chapter 8
Managing Virtual Data Centers
vDC Service Profiles
Step 4
In the Add vDC Service Profile dialog box, complete the following fields:
Name
Description
General Information
vDC Profile Name field
The name of the vDC profile.
vDC Locked check box
Check the check box to deny the use of the vDC for any further
deployments. Actions on existing VMs, within this vDC, are disabled.
Uncheck the check box to allow the use of the vDC for further
deployments.
vDC Description field
The vDC description.
Group drop-down list
Choose the group for which the vDC is being set up.
Cloud Name drop-down list
Choose the cloud on which the vDC is being set up.
Approvers and Contacts
First Approver User Name field
The user who must approve the service request.
Second Approver User Name field The second user who must approve the service request.
Provider Support Email Address
field
The contact or user’s email address. The person who is notified about VM
provisioning using this vDC.
Copy Notifications to Email
Address field
The second contact’s email for copying notifications about vDC.
Policies
System Policy drop-down list
Choose the system policy applicable to the vDC service profile.
Computing Policy drop-down list Choose the computing policy applicable to the vDC service profile.
Network Policy drop-down list
Choose the network policy applicable to the vDC service profile.
Storage Policy drop-down list
Choose the storage policy applicable to the vDC service profile.
Cost Model drop-down list
Choose the cost model applicable to the vDC service profile.
Disable displaying cost in the SR
summary and email page check
box
Check the check box to disable displaying cost in the SR summary and
email page for this vDC service profile.
User Action Policy drop-down list Choose the policy that is used for execution of orchestration workflow post
provisioning of the VMs. The chosen workflow appears as an action button
for VMs within the vDC.
End User Self-Service Options
VM Power Management check
box
Check the check box to enable all VM power management actions for VMs
belonging to this vDC.
VM Resize check box
Check the check box to enable VM resize action for VMs belonging to this
vDC.
VM Snapshot Management check Check the check box to enable all storage snapshot actions for VMs
box
belonging to this vDC.
VM Deletion check box
Check the check box to enable VM delete action for VMs belonging to this
vDC.
VM Disk Management check box Check the check box to enable VM disk management for VMs in this vDC.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
8-5
Chapter 8
Managing Virtual Data Centers
vDC Service Profiles
Name
Description
VM Network Management check
box
Check the check box to enable network management for VMs belonging to
this vDC.
Delete after Inactive VM days
drop-down list
Choose the number of days to wait before deleting an inactive VM. The
VM in the inactive state is when it is not in the power-on state.
Step 5
Click Add.
Cisco UCS Director Administration Guide, Release 4.0
8-6
OL-30149-02
CH A P T E R
9
Managing Catalogs
This chapter contains the following sections:
Note
•
About Managing Catalogs, page 9-1
•
Publishing a Catalog, page 9-1
•
Publishing Advanced Catalogs, page 9-4
•
Viewing a Catalog, page 9-5
•
Editing a Catalog, page 9-5
•
Deleting a Catalog, page 9-6
•
Cloning Catalogs, page 9-6
•
Assessing Deployability, page 9-6
You must be logged in to the appliance before you can run any of the following procedures.
About Managing Catalogs
You can self-provision VMs using predefined catalog items. A catalog item is created by the system
administrator, and defines parameters such as cloud name, and group name to which the VM is bound.
Publishing a Catalog
Step 1
Click Policies > Catalogs.
Step 2
Choose the Catalog tab.
Step 3
Click Add (+).
Step 4
In the Create Catalog dialog box, complete the following fields:
Name
Description
Basic Information
pane
Catalog Name field
The name of the catalog.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
9-1
Chapter 9
Managing Catalogs
Publishing a Catalog
Name
Description
Catalog Description
field
The description of the catalog.
Catalog Type
drop-down list
Choose between:
•
Standard is used to create catalogs for VM provisioning using images from a list
of clouds.
•
Advanced see the “Publishing Advanced Catalogs” entry.
•
Service Container is a container for virtual machines.
•
VDI is a virtual disk image.
Catalog Icon drop-down Choose from a list of icons to associate this catalog with an image. This icon is seen
list
when you are creating a service request using this catalog.
Applied to all groups
check box
Check the check box to enable all groups to use this catalog. Uncheck the check box
to deny its use to other groups.
Selected Groups check
box list
Check the check boxes for the included groups that are from the Select Items dialog
box. The checked group(s) use this catalog to provision new VMs.
Cloud Name drop-down Choose the cloud with the image for VM provisioning.
list
Image drop-down list
Choose the type of image (any existing templates such as Windows, Linux and other
files that make up the image) that you use when VMs are provisioned using this
catalog.
Windows License Pool
Choose the Windows License. 1
Provision all disks in
single datastore check
box
Check the check box to provision all disks in a single datastore.2 You can also choose
to use the datastores configured for each disk in the storage policy.
Service Container
Template Name
drop-down list
Choose the template from the list.3
XenDesktop Catalog
drop-down list
Choose the template from the list of XenDesktop dedicated catalogs configured in
Desktop Studio.4
Note
For more information on multiple disk storage policy creation, see Chapter 6
“Managing Policies”.
1. This option appears only when a Windows image is chosen.
2. This option appears if the chosen template has multiple disks.
3. This option appears when the chosen Catalog Type is Service Container.
4. This option appears when the chosen Catalog Type is VDI.
Step 5
Click Next.
Step 6
In the Applications Detail pane, complete the following fields:
Name
Description
Application Details
Pane
Category drop-down list Choose a vDC category.
Support Contact Email
Address field
The email address of the contact that is notified when a service request is created
using this catalog item.
Cisco UCS Director Administration Guide, Release 4.0
9-2
OL-30149-02
Chapter 9
Managing Catalogs
Publishing a Catalog
Name
Description
Specify OS drop-down
list
Choose the type of OS installed on the VM when it is provisioned.
Specify Other OS field
Any OS that is not available in the Specify OS list.
Specify Applications
check box list
Check the check boxes for applications from the Select Items dialog box. These
applications are installed on the VM during provisioning.
Specify Other
Applications field
The applications that are not available in the Select Items dialog box.
Application Code field
An application code that is used in the VM name.
Step 7
Click Next.
Step 8
In the User Credentials pane, complete the following fields:
Name
Description
Credential Options
drop-down list
Choose to allow or disallow users to retrieve VM access credentials (shared).
User ID field
The user ID.1
Password field
The user password.1
1. This option appears when you choose either of the share options under Credential Options.
Step 9
Click Next.
Step 10
In the Customization pane, complete the following fields.
Name
Description
Post Provisioning
Custom Actions check
box
Check the check box to enable an orchestration workflow that is executed after VM
provisioning.
Workflow drop-down
list
Choose a defined workflow for provisioning.1
VM App Charge
Frequency drop-down
list
Choose Hourly or Monthly.
Active VM Application The cost to this catalog of a VM in active state per hour or month.
Cost field
Inactive VM
Application Cost field
The cost to this catalog of a VM in inactive state per hour or month.
1. This option appears when Post Provisioning Custom Actions is checked.
Step 11
Click Next.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
9-3
Chapter 9
Managing Catalogs
Publishing Advanced Catalogs
Step 12
In the VM Access pane, complete the following fields:
Name
Description
Web Access
Configuration check
box
Check the check box to enable web access to the VM. Uncheck the check box to
disable web access to the VM.
URL field
The URL of the VM.1
Label field
The label that is defined for this URL.1
Remote Desktop Access Check the check box to enable remote desktop access to the VM. Uncheck the check
Configuration check
box to disable remote desktop access to the VM.
box
Server field
The IP address of the server for remote access.2
Port field
The port number on the server for remote access.2
Label field
The label that is defined for this remote access.2
1. This option appears when Web Access Configuration is checked.
2. This option appears when Remote Desktop Access Configuration is checked.
Step 13
Click Next.
Step 14
Review the catalog information in the Summary.
Step 15
Click Submit when done.
Publishing Advanced Catalogs
When you choose the Advanced catalog type, you can provision workflow catalogs to end users. End
users can use these catalogs during a Service Request to execute workflows. You create an Advanced
Catalog Item by defining parameters such as Group Name, Workflow, and so on.
Publishing Advanced Catalogs
Step 1
Click Policies > Catalogs
Step 2
Choose the Catalog tab.
Step 3
Click Add (+).
Step 4
In the Create Catalog dialog box, complete the following fields:
Name
Description
Basic Information
Pane
Catalog Name field
The name of the catalog.
Catalog Description
field
The description of the catalog.
Catalog Type
Choose Advanced as the type of catalog.
Cisco UCS Director Administration Guide, Release 4.0
9-4
OL-30149-02
Chapter 9
Managing Catalogs
Viewing a Catalog
Name
Description
Catalog Icon drop-down Choose the icon to associate this catalog with an image. The icon is seen when
list
creating a service request using this catalog.
Applied to all groups
check box
Check the check box to enable all groups to use this catalog. Uncheck the check box
to deny its use to other groups.
Selected Groups check
box list
Check the check boxes to include groups from the Select Items dialog box. The
checked group(s) can use this catalog to provision new VMs.
Step 5
Click Next.
Step 6
In the vApp Workflow pane, click Workflow Select.
Step 7
In the Select dialog box, check the check box adjacent to the workflow to use.
Step 8
Click Select.
Step 9
Review the catalog information on the Summary page.
Step 10
Click Submit.
Viewing a Catalog
Step 1
Click Policies > Catalogs.
Step 2
Choose the Catalog tab.
Step 3
Choose the Catalog Name to view.
Step 4
Click View.
Editing a Catalog
Step 1
Click Policies > Catalogs.
Step 2
Choose the Catalog tab.
Step 3
Choose the Catalog Name to edit.
Step 4
Click Edit to open the Modify Catalog dialog box.
Note
Step 5
Edit the catalog items, paging through the dialog boxes until you reach the Summary.
Note
Step 6
The fields, drop-down lists, and check boxes are identical to those found in “Publishing a
Catalog”.
The Catalog Name cannot be edited.
Click Submit.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
9-5
Chapter 9
Managing Catalogs
Deleting a Catalog
Deleting a Catalog
Step 1
Click Policies > Catalogs.
Step 2
Choose the Catalog tab.
Step 3
Choose the Catalog Name to delete.
Step 4
Click Delete (X).
Cloning Catalogs
You can clone a catalog item using the clone feature. When you choose a catalog item to clone, all
existing properties are copied into the new catalog ,except for the catalog Name and Description. After
defining the Name and Description, you can modify other properties.
Cloning a Catalog
Step 1
Click Policies > Catalogs.
Step 2
Choose the Catalog tab.
Step 3
Choose the Catalog Name to clone.
Step 4
Click Clone to open the Clone Catalog dialog box.
Step 5
Enter a new catalog Name and Description.
Step 6
Edit the catalog details if necessary.
Step 7
Click Submit.
Assessing Deployability
Note
You can choose a catalog item to assess deployable hosts and provide a reason for excluded hosts.
Step 1
Click Policies > Catalogs.
Step 2
Choose the Catalog tab.
Step 3
Choose the Catalog Entry to assess.
Step 4
Click Deployability Assessment.
Cisco UCS Director Administration Guide, Release 4.0
9-6
OL-30149-02
CH A P T E R
10
Using Self-Service Provisioning
This chapter contains the following sections:
Note
•
Service Requests, page 10-1
•
Service Request Workflow and Details, page 10-4
•
About Scheduling a Service Request, page 10-6
•
About Resubmitting a Service Request, page 10-6
•
Other Service Request Functions, page 10-7
•
Service Request Approval Process, page 10-9
•
Service Request Budgeting, page 10-10
You must be logged in to the appliance before you can run any of the following procedures.
About Self-Service Provisioning
You can provision VMs by using self-service provisioning. However, before a VM is provisioned, you
must create a service request. This action initiates a VM creation workflow that includes budget
validation, dynamic resource allocation, approval, provisioning, life cycle set up, and notification about
the status of service requests.
Service Requests
To provision a VM, you must first create a service request. Once the request is approved by the relevant
administrative user, the VM gets provisioned. A VM is provisioned immediately or scheduled up to 90
days from the day of the service request. The approval process for the service request is optional.
Creating a Service Request with Catalog Type—Standard
Step 1
Click Organizations > Service Requests.
Step 2
Choose the Service Requests tab.
Step 3
Click Create Request.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
10-1
Chapter 10
Using Self-Service Provisioning
Service Requests
Step 4
In the Create Service dialog box, complete the following fields:
Name
Description
Catalog Selection
Request Pane
Select Group
drop-down list
Choose the group(s) for which a new VM is provisioned.
Catalog Type
drop-down list
Choose the catalog type: Standard, Advanced, Service Container, or VDI.
Select Catalog
drop-down list
Choose the catalog that is used for VM provisioning.
Note
Advanced is used for Orchestration Workflow.
Step 5
Click Next.
Step 6
In the Deployment Configuration pane, complete the following fields:
Name
Description
Select VDC drop-down
list
Choose the vDC on which on which the VM is provisioned. vDCs are defined by the
administrator.
VM Name or VM Prefix The VM name or prefix.
field
Comment field
Any comments relating to the deployment configuration.
Provision drop-down
list
Choose either Now or Later. The VM is provisioned immediately or up to 90 days in
the future. When Later is chosen a calendar for the Day, drop-down lists for the Hour
and Minute, and radio buttons for AM or PM appear.
Power OFF the VM
After check box
Check the check box to enter the lifetime of the VM in terms of days and hours after
which the VM is terminated automatically.
Days calendar
The number of days after which the VM is terminated.1
Hours drop-down list
Choose the number of hours after which the VM is terminated.1
Minute drop-down list
Choose the number of minutes after which the VM is terminated.1
1. This option appears when the Power OFF the VM After check box is checked.
Step 7
Click Next.
Step 8
In the Custom Specification pane, complete the following fields:
Name
Description
CPU Cores drop-down
list
Choose the CPU cores for the VM being provisioned.1
Memory drop-down list Choose the amount of memory for the VM being provisioned.1
Storage Tier drop-down Choose an option to customize storage entries for the VM being provisioned.2
list
Note
See more information about the creation of a virtual storage catalog in
Chapter 6 “Managing Policies”. See more information about enabling this
option during catalog creation in Chapter 8 “Managing Catalogs”.
Disks drop-down list
Choose the preferred hard disk size for VM provisioning. The list of available
datastores depends upon the scope conditions specified in the storage policy. You can
enable or disable this option in the storage policy.
Cisco UCS Director Administration Guide, Release 4.0
10-2
OL-30149-02
Chapter 10
Using Self-Service Provisioning
Service Requests
1. This list opens if the resizing option is chosen in the Computing policy dialog box.
2. This custom list opens, if the Virtual Storage Catalog was enabled when the chosen catalog was created.
Step 9
To choose a datastore for a disk, choose a disk from the list and click the Pencil icon.
Step 10
Click Select to a view available datastores.
Step 11
Choose a datastore from the list and click Select.
Step 12
Click Submit.
Note
Step 13
Complete the details in the Custom Workflow pane.
Note
Step 14
Custom workflow inputs apply if the catalog chosen for VM provisioning has Post Provisioning
Custom Actions enabled. In the above scenario, the post-provisioning workflow allows users to
specify custom inputs.
Click Next.
Note
Step 15
For templates with multiple disks, you must choose a datastore for each disk.
The list of available datastores depends upon the scope conditions specified in the storage policy.
You can choose only one datastore for each disk category (System, Data, Database, Swap, and
Log).
Review the Summary for the service request. Click Back to change any entries, or click Submit.
Service Request with Catalog Type—Advanced
By choosing the advanced catalog type during the creation of a service request, you can execute
orchestration workflows. The details involved for creating an advanced catalog are much the same as
creating a standard catalog.
Creating a Service Request with Catalog Type—Advanced
Step 1
Click Organizations > Service Requests.
Step 2
Choose the Service Requests tab.
Step 3
Click Create Request.
Step 4
Choose the Group, Catalog Type (Advanced), and the Catalog (workflow) in the Catalog Selection
section of the Create Service Request dialog box.
Step 5
Click Next.
Step 6
Provide the custom workflow input values in the Custom Workflow section of the Create Service
Request dialog box.
Step 7
Click Next.
Step 8
Review the Summary for the service request.
Step 9
Click Back to edit the entries, or click Submit.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
10-3
Chapter 10
Using Self-Service Provisioning
Service Request Workflow and Details
Depending upon the user inputs entered in the workflow creation, these inputs are reflected
during the service request.
Note
Service Request Workflow and Details
After you create a service request, you can check the status and workflow, cancel the request, resubmit
the request, and so on. These actions are controlled by the toolbar buttons at the top of the service
requests lists.
Service Request Workflow
The Workflow Status box displays details about the service request and the workflow steps. A typical
workflow for a service request includes the following steps:
1.
Initiation—Service request initiation by the user.
2.
Resource Allocation—Allocation of resources that are required for the VM.
3.
Approval—Process of user approval before the VM is provisioned. An email is sent to the approver
who was defined during the catalog creation. This catalog is the catalog that is used during VM
provisioning. This step is optional.
4.
Provision—Provisioning process of the VM.
5.
Set Up Lifecycle Schedule—Life cycle scheduling where the set up, scheduled, and termination
times are set.
6.
Notify—Process of notifying the user through email about VM provisioning.
Optional service request workflow steps include Budget Watch and Check Resource Limits:
7.
Budget Watch—An administrator has to enable budgeting for a group. This step determines if
sufficient budget is available for provisioning a new VM in that group.
8.
Check Resource Limits—Resource limits for a group must be enabled by an administrator. It
determines if sufficient resources are available for provisioning a new VM in that group.
Service Request Details
Service Request details include items under Overview, Ownership, Catalog Information, and the
Current Status of the service request, as follows:
Name
Description
Overview
Request ID
The service request ID number.
Request Type
The type of request (in this case creating a VM).
vDC
The vDC where the VM is provisioned.
Image
The image from which the VM is provisioned.
Request Time
The time of the service request creation.
Request Status
The status of the service request as Complete, Cancelled, Failed, and so on.
Cisco UCS Director Administration Guide, Release 4.0
10-4
OL-30149-02
Chapter 10
Using Self-Service Provisioning
Service Request Workflow and Details
Name
Description
Comments
Any comments.
Ownership
Group
The group to which the service request initiating user belongs.
Initiating User
The user who has initiated the service request.
Duration Hours
The amount of time the VM is active. If defined, the VM will get deleted after
the specified time.
Scheduled Time
The time after which the VM is provisioned. If defined, the VM is provisioned
at 6 a.m. on the scheduled date. If not defined, the VM is provisioned as soon as
the workflow steps for the service request are complete.
Catalog Information
vDC Owner Email
The email ID provided by the administrator when creating a vDC.
Approving Users
The user (if defined) who must approve the service request for VM provisioning.
Catalog Name
The catalog item name from which the VM is provisioned
Catalog Description The catalog item description.
Service Request
Cost
The cost (projected) of provisioning the VM. This cost is determined based on
the Cost Model that is defined for the catalog item.
You can view the status of each workflow step. Details such as warning or error messages and the time
of the request are also displayed. The workflow steps are color-coded to indicate their status:
Note
Color Code
Description
Grey
The step is incomplete.
Green
The step completed successfully.
Red
The step failed. The reason for failure is also described.
Blue
Additional input is required for the step to complete. For example, an approver
was defined for a service request, and until the request is approved, this step is
incomplete.
Approvers can view service requests that are assigned to them under the Approvals tab.
Viewing a Service Request’s Workflow Status
Step 1
Click Organizations > Service Requests.
Step 2
From the left panel, choose a User Group.
Note
The default is All User Groups listing all Service Requests.
Step 3
Choose the Service Request tab.
Step 4
Choose a service request.
Step 5
Click View Details to see the details and status of the service request. By default the Workflow Status
tab appears in the dialog box.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
10-5
Chapter 10
Using Self-Service Provisioning
About Scheduling a Service Request
Viewing a Service Request’s Log
Step 1
Click Organizations > Service Requests.
Step 2
From the left panel, choose a User Group.
Note
The default is All User Groups listing all Service Requests.
Step 3
Choose the Service Request tab.
Step 4
Choose a service request.
Step 5
Click View Details, and choose the Log tab.
About Scheduling a Service Request
You can schedule VM provisioning for a later date using Deferred Provisioning. The default
provisioning is 8.30 a.m. on the date of scheduling. Once the date is set, the VM provisioning status in
the workflow will display the provisioning as scheduled for a future date.
Scheduling Service Requests
Step 1
Click Organizations > Service Requests.
Step 2
Choose the Service Requests tab.
Step 3
Click Create Request.
Step 4
Choose the group, catalog type and catalog (see more information at “Creating a Service Request with
Catalog Type—Standard”) and click Next.
Step 5
Choose the Later option for the Provision field, and the provisioning date in the Service Request dialog
box.
Step 6
Click Next until the Summary page appears.
Step 7
Click Submit.
About Resubmitting a Service Request
You can resubmit a failed service request. A service request could fail for the following reasons:
•
Budget limit (if defined by administrator) is exceeded for the group under which the VM is being
provisioned.
•
Resource limits (if defined by administrator) is exceeded for the group under which the VM is being
provisioned.
•
Provisioning could fail if relevant information is not provided when creating a service request.
Cisco UCS Director Administration Guide, Release 4.0
10-6
OL-30149-02
Chapter 10
Using Self-Service Provisioning
Other Service Request Functions
When a service request is resubmitted, the process starts again from the workflow step that failed in the
earlier submittal. For example, if a service request fails in the Resource Allocation workflow (Step 2),
when this service request is resubmitted, the process is initiated from that step.
Resubmitting a Service Request
Step 1
Click Organizations > Service Requests.
Step 2
From the left panel, choose a User Group.
Note
The default is All User Groups listing all Service Requests.
Step 3
Choose the Service Request tab.
Step 4
Choose the service request to resubmit.
Step 5
Click Resubmit Request.
Other Service Request Functions
Canceling a Service Request
Step 1
Click Organizations > Service Requests.
Step 2
From the left panel, choose a User Group.
Note
The default is All User Groups.
Step 3
Choose the Service Request tab.
Step 4
Choose the service request entry to cancel.
Step 5
Click Cancel Request.
Step 6
Click Submit to cancel the service request.
Rolling Back a Service Request
You can rollback a service request when a service request is created using orchestration workflow or
fenced container deployment.
Step 1
Click Organizations > Service Requests.
Step 2
From the left panel, choose a User Group.
Note
The default is All User Groups listing all Service Requests.
Step 3
Choose the Service Request tab.
Step 4
Choose the service request to archive.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
10-7
Chapter 10
Using Self-Service Provisioning
Other Service Request Functions
Step 5
Click Archive.
Step 6
In the Archive Request dialog box, click Archive.
Note
Choose the Archived Service Requests tab to view all the archived requests.
Viewing Service Requests for a Particular Group
Step 1
Click Organizations > Service Requests.
Step 2
From the left panel, choose a User Group.
Step 3
Choose the Service Requests tab.
Searching the Service Requests History for a Group
Step 1
Click Organizations > Service Requests.
Step 2
Choose the Service Requests tab.
Step 3
Click the Search and Replace button on the toolbar.
Step 4
In the Search and Replace dialog box, enter the search terms in the search fields.
Step 5
Click Submit,
Exporting the Service Requests History for a Group
Step 1
Click Organizations > Service Requests.
Step 2
From the left panel, choose a Group Name.
Step 3
Choose the Service Requests tab.
Step 4
Click the Export Report icon on the right of the toolbar.
Step 5
In the Export Report dialog box, choose the report format: PDF, CSV, or XLS.
Step 6
Click Generate Report.
Reinstating an Archived Service Request
Step 1
Click Organizations > Service Requests.
Step 2
Choose the Archived Service Requests tab.
Step 3
Choose the service request to unarchive.
Cisco UCS Director Administration Guide, Release 4.0
10-8
OL-30149-02
Chapter 10
Using Self-Service Provisioning
Service Request Approval Process
Step 4
ClickUnarchive.
Service Request Approval Process
Before the VM is provisioned, a service request must be approved by a specified approver or approvers
who are defined in the vDC. You have an option to define two approvers for a group.
Note
•
Once created, the service request workflow has a step requiring VM approval that shows the
approver’s name.
•
A service request notification email is sent to the approver(s). The approver(s) are able to see all
requests under the Approvals tab.
•
Once approved, the next step, VM provisioning, is initiated.
See more information about defining approvers in Chapter 7 “Managing Virtual Data Centers”.
Approving a Service Request
Step 1
Click Organizations > My Approvals.
Step 2
Choose the My Approvals tab.
Step 3
Choose the service request entry to approve.
Step 4
To verify the details, click View Details.
Step 5
Click Approve.
Step 6
Add comments in the Service Request dialog box if necessary.
Step 7
Click Approve.
Rejecting a Service Request
Step 1
Click Organizations > My Approvals.
Step 2
Choose the My Approvals tab.
Step 3
Choose the service request entry to reject.
Step 4
Verify the details by clicking View Details.
Step 5
Click Reject.
Step 6
Add comments in the Service Request dialog box if necessary.
Step 7
Click Reject.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
10-9
Chapter 10
Using Self-Service Provisioning
Service Request Budgeting
Viewing the Service Requests Approvals History
Step 1
Click Organizations > My Approvals.
Step 2
Choose the My Approvals tab. All approvals that are either already approved or pending approval are
listed.
Searching the Service Request Approvals History
Step 1
Click Organizations > My Approvals.
Step 2
Choose the My Approvals tab.
Step 3
In the Search field, enter the search term.
Exporting Service Request Approvals History
Step 1
Click Organizations > My Approvals.
Step 2
Choose the My Approvals tab.
Step 3
Choose the Group Name from the list.
Step 4
Click the Export Report icon on the right of the toolbar.
Step 5
In the Export Report dialog box, choose the report format: PDF, CSV, or XLS.
Step 6
Click Generate Report.
Service Request Budgeting
Viewing the Current Month Budget Availability
Step 1
Click Organization > Service Requests.
Step 2
From the left panel, choose either All User Groups or a specific user group.
Step 3
Choose the Current Month Budget Availability tab.
Cisco UCS Director Administration Guide, Release 4.0
10-10
OL-30149-02
Chapter 10
Using Self-Service Provisioning
Service Request Budgeting
Viewing Budget Entries
Step 1
Click Organizations > Summary.
Step 2
From the left panel, choose a user group.
Step 3
Choose the Budget Entries tab.
Adding a Budget Entry
Step 1
Click Organizations > Summary.
Step 2
From the left panel, choose a user group.
Step 3
Choose the Budget Entries tab.
Step 4
Click Add (+).
Step 5
In the Add Budget Entry dialog box, complete the following fields:
Name
Description
Entry Name field
The name of the budget entry.
Budget Amount field
The amount of the budget per month.
Year drop-down list
Choose the year.
Month drop-down list
Choose the month.
Repeat Entries
drop-down list
Choose the number of months for the same amount of budget to repeat.
Step 6
Click Add.
Editing a Budget Entry
Step 1
Click Organizations > Summary.
Step 2
From the left panel, choose a user group.
Step 3
Choose the Budget Entries tab.
Step 4
In the main page, choose the budget entry.
Step 5
Click Edit.
Step 6
In the Edit Budget Entry dialog box, complete the following fields:
Name
Description
Entry Name display-only
field
The name of the budget entry.
Group display-only
drop-down list
Choose the name of the group.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
10-11
Chapter 10
Using Self-Service Provisioning
Service Request Budgeting
Name
Description
Budget Amount field
The amount of the budget per month.
Year display-only
drop-down list
Choose the year.
Month display-only
drop-down list
Choose the month.
Repeat Entries display-only Choose the number of months for the same amount of budget to repeat.
drop-down list
Step 7
Click Save.
Deleting a Budget Entry
Step 1
Click Organizations > Summary.
Step 2
From the left panel, choose a user group.
Step 3
Choose the Budget Entries tab.
Step 4
In the main page, choose the budget entry.
Step 5
Click Delete (X).
Step 6
Confirm the deletion in the Delete Entry dialog box.
Cisco UCS Director Administration Guide, Release 4.0
10-12
OL-30149-02
CH A P T E R
11
Multiple Disk VM Provisioning
This chapter contains the following sections:
Note
•
About Multiple Disk VM Provisioning, page 11-1
•
Workflow for Multiple Disk VM Provisioning, page 11-2
•
About Templates with Multiple Disks, page 11-2
•
Defining the Storage Policies, page 11-2
•
Creating a Catalog, page 11-4
•
Creating a VM Disk, page 11-7
You must be logged in to the appliance before you can run any of the following procedures.
About Multiple Disk VM Provisioning
Cisco UCS Director v4.0 supports VM provisioning of multiple disks from a template. You can configure
VM disk provisioning on a preferred single datastore or multiple datastores. You can also configure
individual disk policies for each additional disk in a template.
Cisco UCS Director classifies the disks into five categories:
Note
•
System
•
Data
•
Database
•
Swap and
•
Log
The disk categories that are defined by Cisco UCS Director are for disk labeling only.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
11-1
Chapter 11
Multiple Disk VM Provisioning
Workflow for Multiple Disk VM Provisioning
Workflow for Multiple Disk VM Provisioning
The following step show how to provision a multiple disk VM.
Step 1Check for the availability of a template with multiple disks
Step 2Assign disk categories
Step 3Define the storage policy
Step 4Create the template catalog.
About Templates with Multiple Disks
To provision a multiple disk VM, a template (image) with multiple disks, must be available . Before
using a template with multiple disks for VM provisioning, you must assign the disk categories for
individual disks.
Assigning Disk Categories
Step 1
Click Virtual > Compute.
Step 2
Choose a VMware cloud and choose the Images tab.
Step 3
Choose a template with multiple disks.
Step 4
Click the View Details button on the toolbar.
Step 5
Click the Disks tab.
Step 6
Choose a disk.
Step 7
Click Assign Disk Type.
Step 8
Choose the disk type (System, Data, Database, Swap, or Log).
Step 9
Click Submit.
Note
You should assign at least one disk as the system disk.
Defining the Storage Policies
The storage policy defines resources such as datastore scope, type of storage to use, minimum conditions
for capacity, latency, and so on. The storage policy also provides an option for you to configure the
additional disk policies for multiple disks and an option to provide datastore choices for the end user
during a service request creation.
Cisco UCS Director Administration Guide, Release 4.0
11-2
OL-30149-02
Chapter 11
Multiple Disk VM Provisioning
Defining the Storage Policies
Cisco UCS Director supports VM provisioning with multiple disks on multiple datastores. There are five
types: System, Data, Database, Swap, and Log. The System disk policy is configured first, and the other
disks are configured later depending on the requirements. You can configure the disk policy individually
for each disk type or choose the default system disk policy for each disk.
When using the additional disks policies, be sure to uncheck the Provision all disks in a single
datastore option during catalog creation for the multiple disk template. For more information about
catalog creation, see “Creating a Catalog”.
In addition, Cisco UCS Director supports datastore selection during the creation of a service request for
VM provisioning by providing you with an option to enable or disable datastore selection for the end
user. The datastores listed for selection depend upon the scope conditions specified in the storage policy
associated with the vDC that was chosen during the creation of the service request.
Creating a Storage Policy
Step 1
Click Policies > Storage.
Step 2
Choose the VMware Storage Policy tab.
Step 3
Click Add (+).
Step 4
In the Add Storage Resource Allocation Policy- System Disk Policy dialog box, complete the
following fields:
Name
Description
Policy Name field
The name of the policy. This name is used during catalog definition.
Policy Description field The description of the policy.
Cloud Name drop-down Choose the cloud in which resource allocation occurs.
list
System Disk Scope
Data Stores Scope
drop-down list
Choose the scope of deployment. Specify whether to use all, include chosen, or
exclude chosen.
Use Shared Data Store
only check box
Check the check box to use shared datastores only.
Storage Options
Use Local Storage
check box
Check the check box to use local storage. By default the field is checked.
Use NFS check box
Check the check box to use NFS storage. By default, the field is checked.
Use SAN check box
Check the check box to use SAN storage. By default, the field is checked.
Minimum Conditions
check box list
Check the check boxes of one or more conditions that should match. Hosts or
datastores that do not meet these criteria are excluded from consideration. If more
than one condition is chosen, then all chosen conditions must match.
Override Template
check box
Check the check box to override the template properties. You are provided with
options to enter custom settings such as using thin provisioning and custom disk size.
Use Thin Provisioning
check box
Check the check box to use thin provisioning during VM storage provisioning.1
Note
Thin provisioning enables dynamic allocation of physical storage capacity to
increase VM storage utilization.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
11-3
Chapter 11
Multiple Disk VM Provisioning
Creating a Catalog
Name
Description
Custom Disk Size
A custom disk size that will override the disk size of the template used for VM
provisioning.1
Resize Options for VM Lifecycle
Allow Resizing of Disk Check the check box to provide an option to choose VM disk size before
provisioning.
Permitted Values for
Disk in GB field
The disk size values for provisioning a VM.2
Allow user to select
datastore from scope
check box
Check the check box to provide the user an option to choose the datastore during the
service request creation.
1. This option appears when Override Template is checked.
2. This option appears when Allow resize of disk is checked.
Step 5
Click Next.
Step 6
In the Additional Disk Policies pane, choose a disk type to configure.
Note
By default the disk policy for the disk is System Disk Policy.
Step 7
Click the Pencil icon and the Edit Disk Policies Entry dialog box appears.
Step 8
To configure the disk policy, uncheck the Same as System Disk Policy check box.
Step 9
In the Edit Entry dialog box, choose the Disk Scope and Storage Options for the disk type.
Step 10
Click Submit.
Step 11
Continue to configure the other disk types as needed.
Step 12
Click Submit.
Note
To use the storage policy created with additional disk policies, you must associate the policy with
the vDC that is used for the VM provisioning.
Creating a Catalog
Adding a Catalog
Step 1
Click Policies > Catalogs.
Step 2
Choose the Catalog tab.
Step 3
Click Add (+).
Cisco UCS Director Administration Guide, Release 4.0
11-4
OL-30149-02
Chapter 11
Multiple Disk VM Provisioning
Creating a Catalog
Step 4
In the Create Catalog-Basic Information dialog box, complete the following fields:
Name
Description
Catalog Name field
The name of the catalog.
Catalog Description
field
The catalog description.
Catalog Type
drop-down list
Choose from Standard (default). Advanced, Service Container, or VDI.
Catalog Icon drop-down Choose the icon that represents the OS.
list
Applied to all groups
check box
Check the check box to apply the catalog to all groups.
Selected Groups button
If the Applied to all groups check box is left unchecked, this button displays the
Select Items dialog box, which lists all groups. Choose the Check All or Check
None buttons or check the individual check boxes for the applicable group(s).
Cloud Name drop-down Choose the cloud. The cloud item that is created or updated is from this cloud.
list
Image drop-down list
Choose the image. The this is the image for the cloud item that is created or updated.
Provision all disks in a
single datastore check
box
Check the option to provision all the disks of the VM in a single datastore. Uncheck
the check box to provision the disks of the VM according to the Additional disk
policies configured with the individual disk preferred datastores as defined in the
storage policy.
Note
If you configured disk polices for the additional disks and then chose the
option to provision all disks in a single datastore, it overrides the additional
disk policies and provision all the VM disks in the same datastore where the
system disk gets provisioned.
Step 5
Click Next.
Step 6
In the Create Catalog-Application Details dialog box, complete the following fields:
Name
Description
Category drop-down list Choose the application category. The application category determines which policies
are used by the vDC where the service is provided. Application categories and
associations with various policies are managed in vDC management.
Support Contact Email
Address field
The support contact email address.
Specify OS drop-down
list
Choose the OS.
Specify Other OS field
Enter an OS that is not found on the drop-down list..
Specify Applications
button
When the button is clicked the Select Items dialog box appears with Check All and
Check None buttons or you may check the individual check box adjacent to the
application(s).
Specify Other
Applications field
Choose the other applications that are used.
Application Code field
The application code used in the VM name. If specified, the value entered must be
from 1 to 4 characters.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
11-5
Chapter 11
Multiple Disk VM Provisioning
Creating a Catalog
Step 7
Click Next and the Create Catalog-User Credentials dialog box appears with the following field:
Name
Description
Credential Options
drop-down list
Choose the VM user credential options. The user credentials for the VM in the
template are shared with users or it is reset before sharing. If shared, the user can
retrieve credentials for the active VM. The drop-down list options are as follows:
•
Do Not Share
•
Share after password reset; requires a userid and password
•
Share template credentials; requires a userid and password.
Step 8
Click Next.
Step 9
In the Customization pane, complete the following fields:
Name
Description
Automatic Guest
Customization check
box
Check the check box to enable automatic configuration of DNS, network and guest
OS properties. Uncheck the check box to disable this feature.
Post Provisioning
Custom Actions check
box
Check the check box to enable the user to specify custom actions. The custom actions
are executed in the workflow after provisioning. Uncheck the check box to disable
this feature.
Cost Computation
VM App Charge
Frequency drop-down
list
Choose Hourly or Monthly for the VM interval cost computation.
Note
The default is Hourly.
Active VM Application The active VM application cost applicable for this catalog.
Cost field
Inactive VM
Application Cost field
The inactive VM application cost applicable for this catalog.
Step 10
Click Next.
Step 11
In the VM Access pane, complete the following fields:
Name
Description
Web Access
Configuration check
box
Check the option to enable access to the VM via a web interface. Uncheck the check
box to disable this feature.
URL field
The URL for web access.
Label field
The action label that the user chooses in the access panel.
Remote Desktop Access Check the option to enable access to the VM via a remote interface. Uncheck the
Configuration check
check box to disable this feature.
box
Step 12
Click Next.
Step 13
In the Summary pane, review the information.
Cisco UCS Director Administration Guide, Release 4.0
11-6
OL-30149-02
Chapter 11
Multiple Disk VM Provisioning
Creating a VM Disk
Step 14
Click either Back (to correct an item) or Submit.
Viewing a Catalog
Step 1
Click Policies > Catalogs.
Step 2
Choose the Catalog tab.
Step 3
Choose a catalog and click View.
Editing a Catalog
Step 1
Click Policies > Catalogs.
Step 2
Choose the Catalog tab.
Step 3
Choose a catalog and click Edit.
Note
The items open to editing are the same as those steps in “Adding a Catalog”.
Cloning a Catalog
Step 1
Click Policies > Catalogs.
Step 2
Choose the Catalog tab.
Step 3
Choose a catalog to clone and click Clone.
Note
The items open to editing are the same as those steps in “Adding a Catalog”. A name change is
required, but you can otherwise retain all the settings of the original catalog.
Creating a VM Disk
Note
You can add an additional disk with a custom size to provisioned or discovered VMs using the Create
VM disk option available through the VM action button.
Step 1
Click Virtual > Compute.
Step 2
From the left side pane, choose a cloud name.
Step 3
Choose the VMs tab.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
11-7
Chapter 11
Multiple Disk VM Provisioning
Creating a VM Disk
Step 4
Choose a VM from the list.
Step 5
At the right side of the toolbar click the down arrow and a drop-down list of VM options will open.
Step 6
Choose Create VM Disk.
Step 7
In the Create VM Disk dialog box, complete the following fields:
Name
Description
VM Name
display-only field
The VM name.
New Disk Size (GB) The disk size for the VM in GB.
field
Select a disk type
drop-down list
Choose the disk label. The choices are as follows:
•
System
•
Swap
•
Data
•
Database
•
Log
Select Datastore
drop-down list
Choose the datastore. The datastores choice depends on the storage policy that is
associated with the VM’s vDC.
Thin Provision
check box
Check the check box to add a thin provisioned disk to the VM.
Step 8
Note
Thin provisioning enables dynamic allocation of physical storage capacity to
increase VM storage utilization.
Click Create.
Cisco UCS Director Administration Guide, Release 4.0
11-8
OL-30149-02
CH A P T E R
12
Using the Chargeback Module
This chapter contains the following sections:
Note
•
Chargeback Features, page 12-1
•
Budget Policy, page 12-2
•
About Cost Models, page 12-2
•
About Modifying a vDC to Include a Cost Model, page 12-4
•
About Package Based Cost Models, page 12-6
•
About Storage Tier Cost Models, page 12-8
•
Chargeback Reports, page 12-9
•
About Change Records, page 12-11
•
About the Chargeback Calculation, page 12-12
You must be logged in to the appliance before you can run any of the following procedures.
Chargeback Features
The Cisco UCS Director’s Chargeback module offers in-depth visibility into the costs of the virtual
infrastructure. It allows the definition and assignment of cost models to policies within departments and
organizations. VM metering data is collected at frequent intervals to ensure accurate calculation of
resource costs.
Features of the Chargeback module are as follows:
•
Flexibility—Provide fixed costs, onetime costs, allocation costs, usage costs, and a combination of
all, based on the organizational requirements.
•
Re-usable Cost Models—Assign cost models to VMs using standardized cost models or templates.
These templates are used to apply cost models to new environments quickly.
•
Reporting—Generate various summary and comparison reports of costs and resource usage for the
virtual infrastructure. Export reports to (PDF, CSV, and XLS) formats and view within a web
browser.
•
Top 5 Reports—Monitor the top five reports for organizations or groups with highest VM cost, CPU,
memory, storage and network costs.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
12-1
Chapter 12
Using the Chargeback Module
Budget Policy
•
Dashboard—Monitor and analyze VM metering information and chargeback in real time with the
built-in dashboard and extensive set of graphical widgets.
Budget Policy
Overall resources are accounted for by the Chargeback module. In addition to Chargeback, individual
groups or organizations must be associated with a budget policy where you can enable or disable the
budget watch and over budget.
Configuring a Budget Policy
Step 1
Click Administration > Users and Groups.
Step 2
Choose the User Groups tab.
Step 3
Choose a group and click Budget Policy.
Step 4
Check or uncheck the check boxes in the Budget Policy dialog box:
Name
Description
Enable Budget Watch
check box
If checked the group’s budget usage is monitored. If unchecked, all budget entries for
this group are ignored.
Allow Over Budget
check box
If checked the group members are allowed to go over the provisioned budget. If
unchecked once the budget is exhausted all requests are rejected until a new budget
is added.
Step 5
Click Save.
About Cost Models
A cost model is used to define unit level costs of virtual resources such as CPU, RAM, and storage. These
costs are used for chargeback calculations of VMs within the virtual infrastructure. Cost models offer a
definition of costs in a linear model, Costs can be defined at the unit level.
The cost of a particular resource for a VM is calculated based on how many units are assigned to that
VM. For example, the cost of 1 GB of RAM is defined within the cost model and this unit cost is used
to determine the cost of RAM for a particular VM.
You can define one-time provisioning costs, active or inactive VM costs, and provisioned, reserved, or
used costs for resources such as CPU, memory and so on. These costs are used to calculate the VM costs
based on usage.
Creating a Cost Model
Step 1
Click Policies > Service Delivery.
Step 2
Choose the Cost Model tab.
Cisco UCS Director Administration Guide, Release 4.0
12-2
OL-30149-02
Chapter 12
Using the Chargeback Module
About Cost Models
Step 3
Click Add (+).
Step 4
In the Add Cost Model dialog box, choose the Standard option under Cost Model Type drop-down list.
Step 5
Complete the following fields:
Name
Description
Cost Model Name field
The name of the cost model
Cost Model Description The description of the cost model
field
Cost Model Type
drop-down list
Choose the type of cost model. Standard indicates a linear cost model. Advanced
indicates a package or script-based cost model. See the “About Package Based Cost
Models” section for the Advanced cost model description and usage. You can also
choose HyperV, if appropriate.
Charge Frequency
drop-down list
Choose the frequency at which the VM’s resources costs are defined. If you want to
specify the costs of resources on an hourly basis, choose Hourly. If you want to
specify the costs of resources on a monthly basis, then choose Monthly.
Fixed Costs
One Time Cost field
The fixed one-time cost for provisioning the VM.
VM Costs
Active VM Cost field
The per hour cost of a VM in the active state.
Inactive VM Cost field
The per hour cost of a VM in the inactive state.
CPU Costs
CPU Charge Unit
drop-down list
Choose the charge unit for CPU: GHz or cores.
Provisioned CPU Cost
field
The provisioned CPU cost per CPU charge unit per hour.1 The amount of CPU that
was provisioned to the VM is taken into consideration.
Note
Reserved CPU Cost
field
The reserved CPU cost per GHz per hour.1 The amount of CPU that has been actually
reserved to the VM is taken into consideration, including the provisioned CPU cost
calculation. Any extra cost for the reserved CPU (apart from provisioning cost) is
entered here. For example, if the provisioning cost is $1 and reserved cost is $1.4, the
extra amount to reserve must be mentioned. In this example, it is $1.4 – $1 = $0.4.
Note
Used CPU Cost field
If you enter a value for the Used CPU Cost, then this field must be left blank.
If you enter a value for the Used CPU Cost, this field must be left blank.
The used CPU cost per GHz per hour.1 The cost is based on the actual CPU usage.
This cost does not take into consideration the provisioned and reserved costs. If you
enter a value for the Used CPU Cost, the provisioned cost and reserved cost fields
must be left blank.
Memory Costs
Provisioned Memory
Cost field
The provisioned memory cost per GB per hour.2
Reserved Memory Cost The reserved memory cost per GB per hour.2
field
Used Memory Cost
field
The used memory cost per GB per hour.2
Network Costs
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
12-3
Chapter 12
Using the Chargeback Module
About Modifying a vDC to Include a Cost Model
Name
Description
Received Network Data The received data cost per GB per hour.
Cost field
Transmitted Network
Data Cost field
The transmitted data cost per GB per hour.
Storage Costs
Committed Storage
Cost field
The committed storage cost per GB per hour.
Uncommitted Storage
Cost field
The uncommitted storage cost per GB per hour. The unused but provisioned storage
is defined as uncommitted storage.
1. The cost if the CPU charge unit is GHz.
2.
The memory cost calculation is done in a similar manner to the CPU cost calculation.
Step 6
Click Add.
About Modifying a vDC to Include a Cost Model
You can add or edit an existing vDC to assign it the newly created cost model. You can edit an existing
vDC or a new vDC can be created and have a cost model assigned to it.
After the cost model is assigned to a vDC, all VMs within the vDC are charged based on the advanced
cost model. Any VMs within vDCs that have the standard type of cost model are still charged according
to the standard cost model.
Adding a vDC to a Cost Model
Step 1
Click Policies > Virtual Data Centers.
Step 2
Choose the vDC tab.
Step 3
Choose the vDC to add to the cost model.
Step 4
Click Add (+).
Step 5
In the Add vDC dialog box, complete the following fields:
Name
Description
vDC Name field
The name of the vDC.
vDC Locked check box Check the check box to deny the use of the vDC for any further deployments. Actions
on existing VMs, within this vDC, are disabled. Uncheck the check box to allow the
use of the vDC for further deployments.
vDC Description field
The vDC specific description.
Group drop-down list
Choose the group for which the vDC is being set up.
Cloud Name drop-down Choose the cloud on which the vDC is being set up.
list
Approvers and Contacts
Cisco UCS Director Administration Guide, Release 4.0
12-4
OL-30149-02
Chapter 12
Using the Chargeback Module
About Modifying a vDC to Include a Cost Model
Name
Description
First Approver User
Name field
The user who must approve the service request.
Second Approver User
Name field
The second user who must approve the service request.
Provider Support Email The contact or user’s email address. The person who is notified about VM
Address field
provisioning using this vDC.
Copy Notifications to
Email Address field
The second contact’s email for copying notifications about vDC.
Policies
System Policy
drop-down list
Choose the system policy applicable to the vDC.
Computing Policy
drop-down list
Choose the computing policy applicable to the vDC.
Network Policy
drop-down list
Choose the network policy applicable to the vDC.
Storage Policy
drop-down list
Choose the storage policy applicable to the vDC.
Cost Model drop-down
list
Choose the cost model applicable to the vDC.
Disable displaying cost
in the SR summary and
email page check box
Check the check box to disable displaying cost in the SR summary and email page
for this vDC.
User Action Policy
drop-down list
Choose the policy that is used for execution of orchestration workflow postprovisioning of the VMs. The chosen workflow appears as an action button for VMs
within the vDC.
End User Self-Service Policies
VM Power
Check the check box to enable all VM power management actions for VMs belonging
Management check box to this vDC.
Step 6
Click Add.
Editing a vDC to Include a Cost Model
Step 1
Click Policies > Virtual Data Centers.
Step 2
Choose the vDC tab.
Step 3
Choose the vDC to add the cost model.
Step 4
Click Manage Categories.
Step 5
Choose the category to edit.
Step 6
Click Edit.
Step 7
In the Edit App Category dialog box, in the drop-down list, choose a Cost Model and a Deploy Policy.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
12-5
Chapter 12
Using the Chargeback Module
About Package Based Cost Models
Step 8
Click Save.
About Package Based Cost Models
A package based cost model allows you to define costs for the system resources as packages instead of
as individual definitions. There are different packages to choose from based on your requirements. This
type of cost model is suitable for non-linear models.
Note
Cisco UCS Director supports definitions of CPU memory (server) packages.
In this type of cost model, the definition is based on the available resource packages. The model is in the
following format:
C – M:X.
C is the number of CPU cores.
M is the memory in GB.
X is the combined monthly cost of C and M.
For example, a package with entry: 2-4:200 implies: CPU cores = 2, memory = 4 GB, and the cost of
this package is $200 per month.
You can define multiple packages using the following format: C1-M1:X1,C2-M2:X2,......,CN-MN:XN.
For example, 1-1:50,1-2:70,1-4:90,2-4:150,2-6:170,2-8:190,4-8:350,4-12:380,4-16:400. The first entry
1-1:50 is a package of 1 core CPU and 1 GB memory that costs $50 per month.
Note
These entries can be edited at any time to suit the cost package requirements.
Creating a Package Based Cost Model
Step 1
Click Policies > Service Delivery.
Step 2
Choose the Cost Model tab.
Step 3
Click Add (+) to create a new cost model.
Step 4
Under the Cost Model Type field, choose the Advanced option.
Step 5
Paste the script provided in the Advanced Cost Model field.
/********************************/
var CPU_MEMORY_COST =
1-2:81,1-4:95,1-8:109,2-4:162,2-6:176,2-8:189,2-16:378,4-12:352,4-16:378;
/********************************/
/* define cost packages as shown above.
The cost packages can be defined in the following format:
C-M:X.
Cisco UCS Director Administration Guide, Release 4.0
12-6
OL-30149-02
Chapter 12
Using the Chargeback Module
About Package Based Cost Models
C is the number of CPU cores.
M is the memory in GB.
X is the combined monthly cost of C and M.
For example, 2-4:162 means CPU cores = 2, memory = 4 GB and cost of this package is $162 per month.
*/
/* When defining multiple packages define it in the following format: C1-M1:X1,C2-M2:X2,
...........,CN-MN:XN
The standard packages are defined at the top of the script using the variable CPU_MEMORY_COST.
This variable can be edited to suit the cost package requirement. */
/* For reference, the storage cost to use is based on the storage tier cost model definition. */
/* do not edit any script below */
computeChargeback(data);
function computeChargeback(data)
{
var map = chargeBackAPI.getCPUMemCostModelMap(CPU_MEMORY_COST);
var cpuCores = data.getVmMeter().getCpuCores();
var memory = data.getVmMeter().getAllocMemGB();
var serverCost = chargeBackAPI.getCostForItem(map,cpuCores, memory);
serverCost = serverCost / (24 * 30);
var storageTierCost = chargeBackAPI.getStorageCostForItem(data.getVmMeter().getVmId());
var storageGB = (data.getVmMeter().getCommittedDiskGB()) +
(data.getVmMeter().getUncommittedDiskGB());
var committedDiskGBCost = (data.getVmMeter().getCommittedDiskGB()) * storageTierCost;
var unCommittedDiskGBCost = (data.getVmMeter().getUncommittedDiskGB()) * storageTierCost;
var storageCost = (storageGB * storageTierCost) / (24 * 30);
var totalVMCost = serverCost + storageCost;
var cb = data.getCbSummary();
cb.setCpuCores(cpuCores);
cb.setMemory(memory);
cb.setServerCost(serverCost);
cb.setCommittedDiskGB(data.getVmMeter().getCommittedDiskGB());
cb.setCommittedDiskGBCost(committedDiskGBCost);
cb.setUncommittedDiskGB(data.getVmMeter().getUncommittedDiskGB());
cb.setUncommittedDiskGBCost(unCommittedDiskGBCost);
cb.setTotalCost(totalVMCost);
}
/* *********************************/
Step 6
Click Add.
Note
Once the cost model has been defined, assign it to a vDC in order to start the chargeback of VMs
based on this cost model.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
12-7
Chapter 12
Using the Chargeback Module
About Storage Tier Cost Models
About Storage Tier Cost Models
You can use storage tier cost model to define multiple costs for storage using the tier format. Current
storage types include local, NFS, SAN, and NAS, andy others. Each storage type cost could vary and
you can incorporate this variation while calculating costs for storage usage.
You can use this model to define different costs for different tiers and then assign existing datastores to
these tiers. You can group similar datastore types by cost wise using the tier cost model.
Each tier must be assigned a cost. This cost is per GB per month. For example, when assigning $ 0.5 to
a tier, all datastores within this tier are charged at $ 0.5 per GB per month. By default, four tiers are
already created, you must assign the costs to them.
Assigning a Cost to a Tier
Step 1
Click Policies > Service Delivery.
Step 2
Choose the Storage Tier Cost Model tab.
Step 3
Choose the tier to edit.
Step 4
Click Edit.
Step 5
Edit the Disk Cost (GB)/Month field.
Step 6
Click Submit.
About Assigning a Datastore to Tiers
You can assign a datastore to a tier so that the cost defined in the tier is used to calculate the cost of
storage within that particular datastore.
When calculating the chargeback for VMs within a datastore, the cost is determined by which tier the
datastore was assigned to. If no tier is assigned to a datastore, the storage cost for that datastore is not
considered when using the advanced (script) based cost model.
When using a regular cost model, where you define the resource costs in a form, storage tier costs are
taken into consideration if tier costs are assigned and datastores are assigned to those tiers. However, if
no tier is assigned to a datastore, the storage cost for VMs under that datastore is taken from the storage
cost entry of the cost model form.
Note
Assigning a datastore to a tier applies only to the regular cost model.
Assigning a Datastore to a Tier
Step 1
Click Virtual > Storage.
Step 2
From the left panel, choose the cloud account.
Step 3
Choose the Datastore Capacity Report tab.
Cisco UCS Director Administration Guide, Release 4.0
12-8
OL-30149-02
Chapter 12
Using the Chargeback Module
Chargeback Reports
Note
Currently the tier based cost is supported only on VMware cloud accounts.
Step 4
Choose the datastore to assign a tier.
Step 5
Click Assign Tier and the Storage Tier dialog box appears.
Step 6
From the drop-down list, choose a tier.
Step 7
Click Submit.
Chargeback Reports
Chargeback provides information about how much organizations are paying for resources, both used and
unused. This feature allows you to optimize resource consumption and costs. The system resources
accounting can be based on monthly usage. Resources such as CPU and memory usage, are monitored
and measured.
Chargeback reports are based on the type of the cost model. Chargeback is calculated and shown in the
form of tabular reports, summaries, graphical reports, and widgets.
The report types are as follows:
•
Viewing
– Current month summary—The current month summary cost report (VM, CPU, storage costs,
and so on.) by groups.
– Previous month summary—The previous month summary cost report (VM, CPU, storage costs,
and so on) by groups.
– Monthly resource accounting details—The resource accounting details (CPU and Memory
usage statistics) for each group on a monthly basis.
– VM level resource accounting details—The resource accounting details at the VM level.
– VM level chargeback details—The charges that are applicable for VM usage using the
Chargeback feature.
•
Export
– Export monthly resource accounting details—Reports of resource accounting details can be
exported as tables.
– Export VM level resource Accounting details—Reports of VM level resource accounting details
can be exported as tables.
– Export VM level chargeback details—Chargeback reports can be exported as tables.
Viewing a Current Month Summary
Step 1
Click Organizations > Chargeback.
Step 2
From the left panel, choose the group to view.
Step 3
Choose the Current Month Summary tab to view the month’s chargeback details for all VMs that
belong to the group.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
12-9
Chapter 12
Using the Chargeback Module
Chargeback Reports
Viewing the Previous Months Summary
Step 1
Click Organizations > Chargeback.
Step 2
From the left panel, choose the group to view.
Step 3
Choose the Previous Month Summary tab to view the previous month’s chargeback details for all VMs
that belong to the group.
Viewing the Monthly Resource Accounting
Step 1
Click Organizations > Chargeback.
Step 2
Choose the group to view from the left hand column.
Step 3
Choose the Resource Accounting tab.
Viewing the VM Level Resource Accounting Details
Step 1
Click Organizations > Chargeback.
Step 2
From the left panel, choose the group to view.
Step 3
Choose the Resource Accounting Details tab to view the individual VMs resource usage details.
Viewing the VM Level Chargeback Details
Step 1
Click Organizations > Chargeback.
Step 2
From the left panel, choose the group to view.
Step 3
Choose the Chargeback tab.
Exporting the Monthly Resource Accounting Details
Step 1
Click Organizations > Chargeback.
Step 2
Choose the Resource Accounting tab.
Step 3
Click the Export Report icon on the right side of the toolbar and the Export Report dialog box appears.
Step 4
From the drop-down list, choose a format:PDF, CSV, or XLS.
Cisco UCS Director Administration Guide, Release 4.0
12-10
OL-30149-02
Chapter 12
Using the Chargeback Module
About Change Records
Step 5
Click Generate Report.
Exporting the VM Level Resource Accounting Details
Step 1
Click Organizations > Chargeback.
Step 2
Choose the Resource Accounting Details tab.
Step 3
Click the Export Report icon on the right side of the toolbar and the Export Report dialog box appears.
Step 4
From the drop-down list, choose a format: PDF, CSV, or XLS.
Step 5
Click Generate Report.
Exporting the VM Level Chargeback Details
Step 1
Click Organizations > Chargeback.
Step 2
Choose the Chargeback tab.
Step 3
Click the Export Report icon on the right side of the toolbar and the Export Report dialog box appears.
Step 4
From the drop-down list, choose a format: PDF, CSV, or XLS.
Step 5
Click Generate Report.
Note
When using the advanced (script) based cost model, CPU and memory costs are combined as one server
cost and displayed in the chargeback report. Storage costs are calculated based on the VM’s datastore
tier cost.
About Change Records
You can use change records within the Change Management Database (CMDB) to track and manage
changes in the system. These records typically display ADD, DELETE, and MODIFY type of events on
any resource, such as a VM, service request, groups, and so on.
Change records display information about the resource type (VM) including the resource name, change
type, change time, and description.
In the case of VM resizes, information is provided about resources of the VMs that were resized and also
about previous and resized resource values.
When a VM has been resized, such changes are recorded and displayed under the Change Records tab.
Accessing Change Records
Step 1
Click Administration > Integration.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
12-11
Chapter 12
Using the Chargeback Module
About the Chargeback Calculation
Step 2
Choose the Change Records tab.
About the Chargeback Calculation
The total cost calculated for a VM includes the following:
Total Cost = active VM cost or inactive VM cost + one-time cost + CPU cost + memory cost + disk cost
+ CPU reserved cost + memory reserved cost + CPU used cost + CPU core cost + memory used cost +
network received used cost + network transmitted used cost + application cost
The VM cost calculation is done only on an hourly basis. The cost for each resource is calculated based
on the values defined in the cost model. The cost calculations are based as follows:
•
Active VM Cost = Cost value that is defined in the cost model for the active VM cost.
•
Inactive VM Cost = Cost value that is defined in the cost model for the inactive VM cost.
•
One Time Cost = Cost value that is defined in the cost model for the one-time cost.
•
CPU Cost = CPU usage (provisioned) × cost that is defined in the cost model for the provisioned
CPU cost.1
•
Memory Cost = Memory usage (provisioned) × cost that is defined in the cost model for the
provisioned memory cost.2
•
Disk Cost = (committed storage × committed storage cost that is defined in the cost model) +
(uncommitted storage × uncommitted storage cost that is defined in the cost model).3
•
CPU Reserved Cost = Reserved CPU × cost that is defined in the cost model for the reserved CPU
cost.1
•
Memory Reserved Cost = Reserved memory × cost that is defined in the cost model for the reserved
memory cost.2
•
CPU Used Cost = Used CPU × cost that is defined in the cost model for the used CPU cost.1
•
CPU Core Cost = Used CPU core × cost that is defined in the cost model for the CPU core cost.4
•
Memory Used Cost = Used memory × cost that is defined in the cost model for the used memory
cost.2
•
Network Received Used Cost = (Network received usage in KB / (1024.0 × 1024.0)) × cost that is
defined in the cost model for the received network data cost.5
•
Network Transferred Used Cost = (Network transmitted usage in KB / (1024.0 × 1024.0)) × cost
that is defined in the cost model for the transmitted network data cost.5
•
Application Cost = (active VM hours × cost that is defined in a catalog for active VM application
cost. ) + (inactive VM hours × cost that is defined in a catalog for the inactive VM application cost).
1. The CPU charge unit is GHz.
2. The memory charge unit is GB.
3. The storage charge unit is GB.
4. The CPU charge unit is per core.
5. The network charge unit is GB.
Cisco UCS Director Administration Guide, Release 4.0
12-12
OL-30149-02
CH A P T E R
13
System Monitoring and Reporting
This chapter contains the following sections:
Note
•
Dashboard, page 13-1
•
Summary, page 13-2
•
Inventory Management, page 13-3
•
Resource Pools, page 13-3
•
Clusters, page 13-3
•
Images, page 13-4
•
Host Nodes, page 13-4
•
VMs, page 13-4
•
Topology, page 13-5
•
Assessment, page 13-5
•
Reports, page 13-5
You must be logged in to the appliance before you can run any of the following procedures.
Dashboard
The dashboard is the first page that you see when you log in. Any report widget in the application can
be added to the Dashboard. You can enable the Dashboard (in the top level menu) for adding important
and favorite report widgets.
Enabling the Dashboard
Step 1
At the top right of the page, click admin.
Step 2
Choose the Dashboard tab.
Step 3
Check the check box Enable Dashboard.
Step 4
Click Apply.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
13-1
Chapter 13
System Monitoring and Reporting
Summary
Adding Report Widgets
Step 1
Click Virtual > Compute.
Step 2
From the left panel, choose the cloud name.
Step 3
Choose the tab with the type of report you want to view.
Step 4
Click the down arrow at the top right of a report.
Step 5
Choose Add to Dashboard.
Refresh Widget Data
You can set refresh to automatic or manual for report widget data. For automatic refresh you have an
option to customize the automatic refresh from 5 to a maximum of 60 minutes.
The Automatic Refresh button on the Dashboard should be set to ON to configure the time.
Summary
The Summary page allows you to manage system inventory. It gives you access to a wide array of tabular,
graphical, and map reports, and also helps in managing inventory life cycle actions.
Each of the reports is displayed as a widget and can be hidden by customization.
Summarizing
Step 1
Click Virtual > Compute.
Step 2
Choose the Summary tab.
Customizing Summary Report Widgets
Step 1
Click Virtual > Compute.
Step 2
Choose the Summary tab.
Step 3
Click the Customize icon to bring up the available report widgets.
Step 4
Click and drag a widget onto the dashboard.
Step 5
Double-click the report to expand the view, or click the top right side of a report and choose Expand
View.
Step 6
Adjust the size of the reports displayed on the Dashboard by using the slide bar.
Cisco UCS Director Administration Guide, Release 4.0
13-2
OL-30149-02
Chapter 13
System Monitoring and Reporting
Inventory Management
Inventory Management
You can monitor system inventory using the Dashboard. Any changes to the physical infrastructure are
updated to the dashboard. The dashboard displays the entire system level infrastructure information for
administrative management.
Accessing System Inventory Details
Step 1
Click Virtual > Compute.
Step 2
From the left panel, choose the cloud name.
Step 3
Choose any of the tabs for detailed information.
Resource Pools
The Resource Pools tab shows resource details at the host node level. These details include the CPU
configured reservation, CPU limit, CPU used, memory used, and so on.
Accessing Resource Details
Step 1
Click Virtual > Compute.
Step 2
From the left panel, choose the cloud name or choose All Clouds.
Step 3
Choose the Resource Pools tab.
Clusters
The Clusters tab displays all the clusters and their details, if available on the data center.
Accessing Clusters
Step 1
Click Virtual > Compute.
Step 2
Choose the Clusters tab.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
13-3
Chapter 13
System Monitoring and Reporting
Images
Images
The Images tab displays all available image IDs and its details. These images include guest OS, CPU,
memory and storage provisioned. You can use these image IDs to provision new VMs.
Accessing Images
Step 1
Click Virtual > Compute.
Step 2
Choose the Images tab.
Host Nodes
The Host Nodes tab displays all physical host nodes that are available in the infrastructure. You can see
details such as the ESX/ESXi version installed, active VMs, power status, and so on.
Accessing Host Nodes
Step 1
Click Virtual > Compute.
Step 2
Choose the Host Nodes tab.
Step 3
From the drop-down list, choose a Report type on the toolbar.
VMs
The VMs tab displays all the VMs and VM specific details for the chosen cloud.
Accessing VMs
Step 1
Click Virtual > Compute.
Step 2
Choose the VMs tab.
Accessing Group Level VMs
Step 1
Click Organizations > Virtual Resources.
Cisco UCS Director Administration Guide, Release 4.0
13-4
OL-30149-02
Chapter 13
System Monitoring and Reporting
Topology
Step 2
Choose a group from the left panel and then choose the VMs tab.
Topology
The Topology tab displays VMware cloud topology. There are four view mode types: Hierarchical,
Concentric, Circular, and Force Directed. Depending on the view mode you choose, you can adjust the
item spacing, distance, radius, rigidity, and force distance.
Accessing Topology Types
Step 1
Click Virtual > Compute.
Step 2
From the left panel, choose the cloud name.
Step 3
Choose the Topology tab.
Step 4
Choose one of the topology types: Hostnode-Datastore Topology, or Hostnode-VM Topology.
Step 5
Click the View Connectivity button on the toolbar and the topology appears in a new page.
Note
Not all of the topology types display.
Assessment
The Assessment tab displays assessment reports, including cloud readiness, virtualization best
practices, performance optimization, capacity, and power optimization.
Accessing Assessments
Step 1
Click Virtual > Compute.
Step 2
From the left panel, choose the cloud name.
Step 3
Choose the Assessment tab.
Step 4
From the Report drop-down list, choose a report type.
Reports
Cisco UCS Director can monitor the virtual infrastructure and system resources by displaying a wide
array of reports. These reports help you to understand system details and provide an insight into how the
system is performing.
Report types include:
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
13-5
Chapter 13
System Monitoring and Reporting
Reports
•
Tabular reports for system information, including overview, host nodes, new VMs, and deleted VMs.
•
Bar and pie graph comparisons, including VMs active versus. inactive, CPU provisioned versus
capacity, and so on.
•
Trend graphs about system resources, including CPU trends, memory trends, VM additions and
deletions, and so on.
•
Other reports include Top 5 reports at the group, vDC, host node, and VM level. The Top 5 reports
are groups with the highest number of VMs, groups with the greatest CPU usage, vDCs with the
highest number of VMs, host nodes with the greatest CPU usage, and so on.
•
Map reports display the system resource information in the form of heat maps or color coded maps.
Accessing Reports
Step 1
Click Virtual > Compute.
Step 2
From the left panel, choose the cloud name.
Step 3
Choose the tab with the type of report (Map, Top 5, or More Reports).
Cisco UCS Director Administration Guide, Release 4.0
13-6
OL-30149-02
CH A P T E R
14
Managing Life Cycles
This chapter contains the following sections:
Note
•
Managing VM Power Settings, page 14-1
•
Resizing a VM, page 14-2
•
Managing VM Snapshots, page 14-2
•
Managing Other VM Actions, page 14-5
You must be logged in to the appliance before you can run any of the following procedures.
Managing VM Power Settings
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
To bring up VM actions, choose the VMs tab and right click a VM (wait for the timer to cycle).
Step 4
Choose an action and the VM Task dialog box opens. Complete the last two fields:
Name
Description
VM Name display-only The name of the VM that is the subject of the action.
field
Power Off display-only The task to power off the VM.
field
Power On display-only
field
The task to power on the VM.
Suspend display-only
field display-only field
The task to put the VM in a suspended state.
Shutdown Guest
display-only field
The task to shut down the guest OS on the VM.
Standby display-only
field
The task to move the VM into a standby state.
Reset display-only field The task to perform a hard reset of the VM.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
14-1
Chapter 14
Managing Life Cycles
Resizing a VM
Name
Description
Reboot display-only
field
The task to perform a soft reboot of the VM.
Comments field
The comments.
Schedule Action radio
button
The task to power on a VM now or at a specific date and time.
Step 5
Click Proceed.
Resizing a VM
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Click the Power OFF button on the toolbar and the VM Task dialog box appears.
Step 5
Choose Execute Now and enter any comments.
Step 6
Click Proceed.
Step 7
Click the Resize VM button on the toolbar and the Resize VM dialog box appears. Complete the
following fields:
Name
Description
VM Name display-only The name of the VM.
field
Current Allocated CPU
display-only field
The current CPU on the VM.
Current Allocated
Memory (GB)
display-only field
Displays the current memory on the VM.
New CPU Count
drop-down list
Choose the CPU required.
New Memory
drop-down list
Choose the memory required.
Step 8
Click Resize.
Managing VM Snapshots
This topic covers five tasks:
Cisco UCS Director Administration Guide, Release 4.0
14-2
OL-30149-02
Chapter 14
Managing Life Cycles
Managing VM Snapshots
•
Create Snapshot—You can create a snapshot of all the VM’s resources in their current state, or you
can revert back to a particular snapshot.
•
Revert Snapshot—If the VM crashes or malfunctions (OS becomes corrupt) you can revert back to
the most recent snapshot of the VM, which brings the VM back up and running. In the case where
there are multiple snapshots for a VM, you can revert to a specific snapshot.
•
Mark Golden Snapshot—You can mark a specific snapshot for a VM as a Golden Snapshot. This
feature protects the snapshot from accidental deletion.
•
Delete a Snapshot—You can delete a snapshot if required. If you delete a Golden Snapshot you must
first unmark it before it can be deleted.
•
Delete All Snapshots—You can delete all snapshots for a VM. However, you cannot delete all
snapshots if there are golden snapshots. You must first unmark the Golden Snapshot and then delete
all snapshots.
Creating VM Snapshots
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Create Snapshot and the Create Virtual Machine Snapshot dialog
box appears. Complete the following action fields:
Name
Description
Snapshot Name field
The snapshot name.
Snapshot Description
field
The snapshot description.
Snapshot Memory
check box
Check the check box to include VM memory
Quiesce Guest File
System check box
Check the check box to take the snapshot in quiesce mode.
Step 6
Note
Quiescing a file system is a process of bringing the on-disk data of a physical
or virtual computer into a state suitable for backups. This process may include
operations such as flushing buffers from the operating systems in-memory
cache to disk or other higher-level application-specific tasks. To use this
option, VMware tools must be installed on the VM.
Click Proceed.
Reverting to a Snapshot
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
14-3
Chapter 14
Managing Life Cycles
Managing VM Snapshots
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Revert Snapshot and the Revert Snapshot Task dialog box appears.
Step 6
Choose a snapshot from the list by checking the check box adjacent to the snapshot name.
Step 7
Click Proceed.
Marking a Golden Snapshot
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Mark Golden Snapshot and the Mark Golden Snapshot Task dialog
box appears.
Step 6
Choose a snapshot from the list by checking the check box adjacent to the snapshot name.
Step 7
Check the Mark as Golden Snapshot check box.
Step 8
Click Proceed.
Deleting a Snapshot
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Delete Snapshot and the Delete Snapshot Task dialog box appears.
Step 6
Choose a snapshot from the list by checking the check box adjacent to the snapshot name.
Step 7
Check the Delete Children check box.
Step 8
Click Proceed.
Deleting All Snapshots
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Cisco UCS Director Administration Guide, Release 4.0
14-4
OL-30149-02
Chapter 14
Managing Life Cycles
Managing Other VM Actions
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Delete All Snapshots and the VM Snapshot Task dialog box appears.
Step 6
Enter an optional comment.
Step 7
Click Proceed.
Managing Other VM Actions
The other VM action menus can be brought up by right clicking on a VM for an shortened menu, or for
a complete menu, by highlighting a VM and clicking on the down arrow at the right side of the toolbar.
Other VM actions are as follows:
•
View VM Details—You can access individual VMs to view details such as summary reports, vNICs,
disks, snapshots, and so on.
•
Stack View—You can view stacks of information about a particular VM including OS, hypervisor,
and infrastructure information.
•
Delete a VM—You can delete a VM from the list. Only a powered-off VM can be deleted.
•
Create a VM Disk—You can add an additional disk with a custom size to a VM.
•
Delete a VM Disk—You can delete a disk.
•
Add vNICs—You can add multiple vNICs to a VM. You also have the option to add or replace a
vNIC in a VM. The options for vNICs depends upon the network policy mapped to the vDC that is
associated to the VM.
•
Launch VM Client—You can set up either web access, remote desktop, or VNC console preferences
to a VM.
•
Assign VM—You can assign a VM to a group or vDC and modify the category of the VM. You can
set the provisioning time, termination time, and label for a VM.
•
Access VM Credentials—You can access a VM’s login credentials when it is set up for web or
remote desktop access, but only if the administrator provides the privileges in the catalog from
which the VM is provisioned.
•
Inventory Collection Request for VM—You can choose a VM and request for on-demand inventory
collection for that VM.
Viewing VM Details
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM from the list.
Step 5
Click the View Details button on the toolbar.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
14-5
Chapter 14
Managing Life Cycles
Managing Other VM Actions
Using Stack View
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Click the Stack View button on the toolbar.
Deleting a VM
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Delete VM and the VM Task dialog box appears.
Step 6
Enter an optional comment and schedule the action to execute now or later.
Note
Step 7
If you choose Execute Later, you must specify a time.
Click Proceed.
Creating a VM Disk
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Create VM Disk and the Create VM Disk dialog box appears.
Complete the following fields:
Name
Description
VM Name display-only The name of the VM.
field
New Disk Size (GB)
field
The disk size for the VM in GB.
Choose a disk type
drop-down list
Choose the disk label.
Cisco UCS Director Administration Guide, Release 4.0
14-6
OL-30149-02
Chapter 14
Managing Life Cycles
Managing Other VM Actions
Name
Description
Choose Datastore
drop-down list
Choose a datastore.
Thin Provision check
box
Step 6
Note
The datastore choices that are available depends upon the storage policy that
is associated to the VM (VM’s vDC).
Check the check box to add a thin provisioned disk to the VM.
Note
Thin provisioning enables dynamic allocation of physical storage capacity to
increase VM storage utilization.
Click Create.
Deleting a VM Disk
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Delete VM Disk and the Delete VM Disk dialog box appears.
Step 6
Choose the disk name from the drop-down list.
Step 7
Click Delete.
Adding vNICs
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Add vNICs and the Add VM vNICs page appears.
Step 6
From the Operation drop-down list, choose Add.
Note
This operation is not allowed if the additional vNIC limit configured in the network policy is
exceeded.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
14-7
Chapter 14
Managing Life Cycles
Managing Other VM Actions
Step 7
Click the Add (+) button on the toolbar and the Add Entry to VM Networks dialog box appears.
Complete the following fields:
Name
Description
NIC Alias drop-down
list
Choose a NIC alias from the list.
Port Group Type
Choose a port group from the list.
display-only drop-down
list
Port Group Name
drop-down list
Choose a port group name from the list.
Adapter Type
The adapter type. The choice is available only if the NIC alias does not have Copy
display-only drop-down Adapter Type from Template chosen in the network policy.
list
DHCP display-only
check box
The check box is checked if the IP is assigned using DHCP.
Static IP Pool field
The static IP address pool.
Network Mask field
The network mask.
Gateway IP Address
field
The gateway IP address.
Step 8
Note
The NIC Alias, Port Group Name, Adapter Type, DHCP, and Static IP Pool choices depend
upon the settings in the network policies that are associated with the VM (VM’s vDC). For more
information about multiple NIC network policies, see Chapter 6 “Managing Policies”.
Note
The VM is powered off to perform this action. The VM will powered on once the action is
completed.
Click Submit.
Replacing a vNIC
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Add vNIC and the Add VM vNICs dialog box appears.
Step 6
From the Operation drop-down list, choose Replace.
Cisco UCS Director Administration Guide, Release 4.0
14-8
OL-30149-02
Chapter 14
Managing Life Cycles
Managing Other VM Actions
Step 7
Choose a vNIC and the Add vNIC dialog box appears. Complete the following fields:
Name
Description
NIC Alias drop-down
list
Choose a NIC alias. Only the vNICs configured in the network policy are visible here.
Port Group Name
drop-down list
Choose a port group.
Adapter Type
drop-down list
Choose the adapter type. The choice is available only if the choice of the NIC alias
does not have Copy Adapter Type from Template chosen in the network policy.
DHCP check box
Check the check box if you want the IP assigned using DHCP.
Static IP Pool field
The static IP address pool.
Network Mask field
The network mask.
Gateway IP Address
field
The gateway IP address.
Step 8
Click Submit.
Note
The Replace operation removes all the existing vNICs from the VM and replaces them with the
vNICs that were added. This operation is not allowed if the additional vNIC limit configured in
the Network Policy is exceeded.
Note
The NIC Alias, Port Group Name, Adapter Type, DHCP, and Static IP Pool choices depend
upon the settings in Network Policy that is associated to the VM (VM’s vDC). For more
information about multiple NIC network policies, see Chapter 6 “Managing Policies”.
Note
The VM is powered off to perform this action. The VM is powered on once the action is
completed.
Deleting vNICs
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Delete vNICs and the Delete VM vNICs dialog box appears.
Step 6
Click the Select button and the Select Items dialog box appears.
Step 7
Choose Check All, Check None, or check the check box adjacent to the vNIC to delete.
Step 8
Click Select.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
14-9
Chapter 14
Managing Life Cycles
Managing Other VM Actions
Launching the VM Client
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM.
Step 5
Click the Launch VM Client button on the toolbar and the Launch Client dialog box appears.
Step 6
From the drop-down list, choose an Access Scheme. You can choose Remote Desktop, Web Access, or
VNC Console.
Note
Step 7
The VNC console is an Ajax-based console that has access to a VM. The console page can be
launched by using any standalone web browser. It does not require a dedicated browser plug-in
and it provides full VM control capabilities.
Choose one of the options and click Proceed.
Enabling the VNC Console on a VM
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Configure VNC.
Step 6
Click Submit
Step 7
Click OK.
Note
Cisco UCS Director automatically configures VNC console access to a VM when the request is
submitted.
Accessing the VNC Console Window for a VM
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM.
Step 5
Click the Launch VM Client button on the toolbar and the Launch Client dialog box appears.
Step 6
From the drop-down list, choose VNC Console as the Access Schema.
Step 7
Click Proceed.
Cisco UCS Director Administration Guide, Release 4.0
14-10
OL-30149-02
Chapter 14
Managing Life Cycles
Managing Other VM Actions
Note
The ESX/ESXi server’s VNC ports (from 5900 to 5964) must be open on the hypervisor for a
VMs VNC console access.
Note
Cisco UCS Director provides automatic configuration of the VNC console for a VM. To
configure, you must open the required ports on the hypervisor.
Note
Hypervisors with ESX 4.X and ESXi 5.0 versions are supported to configure VNC console
access.
Assigning a VM
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM.
Step 5
Click the Assign VM button on the toolbar and the Assign VM dialog box appears. Complete the
following fields:
Name
Description
VM Name display-only The name of the VM.
field
User Group drop-down
list
Choose the user group.
vDC drop-down list
Choose the vDC.
Category drop-down list Choose the category for the VM.
VM User Label field
The VM label if required.
Set Provision Time
check box
Check the check box to set a specific provisioning time for the VM.
Provision Date/Time
calendar, drop-down
lists, radio buttons
The VM’s provisioning date and time.1 There are calendars for the Date, drop-down
lists for the Time (hour and minute), and radio buttons for AM or PM.
Set Termination Time
check box
Check the check box to set a specific termination time for the VM.
Termination Date/Time
calendar, drop-down
lists, radio buttons
The VM’s termination date and time.2 There are calendars for the Date, drop-down
lists for the Time (hour and minute), and radio buttons for AM or PM.
Comments field
The comments if required.
1. This option appears when Set Provision Time is checked.
2. This option appears when Set Termination Time is checked.
Step 6
Click Assign.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
14-11
Chapter 14
Managing Life Cycles
Managing Other VM Actions
About VM Credentials
The VM’s web or remote access login credentials can only be viewed if the administrator provides the
the necessary privileges in the Catalog from which the VM is provisioned.
Viewing VM Credentials
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM.
Step 5
Click the Access VM Credentials button on the toolbar.
Using the Inventory Collection Request for a VM
Step 1
Click Virtual > Compute.
Step 2
Choose the cloud name.
Step 3
Choose the VMs tab.
Step 4
Choose a VM and click the down arrow button on the right side of the toolbar.
Step 5
From the drop-down list, choose Inventory Collection.
Step 6
Click Submit.
Cisco UCS Director Administration Guide, Release 4.0
14-12
OL-30149-02
CH A P T E R
15
Managing CloudSense Analytics
This chapter contains the following sections
Note
•
About CloudSense Analytics, page 15-1
•
Generating a Report, page 15-2
•
Generating an Assessment, page 15-2
You must be logged in to the appliance before you can run any of the following procedures.
About CloudSense Analytics
Cisco Director's CloudSense analytics provide visibility into the infrastructure resources utilization,
critical performance metrics across the IT infrastructure stack, and capacity in real time.
CloudSense significantly improves capacity trending, forecasting, reporting, and planning of virtual and
cloud infrastructures.
The following reports can be generated under CloudSense:
•
Storage inventory reports by group
•
Thin provisioning space report
•
Physical infrastructure inventory report by group
•
Organizational usage of the virtual computing infrastructure
•
Billing report by Management Software Provider (MSP)
•
Virtual infrastructure and assets report
•
VM activity report by group
•
NetApp storage inventory report
•
Network impact assessment report
•
Billing report by customer
•
Cisco UCS data center inventory report
•
VMware host performance summary
•
Storage dedupe status report
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
15-1
Chapter 15
Managing CloudSense Analytics
Generating a Report
Generating a Report
Step 1
Click CloudSense > Reports.
Step 2
From the left panel, choose the report.
Step 3
Click Generate Report.
Note
This step generates a new instant report in either HTML or PDF format.
Generating an Assessment
Step 1
Click CloudSense > Assessments.
Step 2
Click Virtual Infrastructure Assessment Report.
Step 3
Click Generate Report.
Note
This step generates a new instant report in either HTML or PDF format.
Cisco UCS Director Administration Guide, Release 4.0
15-2
OL-30149-02
CH A P T E R
16
Using Macros
This chapter contains the following sections:
Note
•
About VM Name Template Customization, page 16-1
•
About VM Template and Hostname Variables, page 16-5
•
About Application Codes, page 16-5
•
About Macro Orchestration, page 16-5
You must be logged in to the appliance before you can run any of the following procedures.
About VM Name Template Customization
The Cisco UCS Director Macro feature allows you to customize a VM name and VM hostname using
variables provided by the application. VM name and VM hostname creation is automated by using the
variables in the system policy.
Cisco UCS Director also allows automatic creation of VM names and VM hostnames during VM
provisioning. The VM name templates and VM hostname templates are available under the VMware
system policy.
Using the VM Name Template
Step 1
Click Policies > Service Delivery.
Step 2
Choose the VMware System Policy tab.
Step 3
Click Add (+).
Step 4
In the Add Policy dialog box, complete the following fields:
Name
Description
Policy Name field
The name of the policy. This name is used during catalog definition.
Policy Description field The description of the policy.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
16-1
Chapter 16
Using Macros
About VM Name Template Customization
Step 5
Choose the VM Name Template variable names. Complete the following fields:
Name
Description
VM Name Template
field
The VM name. VM Names can be automatically created using a set of
variable names. Each variable must be enclosed in ${VARIABLE}.
The VM name template variables are as follows:
•
CLOUD_NAME—The cloud name that is being deployed.
•
GROUP_NAME—The name of the VM group.
•
CATALOG_NAME—The name of the catalog item or entry.
•
USER—Your user ID.
•
SR_ID—The service request ID.
•
COMMENTS—Your comments.
•
PROFILE_NAME—The name of the policy.
•
LOCATION—The name of the location as specified during cloud
creation.
•
UNIQUE_ID—A random ID to make the name unique.
•
APPCODE—The application code that is the value specified during
catalog creation.
•
COST_CENTER—The cost center group or customer organization. It
is specified during the group or customer organization creation.
Step 6
Choose the optional VM Name Template features.
Step 7
Complete the following fields:
Name
Description
# field
The index character. The index character can be added at the end of the VM name
template to create a unique index number for the VM name. It can be given in
multiples. For example, if a VM name template is vm-${GROUP_NAME}##, VM
name is vm-ABCD01 for the first VM provisioned with this policy. The group name
is ABCD and 01 represents ##.
End User VM Name or
VM Prefix check box
Check the check box to enable the option to add a VM suffix name during the creation
of a service request (deployment configuration).
Power On after deploy
check box
Check the check box to automatically power on all VMs deployed using this policy.
Step 8
Choose the Host Name Template variable names.
Cisco UCS Director Administration Guide, Release 4.0
16-2
OL-30149-02
Chapter 16
Using Macros
About VM Name Template Customization
Step 9
Complete the following fields:
Name
Description
Host Name Template field
The hostname. Cisco UCS Director allows automatic creation of VM hostnames.
hostnames can be automatically created using a set of variable names. Each
variable must be enclosed in ${VARIABLE}.
The hostname template variables are as follows:
Step 10.
•
CLOUD_NAME—The cloud name that is being deployed.
•
GROUP_NAME—The name of the VM group.
•
CATALOG_NAME—The name of the catalog item or entry.
•
USER—Your user ID.
•
SR_ID—The service request ID.
•
COMMENTS—Your comments.
•
PROFILE_NAME—The name of the policy.
•
LOCATION—The name of the location as specified during cloud creation.
•
UNIQUE_ID—A random ID to make the name unique.
•
APPCODE—The application code that is the value specified during catalog
creation.
•
COST_CENTER—The cost center group or customer organization. It is
specified during the group or customer organization creation.
Choose the optional Host Name Template features.
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
16-3
Chapter 16
Using Macros
About VM Name Template Customization
Step 11.
Complete the following fields:
Name
Description
# field
The index character. The index character can be added at the end of the VM name
template to create a unique index number for the VM name. It can be given in
multiples. For example, if a VM name template is vm-${GROUP_NAME}##, then
VM name is vm-ABCD01 for the first VM provisioned with this policy. The group
name is ABCD and 01 represents ##.
DNS Domain field
The IP domain to use for the VM.
Time Zone drop-down
list
Choose from the list of available time zones.
DNS Suffix List field
The DNS suffixes to configure for the DNS lookup. If more than one suffix is
specified, they are separated by a comma.
DNS Server List field
The DNS server IP addresses. Use a comma to separate more than one server.
VM Image Type
drop-down list
Choose the OS of the image that is installed on the VM. Choose Windows and Linux
or Linux Only. For Windows images, further details must be provided.
Product ID field
The Windows product ID or license key.1 The product ID or license key can be
provided here or at the OS license pool. The key at the OS license pool overrides the
key provided here. For more information about the OS license, see the next section.
License Owner Name
field
The Windows license owner name.1
Organization field
The organization name to configure in the VM.1
License Mode
drop-down list
Choose the per-seat or per-server.1
Number of License
Users field
The number of license users or connections.1
WINS Server List
The WINS server IP addresses.1 Multiple values are separated with a comma.
Auto Logon check box
Check the check box to enable automatic log on.1
Auto Logon Count field The number of times to perform automatic log on.1
Administrator Password The password for the administrators account.1
field
Domain/Workgroup
drop-down list
Choose either Domain or Workgroup.1
Workgroup field
The name for the workgroup.2
Domain field
The name of the Windows domain.1
Domain Username field The Windows domain administrator’s username.1
Domain Password field
The Windows domain administrator’s password.1
1. For Windows VMs only.
2. This option is visible if Workgroup is chosen.
Cisco UCS Director Administration Guide, Release 4.0
16-4
OL-30149-02
Chapter 16
Using Macros
About VM Template and Hostname Variables
About VM Template and Hostname Variables
The VM template and hostnames can be automatically generated using a set of variable names. Each
variable must be enclosed in ${VARIABLE}. The allowed variable names are as follows:
Name
Description
${CLOUD_NAME}
The name of the cloud used for VM provisioning.
${GROUP_NAME}
The name of the group to which the VM belongs.
${CATALOG_NAME}
The name of the catalog item used for VM provisioning.
${USER}
The requesting user ID.
${SR_ID}
The service request ID.
${COMMENTS}
The comments specified by the requesting user.
${COST_CENTER}
The cost center that is associated with a group or customer organization.
This is specified during group or customer organization creation.
${APPCODE}
The application code that is specified during catalog creation.
About Application Codes
The application code specified during catalog creation can be used in the VM name. By specifying an
application code for a catalog, the value can be called in the VMware system policy by adding
${APPCODE} as a variable.
Typically, APPCODE can be used to a type of application such as DB, WS, SQL, and so on. The
application type in the VM name or hostname allows you to easily identify the type of the application
within the VM. For example, vm-${GROUP_NAME}##, the VM name is vm-HR01 for the first VM
provisioned with this policy (in here the group name is HR and 01 represents ##). If a new VM is
provisioned for the same group and catalog, that VM is named vm-HR02.
You can add the # character at the end of the VM name template to create a unique index number for the
VM name. It can be given in multiples as vm-${CATALOG_NAME}${APPCODE}, where the VM
name is vm-W2K3DB for the VM provisioned with this policy. The catalog name is W2K3 and the
application code specified is 01.
About Macro Orchestration
During the creation of a Cisco UCS Director workflow, you can use macros for Workflow Task inputs.
During the runtime execution of the workflow, the Orchestrator replaces the values for each macro
before executing the associated action.
Each Cisco UCS Director workflow typically has the following components:
•
Workflow inputs that are defined by the administrator.
•
Tasks that are drag-and-dropped by the administrator from a predefined set of the task library. Each
task has an ID, set of inputs, and outputs.
Macros may be used for each task input. Any workflow level input or a previous task output can be used
as a macro in a subsequent task. For example, a workflow has two inputs labeled Enter Disk Size, and
Max Snapshots, and it has two tasks with IDs task1 and task2. Any input values to task1 or task2 that
takes free-form input can use those two values as macros:
Cisco UCS Director Administration Guide, Release 4.0
OL-30149-02
16-5
Chapter 16
Using Macros
About Macro Orchestration
•
${Enter Disk Size}
•
${Max Snapshots}
Each variable name is exactly the same as the label associated with the input. task2 can also use the
output of task1. If task1 has two output variables, OUTPUT_VOLUME_NAME and
OUTPUT_VOLUME_SIZE, then task2 may refer to them both using the syntax
${task1.OUTPUT_VOLUME_NAME} and ${task1.OUTPUT_VOLUME_SIZE}. Each input field may
refer to more than one macro.
For all workflows, two additional predefined variables can be used in the task input fields:
•
SR_ID: ID: the ID of the current service request
•
PARENT_SR_ID: the Parent SR ID of the current service request (if applicable).
For workflows that are executed in the context of a VM, these additional variables can be used in a
macro:
Name
Description
${VM_NAME}
The name of the VM.
${VM_IPADDRESS}
The IP address of the VM.
${VM_STATE}
The state of the VM (ON or OFF).
${VM_STATE_DETAILS}
The state of the VM, power-on or power-off.
${VM_PARENT}
The ESX server or host node that is hosting the VM.
${VM_CLOUD}
The name of the cloud used for VM provisioning.
${VM_HOSTNAME}
The hostname of the VM
${VM_GROUP_NAME}
The name of the group to which the VM belongs.
${VM_GROUP_NAME}
The group ID to which the VM belongs.
${VM_CATALOG_ID}
The catalog ID used for VM.
${VM_ID}
The VM ID of the chosen VM.
${VM_SR_ID}
The VM service request ID.
${VM_COMMENTS}
The comments specified by the requesting user.
${VM_VDC_NAME}
The name of the vDC.
${VM_VDC_ID}
The vDC ID.
${VM_TYPE}
The type of the VM.
${VM_SCHED_TERM}
The scheduled termination time for the VM.
Cisco UCS Director Administration Guide, Release 4.0
16-6
OL-30149-02