Q100329: How do Collective licenses work?

Follow
  1. Foundry
  2. License Help
  3. FAQ

SUMMARY

This article explains how licenses for our Production Collective and Education Collectives work.

MORE INFORMATION

We have released two Collectives, which are bundles of our products:

  • Production Collective contains NukeStudio, Mari and Modo
  • Education Collective contains NukeStudio, Mari, Modo, Katana and CaraVR

A license for a collective entitles you to run all of the products in that collective e.g. if you purchase the Production Collective then you're able to run Modo, Mari and Nuke/NukeX/NukeStudio.
 
The way this works in terms of licenses depends upon what type of license you have, nodelocked or floating.

NOTE: All Education Student Collective licenses are nodelocked.

Nodelocked licenses:
 
A nodelocked collective license consists of a nodelocked license for each product in the collective.  This allows a single machine to use any or all of the programs within that Collective. 
 
Floating licenses:
 
A floating collective license allows a set number of users/hostmachines to be able to run any or all of the programs in the collective.  For example, if you had 3 floating licenses for the Production Collective then you could have up to 3 machines running any combination of Modo, Mari and Nukestudio but you cannot have 3 machines running one product, e.g. Mari, and a 4th running a different product, e.g. Modo.
 
Floating Collective licenses use a special kind of RLM license called token-based licenses, which require another license to work.  A floating collective license therefore includes token licenses for each product in the collective which are token-locked to a primary license for the whole collective.  The example below is for one floating Production Collective license:

HOST <server_name> 12345678abcd 4101
ISV foundry
LICENSE foundry foundry_production_i 2021.1116 16-nov-2021 1 share=h
min_timeout=30 start=10-nov-2021 issuer=sf
contract=V1:36139368-062d-4d89-b693-59d93dcd2592 issued=10-nov-2021
replace options=a09 _ck=11d61675cf sig="60Q04580RFV8GJ0314P4R1CUBFN
PBA6M4F4C3RN708AG1M3QBNSKJV5JGS7YV25841F05E222B4TE"

LICENSE foundry modo_i 2021.1116 16-nov-2021 token_locked share=h
min_timeout=30 start=10-nov-2021 issuer=sf
contract=V1:36139368-062d-4d89-b693-59d93dcd2592 issued=10-nov-2021
token="<foundry_production_i 2021.1116 1>" _ck=13d8d8f032 sig="60Q0
4580R7FSXXG6ASHMRM696KN0HKB11DWFPYQB08AG119V90H2PRCDEW4JX4WTGSR2VCS
R68160"

LICENSE foundry mari_i 2021.1116 16-nov-2021 token_locked share=h
min_timeout=30 start=10-nov-2021 issuer=sf
contract=V1:36139368-062d-4d89-b693-59d93dcd2592 issued=10-nov-2021
token="<foundry_production_i 2021.1116 1>" options=351
_ck=0dd871d22e sig="60PG4580MM2YRQVUPRNMU3UNETRX1Q8S82CG5SKR08A1K7J
CSBKX163YE40XKMGV652VBJHGSX6G"

LICENSE foundry nuke_i 2021.1116 16-nov-2021 token_locked share=h
min_timeout=30 start=10-nov-2021 issuer=sf
contract=V1:36139368-062d-4d89-b693-59d93dcd2592 issued=10-nov-2021
token="<foundry_production_i 2021.1116 1>" options=fe9
_ck=17d8dce060 sig="60P0452PHAR7MB6HDSWNFCK5EFHW9RW9WEUUME822G7FFMK
CWDKDVEPFBMYRE5Y5WMEF82P9KC"

LICENSE foundry nukex_i 2021.1116 16-nov-2021 token_locked share=h
min_timeout=30 start=10-nov-2021 issuer=sf
contract=V1:36139368-062d-4d89-b693-59d93dcd2592 issued=10-nov-2021
token="<foundry_production_i 2021.1116 1>" options=f31
_ck=8fd8a2ea93 sig="60Q04580GE5JHN2EPU4947MSV18WXYMCVKBJG7EH08AG1GE
3SV42AM4W8740HPXPVK9XSJ3N51KME"

LICENSE foundry nukestudio_i 2021.1116 16-nov-2021 token_locked
share=h min_timeout=30 start=10-nov-2021 issuer=sf
contract=V1:36139368-062d-4d89-b693-59d93dcd2592 issued=10-nov-2021
token="<foundry_production_i 2021.1116 1>" options=00e
_ck=afd89da192 sig="60PG4580NY6EWH6SQC2NEHD7AE1AG1TYA78720N308A1N5Q
5Q8BHE0QTR6KPXXX6BGWRC7WGSX00"

 
The way this works when users run the programs is as follows:
  1. UserA user launches a product, e.g. Modo, which asks the server for a modo_i license
  2. Modo finds the valid modo_i license which is token locked to the foundry_production_i license
  3. If the foundry_production_i license is available it is checked out to UserA and Modo runs

  4. With Modo still running, UserA then launches Mari which asks the server for a mari_i license
  5. Mari finds the valid mari_i license which is token locked to the foundry_production_i license
  6. UserA already has the foundry_production_i license checked out so the Mari license request works and Mari runs.

  7. UserB launches a product, e.g. Mari, and asks for mari_i license
  8. Mari finds the valid mari_i license which is token locked to the foundry_production_i license
  9. The foundry_production_i license is not available so Mari will not run.


 
FURTHER READING
More information about some of the licensing topics mentioned above can be found in the following articles:

    We're sorry to hear that

    Please tell us why