Prerequisites

1. Install the NFS utils package.

   # dnf install nfs-utils -y

2. To check the enabled versions:

   # cat /proc/fs/nfsd/versions

3. Enable the following services:

   # systemctl enable nfs-server
   # systemctl enable rpcbind

Procedure

1. Create the group kvm:

   # groupadd kvm -g 36

2. Create the user vdsm in the group kvm:

   # useradd vdsm -u 36 -g kvm

3. Create the storage directory and modify the access rights.

   # mkdir /storage
   # chmod 0755 /storage
   # chown 36:36 /storage/

4. Add the storage directory to /etc/exports with the relevant permissions.

   # vi /etc/exports
   # cat /etc/exports
    /storage *(rw)

5. Restart the following services:

   # systemctl restart rpcbind
   # systemctl restart nfs-server

6. To see which export are available for a specific IP address:

   # exportfs
    /nfs_server/srv
                  10.46.11.3/24
    /nfs_server       <world>

Procedure

1. Create a new configuration file in the /etc/multipath/conf.d directory.
2. Copy the individual setting you want to override from /etc/multipath.conf to the new configuration file in /etc/multipath/conf.d/<my_device>.conf. Remove any comment marks, edit the setting values, and save your changes.

3. Apply the new configuration settings by entering:

   # systemctl reload multipathd

   Note

   Do not restart the multipathd service. Doing so generates errors in the VDSM logs.

Verification steps

1. Test that the new configuration performs as expected on a non-production cluster in a variety of failure scenarios. For example, disable all of the storage connections.
2. Enable one connection at a time and verify that doing so makes the storage domain reachable.

Procedure

1. Go to the Get Started with Red Hat Virtualization on the Red Hat Customer Portal and log in.
2. Click Download Latest to access the product download page.
3. Choose the appropriate Hypervisor Image for RHV from the list and click Download Now.
4. Start the machine on which you are installing RHVH, booting from the prepared installation media.

5. From the boot menu, select Install RHVH 4.4 and press Enter.

   Note

   You can also press the Tab key to edit the kernel parameters. Kernel parameters must be separated by a space, and you can boot the system using the specified kernel parameters by pressing the Enter key. Press the Esc key to clear any changes to the kernel parameters and return to the boot menu.

6. Select a language, and click Continue.
7. Select a keyboard layout from the Keyboard Layout screen and click Done.

8. Select the device on which to install RHVH from the Installation Destination screen. Optionally, enable encryption. Click Done.

   Important

   Use the Automatically configure partitioning option.

9. Select a time zone from the Time & Date screen and click Done.

10. Select a network from the Network & Host Name screen and click Configure…​ to configure the connection details.

    Note

    To use the connection every time the system boots, select the Connect automatically with priority check box. For more information, see Configuring network and host name options in the Red Hat Enterprise Linux 8 Installation Guide.

    Enter a host name in the Host Name field, and click Done.

11. Optional: Configure Security Policy and Kdump. See Customizing your RHEL installation using the GUI in Performing a standard RHEL installation for Red Hat Enterprise Linux 8 for more information on each of the sections in the Installation Summary screen.
12. Click Begin Installation.

13. Set a root password and, optionally, create an additional user while RHVH installs.

    Warning

    Do not create untrusted users on RHVH, as this can lead to exploitation of local security vulnerabilities.

14. Click Reboot to complete the installation.

    Note

    When RHVH restarts, nodectl check performs a health check on the host and displays the result when you log in on the command line. The message node status: OK or node status: DEGRADED indicates the health status. Run nodectl check to get more information.

    Note

    If necessary, you can prevent kernel modules from loading automatically.

1. The installer installs the RHV-M Appliance to the deployment host.
2. The appliance installs the Manager virtual machine.
3. The appliance installs the Manager on the Manager virtual machine.

Procedure

1. On Red Hat Enterprise Linux hosts:

   1. Reset the virt module:

      # dnf module reset virt

      Note

      If this module is already enabled in the Advanced Virtualization stream, this step is not necessary, but it has no negative impact.

      You can see the value of the stream by entering:

      # dnf module list virt

   2. Enable the virt module in the Advanced Virtualization stream with the following command:

