Job Storage Path in add-on should be platform-dependent #100196

New Issue

Sybren A. Stüvel · 2022-08-04T11:27:08+02:00

Sybren A. Stüvel commented

2022-08-04 11:27:08 +02:00

The getConfiguration OpenAPI operation currently returns the configuration of the Manager as-is. This is insufficient for cross-platform installations, though, as a Manager running Linux will report a Linux path even when the client is running Windows.

This is also reflected in the job storage path as reported by the Blender add-on.

Adding platform and audience parameters like the getVariables operation would resolve this. Those can then be used by the API implementation to perform path modification on the job storage path before returning it.

The `getConfiguration` OpenAPI operation currently returns the configuration of the Manager as-is. This is insufficient for cross-platform installations, though, as a Manager running Linux will report a Linux path even when the client is running Windows. This is also reflected in the *job storage path* as reported by the Blender add-on. Adding `platform` and `audience` parameters like the `getVariables` operation would resolve this. Those can then be used by the API implementation to perform path modification on the job storage path before returning it.

Sybren A. Stüvel commented

2022-08-04 11:27:08 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Sybren A. Stüvel commented

2022-08-04 11:27:08 +02:00

Added subscriber: @dr.sybren

Wouter Vandenneucker commented

2022-08-04 16:52:25 +02:00

Added subscriber: @WouterVandenneucker

Wouter Vandenneucker commented

2022-08-04 16:52:25 +02:00

Came here to write exactly this :)

We've got a threadripper render server with another node on the way running Linux and designer workstations are on windows.

Flamenco 3 being able to run on both would mean I can ditch our self written -far from perfect- render manager that isn't really flexible on adding new devices.

Is there a manual workaround right now using the flamenco-worker.yaml file? There is nothing on changing the shared storage location or file path 'type' in the docs

Came here to write exactly this :) We've got a threadripper render server with another node on the way running Linux and designer workstations are on windows. Flamenco 3 being able to run on both would mean I can ditch our self written -far from perfect- render manager that isn't really flexible on adding new devices. Is there a manual workaround right now using the `flamenco-worker.yaml` file? There is nothing on changing the shared storage location or file path 'type' in the docs

gabe2252 commented

2022-08-04 19:41:26 +02:00

Added subscriber: @gabe2252

zuggamasta commented

2022-08-19 14:55:22 +02:00

Added subscriber: @zuggamasta

zuggamasta commented

2022-08-19 14:57:05 +02:00

We're currently working on our files from Apple Macbooks, and rendering on Windows (could be linux) machines. Sadly flamenco3 is also not able to support us here. And I still did not set up an automation for our case. (Still betting on flamenco getting cross plattform love)

Sybren A. Stüvel commented

2022-08-31 09:31:16 +02:00

This is definitely something that should be supported. The two-way variables will help with this: https://flamenco.blender.org/usage/variables/multi-platform/

There's nothing to do on your side @WouterVandenneucker, this is something that simply has to be coded into Flamenco. I'll see if I can get that done today, before I release the 2nd beta version.

This is definitely something that should be supported. The two-way variables will help with this: https://flamenco.blender.org/usage/variables/multi-platform/ There's nothing to do on your side @WouterVandenneucker, this is something that simply has to be coded into Flamenco. I'll see if I can get that done today, before I release the 2nd beta version.

blender-admin commented

2022-08-31 11:44:37 +02:00

This issue was referenced by 31cf0a4ecc

This issue was referenced by 31cf0a4ecc75db127877218af449610ce9d8df1c

Sybren A. Stüvel commented

2022-08-31 12:06:49 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Sybren A. Stüvel closed this issue

2022-08-31 12:06:49 +02:00

Sybren A. Stüvel self-assigned this 2022-08-31 12:06:49 +02:00

Sign in to join this conversation.