Red Hat - Rondea

Red Hat Enterprise Linux for free: Red Hat's revolution starts with 16 servers

Red Hat announced free availability Red Hat Enterprise Linux for all holders of a Red Hat account, with a limit of 16 server on which you can install this free version. A change following the divestment of CentOS

by Riccardo Robecchi published 21 January 2021 , at 12: 21 in the Device channel

Red Hat Linux

About a month after the announcement of the end of CentOS 8, Red Hat has announced that it will provide a completely free version of Red Hat Enterprise Linux (RHEL), valid for installation and use on up to 16 devices in production. Red Hat therefore somehow completely replaces CentOS with RHEL, albeit only in those environments that require the use of a few machines. This is a major change of pace for the American company.

Red Hat Enterprise Linux goes free (up to a 16 systems)

Red Hat decides to create a second twist after lowering the curtain on the CentOS project as we have always known it: it was in fact a revival of RHEL without the Red Hat brand, which allowed anyone to have access to such software without having to pay for licenses; the lack of contributions and support from the companies that used it led to the closure of the project.

The company has now announced on its blog that Red Hat Enterprise Linux will be available free of charge to all subscribers of the Red Hat Developer Network, which has no purchase costs or obligations. The only limitation introduced lies in the number of production systems on which distribution can be installed: the maximum ceiling is in fact set at 16 systems . This is a large enough number to satisfy the needs of individuals who want to experiment with RHEL and small businesses.

“It’s exactly what it sounds like: for small production use cases, it’s a no cost, no support RHEL. You just need to log in with a free Red Hat account (or using a GitHub account, Twiter, Facebook or other) to download RHEL and receive updates. Nothing else is required “, writes the company in the ad. “This is not a sales program and no salesperson will contact you to try to make a sale. There will be an option to subscribe to full support, but it’s up to you to decide. “

There are also no limits on where you can run the software: you can install this free version of RHEL on AWS, Google Cloud and Microsoft Azure , for example.

Red Hat claims to be aware that this new feature does not cover all possible use cases that it covered CentOS and will then provide new updates in mid-February. The free version of Red Hat Enterprise Linux will be available starting February 1st .

Java framework Quarkus 1.11 introduces RESTEasy Reactive and new Dev UI

The Java framework Quarkus, which was launched under the slogan “Supersonic Subatomic Java” 62 and supported by Red Hat, has been offering JAX-RS-2.1 since then -Implementation RESTEasy, with which HTTP endpoints can be defined. Quarkus 1. 11 now goes one step further and implements RESTEasy Reactive, which offers reactive extensions that go beyond the scope of the JAX-RS-2.1 specification . The RESTEasy-Reactive integration developed in the JBoss project is initially tailored primarily to Quarkus and is based on its vert.x layer in order to be completely reactive.

More speed The RESTEasy-Reactive that was announced experimentally at the end of the year 2020 -Integration is now available to all users of the open source framework with the release of Quarkus 1. 11. As an alternative to Quarkus’ Reactive Routes API, RESTEasy Reactive is intended to open up a way that many Java developers are familiar with to further optimize the performance of their applications. According to the Quarkus development team, it should not be possible to increase the maximum achievable throughput of an application, and start times and memory requirements should also be lower. In addition, typical framework tasks such as scanning annotations or creating metamodels can be done during the build. Further details on RESTEasy Reactive can be found in the implementation documentation.

Expandable developer console With a redesigned console for developer mode, Quarkus developers are to make their work even easier and clearer. The new Dev UI can be flexibly set up to keep an eye on the functions of various extensions of the framework. The range of possibilities ranges from simply listing the CDI beans and endpoints to repeating Flyway migrations and deployments on OpenShift. Quarkus 1. 11 now introduces the technical foundation with a basic set of extensions. In order to gradually expand the Dev Console with further extensions, the support of developers is expressly desired. If you want to contribute your own extensions to the open source framework, you will find valuable information in the Dev UI Guide.

