Improving SLA Accuracy by Aligning Work Order Reported Date with PM Seasonal Start Time | Maximo

Why This Is Needed (in base Maximo)

By default, PM work orders are created with a REPORTDATE based on the PMWoGenCronTask run time.

This causes SLA targets (response, resolution, target start/finish) to be calculated from the wrong date.

Seasonal PMs often require SLAs to start from the seasonal start time defined in PM.TARGSTARTTIME.

By merging that time into the REPORTDATE, SLA calculations become accurate and fully aligned with the seasonal schedule—instead of the cron generation timestamp.

To ensure SLAs calculate correctly from the intended seasonal start time, I added an Object Launch Point automation script on WORKORDER with:

Condition: pmnum is not null

Events: Add, Save, Before Save

The script takes the time from PM.TARGSTARTTIME and applies it to the date in REPORTDATE, ensuring the work order uses the correct seasonal seed date before any SLA is applied.

Install OpenShift on VMware with Assisted Installer. Fully Automatic. | Linux

 Installing OpenShift on VMware with Assisted Installer (Fully Automated)

If you’re looking to quickly set up OpenShift in a data center environment using VMware, the Assisted Installer is one of the most convenient options. This guide walks you through the process of installing OpenShift 4.19 (or the latest version) with minimal manual steps — once configured, the installation is mostly automatic.

Prerequisites

• VMware environment with enough resources (recommended: 16 vCPU, 32 GB RAM, NAT interface for internet access).
• A Linux machine with SSH key generated.
• Basic DNS or /etc/hosts configuration access.

Step 1: Access the Assisted Installer

1. Download the ISO from the Assisted Installer portal.

   The ISO will be tied to your VM’s public key.

2. In the portal, select:

Create Cluster (button) → Data Center (tab) → Create Cluster (button)

Step 2: Define Cluster Settings

• Cluster name: mycluster
• Base domain: mycluster.com
• OpenShift version: 4.19 (or latest available) 
• CPU architecture: x86_64
• External platform integration: None
• Control plane nodes: 1 (Single-node OpenShift) (atleast 3 nodes for HA cluster production grade)
• Hosts’ network configuration: DHCP (default)

Click Next.

Step 3: Operators Page

Leave defaults as-is. Click Next.

Step 4: Host Discovery

1. Select Provisioning Type → Full image file (Download a self-contained ISO).

2. Add your SSH public key:

   • On your Linux machine, run:

     ssh-agent
     cat ~/.ssh/id*.pub
     

   • Copy and paste the output into the Assisted Installer.

3. Skip Proxy and Certificates (set to No).

4. Click Generate Discovery ISO → Download the ISO.

5. Create a VM in VMware (16 vCPU, 32 GB RAM, NAT).

6. Boot the VM with the ISO.

Now, sit back and wait. The installation will run automatically and usually takes about 1 hour.

Step 5: Configure DNS or Hosts File

Before accessing the console, configure your DNS (recommended) or update /etc/hosts on your PC.

DNS entries:

api.assistedcluster.rukndarna.com        A   192.168.23.164
*.apps.assistedcluster.rukndarna.com     A   192.168.23.164

/etc/hosts entries (alternative):

192.168.23.164  api.assistedcluster.rukndarna.com
192.168.23.164  oauth-openshift.apps.assistedcluster.rukndarna.com
192.168.23.164  console-openshift-console.apps.assistedcluster.rukndarna.com
192.168.23.164  grafana-openshift-monitoring.apps.assistedcluster.rukndarna.com
192.168.23.164  thanos-querier-openshift-monitoring.apps.assistedcluster.rukndarna.com
192.168.23.164  prometheus-k8s-openshift-monitoring.apps.assistedcluster.rukndarna.com
192.168.23.164  alertmanager-main-openshift-monitoring.apps.assistedcluster.rukndarna.com

---

Step 6: Access the Web Console

Once installation completes, the console URL will be available:

Web Console:
https://console-openshift-console.apps.assistedcluster.rukndarna.com/

Credentials:

Username: kubeadmin

Password: <password> (replace with your generated password)

You can also download the kubeconfig file for password-less access.

---

Step 7: Connect with oc CLI

From your personal machine, you can connect in two ways:

• Using kubeconfig (no password):

  oc get nodes --kubeconfig=kubeconfigfile
  

• Using username/password:

  oc login -u kubeadmin -p 0000000 https://api.assistedcluster.rukndarna.com:6443
  

---

Common Useful Commands

oc get nodes
oc get co
oc get csr
oc whoami --show-console
oc get services
grep server kubeconfig

---

Done :) we have a single-node OpenShift cluster running on VMware with Assisted Installer — fully automated and ready for exploration.

Installing OpenShift on bare metal using Full Control (UPI) – Quick Step-by-Step Guide | Maximo

This guide explains how to deploy OpenShift on Bare Metal (UPI) in a VMware environment using a Service Node, Bootstrap Node, Control Plane, and Worker Nodes.

In VMware with Service Node, Bootstrap, and Master/worker nodes.

Log in to Red Hat Console: 

Goto - > Clusters -> Data Center -> Other Datacenter Options -> (Bare Mtail /x86_64)

References:

1	GitHub - ryanhay/ocp4-metal-install: Install OpenShift 4 on Bare Metal - UPI
2	How to install OpenShift 4 on Bare Metal - User Provisioned Infrastructure (UPI)
3	How to Install OpenShift 4 on Bare Metal through User Provisioned Infrastructure (UPI)
4	RedHat OpenShift Bootcamp | HA Cluster Deployment with UPI method part1

 

Requirements:

0	Service node/bastion	Any linux, I am using Rocky	2 interfaces: Eth0 , eth1 Eth0 for external using NAT automatic ip.     Eth1 is internal hostonly. (192.168.22.1/24)
	Services	Firewall/router, DNS, webserver, ingress/LoadBalancer,dhcp,
	Openshift Installer	Installer script from console.redhat
	Pull secret	From redhat console
	Cli agent tools	Client tools
	Redhat core os boot iso file to boot	Rhcos*.io
	Actual Redhat core OS raw.gz file	Rhcos*.raw.gz
	Ignition files	Run with raw.gz files on nodes with coreos-installer command
	Timezone	UTC, same as coreos by default
	NAT, IP forwarding	Enable using firewalld	From internal to external
1	Bootstrap node	based on the installer	nmtui :ip 22.200, gw 22.1, ns: 22.1, search domain: ocp.lan
2	Masters	based on the installer	nmtui :ip 22.201-203, gw 22.1, ns: 22.1, search domain: ocp.lan
3	Workers	based on the installer	nmtui :ip 22.211-213, gw 22.1, ns: 22.1, search domain: ocp.lan
4	Vmware vmx files	In all VMs' vmx files, add this before booting	Disk.EnableUUID = "TRUE"
5	Vm storage	Check drive type ·         SCSI / SATA controllers → Devices show up as /dev/sdX. ·         NVMe controllers → Devices show up as /dev/nvmeXnY	lsblk

My VMWare Settings (Virtual Network Editor)

To simulate a production-like isolated OpenShift environment, I used a host-only network as a private subnet accessible via a bastion (service) node. The bastion has an additional NAT interface (vmnet8) to share the host’s internet, acting as a gateway for the OpenShift nodes.