3.3. Private Catalog

Private Catalog is a service that provides Disks for storing templates of Virtual Machines that you have created. You can create new Virtual Machines from the templates saved in Private Catalog.

3.3.1. Available Features

You can use the following features in Private Catalog.
  Feature Overview
1 Provision of a Disk for saving template catalogs A feature that provides a Disk region for saving Virtual Machine templates and adds or reduces the capacity. You can create new Virtual Machines from the templates saved in this Disk region.
2 Create Template feature A feature that converts a created Virtual Machine into a template. You can also delete created templates.
3 Import Template feature A feature for importing Virtual Machine images created on a local server to Private Catalog.
4 Export Template feature A feature for exporting templates stored in Private Catalog to a local server.

../../_images/image84.png

Important

  • Private Catalog can only be used in the same Data Center as the Compute Resource Pool. It cannot be used across different Data Centers.

Note

  • The Private Catalog Disk region is provided by using the Disk resources of storage devices shared by multiple users. Disk resources are provided as user-specific Private Catalogs and therefore cannot be accessed by other users.

3.3.2. Provision of a Disk for Saving Template Catalogs

You can use the Customer Portal to add or reduce the capacity of the Private Catalog Disk region within the ranges shown below.
Item Lower Limit Upper Limit Setting Unit
Disk Resources 10 GB 4,000 GB 1 GB

Important

  • Guest OS license usage fees are incurred if you create a template of a Virtual Machine that contains an OS license provided by Compute Resource, and then create a Virtual Machine based on the template. For details regarding the applicable types of Guest OSes, refer to “3.4 OS License”.
  • If the Virtual Machine is over 4,000GB for total disk capacity + memory resource (different for each Compute Class), the template cannot be created.

Note

  • You can also delete all Private Catalog Disk regions.

3.3.3. Create Template Feature

You can convert a created Virtual Machine and save it as a template in a Private Catalog. You can also delete stored templates.
When creating a template, confirm that the following requirements have been met.
  • The Virtual Machine is powered off
  • The Private Catalog Disk region has more available space than the total value of the Disk capacity and Memory capacity of the Virtual Machine

Note

  • The Virtual Machine is not deleted by creating and deleting templates. The configuration of the root Disk and data Disks for the Virtual Machine and the data are preserved.
Understanding the Consumption of Private Catalog Disk Resources
When creating a template, the following capacity is consumed from the Private Catalog Disk resources.
  • Total value of all of the Disk capacity mounted in the Virtual Machine
../../_images/image90.png

Note

  • The Private Catalog Disk resources consumed by templates are only the total value of the Disk capacity of the Virtual Machine that created the Virtual Machine image. It does not include the Memory capacity.

3.3.4. Import Template Feature

You can import Virtual Machine images created on a local server to Private Catalog.
If you upload a Virtual Machine image file from the Customer Portal using a web browser, the Virtual Machine image file is converted into a template and saved in the Private Catalog.

Important

  • To import a Virtual Machine image, you will require more available space in the Private Catalog Disk region than the total of the Disk capacity and Memory capacity of the Virtual Machine image that is being imported (not the file size of the actual OVA file).
  • You are responsible for appropriately managing licenses for software such as Guest OSes and applications included in the imported Virtual Machine image. For example, please check with the vendor of your Guest OS or application to confirm that the license can be used in Compute Resource, prior to use.
  • For the Guest OS to import and use a Virtual Machine image of Windows Server, you will need to switch the SPLA OS license.
Understanding the Consumption of Private Catalog Disk Resources
When importing a template, the following capacity is consumed from the Private Catalog Disk resources.
  • Total value of all of the Disk capacity mounted in the Virtual Machine
../../_images/image93.png

Note

  • The Private Catalog Disk resources consumed by templates are only the total value of the Disk capacity of the Virtual Machine that created the Virtual Machine image. It does not include the Memory capacity.
VM Image Import Function
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.
  • 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)
    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 were 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.
  • 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.
All characters (text) used within the OVA template, including the OVA file name and parameters within the VM image may not use the following characters.
‘ ’ (space)
multi-byte characters
Characters that may not be used in Microsoft Windows
Other characters that are not listed as UTF-8
  • Requirements of Virtual Hardware
  Windows Linux
Virtual Hardware version 7,8,9
OS type of Virtual Hardware OS type that is appropriate for the installed Guest OS -
Virtual Devices Required CPU, Memory, Video Card, VMCI Device, SCSI Controller, CD/DVD drive (1stdrive), Floppy Drive (1stdrive), Hard Disk (1stdrive)
Virtual Devices Not Supported Parallel Port, SCSI Device, Serial Port, USB Controller, USB Device, PCI Device, CD/DVD drive (2nddevice or more), Floppy Drive (2nddevice 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 1GB, Less than 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 *1 SCSI(0:0)
Virtual Disk size *2 Less than or equal to 2000GB for all virtual disks
vNIC *3 Recommended to delete all vNICs beforehand (will be deleted when importing)
VMCI Must be disabled
CD/DVD Device*4 Host Device Mount or Client Device Mount
CD/DVD Drive Must be either in “Host Device Mount”or “Client Device Mount”setting
*1 Root disk cannot be changed after importing to Enterprise Cloud environment
*2 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.
*3 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.
*4 VM image which includes mounted ISO image cannot be imported. Please create VM image after ISO image is unmounted.

3.3.5. Export Template Feature

You can convert a Private Catalog template to a Virtual Machine image and export it from the Customer Portal to your own environment using a Web browser.

Important

  • If NTT Communications owns the licenses for software included in the exported Virtual Machine image, such as the Guest OS and applications, the continued use of those licenses on your local computer is a license violation and is therefore not permitted. In this situation, you are responsible for appropriately managing licenses by replacing the licenses for such software with licenses that you own.

Note

  • Download sessions established while logged in to the Customer Portal can be continued after logging out of the Customer Portal. However, the download session may be terminated after downloading continuously for more than 48 hours.
  • A template is not deleted even if you export it.

3.3.6. Important Points

Important Points regarding the Windows Server Guest OS
When creating a Virtual Machine from a template that uses Windows Server as the Guest OS, Sysprep will automatically run the first time that you start the Virtual Machine. Sysprep is a tool that configures Windows OS system settings in advance.

Important

  • Microsoft product specifications and license terms allow you to run Sysprep up to the limit listed below. If you exceed this limit, you may not be able to use the Virtual Machine.

    Windows Server 2012 R2: 1000 times

    Windows Server 2012: 1000 times

    Windows Server 2008 R2: 3 times

    *Once the virtual machine is created from the template, you will be using up the limited times for Sysprep running.

Important Points regarding Guest OS Settings
  • In case of using Create Template Feature
When changing the Guest OS network settings, do not disable Network Adaptor (NICS) that has been recognized in the Customer Portal, even if you are not using that Adaptor. Creating a Virtual Machine from a template in which Adaptor is disabled in the Guest OS may result in errors.
  • In case of using Import Template Feature
  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.

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 to switch the license from customer owned to a license that the company provides in Enterprise Cloud. Please contact your local sales representative for details.
Important Points regarding Serves Segment deletion
Server Segment cannot be deleted as long as the template exists on Private Catalog, when Virtual Machine which vNIC connecting the Server Segment is converted. When there is a schedule which deletes Server Segment, please convert Virtual Machine after removing vNIC from the Server Segment in advance.