Language Selection

English French German Italian Portuguese Spanish

Red Hat

Fedora: GSoC, Fedora Program Management, PHP, Fedora Infrastructure, Test Day and EPEL

Filed under
Red Hat
  • Fedora Community Blog: GSoC summer 2019: Fedora Gooey Karma

    The day GSoC projects list was published I started sorting out all the organizations that I’d enjoy working with. Being a Linux user/enthusiast I filtered down to a bunch of Linux distros and desktop managers. Sorting out all the projects, Fedora-Gooey-Karma seemed to be a project that suited the skills I have.

    Once I was sure that Fedora Gooey Karma is a project that I would love to work on during the summer, I mailed @sumantro about the project. We talked about the project on mails.

  • Fedora Community Blog: FPgM report: 2019-37

    Here’s your report of what has happened in Fedora Program Management this week. Fedora 31 Beta is go!

    I have weekly office hours in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else.

  • PHP version 7.2.23RC1 and 7.3.10RC1

    Release Candidate versions are available in testing repository for Fedora and Enterprise Linux (RHEL / CentOS) to allow more people to test them. They are available as Software Collections, for a parallel installation, perfect solution for such tests (for x86_64 only), and also as base packages.

    RPM of PHP version 7.3.10RC1 are available as SCL in remi-test repository and as base packages in the remi-test repository for Fedora 30-31 or remi-php73-test repository for Fedora 29 and Enterprise Linux.

    RPM of PHP version 7.2.23RC1 are available as SCL in remi-test repository and as base packages in the remi-test repository for Fedora 29 or remi-php72-test repository for Enterprise Linux.

  • Karsten Hopp: Onboarding Fedora Infrastructure

    I'm using / working on Fedora since FC-1 and just recently joined the Infrastructure team.

  • Fedora Community Blog: Fedora 31 Gnome Test Day 2019-09-18

    Wednesday, 2019-09-18 is the Fedora 31 Gnome Test Day! As part of changes Gnome 3.34 in Fedora 31, we need your help to test if everything runs smoothly!

  • EPEL Bug: Bash errors on recent EL-8 systems.

    Last week, I got asked about a problem with using EPEL-8 on Oracle Enterprise Linux 8 where trying to install packages failed due to bad license file. I duplicated the problem on RHEL-8 which had not happened before some recent updates.

IBM/Red Hat: Fedora's Power Architecture Builds, WebSphere/WebLogic's Demise, Red Hat’s David Egts

Filed under
Red Hat
  • Fedora Is Beginning To Spin Workstation & Live Images For POWER

    If you are running the likes of the Raptor Blackbird for a POWER open-source desktop and wanting to run Fedora on it, currently you need to use the Fedora "server" CLI installer and from there install the desired packages for a desktop. But moving forward, Fedora is beginning to spin Workstation and Live images for PPC64LE.

    Complementing Fedora's Power Architecture images of Fedora Everything and Fedora Server, Workstation and Live images are being assembled. This is much more convenient for those wanting an IBM POWER Linux desktop thanks to the success of the Raptor Blackbird with most Linux distributions just offering the server/CLI (non-desktop) images by default for PPC64LE.

  • Are Application Servers Dying a Slow Death?

    There has been concern for nearly five years application servers are dead. Truth be told, they are not dead, but is their usage in decline? The simple answer is yes. Over the years, it appears corporate environments have decided the "return on investment" is not there when looking at Java application servers. On the surface, one might assume that the likes of WebSphere or WebLogic might be the ones in decline due to cost. Perhaps it is just affecting the proprietary choices, while their open source based derivatives are growing or remaining steady? Appears not. Whichever Java application server you choose, all of them are in a state of decline.

    Whether it be proprietary options such as WebSphere or WebLogic, or open source alternatives JBoss or Tomcat, all are in decline based on employment listings we review. However, they are not declining at the same pace. From our collection of data, WebSphere and WebLogic's decline has been more muted. The rate of reduction for each of these application servers is in the neighborhood of 25-35% over the last couple years. At the same time, the likes of JBoss and Tomcat have declined around 40-45%. Not a drastic difference, but one that still is notable.

  • Red Hat’s David Egts: Commercial Open Source Software to Drive Federal IT Modernization

    David Egts, chief technologist for Red Hat’s (NYSE: RHT) North American public sector division, advises federal agencies to adopt commercial open source software to help advance their information technology modernization efforts, GovCon Wire reported Aug. 23.

    He said Aug. 22 in an FCW thought piece that agencies should seek software vendors that are well-versed in open source technology as well as government security certifications in order to successfully modernize federal IT processes.

Red Hat: Fedora 32 and IBM's LinuxOne

Filed under
Red Hat
  • MariaDB 10.4 + PHP 7.4 Slated For Fedora 32

    This shouldn't come as much surprise, but the upcoming Fedora 32 will offer the latest "L.A.M.P." stack components.

    The proposal has already been volleyed for including PHP 7.4 in Fedora 32. PHP 7.4 is due out in November as the latest annual update to PHP7. It's too late for Fedora 31 but the timing gives plenty of room to land PHP 7.4 in Fedora 32. Read about the new features and performance improvements with PHP 7.4.

  • IBM Storage syncs new DS8900F array to z15 mainframe launch

    Endpoint security is another new capability that IBM is adding with its Z, LinuxOne and DS8900F systems. Herzog described the new functionality as a "custom handshake" to ensure that the array and the Z system know they're talking to each other, rather than any spoofed system. 

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.

Red Hat: Better Flatpak Support For Firefox, Deep dive into Virtio-networking and vhost-net, SAP

Filed under
Red Hat
  • Better Flatpak Support For Firefox Appears To Be Coming

    One of the best and most practical use-cases for sandboxed Linux apps via Flatpak or Snaps is certainly web browsers. There has been unofficial Firefox Flatpaks offered to this point but it's looking like better support for a Flatpak'ed Firefox could be coming down the pipe soon.

  • Deep dive into Virtio-networking and vhost-net

    In this post we will explain the vhost-net architecture described in the introduction, to make it clear how everything works together from a technical point of view. This is part of the series of blogs that introduces you to the realm of virtio-networking which brings together the world of virtualization and the world of networking.

    This post is intended for architects and developers who are interested in understanding what happens under the hood of the vhost-net/virtio-net architecture described in the previous blog.

    We'll start by describing how the different virtio spec standard components and shared memory regions are arranged in the hypervisor, how QEMU emulates a virtio network device and how the guest uses the open virtio specification to implement the virtualized driver for managing and communicating with that device.

    After showing you the QEMU virtio architecture we will analyze the I/O bottlenecks and limitations and we will use the host’s kernel to overcome them, reaching the vhost-net architecture presented in the overview post (link).

  • RHEL 8 Now Powers SAP Solutions

Red Hat: Flask on Red Hat Enterprise Linux, OpenShift and SAN vs. NAS

Filed under
Red Hat
Server
  • Develop with Flask and Python 3 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 the Flask microframework using the current RHEL 8 application stream version of Python 3.

    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 Django container with Buildah and run it with Podman. The code will be stored on your local machine and mapped into the container when it runs. You?ll be able to edit the code on your local machine as you would any other application. Since 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. While this approach isn?t the way to do things for production, you get the same development inner loop as you?d have when developing locally without containers. The article also shows how to use Buildah to build a production image with your completed application.

  • IBM brings Cloud Foundry and Red Hat OpenShift together

    At the Cloud Foundry Summit in The Hague, IBM today showcased its Cloud Foundry Enterprise Environment on Red Hat?s OpenShift container platform.

    For the longest time, the open-source Cloud Foundry Platform-as-a-Service ecosystem and Red Hat?s Kubernetes-centric OpenShift were mostly seen as competitors, with both tools vying for enterprise customers who want to modernize their application development and delivery platforms. But a lot of things have changed in recent times. On the technical side, Cloud Foundry started adopting Kubernetes as an option for application deployments and as a way of containerizing and running Cloud Foundry itself.

  • SAN vs. NAS: Comparing two approaches to data storage

    For a new sysadmin, storage can be one of the more confusing aspects of infrastructure. This confusion can be caused by lack of exposure to new or different technologies, often because storage needs may be managed by another team. Without a specific interest in storage, an admin might find one’s self with a number of misconceptions, questions, or concerns about how or why to implement different solutions.

    When discussing enterprise storage, two concepts are at the core of most conversations: storage area networks (SAN) and network-attached storage (NAS). Both options provide storage to clients across a network, which offers the huge benefit of removing individual servers as single points of failure. Using one of these options also reduces the cost of individual clients, as there is no longer a need to have large amounts of local storage.

Wherefore Art Thou CentOS 8?

Filed under
Red Hat

IBM's Red Hat Enterprise Linux 8 (and I'm not sure if Red Hat likes me putting IBM in front of it or not) was released on May 7th, 2019. I write this on Sept. 11th, 2019 and CentOS 8 still isn't out. RHEL 7.7 came out on August 6, 2019. In an effort to be transparent, CentOS does have wiki pages for both Building_8 and Building_7 where they enumerate the various steps they have to go through to get the final product out the door.

Up until early August they were making good progress on CentOS 8. In fact they had made it to the last step which was titled, "Release work" which had a Started date of "YYYY-MM-DD", an Ended date of "YYYY-MM-DD", and a Status "NOT STARTED YET". That was fine for a while and then almost a month had passed with the NOT STARTED YET status. If you are like me, when they completed every step but the very last, you are thinking that the GA release will be available Real-Soon-Now but after waiting a month, not so much.

Read more

Servers: "Docker Not Doomed?" and Some IBM/Red Hat Leftovers

