IBM and Red Hat/Fedora Leftovers
-
How to monitor workloads using OpenShift monitoring stack
The out-of-the-box monitoring stack in Red Hat OpenShift provides a comprehensive set of tools and services to monitor various aspects of your workloads, including metrics, logs, events, and traces. With this monitoring stack, you can gain valuable insights into the health and performance of your applications, identify and troubleshoot issues, and optimize resource utilization. This allows you to deliver a seamless user experience and confidently meet your business objectives.
In this article, we will explore the monitoring stack in Red Hat OpenShift and how to use it to monitor a sample application effectively using Prometheus and Grafana.
-
Back up Kubernetes persistent volumes using OADP
OpenShift APIs for Data Protection (OADP) is an operator that lets you back up and restore workloads in Red Hat OpenShift clusters. It is based on the upstream open source project Velero. You can use OADP to backup and restore all Kubernetes resources for a given project, including persistent volumes.
It is a best practice to be able to recreate your workloads via Infrastructure as Code (IAC) pipelines or automation. Most Kubernetes projects in production already have a way to be recreated; however, when it comes to restoring data from persistent volumes, that requires a separate solution. OADP can fill that gap. This article will focus primarily on restoring persistent volumes.
How does OADP back up persistent volumes?
OADP allows backing up and restoring persistent volumes via either Restic or CSI snapshots. In both cases, incremental backups are supported.
-
Red Hat pays to spruik its views on RHEL source code curbs
The SFC panel included policy fellow Bradley Kuhn, AlmaLinux board chair Benny Vasquez, Samba co-founder and CIQ software engineer Jeremy Allison, and Oracle chief architect for Open Source Policy, Strategy, Compliance, and Alliances, James Wright. CIQ is focused on Rocky Linux, another RHEL derivative; AlmaLinux is also a derivative.
Clearly, Red Hat did not think any of its executives would be comfortable in this environment – even though all the talk was about free and open source software which Red Hat claims to champion.
That should tell the free and open source software community where the company's priorities lie.
Hellekson fielded all the softball questions thrown at him by The Futurum Group's Steven Dickens and was allowed to talk at length about the noble work being done by the IBM-owned company. Not surprising, as he who pays the piper generally calls the tune.
One of Dickens' questions embodies perfectly the type of queries that Hellekson fielded: "Red Hat’s commercial business, you’re taking the pipeline of free, community-developed, adding a significant amount of value, testing, certification, support, and they’re looking to build a commercial business off that. You’re not alone in doing this. I had Ash Kulkarni, the CEO of Elastic on this podcast a few weeks back. We’ve spent some time at MongoDB and spoke to their team.
-
How to fully utilize OpenShift for DevOps
There is nothing developers and users hate more than waiting a long time for new software features to be deployed. Being stuck in an endless loop of long response times for QA and feedback is painful, especially when they have started a new project.
-
Fedora Community Blog: Community Blog monthly summary: July 2023
This is the latest in our monthly series summarizing the past month on the Community Blog. Please leave a comment below to let us know what you think.
-
Implementing clean architecture solutions: A practical example
The purpose of this project is to provide developers with a practical example of how clean architecture can be implemented in a real-world scenario. By examining this sample project's code and structure, you will be able to better understand the key concepts and patterns involved in clean architecture.
Why clean architecture?
These days, the IT world is flooded with an overwhelming number of libraries, technologies, frameworks, and platforms to choose from. What's considered the ultimate solution today may become outdated tomorrow. What doesn't exist today might become tomorrow's ultimate solution. Clean architecture incorporates principles like SOLID and domain-driven design and enforces them through module structuring during compilation. However, it's important to note that not everything can be enforced at compile time.
By embracing clean architecture principles, you can design software without getting tied down to specific libraries, infrastructure, or other choices right from the start of your project. Instead, you can postpone those decisions until later in the development process. This approach also makes it easier to switch libraries or infrastructure if needed, enabling you to create software that can stand the test of time. With clean architecture, you can keep your options open and ensure that your platform or application remains robust and adaptable in the long run.