Hello,
I tried this program, following the read of the paper.
I got stuck in run.sh ...
My output is this

2023-05-30 00:07:39.437 INFO 2959466 --- [ main] t.d.c.controller.ControllerApplication : Starting ControllerApplication v0.1-SNAPSHOT using Java 11.0.19 on ubuntu with PID 2959466 (/root/COFFEE/controller/target/controller-0.1-SNAPSHOT.jar started by root in /root/COFFEE/utils)
2023-05-30 00:07:39.441 DEBUG 2959466 --- [ main] t.d.c.controller.ControllerApplication : Running with Spring Boot v2.6.4, Spring v5.3.16
2023-05-30 00:07:39.442 INFO 2959466 --- [ main] t.d.c.controller.ControllerApplication : No active profile set, falling back to 1 default profile: "default"
2023-05-30 00:07:40.350 INFO 2959466 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2023-05-30 00:07:40.456 INFO 2959466 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 95 ms. Found 7 JPA repository interfaces.
2023-05-30 00:07:41.243 INFO 2959466 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
2023-05-30 00:07:41.259 INFO 2959466 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2023-05-30 00:07:41.259 INFO 2959466 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.58]
2023-05-30 00:07:41.327 INFO 2959466 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2023-05-30 00:07:41.328 INFO 2959466 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 1804 ms
2023-05-30 00:07:41.849 INFO 2959466 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default]
2023-05-30 00:07:41.959 INFO 2959466 --- [ main] org.hibernate.Version : HHH000412: Hibernate ORM core version 5.6.5.Final
2023-05-30 00:07:42.174 INFO 2959466 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.1.2.Final}
2023-05-30 00:07:43.053 INFO 2959466 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.MySQL57Dialect
2023-05-30 00:07:44.377 INFO 2959466 --- [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
2023-05-30 00:07:44.394 INFO 2959466 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
2023-05-30 00:07:45.342 INFO 2959466 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ''
2023-05-30 00:07:45.359 INFO 2959466 --- [ main] t.d.c.controller.ControllerApplication : Started ControllerApplication in 6.528 seconds (JVM running for 7.329)
2023-05-30 00:07:48.174 INFO 2959466 --- [nio-8080-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring DispatcherServlet 'dispatcherServlet'
2023-05-30 00:07:48.175 INFO 2959466 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet'
2023-05-30 00:07:48.177 INFO 2959466 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet : Completed initialization in 2 ms
2023-05-30 00:07:48.221 INFO 2959466 --- [ Thread-1] t.d.coffee.controller.TestExecutor : Starting parsing script...
2023-05-30 00:07:48.231 INFO 2959466 --- [ Thread-1] t.d.coffee.controller.TestExecutor : Finished script parsing
Start successfulroot@ubuntu:~/COFFEE/utils# 2023-05-30 00:07:49.270 INFO 2959466 --- [ Thread-1] t.d.coffee.controller.TestExecutor : starting the procedures
2023-05-30 00:07:49.273 INFO 2959466 --- [ Thread-1] t.d.coffee.controller.TestExecutor : waiting for all procedures to finish
2023-05-30 00:07:49.281 INFO 2959466 --- [ Thread-3] t.d.c.c.procedure.BaseProcedure : Executing procedure : 1 / 1
2023-05-30 00:07:49.296 INFO 2959466 --- [ Thread-3] t.d.c.c.procedure.ProcedureQueue : adding 1 futures to start queue
2023-05-30 00:07:49.546 INFO 2959466 --- [nio-8080-exec-2] t.d.c.c.m.controller.CommandController : Added 1 command start times to START queue

and never completes.
If i try to manually curl the localhost again I have this:
2023-05-30 00:09:50.046 INFO 2959466 --- [ Thread-4] t.d.coffee.controller.TestExecutor : Starting parsing script...
2023-05-30 00:09:50.051 INFO 2959466 --- [ Thread-4] t.d.coffee.controller.TestExecutor : Finished script parsing
2023-05-30 00:09:50.315 WARN 2959466 --- [ Thread-4] t.d.c.c.o.kubernetes.KubernetesClient : ApiException occured, try reconnect
Exception in thread "Thread-4" java.lang.IllegalStateException: API Exception while accessing createNamespacedDeployment Kubernetes client API:

    at tools.descartes.coffee.controller.orchestrator.kubernetes.KubernetesClient.throwApiException(KubernetesClient.java:284)
    at tools.descartes.coffee.controller.orchestrator.kubernetes.KubernetesClient.callAPI(KubernetesClient.java:275)
    at tools.descartes.coffee.controller.orchestrator.kubernetes.KubernetesClient.createDeployment(KubernetesClient.java:200)
    at tools.descartes.coffee.controller.orchestrator.kubernetes.KubernetesClient.init(KubernetesClient.java:78)
    at tools.descartes.coffee.controller.TestExecutor.startUp(TestExecutor.java:89)
    at tools.descartes.coffee.controller.TestExecutor.run(TestExecutor.java:59)
    at java.base/java.lang.Thread.run(Thread.java:829)

Caused by: io.kubernetes.client.openapi.ApiException:
at io.kubernetes.client.openapi.ApiClient.handleResponse(ApiClient.java:973)
at io.kubernetes.client.openapi.ApiClient.execute(ApiClient.java:885)
at io.kubernetes.client.openapi.apis.AppsV1Api.createNamespacedDeploymentWithHttpInfo(AppsV1Api.java:683)
at io.kubernetes.client.openapi.apis.AppsV1Api.createNamespacedDeployment(AppsV1Api.java:648)
at tools.descartes.coffee.controller.orchestrator.kubernetes.KubernetesClient.lambda$createDeployment$7(KubernetesClient.java:201)
at tools.descartes.coffee.controller.orchestrator.kubernetes.KubernetesClient.callAPI(KubernetesClient.java:269)
... 5 more

I followed the guide but I am not sure on how to set the following parameters:
ipForLoadAndProxy
all kubernetes.naming
controllerIp

My config is currently this one:

-----------------------------------------

SPECIFIC CONFIGURATION FOR THE CONTROLLER

general settings

controller.exportResults=true
adntroller.reportDirectory=reports
controller.testScript=../test-sequence.script
controller.initialReplicas=0
controller.proxyReplicas=1
controller.networkingTimeoutSeconds=60
controller.database.address=127.0.0.1
controller.database.port=3306

loadgenerator settings

loadgenerator.jarfile=httploadgenerator.jar
loadgenerator.userprofile=loadgenerator/service-user-profile.yaml
loadgenerator.intensityFile=NULL
loadgenerator.requestsPerSec=50
loadgenerator.durationSeconds=6000
loadgenerator.loggingFile=loadout.csv
loadgenerator.requestLoggingFile=loadrequestsout.csv

cluster settings

cluster.orchestrator=kubernetes
cluster.ip=10.96.0.1
cluster.port=443
cluster.controllerIp=10.244.0.100
cluster.proxyNodeName=master
cluster.appContainerPort=8080
cluster.appHealthCheck=true

--- AUTOMATIC CONFIG AT BUILD TIME ---

cluster.appImage=someowner/somerepo:test-app-tag_2022-08-06_15-52
cluster.proxyImage=someowner/somerepo:test-app-tag_proxy_2022-05-24_09-07
cluster.updateImage=someowner/somerepo:test-app-tag_update_2022-08-06_15-54

--- END AUTOMATIC CONFIG AT BUILD TIME ---

kubernetes settings

kubernetes.kubeConfigFile=/root/.kube/config
kubernetes.ipForLoadAndProxy=10.0.2.15
kubernetes.applicationNodePort=30007
kubernetes.proxyNodePort=30006
kubernetes.naming.prefix=of-testing-
kubernetes.naming.proxyDeployment=proxy-deployment
kubernetes.naming.proxyService=proxy-service
kubernetes.naming.proxyLabel=proxy-label
kubernetes.naming.namespace=namespace
kubernetes.naming.label=label
kubernetes.naming.deployment=deployment
kubernetes.naming.service=service
kubernetes.naming.container=container
kubernetes.naming.port=port
kubernetes.update.strategy=RollingUpdate
kubernetes.update.maxSurge=25%
kubernetes.update.maxUnavailable=25%

-----------------------------------------

GENERAL AND SPRING PROPERTIES

logging.level.tools.descartes.coffee.controller=TRACE

server.port=8080

spring.jpa.show-sql=true
spring.jpa.properties.hibernate.dialect=org.hibernate.dialect.MySQL5Dialect
spring.jpa.hibernate.naming.physical-strategy=org.hibernate.cfg.ImprovedNamingStrategy

none: The default for MySQL. No change is made to the database structure.

update: Hibernate changes the database according to the given entity structures.

create: Creates the database every time but does not drop it on close.

create-drop: Creates the database and drops it when SessionFactory closes.

spring.jpa.hibernate.ddl-auto=create

Any clue?
Best.

Currently, application.properties file (especially controller) contains all settings. As best practice, property files should be splitted and documented.

At the moment, results are stored in the database and a summary is printed to the console. For a user it would be nice to have visualization of the results and support for post-processing.

At the moment, crash, health, restart commands are executed deterministically. Support for command execution within an interval (random timing) should be supported in future.

Create Markdown file with step-by-step example

Log outputs in all modules should be standardized and refactored

Tests required for all modules

Separate orchestrator packages in separate modules.
Have to check how to start and compile the framework then.

Console and CSV exporter/reporter need review and deep refactoring. Not all metrics (e.g. command specifics for update/crash) are not reported.

At the moment, generic metrics are measured and saved to the databases. In future, we should support also orchestrator-specific metrics (e.g. from logs or monitoring servers) and include them in the result database and controller.

At the moment, load intensity has to be specified before the experiment. In future, we should support adaptive load, i.e., load should adapt automatically to the test clusters size.

Support units as seconds for delays/offsets etc.