Photoscan on demand processing workflow

[photoscan_user]

What if I want to process data on some remote server like aws instance, how workflow should be organized in terms of activation / deactivation?

Like:
start server
activate photoscan
deacticvate photoscan
turn off server

Is number of activations is limited?

What happens if I will run spot instance that can be shut down at any time?

Like:
start server
activate photoscan
ooops accidentally shutdown

[Alexey Pasumansky]

Hello photoscan_user,

Node-locked license activation procedure is creating so-called "rehostable" directory, that contains the system information to be used for the license validation for the next time the application is started.

So if the folder is deleted when the virtual machine is terminated or if the system parameters do not match the "rehostable" information when the machine is started for the next time - the license would be likely unusable.

[photoscan_user]

Seems I don't fully understand concept of "rehostable" directory, as mentioned here
http://www.agisoft.com/forum/index.php?topic=9005.msg42218#msg42218
licence is stored in .lic file or there are some other files stored in the system?

What about if I don't use spot instances that can be shutdown accidentally, can I use this method for activate \ deactivate of photoscan?
https://agisoft.freshdesk.com/support/solutions/articles/31000134012-how-to-move-transfer-a-photoscan-license-to-another-computer
start server
activate photoscan
deacticvate photoscan
shutdown server

Also according to this
https://github.com/agisoft-llc/cloud-scripts
seems there should be done some exra work to run photoscan on server, is it only needed for run photoscan with GUI or it also affects speed of GPU processing even if I run photoscan with -platform offscreen?

[Alexey Pasumansky]

Hello photoscan_user,

Rehostable license activation assumes creation of the additional directory:
for Windows: C:/ProgramData/Reprise/agisoft/photoscan-pro/
for Linux and Mac OS X: /var/tmp/agisoft/photoscan-pro/
(default paths can be altered by setting AGISOFT_REHOST_PATH environment variable prior to activation).
This directory cannot be removed or modified, as such actions would affect the license validation (lic file without this directory wouldn't work).

The steps that you mention: start server - activate PhotoScan - deactivate PhotoScan - shutdown server - looks safe.
Some configuring of the cloud-based server may be necessary, if you want to use GPU acceleration, or enable GUI mode (requires OpenGL configuring).