MySphere

openshift

OpenShift Day 2 Operations - Part 3

05 Nov, 2025

Retrieving OpenShift Cluster Logs Logs are invaluable for understanding the state of your OpenShift cluster and diagnosing problems. OpenShift provides several ways to access these logs efficiently: Get node logs Display node journal: oc adm node-logs Tail 10 lines from node journal: oc adm node-logs --tail=10 Get kubelet journal logs only: oc adm node-logs -u kubelet.service Grep kernel word on node journal: oc adm node-logs --grep=kernel List /var/log contents: oc adm node-logs --path=/ Get /var/log/audit/audit.log from node: oc adm node-logs --path=audit/audit.log Pod Logs Pod logs provide insights into application behavior. - Retrieve logs for a s

openshift

OpenShift Day 2 Operations - Part 2

19 Aug, 2025

“Day 2” operations refer to everything that happens after the cluster is installed, which could be a lot or a little, depending on how you plan to use the cluster. Effective troubleshooting and monitoring in OpenShift require understanding the right way to retrieve logs and manage issues. While it might be tempting to SSH directly into cluster nodes, OpenShift provides tools and workflows to handle logs more securely and efficiently. Why You Should Avoid SSHing to Nodes SSHing directly into cluster nodes might seem like a quick way to debug issues, but it introduces several risks and challenges: 1. Security Risks - Inconsistent Access Control: Granting SSH access bypasses OpenShift’s

openshift

OpenShift Day 2 Operations - Part 1

29 Jul, 2025

“Day 2” operations refer to everything that happens after the cluster is installed, which could be a lot or a little, depending on how you plan to use the cluster. Verifying the Health of Your OpenShift 4 Cluster Managing an OpenShift 4 cluster effectively involves regular health checks to ensure smooth operation and reliability. An unhealthy cluster can lead to downtime, reduced performance, and compromised workloads. Node Health Healthy nodes are crucial for running workloads effectively. - Use this command to check the node status: oc get nodes Verify that all nodes show Ready in the STATUS column. You can use oc get nodes -o wide to get more details about the cluster For more

What is CPU Thrashing and its Impact on IBM ACE Servers

05 Jul, 2025

Introduction In the context of integration servers, such as IBM App Connect Enterprise (ACE), improper configurations can lead to significant performance issues. One such issue is CPU thrashing, which can be triggered by settings such as setting 256 additional instances for a message flow. This article explains what CPU thrashing is, its causes, effects, and how to mitigate it, focusing on its relevance to IBM ACE. What is CPU Thrashing? CPU thrashing occurs when a computer's CPU becomes overloaded due to excessive context switching between tasks or threads, resulting in poor efficiency and reduced performance. Instead of doing useful work, the CPU spends most of its time managing switchi

openshift

Exploring Kubernetes Startup Scaling

26 Jun, 2025

Kubernetes has long been a cornerstone for managing containerized workloads, and its continuous evolution keeps it at the forefront of cloud-native technologies. One of the exciting advancements in recent releases is the enhancement of startup scaling capabilities, particularly through features like Kube Startup CPU Boost and dynamic resource scaling. In this blog post, we’ll dive into what startup scaling is, how it works, and why it’s a significant addition for Kubernetes users looking to optimize application performance during startup. What is Startup Scaling in Kubernetes? Startup scaling refers to the ability to dynamically allocate additional resources, such as CPU, to pods during th

IBM ACE 13.0.4 Evaluation edition

26 Jun, 2025

IBM App Connect Enterprise 13.0.4 Evaluation Edition is available on the following link: https://www.ibm.com/resources/mrs/assets?source=swg-wmbfd(https://www.ibm.com/resources/mrs/assets?source=swg-wmbfd) Builds on version 13.0 with a focus on usability, AI integration, and automation. - AI watsonx Code Assistant in Toolkit - AI Mapping Assist in Designer - AI Data Assist in Designer - Context Trees for improved Toolkit usability - New Toolkit Discovery Request Nodes: Azure Service Bus and IBM Planning Analytics - New Toolkit Discovery Input Nodes: Amazon EventBridge and Azure Service Bus - Toolkit Salesforce Input node new state persistence policy - Open Telemetry support for Toolkit Ka

openshift

Exploring Red Hat OpenShift 4.18: What’s New and Why It Matters

07 Apr, 2025

Released on February 24, 2025, Red Hat OpenShift 4.18 is here, bringing a fresh wave of enhancements to the Kubernetes-powered hybrid cloud platform. Whether you’re a developer, a sysadmin, or an IT decision-maker, this update has something to pique your interest—think beefed-up security, slick virtualization upgrades, and tools to make your clusters easier to monitor and manage. Let’s dive into what’s new and why OpenShift 4.18 might just be the upgrade your team’s been waiting for. Security That Packs a Punch In today’s world, keeping sensitive data safe is non-negotiable, and OpenShift 4.18 steps up to the plate. One standout feature is the Secrets Store CSI Driver Operator, now fully a

cloud

Create AWS S3 bucket to backup OpenShift projects using IBM Storage Fusion

03 Apr, 2025

To create an AWS S3 bucket to use as a backup location for IBM Storage Fusion, you need to configure the bucket in AWS and ensure that it is properly configured for compatibility with IBM Storage Fusion. Below are the steps to achieve this: Step 1: Sign in to the AWS Management Console 1. Sign in aws.amazon.com(https://aws.amazon.com) and sign in to your AWS account using your credentials. 1. After you sign in, navigate to the AWS Management Console. Step 2: Access the S3 service 1. In the AWS Management Console, use the search bar at the top and enter S3. 1. Select S3 from the results to open the Amazon S3 dashboard. Step 3: Create an S3 bucket 1. From the S3 dashboard, click the Crea

linux

Error when run dnf install rpm-build

31 Mar, 2025

I was installing the IBM MQ Server on a linux box yesterday. I got the error bellow: \root@gateway MQServer\ dnf install rpm-build
Updating Subscription Management repositories.
Instana 14 B/s | 20 B 00:01
Errors during downloading metadata for repository 'instana-agent': Status code: 401 for https://:[email protected]/agent/rpm/generic/x86\64/repodata/repomd.xml (IP: 34.253.98.124)
Error: Failed to download metadata for repo 'instana-agent': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Solution: Delete the Instana Agent repo: rm /etc/yum.repos.d/Instana-Agent.repo
Clear dnf cache: dnf clean all
run dnf i

How to Fix Error 513 When Unzipping Large Files on macOS

25 Mar, 2025

If you’ve ever tried to unzip a large file on macOS and encountered the mysterious "Error 513," you’re not alone. This pesky error can pop up unexpectedly, leaving you scratching your head and wondering why your file won’t extract properly. Recently, I ran into this issue myself while trying to decompress a massive archive using the built-in Archive Utility on macOS. After some trial and error, I found a reliable solution: the Keka application. Here’s a rundown of what Error 513 is, why it happens, and how Keka saved the day. What Is Error 513 on macOS? Error 513 typically occurs when macOS’s default Archive Utility struggles to handle certain zip files—particularly large ones or those wi

Python script to organize photos

03 Mar, 2025

"I have lots of photo files. Since 2006, when I purchased my first digital camera, the number of photos has grown quickly, and after getting an iPhone, the number of photos exploded. With the high number of photos, the number of backups grew as well. I decided to organize all backups and create folders using the format YYYY-MM from the metadata of the photo files." Bellow the python script. The script runs on macos: import os import shutil import datetime import logging import tkinter as tk from tkinter import filedialog from PIL import Image, ExifTags import pillowheif import piexif import struct Setup logging logging.basicConfig(level=logging.DEBUG, format="%(asctime)s - %(levelname

openshift

New Flags in OpenShift 4.17 Must-Gather Tool

11 Feb, 2025

The oc adm must-gather tool is essential for troubleshooting and diagnostics in OpenShift. With the release of OpenShift 4.17, new flags have been introduced to enhance flexibility and precision in data collection. These additions enable administrators to gather logs more efficiently while reducing unnecessary data collection. New Flags in Must-Gather --since This flag allows users to collect logs newer than a specified duration. For example: oc adm must-gather --since=24h This command gathers logs from the past 24 hours, making it easier to pinpoint recent issues. --since-time The --since-time flag lets users specify an exact timestamp (RFC3339 format) to collect logs from a pa