Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Orion specific question,
Why when I start orion agent
```orion agent start```
and I set the following env variable to connect to the orion server
```      PREFECT_ORION_API_HOST: orion_server
      PREFECT_ORION_API_PORT: 4200```
the agent still try to create a database in this case using sqllite on the agent?

Hey <@U012J275170> - as of the latest orion release, the assumption is that all services are running on the same machine so the Agent currently talks directly to the DB (instead of over an API).  This was an implementation detail that helped validate DB performance but is not intended as the go-forward agent implementation.

We are currently working on making orion more deployable which includes a minor agent refactor so that setups like yours will begin working!  We'll be sure to highlight this in the release notes as they come out :+1:

Great thank you, Indeed looking at the restapi I don't see any agent capability. I have been able to make my setup working by making the agent talking directly to my postgres database indeed.
Was trying to replicate the current prefect setup on which all communication are happening using the graphql indeed :slightly_smiling_face:
Looking forward to see this new capability.

Does it mean at the moment the env variable below are only used for registering deployment ?
```      PREFECT_ORION_API_HOST: orion_server
      PREFECT_ORION_API_PORT: 4200```


Yea those environment variables are needed for both registering deployments but also for running workflows / deployments

ok,
I have another follow up question (not my current setup), if I have multiple agent,

•  who is orchestrating which agent will start which flow ?
• does it mean both agent would start the flow ?
• Where is the orchestration scheduler happening ?

because we haven't released the ability to truly deploy orion to a distributed environment, we haven't exposed the necessary interfaces for matching deployments to specific agents / multi-agent setups

the scheduler is a service that current is automatically run when you run `prefect orion start` but (you can probably guess what I'm about to say!) it hasn't been separated out yet as a standalone service

Indeed, this is what I expect :slightly_smiling_face:
Thank you for your reply. i know this is quite early for orion. Just testing for a personal project.
May have more question going forward

awesome -- yup we love to see the questions.  Seeing what questions we get in the early days helps us prioritize our roadmap for releases, so this is great!  I've already made a note from your questions :smile: