Red Hat Product Director reviews the development of the container with PaaS

Author: Daniel Riek, Red Hat's product manager, has more than 17 years of experience in software development and open source work. The article reviews the entire development process of OpenShift and describes some of the opportunities and challenges that OpenShift has encountered from 2011 to the present. Although a bit soft, but also a comprehensive combing PaaS years of the situation, as well as the combination with the container.

@Container container technology conference will be held in Beijing on January 24, 2016, from Huawei, CoreOS, Red Hat, SAE, NetEase honeycomb, seven cattle, love art, microblogging, Tencent, where the network, Jingdong, Mushroom Street, Hewlett-Packard, Rampage comics, sound network, collar cloud and other well-known company's technical staff will share their container application case.

It is nearly a year, but also to the review and summary of the time. The past year has a special meaning for container ecosystems, so thanks to RedHat and OpenShift. RedHat performed well in 2015; for OpenShift, 2015 is a turning point in terms of the product itself and the market.


OpenShift is Red Hat's open source PaaS cloud platform software, released in the spring of 2011 , along with Cloud Foundry (at the same time) to provide Platform-as-a-Service (PaaS) solution. At that time, the early PaaS field was dominated by Heroku, GAE and some other PaaS products. OpenShift and CF provide open cloud solutions to enterprise users in an open source way, which can run on laptops, data centers, or public clouds. With the expansion of the surrounding eco-environment, new competitors to join, customers can benefit from more choices.

By the spring of 2013, developers developed new applications and commercial solutions OpenShift Enterprise (which Red Hat had run private PaaS platform in its data center through its own software) and OpenShift Online (Red Hat's deployment of PaaS services in public clouds) Of the release, Red Hat was a great success. This trend is demonstrated by community developers and early business users. CF saw the same trend later this year, VMware acquired Pivotal as an independent operating company, focused on the PaaS field.

Turning point

There were some important things to happen in the spring of 2013, and on March 21, Solomon Hykes of dotCloud for the first time demonstrated the Docker technology at PyCon. Docker provides a new way to run applications in Linux containers. Container technology itself is no stranger, in fact OpenShift, CF, dotCloud and other PaaS platform core is based on container technology, container technology can be traced back to 2000. But at Red Hat, the product team realized that Docker could help standardize container application packaging and deployment, and see the potential of the fast-growing Docker ecosystem; therefore, RedHat announced that Docker was embedded in RHEL in September and completely rebuilt OpenShift.

In determining the Docker standardization process, we discussed the future of the container and the problem of container scheduling extensions with Google, Twitter, and others. Google as RedHat the most important partner, has many years of experience in the use of containers. In discussing the new technology with Google, we learned that Google has a new container scheduling and clustering management technology and wants to open source, a technology that is Google and RedHat in July 2014 in the open source community released Kubernetes project.

Docker Comes to Enterprise Linux

In 2014, RedHat released RHEL7 support Docker container, also released RHEL Atomic Host, a container-based optimization of the smallest linux release. Red Hat Enterprise Linux 7 / Atomic + Docker + Kubernetes will evolve into a new OpenShift infrastructure platform. OpenShift, born in the PaaS ecosystem, is now fully evolved into a rapidly evolving container ecosystem.

At the same time, Pivotal is also busy building a new open source foundation to monitor the CF project, which appears to be based on OpenStack, which is intended to control the open source PaaS ecosystem. When the Cloud Foundry Foundation was released, OpenShift3 was in a good state, and RedHat decided not to participate. We have a blog , explain why we do not participate in one of the most interesting, industry as large as EMC, IBM, HP and other giants to participate in this new PaaS basic platform, RedHat and Docker, Google, CoreOS, etc. Innovative companies are focused on open source container ecosystems.

OpenShift 3 created

Time soon came to June 2015, OpenShift Enterprise 3 released at the RedHat Summit, when the OpenShift platform was re-transformation, completely embedded Docker and Kubernetes, and this time they have become the hottest open source project. On this basis, and then launched the OpenShift Enterprise 3.1, Atomic Enterprise Platform Public Preview and OpenShift Dedicated public cloud services.

Recent industry reports and articles have highlighted this achievement and call OpenShift Enterprise 3.1 a "typical container platform", not only Docker and Kubernetes, but also the corresponding features: including automatic image creation, automatic deployment services, applications Lifecycle management, language framework access, middleware and databases, and more. These new features enable users who use Java, Node.js, Ruby, Python, PHP and even Microsoft.NET to benefit from faster application development and deployment. The transition from PaaS to the container application platform was successfully completed.

Comparison of ecosystems

The container ecosystem in which OpenShift is located is now like a tornado, driving new technologies, new concepts and new solutions, and we believe that change is inevitable.

The PaaS ecosystem, represented by the Cloud Foundry Foundation, is dominated by several vendors, the most important of which is Pivotal, which revolves around the CF container environment, recently to support the prototype, to the Open Container Initiative RunC standard (RedHat as a maintainer in this standard). The ecosystems around the CF buildpacks package format are confronted with thousands of mirrors from the Docker Hub. The CF dispatch engine now faces not only Kubernetes' competition but also the challenges of Docker Swarm and Apache Mesos, which are now growing rapidly and providing more functionality.

The Docker ecosystem currently has more than 1200 GitHub contributors and 27,000 star projects. The Kubernetes ecosystem has nearly 600 contributors, and many users have used it as a production system scheduler. These new technologies, RedHat as one of the leaders, not only support the OpenShift, but also includes GAE and many other vendor programs. New base platforms, such as the Open Container Initiative and Cloud Native Computing Foundation (CNCF), are designed to manage these new technologies and are well run by many customers. At present it seems that any closed source products are difficult to compete with the open source environment.


OpenShift offers significant benefits from the evolution of container ecosystems, enabling OpenShift to support a wide range of enterprise applications, including stateless, cloud applications, and legacy applications, a feature that is useful for existing applications Huge traditional users, no doubt provide a more easy way to transition.

There are still many things to be perfect, we look forward to 2016, to see a lot of exciting things ready, such as OpenShift Enterprise and OpenShift Dedicated and OpenShift Online and other new version launched. Red Hat Atomic Container infrastructure platform will be in the container network, storage, enterprise services Registry, built-in ELK stack expansion log capabilities and many other usher in new progress.

Red Hat JBoss middleware team will expand support for Red Hat Mobile and Business Process Management solutions. OpenShift built-in Docker build capability will be enhanced, allowing users to create containers directly from source, binary, or existing systems; we also plan to extend container management and operations management through cloudforms to enhance the impact of OpenStack and public clouds such as Amazon, Google and Microsoft Azure Support; we will also enrich the content of OpenShift Reference Architectures, providing best practices for deployment and operation.

All in all, we firmly believe that Openshift3 will provide an optimal solution for the present and future, looking to the future, delighted.

Guten Rutsch und Frohes 2016!

Original links: Containers & PaaS: A Tale of Two Ecosystems (translated: Yang Feng)

Heads up! This alert needs your attention, but it's not super important.