Skip to main contentSKO Technical Academy - Integration

Agile Integration Best Practices Using an IBM GitOps Automation Framework

banner

Agile Integration Best Practices Using an IBM GitOps Automation Framework

Lab Overview

Have you received requests to deliver a Multi-style Integration demo or PoC, and you don’t know how to quickly prepare this environment? You are on the right place. In this session, you will learn how to prepare a demo/PoC environment using GitOps automation framework. This environment will include different assets, capabilities, services and applications of IBM Cloud Pak for Integration.

The first main goal of this session is to provide you a complete CP4I environment with multiple demo assets to be ready to progress your sales opportunity. This first goal is achieved by reusing a multi-style integration demo assets.

The second goal is to provide this environment quickly and easily, by using the GitOps automation framework, more details here about Cloud Pak Production Deployment Guides.

This document was created for Senior Technical Specialists, and we know you are one of them. Because of that, instead to have very detailled steps, we have high level directions about what you need to do. There are some challenges that we don’t explain how to do them, but we are pretty sure that you can do it! But let the proctors know if you have any issue to complete the challenges.

In this session you will learn:

  • the IBM opinionated point of view regarding a GitOps centric method to manage RHOCP infrastructure, IBM integration software and application workload code (three tier GitOps architecture).
  • how to develop, review, and extend an IBM GitOps automation repository that incapsulate key software components within the IBM Integration portfolio.
  • how to position a GitOps automation framework as a key boot-strapping and operational mechanism supporting a Client PoC activity and Client adoption.

Prerequisites

  • You need to have an OpenShift environment with GitOps operators. For this session, your proctor will provide you a pre-installed environment, with admin access (more details below). If you want to create your personal environment, check this video or follow the preparation section from this documentation.
  • You need to have installed in your machine:
  • You need to have a SalesForce account. This should have been completed as part of the Tech Academy pre-requisite work.
  • You need to have a mailtrap account. This too should have been completed as part of the Tech Academy pre-requisite work.
  • You have access to GitHub Organization with all repositories. Your proctor will provide that for you.
  • You need to have your GitHub Personal Access Token. Check here how to create it.

Business Context

This document describes multiple use cases that highlight the multi-style integration patterns needed by an Integration Specialist to implement a digital transformation initiative that showcase the value Cloud Pak for Integration can provide.

In this case a customer has a system of record that has used for many years which ws designed to work with MQ to process requirements, and now they want to extend the application to expose an API in a asecure way as part of their mobile app.

But the requirement doesn’t end there, they are also implementing a new CRM system as a Service and they want to keep both systems in sync without having to modify the original system of record.

Additionally as part of their digital transformation initiative they want to stay closer to their clients and they want to send email notifications when the client is taking certain actions in their mobile app. To support this strategy, the enterprise architecture team wants to implement an event backbone, as part of their event driven architecture.

The following diagram provides a high level view of the scenario: CP4I MultiStyle DemoScenario

In order to implement this demo you will need to deploy an instance of each one of the following components in your OCP Cluster:

  • API Connect Cluster
  • Event Streams Cluster
  • Queue Manager
  • App Connect Enterprise Integration Servers

The following diagram provides a high level implementation view of the scenario with the core capabilities: CP4I MultiStyle HighLevelView

To demonstrate the added value capabilities provided by CP4I you will deploy an instance of the following components in your OCP Cluster:

  • Platform UI (formerly known as Platform Navigator)
  • Automation Foundation Assets (formerly known as Asset Repository)
  • Operations Dashboard

Automation Framework Introduction

What are the Production Deployment Guides?

The Cloud Pak Production Deployment Guides document and demonstrate how to design, deploy and operate cloud-native solutions leveraging IBM Cloud Pak capabilities in Red Hat OpenShift environments. The guides focus on Production level qualities of services such as High Availability, Security and Performance including how to design, install and manage your Cluster in the popular managed and unmanaged Cloud environments as well as tackling disconnected or air-gapped environments.

Production Deployment Guide objectives

There are a number of objectives behind providing the Production Deployment Guides. The three main goals of the Guides are provided below:

  • Provide opinionated, validated Production topologies
  • Provide a GitOps driven automation framework
  • Enable IBMers to setup Production topologies

What is GitOps?

GitOps requires us to describe the entire system declaratively in Git where the desired system state is versioned, managed and applied by software agents.

Automation is key for scale in the Cloud world and OpenShift and Cloud Paks are no different. The implementation code and artifacts provided along with these guides are based on a GitOps approach where infrastructure and everything deployed in to an OpenShift Cluster (including Cloud Paks) is described as code and is managed in the same way that application code would be.

More information on the gitops structure can be read in this page.

Lab Environment

For this session you will use a ROKS 4.8 environment with 5 nodes (b3c.16x64). Following this video, you can have a personal environment for you, including GitOps operator and configuration. But for this section, your lab proctors pre-installed this cluster for you. They already installed GitOps, created an empty GitHub Organization and forked the automation repositories that you will use, for this empty organization (check the video to see the steps already completed).

Because of time restrictions, the proctors already installed some core services of Cloud Pak for Integration, avoiding you to wait almost 90 minutes to complete this installation. In the previous sections, you will check what are installed in this environment.

0 - Preparation

In this section you will do some initial steps to prepare your environment for the lab, including accept the Account Invitation in IBM Cloud, access your cluster web console and by command line interface. Let’s start it!

  1. Log in IBM Cloud.

  2. Open the Notifications page (click on top right ring bell icon).

gitops 0 1
  1. On the Notifications page, you should have an Account notification informing you that “You are invited to join an account in IBM Cloud”. Select this notification and click the Join now link.
gitops 0 2

  1. Follow the steps to accept the invitation.

  2. Now back to the IBM Cloud dashboard, change your IBM Cloud account to 2543884 - itztsglenablement05.

gitops 0 3

  1. Now, click here to open the Team Environments page.

  2. Open your Team’s section (A) (check the number of your team with the Lab’s proctors). Take notes of your Team’s Github organization name (B), you will use it in next section. Then, open your team’s Cluster page (C).

team cluster
  1. On your cluster’s page, click OpenShift web console.
openshift console
  1. Great, you are almost ready for the lab. Last but not least important, let’s copy login command to access the cluster by CLI. On the top right, click your username and select Copy login command.
gitops 0 4
  1. Click Display Token.
display token
  1. Copy the Log in with this token command and paste on a terminal window.
login cmd

Notes: You should have received an invitation for the GitHub Organization of your team. Don’t forget to accept it in your Github account email.

That is it! Now you are ready for the lab. Take a breath and enjoy your lab!

1 - Clone Repositories

As explained before, you already have Github repositories for your team. On previous section, you took notes of your GitHub organization’s name. Now that you have the name, let’s clone the repositories in your local machine.

To clone the respositories, you need to have your Github personal acccess token. If don’t have it, follow these instructions.

  1. Back to the terminal window, use the command below to define your GIT_ORG variable.
export GIT_ORG={REPLACE_WITH_YOUR_GIT_ORG}
  1. Now let’s clone the repositories to your local machine.
mkdir ${GIT_ORG}
cd ${GIT_ORG}
git clone https://github.com/${GIT_ORG}/multi-tenancy-gitops
git clone https://github.com/${GIT_ORG}/multi-tenancy-gitops-infra
git clone https://github.com/${GIT_ORG}/multi-tenancy-gitops-services
git clone https://github.com/${GIT_ORG}/multi-tenancy-gitops-apps
  1. You are welcome to explore all the four repositories of the GitOps Automation framework.

2 - Explore the Environment

Now that you have all the repositories locally, let’s check what have been deployed.

  1. Let’s start by exploring the GitOps Automation Framework YAML files. First, let’s check the kustomization.yaml in infra layer (/multi-tenancy-gitops/0-bootstrap/single-cluster/1-infra/).
vi multi-tenancy-gitops/0-bootstrap/single-cluster/1-infra/kustomization.yaml

Check that tools and ibm-common-services are the namespaces enabled. We will explore these namespaces in OpenShift later. Go ahead and close vi.

explore1
  1. Let’s explore the kustomization.yaml in services layer (/multi-tenancy-gitops/0-bootstrap/single-cluster/2-services/)
vi multi-tenancy-gitops/0-bootstrap/single-cluster/2-services/kustomization.yaml

Here you can check that Platform Navigator, Asset Repository, API Connect and others are already installed in your environment. Don’t worry, in next steps you will install other operators and create new instances.

explore2

  1. Let’s check the installed operators in your Cluster Web Console. You should have the web console page opened, if not, there is a URL available in the Team Environments page.

    On Web Console page, open Operators (A), then Installed Operators (B). Here you can see all the installed operators (C).

explore3
  1. Now, let’s open the ArgoCD UI. Let’s get the ArgoCD Admin’s password first. On Web Console page, open Workloads (A) > Secrets (B).
explore4 1

Filter by openshift-gitops project (A) and open the openshift-gitops-cntk-cluster (B).

explore4 2

Scroll down and click to copy the admin.password. You are welcome to take note of this password.

explore4 3
  1. Now, let’s get the ArgoCD URL. Open Networking (A) and Routes (B).
explore5 1

Click on the openshift-gitops-cntk-server location to open the ArgoCD URL.

explore5 2

If necessary, accept all the risks, and log in with admin user and the password that you copied in the previous step. Note: Don’t log in via openshift, because your openshift user doesn’t have write permission.

explore5 3

  1. Now, you are in Argo CD. Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Here you can see all the applications. In Argo CD, application definitions, configurations, and environments should be declarative and version controlled. Application deployment and lifecycle management should be automated, auditable, and easy to understand.

    As you can see, you have 20 healthy applications in your environment (A), including ibm-platform-navigator (B). You are welcome to explore the Applications tiles page to see the other applications available.

explore6
  1. Great, now let’s check your Cloud Pak for Integration environment. First we need to get the Platform Navigator URL and password. Let’s do it! Back to the OpenShift Web Console, open Workloads (A) and Secrets (B) again.
explore7 1

Now filter by tools project (A) and open the ibm-iam-bindinfo-platform-auth-idp-credentials secret (B).

explore7 2

Scroll down and click to copy the admin_password. You are welcome to take note of this password.

explore7 3
  1. Now, let’s get the Platform Navigator URL. Open Networking (A) and Routes (B).
explore8 1

Scroll down and click on the integration-navigator-pn location to open the Platform Navigator.

explore8 2

If necessary, accept all the risks, and click IBM provided credentials (admin only) link.

explore8 3

Log in with admin user and the password that you copied in the previous step.

explore8 4
  1. Now, let’s explore the CP4I. Close the Welcome dialog.
explore9 1

Let’s check the instances available. Click on Integration instances link.

explore9 2

Great, here you can check that your API Management (including Gateway and Admin), Automation Assets and Integration tracing are Ready to be used.

explore9 3

3 - Prepare the Subscription

Now it’s your time to do some actions using the GitOps Automation Framework. Let’s start by preparing some subscriptions.

  1. Edit multi-tenancy-gitops/0-bootstrap/single-cluster/2-services/kustomization.yaml.
cd multi-tenancy-gitops
vi 0-bootstrap/single-cluster/2-services/kustomization.yaml
  1. Uncomment the lines below to enablle the ACE, MQ and Event Streams operators. Then close and save the YAML file.
- argocd/operators/ibm-ace-operator.yaml
- argocd/operators/ibm-eventstreams-operator.yaml
- argocd/operators/ibm-mq-operator.yaml
  1. In the multi-tenancy-gitops folder: Add, Commit and Push the changes to multi-tenancy-gitops repository.
git add .
git commit -m "adding new operators"
git push origin
  1. Now let’s check the operators installation in Argo CD. Back to the Argo CD console, refresh the 02-Services application. Maybe you need to wait few minutes to make sure that all the status are Sync and Healthy, before progressing.
subscription 4

When completed, you should have 23 healthy applications (A), including ibm-ace-operator, ibm-mq-operator and ibm-eventstreams-operator (B).

subscription 4 2
  1. Back to the OpenShift Web console, open again Operators (A), Installed Operators (B). Check the new three operators in the list (C).
subscription 5

4 - Deploy ACE and ES instances

Now, let’s create App Connect Enterprise and Event Streams instances using the GitOps Automation Framework.

  1. Back to the terminal window. In multi-tenancy-gitops, edit the file below.
vi 0-bootstrap/single-cluster/2-services/kustomization.yaml
  1. In the CP4I for SKO section, uncomment the lines below. Then close and save the YAML file.
- argocd/instances/es-demo.yaml
- argocd/instances/ace-infra.yaml
  1. In the multi-tenancy-gitops folder: Add, Commit and Push the changes to multi-tenancy-gitops repository.
git add .
git commit -m "deploying ace and es"
git push origin
  1. Back to the argoCD console, refresh the 02-Services application. Maybe you need to wait few minutes to make sure that all the status are Sync and Healthy, before progressing.
instances 4 1

When completed, you should have 25 healthy applications (A), including es-demo and ace-infra (B).

instances 4 2
  1. Now, let’s check the new instances in CP4I Platform Navigator. Refresh the Integration instances pages (Menu > Administration > Integration instances), and check if the new instances are available and ready. Note: ignore the warning in Kafka cluster, it is only informing about a new version.
instances 5

5 - Activate MQ Queue Manager

Now, let’s start the application layer. First we need to create the MQ Queue Manager.

  1. Back to the terminal window. In multi-tenancy-gitops, edit the file below.
vi 0-bootstrap/single-cluster/3-apps/kustomization.yaml
  1. In the SKO sample apps section, uncomment the line below. Then close and save the YAML file.
- argocd/sko-sample/mqmgr.yaml
  1. In the multi-tenancy-gitops folder: Add, Commit and Push the changes to multi-tenancy-gitops repository.
git add .
git commit -m "mq queue manager"
git push origin
  1. Back to the argoCD console, refresh the 03-Application application. Maybe you need to wait few minutes to make sure that all the status are Sync and Healthy, before progressing.
queue 4 1

When completed, you should have 26 healthy applications (A), including mqmgr (B).

queue 4 2
  1. On the OpenShift Web Console page, open Workloads (A), and Pods (B).
queue 5 1

Filter by qmgr-demo pods (A) and check if they are running (B).

queue 5 2
  1. On the CP4i Platform Navigator page, refresh the Instagration instances page and open the qmgr-demo.
queue 6 1

On the MQ Console, click on Manage QMGRDEMO.

queue 6 2

Here you can check the Queue Manager.

queue 6 3

6 - Customize Event Streams

Now, let’s create the Event Streams resources for our Multi-Style demo.

  1. Back to the terminal window. In multi-tenancy-gitops, edit the file below.
vi 0-bootstrap/single-cluster/3-apps/kustomization.yaml
  1. In the SKO sample apps section, uncomment the line below. Then close and save the YAML file.
- argocd/sko-sample/eventstream.yaml
  1. In the multi-tenancy-gitops folder: Add, Commit and Push the changes to multi-tenancy-gitops repository.
git add .
git commit -m "customize ES"
git push origin
  1. Back to the argoCD console, refresh the 03-Application application. Maybe you need to wait few minutes to make sure that all the status are Sync and Healthy, before progressing.
es 4 1

When completed, you should have 27 healthy applications (A), including eventstream (B).

es 4 2
  1. Open the eventstream application.
es 5 1

Open the es-demo-setup-job-??? pod.

es 5 2

Open the LOGS tab.

es 5 3
  1. You should see a failure that statefulsets.apps is forbidden.
es 6 1

Let’s fix it! Back to the terminal window, go to the multi-tenancy-gitops-apps folder and edit the file below.

cd ../multi-tenancy-gitops-apps/
vi sko-sample/eventstream/es-demo-setup-job-sa-role.yaml
  1. In the Rules section, create a new rule with the content below and save the new YAML file.
- apiGroups: ["apps"]
  resources: ["statefulsets"]
  verbs: ["get", "watch", "list"]
- apiGroups: ["route.openshift.io"]
  resources: ["routes"]
  verbs: ["get", "watch", "list"]
es 7 1
  1. In the multi-tenancy-gitops-apps folder: Add, Commit and Push the changes to multi-tenancy-gitops-apps repository.
git add .
git commit -m "adding rules"
git push origin
  1. Back to the argoCD console, refresh the eventstream application. Maybe you need to wait few minutes to make sure that all the status are Sync and Healthy.
es 9 1
  1. Now you need to delete es-demo-setup-job to re-run the pod. Open the context menu in es-demo-setup-job (A) and select Delete (B).
es 10 1

Enter es-demo-setup-job (A) to confirm the deletion and click OK (B).

es 10 2

Wait few seconds to recreate the job and pod. When ready, click on the es-demo-setup-job-??? pod again.

es 5 2

Open the LOGS tab again.

es 5 3

Great! Now you should not see any error message.

es 10 3

7 - Configure ACE

Now, let’s work with Application Connect Enterprise. In this part, you are configuring artifacts, secrets and certificates.

  1. Back to the terminal window. In multi-tenancy-gitops-apps folder, open the folder below.
cd sko-sample/ace-00-configs/
  1. Execute the commands below to generate the configuration YAML files. Where:
    • SF_USER is [Email addess used to log into Salesforce]
    • SF_PWD is [Password used to log in][token received in email]
    • SF_CLIENT_ID is [Consumer Key]
    • SF_CLIENT_SECRET is [Consumer Secret]
    • MAILTRAP_USER is [Mailtrap SMTP User]
    • MAILTRAP_PWD is [Mailtrap SMTP Password]
./06-ace-config-barauth-github.sh
./07-ace-config-policy-mq.sh
SF_USER=<my-sf-user> SF_PWD=<my-sf-pwd> SF_CLIENT_ID=<my-sf-client-id> SF_CLIENT_SECRET=<my-sf-client-secret> SF_LOGIN_URL="https://login.salesforce.com" ./08-ace-config-accounts-sf.sh
./10-ace-config-policy-es-scram.sh
./11-ace-config-setdbparms-es-scram.sh
./12-ace-config-truststore-es.sh
./13-ace-config-policy-udp.sh
./14-ace-config-policy-email.sh
MAILTRAP_USER=<user> MAILTRAP_PWD=<pwd> ./15-ace-config-setdbparms-email.sh
  1. Verify that there are 9 YAML files generated in the ace-00-configs folder.
ls *.yaml
ace 3 1
  1. Edit multi-tenancy-gitops-apps/sko-sample/ace-00-configs/kustomization.yaml file.
vi kustomization.yaml
  1. Uncomment the lines below (all the content). Then save and close the YAML file.
- ace-config-accounts-designer.yaml


- ace-config-policy-es-scram.yaml
- ace-config-setdbparms-es-scram.yaml
- ace-config-truststore.yaml


- ace-config-policy-udp.yaml
- ace-config-policy-email.yaml
- ace-config-setdbparms-email.yaml
ace 5 1
  1. In the multi-tenancy-gitops-apps folder: Add, Commit and Push the changes to multi-tenancy-gitops-apps repository.
cd ../../
git add .
git commit -m "ace config"
git push origin
  1. Now, go to multi-tenancy-gitops folder and edit multi-tenancy-gitops/0-bootstrap/single-cluster/3-apps/kustomization.yaml file.
cd ../multi-tenancy-gitops/
vi 0-bootstrap/single-cluster/3-apps/kustomization.yaml
  1. In the SKO sample apps section, uncomment the lines below. Then save and close the YAML file.
- argocd/sko-sample/ace-00-configs.yaml
- argocd/sko-sample/ace-backend.yaml
- argocd/sko-sample/ace-evnt2mail.yaml
- argocd/sko-sample/ace-fwdmqevnt.yaml
- argocd/sko-sample/ace-mqapidflt.yaml
- argocd/sko-sample/ace-mqapiprem.yaml
- argocd/sko-sample/ace-sflead.yaml
  1. In the multi-tenancy-gitops folder: Add, Commit and Push the changes to multi-tenancy-gitops-apps repository.
git add .
git commit -m "ace config"
git push origin
  1. Back to the argoCD console, go to the Applications dashboard. And refresh the 03-Application application. Maybe you need to wait few minutes to make sure that all the status are Sync and Healthy, before progressing.
ace 10 1

When completed, you should have 34 healthy applications (A), including ace-sflead and ace-evnt2mail (B).

ace 10 2
  1. Back to Platform Navigator, open App Connect Dashboard (Menu > Run > Integrations).
ace 11 1

Open Servers.

ace 11 2

Check the Integration servers.

ace 11 3

8 - Customize APIC

Now, let’s create the Provider Organization and Publish the API in APIC.

  1. Go to the folder multi-tenancy-gitops-apps/sko-sample/apic-cust.
cd ../multi-tenancy-gitops-apps/sko-sample/apic-cust
  1. Now let’s configure APIC to submit emails when necessary (e.g.: Portal Users registration). Run the script to generate the APIC mail secret using Mailtrap. Where:
    • MAILTRAP_USER is [Mailtrap SMTP User]
    • MAILTRAP_PWD is [Mailtrap SMTP Password]
MAILTRAP_USER=<user> MAILTRAP_PWD=<pwd> ./apic-user-mail-secret.sh
  1. Check that you have a Secret YAML file in your folder.
ls *secret.yaml
  1. In the multi-tenancy-gitops-apps folder: Add, Commit and Push the changes to multi-tenancy-gitops repository.
