Cisco UCS Director OVF File Upload Guide, Release 4.0First Published: August 14, 2013

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-30140-01

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 LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE 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 versionof the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, 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 OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE 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, networktopology 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 unintentionaland 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: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1110R)

© 2013 Cisco Systems, Inc. All rights reserved.

C O N T E N T S

P r e f a c e Preface v

Audience v

Conventions v

Related Documentation vii

Documentation Feedback vii

Obtaining Documentation and Submitting a Service Request vii

C H A P T E R 1 Overview of OVF Files 1

Overview of OVF Files 1

C H A P T E R 2 Using OVF Files 3

Working with OVF Files 3

Configuring an External Storage Mounting Point 4

Accessing the Storage Application Configuration 4

Uploading OVF Files 5

Deploying OVF Files 6

Deleting OVF Files 7

OVF File Limitations 7

Cisco UCS Director OVF File Upload Guide, Release 4.0 OL-30140-01 iii

Cisco UCS Director OVF File Upload Guide, Release 4.0iv OL-30140-01

Contents

Preface

This preface contains the following sections:

• Audience, page v

• Conventions, page v

• Related Documentation, page vii

• Documentation Feedback, page vii

• Obtaining Documentation and Submitting a Service Request, page vii

AudienceThis guide is intended primarily for data center administrators who use Cisco UCS Director and who haveresponsibilities and expertise in one or more of the following:

• Server administration

• Storage administration

• Network administration

• Network security

ConventionsIndicationText Type

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.

GUI elements

Document titles appear in this font.Document titles

In a Text-based User Interface, text the system displays appears in this font.TUI elements

Cisco UCS Director OVF File Upload Guide, Release 4.0 OL-30140-01 v

IndicationText Type

Terminal sessions and information that the system displays appear in thisfont.

System output

CLI command keywords appear in this font.

Variables in a CLI command appear in this font.

CLI commands

Elements in square brackets are optional.[ ]

Required alternative keywords are grouped in braces and separated by verticalbars.

{x | y | z}

Optional alternative keywords are grouped in brackets and separated by verticalbars.

[x | y | z]

A nonquoted set of characters. Do not use quotation marks around the string orthe string will include the quotation marks.

string

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 codeindicates a comment line.

!, #

Means reader take note. Notes contain helpful suggestions or references to material not covered in thedocument.

Note

Means the following information will help you solve a problem. The tips information might not betroubleshooting or even an action, but could be useful information, similar to a Timesaver.

Tip

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

Caution

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

Timesaver

Cisco UCS Director OVF File Upload Guide, Release 4.0vi OL-30140-01

PrefaceConventions

IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before youwork on any equipment, be aware of the hazards involved with electrical circuitry and be familiar withstandard practices for preventing accidents. Use the statement number provided at the end of each warningto locate its translation in the translated safety warnings that accompanied this device.

SAVE THESE INSTRUCTIONS

Warning

Related Documentation

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

Obtaining Documentation and Submitting a Service RequestFor 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 Ciscotechnical documentation.

Subscribe to theWhat's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feedand set content to be delivered directly to your desktop using a reader application. The RSS feeds are a freeservice and Cisco currently supports RSS version 2.0.

Cisco UCS Director OVF File Upload Guide, Release 4.0 OL-30140-01 vii

PrefaceRelated Documentation

Cisco UCS Director OVF File Upload Guide, Release 4.0viii OL-30140-01

PrefaceObtaining Documentation and Submitting a Service Request

C H A P T E R 1Overview of OVF Files

This information describes how administrators and end users can use Cisco UCS Director to configureappliance storage, upload Open Virtualization Format (OVF) files, and deploy those files to a group orcustomer organization. Group administrators and end users can only deploy OVF files from their respectivegroups.

• Overview of OVF Files, page 1

Overview of OVF FilesThis information describes how administrators and end users can use CiscoUCSDirector to configure appliancestorage, upload Open Virtualization Format (OVF) files, and deploy those files to a group or customerorganization. Group administrators and end users can only deploy OVF files from their respective groups.

Cisco UCS Director OVF File Upload Guide, Release 4.0 OL-30140-01 1

Cisco UCS Director OVF File Upload Guide, Release 4.02 OL-30140-01

Overview of OVF FilesOverview of OVF Files

C H A P T E R 2Using OVF Files

This chapter contains the following sections:

• Working with OVF Files, page 3

• Configuring an External Storage Mounting Point, page 4

• Accessing the Storage Application Configuration, page 4

• Uploading OVF Files, page 5

• Deploying OVF Files, page 6

• Deleting OVF Files, page 7

• OVF File Limitations, page 7

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

The overall process is as follows:

Step 1 Configure storage applianceStep 2 Upload OVF filesStep 3 Deploy OVF files

Cisco UCS Director OVF File Upload Guide, Release 4.0 OL-30140-01 3

Configuring an External Storage Mounting Point

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

Note

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:

DescriptionName

If checked, enables an external mount.Enable External Mount check box

The IP address of your NFS server. An administrator cancreate an NFS share on NetApp Filer or any Network FileSystem (NFS) server as storage. The OVF file that an enduser uploads is stored in the location that is configured bythe administrator.

NFS Server IP Address

field

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

NFS Server Path

field

Step 6 Click Submit.

What to Do Next

Administrators and end users can upload OVF files.

Accessing the Storage Application ConfigurationUploaded files can be stored locally on the Cisco UCS Director appliance.

On the menu bar, choose Administration > Integration > Appliance Storage tab.From this window, you can view existing external storage locations.

Cisco UCS Director OVF File Upload Guide, Release 4.04 OL-30140-01

Using OVF FilesConfiguring an External Storage Mounting Point

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

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

Before You Begin

Ensure that you have the proper access rights.

Step 1 On the menu bar, choose the Administration tab.Step 2 Click the Upload Files tab.Step 3 Click Upload File.Step 4 In the Upload File dialog box, complete the following fields:

DescriptionName

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

• Public—Choose this role to

• User—Choose this role if you are an end user. End users are not grantedextensive privileges. The User role is well suited for first-level support, inwhich problem identification, remediation, and escalation are the primarygoals.

• Group—This role can deploy OVF files.

Folder Type drop-down list

The name of the OVF file to upload and display.File Name field

Browse to choose the required file. ClickOK when the File Upload confirmationdialog box appears.

Only OVF files in zip and jar formats can only be uploaded to the storagelocation. Files larger than 1.6 GB are not supported.

Note

Select a file for upload field

The description of the file (if required).File Description field

Step 5 Click Submit.Step 6 When the Once Submit Result - Upload Successfully dialog box appears, click OK. Uploaded files are accessible

under the Upload Files tab.

What to Do Next

Deploy the OVF file.

Cisco UCS Director OVF File Upload Guide, Release 4.0 OL-30140-01 5

Using OVF FilesUploading OVF Files

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

Step 1 Choose Administration > Integration > Upload Files tab.Step 2 Choose the Deploy OVF tab.Step 3 In the Deploy OVF window, complete the following fields:

DescriptionName

Choose a vDC.

Group administrators and end users can only viewvDCs that are associated to their group.

Note

Select vDC drop-down list

The file location for the selected OVF file.OVF URL field

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

VM Name field

The OVF user name.User Name field

The OVF file password.Password field

The time to provision the VM. Choose eitherNow orLater.Provision field

The number of days or hours to automatically power offthe VM.

Power OFF the VM after field

The number of days to elapse until the VM is automaticallydeleted.

Days field

Enter the number of hours to elapse until the VM isautomatically deleted. The VM is deleted after the specifiednumber of days and hours.

Hours field

Step 4 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.

Cisco UCS Director OVF File Upload Guide, Release 4.06 OL-30140-01

Using OVF FilesDeploying OVF Files

Deleting OVF FilesIf 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 endusers and group administrators are authorized to delete OVF files.

Step 1 Choose Administration > Integration > Upload Files.Step 2 Choose a file and click Delete File.

The Delete File dialog box appears.

Step 3 Click Submit.

OVF File LimitationsOVF 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 bytaking 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.

• The OVF file upload feature file does not support file sizes that are larger than 1.6 GB.

Cisco UCS Director OVF File Upload Guide, Release 4.0 OL-30140-01 7

Using OVF FilesDeleting OVF Files

Cisco UCS Director OVF File Upload Guide, Release 4.08 OL-30140-01

Using OVF FilesOVF File Limitations