Engineering the World
-
Access to Power Systems for Development
Linda, a colleague on IBM Power Systems development, assembled a nice compendium of resources for developing solutions on IBM Power (ppc64le) architecture. To read more click on the link, and review the details Want access to IBM Power Hardware for development efforts? We have compiled a list of cloud, emulation, and on-prem options for you […]
-
Using Ghost on OpenShift Container Platform
To demonstrate a multi-tiered web application, I used ghost, the microblogging platform to deploy the application using kustomize. Kustomize is a higher-level orchestration of the steps to deploy an application with environment specific overlays.
-
Support for detecting nx-gzip coprocessor feature in Node Feature Discovery
When the Worker or Control Plane node has Node Feature Discovery enabled on a Power 10 PowerVM with Red Hat Enterprise Linux 9.1 or higher, the label coprocessor.nx_gzip is present on the node. You can see more details in the PR 956
-
Downloading oc-compliance on ppc64le
My team is working with the OpenShift Container Platforms Optional Operator – Compliance Operator. The Compliance Operator has a supporting tool `oc-compliance`. One tricky element was downloading the oc-compliance plugin and I’ve documented the steps here to help
-
OpenShift on Power Blogs…
Recently, I started a leadership position on a new squad focused on OpenShift on IBM Power Systems. Two of my teammates have posted blogs about their work: I hope you found these as useful as I did. Best wishes, PB
-
Tweak for GoLang PowerPC Build
As many know, Go is a designed to build architecture and operating system specific binaries. These architecture and operating system specific binaries are called a target. One can target GOARCH=ppc64le GOOS=linux go build to build for the specific OS. There is a nice little tweak which considers the architectures version and optimizes the selection of the ASM (assembler code) uses when building the code.
-
Using Go Memory and Processor Limits with Kubernetes DownwardAPI
As many know, Go is a designed for performance with an emphasis on memory management and garbage collection. When used within cgroups with Kubernetes and Red Hat OpenShift Go maximizes for the available memory on the node and the available processors. This approach, as noted by Uber’s automaxprocs, a shared system can see slightly degraded performance when allocated CPUs are not limited to the actually available CPUs (e.g., a prescribed limit).
-
Linking Quay to OpenShift and you hit `x509: certificate signed by unknown authority`
-
Use Qemu to Build S390x images
-
Setting up nfs-provisioner on OpenShift on Power Systems
Here are my notes for setting up the SIG’s nfs-provisioner. You should follow these directions to setup the nfs-provisioner