Greg Desmarais
07/17/2020, 9:50 PM2020-07-17T16:45:04.792-04:00
distributed.scheduler - INFO - Scheduler at: <tcp://10.72.9.106:8786>
2020-07-17T16:45:04.792-04:00
distributed.scheduler - INFO - dashboard at: :8787
2020-07-17T16:45:09.566-04:00
distributed.scheduler - INFO - Receive client connection: Client-675482da-c86e-11ea-b8be-acde48001122
2020-07-17T16:45:09.577-04:00
distributed.core - INFO - Starting established connection
Starting established connection
and the client issuing the flow.run() sits there with Starting flow run
.Jeremiah
07/17/2020, 10:16 PMrun
command and launch the flow into the Dask cluster
• Similarly, when you say you’re calling flow.run()
you’ll probably actually want to call flow.register()
and then issue either a GQL command to run the flow via Agent, or click the run
command in the Prefect UIflow.register()
against the server backend.Greg Desmarais
07/18/2020, 2:48 AMprefect server start
? That seems like a logical place to me. But...when I tried that, I got:
prefect.utilities.exceptions.AuthorizationError: No agent API token provided.
My guess is that I need to update my .prefect/config.toml to point the agent at my server deployment.prefect.context.config.cloud.api
, or prefect.context.config.server.host
?Robin
07/18/2020, 7:06 AMprefect agent start kubernetes --token MY_TOKEN
with a token that you can create via the prefect cloud UI >> Team >> API Tokens
Hope that helps 🙂
https://docs.prefect.io/orchestration/agents/overview.htmlGreg Desmarais
07/18/2020, 2:54 PMserver
.Robin
07/18/2020, 3:09 PM