Sorry AgitatedDove14 can you bump me to that thread?

Hi, any idea if i can acheive this? I just need a list of usernames.

Thanks TimelyPenguin76 , is there an env var for the S3 connection as well?

Thanks this would be a good alternative before the enterprise version comes in. How is this different from argparser btw?

Nice, what are the names of the talks?

ok thanks. this would mean that increasing the disk space for my ClearML is the only option as we are not at liberty to delete.

Thanks. Have a better understanding now.

Hi, by deployment strategies I meant by canary, blue-green...etc..etc. I figured this should be done by clearml-serving and maybe seldon as well.

the hackathon is 3 days.

Hi SuccessfulKoala55 , just wondering how i can follow up on this.

what feature on this paid roadmap are you referring to? I am indeed communicating with Noem on paid features.

Share data across R&D teams with searchable data catalogs available on any environment.

That didn't work as well...

Thank. Gonna try that out. But i hit another snag. Strangely, the Agent is not creating the right venv. This is what the Agent created.
` pip:

• asn1crypto==0.24.0
• attrs==20.3.0
• certifi==2020.12.5
• chardet==4.0.0
• cryptography==2.1.4
• Cython==0.29.22
• furl==2.1.0
• future==0.18.2
• humanfriendly==9.1
• idna==2.6
• importlib-metadata==3.7.0
• jsonschema==3.2.0
• keyring==10.6.0
• keyrings.alt==3.0
• orderedmultidict==1.0.1
• pathlib2==2.3.5
• psutil==5.8.0
• pycrypto==2.6.1
• pygobject...

can you please verify that you have all the required packages installed locally ?

Its not installed on the image that runs the experiment. But its reflected in the requirements.txt.

what is the setting of 

agent.package_manager.system_site_packages

True.

thanks. That seems to work. I got a question, does it save the best model or the model in the last epoch?

Ok let me try that.

Hi, it make sense to automate this part just like how you automate the rest of the MLOps flow, especially when you already support Data Versioning/Lineage, Data Provenance (How it works with the experiment and as a model source) should be in too. Although i agree technically it's probably not possible to tell if the users actually used the indicated datasets after they do a datasets.get_copy() .

yes, previously run experiments. I will just kill clearml-elastic container if that may solve the problem.

docker exec clearml-elastic curl zsh: no matches found:

Yeah me 3.

So the context I'm asking is I realise I'll need to catalogue all the dataset ids created by ppl separately on a spreadsheet. And for each experiment, I'll need to go into the code commit to see which id is being used. But on the other hand, I thought I've seen advertised use cases where the experiment can be directly linked to the dataset id being used. The brain's a bit rusty to recall how it was done.

Okay this part I missed, why would you need to add additional "catalog" when you have the UI?

Yeah this is the part i am trying to reconcile. I don't see any UI for datasets, Or is this a feature of hyperdatasets and i just mixed them up.

Next step to figure out if i can do all that in the python code instead of UI.

thanks.

yah i got that too. This happens when i run the client code on the same machine as the clearml-agent. So i'm wondering if sharing the same clearml.conf cause that problem. Is there a way to specify the clearml.conf instead of defaulting to ~/clearml.conf?

Thanks. This appears to be solely for web UI and API, What if i want to orchestrate on K8S?

And any roadmap on this? The organisation's on ssh auth is firm. This can end up not possible to use ClearML for remote execution.

Try set docker_force_pull: true under agent section of your agent's clearml.conf.

Hi, scenario as follows.

client.py runs task.execute_remotely(queue='myqueue', exit_process=True) The API section of clearml.conf at client side is read in. client side calls clearml server and insert task into queue. K8S glue retrieves task from queue. Spawn a K8S pod. K8S pod performs git clone Error. ssh keys not found.
Each individual has their own key in the gitlab profile and gitlab is configured to only work via ssh.
We can't place the key in the image as this is as good as ...