Enterprise Cloud Knowledge Center
Close the Menu
Home > Enterprise Cloud 2.0 Support Information > FAQ - Enterprise Cloud 2.0 > I want to place an ISO file in the image storage area and mount the ISO image on the virtual server. Is there a function to mount the ISO image as an optical drive?

FAQ

I want to place an ISO file in the image storage area and mount the ISO image on the virtual server. Is there a function to mount the ISO image as an optical drive?

(:Last updated）

The function which mount the ISO image on the virtual server as an optical drive is not provided by this service. (The ISO image of the virtual server can only be used for OS installation.)
We apologize for the inconvenience. Please mount the ISO image on the virtual server and mount the ISO image using the virtual drive etc.

Reference: Service Descriptions _ Image storage area - Private ISO

Is this page helpful?

Yes No
  • ECL2.0
    •  
  • Virtual Server
    •  

Related Pages

  • DNS setting of virtual server RHEL7.5 / CentOS 7.5ECL2.0, OS, Virtual Server

    Issue

    DNS setting is set to 8.8.8.8 after deploying virtual server menu Red Hat Enterprise Linux 7.5/Cent OS 7.5 image.

    Solution

    Execute the following command and change the IP address in the DNS settings (nameserver) to a value appropriate for the customer.

    1# vi /etc/resolv.conf

    For articles on DNS servers, please also refer to the following the link.

    Is the DNS Server provided to Customers?

    https://ecl.ntt.com/en/faq/2.0/cfgw-dns/

    Open in a new window
  • The volume can not be operated when the instance is deleted while the volume is attachedECL2.0, Virtual Server

    Issue

    When you delete an instance while the volume is attached, sometimes you can’t operate the volume. For example, you can’t delete or attach the volume to another instance.

    In this case, The instance is deleted completely, but the volume attached to “None”  and status is still “In-use”.

     

    Solution

    In order to avoid this issue, please detach a volume after turning off an instance before you delete an instance.

    If this issue is happen and you can’t operate the volume,  please inquire with a ticket.

    Open in a new window
  • Red Hat Enterprise Linux 7.5 is available at ECL2.0 virtual serverECL2.0, Virtual Server

    Thank you for using Enterprise Cloud 2.0(ECL2.0)service.

    Please be informed that new version of official image template is available at Enterprise Cloud2.0

    Red Hat Enterprise Linux 7.5 for Virtual Server is available

    ■Official image For Virtual Server

    ・Red Hat Enterprise Linux 7.5

    Region: JP2/JP4/JP5/US1/UK1/DE1/SG1/HK1

    Service launch: May 22, 2019

    Open in a new window
  • The volume created by server API with "source_type:blank" property in "block_device_mapping_v2" does not work properlyECL2.0, Virtual Server

    Issue

    API for creating virtual server instance can create volumes-attached instance by using "block_device_mapping_v2" in request body. When the "source_type": "blank" in "block_dvice_mapping_v2" is specified, the API creates a new volume for the instance.

    The instance can use the volume until you stop the instance by API or GUI. Once you stop the instance, you can not see any volume from the instance.

    Detail

    This section show an example how to reproduce this issue. The JSON shown below contains "source_type:blank" in "block_device_mapping_v2". At first, please call create server API with the JSON.

    {

       "server": {

           "availability_zone": "zone1-groupa",

           "block_device_mapping_v2": [

               {

                   "boot_index": 0,

                   "delete_on_termination": true,

                   "destination_type": "volume",

                   "source_type": "image",

                   "uuid": "29266056-fd5b-4f73-8b4d-194785cbbc45",

                   "volume_size": 100

               },

               {

                   "boot_index": 1,

                   "delete_on_termination": true,

                   "destination_type": "volume",

                   "source_type": "blank",

                   "volume_size": 100

               },

               {

                   "boot_index": 2,

                   "delete_on_termination": true,

                   "destination_type": "volume",

                   "source_type": "blank",

                   "volume_size": 15

               }

           ],

           "flavorRef": "1CPU-4GB",

           "imageRef": "",

           "name": "test-instance",

           "networks": [

               {

                   "fixed_ip": "10.10.0.6",

                   "uuid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",

               }

           ],

           "user_data": ""

       }

    }

    Please look the following screenshot showing two volumes, vdb(100G) and vdc(15G), are attached to the instance before the instance stops for the first time.

    The following screenshot showing after the instance are stopped and started, the volumes, vdb(100G) and vdc(15G), are not visible in the instance.

    And you are not able to attach/detach the volumes with Cloud Computing Control Panel(GUI) and API anymore because it becomes an inconsistent state.

    Workaround

    Please don't create instance with "block_device_mapping_v2" including source_type: blank.

    If you want to create a volumes-attached instance, create the volume in advance by virtual server volumes API or Cloud Computing Control Panel(GUI). After that, set "source_type: volume" and "uuid: <volume uuid>".

    The following JSON is one of example.

    {

       "server": {

           "availability_zone": "zone1-groupa",

           "block_device_mapping_v2": [

               {

                   "boot_index": 0,

                   "delete_on_termination": true,

                   "destination_type": "volume",

                   "source_type": "image",

                   "uuid": "29266056-fd5b-4f73-8b4d-194785cbbc45",

                   "volume_size": 100

               },

               {

                   "boot_index": 1,

                   "delete_on_termination": true,

                   "destination_type": "volume",

                   "source_type": "volume",

                   "uuid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

               },

               {

                   "boot_index": 2,

                   "delete_on_termination": true,

                   "destination_type": "volume",

                   "source_type": "volume",

                   "uuid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

               }

           ],

           "flavorRef": "1CPU-4GB",

           "imageRef": "",

           "name": "test-instance",

           "networks": [

               {

                   "fixed_ip": "10.10.0.6",

                   "uuid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",

               }

           ],

           "user_data": ""

       }

    }

     

    Open in a new window
  • CPU model recognition errorECL2.0, Virtual Server

    Issue

    When creating virtual server instances from certain OS images in the following regions, the CPU model is recognized incorrectly.
    Incorrect: Skylake
    Correct: Broadwell
    *CPU model can be comfirmed by executing "lscpu" command. (It will be shown as Model name.)

    Region

    JP2, JP4, US1, DE1

    OS

    Red Hat Enterprise Linux
    Windows Server 2016

    Solution

    The issue has been resolved by our service infrastructure update work scheduled on May 9th, 2019.

    Customers using the affected instances were notified with details after May 9th, 2019, as the instances need to be stopped and relaunched after the service infrastructure update work is completed.

    Please take the following action for the applicable customers.

     

    1. Shutdown the instance on OS
    *[Caution] Please note that the settings are not reflected by restarting
    2. After confirming the os is stopped on the portal, start the instance from Portal/API

    Open in a new window

Support Information

Enterprise Cloud 2.0

Enterprise Cloud 1.0

We appreciate your cooperation in improving the site

Did this FAQ be helpful? If you have any comments, please let us know.

Thank you

Your feedback has been received.

▲