Enterprise Cloud VM Image Import User Guide. Version 1.0

(1)

Enterprise Cloud

VM Image Import User Guide

(2)

i ntt.com

Version History

Issue Date Comments

(3)

1 ntt.com

Introduction

1) Purpose of this document:

The purpose of this document is to inform Enterprise Cloud customers on how to import a Virtual Machine (VM) to an Enterprise Cloud environment.

Please note that the items and conditions listed in this document are provided as-is and is intended to be updated regularly. Please refer to the most up-to-date version of this document when uploading a VM.

Company strongly recommends to customers that they take and maintain a backup of the VM to be uploaded. Company takes no responsibility that the uploaded VM will function as intended by the customer.

2) Definitions and interpretations:

In this document, the term “Company” refers directly to either NTT Com or to one of its affiliate companies which sells Enterprise Cloud to its end customers.

“Service(s)” refers specifically to the Enterprise Cloud service, in which details are described in the Service Description document.

3) Target Audience

Company assumes that the user of this document has knowledge of VMware ESX, VMware vCenter and can create/export a VM by configuring parameters in ESX and vCenter.

(4)

2 ntt.com

VM Image Import User Guide

1. Prerequisites

In order to import a VM to Enterprise cloud environment, the VM must be created in either one of the (2) environments listed below.

1. VMware vSphere 4.x and above 2. VMware ESXi 4.x and above

In addition to the above, customers are requested to use vCloud Director (VCD) 1.5 and above.

Company takes no responsibility that the imported VM (including the Operating System and application within the VM) will function as intended by the customer.

2. Requirements to create a VM image

Customers are requested to read and understand the following document from VMware vSphere Document Center in order to export a VM image as an OVF template. (External Link)

http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-virtual-machine-admin-guide.pdf

When creating a VM image (exporting to OVF template), the following conditions must be met:

- Customers are requested to use VCD to set “Enable Guest Customization” to “On”. Customers must prepare the VCD environment.

- The VM image must be shutdown properly. VMs that was improperly shutdown prior to creating a VM image may not function when imported to the Enterprise Cloud environment.

- The VM within the VM image is limited to one VM. VM images with multiple VMs (such as vApps) may not be imported to Enterprise Cloud environment.

- All virtual disk files within the VM image must be a single virtual disk file (VMDK file). A VMDK file that is split into multiple files cannot be supported.

3. Requirements of VM image

The VM image must be a single file in OVA format v1.0.0 or 1.1.0. The size of the OVA file must be 250GB or less.

(5)

3 ntt.com

All characters (text) used within the OVA template, including the OVA file name and parameters within the VM image, may not use the following.

‘ ’ (space)

multi-byte characters

characters that may not be used in Microsoft Windows Other characters that are not listed as UTF-8

4. Requirements of Virtual Hardware

Requirements of Virtual Hardware listed in Appendix 1.

5. Requirements of Guest OS

A list of Guest OS’s that may be imported can be found at the following VMware document (external link):

http://www.vmware.com/pdf/vcd_15_users_guide.pdf

Please refer to Chapter 9 “Working With Virtual Machines”, Section “Guest Operating System” and refer to the table in “Guest Operating System Support”. Guest OS installed in the VM image must have Guest Customization as “Automatic”.

All software that requires certain hardware (such as hardware monitoring agents) must be uninstalled or disabled before creating a VM image.

It is the sole responsibility of the customer to comply with all license agreements of the OS, applications, etc when creating and importing a VM image to Enterprise Cloud environment.

When importing a VM with a specific version of Windows Server, there is a possibility that our operator can switch the license from a customer owned to a license that the Company provides in Enterprise Cloud for a price. Please contact your local sales representative for details.

Other requirements of Guest OS listed in Appendix 2.

6. Support by Company for VM Image Import

If customer has trouble when importing a VM image to Enterprise Cloud environment, please contact your local support center for support.

(6)

4 ntt.com

Appendix 1

Virtual Hardware Requirements

Windows Linux

Virtual Hardware version only 7 or 8 (8 recommended)

OS type of Virtual Hardware *1 OS type that is appropriate for the installed Guest OS

Virtual Devices Required CPU, Memory, Video Card, VMCI Device, SCSI Controller, CD/DVD drive (1st

drive), Floppy Drive (1st drive), Hard Disk (1st drive)

Virtual Devices Not Supported Parallel Port, SCSI Device, Serial Port, USB Controller, USB Device, PCI Device,

CD/DVD drive (2nd device or more), Floppy Drive (2nd device or more)

SCSI Bus Sharing None

SCSI Controller LSI Logic SAS recommended LSI Logic Parallel recommend

vCPU 1, 2, 4, 6 or 8

CPU Cores 1 Core per Socket

CPU Resource Allocation Limit Must be “Unlimited”

Memory More than or equal to 1GB, Less than or equal to 32 GB

Virtual Disk Type Thin Provisioning recommended, may be thick provisioned

Virtual Disk numbers Max. 7 virtual disks (including root disk), cannot be in “Independent Mode”

Virtual Device Node of root disk *2

SCSI(0:0)

Virtual Disk size *3 Less than or equal to 2000GB for all virtual disks

vNIC *4 Recommended to delete all vNICs beforehand (will be deleted when importing)

VMCI Must be disabled

CD/DVD Drive Must be either in “Host Device Mount” or “Client Device Mount” setting

*1 For example, when Guest OS in VM is “CentOS 5”, you should select “Red Hat Enterprise Linux 5”, when “CentOS 6” you should select “Red Hat Enterprise Linux 6”.

(7)

5 ntt.com

*2 Root disk can not be changed after importing to Enterprise Cloud environment

*3 When uploading a VM image to Enterprise Cloud environment, it is required to have sufficient space available in the private catalog. The uploaded VM size should be calculated by the virtual disk size, not the thin provisioned file size. For example, if a customer has created a VM image (OVA) with 5 virtual disks each with 500 GB in size, the VM image may be small as 100 GB if using thin provisioned virtual disks. In this case, the total of the virtual disk size would be 2,500GB (500GB x 5) and would fail when importing the VM to Enterprise Cloud according to the limitation of Virtual Disk Size (Less than or equal to 2000GB for all virtual disks). *4 Existing vNICs should be deleted and new vNICs should be created in such a way that Company can support during the post process of VM image import.

(8)

6 ntt.com

Appendix 2

Requirements of Guest OS

Windows Linux

Configuration of Firewall within Guest OS *1

Must permit ICMP

(Company monitors VM using ICMP ping)

Perl N/A Must use Perl pre-installed in the

Guest OS

Network Adaptor (NICs) Must not disable Network Adaptor (NICs) from Guest OS

VMware Tools Must have the most up-to-date VMware tools installed, and must be

automatically enabled when a VM is turned on

*1 Customer has the responsibility to secure the VM. Customer may do so by configuring the vFirewall that Enterprise Cloud provides and/or by using the firewall within the Guest OS or by using other methods.

(9)

7 ntt.com

Appendix 3

The following is the Customer Portal guide to import VM image to Enterprise Cloud environment.

1. Login to the Enterprise Cloud portal and Click on 1 to open the Compute Resource Pool configuration.

2. From the Compute Resource Pool Configuration page, select “Catalogs” to open the catalog page.

1

(10)

8 ntt.com

3.

From the “Catalog” page, click on the + (plus) mark to open popup.

4.

Enterprise Cloud VM Image Import User Guide. Version 1.0