- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
This document outlines the hardware and software requirements for deploying the Knovvu Voice Biometrics (VB) solution. Please ensure all the specifications are met to avoid performance issues.
Acronyms and Abbreviations
DB: Database
NFS: Network File System
VB: Voice Biometrics
VM: Virtual Machine
Important Notes
- The requirements outlined are optimized for deployment on Openshift and Kubernetes platforms.
- Hardware specifications, such as CPU and memory, are based on default system configurations. These may vary depending on the topology, enabled features, and concurrent service loads.
- It is critical to provision the exact hardware specified, as resource scaling after deployment may not be possible, potentially leading to performance issues.
- Resources dedicated to Knovvu Biometrics must be allocated exclusively for its services.
- If deployed on VMs, ensure the host physical servers provide at least the same number of logical cores as the VM cores.
- The license server must run on Windows Server 2016 or newer.
- A minimum network connection speed of 100Mb/s is required for optimal performance.
Database and Storage Notes
- The main database should be named VoiceBiometrics, and the logging database should be named VoiceBiometricsLogs.
- PostgreSQL versions 12, 13, and 14 are supported. If using MSSQL, it must be MS Server 2016 or later.
- For English language deployments, use the collation SQL_Latin1_General_CP1_CI_AS. For Turkish or Arabic implementations, use Turkish_CI_AS.
- Database maintenance, including backups and replication, should be managed by the customer's database team.
- Access permissions should allow full access to the databases for the Knovvu Biometrics service.
- Supported storage options include MinIO, Amazon S3, and NFS-mountable physical storage systems compatible with Kubernetes clusters.
Additional Considerations
- Ensure Knovvu Biometrics services are hosted on dedicated VMs to avoid conflicts or performance degradation.
- Replication and redundancy strategies should be discussed based on the specific deployment environment.
- For any deployment requiring custom configurations, please consult with SESTEK before implementation to ensure compatibility.
Terms Glossary
Term | Definition |
---|---|
Node | A physical or virtual machine that runs the services required for the Knovvu Biometrics solution. |
Pod | A small, scalable unit of deployment in Kubernetes that contains one or more containers. |
VM | A virtual machine that can host Knovvu Biometrics services when the system is not running directly on physical hardware. |
Cluster | A set of nodes or VMs configured to work together to provide scalability and redundancy. |
vCPU | Virtual CPU assigned to the VM or container running Knovvu Biometrics services. |
vCPU Request | The minimum CPU capacity allocated to the service within a container to ensure a smooth operation. |
vCPU Limit | The maximum CPU capacity that a container can use. It ensures that the service does not overconsume resources, impacting other services on the node. |
Was this article helpful?