A match made in heaven?

OpenShift 3 + Eclipse Che

Pete Muir
JHipster 4
Solar eclipse image via Shutterstock

The concept of universal workspaces, championed by Eclipse Che, gave Red Hat the ability to easily replicate and distribute the entire development workspace. Red Hat and Codenvy have integrated Che with OpenShift, providing an easy way to copy both your runtime, and your development workspace.

At Red Hat, we think that software is one of the drivers of today’s world, and we feel that this trend will continue until software is the primary force of the future economy. This will transform everything and everyone, from the largest enterprise, to the hobbyist at home, and we think that success will come to those who have the ability to create, deliver and manage quality software – our job at Red Hat is to empower those software creators. We believe that the best way to empower software creators is to enable them to write better software, faster.

When we create software today, we often hit a brick wall and waste many hours because creating copies of another system is far too hard. We create copies for many reasons – a few common examples are replicating production issues, asking another developer for help or running test suites. Sometimes we need to copy the runtime (e.g. app server, web server, LAMP stack…), sometimes the development workspace and sometimes both.

Linux containers provide the necessary encapsulation of your application and its environment, giving us the ability to easily copy the runtime – something we have never had before. The concept of universal workspaces, championed by Eclipse Che, gave us the ability to easily replicate and distribute the entire development workspace. Red Hat and Codenvy have integrated Che with OpenShift, providing an easy way to copy both your runtime, and your development workspace.

OpenShift 3 provides developers with a self-service platform for provisioning, building and deploying containerized applications, and Eclipse Che provides universal workspaces which are on-demand, collaborative, and standardized – this includes both a workspace server and an integrated browser based IDE.

Walkthrough

In this video you can see a developer working with OpenShift and Che through our example scenario – we’ve been asked by the marketing team to make a simple change to our app.

First the developer got hold of the source for the project, by doing a git import. They then connected the workspace to OpenShift, authenticating using OAuth, and finally, configured the OpenShift environment. In this case we are using Red Hat JBoss Enterprise Application Platform with a Java EE application.

Screen Shot 2016-09-09 at 3.02.12 PM

OpenShift also provides templates for other Java servers and frameworks such as Tomcat, and ActiveMQ, as well other languages and frameworks such as Node, Python, the LAMP stack, Ruby, and more. OpenShift also provides access to many common data stores such as MongoDB, MySQL and Postgres.

Screen Shot 2016-09-09 at 3.03.20 PM

Once the application has built, it’s immediately available. Build logs are available within Che so you don’t even need to go to the OpenShift console to view them.

Screen Shot 2016-09-09 at 3.04.31 PM

Manually triggering a deploy is useful, but of course we really want to start to build out a continuous delivery pipeline. We can easily configure OpenShift so that each time we commit to the git repo, a webhook triggers an OpenShift source to image build.

Screen Shot 2016-09-09 at 3.05.42 PM

OpenShift uses the source to image technology to create a war file using the standard Maven, and then wrap it in a docker image. This is pretty magic, as it allows us to take a run of the mill project, and have it deployed in container on OpenShift.

Now, of course, we would need to spend some time making the code changes, checking they look right and creating the patchset, that we can then commit and push for code review.

But, before we do that, we want to run the test suite. Arquillian, the Java testing framework created and maintained by Red Hat, allows us to easily run the tests, from Eclipse Che, on OpenShift. By running the tests in an exact copy of production, we are even more likely to catch bugs early.

Screen Shot 2016-09-09 at 3.06.58 PM

We all know how frustrating it can be to get your workspace and runtime environment set up every time you need to change context. We think that together Eclipse Che and OpenShift are a great step towards making this problem go away. We’re looking forward to taking the work we’ve started, and shown you here today, a lot further. To find more about Openshift 3, visit https://www.openshift.com/. To find out more about Eclipse Che visit http://www.eclipse.org/che/. We always welcome contributions! Find OpenShift and Eclipse Che on GitHub – https://github.com/openshift andhttps://github.com/eclipse/che. This was also posted on developers.redhat.com.

eclipseorb_color

This post was originally published in the August 2016 issue of the Eclipse Newsletter: Eclipse Che – A New Eclipse IDE

For more information and articles check out the Eclipse Newsletter.

Author

Pete Muir

Pete Muir is Technical Director at Red Hat. As Technical Director for Developer, he is responsible for the technical direction of the Red Hat Developer Group and the architecture of our developer tool offerings. He works with the UXD team to define the end to end experience for the developer.


Comments
comments powered by Disqus