Software Checklist

Use the following checklist when planning the software configuration for a production, distributed Buckit deployment.

Buckit Pre-requisites

	Servers running a Linux operating system with a 6.6+ kernel. Red Hat Enterprise Linux (RHEL) 10 or Ubuntu LTS 22.04.01+ ship with these Kernel’s by default. Ensure the chosen OS uses LTS and in-support releases of a 6.6+ Linux kernel.
	A method to synchronize time servers across nodes, such as with `ntp`, `timedatectl` or `timesyncd`. The method to use varies by operating system. Check with your operating system’s documentation for how to synchronize time with a time server.
	Disable system services that index, scan, or audit the filesystem, system-level calls, or kernel-level calls. These services can reduce performance due to resource contention or interception of Buckit operations. Buckit strongly recommends uninstalling or disabling the following services on hosts running Buckit: `mlocate` or `plocate` `updatedb` `auditd` Crowdstrike Falcon Antivirus software (`clamav`) The above list represents the most common services or softwares known to cause performance or behavioral issues with high performance systems like Buckit. Consider removing or disabling any other service or software which functions similarly to those listed above on Buckit hosts. Alternatively, configure these services to ignore or exclude the Buckit Server process and all drives or drive paths accessed by Buckit.
	System administrator access to the remote servers
	(optional) Load balancer to handle routing of requests (for example, NGINX)
	(optional) Prometheus or a Prometheus-compatible setup for monitoring and metrics
	(optional) Grafana configured for dashboards

Exclusive access to drives

Buckit requires exclusive access to the drives or volumes provided for object storage. No other processes, software, scripts, or persons should perform any actions directly on the drives or volumes provided to Buckit or the objects or files Buckit places on them.

Do not use scripts or tools to directly modify, delete, or move any of the data shards, parity shards, or metadata files on the provided drives, including from one drive or node to another. Such operations are very likely to result in widespread corruption and data loss beyond Buckit’s ability to heal.