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
Can Anyone Please Help Me To Understand What I'M Missing On How To Run An Ml Experiment Using Clearml-Agent Deployed In The Cluster? Here Are The Steps I Followed Considering That I'M Connected To The Cluster: 1. I Installed The Clearml Agent Helm Chart,

can anyone please help me to understand what i'm missing on how to run an ML experiment using ClearML-Agent deployed in the cluster?
Here are the steps I followed considering that I'm connected to the cluster:

  1. I installed the ClearML agent Helm chart, and now I have the ClearML agent running in the "clearml" namespace.
  2. After that, I ran the script from the following GitHub repository: None
  3. I used the command python k8s_glue_example.py --namespace clearml --queue default or python k8s_glue_example.py --namespace clearmlto
  4. going to the web UI, right click the experiment, click on clone and then enqueue the experiment to k8s glue queue

unfortunately, it didn't execute the experiment on my Kubernetes ClearML agent

  
  
Posted one year ago
Votes Newest

Answers 4


@<1523701087100473344:profile|SuccessfulKoala55> never mind I found the answer to use task.execute_remotely .. ty

  
  
Posted one year ago

@<1523701087100473344:profile|SuccessfulKoala55> Thanks for the clarification; it helped! Is there a way to run directly on the k8s agent using the CLI or another method without cloning an existing task and enqueuing it?

  
  
Posted one year ago

Additionally, the k8s glue queue is internal to the operation of the agent and used as an intermediate queue. The agent spawned by the chart monitors a different queue, usually the default queue

  
  
Posted one year ago

@<1595587997728772096:profile|MuddyRobin9> , the helm chart already runs the agent, that script is not relevant for a k8s cluster

  
  
Posted one year ago