Fedora, Red Hat and IBM: Flatpak 1.5.2, Cockpit 209, OpenShift, Java and More
Flatpak 1.5.2 Continues Work On Authentication Support In Push To Handling Paid Apps
Introduced last month was the Flatpak 1.5.1 development build that provided initial support for protected/authenticated downloads of Flatpaks as the fundamental infrastructure work towards allowing paid or donation-based applications within Flathub or other Flatpak-based "app stores" on Linux.
Flatpak 1.5.2 is out this Friday morning and it has continued work on this focus for authenticated/protected downloads. There has been new API coverage around the authentication code, an OCI authenticator is now bundled, a simple user/password authentication-driven option similar to HTTP-based authentication, and related work towards opening up new use-cases for Flatpak.
Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 209.
A new design for the Overview page
The landing page has been completely redesigned. Information is grouped into easier to understand panels, health information is much more prominent, the resource graphs have been moved to their own page, and the hardware information page should now be easier to find.
We’re headed for edge computing
Every week seems to bring a new report on how edge computing is going to take over the world. This crescendo has been building for the past few years, so it’s no surprise that edge computing sits near the peak on the Gartner hype cycle for emerging technologies. But the question remains—will the edge computing phenomenon take over the world as predicted and, if so, how can businesses benefit from it?
In this and future articles, we’ll demystify edge computing, examine its motivations, and explore best practices in creating scalable edge deployments and the role of open source at the edge. We’ll also look at 5G and its impact to the telco industry, remote office/branch office, IoT, and other use cases.
Persistent data implications for apps and microservices
Speed and agility are the name of the game, whether you are running track in a triathlon, racing to find cures to the world’s most nefarious diseases, or developing new applications that are changing the way society interacts. Application development teams can have a profound effect, not only on their organizations’ ability to differentiate themselves, but also the world we live in.
While just a few years ago, some organizations were still concerned with the viability of running production workloads in containers, the benefits of capitalizing on faster development cycles has garnered favor among developers. And, with enterprise-class enhancements delivered by platforms such as Red Hat OpenShift Container Platform, containers have grown from nifty developer projects, to scalable, more manageable infrastructure environments that enable DevOps for the hybrid cloud.
Cloud Pak for Applications supports IBM Z
The latest version of Cloud Pak for Applications, Version 4.0, extends support for Red Hat OpenShift Container Platform 4.2 onto the IBM Z platform.
Now users can extend their hybrid cloud deployments to include Red Hat OpenShift clusters on IBM Z hardware, taking advantage of the container orchestration platform and tools to bring a consistent experience for development of cloud-native workloads.
Support for OpenShift on IBM Z in this release of IBM Cloud Pak for Applications is limited to the container platform only. IBM runtimes continue to provide support for IBM Z, including container deployments where appropriate.
Exploring OpenShift 4.x Cluster
In this video we will explore the cluster installed during the last video, log into the cluster, configure an authentication provider. We will understand the structure of the cluster and the architecture overview of HA installation. We will get deep understanding of what runs on the master node vs worker node, how the load balancers are setup. We will also look at the cloud provider to see all the infrastructure components that got created by the installer.
Celebrating 20 years of enterprise Java: Milestones
As we celebrate the last 20 years of enterprise Java, it is important to look back at the platform's history to better understand where it came from and how we arrived where we are today.
Enterprise Java emerged during a pivotal time in the history of enterprise computing. When Java 2 Platform, Enterprise Edition (J2EE) 1.2 was introduced in December 1999, it not only marked the birth of enterprise Java, but also signaled an important shift in how organizations were thinking about the web.
Roughly five years earlier, in May 1995, the Java programming language had been publicly released. The language was originally developed to address obstacles faced by a stealth innovation team at Sun Microsystems building the Star7, an interactive handheld home entertainment controller; however, after a tepid response from the television industry, the team instead set its sights on the internet.
Web browsers were making the web more accessible to users, and when the Java language was first announced by Sun, it came with a crucial endorsement: Netscape, one of the leaders in the nascent Web browser market at the time, announced in 1995 that it would include support for Java in its namesake browser.