Resource Checks

CloudVision Portal (CVP) enables you to run resource checks on CVP node VMs. You can run checks to determine the current data disk size of VMs that you have upgraded to CVP version 2017.2.0, and to determine the current memory allocation for each CVP node VM.

Performing these resource checks is important to ensure that the CVP node VMs in your deployment have the recommended data disk size and memory allocation for using the Telemetry feature. If the resource checks show that the CVP node VM data disk size or memory allocation (RAM) are below the recommended levels, you can increase the data disk size and memory allocation.

These procedures provide detailed instructions on how to perform the resource checks and if needed, how to increase the CVP node VM data disk size and CVP node VM memory allocation.

Running CVP node VM Resource Checks

CloudVision Portal (CVP) enables you to quickly and easily check the current resources of the primary, secondary, and tertiary nodes of a cluster by running a single command. The command you use is the cvpi resources command.

Use this command to check the following CVP node VM resources:

  • Memory allocation
  • Data disk size (storage capacity)
  • Disk throughput (in MB per second)
  • Number of CPUs

Complete the following steps to run the CVP node VM resource check.

  1. Login to one of the CVP nodes as root.
  2. Execute the cvpi resources command.

    The output shows the current resources for each CVP node VM

    Figure 1. Using the cvpi resource command to run CVP node VM resource checks

Increasing Disk Size of VMs Upgraded to CVP Version 2017.2.0

If you already upgraded any CVP node VMs running an older version of CVP to version 2017.2.0, you may need to increase the size of the data disk of the VMs so that the data disks have the 1TB disk image that is used on current CVP node VMs

CVP node VM data disks that you upgraded to version 2017.2.0 may still have the original disk image (120GB data image), because the standard upgrade procedure did not upgrade the data disk image. The standard upgrade procedure updated only the root disk, which contains the Centos image along with rpms for CVPI, CVP, and Telemetry.

Note: It is recommended that each CVP node have 1TB of disk space reserved for enabling CVP Telemetry. If the CVP nodes in your current environment do not have the recommended reserved disk space of 1TB, complete the procedure below for increasing the disk size of CVP node VMs.

Pre-requisites

Before you begin the procedure, make sure that you:

  • Have upgraded to version 2017.2.0. You cannot increase the data disk size until you have completed the upgrade to version 2017.2.0 (see Migrating the DNS and NTP Server).
  • Have performed the resource check to verify that the CVP node VMs have the data disk size image of previous CVP versions (approximately 120GB or less). See Running CVP node VM Resource Checks.

Procedure

Complete the following steps to increase the data disk size.

  1. Turn off cvpi service by executing the systemctl stop cvpi command on all nodes in the cluster. (For a single-node installation, run this command on the node.)
  2. Run the cvpi -v=3 stop all on the primary node.
  3. Perform a graceful power-off of all VMs.
    Note: You do not need to unregister and re-register VMs from vSphere Client or undefine and redefine VMs from kvm hypervisor.
  4. Do the following to increase the size of the data disk to 1TB using the hypervisor:
    • ESX: Using vSphere client, do the following:
      1. Select the Virtual Hardware tab, and then select hard disk 2.
      2. Change the setting from 120GB to 1TB.
      3. Click OK.
    • KVM: Use the qemu-img resize command to resize the data disk from 120GB to 1TB. Be sure to select disk2.qcow2.
    Figure 2. Using vSphere to increase data disk size
  5. Power on all CVP node VMs, and wait for all services to start.
  6. Use the cvpi status all command to verify that all the cvpi services are running.
  7. Run the /cvpi/tools/diskResize.py command on the primary node. (Do not run this command on the secondary and tertiary nodes.)
  8. Run the df -h /data command on all nodes to verify that the /data is increased to approximately 1TB.
  9. Wait for all services to start.
  10. Use the cvpi -v=3 status all command to verify the status of services.
  11. Use the systemctl status cvpi to ensure that cvpi service is running.

Increasing CVP Node VM Memory Allocation

If the CVP Open Virtual Appliance (OVA) template currently specifies the default of 16GB of memory allocated for the CVP node VMs in the CVP cluster, you need to increase the RAM to ensure that the CVP node VMs have adequate memory allocated for using the Telemetry feature.

Note: It is recommended that CVP node VMs have 32GB of RAM allocated for deployments in which Telemetry is enabled.

You can perform a rolling modification to increase the RAM allocation of every node in the cluster. If you want to keep the service up and available while you are performing the rolling modification, make sure that you perform the procedure on only one CVP node VM at a time.

Once you have completed the procedure on a node, you repeat the procedure on another node in the cluster. You must complete the procedure once for every node in the cluster.

Pre-requisites

Before you begin the procedure, make sure that you:

  • Have performed the resource check to verify that the CVP node VMs have the default RAM memory allocation of 16GB (see Running CVP node VM Resource Checks).
  • Make sure that you perform a GUI-based backup of the CVP system and copy the backup to a safe location (a location off of the CVP node VMs). The CVP GUI enables you to create a backup you can use to restore CVP data.

Procedure

Complete the following steps to increase the RAM memory allocation of the CVP node VMs.

  1. Login to a CVP node of the cluster as cvp user.
  2. Using the cvpi status cvp shell command, make sure that all nodes in the cluster are operational.
    Figure 3. cvpi status cvp shell command
  3. Using vSphere client, shutdown one CVP node VM by selecting the node in the left pane, and then click the Power off the virtual machine option.
    Figure 4. Power off the virtual machine
  4. Click to confirm powering off the virtual machine.
    Figure 5. Powering off confirmation
  5. On the CVP node VM, increase the memory allocation to 32GB by right-clicking the node icon, and then choose Edit Settings.
    Figure 6. Edit Settings

    The Edit Resource Settings dialog appears.

    Figure 7. Edit Resources Settings
  6. Do the following to increase the memory allocation for the CVP node VM:
    • Using the Memory option, click the up arrow to increase the size to 32GB.
    • Click the OK button.

    The memory allocation for the CVP node VM is changed to 32GB. The page refreshes, showing options to power on the VM or continue making edits to the VM properties.

  7. Click the Power on the virtual machine option.
    Figure 8. Power on the virtual machine
  8. Wait for the cluster to reform.
  9. Once the cluster is reformed, repeat step 1 through step 7 one node at a time on each of the remaining CVP node VMs in the cluster.