5S-TES DemoStack Quickstart

Start the starter.sh automation scripts

The DemoStack includes a starter.sh automation script that automates the initial setup process. This script will:

1. Start all Docker Compose services in SeedDemoData = true to seed the demo data and instances.
2. Install and configure the MinIO client (mc).
3. Fetch MinIO access keys for Funnel, which is chosen as the TES executor for the DemoStack quickstart.
4. Installs and setup the Funnel for executing the TES tasks.
5. Generate the Funnel configuration file.
6. Start the Funnel TES server.

Follow these steps to run the starter.sh automation script:

• Within the 5S-TES-deployment root directory, change to the DemoStack directory:

  cd DemoStack
• Give permission to execute the starter.sh automation script:

  chmod +x scripts/starter.sh
  The command above only requires if you run this for the first time.

• Run the starter.sh automation script:

  ./scripts/starter.sh

This will start the stack with the seeding of some demo data and instances.

Wait until all the services are up and running and the starter.sh script shows the following message in the terminal. The status of the services can be checked by running docker stats in a new terminal window.

...
Creating funnel-config.yml...
Starting Funnel...
server               Server listening
httpPort             8000
rpcAddress           :9090
time                 2026-02-25T12:47:16Z

Username: globaladminuser
Password: password123

Approve the Project access to the TRE

Follow this guide to approve the project access to the TRE.

To make sure that the project has been approved and Submission Layer is in sync with TRE Agent, log into the Submission Layer at localhost:7220, using the Keycloak credentials above. Select the project, and navigate to the TREs section. You should see Approved status for the TRE.

Prepare to send the first submission

To send the first submission, you need to disable simulation mode in DemoStack by doing the following:

• Set SeedDemoData to false
• Set UseTESK to true

This can be done manually by editing the .env file and restarting the Docker Compose services or by running the submission-ready.sh automation script.

Follow these steps to run the submission-ready.sh automation script:

1. Open a new terminal window and navigate to the DemoStack directory:

cd DemoStack

2. Give permission to execute the submission-ready.sh automation script:

chmod +x scripts/submission-ready.sh

3. Run the submission-ready.sh automation script:

./scripts/submission-ready.sh

This script will automatically do the required configuration changes, make the stack ready for submission and restart the Docker Compose services.

Send a Hello World submission

The Hello World TES task is a simple submission that is used to demo the DemoStack.

1. Login to the Submission Layer at localhost:7220 using the Keycloak credentials above (if you didn’t already)

2. Go to the Projects page.

3. From the list of projects select the Testing project.

4. Once in the Testing project go to Submissions -> Create Submission -> TES Wizard.

5. On the TES Wizard page select Submission Mode -> Raw JSON

6. Enter the following payload, then click Submit TES Task:

{
  "state": 0,
  "name": "Hello World",
  "inputs": [],
  "outputs": [
    {
      "name": "Stdout",
      "description": "Stdout results",
      "url": "s3://",
      "path": "/outputs",
      "type": "DIRECTORY"
    }
  ],
  "executors": [
    {
      "image": "ubuntu",
      "command": ["echo", "Hello World"],
      "workdir": "/outputs",
      "stdout": "/outputs/stdout"
    }
  ],
  "volumes": null,
  "tags": {
    "project": "Testing",
    "tres": "DEMO"
  },
  "logs": null,
  "creation_time": null
}

This submits a simple task that:

• launches an ubuntu container and executes echo Hello World (“executors” section)
• captures the container output in a file and saves it to the /outputs folder in MinIO (“outputs” section)

Tracking and approving the submission results

You will be redirected to the list of Submissions, click onto the submission you just sent.

You should be able to see the status of the submission. Once it has been processed, the status will be set to: Requested Egress. This means that the results are waiting for egress approval. Follow this guide to approve the submission results.

View the submission results

Once the Egress request has been approved, you can view the results in the Submission Layer’s output bucket.

The final successful process should be like this: