Language Selection

English French German Italian Portuguese Spanish

Fedora, Red Hat and IBM

Filed under
Red Hat
  • Fedora 30 Will Get Bash 5.0 But Yum's Death Sentence Postponed To F31

    Fedora's Engineering and Steering Committee approved new work around the in-development Fedora 30. 

    Originally Fedora 29 was going to drop the old Yum package manager bits now that the DNF package manager has been in good shape for years and is largely a drop-in replacement to Yum. That didn't happen for Fedora 29 and just recently was proposed to drop Yum 3 for Fedora 30, but with that change coming in late and some tooling bits not ready in time, that has been diverted to Fedora 31. FESCo approves of dropping Yum 3 for Fedora 31 and is hoping it will be removed right after Rawhide branches for F30, giving plenty of time to fix any issues that may come up or other unexpected problems. 

  • Measuring user experience success with building blocks

    PatternFly is an open source design system used by Red Hat to maintain visual consistency and usability across the product portfolio. When the PatternFly team started work on PatternFly 4, the next major version of the system, they focused a large part of their effort on evolving the visual language. But how would users respond to the new look and feel?

    To get the raw and unfiltered feedback the team needed, Sara Chizari, a UXD user researcher, planned a reaction study with a fun twist and then headed to Red Hat Summit in San Francisco.

  • Backup partners target Red Hat Ceph Storage

    Red Hat Ceph Storage provides object, block and file data services for organizations modernizing their hybrid-cloud and data analytics infrastructures. With the release of Red Hat Ceph Storage 3.2, improved performance and functionality is driving new storage use cases in the modernized datacenter.

    In addition to data security and integrity, organizations must consider their strategy around data protection, backup and archiving. Whether you are backing up your enterprise application data as part of a disaster recovery strategy, or you are performing deep archives of sensitive records, rich media, or regulated data, Red Hat works with industry-leading backup, recovery and archiving partners to certify Ceph as a backup target for your most important data.

  • Effortless API creation with full API lifecycle using Red Hat Integration (Part 1)

    Nowadays, API development with proper lifecycle management often takes days if not weeks to get a simple API service up and running. One of the main reasons behind this is there are always way too many parties involved in the process. Plus there are hours of development and configuration.

  • Announcing Kubernetes-native self-service messaging with Red Hat AMQ Online

    Microservices architecture is taking over software development discussions everywhere. More and more companies are adapting to develop microservices as the core of their new systems. However, when going beyond the “microservices 101” googled tutorial, required services communications become more and more complex. Scalable, distributed systems, container-native microservices, and serverless functions benefit from decoupled communications to access other dependent services. Asynchronous (non-blocking) direct or brokered interaction is usually referred to as messaging.

    Managing and setting up messaging infrastructure components for development use was usually a long prerequisite task requiring several days on the project calendar. Need a queue or topic? Wait at least a couple weeks. Raise a ticket with your infrastructure operations team, grab a large cup of coffee, and pray for them to have some time to provision it. When your development team is adopting an agile approach, waiting days for infrastructure is not acceptable.

  • Settling In With IBM i For The Long Haul

    If nothing else, the IBM i platform has exhibited extraordinary longevity. One might even say legendary longevity, if you want to take its history all the way back to the System/3 minicomputer from 1969. This is the real starting point in the AS/400 family tree and this is when Big Blue, for very sound legal and technical and marketing reasons, decided to fork its products to address the unique needs of large enterprises (with the System/360 mainframe and its follow-ons) and small and medium businesses (starting with the System/3 and moving on through the System/34, System/32, System/38, and System/36 in the 1970s and early 1980s and passing through the AS/400, AS/400e, iSeries, System i, and then IBM i on Power Systems platforms.

    It has been a long run indeed, and many customers who have invested in the platform started way back then and there with the early versions of RPG and moved their applications forward and changed them as their businesses evolved and the depth and breadth of corporate computing changed, moving on up through RPG II, RPG III, RPG IV, ILE RPG, and now RPG free form. Being on this platform for even three decades makes you a relative newcomer.

More on Fedora 31

  • Fedora 31 Should Be Out Around The End of November

    While Fedora 31 was once talked about to never happen or be significantly delayed to focus on re-tooling the Linux distribution, they opted for a sane approach not to throw off the release cadence while working on low-level changes around the platform. A draft of the release schedule for Fedora 31 has now been published and it puts the release date at the end of November.

    Rather than delaying or cancelling the Fedora 31 release, it will go on like normal and the developers will need to work in their changes to the confines of their traditional six month release cadence.

  • Draft Fedora 31 schedule available

    It’s almost time for me to submit the Fedora 31 schedule to FESCo for approval. Before I do that, I’m sharing it with the community for comment. After some discussion before the end of the year, we decided not to go with an extended development cycle for Fedora 31. After getting input from teams within Fedora, I have a draft schedule available.

    The basic structure of the Fedora 31 schedule is pretty similar to the Fedora 30 schedule. You may notice some minor formatting changes due to a change in the tooling, but the milestones are similar. I did incorporate changes from different teams. Some tasks that are no longer relevant were removed. I added tasks for the Mindshare teams. And I included several upstream milestones.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Seven Concerns Open Source Should Worry About - Part 1

Not long ago, the Linux community celebrated the twenty-fifth anniversary of Linus Torvalds’ famous Internet post, and thus its birth. While Linux was not the first open source project (Richard Stallman announced his GNU Project eight years before), it soon became the poster child of a new way of collaborative development that changed not only how technology is created, but many other aspects of the world as well. Today, most critical software platforms and architectures are open source, and virtually all proprietary software is riddled with free and open source software (FOSS) as well. So, what could go wrong? Well, a lot, actually, unless we pause to think about where the potholes may emerge in the future, and how we can successfully navigate our way around them. That’s what I plan to do in a series of articles to which this is the introduction. Happily, all the potential concerns I will address can be addressed. That’s the good news. The bad news is that neither the commercial world nor the community of developers has a very good history of thinking about some types of risks that might be expensive, inconvenient, or just plain boring to manage or fix. Take security. That’s hardly a risk that’s unique to FOSS. But it is a concern that’s been around for a very long time. So long that we have a pretty compelling record of how both human and commercial nature act in response to security risks. Or, more to the point, don’t act. It would be impossible to find a single new wave of technology – and there have been very many – where security was not addressed as an after thought rather than designed in from the start. Almost always after multiple disasters had already occurred. The latest example is the Internet of Things. The IoT has been building out for going on a decade now, and none of the initial devices had any security features at all. Most of the latest devices still don’t. Some even have designed-in vulnerabilities, like factory programmed, unchangeable passwords. Other risks arise from a different type of complacency – assuming that because FOSS is “good” that it’s not possible to do anything “bad” when it’s created. That’s a dangerous attitude to have when you consider that there are increasing numbers of projects that are heavily funded by multiple head to head competitors. FOSS projects need concise antitrust policies - and then they need to follow them. Codes of Conduct, too. Other aspects of complacency relate to how effective FOSS licenses (as compared to what might be referred to as social pressures) are in a legal sense. Another is unquestioned assumption that the world will always be better with a single, dominant code base. Sometimes, competition between multiple architectures and platforms is a good thing. And while everybody wants to contribute to a rapidly expanding project that’s taking over the world, not everyone wants to do the boring maintenance work after its finished and becomes stable. If too many developers lose interest and drift away, still-crucial elements of the technology ecosystem can become dangerously vulnerable, stagnant and weak. Read more

Network Security Toolkit 30-11210

We are pleased to announce the latest NST release: "NST 30 SVN:11210". This release is based on Fedora 30 using Linux Kernel: "kernel-5.1.17-300.fc30.x86_64". This release brings the NST distribution on par with Fedora 30. Read more

Univention Corporate Server 4.4-1/Point Release UCS 4.4-1: performance improvements, app recommendations and UDM REST API Beta

There are significant performance improvements for managing the contents of the directory service via UDM, especially for application scenarios with complex structures. There have also been further minor improvements in DNS management, where the search for IP addresses is now enabled in further modules, as well as in the use of standard containers of domain controller objects. A brand new feature is the REST API for UDM, which considerably facilitates the integration of UDM with other applications. This REST API has been released as beta version for the time being. After further tests and improvements we plan to release a stable version in autumn. Read more

Proxmox VE 6.0 released!

We're excited to announce the final release of our Proxmox VE 6.0! It's based on the great Debian 10 codename "Buster" and the latest 5.0 Linux kernel, QEMU 4.0, LXC 3.1.0, ZFS 0.8.1, Ceph 14.2, Corosync 3.0, and more. This major release includes the latest Ceph Nautilus feautures and an improved Ceph management dashboard. We have updated the cluster communication stack to Corosync 3 using Kronosnet, and have a new selection widget for the network making it simple to select the correct link address in the cluster creation wizard. With ZFS 0.8.1 we have included TRIM support for SSDs and also support for native encryption with comfortable key-handling. Read more