Among the other new features in Quarkus 1. 11 are worth mentioning the improved support for micrometers. Metrics from Kafka streams can now be displayed and the Prometheus registry has been integrated into the core extension. Further registries such as Azure Monitor, Datadog, JMX, SignalFX, Stackdriver and StatsD will be hosted in the extensions on Quarkiverse in the future.

The Quarkus team has also expanded the shell scripting with jbang. The deeper integration of jbang allows the activation of the development mode and the use of Quarkus platforms (BOM) for version management. The prerequisite for this, however, is at least version jbang v0. 62. All other improvements and new functions are summarized in the blog post about the release of Quarkus 1. 11.

(map)

Free RHEL instead of CentOS

With two changes to the RHEL licensing, Red Hat probably wants to defuse its discontinuation of CentOS somewhat. On the one hand, the provider is expanding its developer program, with which individual developers can equip up to 16 systems with RHEL in the future. These can be used for test purposes, but it can also explicitly refer to systems that are in productive use are free. However, you must register with Red Hat with your own account or single sign-on with a third-party account. Support from Red Hat is not included; The provider also promises not to abuse the users of the program as an opportunity for sales.

Developer program for the entire department Furthermore, complete teams can be added to the developer program in the future, which also does not incur any additional costs and does not limit the options that can be selected. Systems at providers such as Amazon AWS or Microsoft Azure can also be equipped with the free RHEL via Red Hat Cloud Access.

The changes to the developer program are taking effect February 1st. In the announcement, Red Hat also promises to introduce additional programs for previous CentOS applications in mid-February. The regular CentOS will take its leave at the end of 2021, shortly after the step became known, CloudLinux announced a RHEL-compatible alternative.

(fo)

Union: IBM Germany is planning almost 1,000 layoffs

In Germany, IBM will give almost 1000 employees the termination. The group has informed its supervisory boards and the responsible works council committees accordingly in the last few days with maintaining competitiveness and realigning the organization and skills. This was announced by the service union ver.di. In order to implement the layoffs, negotiations on redundancy plans are to be started with the responsible bodies of the companies belonging to the German IBM group . It is also still unclear which parts of the group are affected.

Restructuring and profits Last autumn, IBM expanded its infrastructure Services split off into a new company in order to focus even more on cloud services. In this area, IBM 2018 had the open source provider Red Hat converted for 30 Billion euros taken over. Red Hat is now part of the Cloud & Cognitive Services division. Here IBM was able to record a growth in turnover, while the income of the other services declined. Nevertheless, in the third quarter 2020, IBM was still able to post slightly increasing profits of 1.7 billion US dollars, the equivalent of almost 1.4 billion euros.

IBM CEO Arvind Krishna announced a growth target of five percent for the group in October. To this end, IBM wants to further develop its strategies and implement measures to simplify and improve the business model.

Worldwide, IBM has around 350. 000 Employees, in Germany the number of positions is over 10.000 estimated. The ver.di union protests against the layoffs and calls on IBM not to implement the plans. Information events and protests are being planned.

(fds)

CloudLinux announces AlmaLinux, to pick up the CentOS legacy

Farewell to CentOS as a version free and community driven by Red Hat Enterprise Linux has upset the balance of the market. A void that is filled by other distributions such as AlmaLinux

by Riccardo Robecchi published 19 January 2021 , at 08: 01 in the Innovation channel

Linux

With the CentOS project that has profoundly changed its role within the ecosystem Red Hat , becoming the place where changes are introduced that will end up in Red Hat Enterprise Linux rather than being a “copy” free of the same, there are numerous attempts to create a substitute who knows how to offer the same type of experience. The latest announcement comes from CloudLinux , who announced the launch of their project AlmaLinux .

AlmaLinux announced, a fork of Red Hat Enterprise Linux to replace CentOS

CloudLinux is a company that produces the homonymous Linux distribution based on CentOS designed for hosting service providers and therefore depends on the latter distribution. With the official announcement of the end of the traditional CentOS model, however, CloudLinux has had to take its fate more decisively and has therefore announced that it will itself take care of creating the free fork of Red Hat Enterprise Linux on which to base. your own CloudLinux distribution.

