Skip to main content

Fuse Integration Service - Auto Dealership Management Demo, Part Six

This series of blog is based on building an auto dealership management system on Fuse Integration Service. We will be creating three major functions in the system.
  • Sales report tracking 
  • Vehicle inventory status
  • Customer IoT Service
We have exported a sales report to a web page, provide current inventory status of available cars through web service. And collect customer data from IoT devices on their car then alert close by shops. 

In this part of the series, I want to look at Blue Green Deployment, and how Fuse Integration does it? So what exactly is this "blue green deployment" ? This is one technique to ensure the high availability and is very important in DEVOPS. In continuous delivery to ensure quality of the application, often we want to carry out a set of test before it goes on to an environment before releasing it to clients, this technique allow two versions of application running at the same time, so you can switch between the existing and update application. This will allow you to have near zero downtime deployments, in case of something goes wrong, we can quickly rollback to previous version with near zero downtime as well.

In Fuse Integration Service, because it's base on OpenShift, we can achieve blue green deployment through the Router capability in OpenShift. An OpenShift route expose services we create and mapping it to externally-reachable hostname. The Routers support the following protocols:
  • HTTP
  • HTTPS (with SNI)
  • WebSockets
  • TLS with SNI
From our demo, you can see each one of our service is mapped to a route.


What we are going to do is to deploy new version of our sales report service, without affecting the other one, and then switch this route to new version.

If you still remember the inventory project, it provides a json format list of sales summary

We want to remove the Date column, how do we make sure the data are correct before we deliver this application to all client? Simple, first, let's do the remove of the content in the code,  under our OpportunityGenerator java file,


And before we publish our updated application to OpenShift, we are going to make a little change, change the name of our project, in our pom.xml, change to another name of the application.


And then we can start publish it to OpenShift, with

  • mvn -Pf8-local-deploy

On the console, we will see sales report application running, with two different service name


  • salesreportfile-v2
  • salesreportfile

and if you take a look at the Route view, we can that now each service is connected to their own host name.

We can access the function with two different url from client,

  • http://salesreportfile-demo.cdk.10.1.2.2.xip.io/AutoDMS/salesTracking
  • http://salesreportfile-v2-demo.cdk.10.1.2.2.xip.io/AutoDMS/salesTracking

Now, for old clients they would access the application with the old route, now, for blue green deployment, we can simply switch the route that was originally point to service salesreport to the update salesreport-v2.  To do that, please go to a command line console, and login with the OpenShift v3 client.


ChristinatekiMacBook-Air:Desktop christina$ oc login
Authentication required for https://10.1.2.2:8443 (openshift)
Username: clin@redhat.com
Password: 
Login successful.

Using project "demo".
do a display of routes, again, to see what are available, 

ChristinatekiMacBook-Air:Desktop christina$ oc get route
NAME                 HOST/PORT                                     PATH      SERVICE              LABELS    INSECURE POLICY   TLS TERMINATION
dealeralert          dealeralert-demo.cdk.10.1.2.2.xip.io                    dealeralert                                      
gpsservice           gpsservice-demo.cdk.10.1.2.2.xip.io                     gpsservice                                       
inventoryservice     inventoryservice-demo.cdk.10.1.2.2.xip.io               inventoryservice                                 
salesreportfile      salesreportfile-demo.cdk.10.1.2.2.xip.io                salesreportfile                                  
salesreportfile-v2   salesreportfile-v2-demo.cdk.10.1.2.2.xip.io             salesreportfile-v2                               
Re-route the old service to another route,  
ChristinatekiMacBook-Air:Desktop christina$ oc edit route salesreportfile
Edit cancelled, no changes made.

You will be prompt with a file, edit the host name to the a new one, and save. 


Start re-route the hostname to our new service salesreportfile-v2
ChristinatekiMacBook-Air:Desktop christina$ oc edit route salesreportfile-v2
Edit cancelled, no changes made.

You will be prompt with a file, edit the host name to the original one we had, and save. 






Refresh your the console, and you can see now the original route is now pointed to the new application. 

Try access the content with
  • http://salesreportfile-demo.cdk.10.1.2.2.xip.io/AutoDMS/salesTracking
  • http://salesreportfile-old-demo.cdk.10.1.2.2.xip.io/AutoDMS/salesTracking
And that's it! Simple!

Comments

Popular posts from this blog

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

jboss-devstudio-9.0.0.GA-installer-eap.jar
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 …

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 …