search

ynput / ayon-deadline

Deadline addon for AYON
Apache License 2.0
3 stars 11 forks source link

AY-6587_Deadline: use two or more Ayon servers in one DL repo #27

Closed ynbot closed 3 weeks ago

ynbot commented 2 months ago

Please describe the enhancement you have in mind and explain what the current shortcomings are?

It would be useful if Deadline should be capable to work with two or more Ayon servers (in production and staging/test/dev). Now only one server is available and sometimes it is a bit clumsy

How would you imagine the implementation of the enhancemenet?

No response

Describe alternatives you've considered:

No response

Additional context:

link to discussion on [Discord]() (might be a private channel)

This issue was automatically created from Clickup ticket AY-6587

jakubjezek001 commented 2 months ago

@tweak-wtf Can you provide some practical examples for this proposal?

tweak-wtf commented 1 month ago

yes, this originated from our switch from the legacy to the new cloud backend. we were on 2 separate domains for ayon cloud. so when migrating projects we had to stop rendering, do the switch in ayon's dl plugin settings and continue. no big deal but would put prod on hold for a moment.

possible use case would be running a second ayon instance as complete separate dev environment from prod or another isolated instance for confidential projects. not sure whether one would actually use the same deadline for confidential projects tho.

in case of the dev env... being able to use the same deadline repo as in prod would make developing ayon addons that use deadline easier imho as some require frequent server reboots which might not be desirable on the prod instance.

kalisp commented 1 month ago

How you would imagine separation of jobs between these two AYON servers? Eg. submission job must somehow know that it belongs to AYON1. I could imagine that submission would contain AYON_SERVER_URL to override what is configured in Deadline plugin. That env var (or newly created one to limit unknown issues) could be set in ayon+settings://core/project_environments and pass it only if present.

BigRoy commented 1 month ago

I could imagine that submission would contain AYON_SERVER_URL to override what is configured in Deadline plugin. That env var (or newly created one to limit unknown issues) could be set in ayon+settings://core/project_environments and pass it only if present.

Meh - the address to use shouldn't need to be configured - all we'd need is a toggle that says "Submit along your AYON server URL" because the AYON server URL would be the one you are connected to in your current session and are publishing with. I've actually done this in my test runs from dev too so I can have one deadline running - but with my 'dev' jobs it targets my local dev server instead.

Submitting along AYON_SERVER_URL to the EnvironmentKeyValue works just fine last time I tried. Also - it would be surprisingly easy to implement with this PR: https://github.com/ynput/ayon-deadline/pull/32 because it could just be an additional optional plug-in.

tweak-wtf commented 1 month ago

Meh - the address to use shouldn't need to be configured - all we'd need is a toggle that says "Submit along your AYON server URL" because the AYON server URL would be the one you are connected to in your current session and are publishing with.

exactly like this! would also make the AYON Server URL in the Deadline Plugin obsolete as on the deadline side a worker would just pick up the Server URL from the job and authenticate against that.

BigRoy commented 1 month ago

exactly like this! would also make the AYON Server URL in the Deadline Plugin obsolete as on the deadline side a worker would just pick up the Server URL from the job and authenticate against that.

It'll have to be optional configurable via settings to enable/disable it though - there may be configurations where the Deadline clients (for whatever reason!?) access the AYON server via a different URL potentially?

tweak-wtf commented 1 month ago

true that. would it make sense to make this configurable in the Deadline Plugin or rather from AYON? from the deadline plugin we could have that checkbox Use Server URL from Plugin Info and if it isn't set u have to specify the AYON server to publish to as usual. we would always pass the server URL used to submit from in the plugin info and if an AYON Server URL has been set in the DL plugin we'll use that as an override.

basically this makes it possible to start DCC's from localhost:5000 but submit and publish to https://awesomestudio.ayon.app or vice versa

BigRoy commented 1 month ago

Good question - I'll leave that answer to someone who deals with more complex deadline configurations than I do. Maybe @kalisp or @m-u-r-p-h-y ?