Skip to content

rhdhorchestrator/orchestrator-demo

Folders and files

NameName
Last commit message
Last commit date

Latest commit

b0991f9 · Feb 12, 2025

History

47 Commits
Feb 12, 2025
Feb 12, 2025
Jan 22, 2025
Feb 3, 2025
Feb 12, 2025
Jan 27, 2025
Feb 12, 2025
Jan 9, 2025
Feb 12, 2025

Repository files navigation

Orchestrator demo

This repository contains the source code of workflows we use for demo.

It also contains scripts used to build and push the image of the workflow and to generate the associated manifests in order to deploy the workflows in an OCP cluster.

Pre-requisites

Repository structure

  • Folders starting with 0*_ are the folders containing the workflow projects in Quarkus layout
  • The resources folder contains
    • the Dockerfile used to build the workflow images
    • a Deployment manifest to deploy a proxy application
    • a Route manifest to allow access to the DataIndex graphQL endpoint. Note that to access the route, we must delete the NetworkPolicies
  • The scripts folder contains the scripts used to build and push the workflow image and to generate the manifests used to deploy the workflow.

Getting started

The workflows projects were create using the kn-workflow cli by running:

kn-workflow quarkus create --name <specify project name, e.g. 00_new_project>

Edit the workflow, add schema and spec files and run it locally from project's folder with:

kn-workflow quarkus run

Workflow images

For running the workflow locally (with kn-workflow run), the following image is pulled:

registry.redhat.io/openshift-serverless-1/logic-swf-devmode-rhel8:1.35.0

For building the workflow image, the following images are pulled:

registry.redhat.io/openshift-serverless-1/logic-swf-builder-rhel8@sha256:5590b799420769ee2fe316bc0425bec10f7a29433765244702a23348150e621e
registry.access.redhat.com/ubi9/openjdk-17:1.21-2

References