Deploying Avaya Aura® Device Services on ASP using KVM Cockpit

Last Updated : Dec 13, 2024 |
Prolog information
Metadata
Keywords:
Before you begin
  • Install ASP R6.0.x (KVM on RHEL 8.10) or ASP R7.0.x (KVM on RHEL 9.6).
    For more information, see Installing the Avaya Solutions Platform 130 Series at https://support.avaya.com/css/public/documents/101091802.
  • Download the Avaya Aura® Device Services KVM image aads-kvm-*.ova from PLDS to your computer.
  • Login to the ASP CLI with custadm credentials.
  • Ensure that the staging folder exists: /var/lib/libvirt/staging.
    sudo ls -ld /var/lib/libvirt/images
    Ensure to remove the older images from the staging folder.
    Ensure sufficient space is available in the staging folder to copy the KVM image.
    If the staging folder does not exist, create it using the following commands:
    sudo mkdir /var/lib/libvirt/staging
    sudo chown custadm:wheel /var/lib/libvirt/staging
  • Copy the Avaya Aura® Device Services KVM image aads-kvm-*.ova to the ASP host in /var/lib/libvirt/staging using the winscp tool and custadm credentials.
  • If not still in the CLI, login again to the ASP CLI with custadm credentials.
Note:
All the following commands must be prefaced with “sudo”:
  • Run the following command to verify the Avaya Aura® Device Services KVM image available in the staging folder: sudo ls -lr /var/lib/libvirt/staging
  • Go to /var/lib/libvirt/staging folder, and run the following command to extract the ova file: sudo tar -xvf aads-kvm-*.ova
    KVM OVA file extracts the following files:
    • aads-*.mf
    • aads-*.ova
    • aads-*.ovf
    • aads-*.cert
    • disk1.qcow2
    • disk2.qcow2
    • disk3.qcow2
    • disk4.qcow2
The extracted qcow2 images are in thin provision format. The qcow2 images MUST be converted to thick provision. Ensure you are in the /var/lib/libvirt/staging directory before proceeding. When running the commands to convert to thick provision, a unique identifier can be added to the new qcow2 image. Avaya recommends to use VM name as a unique identifier. Convert disk1.qcow2(thin) to AADS10.3[unique identifier]-disk1.qcow2 (thick). For example:
  • sudo qemu-img convert -O qcow2 -o preallocation=full disk1.qcow2 AADS10.3[unique identifier]-disk1.qcow2
  • sudo qemu-img convert -O qcow2 -o preallocation=full disk2.qcow2 AADS10.3[unique identifier]-disk2.qcow2
  • sudo qemu-img convert -O qcow2 -o preallocation=full disk3.qcow2 AADS10.3[unique identifier]-disk3.qcow2
  • sudo qemu-img convert -O qcow2 -o preallocation=full disk4.qcow2 AADS10.3[unique identifier]-disk4.qcow2
To verify that the conversion is successful and verify the disk size, run the following commands:
  • sudo qemu-img info disk1.qcow2
    Disk size must display as 2.4GB
  • sudo qemu-img info AADS10.3[unique identifier]-disk1.qcow2
    Disk size must display as 125GB
Copy the AADS10.3[unique identifier]-disk1.qcow2, AADS10.3[unique identifier]-disk2.qcow2, AADS10.3[unique identifier]-disk3.qcow2 and AADS10.3[unique identifier]-disk4.qcow2 qcow2 to the /var/lib/libvirt/images directory. Ensure you are in the /var/lib/libvirt/staging directory before performing these steps.
  • sudo cp /var/lib/libvirt/staging/ AADS10.3[unique identifier]-disk*.qcow2 /var/lib/libvirt/images/
  • cd /var/lib/libvirt/images/
  • sudo ls -lr
From the /var/lib/libvirt/images directory, run the following command to change the owner and permissions to 640 on the files:
  • sudo chown qemu:qemu AADS10.3[unique identifier]-disk*
    chmod 640 AADS10.3[unique identifier]-disk*
Go to /var/lib/libvirt/staging directory and remove all the extracted images and converted images. This is important to ensure that there is sufficient space for future deployments of KVM images. Do NOT remove files from the “images” directory.
  • cd /var/lib/libvirt/staging
    sudo ls -lr
    sudo rm *AADS*
