search

JeffersonLab / jiriaf-0.1

3 stars 1 forks source link

JCS design and development #10

Open gurjyan opened 11 months ago

gurjyan commented 11 months ago

Formulate and engineer the central service (JCS) with the following functionalities: a) Examine the resources database table formulated by SWIF2 and forward a SWIF2 request to initiate JRM and allocate resources. b) Once a facility meets the SWIF2 requests and the JRM is operational, populate the available resources database table for JIRIAF. It is presupposed that an appropriate schema for this table has been defined, encompassing details such as the facility, wall time, cores, and memory, among others.

gurjyan commented 11 months ago

Information about the actively running JRMs (i.e., vk) we will get from the k8s App server resident in the JCS.

gurjyan commented 11 months ago

In other words: a) Retrieve data from the SWIF "potential resources" database table. b) Launch a Kubernetes (k8s) node on any idle resources. c) Record the availability of these resources in the "available resources" table once the Kubernetes API server confirms that the node is operational. This might involve setting up a separate thread that regularly communicates with the Kubernetes API server to monitor node statuses and keep the "available resources" table current.