Procedure

1. Start firewalld:

   # systemctl unmask firewalld
   # systemctl start firewalld

   To ensure firewalld starts automatically at system start, enter the following command as root:

   # systemctl enable firewalld

2. Ensure that firewalld is running:

   # systemctl status firewalld

3. Ensure that your management interface is in a firewall zone via

   # firewall-cmd --get-active-zones

Procedure

1. Install the deployment tool:

   # dnf install ovirt-hosted-engine-setup

2. Use the tmux window manager to run the script to avoid losing the session in case of network or terminal disruption.

   Install and run tmux:

   # dnf -y install tmux
   # tmux

3. Start the deployment script:

   # hosted-engine --deploy

   Alternatively, to pause the deployment after adding the deployment host to the Manager, use the command line option --ansible-extra-vars=he_pause_host=true:

   # hosted-engine --deploy --ansible-extra-vars=he_pause_host=true

   Note

   To escape the script at any time, use the Ctrl+D keyboard combination to abort deployment. In the event of session timeout or connection disruption, run tmux attach to recover the deployment session.

4. When prompted, enter Yes to begin the deployment:

   Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine.
   The locally running engine will be used to configure a new storage domain and create a VM there.
   At the end the disk of the local VM will be moved to the shared storage.
   Are you sure you want to continue? (Yes, No)[Yes]:

5. Configure the network. Check that the gateway shown is correct and press Enter. Enter a pingable address on the same subnet so the script can check the host’s connectivity.

   Please indicate a pingable gateway IP address [X.X.X.X]:

6. The script detects possible NICs to use as a management bridge for the environment. Enter one of them or press Enter to accept the default.

   Please indicate a nic to set ovirtmgmt bridge on: (ens1, ens0) [ens1]:

7. Specify how to check network connectivity. The default is dns.

   Please specify which way the network connectivity should be checked (ping, dns, tcp, none) [dns]:

   ping

   Attempts to ping the gateway.

   dns

   Checks the connection to the DNS server.

   tcp

   Creates a TCP connection to a host and port combination. You need to specify a destination IP address and port. Once the connection is successfully created, the network is considered to be alive. Ensure that the given host is able to accept incoming TCP connections on the given port.

   none

   The network is always considered connected.

8. Enter a name for the data center in which to deploy the host for the self-hosted engine. The default name is Default.

   Please enter the name of the data center where you want to deploy this hosted-engine host.
   Data center [Default]:

9. Enter a name for the cluster in which to deploy the host for the self-hosted engine. The default name is Default.

   Please enter the name of the cluster where you want to deploy this hosted-engine host.
   Cluster [Default]:

10. If you want to use a custom appliance for the virtual machine installation, enter the path to the OVA archive. Otherwise, leave this field empty to use the RHV-M Appliance.

11. To deploy with a custom RHV-M Appliance appliance image, specify the path to the OVA archive. Otherwise, leave this field empty to use the RHV-M Appliance.

    If you want to deploy with a custom engine appliance image, please specify the path to the OVA archive you would like to use.
     Entering no value will use the image from the rhvm-appliance rpm, installing it if needed.
     Appliance image path []:

12. Enter the CPU and memory configuration for the Manager virtual machine:

    Please specify the number of virtual CPUs for the VM. The default is the appliance OVF value [4]:
    Please specify the memory size of the VM in MB. The default is the maximum available [6824]:

13. Specify the FQDN for the Manager virtual machine, such as manager.example.com:

    Please provide the FQDN you would like to use for the engine.
    Note: This will be the FQDN of the engine VM you are now going to launch,
    it should not point to the base host or to any other existing machine.
    Engine VM FQDN []:

14. Specify the domain of the Manager virtual machine. For example, if the FQDN is manager.example.com, then enter example.com.

    Please provide the domain name you would like to use for the engine appliance.
    Engine VM domain: [example.com]

15. Create the root password for the Manager, and reenter it to confirm:

    Enter root password that will be used for the engine appliance:
    Confirm appliance root password:

