Skip to content

Quick Start

Please refer to this section to complete system configuration on the virtual machine or physical server to be deployed, and install Docker as the container runtime.

  1. Configure static IP address:

    Terminal window
    sudo vi /etc/sysconfig/network-scripts/ifcfg-<interface>

    Replace <interface> with your network interface name, such as eth0.

  2. Configure DNS server:

    Terminal window
    sudo vi /etc/resolv.conf
  3. Disable firewall:

    Terminal window
    sudo systemctl stop firewalld && sudo systemctl disable firewalld
  4. Disable SELinux:

    Terminal window
    echo -e "SELINUX=disabled\nSELINUXTYPE=targeted" | sudo tee /etc/selinux/config
    sudo setenforce 0
  1. Install Docker CE:

    Terminal window
    sudo dnf -y install dnf-plugins-core
    sudo dnf config-manager --add-repo https://download.docker.com/linux/rhel/docker-ce.repo
    sudo dnf -y install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
  2. Start Docker service:

    Terminal window
    sudo systemctl enable --now docker
  3. Verify Docker installation:

    Terminal window
    docker --version
  4. Reboot the operating system to apply the configuration:

    Terminal window
    sudo reboot

Install the Neutree CLI on the virtual machine or physical server to be deployed and grant it executable permissions. This CLI tool is used to deploy the monitoring components and control plane of Neutree.

  1. Download the Neutree CLI from GitHub Releases according to your server’s CPU architecture:

    Terminal window
    # For amd64
    curl -LO https://github.com/neutree-ai/neutree/releases/download/v1.0.0/neutree-cli-amd64
    # For aarch64
    curl -LO https://github.com/neutree-ai/neutree/releases/download/v1.0.0/neutree-cli-aarch64
  2. Rename and grant executable permissions to the CLI:

    Terminal window
    mv neutree-cli-<arch> neutree-cli
    chmod +x neutree-cli

    Replace <arch> with your server’s CPU architecture: amd64 or aarch64.

Use the Neutree CLI to deploy the OBSStack monitoring component to provide system monitoring and observability support for the platform.

  1. Start the monitoring service:

    Terminal window
    ./neutree-cli launch obs-stack
  2. If the monitoring service fails to start, check the monitoring service logs to troubleshoot:

    Terminal window
    docker compose -f ./neutree-deploy/obs-stack/docker-compose.yml logs

Use the Neutree CLI to deploy the control plane with simplified configuration, providing the management interface.

  1. Run the following command to generate a random JWT secret:

    Terminal window
    openssl rand -base64 32 | tr '+/' '-_' | tr -d '='
  2. Start the control plane service:

    Terminal window
    ./neutree-cli launch neutree-core \
    --version=v1.0.0 \
    --metrics-remote-write-url=http://<obstack_ip>:8480/insert/0/prometheus/ \
    --jwt-secret=<jwt_secret> \
    --grafana-url=http://<obstack_ip>:3030 \
    --admin-password=<admin_password>
    ParameterDescription
    <obstack_ip>IP address of the server where the monitoring component is deployed.
    <jwt_secret>JWT secret string generated in the preparation step.
    <admin_password>Initial password for the Neutree administrator. Optional but recommended to set a custom initial password. If left empty, the system will auto-generate one, which can be retrieved after deployment using kubectl -n neutree logs -l app.kubernetes.io/component=neutree-post-migration-hook-job.
  3. If the control plane service fails to start, check the control plane service logs to troubleshoot:

    Terminal window
    docker compose -f ./neutree-deploy/neutree-core/docker-compose.yml logs

After all services have started, verify the deployment.

  1. Check all service statuses:

    Terminal window
    docker ps
  2. Access the Neutree management interface at http://<control_plane_ip>:3000 using the administrator account admin@neutree.local and the initial password.

    If you cannot access the Neutree management interface, please verify that the Docker service is running properly.