Why AI Agents Need A Human in the Loop Now

  • 10 Mar, 2026

Can AI agents succeed without humans? Anna Gutowska explains the importance of Human-in-the-Loop (HITL) systems for safe and ethical AI decision-making. Learn how HITL balances automation, compliance,

Why AI Agents Need A Human in the Loop NowRead More

A2A vs MCP: AI Agent Communication Explained

  • 10 Mar, 2026

Sobre o vídeo: Ready to become a certified watsonx AI Assistant Engineer v1 - Professional? Register now and use code IBMTechYT20 for 20% off of your exam → https://ibm.biz/BdpXdV Learn more about A

A2A vs MCP: AI Agent Communication ExplainedRead More

Podman pull images behind a corporate proxy

  • 26 Nov, 2025

Today, I set out to pull an image from Docker Hub on a RHEL 9 system using Podman. This step was part of my journey to install Watson Code Assistant for Z. While Podman is a great alternative to Docker on RHEL, the process had its quirks—especially when working with enterprise environments and specialized tools like Watson Code Assistant. In this post, I’ll share what worked, what didn’t, and some tips to make the setup smoother for anyone tackling the same challenge. I can simulate the error using podman pull: podman pull docker.io/library/orientdb:3.2.28 Trying to pull docker.io/library/orientdb:3.2.28... WARN0000 Failed, retrying in 1s ... (1/3). Error: initializing source docker://or

Podman pull images behind a corporate proxyRead More

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 Day 2 Operations - Part 3Read More

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 Day 2 Operations - Part 2Read More

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

OpenShift Day 2 Operations - Part 1Read 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

What is CPU Thrashing and its Impact on IBM ACE ServersRead More

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

Exploring Kubernetes Startup ScalingRead More

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

IBM ACE 13.0.4 Evaluation editionRead More

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

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

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

Create AWS S3 bucket to backup OpenShift projects using IBM Storage FusionRead More

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

Error when run dnf install rpm-buildRead More