16. Optional: Enter an SSH public key to enable you to log in to the Manager virtual machine as the root user without entering a password, and specify whether to enable SSH access for the root user:

    You may provide an SSH public key, that will be added by the deployment script to the authorized_keys file of the root user in the engine appliance.
    This should allow you passwordless login to the engine machine after deployment.
    If you provide no key, authorized_keys will not be touched.
    SSH public key []:
    
    Do you want to enable ssh access for the root user (yes, no, without-password) [yes]:

17. Optional: You can apply the DISA STIG security profile on the Manager virtual machine. The DISA STIG profile is the default OpenSCAP profile.

    Do you want to apply a default OpenSCAP security profile? (Yes, No) [No]:

18. Enter a MAC address for the Manager virtual machine, or accept a randomly generated one. If you want to provide the Manager virtual machine with an IP address via DHCP, ensure that you have a valid DHCP reservation for this MAC address. The deployment script will not configure the DHCP server for you.

    You may specify a unicast MAC address for the VM or accept a randomly generated default [00:16:3e:3d:34:47]:

19. Enter the Manager virtual machine’s networking details:

    How should the engine VM network be configured (DHCP, Static)[DHCP]?

    If you specified Static, enter the IP address of the Manager virtual machine:

    Important

    • The static IP address must belong to the same subnet as the host. For example, if the host is in 10.1.1.0/24, the Manager virtual machine’s IP must be in the same subnet range (10.1.1.1-254/24).
    • For IPv6, Red Hat Virtualization supports only static addressing.

    Please enter the IP address to be used for the engine VM [x.x.x.x]:
    Please provide a comma-separated list (max 3) of IP addresses of domain name servers for the engine VM
    Engine VM DNS (leave it empty to skip):

20. Specify whether to add entries for the Manager virtual machine and the base host to the virtual machine’s /etc/hosts file. You must ensure that the host names are resolvable.

    Add lines for the appliance itself and for this host to /etc/hosts on the engine VM?
    Note: ensuring that this host could resolve the engine VM hostname is still up to you.
    Add lines to /etc/hosts? (Yes, No)[Yes]:

21. Provide the name and TCP port number of the SMTP server, the email address used to send email notifications, and a comma-separated list of email addresses to receive these notifications. Alternatively, press Enter to accept the defaults:

    Please provide the name of the SMTP server through which we will send notifications [localhost]:
    Please provide the TCP port number of the SMTP server [25]:
    Please provide the email address from which notifications will be sent [root@localhost]:
    Please provide a comma-separated list of email addresses which will get notifications [root@localhost]:

22. Create a password for the admin@internal user to access the Administration Portal and reenter it to confirm:

    Enter engine admin password:
    Confirm engine admin password:

23. Specify the hostname of the deployment host:

    Please provide the hostname of this host on the management network [hostname.example.com]:

    The script creates the virtual machine. By default, the script first downloads and installs the RHV-M Appliance, which increases the installation time.

24. Optional: If you set the variable he_pause_host: true, the deployment pauses after adding the deployment host to the Manager. You can now log in from the deployment host to the Manager virtual machine to customize it. You can log in with either the FQDN or the IP address of the Manager. For example, if the FQDN of the Manager is manager.example.com:

    $ ssh root@manager.example.com

    Tip

    In the installation log, the IP address is in local_vm_ip. The installation log is the most recent instance of /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-bootstrap_local_vm*.

    1. Customize the Manager virtual machine as needed.
    2. When you are done, log in to the Administration Portal using a browser with the Manager FQDN and make sure that the host’s state is Up.
    3. Delete the lock file and the deployment script automatically continues, configuring the Manager virtual machine.

