SevOne Data Platform Deployment on OpenShift

Edit online

Red Hat OpenShift Virtualization is a feature (via the virtualization operator) of Red Hat OpenShift Container Platform (OCP) that enables you to run and manage virtual machines (VMs) alongside containerized applications on a single, enterprise-grade Kubernetes platform. It allows you to modernize infrastructure by bringing traditional VM workloads into the same environment as cloud-native services. This approach simplifies operations, enhances scalability across hybrid and multicloud environments, and provides a consistent set of tools for deploying, monitoring, and securing all workloads - whether virtualized or containerized.

Note: Networking Considerations for running SevOne NMS on Red Hat's OCP

Running the Network Management System (NMS) as a virtual machine on OpenShift Container Platform requires Layer 2 (L2) networking to enable features such as clustering and NetFlow, which depend on direct, routable IP access to the VMs within OCP.

Unlike standard OCP pods that use internal overlay networks, NMS VMs must be able to obtain external IP addresses—either through DHCP or static assignment—to support these functions. This ensures that network communication flows properly between NMS components and external systems.

Testing for this deployment was performed on OCP version 4.20.

OpenShift Installation

Edit online

Execute the steps below.

Download the the latest QCOW2 file from IBM Passport Advantage (https://www.ibm.com/software/passportadvantage/pao_download_software.html) via Passport Advantage Online. However, if you are on a legacy / flexible SevOne contract and do not have access to IBM Passport Advantage but have an active Support contract, please contact SevOne Support Team for the file.
Using a web browser of your choice, enter the URL to log in to your RedHat OpenShift console.
Select Administrator from the perspective switcher.
Create custom instance types for SevOne products.
- From the left navigation bar, as an Administrator, under Virtualization, select InstanceTypes.
- Select tab User InstanceTypes.
- Select Create to create an instance type. You will get a default template.
```
apiVersion: instancetype.kubevirt.io/v1beta1
kind: VirtualMachineInstancetype
metadata:
  name: example
  namespace: default
spec:
  cpu:
    guest: 1
  memory:
    guest: 2Gi
          
```
  If you are creating a PAS20k, update the .yaml file. Please refer to Hardware Requirements for Virtual Appliances for details on the hardware component you are creating and update the template above. For example,
```
apiVersion: instancetype.kubevirt.io/v1beta1
kind: VirtualMachineClusterInstancetype
metadata:
  name: pas20k
spec:
  cpu:
    guest: 8
  memory:
    guest: 24Gi
          
```
- Click Create.
  Note: You will see pas20k in the list.
Note: Repeat this step for each of the instance sizes needed.
Create a bootable volume from which all other Virtual Machine (VM) bootable volumes will be cloned.
- From the left navigation bar, as an Administrator, under Virtualization, select Bootable volumes.
- Click Add volume drop-down and select With form.
- In the Add volume pop-up, click Upload to upload the .qcow2 file from the location where it was previously downloaded.
- Ensure that appropriate StorageClass, Volume Mode, and Access Mode are selected for your OpenShift system.
- Change Disk size to 151 GiB.
- Enter the volume name in field Volume name. For example, enter nms8-original.
  Note: Upper-case and spaces are not allowed.
- Select the correct destination project.
- From field Preference, select a preference from the drop-down list. For example, rhel.8.
- Click Save.
  Note:
  If you are prompted to accept a security certificate which typically occurs the first time you upload from the browser. You may see a message similar to Invalid certificate. Please visit the following URL and approve it.
  
  Click the link provided in the message to approve the certificate. A blank page will open, indicating that the certificate has been successfully accepted.
  
  Once done, click Save again to continue.
Note: Wait for the upload to complete. This can take several minutes. When done, you will see the new bootable volume listed.
Clone the original bootable volume as a boot disk for your VM.
- Navigate to Virtualization > Bootable volumes.
- Click Add volume drop-down and select With form.
- For Source type, select Volume. Under Use existing, select Volume > Use volume already available on the cluster.
- Specify the Volume project of the volume you want to clone.
- Choose an existing Volume name from the drop-down list that you want to clone from. For example, nms8-original
- Choose the StorageClass associated to the volume selected.
- Provide the Volume name for the cloned volume. For example, nms8-vm1-boot.
- Specify Preference. For example, rhel.8.
- Click Save.
  Note: Wait for the clone to complete.
Create a VM from the cloned bootable disk in the previous step.
- From the left navigation bar, navigate to Virtualization > VirtualMachines.
- Click Create > From InstanceType.
- Under Select volume to boot from, click the bootable disk cloned for this VM in the previous step. i.e., nms8-vm1-boot.
- Under Select InstanceType, select tab User provided and click the instance type for your SevOne product. For example, pas20k as created above.
- Under VirtualMachine details, specify the VM name for your instance.
- If a data disk is required,
  - Click Customize VirtualMachine.
  - Choose tab Configuration.
  - Select Storage.
  - Click Add disk and select Empty disk (blank).
  - In field Name, specify the disk name, for example, nms8-vm1-data.
  - In field Disk size, specify the disk size in GiB. For example, 1250.
  - Click Save.
  - Click Create VirtualMachine.
    Note: Wait for the VM to finish provisioning.
Perform the steps for VM setup for NMS, DI, Solutions, etc.
Note:
To change the SevOne NMS appliance model type, please refer to SevOne NMS Appliance Configuration Guide for details.

To configure the disk, please refer to KVM Drive Configuration for details.