input
stringlengths 1
12.6k
| output
stringlengths 1
12k
|
|---|---|
like a scale to zero node group?
| flyte-binary cannot be scale to 0, but tasks can be scale to 0 for sure
it is designed to wait for scale-ups etc
|
flyte-binary cannot be scale to 0, but tasks can be scale to 0 for sure
it is designed to wait for scale-ups etc
| <@U01SCEFSUKF> I was just thinking of a way to prevent flyte-binary from being interrupted, while allowing that for tasks
|
<@U01SCEFSUKF> I was just thinking of a way to prevent flyte-binary from being interrupted, while allowing that for tasks
| The approach sounds like a good use of nodegroups.
does flyte binary use VPA or HPA?
|
Hi guys, I have a question.
I would’t like to use auth0 in localhost/login
I can to use an user and password and put this information in a secret?
How I can do it? Help me please
| if you’re using auth0's authorization server, you’ll have to create an application within their app.
then change the admin configuration to point to an external authorization server
but not sure what you mean by use auth0 in localhost/login?
if you redirect admin to use auth0's auth server, they necessarily keep that secret
|
Is it possible to configure other defaults than resource requests through the helm chart? For example default timeout for tasks.
| Unfortunately no
|
Unfortunately no
| <@U0402CYDR98> I think <https://github.com/flyteorg/flyte/issues/2889|task execution deadline> fits your example here right? node and workflow level execution deadlines are currently exposed through propeller configuration.
|
<@U0402CYDR98> I think <https://github.com/flyteorg/flyte/issues/2889|task execution deadline> fits your example here right? node and workflow level execution deadlines are currently exposed through propeller configuration.
| Yes. My use case is to set reasonable defaults in case of stuck workflows that can be overridden with task timeouts.
|
Something weird going on with our flytepropeller. Will probably try to fully redeploy.
Got the log error below when trying to run a workflow that needs to access a secret. Propeller tries to get the webhook to do its work but it seems to think the hostname for the webhook is `flyte-backend-flyte-binary-webhook.flyte.svc`.
```{
"json": {
"exec_id": "ap69gmldszgqd5xc94rk",
"node": "n0",
"ns": "...",
"res_ver": "208312048",
"routine": "worker-2",
"tasktype": "python-task",
"wf": "..."
},
"level": "error",
"msg": "Failed to launch job, system error. err: Internal error occurred: failed calling webhook \"<http://flyte-pod-webhook.flyte.org|flyte-pod-webhook.flyte.org>\": Post \"<https://flyte-backend-flyte-binary-webhook.flyte.svc:443/mutate--v1-pod?timeout=10s>\": service \"flyte-backend-flyte-binary-webhook\" not found",
"ts": "2023-02-22T18:26:12Z"
}```
The `webhook` section of the `core.yaml` configmap for the propeller has
```webhook:
certDir: /etc/webhook/certs
serviceName: flyte-pod-webhook```
Previously, I ran the `flyte-binary` deployment. But I eventually tore it down.
I’ve restarted the k8s deployments but haven’t done any redeploy of the chart
`flyte-backend-flyte-binary-webhook.flyte.svc` looks like the host names `kubefwd` uses and I did use that tool at one point so I wonder if there was some weird alchemy that got things mixed up.
| <@U04P6HHMCG0> so you used `kubefwd`as a kinda-Ingress before?
|
<@U04P6HHMCG0> so you used `kubefwd`as a kinda-Ingress before?
| yea, but we got the ingress worked out. I’m currently redeploying the helm chart
|
yea, but we got the ingress worked out. I’m currently redeploying the helm chart
| ok, did you uninstall the previous `flyte-binary` chart?
We should try a clean install if possible
|
ok, did you uninstall the previous `flyte-binary` chart?
We should try a clean install if possible
| yea, doing a clean install. removing everything
wow, still getting the error message
did `helm uninstall`. Then went through and cleared out the namespaces
|
yea, doing a clean install. removing everything
wow, still getting the error message
did `helm uninstall`. Then went through and cleared out the namespaces
| and I guess the service that the chart actually created is
`flyte-pod-webhook.flyte.svc` right?
|
and I guess the service that the chart actually created is
`flyte-pod-webhook.flyte.svc` right?
| `core.yaml` in the running pod:
```/etc/flyte/config $ cat core.yaml
manager:
pod-application: flytepropeller
pod-template-container-name: flytepropeller
pod-template-name: flytepropeller-template
propeller:
downstream-eval-duration: 30s
enable-admin-launcher: true
gc-interval: 12h
kube-client-config:
burst: 25
qps: 100
timeout: 30s
leader-election:
enabled: true
lease-duration: 15s
lock-config-map:
name: propeller-leader
namespace: flyte
renew-deadline: 10s
retry-period: 2s
limit-namespace: all
max-workflow-retries: 50
metadata-prefix: metadata/propeller
metrics-prefix: flyte
prof-port: 10254
queue:
batch-size: -1
batching-interval: 2s
queue:
base-delay: 5s
capacity: 1000
max-delay: 120s
rate: 100
type: maxof
sub-queue:
capacity: 1000
rate: 100
type: bucket
type: batch
rawoutput-prefix: <s3://infima-flyte/raw/>
workers: 40
workflow-reeval-duration: 30s
webhook:
certDir: /etc/webhook/certs
serviceName: flyte-pod-webhook
/etc/flyte/config $ ```
Services are named right:
For more clarity, here is what I did:
1. `helm fetch --untar --untardir . flyteorg/flyte-core`
2. Made two changes to the `flyteadmin` and `clusterresourcesync` `deployment.yaml`. To get the cluster config working, had to add in these these volume mounts to the spec:
``` {{- with .Values.flyteadmin.additionalVolumeMounts -}}
{{ tpl (toYaml .) $ | nindent 10 }}
{{- end }}```
3. Ran through the deploy, ie
```helm upgrade flyte \
./flyte-core \
--install \
--values values.yaml \
--values values-eks.yaml \
--values values-cluster-config.yaml \
--values values-ingress.yaml \
--create-namespace \
--namespace flyte```
Caveat: I start with the data plane and do some secret updating. But it’s basically that command
here’s something I’m noticing though
the tags in the repo, for instance `1.1.72` for `flyteadmin` , are not the same as the tags that I get when I download the chart.
<https://github.com/flyteorg/flyte/blob/master/charts/flyte-core/values.yaml>
the chart has
```flyteadmin:
enabled: true
# -- Replicas count for Flyteadmin deployment
replicaCount: 1
image:
# -- Docker image for Flyteadmin deployment
repository: <http://cr.flyte.org/flyteorg/flyteadmin-release|cr.flyte.org/flyteorg/flyteadmin-release> # FLYTEADMIN_IMAGE
tag: v1.3.0 # FLYTEADMIN_TAG
pullPolicy: IfNotPresent```
I copied the values files from the repo to start with instead of starting with the ones in the downloaded chart.
well, that change didn’t make a difference. Updated the `values.yaml` to use the tags in the helm chart, so for instance
```<http://cr.flyte.org/flyteorg/flytepropeller-release:v1.3.0|cr.flyte.org/flyteorg/flytepropeller-release:v1.3.0>```
instead of
```<http://cr.flyte.org/flyteorg/flytepropeller:v1.1.62|cr.flyte.org/flyteorg/flytepropeller:v1.1.62>```
|
`core.yaml` in the running pod:
```/etc/flyte/config $ cat core.yaml
manager:
pod-application: flytepropeller
pod-template-container-name: flytepropeller
pod-template-name: flytepropeller-template
propeller:
downstream-eval-duration: 30s
enable-admin-launcher: true
gc-interval: 12h
kube-client-config:
burst: 25
qps: 100
timeout: 30s
leader-election:
enabled: true
lease-duration: 15s
lock-config-map:
name: propeller-leader
namespace: flyte
renew-deadline: 10s
retry-period: 2s
limit-namespace: all
max-workflow-retries: 50
metadata-prefix: metadata/propeller
metrics-prefix: flyte
prof-port: 10254
queue:
batch-size: -1
batching-interval: 2s
queue:
base-delay: 5s
capacity: 1000
max-delay: 120s
rate: 100
type: maxof
sub-queue:
capacity: 1000
rate: 100
type: bucket
type: batch
rawoutput-prefix: <s3://infima-flyte/raw/>
workers: 40
workflow-reeval-duration: 30s
webhook:
certDir: /etc/webhook/certs
serviceName: flyte-pod-webhook
/etc/flyte/config $ ```
Services are named right:
For more clarity, here is what I did:
1. `helm fetch --untar --untardir . flyteorg/flyte-core`
2. Made two changes to the `flyteadmin` and `clusterresourcesync` `deployment.yaml`. To get the cluster config working, had to add in these these volume mounts to the spec:
``` {{- with .Values.flyteadmin.additionalVolumeMounts -}}
{{ tpl (toYaml .) $ | nindent 10 }}
{{- end }}```
3. Ran through the deploy, ie
```helm upgrade flyte \
./flyte-core \
--install \
--values values.yaml \
--values values-eks.yaml \
--values values-cluster-config.yaml \
--values values-ingress.yaml \
--create-namespace \
--namespace flyte```
Caveat: I start with the data plane and do some secret updating. But it’s basically that command
here’s something I’m noticing though
the tags in the repo, for instance `1.1.72` for `flyteadmin` , are not the same as the tags that I get when I download the chart.
<https://github.com/flyteorg/flyte/blob/master/charts/flyte-core/values.yaml>
the chart has
```flyteadmin:
enabled: true
# -- Replicas count for Flyteadmin deployment
replicaCount: 1
image:
# -- Docker image for Flyteadmin deployment
repository: <http://cr.flyte.org/flyteorg/flyteadmin-release|cr.flyte.org/flyteorg/flyteadmin-release> # FLYTEADMIN_IMAGE
tag: v1.3.0 # FLYTEADMIN_TAG
pullPolicy: IfNotPresent```
I copied the values files from the repo to start with instead of starting with the ones in the downloaded chart.
well, that change didn’t make a difference. Updated the `values.yaml` to use the tags in the helm chart, so for instance
```<http://cr.flyte.org/flyteorg/flytepropeller-release:v1.3.0|cr.flyte.org/flyteorg/flytepropeller-release:v1.3.0>```
instead of
```<http://cr.flyte.org/flyteorg/flytepropeller:v1.1.62|cr.flyte.org/flyteorg/flytepropeller:v1.1.62>```
| I’ve hit a deadend. I can’t figure out what the source of that host name the propeller is using. I can’t parse the propeller code to understand where it’s coming up with it. The only source for that name comes from this helper in the binary helm chart and from the manifests, I don’t see that name anywhere.
<https://github.com/flyteorg/flyte/blob/d60c9af85a59ebb4c2265f76cb082b992078a309/charts/flyte-binary/templates/_helpers.tpl#L159|https://github.com/flyteorg/flyte/blob/d60c9af85a59ebb4c2265f76cb082b992078a309/charts/flyte-binary/templates/_helpers.tpl#L159>
|
I’ve hit a deadend. I can’t figure out what the source of that host name the propeller is using. I can’t parse the propeller code to understand where it’s coming up with it. The only source for that name comes from this helper in the binary helm chart and from the manifests, I don’t see that name anywhere.
<https://github.com/flyteorg/flyte/blob/d60c9af85a59ebb4c2265f76cb082b992078a309/charts/flyte-binary/templates/_helpers.tpl#L159|https://github.com/flyteorg/flyte/blob/d60c9af85a59ebb4c2265f76cb082b992078a309/charts/flyte-binary/templates/_helpers.tpl#L159>
| Cc <@U017K8AJBAN>
|
Cc <@U017K8AJBAN>
| the repo is always gonna be ahead of the stable chart release <@U04P6HHMCG0>
it looks like you’re using the flyte-core chart but linking the flyte-binary chart. can you clarify?
ok i think i understand. you had installed the flyte-binary chart before, but now uninstalling it and installing flyte-core?
i think you need to delete the old mutating webhook from the flyte namespace
|
the repo is always gonna be ahead of the stable chart release <@U04P6HHMCG0>
it looks like you’re using the flyte-core chart but linking the flyte-binary chart. can you clarify?
ok i think i understand. you had installed the flyte-binary chart before, but now uninstalling it and installing flyte-core?
i think you need to delete the old mutating webhook from the flyte namespace
| > ok i think i understand. you had installed the flyte-binary chart before, but now uninstalling it and installing flyte-core?
this is correct
> i think you need to delete the old mutating webhook from the flyte namespace
when I’ve been doing clean installs, i’ve completely wiped everything flyte related. the namespaces are all deleted.
|
> ok i think i understand. you had installed the flyte-binary chart before, but now uninstalling it and installing flyte-core?
this is correct
> i think you need to delete the old mutating webhook from the flyte namespace
when I’ve been doing clean installs, i’ve completely wiped everything flyte related. the namespaces are all deleted.
| hmm can you do “kubectl get mutatingwebhookconfigurations”
|
hmm can you do “kubectl get mutatingwebhookconfigurations”
| !
```╰─❯ kubectl get mutatingwebhookconfigurations
NAME WEBHOOKS AGE
flyte-backend-flyte-binary-webhook 1 7d22h
flyte-pod-webhook 1 65d```
good catch.
|
!
```╰─❯ kubectl get mutatingwebhookconfigurations
NAME WEBHOOKS AGE
flyte-backend-flyte-binary-webhook 1 7d22h
flyte-pod-webhook 1 65d```
good catch.
| can you delete the first one?
these aren’t namespaced
|
can you delete the first one?
these aren’t namespaced
| hmmm, perhaps a limitation of Lens.
|
hmmm, perhaps a limitation of Lens.
| it’s created by the flyte deployment. and not namespaced. easy to miss :)
|
it’s created by the flyte deployment. and not namespaced. easy to miss :)
| <@U04P6HHMCG0> this is unfortunate - but how can we avoid this in the future. It is sadly super easy to blame Flyte
|
<@U04P6HHMCG0> this is unfortunate - but how can we avoid this in the future. It is sadly super easy to blame Flyte
| can you add owner references to webhooks?
|
can you add owner references to webhooks?
| `helm uninstall` doesn’t seem to tear down everything
|
`helm uninstall` doesn’t seem to tear down everything
| tricky though. we’d need to make the deployment the owner but the pod won’t know what the deployment is
|
tricky though. we’d need to make the deployment the owner but the pod won’t know what the deployment is
| I tried to track down things that I missed in the teardown. I ran `k get all -A` but clearly that wasn’t good enough.
It didn’t get _everything_
|
I tried to track down things that I missed in the teardown. I ran `k get all -A` but clearly that wasn’t good enough.
It didn’t get _everything_
| right
it’s not a helm owned resource unfortunately
|
right
it’s not a helm owned resource unfortunately
| well, I found a command that really gets everything.
```kubectl api-resources --verbs=list -o name \
| xargs -n 1 kubectl get --show-kind --ignore-not-found```
Thanks for the help <@U017K8AJBAN> and <@UNZB4NW3S>! Hopefully it’s a smooth flyte from here.
|
well, I found a command that really gets everything.
```kubectl api-resources --verbs=list -o name \
| xargs -n 1 kubectl get --show-kind --ignore-not-found```
Thanks for the help <@U017K8AJBAN> and <@UNZB4NW3S>! Hopefully it’s a smooth flyte from here.
| <@U04P6HHMCG0> also please help others in the future
|
<@U04P6HHMCG0> also please help others in the future
| Will do. Definitely becoming an expert on this.
|
Will do. Definitely becoming an expert on this.
| I just ran into the very same problem and the solution worked for me.
Probably the only missing piece would to be update <https://docs.flyte.org/en/latest/deployment/deployment/cloud_simple.html#port-forward-flyte-service|the docs> as they point to a different service name
`kubectl -n flyte port-forward *service/flyte-binary* 8088:8088 8089:8089`
<@U04P6HHMCG0> would you like to contribute that piece? I can assist you if you need
I mean, it should be
`kubectl -n flyte port-forward *service/flyte-backend-flyte-binary* 8088:8088 8089:8089`
|
I just ran into the very same problem and the solution worked for me.
Probably the only missing piece would to be update <https://docs.flyte.org/en/latest/deployment/deployment/cloud_simple.html#port-forward-flyte-service|the docs> as they point to a different service name
`kubectl -n flyte port-forward *service/flyte-binary* 8088:8088 8089:8089`
<@U04P6HHMCG0> would you like to contribute that piece? I can assist you if you need
I mean, it should be
`kubectl -n flyte port-forward *service/flyte-backend-flyte-binary* 8088:8088 8089:8089`
| <@U04H6UUE78B> that name varies by the name of the helm release. in this case the helm release is named flyte-backend. it will likely be different from user to user.
|
<@U04H6UUE78B> that name varies by the name of the helm release. in this case the helm release is named flyte-backend. it will likely be different from user to user.
| <@U04H6UUE78B> I was thinking of removing some key info from my repo and publishing it on github with a guide (that followed along the “AWS manual setup” guide in the old version of the docs). Also making a PR for this: <https://flyte-org.slack.com/archives/C01P3B761A6/p1677172098125769?thread_ts=1676558819.041309&cid=C01P3B761A6>
|
<@U04H6UUE78B> I was thinking of removing some key info from my repo and publishing it on github with a guide (that followed along the “AWS manual setup” guide in the old version of the docs). Also making a PR for this: <https://flyte-org.slack.com/archives/C01P3B761A6/p1677172098125769?thread_ts=1676558819.041309&cid=C01P3B761A6>
| <@U04P6HHMCG0> that would be great! Please let us know if you require any help
|
Hey everyone! I am Akanksha Bhasin, a Technical Evangelist and Community Advocate from India!
I got to know about Flyte from <@UNZB4NW3S> and excited to be a part of this community. :smile:
| Hi <@U058EU2EQBW>! Welcome!
|
Hi <@U058EU2EQBW>! Welcome!
| Hi <@U058EU2EQBW>! Great to see you here!
|
Hi <@U058EU2EQBW>! Great to see you here!
| Hi <@U01J90KBSU9> and <@U057KVAE98T> :wave:
|
Hello everyone my name is Donny and I'm evaluating Flyte for my startup to orchestrate datajobs using Scala or Java, happy to part of this community :slightly_smiling_face:
| Hi <@U0573RANC91>! Welcome! We don't yet have docs for the java sdk; I recommend you to check out the repo.
<https://github.com/flyteorg/flytekit-java/tree/master>
|
Hi <@U0573RANC91>! Welcome! We don't yet have docs for the java sdk; I recommend you to check out the repo.
<https://github.com/flyteorg/flytekit-java/tree/master>
| yeah I took a look at it and it's making me hesitant on moving forward with it due to the lack of documenation. But I just saw that there are some examples in the repo.
Is it recommended to use the scala/java version in production yet?
|
yeah I took a look at it and it's making me hesitant on moving forward with it due to the lack of documenation. But I just saw that there are some examples in the repo.
Is it recommended to use the scala/java version in production yet?
| Spotify uses the java sdk in prod! So yes, it has been battle-tested already!
|
Spotify uses the java sdk in prod! So yes, it has been battle-tested already!
| Cc <@UP4D9EY6T> / <@UU43XA551> and others please chime in
|
Hello everyone. I am building some bioinformatics workflows in Flyte for a small diagnostics company I recently joined. I brought my experience at Freenome to this new role and immediately advocated for using Flyte! Happy to be here.
| Thanks for sharing, we're happy to have you here!
|
Thanks for sharing, we're happy to have you here!
| Welcome to the community, Brian!
|
Hello all, I am Martin and currently exploring capabilities of Flyte for data workflows.
| Hi Martin and welcome to the Flyte community!
I guess you probably already explored, but here are some resources:
<https://flyte.org/data>
<https://docs.flyte.org/projects/cookbook/en/latest/auto/case_studies/ml_training/spark_horovod/index.html>
<https://flyte.org/blog/orchestrating-data-pipelines-at-lyft-comparing-flyte-and-airflow>
In any case, please let the community know any question you may have.
Thank you!
|
Hi Martin and welcome to the Flyte community!
I guess you probably already explored, but here are some resources:
<https://flyte.org/data>
<https://docs.flyte.org/projects/cookbook/en/latest/auto/case_studies/ml_training/spark_horovod/index.html>
<https://flyte.org/blog/orchestrating-data-pipelines-at-lyft-comparing-flyte-and-airflow>
In any case, please let the community know any question you may have.
Thank you!
| Welcome to the community Martin. Great to have you in the community
|
Hi all! Really excited to have found Flyte as it seems to address a lot of my pains points. I'm just getting started but I'm looking to use it for executing bioinformatics workflows on <https://www.golem.network/|Golem>.
| Welcome to the community and thank you for sharing
I do not know what golem, is if you get things working let us know please
|
Welcome to the community and thank you for sharing
I do not know what golem, is if you get things working let us know please
| Thanks! I sure will.
|
Hello everyone, I followed the installation document from this link <https://docs.flyte.org/en/v1.0.0/deployment/aws/manual.html#prerequisites>. All the outputs were as per the documentation, but on the final step where I try to login, "endpoint/console", I get 503 Service Temporarily Unavailable. Any help on this?
thanks in advance
| already addressing this Q on <#C01P3B761A6|flyte-deployment>
|
Hello All, Are there any Flyte meetings (official or unofficial) happening at pycon next month?
| Are you thinking of organizing one?
Cc <@U04H6UUE78B> any ideas. Pycon has many users might be cool
|
Are you thinking of organizing one?
Cc <@U04H6UUE78B> any ideas. Pycon has many users might be cool
| <@U04TVQUUY3S> welcome to the Flyte community!
Well, we can find out who else from the community plans to attend and then organize a gathering
What do you think?
just asked at <#C02JMT8KTEE|events> to find out :slightly_smiling_face:
|
<@U04TVQUUY3S> welcome to the Flyte community!
Well, we can find out who else from the community plans to attend and then organize a gathering
What do you think?
just asked at <#C02JMT8KTEE|events> to find out :slightly_smiling_face:
| I live in SLC, would be willing to assist whoever takes lead. FYI, i've never used Flyte before and just joined the group about an hour ago.
|
I live in SLC, would be willing to assist whoever takes lead. FYI, i've never used Flyte before and just joined the group about an hour ago.
| that's amazing David, thanks for joining.
What problem are you trying to solve with Flyte?
|
:rocket: Ready for a knowledge adventure? Let’s unravel the intricacies of ‘Vector Search with Multilingual Embeddings in a Joint Latent Space’ together in our upcoming Papers Club event. RSVP now: <https://www.gathers.ai/papers-club/vector-search-with-multilingual-embeddings-in-a-joint-latent-space>.
| Thanks for sharing <@U052VMW1BMF>!
|
All ready for the Poster presentation for tomorrow
| Awesome!
|
Awesome!
| Thanks
The response was amazing. Over 100 people came by and asked regarding the project
|
Our <@U04TKCKNGSG> poster for PyCon US is printed and setup at PyCon US :flyte:
<@U04TKCKNGSG> is already here in Salt Lake City. I will fly out tomorrow. It will be on display for next 3 days with presentations running on Sunday!
| thanks for sharing <@U03H0DUGSG6>!
|
thanks for sharing <@U03H0DUGSG6>!
| Are they enforcing the covid mask policy? I have not make it out the door yet.
|
Are they enforcing the covid mask policy? I have not make it out the door yet.
| Great work!
|
Great work!
| I am not entirely sure. Will arrive tonight
|
:loudspeaker:Hello everyone!
Did we mention that there will be an in-person Flyte community happy hour at Seattle *next week*?
If you're by the area or attending PyData, we'd love to meet you there.
:tropical_drink:Grab some food, drinks and enjoy the company of fellow Flyte community members!
:calendar: Thursday, April 27th
:clock1: 7PM
:office: Locust Cider Redmond
Secure your spot!
<https://www.meetup.com/union-ai/events/292959822/>
| Can't wait for this
|
Soo here's where to catch up with Flyte during in-person events this month!
• :kubernetes: ArgoCon EU (co-located to Kubecon EU)
◦ April 18th, 10:20AM EU
◦ <https://sched.co/1Jo9X>
◦ Speaker: <@U01J8L5AR2S>
• :aicamp: Atlanta ML meetup
◦ April 19, 5PM EST
◦ Registration <https://www.aicamp.ai/event/eventdetails/W2023041914?utm_source=linkedin&utm_medium=social&utm_campaign=meetups|link>
◦ Speaker: <@U01DYLVUNJE>
• :pycon: PyCon US MLOps/UnionML poster presentation
◦ Apr 19-27
◦ List: <https://us.pycon.org/2023/schedule/posters/list/>
◦ Authors: <@U03H0DUGSG6> <@U04TKCKNGSG>
• :pydata: Flyte takeover at PyData Seattle!
◦ Talks
▪︎ <https://seattle2023.pydata.org/cfp/talk/XKJKPN/|Building MLOps with UnionML> by <@U03H0DUGSG6> <@U04TKCKNGSG> (Apr 26, 11AM PT)
▪︎ <https://seattle2023.pydata.org/cfp/talk/ZXUAFL/|Flyte: cloud-native ML/Data proc platform> by <@U0265RTUJ5B> (Apr 26, 15:30 PT)
▪︎ <https://seattle2023.pydata.org/cfp/talk/ZJYFSQ/|The Python Data Ecosystem: Navigating a fragmented landscape> by <@UNZB4NW3S> <@UNR3C6Y4T> (Apr 28, 11:45 PT)
If you're attending any of these conferences, do let us know by replying here. Would be great to connect with you all!
| I will be at KubeCon EU before heading out to PyCon US, if anyone is there in either of these two events. would love to meet you folks.
On that note, <@U04H6UUE78B> <https://sched.co/1Jo8u> I will be presenting a talk at KubeCon (HPC Colocated event) on
<https://colocatedeventseu2023.sched.com/|Making the Most Out of Your Hardware Accelerators in a Kubernetes Cluste>r for Machine Learning workloads. And originally it was meant for showing example for Kubeflow. But I would love to cover use case for Flyte as well. Is it possible to connect with the Flyte team and see what we could showcase in our presentation related to this topic.
cc <@U0327QS23K4> <@U01J90KBSU9> <@U01DYLVUNJE>
|
I will be at KubeCon EU before heading out to PyCon US, if anyone is there in either of these two events. would love to meet you folks.
On that note, <@U04H6UUE78B> <https://sched.co/1Jo8u> I will be presenting a talk at KubeCon (HPC Colocated event) on
<https://colocatedeventseu2023.sched.com/|Making the Most Out of Your Hardware Accelerators in a Kubernetes Cluste>r for Machine Learning workloads. And originally it was meant for showing example for Kubeflow. But I would love to cover use case for Flyte as well. Is it possible to connect with the Flyte team and see what we could showcase in our presentation related to this topic.
cc <@U0327QS23K4> <@U01J90KBSU9> <@U01DYLVUNJE>
| I’ll be speaking at ArgoCon and then I’ll attend Kubecon so we can meet for coffee if you want at one point :smile:
|
I’ll be speaking at ArgoCon and then I’ll attend Kubecon so we can meet for coffee if you want at one point :smile:
| Yeah sure!
On that note <@U04H6UUE78B> please let me know if it is possible to see if we could include Flyte in my presentation, because the scope is certainly there
|
Yeah sure!
On that note <@U04H6UUE78B> please let me know if it is possible to see if we could include Flyte in my presentation, because the scope is certainly there
| I think so <@U03H0DUGSG6>
Can we have a call to discuss?
|
I think so <@U03H0DUGSG6>
Can we have a call to discuss?
| Yes please if possible!
|
:loudspeaker: Are you attending PyCon US (Salt Lake City, Apr. 19-27)?
Let us know by reacting to this message (:+1::skin-tone-4:).
We'd like to offer Flyte swag to anyone attending and potentially organizing a gathering!
| I would love to catchup with the Flyte folks!
|
Hi is UnionAI sponsoring PyCon US this year?
| I don't think so, Shivay. <@U0327QS23K4>
|
Hi all, I created an issue <https://github.com/flyteorg/flyte/issues/3588|here> before realizing there was a Slack. Any ideas as to why the Python Ray example (from <https://docs.flyte.org/projects/cookbook/en/latest/auto/integrations/kubernetes/ray_example/ray_example.html|the docs>) registers its workflow just fine, but the Jupyter Notebook example doesn't find any entities? I'm probably missing something obvious so apologies if that's the case.
I noticed that VS Code thinks there is a `\n` after `@workflow`(unsurprising as Jupyter Notebooks are typically run in the browser obviously), not sure if that could be causing the problem.
| <@U052JJCL37Z>, you cannot register workflows present in ipynb files. You can, however, use FlyteRemote to register the tasks and workflows.
<https://docs.flyte.org/projects/flytekit/en/latest/design/control_plane.html#registering-entities>
You can include this code in a separate cell in your jupyter notebook and run it.
|
<@U052JJCL37Z>, you cannot register workflows present in ipynb files. You can, however, use FlyteRemote to register the tasks and workflows.
<https://docs.flyte.org/projects/flytekit/en/latest/design/control_plane.html#registering-entities>
You can include this code in a separate cell in your jupyter notebook and run it.
| Thank you for the quick response.
I think I'm having trouble figuring out what my flyte_entity should be. Let's assume my project name is `repo`, and I have the `ray_example.ipynb` file in the `workflows` folder, and I'm trying to add the workflow to the `development` domain.
I was adding a new separate cell to the bottom of the Jupyter Notebook `ray_example.ipynb` file like so:
```from flytekit.remote import FlyteRemote
from flytekit.configuration import Config, SerializationSettings, ImageConfig
# Using image pushed to local registry at localhost:30000
img = ImageConfig.from_images(
"localhost:30000/repo:latest", {"repo": "localhost:30000/repo:latest"}
)
# FlyteRemote object is the main entrypoint to API
remote = FlyteRemote(
config=Config.for_sandbox(),
default_project="repo",
default_domain="development",
)
# Get Task
# flyte_task = remote.fetch_task(name="workflows.ray_example", version="v1")
flyte_task = remote.fetch_task(
name="workflows.ray_example",
version="v1",
project="repo",
domain="development",
)
flyte_task = remote.register_task(
entity=flyte_task,
serialization_settings=SerializationSettings(image_config=None),
version="v2",
)
flyte_workflow = remote.register_workflow(
entity=flyte_task,
serialization_settings=SerializationSettings(image_config=None),
version="v1",
)
flyte_launch_plan = remote.register_launch_plan(entity=flyte_task, version="v1")```
Yet I still receive the `FlyteEntityNotExistException`. Apologies if the answer is obvious. Thank you again so much for any help/assistance you can provide!
|
Thank you for the quick response.
I think I'm having trouble figuring out what my flyte_entity should be. Let's assume my project name is `repo`, and I have the `ray_example.ipynb` file in the `workflows` folder, and I'm trying to add the workflow to the `development` domain.
I was adding a new separate cell to the bottom of the Jupyter Notebook `ray_example.ipynb` file like so:
```from flytekit.remote import FlyteRemote
from flytekit.configuration import Config, SerializationSettings, ImageConfig
# Using image pushed to local registry at localhost:30000
img = ImageConfig.from_images(
"localhost:30000/repo:latest", {"repo": "localhost:30000/repo:latest"}
)
# FlyteRemote object is the main entrypoint to API
remote = FlyteRemote(
config=Config.for_sandbox(),
default_project="repo",
default_domain="development",
)
# Get Task
# flyte_task = remote.fetch_task(name="workflows.ray_example", version="v1")
flyte_task = remote.fetch_task(
name="workflows.ray_example",
version="v1",
project="repo",
domain="development",
)
flyte_task = remote.register_task(
entity=flyte_task,
serialization_settings=SerializationSettings(image_config=None),
version="v2",
)
flyte_workflow = remote.register_workflow(
entity=flyte_task,
serialization_settings=SerializationSettings(image_config=None),
version="v1",
)
flyte_launch_plan = remote.register_launch_plan(entity=flyte_task, version="v1")```
Yet I still receive the `FlyteEntityNotExistException`. Apologies if the answer is obvious. Thank you again so much for any help/assistance you can provide!
| I'm assuming you've not registered the flyte task yet. In that case, you needn't fetch the task. Directly register it. Check out <https://docs.flyte.org/projects/cookbook/en/latest/auto/case_studies/feature_engineering/feast_integration/Feast_Flyte_Demo.html> example.
|
I'm assuming you've not registered the flyte task yet. In that case, you needn't fetch the task. Directly register it. Check out <https://docs.flyte.org/projects/cookbook/en/latest/auto/case_studies/feature_engineering/feast_integration/Feast_Flyte_Demo.html> example.
| Thank you for your response <@U01J90KBSU9>. I believe in my code snippet above, that's what I've done in this section:
```flyte_task = remote.register_task(
entity=flyte_task,
serialization_settings=SerializationSettings(image_config=None),
version="v2",
)```
Interestingly, this user suggests that registering workflows inside Jupyter notebooks is not possible: <https://github.com/flyteorg/flyte/issues/3588#issuecomment-1509599891>
If it is indeed possible, I would be happy to work on an MR to add an example Jupyter Notebook file to the Ray example (<https://docs.flyte.org/projects/cookbook/en/latest/auto/integrations/kubernetes/ray_example/ray_example.html>), just need to figure out how to get an example workflow working via a Jupyter Notebook. I'm just pushing the Docker image to the local registry at `localhost:30000`, which is what I would think would be the simplest implementation possible to run a workflow.
I do notice that it looks like there is an example with Papermill, but obviously that's not Ray: <https://docs.flyte.org/projects/cookbook/en/latest/auto/integrations/flytekit_plugins/papermilltasks/simple.html#sphx-glr-auto-integrations-flytekit-plugins-papermilltasks-simple-py|https://docs.flyte.org/projects/cookbook/en/latest/auto/integrations/flytekit_plugins/papermilltasks/simple.html#sphx-glr-auto-in[…]ltasks-simple-py>
|
Thank you for your response <@U01J90KBSU9>. I believe in my code snippet above, that's what I've done in this section:
```flyte_task = remote.register_task(
entity=flyte_task,
serialization_settings=SerializationSettings(image_config=None),
version="v2",
)```
Interestingly, this user suggests that registering workflows inside Jupyter notebooks is not possible: <https://github.com/flyteorg/flyte/issues/3588#issuecomment-1509599891>
If it is indeed possible, I would be happy to work on an MR to add an example Jupyter Notebook file to the Ray example (<https://docs.flyte.org/projects/cookbook/en/latest/auto/integrations/kubernetes/ray_example/ray_example.html>), just need to figure out how to get an example workflow working via a Jupyter Notebook. I'm just pushing the Docker image to the local registry at `localhost:30000`, which is what I would think would be the simplest implementation possible to run a workflow.
I do notice that it looks like there is an example with Papermill, but obviously that's not Ray: <https://docs.flyte.org/projects/cookbook/en/latest/auto/integrations/flytekit_plugins/papermilltasks/simple.html#sphx-glr-auto-integrations-flytekit-plugins-papermilltasks-simple-py|https://docs.flyte.org/projects/cookbook/en/latest/auto/integrations/flytekit_plugins/papermilltasks/simple.html#sphx-glr-auto-in[…]ltasks-simple-py>
| Papermill is for running jupyter notebook as a flyte task. In your case, I assume you're trying to register tasks and workflows that are present within your jupyter notebook which is absolutely possible. What <@USU6W5ATA>'s telling is that you cannot register code present in your Jupyter with `pyflyte run` or `pyflyte register`. You need to use FlyteRemote to register your code. Can you try registering by following the example I've sent earlier?
|
Papermill is for running jupyter notebook as a flyte task. In your case, I assume you're trying to register tasks and workflows that are present within your jupyter notebook which is absolutely possible. What <@USU6W5ATA>'s telling is that you cannot register code present in your Jupyter with `pyflyte run` or `pyflyte register`. You need to use FlyteRemote to register your code. Can you try registering by following the example I've sent earlier?
| Thanks so much for the help <@U01J90KBSU9>. I closed my GitHub issue as I did get the workflow to successfully register via importing the Jupyter Notebook via Papermill.
However I'm still curious about FlyteRemote, I set up the FlyteRemote syntax, but I see that you said here that you can't use `pyflyte run` or `pyflyte register`, and I don't really see in the documentation regarding FlyteRemote what the equivalent commands would be to register workflows via FlyteRemote would be. If I'm using FlyteRemote, what command would need to be run to register workflows, since we can't use `pyflyte register`? Apologies again for the confusion on my part.
|
Thanks so much for the help <@U01J90KBSU9>. I closed my GitHub issue as I did get the workflow to successfully register via importing the Jupyter Notebook via Papermill.
However I'm still curious about FlyteRemote, I set up the FlyteRemote syntax, but I see that you said here that you can't use `pyflyte run` or `pyflyte register`, and I don't really see in the documentation regarding FlyteRemote what the equivalent commands would be to register workflows via FlyteRemote would be. If I'm using FlyteRemote, what command would need to be run to register workflows, since we can't use `pyflyte register`? Apologies again for the confusion on my part.
| No problem! You'd have to use `register_task` / `register_workflow` / `register_launch_plan` / `register_script` function. FlyteRemote is a Python API. You can use it to programmatically register your code.
<https://github.com/flyteorg/flytekit/blob/e865db57d3bfbb7fb997417b052a05bc871cb0ed/flytekit/remote/remote.py>
|
No problem! You'd have to use `register_task` / `register_workflow` / `register_launch_plan` / `register_script` function. FlyteRemote is a Python API. You can use it to programmatically register your code.
<https://github.com/flyteorg/flytekit/blob/e865db57d3bfbb7fb997417b052a05bc871cb0ed/flytekit/remote/remote.py>
| Ah thank you! I see now. That makes sense. :slightly_smiling_face:
|
hi, I installed master version of kuberay operator and deployed the ray cluster. When I submit the workflow, I could see only head pod getting created and worker pods are not getting created. In ray operator logs I could find some error in creating worker pods. It says failed quota but we have enough project quota and also the requested resources are very less. do anyone have idea on how to solve this issue
`@task(task_config=ray_config, requests=Resources(mem="2000Mi", cpu="1"), limits=Resources(mem="3000Mi", cpu="2"))`
```- development:
- projectQuotaCpu:
value: "64"
- projectQuotaMemory:
value: "150Gi"
value: |
apiVersion: v1
kind: ResourceQuota
metadata:
name: project-quota
namespace: {{ namespace }}
spec:
hard:
limits.cpu: {{ projectQuotaCpu }}
limits.memory: {{ projectQuotaMemory }}```
| can you ask this question in the ray slack?
this is really a ray problem seems like
|
Hi, we recently opened a <https://github.com/flyteorg/flyteplugins/pull/321|pull request> to address the following <https://github.com/flyteorg/flyte/issues/2883|issue> (inter-cluster communication between Flyte and custom Ray cluster). Can someone please review it? It adds to a product Spotify is building that is integral to our machine learning platform.
cc <@U03F38WVDHN>
| Hey <@USU6W5ATA> <@UNZB4NW3S> we are trying to make Flyte work for our internal Flyte cluster setup. <@U03T940SK40> opened this PR to enable the inter-cluster communication feature for Ray plugin. Could you guys help take a look? Thank you so much!
|
Hey <@USU6W5ATA> <@UNZB4NW3S> we are trying to make Flyte work for our internal Flyte cluster setup. <@U03T940SK40> opened this PR to enable the inter-cluster communication feature for Ray plugin. Could you guys help take a look? Thank you so much!
| Thanks, reviewing
|
Thanks, reviewing
| :+1:
cc <@U01E1L78CLA>
|
:+1:
cc <@U01E1L78CLA>
| Technically, the changes are similar to what Spotify did for the <https://github.com/spotify/flyte-flink-plugin|Flyte-Flink plugin>. Our data infra team also added context to the issue I linked. Thanks!
|
Technically, the changes are similar to what Spotify did for the <https://github.com/spotify/flyte-flink-plugin|Flyte-Flink plugin>. Our data infra team also added context to the issue I linked. Thanks!
| cc <@U029U35LRDJ> to review as well
|
cc <@U029U35LRDJ> to review as well
| timely :smile:
|
timely :smile:
| Looks great, merged, thanks <@U03T940SK40>! Now we would just need to update the flyteplugin dependency version in flytepropeller. Is this something you're looking for an immediate propeller release on or are you building your own image anyways?
|
Looks great, merged, thanks <@U03T940SK40>! Now we would just need to update the flyteplugin dependency version in flytepropeller. Is this something you're looking for an immediate propeller release on or are you building your own image anyways?
| Thanks a lot <@U029U35LRDJ>! Yess -- Since we prefer to always stay on a stable Flyte release, it is better if we make a new release to cover this plugin
|
Thanks a lot <@U029U35LRDJ>! Yess -- Since we prefer to always stay on a stable Flyte release, it is better if we make a new release to cover this plugin
| Stable Flyte release will be 1.4
|
Stable Flyte release will be 1.4
| <@UNZB4NW3S>, what’s the rough timeline for Flyte 1.4 release?
|
<@UNZB4NW3S>, what’s the rough timeline for Flyte 1.4 release?
| So 1.4 is the current stable, 1.5 will be end of month (maybe first week of April) since we switched to a monthly release cycle. I opened <https://github.com/flyteorg/flytepropeller/pull/542|this PR> to get the plugin updates merged into propeller and will make sure this is merged for the 1.5 release.
|
So 1.4 is the current stable, 1.5 will be end of month (maybe first week of April) since we switched to a monthly release cycle. I opened <https://github.com/flyteorg/flytepropeller/pull/542|this PR> to get the plugin updates merged into propeller and will make sure this is merged for the 1.5 release.
| Thanks <@U029U35LRDJ>!
|
Hi Guys, I am using bazel to build the flyte target but when I use bazel output binaries to serialize and register the workflows it lead to _*ModuleNotFoundError: No module named 'pyflyte'*_ at the time of task execution. The error occurred because the value of `resolver` in task container argument changed from usual `flytekit.core.python_auto_container.default_task_resolver` to `pyflyte.pypi_flytekit.site-packages.flytekit.core.python_auto_container.default_task_resolver` . Did anyone face this issue ? is there a way to control this?
| this just sounds like the virtualenv or the local python environment doesn’t have flytekit installed.
pyflyte comes stock with flytekit, it should always be present
|
this just sounds like the virtualenv or the local python environment doesn’t have flytekit installed.
pyflyte comes stock with flytekit, it should always be present
| I am trying to ship pyflyte as a Bazel dependency, so not installing it externally on the environment.
|
I am trying to ship pyflyte as a Bazel dependency, so not installing it externally on the environment.
| <@U04MG1WLA4T> I wound up wrapping pyflyte in a `py_binary` target and adding that to my `py3_image`. That pattern should work for you
|
One thing that'd be awesome to share is how each of our implementations is handling serialization, registration & execution. Do you all have separate targets for each, or are any of the steps handled together?
In our case, we handle both serialization & registration in a single `.register` target, and handle execution w/ a `py_binary` target that takes in the launch plan name & user-specified CLI args that are passed to `flyte_remote.execute` inside that binary. One interesting concern is that it requires the user to remember to register prior to attempting to launch an execution, and this is an area we'd really like to clean up and make more seamless. Curious if anyone else has different solutions for this?
| Hi <@U03BT8P2XGA>, you got any lead here ? I am also looking forward to make the process one shot, without manually worrying about such dependency. Below is our way of doing it.
we have also combined serialization & registration in a single `.register` target, My design for launchplan is to pass a list of launchplans defined in workflow file as an attribute to flyte_library rule and it will prepare a separate target for launchplan, which will have dependency on register. So flow will look like
`.push` for image
`.register` serialize and register (serialization dont produce any executable just the serialized proto consumed by registration)
`.launch` activate the launcplans (deppends on registration but that will only build the executable for registeration will not run it)
All the three steps will use the `commit-id` as version and dirty-repo will result in failure
We have also ensured to make `pyflyte*` and `flytectl` as bazel dependency rather than installing separately in the dev environment
|
:eagle::link: *<https://github.com/ByronHsu/LangChain-FlyteBot|Building Flyte LangChain Bot on Flyte>*!
The bot becomes a Flyte expert by consuming all public slack conversation and Flyte source code. He can answer everything about Flyte!
Example:
> Human: how is fast registration implemented?
> AI: Fast registration in Flyte allows users to update workflow code without having to rebuild the entire docker image. This is achieved by zipping up the code, uploading it to the configured blob store using a signed URL, and then prepending a command to the task’s normal command. At runtime, the command downloads the archive from the blob store and unzips it to the root of the container’s image. The `pyflyte package` command with the `--fast` flag can be used to enable fast registration. It is important to note that registration is a two-step process involving compilation and registration, and separate commands are available for each step. More information can be found in the Flyte documentation.
Feel free to check out my repo :smile:
| <@UNZB4NW3S>
|
<@UNZB4NW3S>
| Fab! I'm working on fine-tuning an LLM on flyte slack data.
|
Fab! I'm working on fine-tuning an LLM on flyte slack data.
| This is awesome
<@U042Z2S8268> could you write a blog we can help and share this
What’s the data here the docs in a vector index
Niels had written this sometime ago <https://github.com/unionai-oss/flyte-attendant|https://github.com/unionai-oss/flyte-attendant>
|
This is awesome
<@U042Z2S8268> could you write a blog we can help and share this
What’s the data here the docs in a vector index
Niels had written this sometime ago <https://github.com/unionai-oss/flyte-attendant|https://github.com/unionai-oss/flyte-attendant>
| <@UNZB4NW3S> the data comes from slack channel and most of the flyte repo: <https://github.com/ByronHsu/LangChain-FlyteBot/blob/master/ingest_data.py#L149>
happy to share. Can i use github readme as the blog? or i should publish somewhere else
|
<@UNZB4NW3S> the data comes from slack channel and most of the flyte repo: <https://github.com/ByronHsu/LangChain-FlyteBot/blob/master/ingest_data.py#L149>
happy to share. Can i use github readme as the blog? or i should publish somewhere else
| publish it on linkedin
or on <http://flyte.org/blog|flyte.org/blog>
cc <@U04H6UUE78B> / <@U01J90KBSU9> / <@U0327QS23K4>
|
publish it on linkedin
or on <http://flyte.org/blog|flyte.org/blog>
cc <@U04H6UUE78B> / <@U01J90KBSU9> / <@U0327QS23K4>
| Hey <@U042Z2S8268> this is amazing and we really appreciate it. For the blog, let us know what do you need (reviews, editorial work,etc), happy to help (in fact, this makes me happy in many ways!)
As for where to post it, I guess both Flyte blog and LI could be used?
|
Hey <@U042Z2S8268> this is amazing and we really appreciate it. For the blog, let us know what do you need (reviews, editorial work,etc), happy to help (in fact, this makes me happy in many ways!)
As for where to post it, I guess both Flyte blog and LI could be used?
| > both Flyte blog and LI
sounds good! I can have a draft tonight
i might need the help for blog banner design :joy:
how to publish a blog to flyte <@U04H6UUE78B>
|