25. Select the type of storage to use:

    Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]:

    • For NFS, enter the version, full address and path to the storage, and any mount options:

      Please specify the nfs version you would like to use (auto, v3, v4, v4_1)[auto]:
      Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/nfs
      If needed, specify additional mount options for the connection to the hosted-engine storage domain []:

    • For iSCSI, enter the portal details and select a target and LUN from the auto-detected lists. You can only select one iSCSI target during the deployment, but multipathing is supported to connect all portals of the same portal group.

      Note

      To specify more than one iSCSI target, you must enable multipathing before deploying the self-hosted engine. See Red Hat Enterprise Linux DM Multipath for details. There is also a Multipath Helper tool that generates a script to install and configure multipath with different options.

      Please specify the iSCSI portal IP address:
      Please specify the iSCSI portal port [3260]:
      Please specify the iSCSI discover user:
      Please specify the iSCSI discover password:
      Please specify the iSCSI portal login user:
      Please specify the iSCSI portal login password:
      
      The following targets have been found:
      	[1]	iqn.2017-10.com.redhat.example:he
      		TPGT: 1, portals:
      			192.168.1.xxx:3260
      			192.168.2.xxx:3260
      			192.168.3.xxx:3260
      
      Please select a target (1) [1]: 1
      
      The following luns have been found on the requested target:
        [1] 360003ff44dc75adcb5046390a16b4beb   199GiB  MSFT   Virtual HD
            status: free, paths: 1 active
      
      Please select the destination LUN (1) [1]:

    • For Gluster storage, enter the full address and path to the storage, and any mount options:

      Important

      Only replica 1 and replica 3 Gluster storage are supported. Ensure you configure the volume as follows:

      gluster volume set VOLUME_NAME group virt
      gluster volume set VOLUME_NAME performance.strict-o-direct on
      gluster volume set VOLUME_NAME network.remote-dio off
      gluster volume set VOLUME_NAME storage.owner-uid 36
      gluster volume set VOLUME_NAME storage.owner-gid 36
      gluster volume set VOLUME_NAME network.ping-timeout 30

      Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/gluster_volume
      If needed, specify additional mount options for the connection to the hosted-engine storage domain []:

    • For Fibre Channel, select a LUN from the auto-detected list. The host bus adapters must be configured and connected, and the LUN must not contain any existing data. To reuse an existing LUN, see Reusing LUNs in the Administration Guide.

      The following luns have been found on the requested target:
      [1] 3514f0c5447600351   30GiB   XtremIO XtremApp
      		status: used, paths: 2 active
      
      [2] 3514f0c5447600352   30GiB   XtremIO XtremApp
      		status: used, paths: 2 active
      
      Please select the destination LUN (1, 2) [1]:

26. Enter the disk size of the Manager virtual machine:

    Please specify the size of the VM disk in GB: [50]:

    When the deployment completes successfully, one data center, cluster, host, storage domain, and the Manager virtual machine are already running. You can log in to the Administration Portal to add any other resources.

27. Optional: Install and configure Red Hat Single Sign On so that you can add additional users to the environment. For more information, see Installing and Configuring Red Hat Single Sign-On in the Administration Guide.
28. Optional: Deploy Grafana so you can monitor and display reports from your RHV environment. For more information, see Configuring Grafana in the Administration Guide.

Procedure

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

   Note

   If you are using an IPv6 network, use an IPv6 transition mechanism to access the Content Delivery Network and subscription manager.

2. Find the Red Hat Virtualization Manager subscription pool and record the pool ID:

   # subscription-manager list --available

3. Use the pool ID to attach the subscription to the system:

   # subscription-manager attach --pool=pool_id

   Note

   To view currently attached subscriptions:

   # subscription-manager list --consumed

   To list all enabled repositories:

   # dnf repolist

4. Configure the repositories:

   # subscription-manager repos \
       --disable='*' \
       --enable=rhel-8-for-x86_64-baseos-eus-rpms \
       --enable=rhel-8-for-x86_64-appstream-eus-rpms \
       --enable=rhv-4.4-manager-for-rhel-8-x86_64-rpms \
       --enable=fast-datapath-for-rhel-8-x86_64-rpms \
       --enable=jb-eap-7.4-for-rhel-8-x86_64-rpms \
       --enable=openstack-16.2-cinderlib-for-rhel-8-x86_64-rpms \
       --enable=rhceph-4-tools-for-rhel-8-x86_64-rpms \
       --enable=rhel-8-for-x86_64-appstream-tus-rpms \
       --enable=rhel-8-for-x86_64-baseos-tus-rpms

5. Set the RHEL version to 8.6:

   # subscription-manager release --set=8.6

6. Enable the pki-deps module.

   # dnf module -y enable pki-deps

7. Enable version 12 of the postgresql module.

   # dnf module -y enable postgresql:12

