Path translations for Client and Workers #51747

New Issue

Sybren A. Stüvel · 2017-06-08T14:00:50+02:00

Sybren A. Stüvel commented

2017-06-08 14:00:50 +02:00

Currently paths (job storage, render output) are passed as-is between the Client (like the Blender Cloud Add-on) and Flamenco Workers. This will cause failure when

paths are different on the Client and the Workers (say /media/server/job on the Client and /mnt/server/job on the Workers).
the Client and Worker OSses use fundamentally different paths (\server\job on Client running Windows, /mnt/server/jobs on Worker running Linux).

There are roughly two approaches to this:

Introduce variables for the different paths that are in use (like job storage and render output, but future job types could have other paths), communicate those to the Client and Workers. This should be available to the server, so that selecting a Manager in the Blender Cloud Add-on picks up on this. Configuration could happen on the Server, or be part of the Manager config that is pushed to the Server.
Have path translation rules, so that the Client can just use any desired path, which gets translated to a suitable path before sending to the Workers. This could be simple slash conversion and string/regexp replacement. This translation can happen on the Manager.

Currently paths (job storage, render output) are passed as-is between the Client (like the Blender Cloud Add-on) and Flamenco Workers. This will cause failure when - paths are different on the Client and the Workers (say /media/server/job on the Client and /mnt/server/job on the Workers). - the Client and Worker OSses use fundamentally different paths (\\server\job on Client running Windows, /mnt/server/jobs on Worker running Linux). There are roughly two approaches to this: 1. Introduce variables for the different paths that are in use (like job storage and render output, but future job types could have other paths), communicate those to the Client and Workers. This should be available to the server, so that selecting a Manager in the Blender Cloud Add-on picks up on this. Configuration could happen on the Server, or be part of the Manager config that is pushed to the Server. 2. Have path translation rules, so that the Client can just use any desired path, which gets translated to a suitable path before sending to the Workers. This could be simple slash conversion and string/regexp replacement. This translation can happen on the Manager.

Sybren A. Stüvel commented

2017-06-08 14:00:50 +02:00

Changed status to: 'Open'

Sybren A. Stüvel commented

2017-06-08 14:00:50 +02:00

Added subscribers: @dr.sybren, @fsiddi

Sybren A. Stüvel commented

2017-06-09 10:56:31 +02:00

Changed status from 'Open' to: 'Resolved'

Sybren A. Stüvel closed this issue

2017-06-09 10:56:31 +02:00

Sybren A. Stüvel self-assigned this 2017-06-09 10:56:31 +02:00

Sybren A. Stüvel commented

2017-06-09 10:56:31 +02:00

Implemented:

Server: 2e55892272
Manager: e48261c252554db0fdb51a4961126e03b05e3d2b
Blender Cloud add-on: a51f61d9b5dac066b0a54ea9c985b2dbc1446334

Workers are oblivious to this change, so no change required there.

Implemented: - Server: 2e55892272a224d5ecae3193faba8b337b2b5ba8 - Manager: [e48261c252554db0fdb51a4961126e03b05e3d2b](https://github.com/armadillica/flamenco-manager-go/commit/e48261c252554db0fdb51a4961126e03b05e3d2b) - Blender Cloud add-on: a51f61d9b5dac066b0a54ea9c985b2dbc1446334 Workers are oblivious to this change, so no change required there.

Sybren A. Stüvel commented

2017-06-09 11:13:11 +02:00

PS: I implemented option 2 (see description above).

Sign in to join this conversation.