FineOps Server Preparation

  • Last update: 2024-04-18
  • Overview 

    The resource requirements that a server must meet for deploying FineOps are detailed in this article.

    Server Quantity 

    FineOps Edition
    Recommendation
    FineOps Standard Edition

    It is recommended that FineOps monopolizes one server.

    That is, only deploy FineOps on the server, and do not deploy other applications or FanRuan projects to ensure the independence of operation and maintenance.

    FineOps Basic Edition

    FineOps can share a server with a single-node FanRuan project.

    That is, deploy FineOps and a FanRuan application (a standalone project) on the server, and do not deploy other content.

    Nonexistence of Docker 

    When using the FineKey tool to deploy FineOps, the Docker container is automatically installed.

    Ensure that the server where FineOps is located has no pre-installed Docker. Otherwise, the FineOps deployment may fail due to version and permission issues.

    Execute the following command. 

    docker version
    • If it returns nothing, no Docker is installed.

    • If it returns the version number, a Docker has been installed. Replace the server.

    Operating System Requirement 

    ItemRecommendationSupported Configuration/Lowest Requirement
    TypeLinuxLinux
    ArchitectureX86_64X86_64
    KernelKernel 3.10 and later releasesKernel 3.10 and later releases
    Linux distributionUbuntu 22

    Ubuntu 18.04.4 and later releases

    CentOS 7.3 to 7.9

    Red Hat 7.6 and later releases

    Resource Allocation Requirement 

    The server on which FineOps is deployed shall meet the following requirements.

    Item

    Requirement

    CPUAt least four cores
    Disk typeXFS
    Remaining free disk space of the root directory

    1 GB

    Remaining free disk space of the installation directory

    Take the larger value between the following listed ones as the configuration requirement.

    1) There is a partition in the server with more than 200 GB of free space left and a minimum free space of 100 GB.

    Note: If you are preparing a new disk, the one with a minimum free space of 120 GB is recommended. As the system takes up some space, the free space may be less than 100 GB.

    2) If there are many non-containerized O&M projects to be loaded into FineOps, prepare the disk according to the number of non-containerized projects (FR/BI/FDL). Ensure that there is a partition in the server with remaining available space of no less than 50 GB multiplied by the project quantity.

    Note: You can use the df-h command to query the disk space. There must be a partition that meets the condition. 

    Remaining free physical memory

    For an exclusive server of FineOps Standard Edition, the memory larger than 16 GB is recommended and should be at least 12 GB. 

    For an inclusive server of FineOps Standard Edition, the memory should be larger than 16 GB.

    For the server of FineOps Basic Version, the memory should be larger than 4 GB.

    The configuration requirements in the above table must be met because each component of FineOps has minimum operational requirements, as shown in the following table.

    ComponentMaximum CPU UsageMaximum Memory UsageMemory Allocation Xmx
    ops2 cores//
    nginx1 core//
    ops-agent1 core/1 GB
    pushgateway0.1 core0.1 GB/
    prometheus1 core1 GB/
    grafana1 core1 GB/
    alertmanager1 core1 GB/
    elasticsearch1 core/2 GB
    skywalking_oap1 core/2 GB
    registry1 core//

    Attachment List


    Theme: FineOps Deployment
    Previous
    Next
    • Helpful
    • Not helpful
    • Only read