Server system communication diagrams

The communication between CLC software and other local resources for some common CLC Server setups are summarized in the diagrams below.

These diagrams do not include representation of communication with external resources, such as accessing reference data from remote locations, downloading licenses for CLC software, or interacting with a CLC Genomics Cloud setup.

Representative CLC Server grid setup with LDAP authentication

Image communication-clc-server-gridnodes-ldap
Figure 23.1: A representative CLC Server setup, where job execution is carried out on grid nodes, and authentication has been configured to use LDAP. The dotted line between grid node and the master CLC Server represents the communication that triggers an index update when a job has created files in a CLC File System Location.

Representative CLC Server grid setup using built-in authentication

Image communication-clc-server-gridnodes-builtin-auth
Figure 23.2: A representative CLC Server setup, where job execution is carried out on grid nodes, and the built-in authentication mechanism is being used. The dotted line between grid node and the master CLC Server represents the communication that triggers an index update when a job has created files in a CLC File System Location.

Representative CLC Server job node setup with LDAP authentication

Image communication-clc-server-jobnodes-and-ldap
Figure 23.3: A representative CLC Server setup, where job execution is carried out on job nodes, and and authentication has been configured to use LDAP.

Representative CLC Server job node setup using built-in authentication

Image communication-clc-server-jobnodes-builtinauth
Figure 23.1: A representative CLC Server setup, where job execution is carried out on job nodes, and the built-in authentication mechanism is being used.