Quick Introduction to Fuse 7.5 on OpenShift

Goals

• Benefits of Fuse on OpenShift Benefits
• Understanding administrative tasks for Fuse on OpenShift
• Explaining how to start developing for Fuse on OpenShift

Benefits of Fuse on OpenShift

• Native integration with Docker, Kubernetes, OpenShift
• Transparency in platform changes for developers
• Self-service, scaling, CI/CD for administrators
• Application runtime built for microservice deployments

Administrator Tasks

The main administrative tasks will typically be:

Installing Fuse imagestreams and templates on the OpenShift 4.x server

• Setting up the Fuse Console on OpenShift 4.x
• Installing API Designer on OpenShift 4.x - (Apicurio) (Optional, through OperatorHub)

Installing Fuse imagestreams and templates on the OpenShift 4.x server

ImageStrams is an OpenShift API object that represents single virtual view of related images.

• For Installing Fuse imagestreams and templates, you must have the administrator role for the OpenShift project.

1. Type of Red Hat Fuse 7 images:
2. Install Red Hat Fuse 7 images:
   You can refer to script for installing image streams and templates.
3. fuse-karaf-openshift: Camel applications based on Karaf
4. fuse-java-openshift: Camel applications based on standalone Java™ flat file or Spring Boot
5. fuse-eap-openshift: Camel applications based on JBoss EAP

Setting up the Fuse Console on OpenShift 4.x

On OpenShift 4.x, you can choose one of these Fuse Console deployment options:

Cluster — The Fuse Console can discover and connect to Fuse applications deployed across multiple namespaces (projects) on the OpenShift cluster. To deploy this template, you must have the administrator role for the OpenShift cluster.

1. Namespace — The Fuse Console has access to a specific OpenShift project (namespace). To deploy this template, you must have the administrator role for the OpenShift project.

• script for installing fuse console for cluster
• script for installing fuse console for namespace

Getting Started for Developers

Maven Archetypes

Used to generate new project with required resources and POM dependencies

Archetype catalog located in Maven repositories:

• Red Hat Fuse
• Red Hat GA

Archetype types

Karaf & Spring Boot 1.5

Example command to create project:

mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate \ -DarchetypeCatalog=https://maven.repository.redhat.com/ga/io/fabric8/archetypes/archetypes-catalog/2.2.0.fuse-750020-redhat-00002/archetypes-catalog-2.2.195.redhat-000032-archetype-catalog.xml \ -DarchetypeGroupId=org.jboss.fuse.fis.archetypes \ -DarchetypeVersion=2.2.0.fuse-750020-redhat-00002 \ -DarchetypeArtifactId=<archetype-name>

Table 1. Available Archetypes

Spring Boot 2

For more information see Deploying into Spring Boot For more information on all of the differences between Spring Boot 1 and Spring Boot 2, see Spring Boot’s Migration Guide and Spring Boot 2 Release Notes.

Example command to create project:

mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate \ -DarchetypeCatalog=https://maven.repository.redhat.com/ga/io/fabric8/archetypes/archetypes-catalog/2.2.0.fuse-sb2-750011-redhat-00006/archetypes-catalog-2.2.0.fuse-sb2-750011-redhat-00006-archetype-catalog.xml \ -DarchetypeGroupId=org.jboss.fuse.fis.archetypes \ -DarchetypeVersion=2.2.0.fuse-sb2-750011-redhat-00006 \ -DarchetypeArtifactId=<archetype-name>

Table 2. Available Archetypes

Set Up Maven Archetype Catalog in JBoss Developer Studio/Code Ready

1. From JBoss Developer Studio, select Preferences.
2. Select Maven → Archetypes.
3. Select Add Remote Catalog and complete the fields with these values:
• Catalog File: https://maven.repository.redhat.com/ga/io/fabric8/archetypes/archetypes-catalog/2.2.0.fuse-000092-redhat-2/archetypes-catalog-2.2.0.fuse-000092-redhat-2-archetype-catalog.xml
• Description: Fuse EA Archetypes

Packaging Process

Deployment with S2I

Workflow process for S2I Code Workflow

1. Code pulled from Git repository, or from developer machine after compression, and copied onto S2I builder image
2. S2I builder image pulled from registry into node where build takes place
3. Maven build takes place, pulling required dependencies and generating application artifacts
4. Docker image created, based on Red Hat Fuse S2I image and containing application artifacts
5. Docker image pushed into OpenShift registry
6. Container started on OpenShift node

Workflow process for S2I Binary Workflow

It is called binary because you bypass Git repository, and do the build on your local machine and then push the generated binary directly to OpenShift.

Table 3. S2I Binary Build Types

Fabric8

Fabric8 makes it easy to create Microservices, build, test, and deploy them via Continuous Delivery pipelines then run and manage them with Continuous Improvement and ChatOps.

• Fabric8 maven plugin can be used to perform S2I binary build and deploy, allowing developers to deploy directly from their desktop to OpenShift.
• Fabric 8 CICD fabric8 provides Continuous Integration and Continuous Delivery (CI and CD) infrastructure built as a set of Kubernetes resources, which are easy to Install.
• Jenkins Pipeline Library to help reuse Jenkins Pipeline functions and steps across projects.
• Jenkinsfile Library is a library of reusable Jenkinsfile files you can copy into your project.