2.2. Virtual Server

2.2.1. Overview

2.2.1.1. Overview

This menu provides customer-dedicated virtual servers accommodated within the shared physical servers platform.
Creating, configuring and deleting virtual servers are completely automated. Customers are able to utilize them on-demand.

Note

NTT Com paraphrases “Nova” and “Cinder”, the OpenStack components, into “Compute” and “Volume” respectively.

2.2.1.2. Features

Following are the features of Virtual Server menu:

1.High Elasticity

API enables Customers to scale-in/out (increase/decrease the number of virtual servers) and scale-up/down (increase/decrease the specs of virtual servers) in real time.
This means Virtual Server menu enables Customers to operate their system in optimised specs and units, and deploy with high elasticity.
For instance, Virtual Server menu is the best fit with the system that requires handling burst traffic, as well as the web platform for their particular event temporarily.

2.High Cost Performance

With the low-cost virtual servers, this service will be the best fit with the Customers who operate the system focusing on cost performance.
This menu has no minimum use period, and the resources are charged by pay-as-you-go basis. As such, Customers can optimise their cost even if their usage period is a short one such as couple of days or months.
Customers can flexibly design their system as they can easily create/manage/delete the resources in real-time operation via Customer Portal / API.

3.OpenStack-Based Gears for Cloud Service

Virtual Server menu is based on OpenStack, industry-leading open source projects, with OpenStack native API.
This menu is best fit with the Customers who would like to migrate their system deployed in other OpenStack-based cloud services to Enterprise Cloud, or the Customers who need the development environment for OpenStack-compatible systems.

2.2.2. Descriptions of Menu

2.2.2.1. Compute

Compute

Virtual servers of multiple Customers are accommodated within the same physical servers platform provided by NTT Com.
NTT Com provides the plans (flavor), the combinations of CPU and Memory, so Customers can select their favorite plan as needed.

How to Create Instance

There are two ways of creating Instance in Virtual Server menu:

Note

Virtual Machine (VM) is created through a combination of Compute and Volume (or Root Disk described later). Virtual Server menu, Instance is defined as the Virtual Machine created as such.

Method

Items

Method 1

Customers boot Instance directly from Image (Official Image Template or Private Image Template).
In this case, root disk is automatically created. (Volume is not necessary).
The root disk is free of charge, but it is not displayed on the Customer Portal. Moreover, root disk will not be deleted when Instance stops or reboots; however, Customers are noted that root disk is also automatically deleted once Instance gets deleted.
This method is ideal for Customers who would like to create Instance immediately.

Method2

Customers create the volume from Image (Official Image Template or Private Image Template) and then boot Instance from the volume.
In this case, Customers create bootable volume first, and boot the Instance by setting the bootable Volume as root volume.
This method is ideal for Customers who would like to store the OS area of Instance consistently.
Please refer to the next section regarding the terminologies of bootable volume.

Following diagram shows how Instance is created:

Image: Instance: Creation & Deletion

インスタンスの作成および削除のイメージ

Follow-Up: Difference between Root Disk and Root Volume

For follow-up information, following table shows the difference between Root Disk and Root Volume:

Name

Overview

Capacity

View Portal

Pricing

Root Disk

Root Disk is automatically created when Customers boot Instance directly from Image.
When the Instance is deleted, root disk is also automatically deleted.

Customer s cannot specify the size of Root Disk, as it is automatically created based on the Image size.

N (Not displayed)

Free of charge (Compute usge is charged)

Root Volume

Customers can boot the Instance by setting bootable volume as a Root Volume.
Even if the Instance is deleted, Root Volume will remain as a bootable volume, and they can use it as a root volume for booting the Instance.
When Customers create a volume, they can select the size of Root Volume from the plan list.
*Customers cannot specify the size of Root Volume less than the Image size.

Y (Displayed)

Charged (In addition to the Compute usage, volume usage is also charged)


2.2.2.2. Volume

Volume Size

NTT Com provides shared Virtual Storage, that multiple Customers’ Volumes (Virtual Storage) are accommodated within the same infrastructure.
Customers can freely select the size as needed from the plan list.
Instance is available once OS is started, after Customers create Bootable Volume from the OS image and boot it as Root Volume.
Furthermore, Customers can store data by attaching Data Volume to Instance as a data disk.

Glossaries of Volume

Depending on the status of Volume, there are five types of Volume: Bootable Volume, Unbootable Volume, Empty Volume, Root Volume, and Data Volume.
This section describes the definition of each Volume. These Volumes are consistently belongs to the same service, but NTT Com defines them for describing what the Volume is to Customers.

Glossary List of Volume (These definition is for Customers’ information. As such, these are categorized in the same Volume service)

Japanese Term

English Term

Defined Functions

Volume

Volume
Volume is defined as virtual storage in Virtual Server menu. Customers can store the data of their Instance into the Volume, and they can boot Instance by storing the OS.
When creating Volume, Customers can select the size from the plan list prepared by NTT Com. And Volume is a generalized term of five types of Volume described below.
Creating volume excess of template size is not allowed.
Unlike the Root Disk, Volume will remain unless it is deleted. Therefore, it still remains even when the Instance is deleted.
There are following five types of Volume: Bootable Volume, Unbootable Volume, Empty Volume, Root Volume, and Data Volume.

Bootable Volume

Bootable Volume
Bootable Volume is defined as the Volume that can either boot from OS Image or is set as bootable.
Bootable Volume can be assigned as Root Volume. If Customers store OS, they can operate via console after the Instance is booted.
(Instance cannot boot properly even if Customers set the Volume to boottable, in case OS is stored wrongly in their BYOL template.)* It can not be created with the capacity below the size of the template
Furthermore, Customers can attach the Bootable Volume to the Instance as a Data Volume. If Customers set it unbootable, it can be Unbootable Volume.

Unbootable Volume

Unbootable Volume
Unbootable Volume is defined as the Volume that is set as unbootable even though it is created from a template.
It is the same as Bootable Volume in that both Volumes are created from Image and include it. The difference is that whether the Volume is set as bootable or not.
It cannot be assigned as Root Volume as it is set to unbootable.
However, Customers can attach the Unbootable Volume to their Instance by designating it to as a Data Volume. Furthermore, they can set Unbootable Volume back to Bootable by modifying its settings.
*Even though Customers modify the setting of Unbootable Volume to bootable, they are required to store OS correctly in order for the Bootable Volume to work correctly.

Empty Volume

Empty Volume
Empty Volume is defined as the Volume that is created without any Image.
Empty Volume is set unbootable by default., thus it is not designated as Root Volume. However, it is attachable as Data Volume to the Instance. Furthermore, Empty Volume can be set as Bootable.
*Even though Customers modify the setting of Empty Volume to bootable, they are required to store OS correctly in order for the Bootable Volume to work correctly.
*Even though Customers modify the setting of Unbootable Volume to bootable, they are required to store OS correctly in order for the Bootable Volume to work correctly.

Root Volume

Root Volume
Root Volume is defined as the first Volume among those connected to Instance. And that Volume has OS area of the Instance.
Instance detects the Root Volume as the OS aera and boots from it.
Unlike Data Volume, Customers cannot attach/detach Root Volume. Unless they delete the Instance, it will be the Root Volume of that Instance.
Besides, unlike the Root Disk, Root Volume remains as the Volume if Customers delete the Instance.

Data Volume

Data Volume
Data Volume is defined as the second or subsequent Volume among those connected to Instance. And that Volume has no OS area of the Instance.
Instance detects the Data Volume as attached disk, so it cannot boot from the OS within the Data Volume even if it is stored.
Customers can attach Bootable, Unbootable and Empty Volume to Instance as a Data Volume.
Data Volume remains as the Volume even if Customers delete the Instance.
Customers can attach/detach Data Volume, and can change the connecting Instance.

Comparison of Volume Types

 

Assign OS Image(w/OS Image)

Set Boot

Assigned as Root Volume

Assigned as Data Volume

Bootable Volume

Yes

Bootable

Possible

Possible

Unbootable Volume

Yes

Unbootable

Impossible

Possible

Empty Volume

No

Unbootable

Impossible

Possible

Image of Type of Volumes

ボリュームの種類のイメージ

2.2.2.3. OS

About the service od OS, please refer to the service description of the OS.

2.2.2.4. (Reference) Upload Images/Snapshots

Customers can convert Instances and Volumes into Images. They can store the status of Instance as private template. And they can also create Instances and Volumes from private template as a copy of them.
Customers can bring their own Image and store as private template. As such, they can create the Instance and Volume from that Image.
Please refer to the service description of the “image storage area” for more information.

2.2.2.5. Reference: Status Change Diagram in Virtual Server Menu

Following diagram shows the status change in Virtual Server menu:

Status Change Diagram in Virtual Server Menu

仮想サーバーの状態遷移のイメージ

2.2.2.6. <Supplement> Region, Zone, and Group

Customers can select Region, Zone and Group for their Instance and Volume.
By doing this, they can design and configure the redundant systems as they like.
For more details, please refer to the Service Description of Region/Zone/Group.

2.2.3. Available Functions

2.2.3.1. Compute

Settings for Creating Instance

When Customers create Instance, they are required to configure following settings.
Instance is created and launched after they configure all the items and press “start”.

Settings for Creating Instance

List of Items to be set when Instance is launched:1

Category

Settings

Overview

Items

Action

Detail

Zone/Group

Select the Zone / Group

Select the combination of Zone and Group where Instance will be accommodated.
If Customers select “Any Zone/Group”, the combination of Zone and Group will be determined randomly.

Customer Portal /API

 

Instance Name

Set Virtual Server name

Enter the name of Instance to be created. Customers can input up to 255 alphanumeric characters.(*1) They can also configure duplicated names within their Tenant.

Customer Portal /API

 

Flavor

Select Flavor

Select Flavor (Plan of CPU & Memory in combination) of Instance to be created.

Customer Portal /API

 

Boot Source for Instance

Select Boot Source

Select boot source (OS Data) of Instance to be created. Customers can select “Boot from the Image” or “Boot from the Volume”.
  • When “Boot from the Image” was selected, Customers need to select the Image. Root Disk is automatically created from the Image, and Instance is booted.

  • When “Boot from the Volume” was selected, Customers need to select the Volume (Bootable Volume). Instance, that selected Root Disk is attached to, will be created.

Customer Portal /API

Data Volume

Data Volume

Select Data Volume

Instance, that selected Root Disk is attached to, will be created. If selected, selected Data Volume will be attached. *This is optional settings.
*The number of selectable volumes on the instance creation screen is one. Therefore, although the number of volumes that can be attached at the same time as the instance creation is one, the customer can attach multiple volumes after creating an instance.

Reference: In the case Customers would like to utilize Data Volume as the data disk of their Instance, mount settings will be needed on the OS after the Data Volume is attached with this operation.

Customer Portal /API

Post-install script Post-install script

Customized scripts

Customers can upload an automatically executable script configured to run after instances are launched.

Customer Portal /API

Access and security

Key pair Setting

Select Key Pair

Create / register an SSH key pair to access the instance that is created. It can be selected as an SSH key pair of the created instance.
Customers can use 1 of the SSH key pair as an SSH key pair of multiple instances.

Customer Portal /API

   

Import key pair(s)

Customer’s SSH public key can be imported.

Customer Portal /API

   

Administrator Password

By setting the contents of the public key file, customers can log in using the private key after instance startup.

Customer Portal /API

Network

Network

Select Network Connectivity

Select Logical Network to be connected to.
Customers are required to create Logical Network prior to creating Instance.
*The selectable network is only the logical plane of the data plane. Please note that the logical plane of the storage plane can not be selected. For details of the logical network, refer to the service descriptions of the logical network.
*If you do not enter the IP address of the connected logical network, the lowest number among the unused IP addresses is assigned as the IP address of the interface from within the IP address allocation pool of the connected logical network.
Reference: Customers are required to set IP Address when they connect Instance with Logical Network. They can either designate a specific IP address, or automatically assign IP address from the address range they set in advance.

