ivoa / cirasa-planner Goto Github PK

View Code? Open in Web Editor NEW

0.0 12.0 2.0 5.8 MB

Use case and prototype ExecutionPlanner for the CIRASA visualization tools

License: GNU General Public License v3.0

Java 18.34% Python 81.21% Dockerfile 0.13% Shell 0.32%

cirasa-planner's Introduction

CIRASA-planner

Use case and prototype ExecutionPlanner for the CIRASA visualization tools

cirasa-planner's People

Contributors

Watchers

Forkers

zarquan molinaro-m

cirasa-planner's Issues

Move started and completed to the message log

If we move Execution started and completed to the message log we don't need them as explicit properties.

Offerset access method

Add a webservice method to access an offerset.

/offerset/{ident}

Move Spring projects into a sub directory

Current structure

\- java
     | 
     +- chatgpt
     |
     +- spring-openapi
     |
     \- spring-webapp

Target structure

\- java
     | 
     +- chatgpt
     | 
     \- spring
           |
           +- spring-openapi
           |
           \- spring-webapp

Move result to the start of OffersResponse

Just for human readability, put the [YES|NO] result at the top of the response.

Log messages for compute, storage and data resources.

Based on Message Templates
https://messagetemplates.org/

Combine offer and execution status

Combine the offer and execution status values.

From offer:

OFFERED
ACCEPTED
REJECTED
EXPIRED

From execution:

WAITING
STANDUP
RUNNING
TEARDOWN
COMPLETED
CANCELLED
FAILED

From the ExecutionBroker document:

PENDING The job has been created, but the resources have not be prepared yet.
SETUP The ExecutionWorker service is setting up the resources needed to execute the job. This includes things like staging any datasets that will be needed locally.
READY The job is ready and waiting to start.
RUNNING The job is running.
TEARDOWN The execution has finished and the ExecutionWorker service is clearing up the resources that were used. This includes things like transferring the results to permanent storage and releasing local resources.
COMPLETED The job has been completed.
FAILED The job failed to complete.
CANCELLED The job was cancelled.

Move `expires` to the offerset

The execution/offer needs to have a uuid

All the resources have uuids, the executable has a uuid, but the execution itself doesn't.
That's the one thing that is referenced in a wesbervice path /execution/{uuid}, and we don't assign it a uuid.

Java Spring generator represents YES and NO as TRUE and FALSE

Include a 'this' pointer for an execution.

Include a 'this' pointer for an execution in the execution status response.

Move the Python projects into subdirectories based on generator

Create separate directories for the Koxudaxi FastAPI generator and the OpenAPITools generator

Execution belongs to an offerset

Execution belongs to a group or offerset, needed to find and REJECT the other offers in the same set them when one of them is ACCEPTED.

An offerset needs to have a uuid identifier to access it.
The service needs an /offerset/{uuid} endpoint to list the members of the set.
An execution needs a reference back to its parent offerset