Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hi, I'D Like To Know If It'S Possible To Change The Artifact File Path That Is Shown In The Ui. I'D Need This Because I Have Clearml Agents That Are Running In The Same Vpc Of The Server, So They Use The Internal Dns For The Api Server And Files Server An

Hi, I'd like to know if it's possible to change the artifact FILE PATH that is shown in the UI. I'd need this because I have clearml agents that are running in the same VPC of the server, so they use the internal dns for the api server and files server and, therefore, when I upload an artifact to the clearml server the file path will contain the internal DNS. In this way, however, I'm unable to download the artifact from the UI, where I should use, instead, the external path to the internet-facing load balancer that exposes the webserver, apiserver and fileserver. The clearml server is deployed on AWS EKS with helm and the chart I'm using is https://allegroai.github.io/clearml-server-helm/

  
  
Posted 2 years ago
Votes Newest

Answers 2


Hi AgitatedDove14 , thank you for your answer!
At the moment I can't configure both internal/external with the same dns. Before changing the server infrastructure, i'm trying a workaround where I upload the artifact with the internal file server path, and then I upload a string artifact which is the first artifact url where I replace the internal dns with the external dns, and use it to download the artifact from the UI.

  
  
Posted 2 years ago

Hi LovelyHamster1
That is a good point, I think the safest / robust way is to configure both to use the same dns name/s so both (internal/external) are accessible.
Some background, the URL itself on the artifact is basically a standalone, once registered on the Task, the UI will not replace it but use it as is (The UI has no "understanding" on which server it is, it will just fetch the file).
Are you also using a diff port on the load balancer ?
(because the easiest fix is on your external remote machine to define the hosts file so that the "internal_files_server" is resolved to the external IP (e.g. "11.22.33.44")

  
  
Posted 2 years ago
688 Views
2 Answers
2 years ago
one year ago
Tags
Similar posts