From c3d305e0e222b3382d5feaedf15b5c1cf914dcb5 Mon Sep 17 00:00:00 2001
From: clearml <>
Date: Thu, 16 Jan 2025 12:04:43 +0200
Subject: [PATCH] Update GitHub repo
---
LICENSE | 2 +-
README.md | 45 +++++++++------------------------------------
apiserver/LICENSE | 2 +-
fileserver/LICENSE | 2 +-
4 files changed, 12 insertions(+), 39 deletions(-)
diff --git a/LICENSE b/LICENSE
index b71ce66..19931a1 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,7 +1,7 @@
Server Side Public License
VERSION 1, OCTOBER 16, 2018
- Copyright © 2024 ClearML Inc.
+ Copyright © 2025 ClearML Inc.
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
diff --git a/README.md b/README.md
index 4caaf5a..13a971c 100644
--- a/README.md
+++ b/README.md
@@ -7,42 +7,15 @@
[](https://img.shields.io/badge/license-SSPL-green.svg)
[](https://img.shields.io/badge/python-3.9-blue.svg)
-[](https://img.shields.io/github/release-pre/allegroai/trains-server.svg)
-[](https://artifacthub.io/packages/search?repo=allegroai)
+[](https://img.shields.io/github/release-pre/clearml/trains-server.svg)
+[](https://artifacthub.io/packages/search?repo=clearml)
----
-
-
-**Note regarding Apache Log4j2 Remote Code Execution (RCE) Vulnerability - CVE-2021-44228 - ESA-2021-31**
-
-
-
-According to [ElasticSearch's latest report](https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476),
-supported versions of Elasticsearch (6.8.9+, 7.8+) used with recent versions of the JDK (JDK9+) **are not susceptible to either remote code execution or information leakage**
-due to Elasticsearch’s usage of the Java Security Manager.
-
-**As the latest version of ClearML Server uses Elasticsearch 7.10+ with JDK15, it is not affected by these vulnerabilities.**
-
-As a precaution, we've upgraded the ES version to 7.16.2 and added the mitigation recommended by ElasticSearch to our latest [docker-compose.yml](https://github.com/allegroai/clearml-server/blob/cfccbe05c158b75e520581f86e9668291da5c70a/docker/docker-compose.yml#L42) file.
-
-While previous Elasticsearch versions (5.6.11+, 6.4.0+ and 7.0.0+) used by older ClearML Server versions are only susceptible to the information leakage vulnerability
-(which in any case **does not permit access to data within the Elasticsearch cluster**),
-we still recommend upgrading to the latest version of ClearML Server. Alternatively, you can apply the mitigation as implemented in our latest
-[docker-compose.yml](https://github.com/allegroai/clearml-server/blob/cfccbe05c158b75e520581f86e9668291da5c70a/docker/docker-compose.yml#L42) file.
-
-**Update 15 December**: A further vulnerability (CVE-2021-45046) was disclosed on December 14th.
-ElasticSearch's guidance for Elasticsearch remains unchanged by this new vulnerability, thus **not affecting ClearML Server**.
-
-**Update 22 December**: To keep with ElasticSearch's recommendations, we've upgraded the ES version to the newly released 7.16.2
-
----
-
## ClearML Server
#### *Formerly known as Trains Server*
-The **ClearML Server** is the backend service infrastructure for [ClearML](https://github.com/allegroai/clearml).
+The **ClearML Server** is the backend service infrastructure for [ClearML](https://github.com/clearml/clearml).
It allows multiple users to collaborate and manage their experiments.
**ClearML** offers a [free hosted service](https://app.clear.ml/), which is maintained by **ClearML** and open to anyone.
In order to host your own server, you will need to launch the **ClearML Server** and point **ClearML** to it.
@@ -124,9 +97,9 @@ In order to set up the **ClearML** client to work with your **ClearML Server**:
it will be inferred from the http/s scheme.
After launching the **ClearML Server** and configuring the **ClearML** client to use the **ClearML Server**,
-you can [use](https://github.com/allegroai/clearml) **ClearML** in your experiments and view them in your **ClearML Server** web server,
+you can [use](https://github.com/clearml/clearml) **ClearML** in your experiments and view them in your **ClearML Server** web server,
for example http://localhost:8080.
-For more information about the ClearML client, see [**ClearML**](https://github.com/allegroai/clearml).
+For more information about the ClearML client, see [**ClearML**](https://github.com/clearml/clearml).
## ClearML-Agent Services
@@ -143,7 +116,7 @@ increased data transparency)
ClearML-Agent Services container will spin **any** task enqueued into the dedicated `services` queue.
Every task launched by ClearML-Agent Services will be registered as a new node in the system,
providing tracking and transparency capabilities.
-You can also run the ClearML-Agent Services manually, see details in [ClearML-agent services mode](https://github.com/allegroai/clearml-agent#clearml-agent-services-mode-)
+You can also run the ClearML-Agent Services manually, see details in [ClearML-agent services mode](https://github.com/clearml/clearml-agent#clearml-agent-services-mode-)
**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, as it will put unnecessary load on the server.
@@ -166,7 +139,7 @@ To restart the **ClearML Server**, you must first stop the containers, and then
## Upgrading
-**ClearML Server** releases are also reflected in the [docker compose configuration file](https://github.com/allegroai/trains-server/blob/master/docker/docker-compose.yml).
+**ClearML Server** releases are also reflected in the [docker compose configuration file](https://github.com/clearml/trains-server/blob/master/docker/docker-compose.yml).
We strongly encourage you to keep your **ClearML Server** up to date, by keeping up with the current release.
**Note**: The following upgrade instructions use the Linux OS as an example.
@@ -199,7 +172,7 @@ To upgrade your existing **ClearML Server** deployment:
1. Download the latest `docker-compose.yml` file.
```bash
- curl https://raw.githubusercontent.com/allegroai/trains-server/master/docker/docker-compose.yml -o docker-compose.yml
+ curl https://raw.githubusercontent.com/clearml/trains-server/master/docker/docker-compose.yml -o docker-compose.yml
```
1. Configure the ClearML-Agent Services (not supported on Windows installation).
@@ -227,7 +200,7 @@ To upgrade your existing **ClearML Server** deployment:
If you have any questions, look to the ClearML [FAQ](https://clear.ml/docs/latest/docs/faq), or
tag your questions on [stackoverflow](https://stackoverflow.com/questions/tagged/clearml) with '**clearml**' tag.
-For feature requests or bug reports, please use [GitHub issues](https://github.com/allegroai/clearml-server/issues).
+For feature requests or bug reports, please use [GitHub issues](https://github.com/clearml/clearml-server/issues).
Additionally, you can always find us at *clearml@allegro.ai*
diff --git a/apiserver/LICENSE b/apiserver/LICENSE
index b71ce66..19931a1 100644
--- a/apiserver/LICENSE
+++ b/apiserver/LICENSE
@@ -1,7 +1,7 @@
Server Side Public License
VERSION 1, OCTOBER 16, 2018
- Copyright © 2024 ClearML Inc.
+ Copyright © 2025 ClearML Inc.
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
diff --git a/fileserver/LICENSE b/fileserver/LICENSE
index b71ce66..19931a1 100644
--- a/fileserver/LICENSE
+++ b/fileserver/LICENSE
@@ -1,7 +1,7 @@
Server Side Public License
VERSION 1, OCTOBER 16, 2018
- Copyright © 2024 ClearML Inc.
+ Copyright © 2025 ClearML Inc.
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.