VidyoPortal VM provisioning requirements
VidyoPortal version 3.3 or later is available as a single Virtual Edition that dynamically enforces capacity limits based on the number of vCPU allocated. The default OVA has the resource reservations pre-configured for profile 1 below, but can be adjusted based on your individual needs.
The following configurations are the only supported configurations.
|
Note OVA is pre-configured for the below Usage Profile 1 for version 19.2.0.x. |
|
Usage Profile |
VidyoPortal capacity |
VM configuration |
Resource reservation |
Physical host |
|||
|---|---|---|---|---|---|---|---|
|
vCPU (Cores) |
RAM (GB) |
Storage (GB) |
CPU (GHz) |
RAM (GB) |
Min. CPU speed (GHz) |
||
|
Usage Profile 1 |
10,000 Users; 1,000 Tenants |
4 |
12 |
100 |
8 |
8 |
3.0 |
|
Usage Profile 2 |
10,000 Users; 1,000 Tenants |
8 |
12 |
100 |
8 |
12 |
2.0 |
|
Usage Profile 3 |
1,000 Users; 100 Tenants |
2 |
8 |
100 |
2 |
8 |
2.0 |
|
Usage Profile 4* |
Single Tenant; API Centric |
4 |
12 |
100 |
8 |
12 |
2.0 |
*For higher API-centric implementations, you may need to increase reservations for performance reasons. For specific guidance on your use case, contact Vidyo Support for more information.
VidyoPortal VE may be run together with VidyoRouter VE and/or VidyoGateway VE on the same physical host server for a low-cost solution.
|
Note VidyoPortal VE can be configured to use the Hot Standby software option. |