Mix Windows and Linux nodes with network share

Installation and configuration.
Post Reply
User avatar
andrep
Posts: 6
Joined: Wed Nov 02, 2022 1:36 pm
Location: Netherlands
Contact:

Mix Windows and Linux nodes with network share

Post by andrep »

Hi,

I was looking for some examples to combine Windows and Linux nodes with a storage location on a network share.
In Windows this location is mapped as a drive letter, but in Linux - of course - it is just a /mnt/share location.
Most of our renders are coming from Windows hosts, so the drive letter naming is fine and the render nodes can store their finished renders on that share.
However, our Linux hosts fail because they can't find the drive letter to get or store the files to safe the finished renders.
I was thinking maybe there is an example available to rename the share location in a configuration file, or should I set up two separate render servers for each distro?
User avatar
andrep
Posts: 6
Joined: Wed Nov 02, 2022 1:36 pm
Location: Netherlands
Contact:

Re: Mix Windows and Linux nodes with network share

Post by andrep »

I've got it handled after looking at the error logs.
It was looking for a folder Z: in /var/tmp/afanasy/
So, if I mount the share at /var/tmp/afanasy/Z:, it works :)

I also tried the below in my config.json on all renders, but that didn't seem to work for our setup.

Code: Select all

.....
"OS_linux":{

        "pathsmap":[
                ["/mnt/triglav/",       "Z:/"]
        ]
}
"OS_windows":{

        "pathsmap":[
                ["Z:/",	"/mnt/triglav"]
        ]
}
.....
User avatar
timurhai
Site Admin
Posts: 911
Joined: Sun Jan 15, 2017 8:40 pm
Location: Russia, Korolev
Contact:

Re: Mix Windows and Linux nodes with network share

Post by timurhai »

Hello!

Sorry for the delay. We had a deadline and noticed your posts just now.

Paths map setup has a "client <-> server" pairs:
https://cgru.readthedocs.io/en/latest/a ... #paths-map
On job submisson it goes in "client -> server" direction, on task start it goes in "client <- server" direction.
So server stores some "server" paths, and each client can transfer it back to "client".

If you have:

Code: Select all

"OS_windows":{"pathsmap":[["Z:/","/mnt/triglav"]]}
you do not need:

Code: Select all

"OS_linux":{"pathsmap":[["/mnt/triglav/","Z:/"]]}
Also you should test your json file for syntax errors.
If some file exactly contains that pasted piece - there is no comma between members - it is an error, you have no paths map configured.
Timur Hairulin
CGRU 3.3.1, Ubuntu 20.04, 22.04, MS Windows 10 (clients only).
Post Reply