The following file is needed to install the DSC SWe on a KVM host. This installation file can be executed on the KVM host locally or on a Linux workstation that supports Python, libvirt, SCP, and SSH. 

The installation file contains the following:

  • VM Installation script
  • VM image (QCOW2)
Prerequisites

  • Download the dsc_swe_<release>_nb<date>_KVM.sh installation file for your release from the Ribbon Global Software Center. For example, dsc_swe_18_0_0_nb20190317_KVM.sh.

    The file version is specified in the Release Notes and instructions for downloading files from the Ribbon Global Software Center are here: Downloading Software from the Ribbon Support Portal. 

Start

  1. Prepare the KVM Host machines.

    Tip

    Consider the user (and authentication) required for virsh interaction and for file manipulation.

  2. Prepare the Linux workstation (or the host machine). The workstation needs to support Python, libvirt, SCP, and SSH. The workstation must be able to reach both/all host machines

  3. Transfer the dsc_swe_<release>_nb<date>_KVM.sh installation file to a Linux machine (KVM Host or workstation).

    Tip

    A Linux workstation (or a host machine) can execute the installer script and direct the install to one or more KVM Hosts through an SSH session. The workstation must have Python and the libvirt module.

  4. Go to the location where you stored the installation file and make sure that the installation file was correctly transferred by entering the following. 

    ./dsc_swe_<release>_nb<date>_KVM.sh -check
    Example
    ./dsc_swe_18_0_0_nb20190317_KVM.sh -check

    If you see Complete on the screen, this means that the check sum and md5sum are as they should be.

  5. Next Steps: Refer to Creating a New DSC SWe VM, to execute the dsc_swe_<release>_nb<date>_KVM.sh script to create the configuration file and install for all new VMs. The script deploys all VMs for the DSC SWe system across all KVM Hosts. The VMs will be in running state with the appropriate hostnames and IP addresses applied. To run on each host, a configuration file for each host is used.


  • No labels