Minimum Requirements for Sisense in Linux Environments
Below are descriptions and explanations describing the minimum requirements for Sisense in Linux environments.
Supported Browsers
The Sisense Web Application runs in the following HTML5 supported browsers:
- Microsoft Edge
- Google Chrome
- Firefox
- Safari version 7 and higher
Sisense supports Safari 10 and higher when embedding iFrames.
Note:
Internet Explorer 11
If you are using Internet Explorer 11, Sisense recommends moving to another browser. Microsoft ended IE11
support for various Microsoft products during 2021 and Sisense stopped supporting IE11 by the end of 2021.
IE11 is not supported for the Sisense internal web-based file browser application.
The Sisense Web Application also works in mobile phone and tablet browsers that support HTML5. See Viewing Dashboards on Mobile Devices to learn more about mobile compatibility.
Minimum System Requirements
The Sisense Linux deployment is certified to run on the following operating systems.
Note the following:
- Sisense supports only x86-64/AMD64 architecture (e.g., ARM64 currently not supported). You can verify this by running the "hostnamectl" command in Linux to confirm the current architecture in place (e.g., Architecture: x86-64).
- The OS versions specified below are also based on the minor release number, and should be taken into consideration to ensure proper compatibility (e.g., CentOS 8.4 is not currently supported as it is not specified below).
- The OS needs to be an official release of the given Linux OS, and one that has not been customized (e.g., where the OS was modified to harden the kernel).
OS | OS version | Sisense
Minimal Version |
---|---|---|
Ubuntu | 18.04 LTS | L8.0.2 |
20.04 LTS | L2021.5 | |
22.04 LTS | L2022.11 | |
CentOS | ||
8 Stream | L2021.9 | |
Amazon Linux | 2.0 | L8.0.2 |
Red Hat Enterprise Linux | 7.0 | L8.0.2 |
8.0, 8.4, 8.6 | L2021.7 | |
8.5, 8.7 | L2023.3 | |
Red Hat OpenShift |
4.8 |
L2021.3 |
The CentOS Project set December 31, 2021, as the CentOS 8 end-of-life date, and no operating system updates will
be issued after that date. Sisense will align with the CentOS 8 EOL date.
For continued support, Sisense customers must migrate to a supported OS version, such as CentOS 8 Stream
(supported by Sisense Linux v2021.9), CentOS 7, or another supported OS version that is listed in the table.
Minimum Hardware Requirements
Ensure that your system has at least the following hardware requirements:
- 8 CPUs
- The memory requirements specified in the recommended deployment sizes table
Recommended Deployment Sizes
The table below describes the minimum requirements for your production deployment. The exact deployment parameters depend on your specific use-case and usage needs.
It is possible for a deployment with machines that have more memory and cores to exceed the large-scale recommendations.
Deployment Size | Small Scale | Medium Scale | Large Scale |
---|---|---|---|
Deployment type |
Single node, cluster optional |
Recommended: Cluster Note:: The parameters are for each node. |
Recommended: Cluster Note:: The parameters are for each node. |
Disk 1
|
350GB
Root volume |
||
Disk 2 Sisense requires SSDs
|
400GB second volume | 400GB second volume
(shared storage for cluster) |
400GB second volume
(shared storage for cluster) |
Disk IOPS |
The disk must have at least:
|
The build nodes disk must have at least:
|
|
System Memory |
32GB |
64GB - 128GB |
256GB - 512GB |
Total number of rows being built in parallel |
50M |
300M |
1B |
If the OS defines sub disks for different directories, the following directories must have at least this amount of storage:
- 300GB for /var/lib
- 50GB for /var/log/sisense
- Your Linux deployment must use AVX2 (also known as Haswell New Instructions).
- For cluster deployments that use a shared storage, the following requirements are for the cluster's first three nodes. Each of the first three nodes must have a second unformatted, unmounted, and unpartitioned hard disk with at least 400GB disk space available, plus additional storage for the ElastiCubes.
- For Azure systems that have a 30GB default capacity, you must stop the instance and expand the OS disk capacity up to 300GB before proceeding with installation. Sisense supplies the following scripts to assist you with expanding the disk capacity:
- NVMe disks are recommended for the second disk.
If NVMe disks are not used in your system, SSDs are mandatory.
Sisense does not support systems running with HDD. - AWS disk IOPS is determined by a formula.
EBS gets 250MB/s at 3000 IOPS at the peak, but tokens are provided depending on the disk size. - Servers must be connected to the internet and must have network access to a Docker Hub.
If you are performing an offline installation, see Installing Sisense in an Offline Environment. - The network between the servers must reach at least 1 Gbps.
- The installation requires the user/password or SSH key. In a multi-node deployment, the same user credentials (password/SSH key) must be defined on all of the server nodes.
- See Integrating Sisense with Portworx if your environment uses the Portworx platform for end-to-end storage and data management solution on the Kubernetes cluster.
- Set kubernetes_minimum_pods to 58 per node.
Compatibility Matrix
- Kubernetes types supported (for pre-built Kubernetes clusters):
- AWS Elastic Kubernetes Service
- Google Cloud Engine
- Azure Kubernetes Service
- RedHat OpenShift
-
Sisense on Linux supports Kubernetes versions 1.20 through 1.24, based on the following table:
Kubernetes Version 1.20 1.21 1.22 1.23 1.24 Sisense Version
L2021.8 ✓ ✓ ✕ ✕ ✕ L2021.9 ✓ ✓ ✕ ✕ ✕ L2021.10 ✓ ✓ ✕ ✕ ✕ L2021.11 ✓ ✓ ✕ ✕ ✕ L2021.12 ✓ ✓ ✕ ✕ ✕ L2022.1 ✓ ✓ ✕ ✕ ✕ L2022.2 ✓ ✓ ✕ ✕ ✕ L2022.3 ✓ ✓ ✕ ✕ ✕ L2022.4 ✓ ✓ ✓* ✕ ✕ L2022.5 ✓ ✓ ✓* ✕ ✕ L2022.6 ✓ ✓ ✓* ✕ ✕ L2022.7 ✓ ✓ ✓ ✕ ✕ L2022.8 ✓ ✓ ✓ ✓** ✓** L2022.9 ✓ ✓ ✓ ✓** ✓** L2022.10 ✓ ✓ ✓ ✓** ✓** L2022.11 ✓ ✓ ✓ ✓** ✓** L2023.1 ✓ ✓ ✓ ✓** ✓** L2023.2 ✓ ✓ ✓ ✓** ✓** L2023.3 ✓ ✓ ✓ ✓** ✓** * Kubernetes 1.22 is only supported for RKE or Provisioner installations.
** If installing or upgrading to EKS 1.23 or higher, see Creating a Service Account for the EBS CSI Driver on EKS.
Open Ports Requirements
Linux outbound ports:
- 443
- 80
The following inbound and outbound ports must be open in the server's firewall before the installation. In the table below:
-
Same security group means that, for an internal cluster, all of the Kubernetes nodes need to open those ports to any other Kubernetes nodes within the cluster.
-
Customer IP Address means that those ports should be accessible from outside the cluster, in order to use the application. The customer can set the IP scope level, that is, who is able to access the network.
Namespaces | TCP/UDP | Ports | Source |
---|---|---|---|
HTTP |
TCP |
80 |
Same security group |
HTTPS |
TCP Https |
443 |
Same security group |
Custom TCP Rule
|
TCP |
30030 |
Customer IP Address |
Custom TCP Rule |
TCP kubernetes admin |
6443 |
Customer IP Address |
Custom TCP Rule |
TCP etcd |
2379 - 2380 |
Same security group |
Custom TCP Rule |
TCP Rook-Ceph |
9443 6789-6790 3300 6800 - 7300 9283 9070 |
Same security group |
Custom TCP Rule |
TCP Calico |
9099 |
Same security group |
Custom TCP Rule |
TCP Calico - bird? |
179 |
Same security group |
Custom TCP Rule
|
TCP |
30845 |
Customer IP Address |
Custom TCP Rule |
TCP |
10249 - 10259 |
Same security group |
Custom TCP Rule |
TCP |
30000 - 39999 |
Same security group |
Custom TCP Rule |
TCP Weave - rpcbind |
111 |
Same security group |
Custom TCP Rule |
TCP Node exporter |
9100 |
Same security group |
SSH |
TCP |
22 |
Customer IP Address |
Server Connectivity Requirements
The servers must be connected to the Internet and must have network access to the following server list:
- apt.dockerproject.org
- archive.ubuntu.com
- auth.cloud.sisense.com
- bitbucket.org
- bugs.launchpad.net
- dl.fedoraproject.org
- docs.docker.com
- docs.helm.sh
- download.docker.com
- github.com
- gcr.io
- github.com
- grafana.com
- help.ubuntu.com
- index.docker.io
- kubernetes.io
- l.sisense.com
- mirror.centos.org
- ppa.launchpad.net
- pypi.python.org
- quay.io
- registry-1.docker.io
- storage.googleapis.com
- www.ubuntu.com
- yum.dockerproject.org
Default Packages Repository
Before installing Sisense, ensure that the default packages repository for your Linux distribution is configured and enabled. Sisense installer requires this as it installs the following packages:
- python 3
- python3-pip
- nc
- sshpass
- jq
- libselinux-python3
- dbus (for Ubuntu only)
For RHEL/Centos Linux, access to dl.fedoraproject.org and all its mirrors (cdn.redhat.com network - details are here: https://access.redhat.com/articles/1525183) is required to successfully install all the above packages.
Check that the packages repository is pre-installed on your server as follows:
Verification commands (for RHEL/Centos):
sudo yum install gawk
sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
sudo yum install --enablerepo="epel" python3-pip nc sshpass jq libselinux-python3
Verification commands for Amazon linux:
sudo amazon-linux-extras install epel
sudo yum reinstall python3 python3-pip || sudo yum install -y python3 python3-pip
sudo yum install nc sshpass jq libselinux-python3
Verification commands for Ubuntu:
sudo apt-get update
sudo apt-get install python3 netcat sshpass python3-apt python3-pip dbus
sudo apt-get install jq
python3 and pip
python3 and pip must be accessible from terminal via the commands:
python3
pip
Verification commands:
sudo python3 -m pip install --upgrade --force-reinstall pip
sudo python3 -m pip install configparser zipp
sudo python3 -m pip install -r kubespray/requirements.txt --ignore-installed (from the installation folder)
The DNS must be configured
The DNS must be configured in the system. This is needed to resolve:
- the Docker registry
- the DNS server must be accessible from the Kubernetes nodes where Sisense is deployed, for Sisense component interconnections to function properly.
Whitelisted Resources
The following whitelisted resources must be added:
- cdn.redhat.com (for details, see https://access.redhat.com/articles/1525183)
- pypi.org to install python modules
Minimum Requirements Video
For more information about minimum requirements, watch this video: