Red Hat Cloud Enterprise Hybrid Cloud Main Product red hat cloud infrastructure OpenStack. The new version of OpenShift 4 specializes in large enterprise application architecture requirements, strengthens K8s support, and automates transportation capabilities. It will not only develop, test, deploy, or even cross-cloud, cloudy formal environment maintenance, automatically integrated to a single platform for scheduling and management red hat cloud infrastructure.
In addition to exposing its new hybrid cloud strategy, Red Hat also launched OpenShift 4, a new generation of hybrid cloud products, at this year’s user conference. It not only strengthens Kubernetes support, but also adds automatic scheduling and management capabilities to the platform. Many convenient cloud, hybrid cloud application deployment, management optimization features, and Microsoft joined forces to formally launch OpenShift service on Azure public cloud to help Red Hat pull the cloudy, hybrid cloud competition.
After 4 years, OpenShift 4 is finally officially launched.
Red Hat, an open source software giant known for its enterprise-class Linux OS, has made a name in the highly competitive hybrid cloud market in recent years by relying on the OpenShift container platform that can eat cloudy and cross-cloud as the main hybrid cloud product. . It has been revised many times, and has been released to the 3.11 version of OpenShift last year. It is currently a relatively mature hybrid cloud product on the market. After the OpenShift 3 version began to push Kubernetes, it made it popular with many companies and embraced the hybrid cloud architecture. At least 1,000 companies have adopted it today, red hat cloud infrastructure building their own hybrid cloud application environment on the platform, and many of them are large enterprises, such as US oil giant ExxonMobil, Delta Air Lines, Singapore’s largest commercial bank DBS Bank (DBS) Bank), Deutsche Bank, American chain department store Kohl’s, and Lotte Card.
In recent years, Red Hat has joined forces with public cloud industry players, especially AWS, Microsoft, IBM and other three cloud giants, rushing into the cloud Linux operating system, or the hybrid cloud service market of the enterprise cloud PaaS platform, launching the cloud version OpenShift The deployment solution makes it easy for enterprise users to package applications in a container and move various containerized applications to the public cloud platform through OpenShift. To eat the physical server, VM, private cloud, and public cloud container application market.
By taking a leading edge in the hybrid cloud market, Red Hat has recently become the target of even the most cloud-based companies such as AWS and Microsoft, and even IBM has not hesitated to buy it. It is Red Hat. This OpenShift Hybrid Cloud Ace is held in the hand.
Red Hat’s newly released enterprise version of OpenShift 4 software is also the most important revision since the launch of OpenShift 3, which is based on the container scheduling platform Kubernetes four years ago. However, only the developer preview version is released, the official version is released in June. Out. Unlike the previous edition, Kubernetes is just one of many container scheduling competitors. Paul Cormier, president of Red Hat Products and Technology, pointed out that after years, Kubernetes has won the industry standard enterprise-class container scheduling tool, and many companies are accustomed to It is used to schedule and manage container applications, even to build a microservices application architecture.
But like the emergence of Linux more than a decade ago, Paul Cormier believes that Kubernetes’ work is just getting started, especially in Kubernetes management in a formal environment, which is still a major challenge, including updates, security fixes and lifecycle management. Because when the architecture is more and more complex and needs to be managed across the cloud, “Once you make an application error, you don’t even know where this microservice or application is running”, which is why we are automating the new OpenShift 4 in the new version. s reason. He said that it is precisely to solve the problem of large-scale container cluster management that must be faced in the maintenance of the cloud after the establishment of a cloudy, hybrid cloud environment.
The new version of OpenShift 4 not only enhances Kubernetes support, but also adds automatic scheduling and management capabilities to the platform, as well as many convenient cloud, hybrid cloud application development, deployment, and management optimization features red hat cloud infrastructure.
Two key elements of container platform automation: Operators, CoreOS
Therefore, when Red Hat released version 4.0, it re-architected the OpenShift platform deployment and maintenance management method. By integrating the CoreOS technology that was last year and Red Hat CoreOS, it was combined with the Kubernetes application development. Framework Operators can be installed in an automated manner, software update, lifecycle management, etc., so that not only the development, testing, and deployment of Day 1, but also the maintenance of Day 2 formal environment, even the dimension of the cloud and cloudy environment. It can also be automatically integrated to a single platform for scheduling and management. Therefore, it can better meet the needs of large enterprise application architectures, not only to manage larger container clusters or microservice scales, but also to handle more complex container applications, such as Management of complex databases, etc. (Red hat cloud infrastructure)
The automation of this generation of container platforms has two key points. One is to integrate the K8s application development framework Operators, although Red Hat has released Operators last year, and provides technical preview testing in version 3.11, but until the 4.0 release, Red Hat After the formal integration of Operators into the enterprise-class OpenShift platform, after half a year of testing, this generation of OpenShift has been able to fully support Operators to automate container application lifecycle management.
The biggest benefit of adding operators is that the platform can now manage State Services (stateless services) and now manage State Services at the same time. For example, Web application is a non-state container application, and management is relatively simple. In contrast, the management of stateful container applications is much more complicated, such as complex database management, but in version 4.0, operators can also be used. Automatic management of management of these stateful container applications or other more complex applications, including automatic horizontal scaling, security vulnerability patching, and reset configuration red hat cloud infrastructure.
The maintenance personnel can also use the Kubernetes API to write operational knowledge and operational processes in the field, and package these expertise into the Operator software form, allowing the software to automatically perform the maintenance work and execute it on Kubernetes to facilitate the maintenance manager. Automated and scalable way to manage Kubernetes applications; for developers red hat cloud infrastructure, you can also use a more automated way to build and deploy Kubernetes applications, without the development expertise of the Kubernetes API, you can develop execution Business logic applications with scalability, upgrades, and backup capabilities. For example, Prometheus Operator, which is set up and managed by Kubernetes, or etcd Operater, which builds and manages Kubernetes clusters, allows developers and managers to implement cross-cloud management in a more automated manner.
Even for the convenience of finding and sharing Operators, Red Hat will also integrate the OperatorHub.io website, which previously provided the Kubernetes community to share Operators, into this version, which will be available to users directly on the OpenShift 4 platform. At present, the site has placed nearly 40 operators, and more than 10 categories, such as database, monitoring, network and so on. Red Hat has further launched the Operators certification service, which is an official version of the Red Hat officially certified and tested to differentiate the community version, so that the service of the partner can be more stable and deliver the software service to OpenShift. Large enterprise users with higher reliability and stability requirements are needed.
Even the installation process is much simpler. In the past, when installing OpenShift, users had to manually configure the underlying infrastructure, whether it was installed in a public cloud or in their own data center, but now, OpenShift 4 introduces a complete set of automation. Deployment and configuration solutions that cover hardware, operating systems, containers, and software applications.
Unlike OpenShift 3, which is installed manually, the OpenShift 4 preset is automatically installed. It will automatically execute the container cluster with the script program. The required configuration work, including network, machine, operating system, etc., simplifies the container cluster or micro service. Deploy and install the job. However, version 4.0 can only be used by AWS. Others such as Azure, GCP, or Red Hat OpenStack Platform, as well as bare-metal RHHI fusion architecture, will be added in subsequent releases.
Red Hat also uses this application script to automatically create an OpenShift cluster execution environment, called the Installer Provisioned Infrastructure (IPI), to distinguish another User Provisioned Infrastructure (UPI) installation. The UPI installation is managed. The user installs and maintains the OpenShift cluster resources, such as the computing unit and network configuration, OpenStack according to the configuration requirements of the cloud or data center infrastructure, thereby improving the flexibility of the platform in a specific cloud environment. However, this mode will be available in AWS, VMware, and bare metal when version 4.1 is released. Azure, GCP, and Red Hat OpenStack Platform will be available later, version 4.3.
Since the launch of the Red Hat OpenShfit hybrid cloud platform six years ago, it has been adopted by more than 1,000 companies. It has built its own hybrid cloud architecture on different platforms, such as US oil giant ExxonMobil and Delta Air Lines. , DBS Bank, Deutsche Bank, American chain department store Kohl’s, etc.
RHEL CoreOS is a lightweight RHEL 8 version
RHEL CoreOS is another key to OpenShift’s automated maintenance management. It is different from the old version. In the installation process, the new OpenShift 4 will be automatically created in addition to the new OpenShift installation tool to facilitate OpenShift deployment. The Linux host OS executed on OpenShift red hat cloud infrastructure OpenStack, which uses RHEL CoreOS as a host image file, allows OpenShift to execute the Kubernetes application on a lighter container OS. RHEL CoreOS is not only a slimmed and re-optimized version of RHEL, but also uses the latest RHEL 8 kernel and core library, so it has the security and stability features of Enterprise Linux.
By executing RHEL CoreOS, OpenShift 4 can also use the Atomic OSTree repository on Operators to update and manage different OS versions for OpenShift 4 clusters, keeping the entire container platform up to date, improving the past because of individual management and updates of Kubernetes and In RHEL, problems caused by the OpenShift platform upgrade are easily caused by inconsistent update versions. With the launch of OpenShift 4, now, through the Operators automation mechanism, Kubernetes and RHEL can be automatically updated to the latest version.
Huang Yurong, vice president of growth and emerging markets for Red Hat Asia, explained further that because OpenShift 4 embeds RHEL CoreOS, it can be combined with Operators to provide OTA online update functions similar to mobile apps. Once a critical update or new version is available, it will be notified. The user immediately obtains these updates, and even if the network is interrupted, the update packages are first loaded into the local content storage area, and after the network is restored, they are deployed through the Operators automation mechanism. It can also automatically update K8s core services and components on the platform, such as Prometheus, Grafana, Elasticsearch, and software-defined networks.
OpenShift officially supports Microsoft Azure Cloud Edition deployment plan
In addition to the enterprise version of OpenShift software, there is also a major release of the online OpenShift service. On the first day of the conference, Red Hat CEO Jim Whitehurst and Microsoft CEO Satya Nadella announced the official release of Azure Red Hat OpenShift.
In fact, as early as last year at the Red Hat Summit, Red Hat teamed up with Microsoft to publish the OpenShift container management service on Azure, but it was still a private preview, and the general company could not use it, but with the official launch of the service, For enterprises, in addition to AWS, there will be more new options in the future, you can use the Azure Cloud OpenShift service to build your own hybrid cloud application environment. However, at this stage, only the commercial version of OpenShift Container Platform, and the community’s OKD version (formerly OpenShift Origin) can be deployed on the Azure public cloud, other versions are not (red hat cloud infrastructure).
This generation of OpenShift also strengthens Knative for open source serverless application management, and Istio support for service grid technology. Red Hat also promotes KEDA serverless new project with Microsoft, allowing OpenShift to execute Microsoft serverless service Azure. Functions red hat cloud infrastructure.
In addition to Istio, the container platform further integrates tracking and management functions such as Jaeger and Kiali. More development and management of new tools, such as the new Red Hat CodeReady Workspaces, provides developers with a more complete Kubernetes application development environment with tools for building, testing, executing, and debugging applications. Used directly on the OpenShift platform.
Red Hat also revealed that it is developing OpenShift Container Storage, the next generation of software-defined storage products, which can provide common storage functions for native cloud applications, such as data encryption, replication, etc., which can also be deployed across the cloud and can handle various complex task executions, such as SQL or NoSQL database, CI/CD process, and AI and ML inference models.
Red Hat revealed that OpenShift 4.3 can also manage Windows containers.
In this year’s conference, Red Hat also revealed on the agenda of the container platform technology that it will continue to add new features and features after the official release of OpenShift 4 red hat cloud infrastructure.
Although OpenShift 4 will not be released in June this year, as early as Red Hat this year’s conference on the technical platform of the container platform, Red Hat also revealed in advance that after the official release of OpenShift 4, the plan will increase in the second half of this year. New features and updates. Judging from the latest OpenShift product roadmap revealed by Red Hat, it is expected that three versions will be released in the second half of the year, including versions 4.1, 4.2 and 4.3. First red hat cloud infrastructure, OpenShift 4 will be equipped with the new version of Kubernetes 1.15 when the 4.3 version is released, and will officially bring the Windows container into the OpenShift container platform before the end of the year.
Open to allow OpenShift to execute the Windows container, has been a lot of business users are looking forward to the new features that OpenShift can join, for enterprises that rely heavily on Microsoft Windows OS, with Windows container support, you can use OpenShift to manage Linux containers and Windows at the same time. Containers, instead of managing two sets of environments, can use the same set of resource scheduling and management methods as Linux containers to manage Windows containers, whether it is deployment or management scheduling will be more flexible red hat cloud.
Second, red hat cloud infrastructure the previous version 4.2 is to enhance the integration of OpenShift and Windows network functions, such as Open Virtual Network (OVN), and to provide automated deployment and configuration solutions in more public cloud environments, including Azure, GCP, OSP, IBM Cloud. , Alibaba Cloud, Red Hat Cloud RHV, and other bare metal.
In addition, red hat cloud infrastructure in terms of application development, in addition to strengthening the OperatorHub function and expanding the field application, for the container cluster deployment, a general hybrid cloud (UHC) cluster deployment and scheduling management method will be provided from 4.1. Finally, 4.1 and 4.2 will expand support for Serverless management, and will be able to get out of the preview test before the end of the year and launch the official version. It also includes OpenShift Pipelines workflow, Developer CLI interface and more.