This article describes the installation of the Kloudspot software stack on an Ubuntu 22.04 virtual machine or bare-metal server.
Some or all of the following components can be installed:
KloudHybrid
KloudInsights
KloudManage
The components are selected for installation using true/false flags in the YAML values file used to control the Helm chart installation.
System Requirements
The following are the recommended specifications to run different configurations:
Any system used needs to support the AVX flag - most newer bare metal systems will support this. VM servers often don't by default. Please refer to your VM server documentation.
Minimum Specification
The recommended specification to run one of the following configurations:
- KloudHybrid (<3000 users)
- KloudManage
Is:
- 4 core
- 16 GB RAM
- 150 GB SSD/Disk, configured using LVM with 50 GB assigned to /
Medium Specification
The recommended specification to run one of the following configurations:
- KloudHybrid >3000 users
- KloudInsights
Is
- 8 core
- 32 GB RAM
- 300 GB SSD/Disk configured using LVM with 50 GB assigned to /
Full System Specification
In order to run the full software stack we recommend:
- 8 core
- 64 GB RAM
- 1x500GB, 1x500GB SSD configured using LVM with 100 GB assigned to /
- Ubuntu 22.04 Server image
System requirement
Any system used needs to support the AVX flag - newer bare metal systems will support this. VM servers often don't by default. Please refer to your VM server documentation.
Each node should have a minimum of the following specification:
- 8 core
- 32 GB RAM
- 1x100GB, 1x500GB SSD configured using LVM with 50 GB assigned to /
- Ubuntu 22.04 Server image
The recommended spec when running both KloudInsights and KloudManage is:
- 16 core
- 64 GB RAM
- 1x100GB, 1x500GB SSD configured using LVM with 50 GB assigned to /
- Ubuntu 22.04 Server image
Three nodes are required for a system to be able survive node failure, however if there is a heavy load on the system, one or more worker nodes may need to be added to the cluster to provide extra capacity.
Ports & Firewall Configuration
It is assumed that there are no port restrictions on communications between nodes.
Outbound
The follow outbound ports/paths need to be allowed in most configurations
|
Purpose |
Destination Address |
Destination Port |
Protocol |
Service |
|
Software & license install *1 |
*.kloudspot.com |
443 |
TCP |
HTTPS |
|
Installation sources |
443 |
TCP |
HTTPS |
|
|
Network Time |
*.ntp.org |
123 |
UDP |
NNTP |
|
Cisco WLC access (if required) |
|
16113 |
TCP |
|
*1 : Can be limited to install only if necessary
Inbound
Single Node
The following inbound ports need to be allowed if the function is required
|
Port |
Usage |
Optional |
|
30003/UDP |
Aruba RTLS |
yes |
|
30004/UDP |
Aeroscout |
yes |
|
30002/TCP |
Meraki MV Sense MQTT |
yes |
|
30005/TCP |
Huawei |
yes |
|
30006/TCP |
Huawei BLE |
Yes |
|
8083, 8084/TCP |
Access camera feeds |
Yes |
|
48082/48083/TCP |
Sensor/AP data |
yes |
Cluster
|
Port |
Usage |
Optional |
|
3333/UDP |
Aruba RTLS |
yes |
|
5555/UDP |
Aeroscout |
yes |
|
6666/TCP |
Meraki MV Sense MQTT |
yes |
|
7777/TCP |
Huawei |
yes |
|
7778/TCP |
Huawei BLE |
yes |
|
8083, 8084/TCP |
Access camera feeds |
Yes |
|
48082/48083/TCP |
Sensor/AP data |
yes |