Reputation
Badges 1
39 × Eureka!ok,
just a small question, is the parameter “defaultContainerImage” tell the glue agent which image to use for the spawned agent ?
I do not remember exactly all the steps we did, but with the help of clearml team we found solution by adding:Task.add_requirements((…)
outside the pipeline code
no problem, you and your team are very responsive and help us a lot.
no, it work if the tag exist and i do other change to the task. but if the task does not have the task and I just add the tag the event is not trigger.
Hi,
res is None but the trigger works when doing other changes so i guess it was added.
Not sure I understand, you are saying I should not create user credentials and add them in values.yaml at secret.credentials.apiserver and secret.credentials.tests. ?
I will check it and update you
For now we used a workaround and forked the helm charts repo and we changed in the agents deployment.yaml, instead of taking the key and secret from the clearml-conf secret we take them from another secret we created so the server does not “know” about this new key and secret and does not reset them
but the system account key and secret can’t be the same for every installation, no? i need to generate specific one for my installation, no?
for now we used fixed number of cpu agents but it will be better if it was dynamic with glue agent
we already using glue to manage our gpu pods. The agents we use for the pipelines are simple cpu agent.
can we use multiple k8s-glue - one for cpu and one for gpu pods?
since the gpu is expensive we want the glue to manage the pods
not urgent after we used the workaround
Thanks CostlyOstrich36 OutrageousSheep60 , using output_uri = “<GS_BUCKET>” solve it.
Where should i put this line? inside the pipeline function?
I am getting this error:clearml.task - WARNING - Requirement ignored, Task.add_requirements() must be called before Task.init()
Works locally but not when running inside agent.
I found that adding the:Task.add_requirements('protobuf', '<=3.20.1')
before the pipeline decorator it works
Immediately after i use “add_external_files” i see it changed the original file link and removed from it the “ gs://bucket_name ”
not getting any error when uploading.
I use “add_external_files” so it is not really uploading the file just the dataset info
For now we store only one file in a dataset.
I just downgraded to 1.7.2, will wait for the fix.
Thanks for the workaround.