The intent is to provide a perfect replacement for CentOS , so that there is no need to make changes to the software or system to achieve compatibility. The AlmaLinux base will be Red Hat Enterprise Linux 8 , with a support period that will extend at least until 2029 . CloudLinux plans to implement a migration path to AlmaLinux from CentOS that is clear and direct, so as not to have to make substantial changes to their systems to move to the new distribution.

The launch is expected in the first quarter of 2021, as explained in the company’s blog.

CentOS clone Project Lenix becomes AlmaLinux

According to the manufacturer CloudLinux, the RHEL-based operating system will appear in the first quarter 2021.

The CentOS alternative developed under the working title Project Lenix is now called AlmaLinux and will be released as planned by March 2021. The distribution, which is binary-compatible with Red Hat Enterprise Linux (RHEL), comes from CloudLinux Inc., which markets a distribution especially for hosting providers with the CentOS-based CloudLinux OS.

CentOS was 2004 started as a community project of a RHEL-compatible Linux distribution. Red Hat provides the RHEL source packages free of charge under the GPL. 2014 CentOS and Red Hat merged. Since then, every new RHEL version has been followed by a CentOS version without proprietary content and certified security policies from Red Hat.

End 2020 Red Hat announced the end of the previous CentOS. In addition to Project Lenix, alias AlmaLinux, Rocky Linux also succeeds CentOS. Rocky Linux comes from Gregory Kurtzer, the founder of the CentOS project. A release date for Rocky Linux has not yet been set.

(un)

Sysdig observed a shift left at Container Security

The platform provider Sysdig, which focuses on Secure DevOps, has presented its annual “Container Security and Usage Report” for the fourth time. In the output for 2021, Sysdig comes to the conclusion that more and more users are attaching greater importance to security and monitoring. Almost three-quarters (74 percent) of the DevOps teams surveyed scan their container images early in the build process of their CI / CD pipelines even before deployment. According to Sysdig, Container Security is performing a clear shift left.

Insights into productive container deployments The findings presented in the report are based on the analysis of data from around 2 million container deployments by Sysdig customers. This is only a subset of the containers running daily in Sysdig accounts. In addition, the provider also included publicly accessible data from container deployments at GitHub, Docker Hub and the Cloud Native Computing Foundation (CNCF). In addition to the welcome trend towards a shift left, the data also reveal persistent security problems – especially with regard to the rights settings for containers: In 58 Percent of the examined cases, the images run with root privileges.

Thus, almost two thirds of the examined containers are susceptible to being compromised during runtime. According to Sysdig, the fact that DevOps teams apparently do not shy away from this risk has to do with the fact that many people consider rapid deployment more important. The associated dangers are also put into perspective when looking at the average lifespan of container images. Almost half of all examined images come to runtimes of less than five minutes, not even 20 percent run a day or longer. On the one hand, the very short Lifespan cycles keep the risk of attack low, but also make comprehensive monitoring of the container images during runtime more difficult.

Docker Runtime is becoming less important Sysdig has identified another important trend in the use of container runtimes and registries. Not only since Kubernetes wanted to discontinue support for Docker as a runtime environment, its popularity has suffered. Sysdig users are also increasingly turning to the alternatives Containerd and cri-o. According to the report, Docker Runtime is only used by 36 percent, the shares of Containerd and cri-o have doubled compared to the previous year 33 or 17 percent. It should be noted, however, that Docker is also internally based on Containerd and at least prefer platforms such as Red Hat OpenShift cri-o.

Prefer Sysdig users More and more often the container runtimes Containerd and cri-o compared to Docker.

(Image: Sysdig)

For the container registries for hosting and managing images, Docker still the top position (33 percent), according to Sysdig, competing offers such as Google Cloud Registry (GCP) and Quay are found but increasingly frequent use. GCP with a share of 26 percent is the most important public cloud repository. Quay recorded an increase from to 24 Percent the greatest growth.

