Please login to post comment


  • Amruta Bhaskar
  • Jan 20, 2020
  • 0 comment(s)


Open Shift is a clan of containerization software developed by Red Hat. Open shift container is the leading product platform an on-premises platform as a service built around Dockers containers, it is arranged and managed by Kubernetes on a foundation of Red Hat Enterprises Linux with full-stack automated operations to manage hybrid cloud and multi-cloud placements and gives you tools like a web console and CLI to manage features like load balancing and horizontal scaling. It simplifies operations and development for cloud-native applications.

The family’s other products provide this platform through different environments such as OKD that serves as the community-driven upstream, Open Shift Online is the platform offered as software as a service, and Open Shift dedication is the platform offered as a managed service. That is optimized to improve developer productivity and endorse innovation.


Open Shift is a PaaS. Gartner calls Open Shift is a Cloud-Enabled Application Platform (CEAP). Service as a platform or service as an application the platform is a category of cloud computing service that provides a platform permitting customers to develop, run, and manage applications without the difficulty of building and maintaining the infrastructure typically associated with developing and launching an app.

Open Shift uses Red Hat Enterprises Linux and its Security-Enhanced Linux subsystem as its foundation. It supports many languages for easiness of development, including Java, PHP, Python, Ruby, Perl, and Node.js.


Open Shift originally came from Red Hat’s achievement of Makara, a company with a brand PaaS solution based on Linux containers. Even though Open Shift is announced in May 2011, it was propriety technology that did not become open-source until May 2012. Until the v3, the container technology used custom-developed technologies. This altered in v3 by the adoption of Dockers as the container technology and Kubernetes as the container orchestration technology. The v4 product has multiple architectural changes – a prominent one being a shift to using CRIO as the container runtime, and Buildah as the container build tool, thus breaking the exclusive dependency on Dockers.


With S2I (Source-to-image), developers can quickly and easily create applications and deploy them, a developer can even develop his code without creating a container first. Operators can influence placement and policy to arrange environments that meet their best practices. It makes your development and operations work smoothly together when joining them in a single platform.


Since Polyglot, Multi-language deploys Dockers containers, it gives the ability to run many languages, frameworks, and databases on the same platform. By this, it can easily deploy microservices written in Java, Python or other languages.


In build automation, Open Shift automates the process of building new container Images for all of the users. It can run standard Dockers builds based on the Dockers files you provide and it also provides a “Source-to-image” a feature which allows specifying the source from which to create your images. This allows the administrator to control a set of base or “builder images” and then users can cover on top of these. The build source could be a Git location, it could also be a dual like a WAR/JAR file. Users can also modify the build process and create their own S2I images.


In Deployment automation, Open Shift automates the deployment of application containers. It supports rolling developments for multi-containers apps and allows to roll back to an older version.


Its Continuous integration Open Shift provides built-in continuous integration capabilities with Jenkins and it can also tie into your existing CI solutions. The Open Shift Jenkins image can also be used to run Jenkins masters and slaves on Open Shift.


There are many versions of Open Shift, spoiler which is based on Open Shift Origin. Origin provides an Open Source application container platform. All sources code for the Origin project is available under the Apache License (Version 2.0) on GitHub.


It is benefited for a developer to push code to build and run on Open Shift through their software version control solution or Open Shift can be integrated with a developer’s own automated build and continuous integration/continuous deployment system. Here S2I will be useful. It is benefited in Open Shift orchestrates where application containers will run and manages the application to ensure it’s available for end-users. It benefited in managing the app running in the cloud that can monitor, debug, and tune on the fly.


On a deeper look focusing on infrastructure, Open Shift run on any choice such as physical, virtual, public. It uses a Software-Defined-Networking approach to provide a unified cluster network that enables the communication between pods across the Open Shift cluster. This pod network is established and maintained by the Open Shift that configures on overlay network using OpenvSwitch (OvS). The OVS-subnet plug-in is the original plug-in which provides a “flat” pod network where every pod can interconnect with each pod and service.


Managing storage in persistent storage is a different problem from managing to compute resources. Open Shift Origin influences the Kubernetes Persistent Volume framework that allows administrators to provision persistent storage for a cluster. Developers can request PV resources without specific knowledge of the basic storage infrastructure by using Persistent Volume Claims (PVCs), PVCs are specific to a project that is created and used by developers as a means to use a PV, these resources on their own are not scoped to any single project it can be shared across the whole Open Shift Origin cluster and it can be claimed for any project.


Please login to post comment

( 0 ) comment(s)