The Weka agent is software installed on user application servers that need access to the Weka file services. When using the Stateless Client feature, the agent is responsible for ensuring that the correct client software version is installed (depending on the cluster version) and that the client connects to the correct cluster.
A host that runs the Weka software and is installed with SSD drives dedicated to the Weka system, providing services to client hosts. A group of backend hosts forms a storage cluster.
The Weka client is software installed on user application servers that need access to Weka file services. The Weka client implements a kernel-based filesystem driver and the logic and networking stack to connect to the Weka backend hosts and be part of a cluster. In general industry terms, "client" may also refer to an NFS, SMB, or S3 client that uses those protocols to access the Weka filesystem. For NFS, SMB, and S3 the Weka client is not required to be installed in conjunction with those protocols.
A collection of Weka backend hosts, together with Weka clients installed on the application servers, forming one sharable, distributed, and scalable file storage system.
Weka uses Linux containers (LXC) as the mechanism for holding one node or keeping multiple nodes together. Containers can have different nodes within them. They can have frontend nodes and associated DPDK libraries within the container, or backend nodes, drive nodes, management node, and DPDK libraries, or can have NFS, SMB, or S3 services nodes running within them. A host can have multiple containers running on it at any time.
A Weka configuration in which Weka backend nodes run on the same host with applications.
The target period of time for tiered data to be retained on an SSD.
The number of data blocks in each logical data protection group.
A Weka configuration that dedicates complete servers and all of their allocated resources to Weka backends, as opposed to a converged deployment.
A collection of hardware components that can fail together due to a single root cause.
A collection of filesystems that share a common tiering policy to object-store.
Is the collection of Weka software that runs on a client and accesses storage services and IO from the Weka storage cluster. The frontend consists of a frontend node that delivers IO to the Weka driver, a DPDK library, and the Weka POSIX driver.
Frequently used data (as opposed to warm data), usually residing on SSDs.
A physical or virtual server that has hardware resources allocated to it and software running on it that provides compute or storage services. Weka uses backend hosts in conjunction with clients to deliver storage services. In general industry terms, in a cluster of hosts, sometimes "node" is used instead.
Amount of space available for user data on SSDs in a configured Weka system.
A software instance that Weka uses to run and manage WekaFS. Nodes are dedicated to managing different functions such as (1) NVMe Drives and IO to the drives, (2) compute nodes for filesystems and cluster-level functions and IO from clients, (3) frontend nodes for POSIX client access and sending IO to the backend nodes, and (4) management nodes for managing the overall cluster. In general industry terms, a node also may be referenced as a discrete component in a hardware or software cluster. Sometimes when referring to hardware, the term host may be used instead.
The Portable Operating System Interface (POSIX) is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems. The WekaFS client is POSIX compliant, which means that it presents data to the OS on which it is installed in a manner that conforms to the POSIX standard. The WekaFS client is sometimes informally referred to as the POSIX client or POSIX driver when describing the overall storage system architecture.
The total capacity that is assigned to filesystems. This includes both SSD and object store capacity.
The Weka process of rehydrating data from an object store to an SSD, based on a prediction of future data access.
Total SSD capacity owned by the user.
The target time for data to be stored on SSDs before releasing from the SSDs to an object-store.
The deletion of the SSD copy of data that has been tiered to the object-store.
The creation of an SSD copy of data stored only on the object-store.
In Weka terms, a physical or virtual instantiation of hardware on which software runs and provides compute or storage services. In general industry terms, a server may also refer to a software process that provides a service to another process, whether on the same host or to a client (e.g. NFS server, SMB server, etc.).
A mode of the Weka software that has been installed and is running, but has not been attached to a cluster.
A Weka feature for uploading snapshots to object stores.
Weka configuration consisting of SSDs and object stores for data storage.
Copying of data to an object store, while it still remains on the SSD.
The minimum time to wait before considering data for tiering from an SSD to an object-store.
The storage capacity that is available for new filesystems.
Less frequently-used data (as opposed to hot data), usually residing on an object-store.