Reputation
Badges 1
662 × Eureka!TimelyPenguin76 CostlyOstrich36 It seems a lot of manual configurations is required to get the EC2 instances up and running.
Would it not make sense to update the autoscaler (and example script) so that the config.yaml that's used for the autoscaler service is implicitly copied to the EC2 services, and then any extra_clearml_conf are used/overwritten?
Those are cool and very welcome additions (hopefully the additional info in the Info tab will be a link?) π
The main issue is the clutter that the forced renaming creates, as shown in the pictures I attached in the other thread.
Why does ClearML hide the dataset task from the main WebUI? Users should have some control over that. If I specified a project for the dataset, I specifically want it there, in that project, not hidden away in some .datasets hidden sub-project. Not...
It can also log generate a log file with this method, it does not have to output it to CONSOLE tab.
I should maybe mention that the security regarding this is low, since this is all behind a private VPN server anyway, I'm mostly just interested in having the credentials used for backtracking purposes
That's enabled; I was aiming if there are flags to add to pip install CLI, such as --no-use-pep517
Hey @<1537605940121964544:profile|EnthusiasticShrimp49> ! Youβre mostly correct. The Step classes will be predefined (of course developers are encouraged to add/modify as needed), but as in the DataTransformationStep , there may be user-defined functions specified. Thatβs not a problem though, I can provide these functions with the helper_functions argument.
- The
.add_function_stepis indeed a failing point. I canβt really create a task from the notebook because calling `Ta...
Thanks CostlyOstrich36 !
Now my extra_vm_bash_script looks like so:
` deactivate
apt-get install -y gfortran libopenblas-dev liblapack-dev libpq-dev python-is-python3 python3-pip python3-dev proj-bin libgraphviz-dev graphviz graphviz-dev libgdal-dev
apt-get install software-properties-common -y
add-apt-repository ppa:deadsnakes/ppa -y
apt update
apt install python3.7 python3.8 python3.9 python3.7-distutils python3.8-distutils python3.9-distutils python3.10-distutils python3.7-dev python3.8-dev python3.9-dev pyt...
Or to be clear, the environment installed by the autoscaler under /clearml_agent_venv has poetry installed, and it uses that to set up the environment for the executed task, e.g. in root/.clearml/venvs-builds/3.10/task_repository/.../.venv , but the latter does not have poetry installed, and so it crashes?
I also tried adding gent.package_manager.system_site_packages = true to ensure these virtual environments have access btw, still no avail
But to be fair, I've also tried with python3.X -m pip install poetry etc. I get the same error.
Sure SuccessfulKoala55 , and thanks for looking into it.
As an alternative (for now, or in general), we could consider reverting back to pip. The issue we encounter is that we have a monorepo, so frozen requirements should specify relative paths, but pip freeze does not seem to do that, so ClearML also fails in pip mode
We're not using the docker setup though. The CLI run by the autoscaler is python -m clearml_agent --config-file /root/clearml.conf daemon --queue aws_small , so no docker
Is there a way to specify that flag within the config file, SuccessfulKoala55 ?
SuccessfulKoala55 help me out here π
It seems all the changes I make in the AWS autoscaler apply directly to the virtual environment set for the autoscaler, but nothing from that propagates down to the launched instances.
So e.g. the autoscaler environment has poetry installed, but then the instance fails because it does not have it available?
That still seems to crash SuccessfulKoala55 π€
EDIT: No, wait, the environment still needs updating. One moment still...
Still crashing, I think that may not be the correct virtual environment to edit π€
It's the one created later down the line
I'll try a hacky-way around it with sed -i 's/include-system-site-packages = false/include-system-site-packages = true/g' clearml_agent_venv/pyvenv.cfg and report back.
I'll try that in a bit (that requires some access control changes). Any idea how can I modify the dynamically created virtualenv?
` Poetry Enabled: Ignoring requested python packages, using repository poetry lock file!
The currently activated Python version 3.10.6 is not supported by the project (~3.8.0).
Trying to find and use a compatible version.
Using python3.8 (3.8.16)
Creating virtualenv ... in /root/.clearml/venvs-builds/3.10/task_repository/...git/.venv
Installing dependencies from ...
Created this for follow up, SuccessfulKoala55 ; I'm really stumped. Spent the entire day on this π₯Ή
https://github.com/allegroai/clearml-agent/issues/134
Anyway sounds good! π
AgitatedDove14 for future reference this is indeed a PEP-610 related bug, fixed in https://python-poetry.org/blog/announcing-poetry-1.2.0a1/ . I see we can choose the pip version in the config, can we also set the poetry version used? Or is it updated from the lock file itself, or...?
Hmmm maybe π€ I thought that was expected behavior from poetry side actually
Haha, I've opened so many issues these past few days... Sure, np!
Right so it uses whatever version is available on the agent.
Yeah it would be nice to have either a poetry_version (a-la https://github.com/allegroai/clearml-agent/blob/5afb604e3d53d3f09dd6de81fe0a494dacb2e94d/docs/clearml.conf#L62 ), rename the latter to manager_version , or just install from the captured environment, etc? π€
That was a good idea, unfortunately did not help too much, but I think I may have a found a work around, thanks!