Team Render Cloud Control is very easy to use. Highlights of work presented in this video (Control+MouseClick). You just need to know some important conditions for its operation and configuration to avoid further mistakes and losing money. So let’s start.

The utility automates launching applications Team Render Client and Team Render Server inside the instances to automatically create a render farm. There may exist several render farms, the utility identifies all participants in each of the tag «Name». The group name must contain only latin characters, digits, "-" (minus) and "_" (underscore).

name_tag.png

To add more instances to an already running the renderfarm, you need to create a similar request, with the same data on the Availability Zone, a Placement Group and with the same identifier in the tag «Name».

ava_placement.jpg

name_tag_new.png

Instances run and determine automatically the server and connect to it as clients.

To split a render farm for a few, you need to change the tag «Name» at the relevant instances and send the command Reboot. After rebooting, the new group will appear in the server and the remaining instances connect to it as clients.

name_tag.png

How monitor works

monitor.png

After starting the instance a user is notified about the beginning of work, and the monitor starts monitoring application Team Render Client. Every minute, the monitor checks how the application is loading the CPU of the instance on the basis of the data changes the status in the console and executes the action.

Status Monitor

  1. Standby - standby mode. Lasts 40 minutes. After this action will be performed.
  2. Busy - Client is loading. At this moment, the render job is running.
  3. Idle - Client is idle. This status is always displayed after a Busy. Idle state of the instance is a period of time specified in the TR Time, when this period of time is finished, the TR Action is executed.
  4. No_Client - Team Render Client application is not running, there is no monitoring data.

       

If the field TR Action empty, and the field TR Time is set, then after a predetermined time period, the instance will change its status to Standby.

If the field TR Action is set, and the field TR Time is empty, then the action will not be executed.

The default settings fields TR Action and TR Time, are set by user in the tags of a paticular Security group, which is used when sending a request. They are used only when you start the instance.

sec1.png

sec2.png

 

Monitor actions

  1. stop - stops the instance. If applied to the instance on the spot request, the value is changed to terminate.
  2. terminate - terminates (delete) instance.
  3. message - sends to user an alert by email or Pushbullet. Moves the instance to the Standby status.
  4. mstop, mterminate takes the appropriate action, plus sending notification.

Attention! Incorrectly filled fields TR Action and TR Time monitor cleans up. Be careful, do not let typos!        

Notifications

If Pushbullet Access Token is specified in the file %userprofile%\TRCC\pushbullet_token.txt, all alerts will be send through the Pushbullet service.

If the Access Token is not specified or incorrect, all notifications will be send to your email.    

Preferences

serv.png

Attention! TRCC working on standard port settings for the server - 5402, the client - 5401, web interface - 8080. If you change these settings in the program preferences, it is necessary to make similar changes in the file %userprofile%\.aws\tr_scripts.ini