The Container Security and Usage Report 2021 also provides other interesting insights into the operative container environments of Sysdig users, for example the use of monitoring and security tools such as Prometheus or the Falco, which Sysdig has handed over to the CNCF. The full report is available for free download on the company website.

(map)

Relocation complete: The Eclipse Foundation is now officially European

As announced, the Eclipse Foundation has moved its legal headquarters to Europe. To this end, it founded the Eclipse Foundation AISBL (Association internationale sans but lucratif), which is known in German as an international non-profit association (IVoG), a legal form used in Belgium for non-profit organizations. Now the foundation has completed all the formalities for the move.

The managing director of the Eclipse Foundation Mike Milinkovich describes in a blog post that since May 2020 Planned move as a labor-intensive process. The first step has been taken with the official establishment of the AISBL, but further tasks await the members and those who contribute to the open source projects.

Strong in Europe According to Milinkovich, the Eclipse Foundation is the largest open source foundation in Europe in terms of employees, projects, developers and members. Total 170 members and over 900 Contributors come from European countries.

Europe has traditionally been a strong region for the Eclipse Foundation.

(Image: Eclipse Foundation)

Numerous large European and specifically German companies are founding members of the Eclipse Foundation AISBL, including Bosch, Daimler TSS and SAP. In addition, the European Commission considers Milinkovich’s open source initiatives to be strategically important for digital and industrial transformation.

Since the beginning, the Eclipse Foundation has been based in North America, despite its many European members. At the time of the announcement of the move, there was talk of 18 percent. The changes in the events for the community were gradual: the European EclipseCon overtook its formerly big US sister over the years. The latter eventually disappeared from the scene, while the EclipseCon still exists.

From the line of fire of the trade war The European establishment has the advantage for the Eclipse Foundation that it is not under direct US influence. This puts it outside the firing line of the trade war between the USA and China that has escalated in recent years. The members of the foundation include the Chinese company Huawei, which is the focus of the dispute. The move to Europe will secure the multi-faceted growth of the Eclipse Foundation in the long term, which, according to Milinkovich, last year 60 have joined new members.

The move of the Foundation’s corporate governance to Europe entails some organizational and legal changes. The European legal entity will now take control of the names, trademarks and brands. In future, membership fees will also be billed in euros.

However, this does not mean that the Eclipse Foundation is withdrawing from the USA. The Eclipse Foundation Inc. in the US state of Delaware remains in existence under the legal guidelines there. The move also does not affect the daily work that should be distributed across the Canadian and European branches.

For those who work on Eclipse projects, little should change initially. In the FAQ on the move, it says “The short version is: Continue as before. In the short term, it will remain business as usual for commiters and contributors of Eclipse projects.” However, as part of the move, the Foundation set up resources for development with GitLab in Europe, and according to the FAQ, those responsible are welcome to migrate their projects to it at any time.

(Image: Eclipse Foundation)

The Eclipse Foundation was founded 2001 and was previously headquartered in Ottawa, Canada. The history goes back three years further: 900 IBM started together with a consortium of software providers such as Red Hat, SuSE and Borland the Eclipse IT project.

The foundation, which welcomes both companies and individuals, was created with the aim of creating a vendor-independent community. The projects are publicly available under the Eclipse Public License

One of the well-known projects is the Eclipse IDE. In the last few years there has been a strong increase in the enterprise Java environment. The Java EE successor Jakarta EE is under the umbrella of the foundation, and Eclipse MicroProfile is primarily aimed at the development of microservices. The OSGi Alliance recently handed over its work to the Foundation. In addition, the Foundation is traditionally well positioned in the Internet of Things (IoT) sector.

Overall, there are currently 18 Working groups for the individual areas.

More details about the move can be found in the Eclipse blog and the FAQ as well as a presentation on the Eclipse Foundation AISBL in PDF format. In addition, the Foundation has published a white paper on digital transformation in Europe through global open source collaboration.

(rme)

More security for OpenShift: Red Hat wants to take over StackRox

In the future, StackRox will belong to Red Hat, with the planned takeover of the Kubernetes security provider, the software manufacturer primarily wants to strengthen its OpenShift. The latter is Red Hat’s cloud management platform, which combines a Kubernetes distribution with other services and support for corporate use.