Customer Portal /API

Meta Data

Meta Data

Set Meta Data

Customers can set meta data of their Instance. They can set up to 120 pairs and 255 alphanumeric characters. (*1)
Follow-up: Meta Data
Customers can add any key values for meta data, and they can mange by grouping multiple Instances as one system.

Customer Portal /API

HA Setting

HA Setting

Enable/Disable HA

Customers can set HA functions of Instance enabled/disabled. HA function is enabled by default.
In case Customers configure the HA settings of their Instance disabled, and the Instance stops due to the maintenance or failures, it cannot be automatically booted. As such, they are required to boot it by themselves.

Customer Portal /API

*1 Available characters:abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!”#$%&’()*+,-./:;<=>?@[\]^_`{|}~


Follow-Up: Routing Information when Connected to Network

When Customers create Instance, they are required to connect it to Logical Network, and the Instance will load routing information in the Subnet of Logical Network.
The default gateway information in the Subnet will be loaded to the routing information of their Instance. However, the next-hop information in the Subnet is not loaded.

Example:

Network Address

Default Gateway

10.10.0.0/24 10.10.0.1
If above Sub-Net Routing info is recorded as below:

Network Address

Next Hop

192.168.0.0/24 10.10.0.10
The Instance’s routing info that connects to this Sub-Net will be
as follows:

Network Address

Next Hop

192.168.0.0/24
10.10.0.**1**
This means the next hop value is the “default gateway” of Logical Network, not the “next hop”.

Operable Attributes of Instance

Following operations are executable in Instance:

Operable Items of Instance::

List of Operable Items of Instance:

Item

Overview

Items

Action

Instance Overview

Instance Overview

Customers can view the detailed information, IP Address, connected Volumes of their Instance.

Customer Portal /API

Create Instance

Create Instance

Create and launch Instance through selecting boot source, Flavor etc.
Root Disk is simultaneously created that includes the Boot Image selected by Customers. For more details, plaese refer to previous section.

Customer Portal /API

Boot Instance

Boot Instance

Boot Instance of power-off state.

Customer Portal /API

Shut down Instance

Shut down Instance

Shut down Instance.
If shutting down Instance cannot be completed within three minutes, it will be forced to shut down. And it might cause to break OS or system Because it is possible to stop instances even if you shut down from the OS, we recommend this way.
Because it is possible to stop instances even if you shut down from the OS, we recommend this way. (Please use this function if shutdown on OS can not be carried out for some reason)
Reference: Root Disk will not be deleted even when Instance is shut down.

Customer Portal /API

Edit Instance

Edit Instance Name
Modify Meta Data
HA Enabled/Disabled

Customers can edit the settings of such as Instance name, meta data, HA enabled/disabled etc.

Customer Portal /API

Console

Connect Console

Customers can connect to Console.
Keyboard locale is “Standard (US) Keyboard” when connecting from Customer Portal. Keyboard layout may be different from the above in case Customers use other language keyboards such as Japanese JIS Keyboard. In the event that Customers would like to use the keyboard other than “Standard (US) Keyboard”, they are required to change the keyboard layout with the OS settings, and then connect to the Console with RDP/SSH connection.

Customer Portal /API

Re-Size or Modify Instance

Change Flavor

Change compute Flavor.
Customers can change the Flavor when the Instance is booted. However, the Instance will be rebooted when Flavor change is completed.
Reference: Root Disk is not deleted even if Customers change the Flavor.

Customer Portal /API

Delete Instance

Delete Instance

Delete the Instance that is being turned off.
Root Disk is automatically deleted when Customers delete the Instance. Root Disk cannot be reverted once deleted.
Reference: Root Volume will remain as Volume even if Root Disk is deleted.

Customer Portal /API

Add Interface

Add Interface of Instance

Add Port of Logical Network and the virtual NIC of Instance respectively.
NTTCom recommend that you add the interface with the instance stopped.
Performing an instance startup or off / on (including rebooting with the HA function) after adding / deleting interfaces or attaching / detaching volumes, could cause the data volume to go offline or the interface device name to change.
Once the instance is turned off / on (* 1), this event will never occur again unless you add / delete interfaces or attach / detach volumes newly. Therefore, if an event occurs, please turn the instance off / on, and make sure the state of the interface, volume is not changed. (When adding / deleting an interface or attaching / detaching a volume in stopped state, it is unnecessary to turn off / on after instance startup)
After shutting down on the OS, confirm that the status of the instance is stopped, and execute “instance start” with portal or API. (Please note that rebooting on the OS is not enough)
It is not possible to simultaneously connect from multiple virtual NICs in one instance to the same logical network. (The maximum number of connections for one instance of the same logical network is 1)
*(To customers who use the API) When executing addition / deletion of the interface consecutively, after execution of one addition / deletion, confirm that the interface information of the instance is in the state after addition / deletion is completed If you can confirm it, please execute the next addition / deletion. Instance interface information is stored in Get server details API Response You can check with addresses.

Customer Portal /API

Delete Interface

Delete Interface of Instance

Delete Port of Logical Network and the virtual NIC of Instance respectively.
NTTCom recommend that you delete the interface with the instance stopped.
Performing an instance startup or off / on (including rebooting with the HA function) after adding / deleting interfaces or attaching / detaching volumes, could cause the data volume to go offline or the interface device name to change.
Once the instance is turned off / on (* 1), this event will never occur again unless you add / delete interfaces or attach / detach volumes newly. Therefore, if an event occurs, please turn the instance off / on, and make sure the state of the interface, volume is not changed. (When adding / deleting an interface or attaching / detaching a volume in stopped state, it is unnecessary to turn off / on after instance startup)
After shutting down on the OS, confirm that the status of the instance is stopped, and execute “instance start” with portal or API. (Please note that rebooting on the OS is not enough)
*(To customers who use the API) If the customer wants to delete / add interfaces consecutively, after execution of one addition / deletion, confirm that the interface information of the instance is in the state after deletion / addition completion If the customer can confirm it, please execute the next delete / add. Instance interface information is stored in Get server details API Response You can check with addresses.

