Adding Storage

For this example scenario, you attach an iSCSI storage to your virtualization environment and then upload an ISO image to the data domain. If you do not have access to an iSCSI device, refer to Storage in the Oracle Linux Virtualization Manager: Administration Guide for the procedures for adding other storage types to your virtualization environment.

Attaching an iSCSI Data Domain

For iSCSI storage, a storage domain is created from a volume group that is composed of pre-existing LUNs.

To attach an iSCSI data domain to your virtualization environment:

  1. Go to Storage and then click Domains.

    The Storage Domains pane opens.

  2. Click New Domain.

    The New Domain dialog box opens.

  3. For the Name field, enter a name for the data domain.

  4. From the Data Center drop-down list, select the Data Center for which to attach the data domain.

    By default, the Default option is selected in the drop-down list.

    For this step, leave Default selected from the drop-down list because the default data center and cluster are used for the example scenario.

    For the procedures to create new data centers or a new clusters, refer to Data Centers or Clusters tasks in the Oracle Linux Virtualization Manager: Administration Guide.

  5. From the Domain Function drop-down list, select the domain function. By default, the Data option is selected in the drop-down list.

    For this step, leave Data as the domain function because you are creating a data domain in this example.

  6. From the Storage Type drop-down list, select iSCSI.

  7. For the Host to Use drop-down list, select the host for which to attach the data domain.

    For this example scenario, select the host added in Adding a KVM Host to the Manager.

  8. When iSCSI is selected for the Storage Type, the Discover Targets dialog box opens and the New Domain dialog box automatically displays the known targets with unused LUNs under the Target Name column.

    If the Discover Targets dialog box is not visible in the New Domain dialog box, make sure that you have selected the Target > LUNS view on the left-side of the column.

    If the target from which you are adding storage is not listed, complete the following fields in the Discover Targets dialog box:

    1. For the Address field, enter fully qualified domain name or IP address of the iSCSI host on the storage array.

    2. For the Port field, enter the port to connect to on the host when browsing for targets. By default, this field is automatically populated with the default iSCSI Port, 3260.

    After completing these fields, click Discover.

    The Target Name column updates to list all the available targets discovered on the storage array.

  9. Under the Target Name column, select the desired target and select the black right-directional arrow to log in to the target.

    The Storage Domains pane refreshes to list only the targets for which you logged in.

  10. Click + to expand the desired target.

    The target expands to display all the unused LUNS.

  11. Click Add for each LUN ID that is to connect to the target.

  12. (Optional) Configure the advanced parameters.

    If you are using ZFS storage, you must uncheck the Discard after Delete option.

  13. Click OK.

    You can click Tasks to monitor the various processing steps that are completed to attach the iSCSI data domain to the data center.

    After the iSCSI data domain has been added to your virtualization environment, you can then upload the ISO images that are used for creating virtual machines in Creating a New Virtual Machine.

Uploading Images to the Data Domain

Before using the Manager to upload images to the data domain, you must perform the following steps to ensure that the prerequisites for uploading images have been met on the Manager and KVM hosts.

Before You Begin

To ensure that the prerequisites for uploading images to the data domain have been met:

  1. On the engine host, verify that the ovirt-image-proxy service has been configured and is running.

    # systemctl status ovirt-imageio-proxy.service

    When the service is running, the output displays as follows.

    # systemctl status ovirt-imageio-proxy.service
      ovirt-imageio-proxy.service - oVirt ImageIO Proxy
       Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service; enabled; 
       vendor preset: disabled)
       Active: active (running) since Mon 2019-03-25 13:12:29 PDT; 2 weeks 0 days ago
     Main PID: 28708 (ovirt-imageio-p)
       CGroup: /system.slice/ovirt-imageio-proxy.service
               └─28708 /usr/bin/python2 /usr/bin/ovirt-imageio-proxy
    ...

    This service is automatically configured and is started when you run the engine-setup command during the installation of the Manager.

  2. On the engine host, copy the ovirt-engine certificate as a trusted certificate to the /etc/pki/ca-trust/source/anchors/ovirt.ca.pem file, or use the correct path of the file:

    # scp /etc/pki/ovirt-engine/ca.pem \
    root@image-proxy-address:/etc/pki/ca-trust/source/anchors/ovirt.ca.pem

    You can obtain the address to enter for the image-proxy-address variable by entering the engine-config --get ImageProxyAddress command.

  3. On the KVM host, verify that the ovirt-image-proxy service has been configured and is running. For example:

    # systemctl status ovirt-imageio-daemon
      ovirt-imageio-daemon.service - oVirt ImageIO Daemon
       Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-daemon.service; disabled; 
       vendor preset: disabled)
       Active: active (running) since Wed 2019-03-27 18:38:36 EDT; 3 weeks 4 days ago
     Main PID: 366 (ovirt-imageio-d)
        Tasks: 4
       CGroup: /system.slice/ovirt-imageio-daemon.service
               └─366 /usr/bin/python /usr/bin/ovirt-imageio-daemon
    
    Mar 27 18:38:36 myserver systemd[1]: Starting oVirt ImageIO Daemon...
    Mar 27 18:38:36 myserver systemd[1]: Started oVirt ImageIO Daemon.
    
  4. On the KVM host, ensure the ovirt-image-proxy is properly linked by creating a directory for the certificate and then creating a symbolic link to the certificate.

    # mkdir /etc/pki/ovirt-engine/
    # ln -s /etc/pki/ca-trust/source/anchors/ovirt.ca.pem /etc/pki/ovirt-engine/ca.pem
  5. Verify that the certificate authority has been imported into the web browser used to access the Manager by browsing to the following URL and enabling the trust settings: https://engine_address/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA

  6. Verify that you are using a browser that meets the browser requirement to access the Administration Portal.

    For more information, refer to the Logging in to the Administration Portal.

  7. Proceed to Uploading an ISO Image to the Data Domain.

Uploading an ISO Image to the Data Domain

To upload an ISO image to data domain using the Manager:

  1. Download or copy an ISO image file that you want to upload into your environment to a location on your desktop, laptop, or a system where the Manager is accessible from a Web browser.

  2. Go to Storage and then click Disks.

    The Disks pane opens.

  3. Click Upload and then select Start from the drop-down list.

    The Upload Image dialog box opens.

  4. Click Choose File and navigate to the location where you saved the ISO image.

  5. Complete the Disk Options section of the dialog box.

  6. Ensure that the prerequisites have been met by clicking Test Connection.

    If the test returns a warning or error message, refer to Before You Begin to review the prerequisites.

  7. Click OK to start uploading the ISO image.

    The status field on the Disks pane tracks the progress of the upload.

    After the ISO image upload is completed successfully, you can attach the image to virtual machines as CDROMs or use the image to boot virtual machines.