Language Selection

English French German Italian Portuguese Spanish

Red Hat: Edge Computing, Red Hat Success Stories, OpenShift 4.2 and More

Filed under
Red Hat
  • 10 edge computing myths, debunked

    Edge computing can mean different things to different technology leaders – from “anything that’s not in the cloud” to “the practice of capturing, storing, processing, and analyzing data nearest to where the data is generated.” As important as knowing what edge computing is, however, is understanding what it is not.

    [...]

    “Edge can vary based on computing, storage, and where you engage streaming data,” says Jason Mann, VP of IoT at SAS. It will also vary based on your point of view, adds Hopkins. The enterprise edge will look different than a cloud vendor’s or a telco’s edge.

  • Red Hat Success Stories: Reducing friction in Southeast Asia banking and more

    Wondering how Red Hat is helping its customers to succeed? Last month we published six customer success stories that highlight how we've helped customers gain efficiency, cut costs, and transform the way they deliver software. Read on to find out how Ascend Money, Heritage Bank, Generali Switzerland, and others have worked with Red Hat to improve their business.

    [...]

    To improve the efficiency of its application processes, Ascend Money decided to migrate its legacy applications to a standardized platform using Red Hat technology. With assistance from Red Hat Consulting, Ascend Money moved both its legacy applications and new cloud-native services to OpenShift Container Platform, providing a single platform for IT and developers to collaborate across cloud environments.

  • OpenShift 4.2 Disconnected Install

    In a previous blog, it was announced that Red Hat is making the OpenShift nightly builds available to everyone. This gives users a chance to test upcoming features before their general availability. One of the features planned for OpenShift 4.2 is the ability to perform a “disconnected” or “air gapped” install, allowing you to install in an environment without access to the Internet or outside world.

  • Develop with Node.js in a container on Red Hat Enterprise Linux

    In my previous article, Run Red Hat Enterprise Linux 8 in a container on RHEL 7, I showed how to start developing with the latest versions of languages, databases, and web servers available with Red Hat Enterprise Linux 8, even if you are still running RHEL 7. In this article, I’ll build on that base to show how to get started with Node using the current RHEL 8 application stream versions of Node.js and Redis 5.

    From my perspective, using Red Hat Enterprise Linux 8 application streams in containers is preferable to using software collections on RHEL 7. While you need to get comfortable with containers, all of the software installs in the locations you’d expect. There is no need to use scl commands to manage the selected software versions. Instead, each container gets an isolated user space. You don’t have to worry about conflicting versions.

    In this article, you’ll create a Red Hat Enterprise Linux 8 Node.js container with Buildah, and run it with Podman. The code will be stored on your local machine and mapped into the RHEL 8 Node.js container when it runs. You’ll be able to edit the code on your local machine as you would any other application. Because it is mapped via a volume mount, the changes you make to the code will be immediately visible from the container, which is convenient for dynamic languages that don’t need to be compiled. This method isn’t the way you’d want to do things for production, but it gets you started developing quickly and should give you essentially the same development inner loop as you’d have when developing locally without containers. This article also shows how you can use Buildah to build an image with your completed application that you could use for production.

    Additionally, you’ll set up the Red Hat Enterprise Linux 8 Redis application stream in a container that is managed by systemd. You’ll be able to use systemctl to start and stop the container just as you would for a non-container installation.

More in Tux Machines

Python Across Platforms

  • Chemists bitten by Python scripts: How different OSes produced different results during test number-crunching

    Chemistry boffins at the University of Hawaii have found, rather disturbingly, that different computer operating systems running a particular set of Python scripts used for their research can produce different results when running the same code. In a research paper published last week in the academic journal Organic Letters, chemists Jayanti Bhandari Neupane, Ram Neupane, Yuheng Luo, Wesley Yoshida, Rui Sun, and Philip Williams describe their efforts to verify an experiment involving cyanobacteria, better known as blue-green algae. Williams, associate chair and professor in the department of chemistry at the University of Hawaii at Manoa, said in a phone interview with The Register on Monday this week that his group was looking at secondary metabolites, like penicillin, that can be used to treat cancer or Alzheimer's.

  • Chemists discover cross-platform Python scripts not so cross-platform

    In a paper published October 8, researchers at the University of Hawaii found that a programming error in a set of Python scripts commonly used for computational analysis of chemistry data returned varying results based on which operating system they were run on—throwing doubt on the results of more than 150 published chemistry studies. While trying to analyze results from an experiment involving cyanobacteria, the researchers—Jayanti Bhandari Neupane, Ram Neupane, Yuheng Luo, Wesley Yoshida, Rui Sun, and Philip Williams—discovered significant variations in results run against the same nuclear magnetic resonance spectroscopy (NMR) data. The scripts, called the "Willoughby-Hoye" scripts after their authors—Patrick Willoughby and Thomas Hoye of the University of Minnesota—were found to return correct results on macOS Mavericks and Windows 10. But on macOS Mojave and Ubuntu, the results were off by nearly a full percent.