Customer Portal /API

Create Snap Shot

Create the Image of Instance

Customers can convert the Root Disk connected to the Instance into an Image, and then store it into Image Storage as a Private Image Template in qcow2 format. For more details, please refer to the Service Description of Image Storage.
Customers are required to create snapshot after shutting down the Instance. In the event that snapshots are created while the Instance is booted, Data inconsistency will occur. As a consequence, they may not be able to restore the Image properly from the snapshot.

Reference: The scope of conversion to Image when creating a Snapshot is the Root Disk of Instance.
As such, Customers are noted that Root Volume or Data Volume is not converted as the Snapshot even if they are attached to the Instance.
If you want to upload the image of root volume or data volume, remove the target volume once from the corresponding virtual server and execute “Upload to image (the function of volume menu) ”.

Customer Portal /API

Note

Follow-UP: Instance Reboot

Reboot function is not provided as a Instance of Virtual Server. Customers are required to reboot on the OS command, or shut down and then boot the Instance.


Note

<Supplementary information> About changing the IP address of the instance

In order to change the IP address of the instance (logical network to be assigned), it is necessary to delete (disconnect) the interface of the IP address and add (reconnect) the interface of the IP address.


Specifications of Instance

NTT Com provides following functions as Virtual Server Menu by default:

Default Functions of Instance:

Functions

Overview

Virtual NIC

Instance has one virtual NIC by default. Customers can add virtual NIC by adding interface. Virtual NIC is recognized as 10Gbps interface.

Live Migration

When NTT Com performs the maintenance operation to migrate the infrastructure that accommodates Customers’ Instances, Live Migration enables the migration without shutting down these Instances.
When NTT Com needs to change the accommodating infrastructures of Customers Instance, NTT Com will be able to offer the maintenance without affecting their live Instances.
This Live Migration Function does not change the accommodations of Customers’ Instance beyond crossing over their original Zones/Groups.
HA(High Availability)
When there is a failure in the physical servers accommodating Customers’ Instance, other physical servers within the same Zone/Group will automatically take over the accommodations as their Instance.
HA function requires reboot; however, HA enables faster recovery of Customers’ Instance, as automatic boot of other physical servers is made the recovery faster than manual operation.
(Reference) Stopping the instance with GUI / API or shutting down on the OS does not activate the HA function (Instance is stopped)
Reference: HA Function is enabled by default. Customers can modify the settings disabled per Instance. However, once HA Function is disabled by Customers, Instances do not boot automatically in case they are powered off due to the maintenance by NTT Com or any failure occurs. In that case, Customer are required to boot the Instance by themselves.

(Reference) Metadata Service

In this service, the service called as “Metadata Service” is hold as service infrastructure and provided for distributing/configuring various setting.
Instance which is enabled to access to Metadata Service automatically access to Metadata Service when the instance is launched (including reboot by HA), therefore various setting is distributed.
Service description of Metadata Service is as below;

Service description of Metadata Service

IP address of Metadata Service

169.254.169.254

Conditions for accessing to Metadata Service

Metadata Service can be accessed if the following conditions are satisfied.
Resource which has default gateway IP address configured on the instance is existed.
The instance can reach(IP reachable) the resource which has default gateway IP address.

When access to Metadata Service

Launch Instance(including reboot by HA)

Distributed/Configured information by accessing to Metadata Service

When use Official Image, cloud-init(Linux series) or cloudbase-init(Windows series) is executed.
For the details of cloud-init and cloudbase-init, please see FAQ .

Fee for Metadata Service

Free of charge (Any fees for accessing Metadata Service such as transfer fee and service charge of Metadata Service are not required.)


2.2.3.2. Volume

Setting Items for Volume Creation

Customers can configure following settings when they create Volume:
After they complete these settings, Volume is created once they press “Create Volume” button in Customer Portal.

List of Settings for Creating Volume

Setting item list at the time of volume creation

Settings

Overview

Items

Action

Zone/Group

Select the Zone / Group

Select the Zone/Group that accommodates Volume to be created. If Customers select “Any Zone/Group”, the combination of Zone and Group will be determined randomly.

Customer Portal /API

Name of Volume

Name of Volume

Enter the name of Volume to be created. Customers can input up to 255 alphanumeric characters.(*1) They can also configure duplicated names within their Tenant.

Customer Portal /API

Descriptions

Comment

Customers can describe a comment on the Volume to be created. Customers can input up to 255 alphanumeric characters.(*1) They can also configure duplicated names within their Tenant. *Optional Service.

Customer Portal /API

Bootable

Set Bootable / Unbootable

Customers can set the Volume as bootable/unbootable.
Reference: Volume created from Private Image is bootable by default. As for Empty Volume, it is unbootable by default.

Customer Portal /API

Volume Source

Select Volume Source

Select the Image to put into the Volume to be created.
  • When Customers select By “No source selected”, Empty Volume is created.

  • When Customers select “Image”, they are required to select the Image as a Source.

Customer Portal /API

Capacity

Capacities

Specify the capacity of Volume to be created. Customers are required to select the capacity from the plan list prepared by NTT Com. If Customers would like to use Image as a Source, t.hey need to set the capacity in larger values than that of Image.

Customer Portal /API

*1 Available characters:abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!”#$%&’()*+,-./:;<=>?@[\]^_`{|}~

Operable Items in Volume

Following operations are executable in Volume:

Operable Items of Instance:

Operable Items of Instance:

Item

Overview

Items

Action

Volume Overview

Volume Overview

Customers can view Volume name, specs, connection status and Volume Source etc.

Customer Portal /API

Create Volume

Create Volume

Create Volume. If Customers select Image, the Volume with the Image (either Bootable or Unbootable Volume) will be created.
If they do not select any template, Empty Volume will be created. For more details, please refer to the previous section.

Customer Portal /API

Manage Connectivity

Set Instance
to be Attached/Detached
Customers can attach/detach their Volume to Instance. They can assign the Volume as Data Volume by attaching additional Volume to the Instance.
After attaching / detaching the volume, start up the instance and check that the state of the interface and the volume are not changed. Performing an instance startup or off / on (including rebooting with the HA function) after adding / deleting interfaces or attaching / detaching volumes, could cause the data volume to go offline or the interface device name to change.
Once the instance is turned off / on (* 1), this event will never occur again unless you add / delete interfaces or attach / detach volumes newly. Therefore, if an event occurs, please turn the instance off / on, and make sure the state of the interface, volume is not changed. (When adding / deleting an interface or attaching / detaching a volume in stopped state, it is unnecessary to turn off / on after instance startup)
*1) You are required to “Shut off instance” and “Start instance” via Customer Portal / API. (Please note that it was not done at OS reboot)
Attach/detach volumes can be operated even if the instance is in running, however, please operate OFF/ON(*1) after deleting interface for the reason described above. Operating attach volumes after instance is stopped is recommended. If operate attach in running (i.e. online attach), it might be occurred to unable to recognize attached volumes normally.
When attaching a volume to an instance booted from an ISO image (an instance composed of an ISO image and an empty volume), the maximum number of attachable volumes is four. In addition, when attaching two or more volumes to an instance booted with an ISO image from the customer portal, please note that the second and subsequent volumes are attached with the device format with hdc, hdd, etc., and the I / O performance can be reduced. (In the case of API, this can be avoided because you can select the device format). For the flow of creating an instance from the ISO image, please refer to the ** `tutorial<https://ecl.ntt.com/en/documents/tutorials/rsts/Virtual-Server/create/from_privateiso.html>`_** .
Reference: In the case Customers would like to utilize Data Volume as the data disk of their Instance, mount settings will be needed on the OS after the Data Volume is attached with this operation.
*As for attaching / detaching repeatedly about the volume which the OS of monthly fixed charge is entered, fixed monthly fee for OS is generated accordingly, please note.

Customer Portal /API

Boot Instance

Boot Instance from Volume

Create and boot Instance with configuring Root Volue as Bootable Volume.

Customer Portal /API

Create Volume

Create Volume

Create Volume. If Customers select Image, the Volume with the Image (either Bootable or Unbootable Volume) will be created.
If they do not select any template, Empty Volume will be created. For more details, please refer to the previous section.

Customer Portal /API

Upload to Image

Get Volume Image

Customers can convert the Volume into Image, and then store it into Image Storage as a Private Image Template in qcow2 or raw format.
Uploading to Image (Getting Volume Image) cannot be operated in case the Volume is attached to the Instance. Customers are required to perform this operation after detaching the Volume from the Instance.
In the case Customers would like to convert Root Volume into Image, they need to delete the Instance first, and then uploading to the Image without connecting any Instance, which is the same status as Bootable Volume.
In case of deleting the instance for image of the root volume and uploading to the image and then creating the instance again, please note that the instances before and after the uploading operation on the image are handled as different instances, so the usage fee is charged as another instance. (For example, if you use an OS with a fixed monthly fee, both the monthly fixed fee of the OS for the instance before the upload operation and the monthly fixed fee for the OS after the operation will be charged))

Customer Portal /API

Delete Volume

Delete Volume

Delete Volume
Volume cannot be reverted once deleted.

Customer Portal /API

Edit Volume

Edit Volume Name

Customers can edit the name and description of Volume.
Furthermore, they can set bootable/unbootable volume. (Setting Bootable means that they can select as a boot source of Instance, and setting unbootable means they cannot.)

Customer Portal /API

Volume expansion

Volume expansion

Created volume size is expanded.
*The change cannot be made in case the Volume is attached to the Instance. Customers are required to detach the Volume from the Instance and make the change without connecting to any instance.
*Changes cannot be made while uploading to Image (converting Volume into Image).
*Rood Disk cannot be expanded. This function only targets Volume.
When expanding the root volume and deleting the instance, uploading to the image and then creating the instance again, the instances before and after the uploading operation on the image are handled as different instances, (For example, if you use an OS with a fixed monthly fee, both the monthly fixed fee of the OS for the instance before the upload operation and the monthly fixed fee for the OS after the operation are generated in the image)

Customer Portal /API


2.2.4. Menu

2.2.4.1. List of Menu

The menu list provided by Virtual Server menu is as follows:

Menu List of Virtual Server Menu

Menu

 

Virtual Server

Compute

 

Volume

  OS

2.2.4.2. Plan List

Compute

Following is the List of Flavors (Plans) for Compute:

List of Flavors for Compute

Menu

Flavor

vCPU GB

Compute

1CPU-4GB 1 4
  2CPU-8GB 2 8
  4CPU-16GB 4 16
  8CPU-32GB 8 32
  16CPU-64GB 16 64
  32CPU-128GB 32 128
  1CPU-2GB 1 2
 

2CPU-4GB

2 4
  4CPU-8GB 4 8
  8CPU-16GB 8 16
  16CPU-32GB 16 32
  32CPU-64GB 32 64
  1CPU-8GB 1 8
  2CPU-16GB 2 16
  4CPU-32GB 4 32
  8CPU-64GB 8 64
  16CPU-128GB 16 128

** Image diagram of Compute’s flavor list **

コンピュートのフレーバー一覧のイメージ

Note

  • In the case of flavors of 32vCPU, memory access performance may decrease by about 10%, so please be careful in advance.

  • (In the case of flavors of 32vCPU, there is a possibility of straddling the physical socket, which may reduce memory IO throughput.)


Note

  • 1vCPU for Compute will be max 2.30GHz or equivalent of such (as of March 2016); however, this may be changed as NTT Com changes the specification of physical servers.

  • Furthermore, Customers are advised that the this menu does not guarantee the full-time maximum processing performance.

Volume

Following is the list of sizes (plans) for Volume:

List of Volume Size

Menu

Size

Volume

15GB
  40GB
  80GB
  100GB
  300GB
  500GB
  1TB(1,024GB)
  2TB(2,048GB)
  3TB(3,072GB)
  4TB(4,096GB)

Official Image

The official image plan is as follows.

Official image plan

Menu

Plan

Official Image Template

OS Version

OS Editions

Application Version

Application Edition

OS CentOS CentOS 7.1-1503 CentOS 7.1-1503      
    CentOS 7.3-1611 CentOS 7.3-1611      
  Ubuntu Ubuntu 14.04.1 Ubuntu 14.04.1      
    Ubuntu 16.04.1 Ubuntu 16.04.1      
  Windows Server Windows Server 2012 R2 Standard Edition Windows Server 2012 R2 Standard Edition    
    Windows Server 2016 Datacenter Edition Windows Server 2016 Datacenter Edition    
  Red Hat Red Hat Enterprise Linux 7.1 Red Hat Enterprise Linux 7.1      
    Red Hat Enterprise Linux 7.3 Red Hat Enterprise Linux 7.3      
    Red Hat Enterprise Linux 7.1 for SAP Applications Red Hat Enterprise Linux 7.1 for SAP Applications    

Middleware

SQL Server SQLServer 2014 Windows Server 2012 R2 Standard Edition SQL Server 2014 SP1 Standard Edition
          SQL Server 2014 SP2 Standard Edition
    SQLServer 2016 Windows Server 2012 R2 Standard Edition SQL Server 2016 SP1 Standard Edition
      Windows Server 2016 Datacenter Edition SQL Server 2016 SP1 Standard Edition
  RDS SAL Windows Server Remote Desktop Services SAL Windows Server 2012 R2 Standard Edition Windows Server Remote Desktop Services SAL  
      Windows Server 2016 Datacenter Edition Windows Server Remote Desktop Services SAL  
  Oracle OracleDB 12.1.0.2.0 SE2 Oracle Linux 7.1   Oracle Database 12c Release 1 (12.1.0.2.0) Standard Edition 2(SE2)
    OracleDB 12.1.0.2.0 SE2 Red Hat Enterprise Linux 7.1   Oracle Database 12c Release 1 (12.1.0.2.0) Standard Edition 2(SE2)
    OracleDB 12.1.0.2.0 SE2 Windows Server 2012 R2 Standard Edition Oracle Database 12c Release 1 (12.1.0.2.0) Standard Edition 2(SE2)
      Windows Server 2016 Datacenter Edition Oracle Database 12c Release 1 (12.1.0.2.0) Standard Edition 2(SE2)
    OracleDB 12.1.0.2.0 EE Oracle Linux 7.1   Oracle Database 12c Release 1 (12.1.0.2.0) Enterprise Edition(EE)
    OracleDB 12.1.0.2.0 EE Windows Server 2012 R2 Standard Edition Oracle Database 12c Release 1 (12.1.0.2.0) Enterprise Edition(EE)

2.2.4.3. Subscriptions Method

Any Customers with contracts of Enterprise Cloud 2.0 are able to subscribe Virtual Server.
Customers can create resources via Customer Portal/API in real-time.
NTT Com charges based on the usage of resources created by Customers (such as time and capacity).

2.2.5. Terms and Conditions of Use

2.2.5.1. Conditions for Usage with Other Services

Prerequisite for Virtual Server Menu

In order for Customers to create Instance, they are required to create Logical Network in advance.
In order for Customers to create Instance,
they are required to create Logical Network in advance.
*Customers can create Volume without preparing Logical Network in advance.

Conditions for Usage of Virtual Server Menu with Other Menus

There are no specific requirement or conditions for pairing combination of Virtual Server menu with other menus.
Customers can combine Virtual Server menu with the following menus;

Examples of Pairing Conditions with Other Menus:

Menu

Sub Menu

Use Case for Combination with Virtual Server Menu

Image Storage

 
Customers can store Volume and Instance by converting into Images, and can bring in and store their Image files. They can create Instance or Volume with OS Image from these Images above.

Storage

Block Storage (I/O Performance)

Customers can Block Storage as an external disk of Instance by connecting Block Storage and Instance via Logical Network.
Even if Customers store OS Image within the Block Storage, they cannot boot the Instance from Block Storage. That is, the Block Storage cannot be the Root Volume.
When Customers utilize Instance, they are required to use the Volume of Virtual Server Menu for storing OS Image.

Network

Logical Network

In the case Customers connect Instances with Logical Network, the communication among Instances is available, as well as the communication among Instances and other services.

 

Internet Connectivity

In the case Customers connect Instances with Internet or VPN Connectivity menu via Logical Network, Instances can connect to Internet or VPN.

 

VPN Connectivity

Same as above

 

DC Inter-Connectivity

Secure, high-speed, free/low cost communication is realized through connections between Instances in different regions and connecting Instance and colocation.

 

Enterprise Cloud Inter-Connectivity (EIC)/ Colocation Inter-Connectivity (CIC)

In the case Customers connect Instances with Enterprise Cloud Inter-Connectivity (EIC) or Colocation Inter-Connectivity (CIC), Instances can connect to Enterprise Cloud 1.0 or colocation.

 

Firewall (Brocade 5600 vRouter)

In the case Customers connect Instances with Firewall via Logical Network, they can control the network communication with Firewall menu.

 

Load Balancer(NetScaler VPX)

Load balancing of multiple instances will be possible by connecting the instance and the load balancer in the logical network.

Middleware

SAP HANA

Combined with the SAP HANA menu, the customer can configure the SAP system infrastructure.

  Oracle

Customers can use Oracle Database and cluster (Oracle Real Application Clusters (RAC)) configuration on Instance.

Support  

Virtual Server menu is supported with the selected level of Support menu.

Monitoring  

Customers can monitor the status of Instances with Monitoring menu.



Warning

WARNING: Please refer to NG configuration of Logical Network when customer connects resources.

2.2.5.2. Minimum Contract Period

This Service does not set a minimum contract period.

2.2.5.3. Notes for Customers Prior to Use

Support Coverage

This menu provides support with following coverage:

  • The failures of Virtual Server’s infrastructure, Portal screen or API are supported by this menu.
    However, Customers are advised that the failures above the OS layer, such as application installed in the Virtual Server, are not supported.
  • But for the virtual server that was created from the official image template it will be supported,
    Bug suspected because of the settings and applications on the customer’s OS, will be unsupported for the inquiry.
  • With regards to the range support of the official image template, please refer to the service description of the OS.
  • For the virtual server that was created from the private image template will be principle unsupported.
    (Please note that NTT Com will provide the knowledge. But the analysis, surveys, etc. is not provided.)
  • When setting an IP address fixedly on the instance OS by turning off the DHCP of the logical network etc., please set the IP address assigned to the interface on the logical network on the OS.
    Setting an IP address different from the IP address assigned on the logical network on the instance OS is deprecated and is not supported. (There is a possibility that communication can not be performed normally)

2.2.5.4. Notes

  • NTT Com does not take any backup of Customers’ data stored in this menu. Customers are strongly recommended that they obtain backup data as needed.

  • Regardless of the cause, NTT Com does not take any responsibility for any direct or indirect damages to Customers or third party when Customers’ data stored in this menu are lost, damaged, leaked or failed in any way, and are being utilized for any purpose.

  • NTT Com will erase the Customers’ data stored in this menu in the event that Customers terminate the contract of this menu.

  • NTT Com will terminate or erase the subscription of the customer on this menu if the customer decides that it violates the terms of this menu or other policy or in case of doubt.

  • This menu provides following support:

    • Infrastructure of this menu is monitored 24/7.

    • Maintenance and troubleshooting are provided based on the details on Support menu described in other documents.

    • This menu provides HA function. In case there is a failure in the physical servers accommodating Virtual Server menu, other physical servers will automatically take over the accommodation. However, HA functions requires reboot, and Customers will experience the disconnection due to the reboot and switchover. Customers are noted that they cannot perform any operation to Virtual Servers during the reboot and switchover is being processed.

    • The quality of operation is based on the Service Description of Support.

  • In the event that Customers’ Instance and Volume do not work properly due to this menu, NTT Com regards this as a “failure”. NTT Com will inform the Customers with the methods regulated separately. Distinctively, NTT Com will consider the following events as failures:

    • Sudden halt of VM

    • Complete disconnection of network at the side of Virtual Server.

    • Failure of physical servers’ NIC.

    • Failing to boot OS of Customers’ Instance.

    • Failure of disk access due to the unexpected detachment.

    • Data loss and damage (*excluding intermittent packet loss)

    • Failure of Customer Portal / API that affect such as Customers’ operation.

    Following events are not regarded as failures:

    • Host migration by Live Migration functions.

    • Any failure or instability above the OS layer

    • Failure of creating resources.

    • Quality Deterioration.


2.2.5.5. Restrictions

Restrictions: Instance

Instance has following restrictons:

Restrictions: Instance

Category

Restrictions

Items

Number of Virtual NICs

1~16

Up to 16 Virtual NICs are available per Instance.

Number of IPs for Setting Virtual NICs

1
Customers are able to assign one IP address per Virtual NIC of an Instance.
They are not allowed to assign multiple IP addresses per one Virtual NIC.

Bandwidth of Virtual NICs

10Gbps at Best Effort
(Bandwidth Restrictions may apply)
Bandwidth of Virtual NIC is 10Gbps best effort. However, for the stability of this menu, NTT Com sets bandwidth restriction depending on the flavor.

Performance of root disk

Variable upper limit for IOPS and throughput
To stabilize the service, a variable upper limit is set for IOPS and throughput of the root disk.
The limit of IOPS and throughput is applicable within 3 hours after the instance(i.e. the root disk) is created.(The performance of root disk might be down within 3 hours by the limit)

Number of Attachable Disks

0~10
Up to 10 Volumes will be attachable in total.
Reference: The maximum number mentioned above does not include Root Volume or Root Disk.
*For ISO image booted instances, the number of attachable volumes is three.

Set number of key pair

0~120

Customers can create up to 120 key pairs per Tenant.

Number of Meta Data Settings

0~128

Up to 128 rules are available as the Key Value of Meta Data.

Session

Approx. 50,000 Sessions

Approx. 50,000 sessions per instance are set as the limit of the number of session.
Therefore, if many sessions are required to customer’s system(*1), please note it when use virtual server or please use baremetal server.
(Baremetal server is not set a limit of the number of session)
In virtual server, from the view point of stable system operation, the limit is set for disturbing other instance influence as shared service.
However, it does not mean that virtual server guarantees session is always available up to the limit.
For example, Microsoft Office 365 tends to require many sessions.
It depends on situation, however, if approx.1000 IDs transactions for Microsoft Office 365 are handled on virtual server
(i.e. if virtual router which is constructed on virtual server handles approx.1000 IDs transactions for Microsoft Office 365),
it might reach the limit.

Constraints of the post-installation actions (Post-install script / key pair / meta data)

  • Post-install script

    Post-install script has, after startup of instance, the ability to set the executable script automatically. Restrictions of the Post-install script function is as follows.

Category

Methods

Numbers

Unit

Maximum Number of Script

Customer Portal /API

1

Script

Script Size

Customer Portal

16 kb
  API 64 kb

Encoding Method

Customer Portal /API

base64 NA

<Reference>For respective OS Format Use Cases
As for the format of each OS, Please refer to the following table:

Official Image Template

Execution File

Execution Format

CentOS/Ubuntu/Red Hat cloud-init https://help.ubuntu.com/community/CloudInit
Windows cloudbase-init https://github.com/stackforge/cloudbase-init

  • Key pair

    Restrictions on the registration of the key pair will be as follows.

Category

Methods

Numbers

Unit

Maximum Number of File

Customer Portal /API

10

File

Length of File Paths

Customer Portal /API

255 byte

Script Size

Customer Portal /API

10 kb

Encoding Method

Customer Portal /API

base64 NA

Note

The registered key pair is managed per user. Refer to followings for specification.

  • Only registered users can view and use the registered key pair (it can not be viewed or used by anyone other than registered users)

  • Registered key pairs can be viewed and used from other tenants as long as they are registered users.


  • Meta Data

    Restrictions on the registration of the meta data will be as follows.

Category

Methods

Numbers

Unit

Maximum Number of Configurable Key/Value Pair

Customer Portal /API

128

Pairs

Maximum Letter Size of Configurable Key and Configurable Value Respectively

Customer Portal /API

255 byte

Restrictions: Volume

Volume has following restrictions:

Restrictions: Volume

Category

Restrictions

Items

Capacity

Select from the plan list. Each plan has static capacity from 15GB to 4,096GB (4TB).

Up to 4096GB (4TB) is available per volume.

Manage Connectivity

Connectivity Management

Connectivity with the resources in different Zones/Groups

Performance

Variable upper limit for IOPS and throughput

To stabilize the service, a variable upper limit is set for IOPS and throughput of the volume.
The limit of IOPS and throughput is applicable within 3 hours after the volume is attached.(The performance of volume might be down within 3 hours by the limit)

Note

Customers are not allowed to connect the Instance with the Volume located in different Zone/Group.

ゾーン/グループとボリューム

As mentioned above, Customers are not allowed to connect the Instance and Volume by crossing over the Zone/Group they belong to.

Restrictions on the official image

Following is the size of each Official Image Template.
And this is also the size of Root Disk when Instance is created.
Furthermore, when Customers create the Volume from Official Image Template, they cannot create the Volume with the size less than the following values.

Official Image Template Size

Official Image Template

Size

CentOS 7.1-1503 15GB
CentOS 7.3-1611 15GB
Ubuntu 14.04.1 15GB
Ubuntu 16.04.1 15GB
Windows Server 2012 R2 Standard Edition 80GB
Windows Server 2016 Datacenter Edition 80GB
Red Hat Enterprise Linux 7.1 40GB
Red Hat Enterprise Linux 7.3 40GB
Red Hat Enterprise Linux 7.1 for SAP Applications 40GB
SQL Server 2014_Windows Server 2012 R2 80GB
SQL Server 2016_Windows Server 2012 R2 80GB
SQL Server 2016_Windows Server 2016 80GB
Windows Server Remote Desktop Services SAL_Windows Server 2012 R2 80GB
Windows Server Remote Desktop Services SAL_Windows Server 2016 80GB
OracleDB 12.1.0.2.0 SE2_Red Hat Enterprise Linux 40GB
OracleDB 12.1.0.2.0 SE2_Oracle Linux 40GB
OracleDB 12.1.0.2.0 SE2_Windows Server 2012 R2 80GB
OracleDB 12.1.0.2.0 SE2_Windows Server 2016 80GB
OracleDB 12.1.0.2.0 EE_Oracle Linux 40GB
OracleDB 12.1.0.2.0 EE_Windows Server 2012 R2 80GB

Maximum Number of Resource Limits

This Service sets the following maximum limits for the creatable resources for every ONE Tenant.

Maximum Number of Available Resources per Tenant

Menu

 

Uppermost Maximum Numbers

Virtual Server

Compute

Maximum Number of Available Resources per Tenant

 

Volume

Up to 512TB or 512 Volumes can be created per Tenant.


Note

The registered key pair is managed per user. Refer to followings for specification.

  • Only registered users can view and use the registered key pair (it can not be viewed or used by anyone other than registered users)

  • Registered key pairs can be viewed and used from other tenants as long as they are registered users.


2.2.6. Pricing

2.2.6.1. Initial Fee

There is no initial fee.

Note

  • Please refer to the service description of the OS menu for the price specification of the OS menu.

    https://ecl.ntt.com/en/documents/service-descriptions/rsts/server/OS/index.html

  • As described in the service description of the OS menu, if the root disks storing the OS of the official image template of this menu and volumes are multiple-attached to one instance, please note in advance that the OS menu fee will be added, depending on the number of root disks and volumes attached.


2.2.6.2. Monthly Fee

Monthly charge applied for Virtual Server menu is per-minute-basis with capped pricing per month. This is applied to Compute, Volume and OS respectively.

Note

Please refer to the service description of the OS menu for the price specification of the OS menu.
As described in the service description of the OS menu, if the root disks storing the OS of the official image template of this menu and volumes are multiple-attached to one instance, please note in advance that the OS menu fee will be added, depending on the number of root disks and volumes attached.
*As for attaching / detaching repeatedly about the volume which the OS of monthly fixed charge is entered, fixed monthly fee for OS is generated accordingly, please note.
*In the case of using “Upload to Image” function, if instances are deleted, uploaded to the image and created again, instances before and after the upload operation are treated as different instances in the image, Please note that usage fees for instances and OS are also treated separately (Please note that monthly fixed fee will be generated before and after uploading to the image if the fee for OS is fixed monthly)

2.2.7. SLA for Virtual Server Menu

2.2.7.1. SLA

The SLA of this menu is based on the standardized SLA for Enterprise Cloud 2.0; for the details please refer to the Service Description of SLA.

Note

Notes for Customers Regarding SLA for Virtual Server Menu

  • Customers are noted that the failure time for following cases is not counted in the SLA for Virtual Server menu:

    • Recovery time due to the HA activation.

    • The case NTT Com cannot recover by HA as Customers has been disabled the HA function by themselves.

    • Failures of OS or software installed in Virtual Servers

    • Performance DeterioratiComon of compute resources (CPU/Memory/Disk).

    • Maintenance performed by NTT Com by predetermined methods.

    • Failure of creating resources.

    • Failure of Customer Portal/API.

  • As for the data loss or inconsistency, SLA will be applied to the month when these issues occur, only in the case these issues are attributable to NTT Com.