Production over WAN

Administration
1

Is AYON made for WAN usage as well?

Has anyone used AYON over WAN or is it primarily made for LAN? I am thinking about using AYON for a production but we don’t share a local network. Everything would need to go over the internet. I have concerns about network speed as not every artist has a super fast network connection.

How does AYON load data? Does it only download necessary files?

What exactly happens when opening a project through the Loader? Does the Loader only load the file structure and then starts when opening a project?

What happens if files are really big and take a time to download?

Would like to hear your experience or the details of the implementation. Any advise for my scenario?
Thanks in advance

2

Hello,

AYON Server like any other docker service can be deployed in you network, either LAN, WAN or Internet.
You can also, get a ready to use online AYON Server via our Ynput Cloud.

Through out AYON, there are different storages you’ll be interacting with:

  1. AYON Server Storage: Dedicated storage within your server which contains required data for the server to operate and has the database and reviewable media (which can be uploaded manually via server web ui or uploaded automatically via pipeline.).
  2. Studio Storage: Shared storage across your studio which contains all pipeline data like workfiles and published products. it’s also where loaders bring products. Locations of this storage are configured on your AYON Server.
  3. Remote Storage: This is an online storage like Google’s or Dropbox’s where you can sync your studio storage to it. You can handle this storage yourself via third party applications or via our addon sitesync.

About storage and network performance/speed, this is related to your infrastructure setup.

3

Hi,

My question is how does the user interact with the studio storage? What happens if a user opens a file by using the Loader desktop application? Does it only download files on demand or does it always sync the entire studio storage?

4

Could you elaborate on your intended setup? is it for remote artists or onsite artists.

Also, are you asking about the default behavior of pipeline tools or sitesync addon?

5

All of the artists are remote. We have one centralized server accessible over internet.

I wasn’t aware of the sitesync addon. While it seems like this would address all concerns about maintaining a local copy of files and pushing them to the main server upon committing changes, I would still like to understand what the default behavior is without the sitesync addon

6

Without Sitesync addon:

  • It’s expected that all artists have access to
    1. the AYON Server (either local or on Internet).
    2. the shared storage within the studio. (which can be a network shared storage or storage synced by a third party software)
  • When artists interact with workfiles or publish or load products, they access the files on the shared storage.
  • In this scenario, remote artists would an access to the server as well as shared storage and it’s not covered by AYON (without sitesync addon)
  • Remote artists/any users can still interact with the pipeline and publish products via web publisher addon.

With Sitesync addon:
Well, it’s same as what outlined above plus:

  • Users can download products via AYON Browser Tool
  • Users can open published workfiles.
  • Users can publish products and workfiles.
  • I don’t think user’s local workfiles are synced to the studio storage.

:books: Doc Links: