Scenarios / Realtime Inventory
A little bit more on environments
For demonstration purpose, only the rt-inventory-dev environment is detailed. One ArgoCD app: rt-inventory-dev-env is monitoring
the folder environments/rt-inventory-dev/env/overlays which define the namespace and roles,…
Each application of the solution are also monitored by an ArgoCD and their declarations are done using standard kubernetes manifests. Here is an exampe of app tree structure:
── store-inventory│ ├── base│ │ └── kustomization.yaml│ ├── kustomization.yaml│ ├── overlays│ │ └── kustomization.yaml│ └── services│ └── store-inventory│ ├── base
The last intesting part is to declare the products used within the Cloud Pak for Integration, and deployed in the context of
the respective environments. Everything is in services folder. The tree looks like below:
── apicurio│ ├── base│ │ ├── es-kafka-topics.yaml│ │ ├── kustomization.yaml│ │ └── registry.yaml│ └── overlays│ └── kustomization.yaml├── event-endpoint│ ├── base
With the public docker images, and the public GitOps repository, the solution can be deployed to an OpenShift cluster with or without Cloud Pak for Integration already deployed.
Run on your laptop
Install Yourself on OpenShift
It is possible to do a step by step deployment of the solution without any gitops deployment. This is more like a lab tutorial, where you can progress more slowly and verify the result at each steps.
Go to the rt-inventory-gitops/ocp-demo-step-by-step folder and follow the README instructions to make
a step by step approach creating records with the simulator, see them in MQ Queue, start the Kafka Connector MQ source, to move data to Event Streams topic, then
do the kafka streams processing.
Run with gitops on openshift
In this approach, we propose to use a GitOps repository and deploy the solution using few scripts and oc CLI commands.
In the figure below, all the components are deployed with OpenShift GitOps. The blue components are IBM product components like Event Streams and MQ operators and some other operators, like Elastic Search.
The green rectangles represent the microservices and kafka connectors source or sink deployed as part of the solution.
See next guided tour for GitOps approach.
Use Case Guided Tour
Bootstrap GitOps
Bootstrapping GitOps is mostly to install the MQ, Event Streams, APIC Connect, OpenShift Gitops, and ElasticSearch operators, and do any pre-requisites like entitlement keys.
We prefer to keep the bootstrap instructions in the source repository, therefore follow the up to date instructions from the gitops main readme.
Deploy the Solution
Once operators are deployed.
Deploying the full solution is by starting ArgoCD app of apps:
oc apply -k config/argocdAccess the OpenShift GitOps (ArgoCD) console
chrome https://$(oc get route openshift-gitops-server -o jsonpath='{.status.ingress[].host}' -n openshift-gitops)
The expected set of ArgoCD apps looks like (and all should be green):
rt-inventory-Argo-app is an app of apps
rt-inventory-dev-env is for the rt-inventory-dev namespace
rt-inventory-dev-services is for event streams, kafka connect cluster and mq deployments in dev-env namespace
rt-inventory-store-simulator-app is for the simulator app used in the demo.
rt-inventory-item-inventory for the item aggregator application
rt-inventory-store-inventory for the store aggregator application
rt-inventory-dev-eepm-service for Event End Point management
rt-inventory-dev-elastic-svc for Elastic Search deployment
rt-inventory-dv-kibana-svc for Kibana
Verify pods
oc project rt-inventory-devoc get podsNAME READY STATUS RESTARTS AGEdev-kafka-cruise-control-6d6bf8b774-99rwl 2/2 Running 0 4ddev-kafka-entity-operator-75f7bc8f5c-x4vkt 3/3 Running 0 4ddev-kafka-kafka-0 1/1 Running 0 4ddev-kafka-kafka-1 1/1 Running 0 4ddev-kafka-kafka-2 1/1 Running 0 4d