Installing rWeb
Installation procedures for hardware and virtual rWebs. This is the main management platform that should be set up prior to installing any RIOS filter devices.
Overview
The rWeb management platform can be installed as either hardware or as a VM. There are currently two supported hypervisor platforms (KVM and VMWare):
In order to function, the system requires specific ports to be open between rWeb and RIOS filter devices, as well as for all systems to be able to use NTP. rWeb's specific port requirements are listed here.
VM Resource Allocation
VM rWeb requires a baseline minimum of resources to be allocated before it will work. You should pick an appropriate baseline from this table depending on your intended use. rWeb can be resized to use additional resources if your needs change.
| Installation Type | CPU Cores | Memory | Storage | Notes |
|---|---|---|---|---|
| Minimum | 1 CPU | 8 GB | 15 GB | This is the minimum set of resources required to start the VM. For small or trial deployments with 1-2 RIOS devices, 1 week of data retained |
| Recommended | 4 CPU | 16 GB | 15 GB SSD-Tier | This will provide the best performance boosts to the VM short of matching our hardware rWeb specifications. For small to medium deployments, and clustered systems. Increase memory and storage if retaining more than 1 week of historical data. |
| Hardware Equivalent | 4 CPU | 32 GB | 1 TB SSD-Tier | This resource allocation is on par with our current hardware rWeb specifications. For medium to large deployments, or clustering with physical rWeb. 6+ months of data retained. |
If using AS/CC, you should meet the "Recommended" level of requirements.
VM Performance Considerations
Disk throughput is the highest performance impacting factor for rWeb. Ensuring the VM backing store is SSD equivalent is the best way to improve overall performance.
For deployments that require more historical data retention, resizing the storage upwards of 15GB is recommended.