8. Enable version 14 of the nodejs module:

   # dnf module -y enable nodejs:14

9. Update the Self-Hosted Engine using the procedure Updating a Self-Hosted Engine in the Upgrade Guide.

1. In a web browser, navigate to https://manager-fqdn/ovirt-engine, replacing manager-fqdn with the FQDN that you provided during installation.

   Note

   You can access the Administration Portal using alternate host names or IP addresses. To do so, you need to add a configuration file under /etc/ovirt-engine/engine.conf.d/. For example:

   # vi /etc/ovirt-engine/engine.conf.d/99-custom-sso-setup.conf
   SSO_ALTERNATE_ENGINE_FQDNS="alias1.example.com alias2.example.com"

   The list of alternate host names needs to be separated by spaces. You can also add the IP address of the Manager to the list, but using IP addresses instead of DNS-resolvable host names is not recommended.

2. Click Administration Portal. An SSO login page displays. SSO login enables you to log in to the Administration and VM Portal at the same time.
3. Enter your User Name and Password. If you are logging in for the first time, use the user name admin along with the password that you specified during installation.
4. Select the Domain to authenticate against. If you are logging in using the internal admin user name, select the internal domain.
5. Click Log In.
6. You can view the Administration Portal in multiple languages. The default selection is chosen based on the locale settings of your web browser. If you want to view the Administration Portal in a language other than the default, select your preferred language from the drop-down list on the welcome page.

Procedure

1. In the Administration Portal, click Compute → Hosts.

2. Click New.

   For information on additional host settings, see Explanation of Settings and Controls in the New Host and Edit Host Windows in the Administration Guide.

3. Use the drop-down list to select the Data Center and Host Cluster for the new host.
4. Enter the Name and the Address of the new host. The standard SSH port, port 22, is auto-filled in the SSH Port field.

5. Select an authentication method to use for the Manager to access the host.

   • Enter the root user’s password to use password authentication.
   • Alternatively, copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_keys on the host to use public key authentication.
6. Optionally, configure power management, where the host has a supported power management card. For information on power management configuration, see Host Power Management Settings Explained in the Administration Guide.
7. Click the Hosted Engine tab.
8. Select Deploy.
9. Click OK.

Procedure

1. From the Administration Portal, click Compute → Hosts.
2. Click New.
3. Use the drop-down list to select the Data Center and Host Cluster for the new host.
4. Enter the Name and the Address of the new host. The standard SSH port, port 22, is auto-filled in the SSH Port field.

5. Select an authentication method to use for the Manager to access the host.

   • Enter the root user’s password to use password authentication.
   • Alternatively, copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_keys on the host to use public key authentication.

6. Optionally, click the Advanced Parameters button to change the following advanced host settings:

   • Disable automatic firewall configuration.
   • Add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
7. Optionally configure power management, where the host has a supported power management card. For information on power management configuration, see Host Power Management Settings Explained in the Administration Guide.
8. Click OK.

Procedure

1. In the Administration Portal, click Storage → Domains.
2. Click New Domain.
3. Enter a Name for the storage domain.
4. Accept the default values for the Data Center, Domain Function, Storage Type, Format, and Host lists.
5. Enter the Export Path to be used for the storage domain. The export path should be in the format of 123.123.0.10:/data (for IPv4), [2001:0:0:0:0:0:0:5db1]:/data (for IPv6), or domain.example.com:/data.

6. Optionally, you can configure the advanced parameters:

   1. Click Advanced Parameters.
   2. Enter a percentage value into the Warning Low Space Indicator field. If the free space available on the storage domain is below this percentage, warning messages are displayed to the user and logged.
   3. Enter a GB value into the Critical Space Action Blocker field. If the free space available on the storage domain is below this value, error messages are displayed to the user and logged, and any new action that consumes space, even temporarily, will be blocked.
   4. Select the Wipe After Delete check box to enable the wipe after delete option. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist.
7. Click OK.

Procedure

1. Click Storage → Domains.
2. Click New Domain.
3. Enter the Name of the new storage domain.
4. Select a Data Center from the drop-down list.
5. Select Data as the Domain Function and iSCSI as the Storage Type.