Ensure that the network bridge is configured during the KVM deployment.
  1. Log in to the KVM Cockpit web console as custadm in the following format: https://<IP address or FQDN of KVM host>:9090.
  2. For administration actions, on the top-right of the window, click on the Limited access button.
    ADDITIONAL INFORMATION:
    Figure: Limited access button
    Note:
    You require administrator access in order to view virtual machines. Administrator access is like root access. Ensure that you take care making updates.
  3. In the Switch to administrative access window, enter the password for custadm.
    ADDITIONAL INFORMATION:
    Figure: Switch to administrative access
    The Limited access button on the top-right of the window changes to Administrative access.
    Figure: Administrative access button
  4. Navigate to SystemVirtual MachinesImport VM.
  5. In the Import a virtual machine window, do the following:
    1. In the Name field, enter a name for the Avaya Aura® Device Services virtual machine.
    2. In the Disk Image field, select the AADS10.3[unique identifier]-disk1.qcow2 image of the Avaya Aura® Device Services on the KVM Cockpit host under /var/lib/libvirt/images/ directory.
    3. In the Operating System field, select RHEL 9.6 version.
    4. In the Memory field, select the required memory in MiB format.
      ADDITIONAL INFORMATION:
      Note:
      Based on the required footprint, enter a value in the Memory field.
      For more information on footprints, see Avaya Aura Device Services virtual machine resource requirements
    5. Click Import and edit.
      ADDITIONAL INFORMATION:
      Virtual Machine details page appears.
      Under the Disks section, verify the AADS10.3[unique identifier]-disk1.qcow2 image disk image size is correctly displayed in the Capacity field. By default, virtio is selected under the Bus field, and this needs to be modified.
  6. Under the Disks section, click Edit.
  7. In the Edit <attributes name> window, do the following:
    1. in the Bus field, select scsi.
    2. In the Cache field, select directsync.
    3. click Save.
      ADDITIONAL INFORMATION:
      In the Disks section, ensure that scsi appears under the Bus field and directsync appears under the Additional Cache field.
  8. Click Add disk to add AADS10.3[unique identifier]-disk2.qcow2 , AADS10.3[unique identifier]-disk3.qcow2, AADS10.3[unique identifier]-disk4.qcow2 disk image, and do the following:
    1. In the Source field, select Custom path.
    2. In the Custom path field, select AADS10.3[unique identifier]-disk1.qcow2 image on the KVM host location path /var/lib/libvirt/images
    3. In the Device field, select Disk image file.
    4. Expand the Show additional options field.
    5. In the Cache field, select directsync.
    6. In the Bus field, select SCSI bus type.
    7. Click Add.
    ADDITIONAL INFORMATION:
    In the Disks section, verify that the four disk images are assigned correctly. The newly added disk must have the 125 GiB AADS10.3[unique identifier]-disk1.qcow2, 70 GiB for AADS10.3[unique identifier]-disk2.qcow2, 40 GiB for AADS10.3[unique identifier]-disk3.qcow2 and 10 GiB for AADS10.3[unique identifier]-disk4.qcow2 assigned under the Capacity and field, scsi assigned under the Bus field, and directsync under the Cache field.
  9. In the Overview section, in the Firmware field, select UEFI and click Save.
  10. In the Overview section, in the CPU field, click edit.
    ADDITIONAL INFORMATION:
    CPU Details window opens.
  11. In the CPU details window, based on the required footprint, enter a value in the vCPU Maximum and vCPU Count fields.
    ADDITIONAL INFORMATION:
    For more information on footprints, see Avaya Aura Device Services virtual machine resource requirements.
  12. Click Apply.
  13. In the Network interfaces section, click Edit and select the Network Bridge, and click Save.
  14. On the virtual machine, click Run to start the Avaya Aura® Device Services virtual machine.
Next steps
On first boot of the Avaya Aura® Device Services configure the AADS virtual machine, network properties and follow the Avaya Aura® Device Services deployment guide.
Existing instructions for installation of these artifacts using the CLI and UI are applicable. Note that the “snapshot” functionality present in ASP R5.1.x and earlier is replaced with an equivalent feature, titled Virtual Machine Backup (clone).
For more information about the Virtual Machine Backup (clone), see Appendix of the Avaya Aura® Device Services deployment guide.