Chapter 1. New and Changed Information for this Release

New and Changed Information for this Release

Chapter 2. Using OVF Files

Overview of OVF Files

Working with OVF Files

Configuring an External Storage Mounting Point

Accessing the Storage Application Configuration

Uploading OVF Files

Deploying OVF Files

Deleting OVF Files

OVF File Limitations

Preface

Audience

Conventions

Related Documentation

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. New and Changed Information for this Release

- New and Changed Information for this Release

New and Changed Information for this Release

No significant changes were made to this guide for the current release.

Chapter 2. Using OVF Files

This chapter contains the following sections:

- Overview of OVF Files

- Working with OVF Files

- Configuring an External Storage Mounting Point

- Accessing the Storage Application Configuration

- Uploading OVF Files

- Deploying OVF Files

- Deleting OVF Files

- OVF File Limitations

Overview of OVF Files

This information describes how administrators and end users can use Cisco UCS Director to configure appliance storage, upload Open Virtualization Format (OVF) files, and deploy those files to a group or customer organization. Group administrators and end users can only deploy OVF files from their respective groups.

Working with OVF Files

The administrator, group-administrator, or end user can upload Open Virtualization Format (OVF) files (in both zip and jar formats) to a previously configured storage location where they are deployed.

The overall process is as follows:

Step 1

Configure storage appliance.

Step 2

Upload OVF files.

Step 3

Deploy OVF files.

Step 4

(Optional)Delete OVF files.

Configuring an External Storage Mounting Point

Note

By default the appliance storage location is configured to the local storage location (/opt/infra/uploads/external/public/*).

Step 1

On the menu bar, choose Administration > Integration > Appliance Storage tab.

Step 2

In the Appliance Storage window, click Template Storage.

Step 3

Click the Edit Mount Point icon.

Step 4

In the Edit NFS Mount Configuration dialog box, check the Enable External Mount check box to configure the external mount point.

Step 5

In the Edit NFS Mount Configuration dialog box, complete the following fields:

Name

Description

Enable External Mount check box

If checked, enables an external mount.

NFS Server IP Address

field

The IP address of your NFS server. An administrator can create an NFS share on NetApp Filer or any Network File System (NFS) server as storage. The OVF file that an end user uploads is stored in the location that is configured by the administrator.

NFS Server Path

field

The NFS server path/share directory, such as /vol/ovfupload.

Step 6

Click Submit.

What to Do Next

Administrators and end users can upload OVF files.

Accessing the Storage Application Configuration

Uploaded files can be stored locally on the Cisco UCS Director appliance.

Step 1

On the menu bar, choose Administration > Integration.

Step 2

Click the Appliance Storage tab.
From this window, you can view existing external storage locations.

Uploading OVF Files

Cisco UCS Director allows an administrator, group administrator, or end user to upload OVF files (OVA, zip and jar formats) to a predefined storage location and deploy them to a group or customer organization.

Note

Group administrators and end users are the only types with privileges to upload and deploy OVF files.

Before You Begin

Ensure that you have the proper access rights.

Step 1

On the menu bar, choose Administration > Integration.

Step 2

Click the User OVF Management tab.

Step 3

Click Upload File.

Step 4

In the Upload File dialog box, complete the following fields:

Name

Description

Folder Type drop-down list

The type of folder containing the OVF file. Choose one of the following:

- Public—This file is available to all public users.

- User—Choose this role if you are an end user. End users are not granted extensive privileges. The User role is well suited for first-level support, in which problem identification, remediation, and escalation are the primary goals.

- Group—The file is only available to those in a defined group.

File Name field

The name of the OVF file to upload and display.

Upload option

Launches the File Upload dialog box in which you can browse and select an OVF file.

Note:
Only OVF files in OVA, zip and jar formats can only be uploaded to the storage location.

After the file is uploaded, and a confirmation message stating that the file is ready for use is displayed. Click Submit.

The Submit button is enabled only after the file is uploaded in the File Upload dialog box.

File Description field

The description of the file (if required).

Step 5

Click Submit.

Step 6

When the Submit Result - Upload Successfully dialog box appears, click OK. The uploaded file is listed in the User OVF Management table.

What to Do Next

Deploy the OVF file.

Deploying OVF Files

If you are an administrator, you have the authority to deploy OVF files to a group by selecting the group's Virtual Data Center (vDC). Once an OVF file is deployed to a vDC, the files are automatically unzipped and a VM is deployed on a VMware cloud that is associated to the vDC.

Step 1

On the menu bar, choose Administration > Integration.

Step 2

Click the User OVF Management tab.

Step 3

Choose an OVF file from the table.

Step 4

Click Deploy OVF.

Step 5

In the Deploy OVF window, complete the following fields:

Name

Description

Select vDC drop-down list

Choose a vDC.

Note:
Group administrators and end users can only view vDCs that are associated to their group.

OVF File Name field

The name of the selected OVF file.

VM Name field

The VM name. If you do not enter a VM name, a default name is automatically provided.

User Name field

The OVF user name.

Password field

The OVF file password.

Provision field

The time to provision the VM.

Choose either Now or Later. If you choose Later, then you must select the date and time.

Power OFF the VM after field

Check this check box to specify the number of days or hours after which the VM is automatically powered off.

Days field

The number of days to after which the VM is automatically powered off.

Hours field

The number of hours after which the VM is automatically powered off.

Step 6

Click Submit.
After an OVF file deploys, a service request is created that displays the status of the deployed OVF. For more information, refer to the Viewing Service Requests topic.

Deleting OVF Files

If you are an administrator, you can delete files located in the storage area.

Before You Begin

You must obtain the proper authorization to delete files from the Cisco UCS Director appliance. Service end users and group administrators are authorized to delete OVF files.

Step 1

On the menu bar, choose Administration > Integration.

Step 2

Click the User OVF Management tab.

Step 3

Choose an OVF file from the table and click Delete File.
The Delete File dialog box appears.

Step 4

Click Submit.

OVF File Limitations

OVF File Upload Limitations

The current OVF file upload limitations are as follows:

- Provisioning a VM from an OVF file with multiple NICs is not supported. The VM is provisioned by taking a primary vNIC only into consideration.

- Custom resize (CPU, memory and disk) is not possible for VMs provisioned from an OVF file.

- Multi-disk provisioning is not supported for VM that are provisioning from an OVF VM.

Preface

- Audience

- Conventions

- Related Documentation

- Documentation Feedback

- Obtaining Documentation and Submitting a Service Request

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

- Virtualization and virtual machines

Conventions

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.

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.

Caution

Means reader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data.

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.

Timesaver

Means the described action saves time. You can save time by performing the action described in the paragraph.

Warning

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

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: Click Here .

Cisco UCS Documentation Roadmaps

For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: Click Here .

For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap available at the following URL: Click Here .

Note

The Cisco UCS B-Series Servers Documentation Roadmap includes links to documentation for Cisco UCS Manager and Cisco UCS Central. The Cisco UCS C-Series Servers Documentation Roadmap includes links to documentation for Cisco Integrated Management Controller.

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to ucs-director-docfeedback@cisco.com. We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's New in Cisco Product Documentation RSS feed. RSS feeds are a free service.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)