6. Select an active host as the Host.

   Important

   Communication to the storage domain is from the selected host and not directly from the Manager. Therefore, all hosts must have access to the storage device before the storage domain can be configured.

7. The Manager can map iSCSI targets to LUNs or LUNs to iSCSI targets. The New Domain window automatically displays known targets with unused LUNs when the iSCSI storage type is selected. If the target that you are using to add storage does not appear, you can use target discovery to find it; otherwise proceed to the next step.

   1. Click Discover Targets to enable target discovery options. When targets have been discovered and logged in to, the New Domain window automatically displays targets with LUNs unused by the environment.

      Note

      LUNs used externally for the environment are also displayed.

      You can use the Discover Targets options to add LUNs on many targets or multiple paths to the same LUNs.

      Important

      If you use the REST API method discoveriscsi to discover the iscsi targets, you can use an FQDN or an IP address, but you must use the iscsi details from the discovered targets results to log in using the REST API method iscsilogin. See discoveriscsi in the REST API Guide for more information.

   2. Enter the FQDN or IP address of the iSCSI host in the Address field.
   3. Enter the port with which to connect to the host when browsing for targets in the Port field. The default is 3260.

   4. If CHAP is used to secure the storage, select the User Authentication check box. Enter the CHAP user name and CHAP password.

      Note

      You can define credentials for an iSCSI target for a specific host with the REST API. See StorageServerConnectionExtensions: add in the REST API Guide for more information.

   5. Click Discover.

   6. Select one or more targets from the discovery results and click Login for one target or Login All for multiple targets.

      Important

      If more than one path access is required, you must discover and log in to the target through all the required paths. Modifying a storage domain to add additional paths is currently not supported.

      Important

      When using the REST API iscsilogin method to log in, you must use the iscsi details from the discovered targets results in the discoveriscsi method. See iscsilogin in the REST API Guide for more information.

8. Click the + button next to the desired target. This expands the entry and displays all unused LUNs attached to the target.
9. Select the check box for each LUN that you are using to create the storage domain.

10. Optionally, you can configure the advanced parameters:

    1. Click Advanced Parameters.
    2. Enter a percentage value into the Warning Low Space Indicator field. If the free space available on the storage domain is below this percentage, warning messages are displayed to the user and logged.
    3. Enter a GB value into the Critical Space Action Blocker field. If the free space available on the storage domain is below this value, error messages are displayed to the user and logged, and any new action that consumes space, even temporarily, will be blocked.
    4. Select the Wipe After Delete check box to enable the wipe after delete option. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist.
    5. Select the Discard After Delete check box to enable the discard after delete option. This option can be edited after the domain is created. This option is only available to block storage domains.
11. Click OK.

Procedure

1. Click Storage → Domains.
2. Click New Domain.
3. Enter the Name of the storage domain.

4. Select an FCP Data Center from the drop-down list.

   If you do not yet have an appropriate FCP data center, select (none).

5. Select the Domain Function and the Storage Type from the drop-down lists. The storage domain types that are not compatible with the chosen data center are not available.

6. Select an active host in the Host field. If this is not the first data domain in a data center, you must select the data center’s SPM host.

   Important

   All communication to the storage domain is through the selected host and not directly from the Red Hat Virtualization Manager. At least one active host must exist in the system and be attached to the chosen data center. All hosts must have access to the storage device before the storage domain can be configured.

7. The New Domain window automatically displays known targets with unused LUNs when Fibre Channel is selected as the storage type. Select the LUN ID check box to select all of the available LUNs.

8. Optionally, you can configure the advanced parameters.

   1. Click Advanced Parameters.
   2. Enter a percentage value into the Warning Low Space Indicator field. If the free space available on the storage domain is below this percentage, warning messages are displayed to the user and logged.
   3. Enter a GB value into the Critical Space Action Blocker field. If the free space available on the storage domain is below this value, error messages are displayed to the user and logged, and any new action that consumes space, even temporarily, will be blocked.
   4. Select the Wipe After Delete check box to enable the wipe after delete option. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist.
   5. Select the Discard After Delete check box to enable the discard after delete option. This option can be edited after the domain is created. This option is only available to block storage domains.
9. Click OK.