Published on Tux Machines (http://www.tuxmachines.org)

Home > content > Red Hat/Fedora Leftovers

Red Hat/Fedora Leftovers

By Roy Schestowitz Created 23/11/2020 - 5:27pm Submitted by Roy Schestowitz on Monday 23rd of November 2020 05:27:57 PM Filed under Red Hat [1]

Order from chaos: Red Hat and Starburst come together to simplify data access[2]

Enterprises rely on data to bring order to their organizations through automation, business process management and optimization, and increased intelligence that leads to better decision making. Yet data can be difficult to access, especially when it exists in many places.

Today, data can be found in data centers, the cloud, vendor environments, and in traditional and software-defined data sources. Data ingested from the network edge may be aggregated at remote locations, transactional databases and data warehouses typically live in the core datacenter, while cloud-native applications generally store data in a private and/or public cloud. Data stores can be found in distributed, hybrid cloud, traditional, and modern applications?in many cases within the same organization.

Extending choice for more flexible, more secure open hybrid cloud: Red Hat Enterprise on AWS Outposts[3]

Linux and open hybrid cloud go hand-in-hand - the power, flexibility and scale of hybrid cloud is made possible by the foundation of the Linux operating system. The world?s leading enterprise Linux platform, Red Hat Enterprise Linux (RHEL), already delivers this foundation across nearly every public cloud, server architecture and virtualized environment, but customer needs aren?t static. As new options for hybrid cloud computing emerge, we work to extend RHEL to meet these deployments, highlighted by support today for RHEL on AWS Outposts.

While many organizations are able to reach outside of the confines of their datacenter to explore public and hybrid cloud options, some cannot due to unique security or compliance needs. Outposts bring the scale and power of Amazon Web Services (AWS) cloud to corporate datacenters in an appliance managed by AWS experts. Now, the organizations using Outposts can turn to RHEL to provide greater consistency across their IT estate, from traditional bare- metal servers, virtualized environments, private cloud infrastructure and their gateway to public cloud resources.

[...]

Our goal with RHEL is to deliver an operating system that spans the open hybrid cloud, regardless of the path that an organization takes or the tools that they choose to use. With this new support for AWS Outposts, we have continued to drive customer choice in how they build hybrid cloud deployments with a single common platform in RHEL.

Run serverless functions, Kubernetes ingress controllers comparisons, and more industry trends | Opensource.com[4]

As part of my role as a principal communication strategist at an enterprise software company with an open source development model, I publish a regular update about open source community, market, and industry trends. Here are some of my and their favorite articles from that update.

Fedora 34 Change: Route all Audio to PipeWire (System-Wide Change)[5]

Fedora 34 Might Try To Use PipeWire By Default To Replace PulseAudio/JACK[6]

Red Hat for several years now has been working on PipeWire to overhaul audio/video stream management on Linux while being able to fill the duties currently managed by the likes of PulseAudio and JACK and being engineered with Wayland and security in mind among other modern Linux technologies. With Fedora 34 next spring they may try to ship PipeWire by default in place of JACK, PulseAudio, and even legacy ALSA.

For a while now Fedora has offered PipeWire packages but not yet used by default when it comes to audio handling. A pending change proposal for Fedora 34 would now route all audio through PipeWire rather than the existing JACK and PulseAudio.

With the proposed plan, Fedora 34 next spring with PipeWire would take over all desktop audio duties by default from PulseAudio. PipeWire provides a functionally compatible implementation of the PulseAudio daemon so existing Linux software should continue to work fine. Similarly, PipeWire would provide F34's JACK support for professional audio needs. For legacy ALSA clients, an ALSA plug-in for PipeWire allows routing audio through it as well.

Red Hat

Source URL: http://www.tuxmachines.org/node/144675 Links: [1] http://www.tuxmachines.org/taxonomy/term/142 [2] https://www.redhat.com/en/blog/order-chaos-red-hat-and-starburst-come-together-simplify-data-access [3] https://www.redhat.com/en/blog/extending-choice-more-flexible-more-secure-open-hybrid-cloud-red-hat-enterprise- linux-aws-outposts [4] https://opensource.com/article/20/11/love-multi-cloud-and-more-industry-trends [5] https://lists.fedoraproject.org/archives/list/[email protected]/thread/ZWIX7EQG6EHXVGJBENN6JH3XGYLX3FTW/ [6] https://www.phoronix.com/scan.php?page=news_item&px=Fedora-34-PipeWire-Plan