Filed under
Red Hat
Server
  • Docker Not Doomed?

    Modern application development essentially consists of composing an application from a variety of services. These services aren't just infrastructure components that live on a server any more. They're delivered via an API and could be almost anything underneath as the abstractions start to pile up.

    COBOL code at the other end of a message bus with a lambda-function frontend? Okay. Ephemeral container running a Spring Boot service that connects to an RDBMS on a physical Unix server on the other side of the country? Sure, why not? Modern applications don't really care, because it's all about getting the job done. The name of the game is loosely-coupled modular components.

    This is why Docker has joined forces with Microsoft, Bitnami, HashiCorp, and a few others to create the Cloud Native Application Bundle (CNAB) specification. Docker uses this spec as part of its Docker App tool, which behaves a lot like docker-compose to collect a variety of services together into a single application bundle that can be shared around. It's a lot like a container collection, and brings the same easy portability of containers to composed applications.

    "[Docker App] allows you to describe not just containers, but other services around which the app is dependent," says Johnston. "And it allows you to do things that enterprises care about, such as signing the bundle, verifying that signature, and automatically promoting it based on that signature and things like that."

  • Red Hat OpenShift Service Mesh is now available: What you should know

    As Kubernetes and Linux-based infrastructure take hold in digitally transforming organizations, modern applications frequently run in a microservices architecture and therefore can have complex route requests from one service to another. With Red Hat OpenShift Service Mesh, we’ve gone beyond routing the requests between services and included tracing and visualization components that make deploying a service mesh more robust. The service mesh layer helps us simplify the connection, observability and ongoing management of every application deployed on Red Hat OpenShift, the industry’s most comprehensive enterprise Kubernetes platform.

    Red Hat OpenShift Service Mesh is available through the OpenShift Service Mesh Operator, and we encourage teams to try this out on Red Hat OpenShift 4 here.

  • Catching up with Red Hat at Sibos 2019

    Red Hat is excited to once again be attending Sibos, an annual financial services industry conference exhibition and networking event that is hosted by SWIFT. This year, the event is being held in London, England from September 23rd through 26th. Red Hat will be attending to sponsor a number of activities and discuss how and why enterprise open source technologies offer innovative capabilities that can help firms thrive in their digital journeys.

Fedora 32 Looking At Switching Firewalld From Iptables To Nftables

Filed under
Red Hat

While Fedora 31 isn't even out yet, looking ahead to the Fedora 32 release next spring is a plan to switch firewalld as Fedora's default network firewall from its existing iptables back-end to the more modern nftables back-end.

Firewalld upstream has begun defaulting to Nftables and distributions like Red Hat Enterprise Linux 8 are also using it. Now with Fedora 32 that default change-over is likely to take place to provide rule consolidation, namespaced rules support, and more software projects focusing on nftables over iptables.

Read more

Also: How to set up a TFTP server on Fedora

Server: Red Hat, Intel and SUSE

Filed under
Linux
Red Hat
Server
SUSE
  • Introduction to virtio-networking and vhost-net

    In this post we have scratched the surface of the virtio-networking ecosystem, introducing you to the basic building blocks of virtualization and networking used by virtio-networking. We have briefly covered the virtio spec and the vhost protocol, reviewed the frontend and backend architecture used for implementing the virtio interface and have taken you through the vhost-net/virtio-net architecture of vhost-net (host kernel) communicating with virtio-net (guest kernel).

    A fundamental challenge we had when trying to explain things was the historical overloading of terms. As one example, virtio-net refers both to the virtio networking device implementation in the virtio specification and also to the guest kernel front end described in the vhost-net/virtio-net architecture. We attempted to address this by explaining the context of terms and using virtio-net to only describe the guest kernel frontend.

    As will be explained in later posts, there are other implementations for the virtio spec networking device based on using DPDK and different hardware offloading techniques which are all under the umbrella of the virtio-networking.

    The next two posts are intended to provide a deeper understanding of the vhost-net/virtio-net architecture. One post will be intended for architects providing a technical deep dive into the vhost-net/virtio-net and explaining how in practice the data plane and control planes are implemented. The other post intended for developers will be a hands on session including Ansible scripts to enable experimenting with the vhost-net/virtio-net architecture.

    If you prefer high level overviews we recommend you keep an eye out for the virtio-networking and DPDK introductions, to be published in the upcoming weeks.

  • Intel Issues Second Release Of Its Rust-Written Cloud-Hypervisor For Modern Linux VMs

    Intel's open-source crew has released version 0.2 of its primarily Rust-developed Cloud Hypervisor and associated firmware also in Rust.

    The Intel Cloud Hypervisor is their experimental VMM running atop KVM designed for modern Linux distributions and VirtIO para-virtualized devices without any legacy device support.

  • Announcing SUSE CaaS Platform 4

    SUSE CaaS Platform 4 raises the bar for robust Kubernetes platform operations with enhancements that expand platform scalability options, strengthen application security, and make it easier to keep pace with technology advancements. Integrating the latest releases of Kubernetes and SUSE Linux Enterprise, SUSE CaaS Platform 4 continues to provide industry leading application delivery capabilities as an enterprise-ready solution.

  • A new era in Cloud Native Application Delivery is here
  • 3 Infrastructure Compliance Best Practices for DevOps

    For most IT organizations, the need for compliance goes without saying. Internal corporate policies and external regulations like HIPAA and Sarbanes Oxley require compliance. Businesses in heavily regulated industries like healthcare, financial services, and public service are among those with the greatest need for strong compliance programs.

Syndicate content