cd ../../
git add .
git commit -m "apic user mail secret"
git push origin
  1. Go to the multi-tenancy-gitops folder and edit the file multi-tenancy-gitops/0-bootstrap/single-cluster/3-apps/kustomization.yaml.
cd ../multi-tenancy-gitops/
vi 0-bootstrap/single-cluster/3-apps/kustomization.yaml
  1. In the SKO sample apps section, uncomment the line below. Then save and close the YAML file.
- argocd/sko-sample/apic-cust.yaml
  1. In the multi-tenancy-gitops folder: Add, Commit and Push the changes to multi-tenancy-gitops repository.
git add .
git commit -m "apic customization"
git push origin
  1. Back to the argoCD console, refresh the 03-Application application. Maybe you need to wait few minutes to make sure that all the status are Sync and Healthy, before progressing.
apic 8 1

When completed, you should have 35 healthy applications (A), including apic-cust(B).

apic 8 2
  1. Open the apic-cust application.
apic 9 1

Open the apim-demo-setup-job.

apic 9 2

Open the LOGS tab.

apic 9 3

Check the log to confirm that the apic-setup job is successful.

apic 9 4
  1. Great, now you are ready to publish your API. Back to the OpenShift Console, open the Pods page (Workloads > Pods) (A), on the tools namespace (B), filter by the word publish (C).
apic 10 1
  1. Open the apic-publish-deployment pod.
apic 11 1 
Go to the **Terminal** tab.
apic 11 2
  1. In the Terminal session, run ./apic-publish-api.sh. Accept the license. And feel free to accept or not the limited usage tracking.
apic 12 1

  1. You need to authenticate in APIC to publish the API. Let’s do it! Open the URL provided in a different browser session.

  2. If necessary log in APIC with Common Services User Registry.

apic 14 1

Log in with your admin and password.

apic 14 2
  1. Copy the code.
apic 15 1

And paste to the terminal tab on OpenShift Web Console to continue the publish process.

apic 15 2
  1. Great, your API is published successfully.
apic 16 1

9 - Check the Demo Assets

Great, in this part of the lab, you will check the Demo environment and assets. On the other hand, you will collect all the evidences to prove that you were able to complete the lab (check the 3 screenshots notes).

  1. Back to ArgoCD page, go to the main page, and check all the 35 applications are synced and healthy.
final 1 1
  1. Now, let’s test your demo. Open the Platform Navigator page and go to the Integration Instances view (Menu > Administration > Integration instances).
final 2 1
  1. Here you should see all the integrations as Ready (Note: Ignore the Warning in Kafka cluster).
final 3 1
  1. Then, open the API management.
final 4 1

If necessary log in API Manager with Common Services User Registry.

  1. Click Develop APIs and products.
final 5 1

And select JGRMQAPI.

final 5 2
  1. Put your API online.
final 6 1 final 6 2
  1. Now, let’s try it! Open the Explorer tab.
final 7 1
  1. Click on POST /contacts.
final 8 1
  1. Open Try it.
final 9 1
  1. On the Body section, click Generate to create a request body sample.
final 10 1
  1. Click Send.
final 11 1
  1. If you received 200 response, your request has been processed (success). Note: if you receive a CORS issue. Open the URL, accept the risks and try again.
final 12 1
  1. Now, let’s check the Integration Tracing page (Operate > Integration Tracing).
final 13 1
  1. Close the What’s New dialog.
final 14 1

Accept the license.

final 14 2
  1. Open the Traces view.
final 15 1
  1. Select the entry that has all APIC ACE and MQ components in the services column.
final 16 1
  1. Great, here you should have the integrated trace graph with 10 nodes, including all the demo components.
final 17 1

Summary

You have successfully completed this lab. In this lab you learned:

  • the IBM opinionated point of view regarding a GitOps centric method to manage RHOCP infrastructure, IBM integration software and application workload code (three tier GitOps architecture).
  • how to develop, review, and extend an IBM GitOps automation repository that incapsulate key software components within the IBM Integration portfolio.
  • how to position a GitOps automation framework as a key boot-strapping and operational mechanism supporting a Client PoC activity and Client adoption.

Check this video later, if you want to learn how to deliver a demo using this demo environment.

So far we have focused on the “runtime” aspect of the deployment, but to provide a full demo experience, in some cases you will need to walk a customer through the assets that make up the demo scenario. If you want to have the developer experience in your demo/POC, check here how to do it.

Edit this page on GitHub