SevOne Data Platform Deployment on IBM Cloud

This document describes how to deploy SevOne NMS on IBM Cloud.

touch /etc/cloud/cloud-init.disabled

To deploy IBM SevOne NPM component, NMS, on IBM Cloud, the following steps are required.

• Obtain the required IBM SevOne NPM KVM/Openstack .qcow2 image for component, SevOne NMS, from IBM Passport Advantage (https://www.ibm.com/software/passportadvantage/pao_download_software.html) via Passport Advantage Online.
• Upload the .qcow2 image files to a bucket in IBM Cloud Object Storage.
• Create a custom image with the following properties; specify the cos:// path to the uploaded .qcow2 image file.
  • Name - sevone-nms-8-0-0
  • Image source - Cloud Object Storage
  • Locate image file by url - cos://<location>/<bucket-name>/<object-name>
  • Operating system - Red Hat Enterprise Linux (RHEL)
  • Version - rhel-9-amd64-byol
• Create an instance from the image.
  • Name - specify a valid name for your instance.
  • Image - select the custom image created in the step above.
  • Profile - select the profile from the table.
  • Ssh Key - specify or create an SSH key.
  • Boot Volume - specify the size from the table.
  • Data Volume - specify the size from the table.
• Log on to the instance created and perform the following.
  • Using a text editor of your choice, create /opt/ibmcloud_setup.sh file, if it does not exist.

    
    touch /opt/ibmcloud_setup.sh
    

  • Edit /opt/ibmcloud_setup.sh file.

    
    vi /opt/ibmcloud_setup.sh
    

  • Add the following script to configure the data disk and run the script manually with bash.
    Important: If an empty data disk is attached to a virtual machine on first boot, it will be automatically formatted, mounted, and configured. However, if the user has already booted and now wants to attach a /data disk, run the script below.
    Example: ibmcloud_setup.sh

    
    # This script is only valid during initial deployment, and should not be used 
    # to migrate data on an existing environment with a significant amount of 
    # collected historical data
    set -e
    
    MIN_SIZE=$((150 * 1024 * 1024 * 1024))
    DATA_SIZE=$(df -B1 /data 2>/dev/null | awk 'NR==2 {print $3}')
    if [[ "$DATA_SIZE" =~ ^[0-9]+$ ]] && (( DATA_SIZE > MIN_SIZE )); then
    	MIN_SIZE=$DATA_SIZE
    fi
    DISK_NAME=$(lsblk -o NAME,FSTYPE,SIZE -Jb | jq -r --argjson minSize "$MIN_SIZE" '[.blockdevices[] | select((.children|length==0) and (.size|tonumber >= $minSize) and (.fstype|not))] | max_by(.size|tonumber) | select(.) | .name')
    
    if [ -z "$DISK_NAME" ]; then
    	echo "No appropriate blank disks found" >&2
    	exit 1
    fi
    
    systemctl stop nms
    mkdir -p /data_temp /data
    mv /data/* /data_temp
    
    mkfs.xfs /dev/$DISK_NAME
    cat > /etc/systemd/system/data.mount <<__DATA_MOUNT__
    [Unit]
    Description=Mount unit for /data
    Before=nms_deployment.service prometheus_deployment.service collectors_deployment.service
    
    [Mount]
    What=/dev/$DISK_NAME
    Where=/data
    Type=xfs
    DirectoryMode=0755
    
    [Install]
    WantedBy=multi-user.target
    __DATA_MOUNT__
    
    systemctl daemon-reload
    systemctl enable data.mount
    systemctl restart data.mount
    mv /data_temp/* /data
    systemctl start nms
    rmdir /data_temp
    

  • Perform the steps in SevOne NMS Appliance Configuration Guide to configure the appliance size.

    Appliance Size	Profile	Boot Volume (GB)	/ Data Disk (GB)
    PAS5k	bx3d-2x10	150	600
    PAS20k	bx3d-4x20	150	600
    PAS60k	bx3d-8x40	150	1250
    PAS100k	bx3d-8x40	150	2000
    PAS200k	bx3d-32x160	150	4000
    DNC100	bx3d-8x40	150	400
    DNC300	bx3d-16x80	150	800
    DNC1000	bx3d-32x160	150	1500
    DNC1500	bx3d-32x160	150	3000