Skip to main content

Red Hat JBoss - HP IT Summit in Taiwan, Openshift and Devops

Last Friday, I had a JBoss talk in HP taiwan IT summit, normally, developers doesn't really go to the forums like this, HP are know for their Hardware and infrastructure solutions, but I was there to break the boundary between developers and infrastructure gentlemen/ladies :)

It was a very short 40 minutes session, and it was the last session of the day, to make sure everyone is still awake and concentrating, I also did a little demo too.

As a developer, I wanted to discuss how Openshift has really boost the DevOps, and make our life much easier from a developer point of view, and also allowing system administrators to be relieved from their boring day to day routine job.

Automation place a big part of the DevOps world, OpenShift let developers create and setup a runtime environment on their own, so no more email or phone calls between 2 parties, developers can spin up an application server in few seconds without bothering his/her colleague. Inside Openshift, there are various cartridges you can choose from, the cartridges are how OpenShift installs Languages & Middleware, so there will be an JBoss Enterprise Application Server, or JBoss Fuse for developers to choose their middleware platform, and there are also cartridges of MongoDB or Postgresql and more, if developer needed a database. The instance developers create can be deploy both on premise or cloud, it is completely transparent to developers. They will not need to worry about anything can can then concentrated on their work. With JBoss developer studio it seamlessly combines with openshift, so developers can quickly update their code through the git to the repository inside their openshift nodes.

To make sure we make the most of DEVOPS, we should seriously consider breaking our code/project into smaller chunks, (Believe me, It is so common in Taiwan that I bumped into a WAR or EAP even a JAR file with 1-200 MB, even seen one with more then 700MB). Modulize it, It will improve the development cycle

1. Shorten the developement cycle with less code to maintain and test
2. Less complex code, so it's easier to maintain.
3. Modules can be reused. Even Test code are easier to create because we have limit what each module can do.
4. And be replace or remove with less impact, because it's less sticky in code.

To modulize it and make it more suitable to run in cloud, it is important that we keep it stateless. Or keep the state in your data. Openshift is also a great xPaaS, meaning it provides a great platfrom that integrates everything together with the help from JBoss Fuse technology. With the combination of JBoss Fuse and Openshift, it allows administrator to dynamically create as many instance as the hardware can handle. Give more flexibility to them.

I hope I crack a little hole in the wall between devlopers and system adminstrator with Openshift. :)
Thanks! And here are the slides on that day.


Popular posts from this blog

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.

2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.

So, now we know …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.

And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.

And select JBoss Fuse Development for the plugin,

Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …