FINALLY LETTING THE DEVELOPERS DEVELOP

Solving the 70/30 Dev problem with Openshift Container Platform

Ian ‘Uther’ Lawson

Principal Domain SolutionArchitect
Openshift Evangelist/Ex-Frustrated-Developer
 Why do we do it?

“Being a developer is a thankless task involving

coffee, stress, deadlines, middle-management and long days….”

FAME!
FORTUNE!
RESPECT!
THE THRILL OF CREATINGSOMETHING
2
 The 70/30 Problem

● Historically the art of development has been problematic

● Devs were a poor-man’s Sys-Admin for their development kit
● Too much wasted time configuring the box on which you develop
● At the expense of WRITING CODE and ACTUALLY DEVELOPING
● Also led to the *fun* of trying to get singular test environments
● 70/30 – 70% of time as a developer used to be wasted on nugatory things
● Writing BOILERPLATE code
● Writing SCAFFOLDING code
● Sourcing frameworks and libraries, and installing them
● NOT WRITING CODE!

3
 Why is Openshift sucha game-changer?

● It covers the ‘build’ side of creating Container Images in an elegant, extensible and developer-cuddly way
● It does all the dull bits for you, leaving time for you to write the next generation of Hello World
● Red Hat have taken a developer opinionated approach specifically to make our lives easier
● I no longer have to craft Maven XML, and for that I am HUGELYgrateful (biased)

4
 In Dev-Speak, how does it actually help us?
Environments at the push of a (couple of) button(s)!
When demoing to devs this feature, above every other, just appeals.
Take a git repo, choose a framework, choose a base image, give it a name, couple of minutes later a
compiled node.js application running in a single Pod with an external route pre-defined…….

5
 But I want to use Rust! Or Golang. Or…...
A multitude of supported frameworks
Not strictly accurate - Openshift can orchestrate *any* Docker container, but out of the box provides full
support over a number of standard frameworks, including SpringBoot for all you Fat-Jar fans out there
The concept of Source-2-Image allows for extensibility as well, and the new Red Hat Openshift Application
Runtimes adds an extra layer of simplicity for scaffolding and creating microservice based apps *quickly*

6
 But what about my IDE?
Wouldn’t an integrated IDE be useful…...
As part of the forthcoming OCP4 release, and usable with OCP3.11, Red Hat is working on ‘CodeReady
Workspaces’.
This is a containerised and tailored version of Eclipse-Che, which provides a hosted full developer IDE
including lifecycle controls, repo controls and language specific editing (auto-completion, syntax checking,
optimisation).

7
 Being honest…….

I would have given body parts to have been able to use OCP when I was a day-to-day developer
● It simplifies the tasks I need to perform *before* I can start writing code
● Once I start writing code the boilerplate activities are all single click operations
● I can control and test the way in which my App is deployed in a far easier way than before
● I can abstract the dull bits, connection pooling, service discovery, logging, onto OCP
● I can FOCUS on just writing the good stuff. Like a new Hello World
● I can get consistency of framework without hand-crafting my environments
● I can get consistency of behaviour without having to script my deployments
● I can use the automation of any of the parts of the development lifecycle. More coffee time….
● And I can do all of this in a controlled and safe environment without impacting other devs

8
 Still not convinced? Try it. For free….
There are plenty of ways to have a quick play with OCP
https://manage.openshift.com/ - Openshift Online, a small environment for free

https://learn.openshift.com/ - Fantastic hosted interactive learning tool for OCP

https://try.openshift.com/ - Spin up a copy of the dev preview of the next generation OCP (requires AWS)

https://developers.redhat.com/launch/ - Launchpad for scaffolding the RHOAR apps

9
THANK YOU
plus.google.com/+RedHat facebook.com/redhatinc

linkedin.com/company/red-hat twitter.com/RedHat

youtube.com/user/RedHatVideos