User Guide

Tool Usage

RPM Mode

You can interact with WAAS Booster using the commands supported by WAAS Booster.

The following commands can be used to interact with WAAS Booster:

Start WAAS Booster.
```
systemctl start waasbooster
```
Stop WAAS Booster.
```
systemctl stop waasbooster
```
Check the adjustment actions of WAAS Booster on a container.
```
tail -f /var/log/waasbooster.log
```

NOTE: After this tool is started, the dynamic load-based scheduling function can be automatically implemented in container scenarios. No additional operations are required. If you want to view the adjustment process, you can view the logs.

You can interact with WAAS Booster using the commands supported by WAAS Booster.

Kubernetes Pod Mode

You can create and delete WAAS Booster pods using kubectl. After a pod is created, the WAAS Booster service is automatically started. After the pod is deleted, the WAAS Booster service is automatically stopped.

Assume that the WAAS Booster pod configuration file is waasbooster.yaml. The following uses this file as an example to describe common operations on Kubernetes pods.

NOTE: All the following operations are performed on the primary node.

Create a WAAS Booster pod.
```
kubectl apply -f waasbooster.yaml
```
Delete the WAAS Booster pod.
```
kubectl delete -f waasbooster.yaml
```
Check the adjustment actions of WAAS Booster on a container.

Assume that the target pod is waasbooster-daemon-rhwdz.
1. If continuous monitoring is required, you can enter the container to view logs.
  1. Access the container.
```
kubectl exec -it waasbooster-daemon-rhwdz bash
```
  2. View logs.
```
tail -f /var/log/waasbooster.log
```
2. If you want to view the adjustment actions temporarily, you can view the Kubernetes logs.
```
kubectl logs waasbooster-daemon-rhwdz
```

Security Management

Directory and File Permissions

Table 1 describes the WAAS Booster directory and file permissions for RPM-based deployment.

Table 1 Directory and file permissions of WAAS Booster

Directory or File Name	Location	User Permission	File Permission	Description
/usr/local/waasbooster	/usr/local/waasbooster	waas:waas	644	WAAS Booster installation directory
/var/log/waasbooster.log	/var/log/waasbooster.log	root:root	644	Logs generated by WAAS Booster
/var/waasbooster/	/var/waasbooster	root:root	750	WAAS Booster data storage path
/var/run/waasbooster_manager/	/var/run/waasbooster_manager/	root:root	644	Path for storing temporary files of WAAS Booster

Table 2 describes the WAAS Booster directory and file permissions for deployment using Kubernetes pods.

Table 2 Directory and file permissions of WAAS Booster deployed using Kubernetes pods

Directory or File Name	Location	User Permission	File Permission	Description
/app/	/app/	root:root	644	WAAS Booster installation directory
/var/log/waasbooster.log	/var/log/waasbooster.log	root:root	644	Logs generated by WAAS Booster
/var/run/waasbooster_manager/	/var/run/waasbooster_manager/	root:root	644	Path for storing temporary files of WAAS Booster

Log Management

NOTICE: Do not delete log files generated by WAAS Booster by mistake.

Run logs are exported to the log files of the OS.
The WAAS Booster log file is /var/log/waasbooster.log.