Red Hat wants to integrate the StackRox software into OpenShift, but the announcement of the takeover remains vague here: users should be able to enforce their security guidelines in every phase of the life cycle of an application, the tools for this should be available natively in OpenShift in the future. At the same time, both companies promise to continue to offer the StackRox services for other Kubernetes platforms such as Amazon’s Elastic Kubernetes Service (EKS), Microsoft’s Azure Kubernetes Service (AKS) and the Google Kubernetes Engine (GKE).

Red Hat plans to complete the takeover in the first quarter 2021. All information available can be found in the announcements from Red Hat and StackRox. The competition is also currently strengthening its Kubernetes portfolio with acquisitions: Last year, SUSE bought Rancher Labs, VMware Octarine and Veeam Kasten.

Why Reactive: Reactive Architectures and their History

What do Rammstein tickets, Baukindergeld and SV Werder Bremen jerseys have in common? All three were so popular that the respective websites for booking tickets, applying for funding and ordering bibs collapsed within a very short time due to the influx of visitors.

In addition to the anger and disappointment of customers and citizens and the associated loss of reputation for the providers, such failures – caused by excessive traffic – are usually also associated with massive financial losses. In some business models and application scenarios, they would be downright fatal: streaming services such as Netflix and Spotify, IoT networks in smart cities and autonomous vehicles are essentially dependent on the systems on which they are based remain operational under all circumstances, regardless of the amount of data and the required performance.

Recently, Netflix published a post-mortem on a callback problem in the software architecture: In general, the callback came after 15 Milliseconds, but not always. Occasionally it took significantly longer, which led to problems when playing. The Android scheduler framework had a callback of 15 milliseconds requested – however, this only means that the callback is at least 15 May need milliseconds (not at most, but at least, as security expert Felix von Leitner explains in a blog post). The bug might have been avoidable through a different software design. The Reactive Manifesto was created 27 from the cooperation of the companies Netflix, Pivotal and Red Hat. Since then around 27. 000 Developers signed the manifesto, and almost all Reactive publications refer to it. It defines values, non-functional requirements and principles that stand for a reactive architecture (see Fig. 1).

Reactive architectures penetrate ever more deeply into software applications that describe the goals and intentions of this type of architecture this policy paper. However, at first glance it does not seem to provide any new information. It is worth taking a look at the historical development of the architectural styles in order to better understand the concept.

Values, requirements and principles of the Reactive Manifesto (Fig. 1)

(Image: msg Group)

According to the manifesto, the most important value is responsiveness, the fast and reliable response behavior of reactive applications. Elasticity and resilience (both non-functional requirements) should lead to this behavior: Elasticity stands for dynamic scaling depending on the load behavior, and resilience for recognizing failures and correcting them independently.

The load behavior can be different. Sometimes it is access by users from the Internet, sometimes it is the sending of MQTT messages from an IoT device. For example, the elasticity in a microservices architecture can be achieved by adding microservice instances when the load increases and exiting them again when the load decreases. Resilience can be achieved in a microservices architecture by providing multiple microservice instances redundantly so that in the event of a failure another instance can take over the tasks. The system automatically detects the error and restarts the microservice instance so that it can take over the tasks again. Asynchronous communication via messaging should meet these requirements.

Red Hat opens Kuberntes for Windows containers

With the Windows Machine Config Operator (WMCO), Red Hat is introducing Windows container support into its Kubernetes distribution OpenShift, creating a common Kubernetes basis for Windows and Linux container workloads. Until now, only Linux applications could be containerized, Windows applications had to run in VMs that were integrated into the OpenShift Container Platform (OCP) via the virtualization layer.

With OpenShift 4.6, Windows applications that were created in Visual Studio or Visual Studio Code can now also be containerized and executed in OpenShift. However, this is currently limited to OCP on Azure and OCP on AWS. Support in OCP on vSphere, on Bare Metal, on Red Hat Virtualization, on Red Hat OpenStack Platform and managed OpenShift offerings such as Azure RH OpenShift and OpenShift Dedicated is to follow.

