How Docker Changed the Way We Develop and Release OpenShift Online

By now you’ve probably heard about Docker, the lightweight container management project. As the Docker website mentions “the same container that a developer builds and tests on a laptop can run at scale, in production, on VMs”, etc. The OpenShift Online engineers and operations team saw this as an opportunity to change the way we develop and release the independent parts of our product.

Here’s how we’ve completely changed the way we create and use development environments.


GearD: The Intersection of PaaS, Docker and Project Atomic

When it comes to the technology available to leverage in a PaaS platform, this is an amazing time. PaaS platforms such as OpenShift are usually at the intersection of developers and operations and establish the patterns to make both parties efficient. Practically, that means that PaaS platforms are tightly integrated with both the development tooling as well as the operating system itself. And in the operating system, there is a lot of change underfoot!

The change in the operating system is occurring for a few reasons. The first dates back to the introduction of IaaS and cloud. IaaS started changing the way we think about workloads and operating system instances. They started to become more elastic and developers started designing their applications around that elasticity. They didn’t assume an operating system instance or host would just run forever.

Then Linux containers came along and amplified the expectations around elasticity.