Minimum Requirements for ZETALY BI in Linux Environments
    • 10 Jul 2023
    • 5 Minutes to read
    • Contributors
    • Dark
      Light

    Minimum Requirements for ZETALY BI in Linux Environments

    • Dark
      Light

    Article summary

    Below are descriptions and explanations describing the minimum requirements for ZETALY BI in Linux environments.


    Supported Browsers


    The ZETALY BI Web Application runs in the following HTML5 supported browsers:

    • Microsoft Edge

    • Google Chrome
    • Firefox
    • Safari version 7 and higher
      ZETALY BI  supports Safari 10 and higher when embedding iFrames.
    Note:

    Internet Explorer 11
    If you are using Internet Explorer 11, ZETALY recommends moving to another browser. Microsoft ended IE11 support for various Microsoft products during 2021 and ZETALY stopped supporting IE11 by the end of 2021.
    IE11 is not supported for the ZETALY BI internal web-based file browser application.

    The ZETALY BI Web Application also works in mobile phone and tablet browsers that support HTML5.


    Minimum System Requirements


    The ZETALY BI Linux deployment is certified to run on the following operating systems.

    Note the following:

    • ZETALY BI 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).

      

    OSOS versionZETALY BI
    Minimal Version
    Ubuntu18.04 LTSL8.0.2
    20.04 LTSL2021.5
    CentOS7.0, 7.4, 7.6, 7.7L8.0.2
    8.0, 8.1, 8.2, 8.3L2021.7
    8 StreamL2021.9
    Red Hat Enterprise Linux7.0L8.0.2
    8.0L2021.7
    Red Hat OpenShift

    4.8

    L2021.3
    Note:

    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. ZETALY BI will align with the CentOS 8 EOL date.
    For continued support, ZETALY BI customers must migrate to a supported OS version, such as CentOS 8 Stream (supported by ZETALY BI 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



    The table below describes the minimum requirements for your production deployment. The exact deployment parameters depend on your specific use-case and usage needs.

    Notes:

    It is possible for a deployment with machines that have more memory and cores to exceed the large-scale recommendations.

       

    Deployment SizeSmall ScaleMedium ScaleLarge 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
    ZETALY BI requires SSDs
    (Optional) The root volume disk size may need to be increased when using larger local backup temporary files during backups.

    350GB
    Root volume

    Disk 2

    ZETALY BI requires SSDs
    Required space for ElastiCube files + Plugins + Builds + Backup archives
    ZETALY recommends a second disk size of at least: The size of all ElastiCubes x 2

    400GB second volume400GB second volume
    (shared storage for cluster)
    400GB second volume
    (shared storage for cluster)
    Disk IOPS

    The disk must have at least:

    • 100MB/s
    • 1600 IOPS

    The build nodes disk must have at least:

    • 100MB/s
    • 1600 IOPS


    System Memory

    32GB

    64GB - 128GB

    256GB - 512GB

    Total number of rows being built in parallel

    50M

    300M

    1B

    Note:

    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
      If more specific sub disks are defined (for example: “/var/lib/docker” and/or “/var/lib/kublet”), make sure you allocate enough space for each of them, otherwise certain components of the platform will not work.
    • Your Linux deployment must use AVX2 (also known as Haswell New Instructions).
    • The kernel version is held due to the limitation with GlusterFS Fuse.
    • 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. ZETALY BI supplies specific 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.
      ZETALY BI 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.
    • 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 ZETALY BI 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.

    Kubernetes compatibility

    • Kubernetes types supported (for pre-built Kubernetes clusters):
      • AWS Elastic Kubernetes Service
      • Google Cloud Engine
      • Azure Kubernetes Service
      • RedHat OpenShift
    • ZETALY BI on Linux supports Kubernetes versions 1.17 through 1.24
    Notes
    • Kubernetes 1.22 is only supported for RKE or Provisioner installations. 
    • Versions 1.23 and higher need 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.

       

    Namespaces

    TCP/UDP

    Ports

    Source

    HTTP

    TCP

    80

    Same security group

    Custom TCP Rule
    Grafana

    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 UDP Rule

    UDP

    Gluster

    24007 - 24008

    Same security group

    Custom TCP Rule

    TCP

    Gluster FS

    49152 - 49157

    Same security group

    Custom TCP Rule

    TCP

    Calico

    9099

    Same security group

    HTTPS

    TCP

    Https

    443

    Same security group

    Custom TCP Rule

    TCP

    Calico – bird?

    179

    Same security group

    Custom TCP Rule

    TCP

    Gluster

    24007 - 24008

    Same security group

    Custom TCP Rule
    ZETALY BI Web UI

    TCP

    30845

    Customer IP Address

    SSH

    TCP

    22

    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

    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 ZETALY BI, ensure that the default packages repository for your Linux distribution is configured and enabled. ZETALY BI 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 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 ZETALY BI is deployed, for ZETALY BI component interconnections to function properly.

    Whitelisted Resources

    The following whitelisted resources must be added:




    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.