Skip to content
New issue

AMS Workflow scheduler

Past due by 11 months 40% complete

Over the last months we have developed the core individual parts of AMS, namely the C++ library, the ams-stager, data base API, file accessors and, example training scripts. All of these are glued together by ad-hoc scripts to test the individual functionalities. We need to provide a mechanism to clearly deploy a workflow of a single AMS enable applicatio…

Over the last months we have developed the core individual parts of AMS, namely the C++ library, the ams-stager, data base API, file accessors and, example training scripts. All of these are glued together by ad-hoc scripts to test the individual functionalities. We need to provide a mechanism to clearly deploy a workflow of a single AMS enable application instance.

We need to provide a mechanism to deploy all of those individual pieces and correctly connect them to have an end-to-end execution. To get us there we need the following pieces:

  1. Clean AMS-(Surrogate + UQ) interface.
  2. Reliable RMQ connection + understanding of scaling/number of clients.
  3. AMSlib extension to instantiate a AMSManager::singleton which provides references to the database directories and to all the models.
  4. A workflow manager that instantiates all the respective jobs in a flux allocation.
Loading