Installing Yadle: SaaS: Yadle agent
The Yadle agent is responsible for the indexing of your files. The agent runs inside a Docker container enabling ease of deployment.Pre-requisites:
1. Linux Host Machine or VM
- RHEL/CentOS or Debian/Ubuntu Linux Distributions
- System Minimum Requirements:
- 4 Cores, 16 GB RAM, 100 GB Disk Space
- Able to access the internet over port 443 (https)
- Curl and Gunzip
3. Install Docker Compose
Download Yadle agent installation script from:
$ curl -O https://download.yadle.com/docker/install_yadle_agent_saas
After you download the script, set the execute bit:
$ chmod +x install_yadle_agent_saasNote:
- This is a bash script that will execute the steps needed to download, deploy, and configure a Docker version of the Yadle agent on your host. Where you save the downloaded script is unimportant – it will download the container, add it to Docker, and then configure itself.
- The installation script can be run multiple times without issue. Each time it is run, it examines and determines the state of the container, repairing or configuring any elements that are not correct.
Configure Yadle Data Directory.
The Yadle agent installer will prompt you for a “Data root path”. This is the location of the volumes that you want to index with Yadle.
Yadle will only index files that are at or below this path. It is recommended to create a directory /yadle, and put mount points under this directory for the volumes you want Yadle to index. This will allow you to easily add or remove subfolders to the /yadle directory as you want to add or remove volumes to be indexed.
$ sudo mkdir /yadleNote:
- It is NOT necessary for the mount points on the Yadle agent to be the same as the user’s mount points. Yadle provides a mechanism that allows you to map the mount points on a Yadle agent system to user map points via File Mapping.
Run the Yadle agent installation script. Since docker is being used, the script must be run as a sudoer or root user.
$ sudo ./install_yadle_agent_saas
The Yadle agent script will execute and you will be prompted for the following values:
Enter Organization ID:
– The Organization ID is provided to you by Yadle.
Enter Application ID:
– The Application ID is provided to you by Yadle.
Enter host for Yadle API Server:
– The Yadle API Server hostname is provided to you by Yadle..
Enter Yadle admin account user:
– default username: yadle
Enter Yadle admin account password:
– default password:password
Install Directory For Yadle agent:
– Recommended:/opt/<org> Replace <org> with the name of your organization e.g., google
Data Root Path:
– Recommended: /yadle
- The script will output many messages. Progress messages will be displayed as the container is downloaded, started and configured.
- Any problems will be displayed in red text and the script will stop.
- Successful installation will output docker status and “Installation completed”
Starting and Stopping Yadle Agent:
The installer for the Yadle agent will generate scripts to stop and start the Docker container with the proper parameters. The
stop_yadle.sh and located in the default install directory.
$ sudo /opt/<org>/agent/start_yadle.sh
$ sudo /opt/<org>/agent/stop_yadle.shNote:
- If you reboot the system that is running the Yadle agent, the containers will NOT be restarted by
default. Start them with
stop_yadle.shneed to run as sudoer.
The installer for the Yadle agent will also generate a script to run for updating the agent. It is named
<org>_update_yadle_agent.sh and located in default install location
$ sudo /opt/<org>/agent/<org>_update_yadle_agent.shNote:
<org>_update_yadle_agent.shneeds to run as sudoer.
Mounting File Systems to /yadle Data Root:
After successful installation of the Yadle agent, the next step is to mount the desired file systems to be indexed by Yadle under the /yadle Data Root Path.
Let’s imagine you have three network volumes that you want to index with Yadle:
The above three network volumes are mounted on the Yadle data root path /yadle with the following mount points:
/nas/images —> /yadle/images/
/server/data/videos —> /yadle/videos/
/ssd_array/admin/local —> /yadle/local/
- Yadle agent only requires read access to mounted volumes. Best practice to mount with -r option for read-only.
- It is recommended to add these mounts to /etc/fstab file so that they are mounted each time the Yadle agent host system starts.
- All three of these local mounts are now available to Yadle agent for indexing