Largely automated The Windows Machine Config Operator is a prerequisite for containerized Windows applications on OpenShift. The certified OpenShift operator is based on the Kubernetes Operator Framework and, according to Red Hat, is also supported by Microsoft. Administrators can access the WMCO via the Operator Hub in order to integrate and manage their Windows containers in Kubernetes via the OpenShift console.

The WMCO configures Windows VMs as working nodes for the Kubernetes cluster on which the Windows container workloads can then run. To do this, the administrator creates a MachineSet that uses a Windows image with the Docker container runtime installed. The operator then searches for machines with the designation machine.openshift.io/os-id: Windows . In future versions, Windows containers will also have the newer containerd format preferred by Kubernetes.

A detailed guide to containerizing Windows applications under OpenShift 4.6 can be found in Red Hat’s OpenShift blog.

(sun)

heise + | Fedora 33 in the test: New specifications with Btrfs, Systemd-Resolved and zRAM

The decision, from Fedora 33 Using Btrfs as the standard file system for the desktop versions caused a certain stir: Fedora sponsor Red Hat had the promising file system in its Enterprise Linux (RHEL) and instead relies on XFS supplemented by the storage management software Stratis. The choice in favor of Btrfs came from the community and should not be misinterpreted as a rethink at Red Hat. Red Hat developers again initiated the inclusion of Stratis 2.1 in Fedora 33.

Up to now, Btrfs could be selected for the system partition during the installation, but this had to be set up manually. That was cumbersome with the traditionally poor partitioner built into the Fedora installer. Fedora set up two subvolumes for the system partition ( / ) and user directories ( / home ) on our test computers and an Ext4 partition for / boot .

Apart from the subvolumes, Fedora does not yet use any of the Btrfs features like snapshots or compression. OpenSUSE has long since made progress, using Btrfs snapshots for a rollback function integrated in the Grub boot menu.

Access to all contents of heise + exclusive tests, advice & background: independent, critically well-founded c’t, iX, Technology Review, Mac & i, Make, c’t Read photography directly in the browser register once – on all devices read – can be canceled monthly first month free, then monthly 9 , 95 € Weekly newsletter with personal reading recommendations from the editor-in-chief Start FREE month Start the FREE month now heise + already subscribed?

After the end of CentOS: CloudLinux invests in CentOS clone

After Red Hat discontinued the free RHEL clone CentOS in its current form, alternatives for CentOS users are increasingly emerging. CentOS co-founder Greg Kurtzer quickly started a new RHEL clone called Rocky Linux as a community project, which, like CentOS, is to follow the release frequency of Red Hat Enterprise Linux.

Now CloudLinux Inc., developer of the CentOS-based CloudLinux OS for shared hosting providers, has also announced a free RHEL clone. Project Lenix is said to be in the first quarter as free, open source and at 100 percent Binary compatible community distribution with RHEL 8 will be published.

Migration without downtime You would like your own developers and resources as well as the Invest many years of experience in maintaining your own RHEL clone. Last but not least, CLoudLinux expects more visibility for its own commercial Linux distribution. Current CentOS users are promised an easy changeover to Lenix without downtime. The company has already developed a technology for updating without rebooting for its own CloudLinux.

CentOS started 2004 as a community project , which creates a RHEL-compatible Linux distribution from the freely available RHEL source packages, which Red Hat provides free of charge under the GPL. The compiled Red Hat Enterprise Linux is only available as a subscription to paying customers. 2014 CentOS and Red Hat merged. Since then, every new RHEL version has been followed by a CentOS version that dispenses with trademarked content and certified security policies from Red Hat. CentOS offers the stability and features of Red Hat Enterprise Linux, but can be used on any number of computers without a subscription.

(odi)

Gaia-X: Big US hyperscalers want to get involved in the EU cloud

Gaia-X should become an interoperable European alternative to cloud services from IT giants such as Amazon, Alibaba, Google or Microsoft. But most of the Americans in particular immediately expressed interest in participating and are now all on board at least as partners and members of technical working groups.

At the two-day digital “Gaia-X Summit”, all representatives of the US corporations emphasized on Thursday that they play an important role in the European cloud initiative and that values such as data protection, interoperability, trust, transparency and openness are clearly committed want to fully support free software.

“We believe in open source and an open cloud”, underlined Wieland Holfelder, head of Google’s Munich development center. Many customers are very concerned about a lock-in effect. The participation in Gaia-X will help to dispel these fears and to build the “next generation of the data infrastructure”. In addition to technical components, Google will provide easily implementable standards of behavior for the General Data Protection Regulation (GDPR). To enable “trustworthy data processing”, customers could save their cryptographic access codes outside of the cloud. Also in the interest of a stronger involvement with Gaia-X, the group has also agreed on a cooperation with the French provider OVHcloud.

“Natural partner” IBM Hillery Hunter, chief technologist of IBM’s cloud division, recommended her company as a “natural partner in the area of digital sovereignty”. It has been investing in open source for over 20 years and took over the pioneer Red Hat last year. For them there is no question: “We have to ensure interoperability and avoid lock-in effects in order to support the export-oriented European economy.” Users should “have complete control over their data”.

Casper Klynge, Microsoft’s “Foreign Minister” in Europe, described Gaia-X as a “catalyst for a competitive European Economy”. Microsoft has long relied on partnerships with local providers with the exchange of know-how and share the vision of a free flow of data across borders. Microsoft respects European values and rules and has supported the GDPR from the beginning.

IBM Cloud for Telecommunications, an open ecosystem for the transformation of the telco market

IBM Cloud for Telecommunications may already count on 35 partners, including companies of the caliber of Nokia, Samsung and Cisco. The purpose of the platform is to make the most of the potential of 5G both in the consumer and professional fields

of Alberto Falchi published on 09 November 2020 , at 17: 03 in the Cloud channel

IBM Nokia Cisco 5G

IBM opens its cloud to telcos with IBM Cloud for Telecommunications, an open platform designed to accelerate business transformation in the telecommunications sector, which will allow companies that adopt it to offer their customers new digital experiences and at the same time modernize their corporate infrastructure and the applications that rely on it.

IBM Cloud for Telecommunications, to exploit the full potential of 5G

The spread of 5G will completely revolutionize the business of many companies, especially those operating in the telco sector. This is mainly due to the virtualization that underlies these networks, which allows the creation of new services that leverage data. The new IBM platform will allow these companies to be able to count on the scalability and flexibility necessary to face new business challenges. It is based on Red Hat OpenShift and the support of numerous partners, who will provide the software and hardware needed to face the revolution, and includes the IBM Cloud Satellite services , which allow you to run the services IBM Cloud where you want it: in the cloud, on premises or at the edge. IBM Edge Application Manager and IBM Telco Network Cloud Manager will help speed up the delivery of new services and automate processes through AI while containing infrastructure costs.

According to IBM, the new platform allows to accelerate the development of new services by 33% , reduce downtime by 95% and improve productivity by 37%. Currently, the ecosystem has 35 partners, among which names such as Nokia, Cisco , Intel, Samsung, Juniper, Dell, Palo Alto and many others: the complete list is available at this address.

“ We are proud to partner with IBM to develop leading-edge 5G solutions in the telecommunications industry , with Red Hat OpenShift. Customer service providers will benefit from a new opportunity to quickly and efficiently deploy private 5G networks “- stated Jane Rygaard, Head of Edge Cloud at Nokia -” The shift to 5G will be crucial for companies wishing to complete digital transformation plans. And having multiple cloud-based solutions will help the sector to lay the foundations for further progress “.

“ Cisco is proud to make its industry-leading data processing solutions available to IBM Cloud for Telecommunications , security and Service Provider “- stated Keith Dyer, VP for IBM Strategic Alliance – “ We are pleased to expand our 20-year partnership with IBM and to bring the potential of our joint solutions to our common customers “.