Use case of Openshift
OpenShift is a family of containerization software products developed by Red Hat. Its flagship product is the OpenShift Container Platform — an on-premises platform as a service built around Docker containers orchestrated and managed by Kubernetes on a foundation of Red Hat Enterprise Linux. The family’s other products provide this platform through different environments: OKD serves as the community-driven upstream (akin to the way that Fedora is upstream of Red Hat Enterprise Linux), OpenShift Online is the platform offered as software as a service, and OpenShift Dedicated is the platform offered as a managed service.
The OpenShift Console has developer and administrator oriented views. Administrator views allow one to monitor container resources and container health, manage users, work with operators, etc. Developer views are oriented around working with application resources within a namespace. OpenShift also provides a CLI that supports a superset of the actions that the Kubernetes CLI provides.
OpenShift Container Platform has a microservices-based architecture of smaller, decoupled units that work together. It runs on top of a Kubernetes cluster, with data about the objects stored in etcd, a reliable clustered key-value store. Those services are broken down by function:
- REST APIs, which expose each of the core objects.
- Controllers, which read those APIs, apply changes to other objects, and report status or write back to the object.
Users make calls to the REST API to change the state of the system. Controllers use the REST API to read the user’s desired state, and then try to bring the other parts of the system into sync. For example, when a user requests a build they create a “build” object. The build controller sees that a new build has been created, and runs a process on the cluster to perform that build. When the build completes, the controller updates the build object via the REST API and the user sees that their build is complete.
The controller pattern means that much of the functionality in OpenShift Container Platform is extensible. The way that builds are run and launched can be customized independently of how images are managed, or how deployments happen. The controllers are performing the “business logic” of the system, taking user actions and transforming them into reality. By customizing those controllers or replacing them with your own logic, different behaviors can be implemented. From a system administration perspective, this also means the API can be used to script common administrative actions on a repeating schedule. Those scripts are also controllers that watch for changes and take action. OpenShift Container Platform makes the ability to customize the cluster in this way a first-class behavior.
To make this possible, controllers leverage a reliable stream of changes to the system to sync their view of the system with what users are doing. This event stream pushes changes from etcd to the REST API and then to the controllers as soon as changes occur, so changes can ripple out through the system very quickly and efficiently. However, since failures can occur at any time, the controllers must also be able to get the latest state of the system at startup, and confirm that everything is in the right state. This resynchronization is important, because it means that even if something goes wrong, then the operator can restart the affected components, and the system double checks everything before continuing. The system should eventually converge to the user’s intent, since the controllers can always bring the system into sync.
What is the use of OpenShift?
There are the following use of OpenShift:
- Helps developers delivering high-quality applications and functionalities in a faster way;
- Improves business and efficiency results satisfying the customers’ and users’ needs;
- The continuous application management needs less time;
- Reduces the applications’ developed costs associated to the infrastructure and platforms’ development.
Industry Use Case of OpenShift:
Why Cisco Use OpenShift?
To keep pace with customer demand, Cisco, a leading provider of networking solutions, must quickly deliver new IT products and solutions. The challenge is to keep its IT team engaged and productive to fuel innovation. With help from Red Hat, Cisco built its Lightweight Application Environment (LAE), which runs on Red Hat OpenShift Container Platform, a Platform-as-a-Service (PaaS) technology formerly known as OpenShift Enterprise by Red Hat.
Challenge: Improve productivity and speed to market
Cisco’s success depends on its ability to quickly deliver innovative IT products and solutions to customers. Delays can cost the company business. To encourage speed to market and improve satisfaction, Cisco needed to keep its 1,000+ developers fully engaged in designing and building applications and guard against high employee turnover, low productivity, and slow response times.
Solution: Build a 1-stop shopping catalog
Cisco turned to Red Hat to design and build its LAE, a PaaS deployment that supports hundreds of apps that power a variety of business functions. The solution gives developers a self-service portal they can use to order the IT resources they need to develop apps, eliminating manual provisioning. “It’s a 1-stop shopping catalog … making the ordering process seamless and easier for developers to use,” said Sudha Agrahara, IT manager at Cisco.
Airbus designs, manufactures, and delivers industry-leading commercial aircraft, helicopters, military transports, satellites, and launch vehicles, as well as providing data services, navigation, secure communications, urban mobility, and other solutions for customers on a global scale.
Airbus is undergoing a transformation to offer services on any type of platform and provide on-demand access to software-defined infrastructure. The organization chose to create a Platform-as-a-Service (PaaS), using Red Hat OpenShift and other Red Hat technology but sought to improve in-house skills and internal integration for faster, more efficient development of cloud-native applications.
Path to innovation
To build a path to faster application delivery with DevOps practices, Airbus participated in a Red Hat Open Innovation Labs engagement. During the 6-week residency, Airbus’s teams worked closely with Red Hat consultants to learn about building cloud-native applications following DevOps practices. The project used Open Practice Library foundational approaches to collaborative, iterative strategy and development to envision, plan, and begin building an initial prototype platform. Weekly review meetings helped participants hone the project roadmap and stay informed of progress.
• Built and demonstrated an initial unified PaaS and reusable components for supporting key business capabilities
• Gained hands-on skills and experience for in-house creation of cloud-native applications following DevOps and cloud-native design practices
• Established foundation for significantly faster delivery of new services and ongoing expansion of the platform