today's leftovers

  • Fedora Removes 32bit, System76 Coreboot, Flatpak, Valve, Atari VCS, Docker | This Week in Linux 84

    On this episode of This Week in Linux, we talk about Fedora Removing 32-bit, well sort of. System76’s announced two laptops using Coreboot firmware. There is some interesing news regarding Docker and its future. Then we’ll check out some Linux Gaming news with some really exciting news from Valve! 

  • PostgreSQL 12 boosts open source database performance

    Performance gains are among the key highlights of the latest update of the open source PostgreSQL 12 database. PostgreSQL 12 became generally available Oct. 3, providing users of the widely deployed database with multiple enhanced capabilities including SQL JSON query support and improved authentication and administration options. The PostgreSQL 12 update will potentially affect a wide range of use cases in which the database is deployed, according to Noel Yuhanna, an analyst at Forrester Research. "Organizations are using PostgreSQL to support all kinds of workloads and use cases, which is pushing the needs for better performance, improved security, easier access to unstructured data and simplified deployments," Yuhanna said. "To address this, PostreSQL12 improves performance by improving its indexing that requires less space and has better optimization to deliver faster access."

  • Olimex Launches NB-IoT DevKit Based on Quectel BC66 Module for 19 Euros

    There are three LPWAN standards currently dominating the space LoRaWAN, NB-IoT, and Sigfox. 

  • Intel Denverton based Fanless Network Appliance Comes with 6x Ethernet Ports, 2x SFP Cages
  • Heading levels

    the headings would be “Apples” (level 1), “Taste” (level 2), “Sweet” (level 3), “Color” (level 2). Determining the level of any given heading requires traversing through its previous siblings and their descendants, its parent and the previous siblings and descendants of that, et cetera. That is too much complexity and optimizing it with caches is evidently not deemed worth it for such a simple feature. However, throwing out the entire feature and requiring everyone to use h1 through h6 forever, adjusting them accordingly based on the document they end up in, is not very appealing to me. So I’ve been trying to come up with an alternative algorithm that would allow folks to use h1 with sectioning elements exclusively while giving assistive technology the right information (default styling of h1 is already adjusted based on nesting depth). The simpler algorithm only looks at ancestors for a given heading and effectively only does so for h1 (unless you use hgroup). This leaves the above example in the weird state it is in in today’s browsers, except that the h1 (“Color”) would become level 2. It does so to minimally impact existing documents which would usually use h1 only as a top-level element or per the somewhat-erroneous recommendation of the HTML Standard use it everywhere, but in that case it would dramatically improve the outcome.

  • openSUSE OBS Can Now Build Windows WSL Images

    As Windows Subsystem for Linux (WSL) is becoming a critical piece of Microsoft’s cloud and data-center audience, openSUSE is working on technologies that help developers use distributions of their choice for WSL. Users can run the same WSL distribution that they run in the cloud or on their servers. The core piece of openSUSE’s WSL offering is the WSL appx files, which are basically zip files that contain a tarball of a Linux system (like a container) and a Windows exe file, the so called launcher.

2D using Godot

This brings me to the GUI parts. I’m still not convinced that I understand how to properly layout stuff using Godot, but at least it looks ok now – at the cost of some fixed element sizes and such. I need to spend some more time to really understand how the anchoring and stretching really works. I guess I have a hard time wrapping my head around it as the approach is different from what I’m used to from Qt. Looking at the rest of the code, I’ve tried to make all the other scenes (in Godot, everything is a scene) like independent elements. For instance, the card scene has a face, and an is_flipped state. It can also signal when it is being flipped and clicked. Notice that the click results in a signal that goes to the table scene, which decides if the card needs to be flipped or not. The same goes for the GUI parts. They simple signal what was clicked and the table scene reacts. There are some variables too, e.g. the number of pairs setting in the main menu, and the points in the views where that is visible. Read more

Linux Graphics Stack: Intel, AMD and More

  • Intel Linux Graphics Driver Adds Bits For Jasper Lake PCH

    Details are still light on Jasper Lake, but volleyed onto the public mailing list today was the initial support for the Jasper Lake PCH within the open-source Linux graphics driver side. The patch adds in the Jasper Lake PCH while acknowledging it's similar to Icelake and Tigerlake behavior. The Jasper Lake PCI device ID is 0x4D80. The patch doesn't reveal any other notable details but at least enough to note that the Jasper Lake support is on the way. Given the timing, the earliest we could see Intel Jasper Lake support out in the mainline kernel would be for Linux 5.5, which will be out as stable as the first kernel series of 2020 and in time for the likes of Ubuntu 20.04 LTS and Fedora 32.

  • Linux Graphics Drivers Could Have User-Space API Changes More Strictly Evaluated

    In response to both the AMD Radeon and Intel graphics drivers adding new user-space APIs for user-space code that just gets "[thrown] over the wall instead of being open source developed projects" and the increase of Android drivers introducing their own UAPI headaches, Airlie is looking at enforcing more review/oversight when DRM drivers want to make user-space API changes. The goal ultimately is to hopefully yield more cross-driver UAPI discussions and in turn avoiding duplicated efforts, ensuring good development implementations prior to upstreaming, and better quality with more developers reviewing said changes.

  • xf86-video-ati 19.1 Released With Crash & Hang Fixes

    For those making use of xf86-video-ati on X.Org-enabled Linux desktops, the version 19.1 release brings just a handful of new fixes. This release was announced today by Michel Dänzer who last month departed AMD to now work on Red Hat's graphics team. Michel is sticking around the Mesa/X.Org world for Red Hat's duties but is hoping someone else will be picking up maintenance of the xf86-video-ati/xf86-video-amdgpu DDX drivers going forward. Granted, not a lot of activity happens to these X.Org DDX drivers these days considering more Linux desktops slowly moving over to Wayland, many X11 desktops using the generic xf86-video-modesetting, and these AMD drivers being fairly basic now with all of the big changes in the AMDGPU DRM kernel driver.