General information#
It is recommended to read and understand this document. It will help you to find out what components LUNA PLATFORM consists of and what tasks they solve.
Deploy should be performed in the order specified in the document.
All the services can be divided into general and optional. You can't launch and use LP without general services, whereas optional services provide extra features and are not mandatory. Most of the services have their database or file storage.
General services
| Service | Description | Database |
|---|---|---|
| API | The main gateway to LP. Receives requests, distributes tasks to other LP services | |
| Handlers | Detects faces in images, extracts face properties and creates samples. Extracts descriptors from samples. Extracts basic attributes of the images. Creates and stores handlers | PostgreSQL/ Oracle |
| Python Matcher | Performs matching tasks | |
| Faces | Creates faces, lists, and attributes. Stores these objects in the database. Allows other services to receive the required data from the database | PostgreSQL/ Oracle, Redis |
| Image Store | Stores samples, reports about long tasks execution, created clusters and additional metadata | Local storage/ Amazon S3 |
| Events | Stores data on the generated events in the database. This service can be disabled, but it is recommended to use it, if you are going to save events | PostgreSQL |
| Licenses | Checks your license conditions and returns information about them | |
| Admin | Enables to perform general administrative routines | PostgreSQL/ Oracle |
| Configurator | Stores all configurations of all the services in a single place | PostgreSQL/ Oracle |
| Tasks | Performs long tasks, such as garbage collection, extraction of descriptors with a new neural network version, clustering | PostgreSQL/ Oracle |
| Tasks Worker | Performs the internal work of the Tasks service | PostgreSQL/ Oracle |
Optional services
| Service | Description | Database |
|---|---|---|
| Sender | Sends notifications about created events via web-socket. | Redis |
| Liveness | The service is used for Liveness V1 utilization. It enables LP to detect presentation attacks. This service requires an additional license. | |
| Backport 3 | The service is used to process LUNA PLATFORM 3 requests using LUNA PLATFORM 5. | PostgreSQL/ Oracle |
| Backport 4 | The service is used to process LUNA PLATFORM 4 requests using LUNA PLATFORM 5. | |
| User Interface 3 | User Interface is used to visually represent the features provided with the Backport 3 service. It does not include all the functionality available in LP 3. | |
| User Interface 4 | User Interface is used to visually represent the features provided with the Backport 4 service. It does not include all the functionality available in LP 4. |
Services for index building and search by index
| Service | Description | Database |
|---|---|---|
| Index Manager | Forms tasks for index building and coordinates the process of index delivery to Indexed Matcher servers. | PostgreSQL |
| Indexer | Creates indexes based on a descriptors' list. | |
| Indexed Matcher | Searches by indexes. | |
| Matcher Daemon | Copies the index from the server, on which Indexer is installed, to the server for search by an index (Indexed Matcher). Restarts Indexed Matcher with a new index generation. Matcher Daemon is installed on the Indexed Matcher server. | |
| Message queue | A message queue is used for interaction with index services. by default, RabbitMQ is used. | |
| Python Matcher Proxy | The service manages matching requests and routes them to Python Matcher or Indexed Matcher. |
All the procedures in the following manual are described for CentOS. If it is required to deploy dockers on any other OS, please refer to the Docker Compose documentation for information: