For those of yall that missed it… `pip install daf...
# general
j
For those of yall that missed it…
pip install daft-launcher
Initialize the launcher’s configs (default AWS region, number of machines etc)
Copy code
daft init-config
Launch a cluster and see that it’s running
Copy code
daft up
daft list
Connect to the cluster!
Copy code
daft connect
Tear it down
Copy code
daft down
It’s easier more than ever now to try Daft out on a distributed environment, all you need is an AWS account and use
daft-launcher
k
I got ModuleNotFoundError: No module named 'tomllib' after installing 🥲 I guess there is a python version dependency?
j
@Raunak Bhagat halp
Mmmm yes
tomllib is a Python module introduced in Python 3.11
Wonder if there’s a future import we could do here.
r
Ah yes,
tomllib
is for >=3.11 and
toml
is for < 3.11 I believe... I'll have to see how to fix this. @Kyle Apologies for that mistake! If possible, are you able to use 3.11 for pure testing purposes? If not, I'll try and get a fix up asap.
k
No worries! I don't think I will be using the launcher for the time being because I don't have access to the cloud resources directly. Just wanted to test the package to see where I'd get stuck 😬
👍 1
r
For sure, that makes sense. I've been trying to iron out all of the bugs, so your trial-and-error process is greatly appreciated!
j
@Kyle do yall use kubernetes? I wonder if maybe we should make a kubernetes backend for daft-launcher. It would require certain permissions though, such as the ability to launch pods in the provided namespace, and port-forward capabilities
k
Yes we do but I generally do not have the permissions to touch those configurations. It also wouldn't be a major concern for me at the moment. I think the questions you're asking on configuration settings in cloud could be useful as well if people knew what to ask for, so that they can determine and find out if there are some existing resources within their own companies they could reuse or if they need to be the ones setting it up.
👍 1
r
Hey Kyle, forgot to update you earlier, but the toml problem has been fixed in v0.3.7! If you have the chance, please give it a try. Also, the minimum python version is set to 3.9.
k
Okay thanks! I was also wondering, is it possible to peer into an existing cluster to view how it was set up and then reuse all of those configs to down and up the cluster?
r
Hmm, could you elaborate on what you mean by “how it was set up”, please? Do you mean you want to see all of the installations which occurred, for example?
k
Yes like the setup_commands
Basically all the configs which were passed to ray on cluster setup
I'm just imagining a scenario whereby i can get daft to connect to an existing cluster and then kind of understand what all the setup steps i need to include are if i were to up a cluster using the launcher
r
Hmm, I’ll have to see. I’ll get back to you as soon as possible on this.
k
Thanks!
Works well now! The config got created!
❤️ 1
r
Nice to hear!
j
Wait are you bypassing your k8s Ray clusters now? 😛
and just using the
daft-launcher
ec2 machines directly?
k
Haha no.. only got to the config toml creation step i dont have access to the cloud to bring up or down the resources 🫠