ClearML/clearml-server
1
0
Fork 0
mirror of https://github.com/clearml/clearml-server synced 2025-02-07 05:27:23 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Allegro AI 2020-06-02 00:36:35 +03:00 committed by GitHub
parent 3f8d5bc346
commit f31526042d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@ -102,17 +102,22 @@ For more information about the Trains client, see [**Trains**](https://github.co
## Trains-Agent Services <a name="services"></a>
*Trains-Agent Services* provides the ability to launch long lasting jobs that previously had to be
executed on local / dedicated machines. To name a few use cases, auto-scaler service (spinning instances
Starting v0.15 *trains-server* deployment includes a *trains-agent services* container running as
part of the docker container collection on the machine.
*Trains-Agent Services* is an extension of *Trains-Agent* that provides the ability to launch long-lasting jobs
that previously had to be executed on local / dedicated machines. It allows a single agent to
launch multiple dockers (Tasks) for different use cases. To name a few use cases, auto-scaler service (spinning instances
when the need arises and the budget allows), Controllers (Implementing pipelines and more sophisticated DevOps logic),
Optimizer (such as Hyper-parameter Optimization or sweeping), and Application (such as interactive Bokeh apps for
increased data transparency)
Technically speaking *Trains-Agent Services* is an extension of *Trains-Agent* that adds the ability to
launch multiple dockers (Tasks) from the same running agent.
Every launched Task will be registered as a new Node in the system and will track its own progress.
**Notice!** *Trains-Agent Services* will spin **any** Task enqueued into the `services` queue,
it is the users responsibility to make sure the proper Tasks are pushed into the services queue.
*Trains-Agent Services* container will spin **any** Task enqueued into the dedicated `services` queue.
Every Task launched by *Trains-Agent Services* will be registered as a new Node in the system,
providing tracking and transparency capabilities.
**Note**: It is the user's responsibility to make sure the proper Tasks are pushed into the `services` queue.
Do not enqueue training / inference Tasks into the `services` queue, it will put unnecessary load on the server.
## Advanced Functionality