I think all relevant env variables are in the docker compose. You can spin different APIservers on different machines without elastic/mongo/redis and then point them to the relevant machines that have those services running

Yes i know i can do that, but if all APIservers have access to the same data, then every user will be able to see the experiments of all servers.
Am i missing something here?

Yeah I think you're right. You're basically looking for a capability to segregate users into groups so they won't have visibility between themselves?

Yes I am trying to solve the authorization problem by creating multiple clearML servers but i want to avoid having one elastic search per server.
The users of each clearML server must have access to experiments of that specific server.
Imagine that each clearml server will have users belonging to the same group/team

Role based access controls are supported only in Scale/Enterprise versions.

Yes, that's why I am trying to find alternatives. I know i can't have one tenant with role-based access and I was thinking if there was another way to implement a similar functionality

ok I will think about. Thanks again

Hi @<1582904426778071040:profile|SteepBat69> , that's an interesting question. In theory I think it should be possible

I would suggest considering a Scale/Enterprise license. The amount of time you would be wasting in man hours on managing, doing hacks and patches on this and various other capabilities would most likely cost you in the long run much more than a license. Not to mention the dedicated support and other features you would be receiving.

hi @<1523701070390366208:profile|CostlyOstrich36> thanks for replying.
Yes but the different clearml instances must be isolated somehow. I mean that in other databases like postgresql, you can define multiple schemas or even different databases. What about elasticsearch? I'm not experienced with it.
Is there any other environment variable related to elastic except from the ones defined in the compose?(CLEARML_ELASTIC_SERVICE_HOST, CLEARML_ELASTIC_SERVICE_PORT, CLEARML_ELASTIC_SERVICE_PASSWORD)