Product Features
ZStack ZStone provides management and monitoring services for various resources, including servers, hard disks, data disks, block storage volumes, storage pools, and buckets. This topic describes the features provided by ZStack ZStone.
| Type | Feature | Description | |
|---|---|---|---|
| Cluster | Cluster Overview | Visually displays the platform's cluster storage status, cluster resource statistics, and unread alarm statistics in recent seven days in card form. | |
| Cluster storage status: Cluster Health Status, Cluster Capacity Statistics, Cluster Real-Time Data, Cluster Performance Monitoring (IOPS, Bandwidth, and Latency), and Capacity Usage Trend are included. | |||
| Cluster resource statistics: Monitoring Node, Hardware (Server and Hard Disk), Storage Resource (Data Disk), and storage services. | |||
| File Storage | File Share | Supports two file protocols, NFS and SMB. | |
| Supports basic life-cycle management of NFS shares, including creation and deletion. | |||
| A single NFS share supports adding up to 100 clients. | |||
| Supports viewing NFS share addresses and quick access to NFS share addresses, recommended v3 mount parameters, and recommended v4 mount parameters. | |||
| Supports basic life-cycle management of SMB shares, such as creation and deletion. | |||
| A single SMB share supports adding up to 100 file users. | |||
| Supports viewing SMB share addresses and quick access to SMB share addresses and recommended mount parameters. | |||
| File Gateway | Supports basic life-cycle management of file gateway groups, including creation and deletion. | ||
| Supports dynamically creating or deleting gateway nodes based on business needs. A single file gateway group supports adding up to 10 servers as gateway nodes. | |||
| File User | Supports basic life-cycle management of local users, including creation, editing, and deletion. | ||
| Supports changing password for local users. | |||
| File Directory | Supports basic life-cycle management of file directories, including creation and deletion. | ||
| File System | Supports initializing the file system to store metadata information and file data. | ||
| Block Storage | Block Storage Volume | Supports basic life-cycle management of local block storage volumes, including creation and deletion. | |
| Supports maintenance operations for third-party block storage volumes, including synchronization and deletion. | |||
| Supports setting business QoS for block storage volumes based on business needs. | |||
| Supports expanding capacity of block storage volumes. | |||
| Supports migrating block storage volumes to other storage pools. | |||
| Supports creating snapshots for block storage volumes, enabling quick rollback in case of failures. | |||
| Supports rolling back block storage volumes to a specified snapshot point. | |||
| Supports deep cloning block storage volumes. | |||
| Snapshot Management | Supports centralized management of block storage volume snapshots, including cloning and deletion. | ||
| Supports two types of clone: Linked Clone and Independent Clone. | |||
| Object Storage | Storage Policy | Supports basic life-cycle management of storage policies, including creation and deletion. | |
| Supports maintenance operations such as setting default policy, setting data compression, and adding storage class. | |||
| Supports adding storage class from storageclass_0 to storageclass_6 to meet different storage requirements for objects within buckets. | |||
| Object Gateway | Supports basic life-cycle management of S3 gateways, including creation, enabling, disabling, and deletion. | ||
| Supports basic life-cycle management of high-availability (HA) object gateways, including creation and deletion. | |||
| Supports adding or removing load balancer listeners for HA object gateways. | |||
| Supports creating object gateways with Business role, responsible for handling business requests. | |||
| Object User | Supports basic life-cycle management of object users, including creation, enabling, disabling, and deletion. | ||
| Supports setting quotas for object users, including user quota and single-bucket quota. | |||
| Supports three user permissions: read, write, and delete, which can be combined based on actual business needs. | |||
| Supports maintenance operations such as modifying user quotas, user permissions, or storage policies. | |||
| Supports basic life-cycle management of user key pairs, including generation and deletion. | |||
| Bucket | Supports basic life-cycle management of buckets, including creation and deletion. | ||
| Supports setting a bucket owner, who by default has full access permissions to the bucket. | |||
| Supports granting specified ACL permissions to object users, including READ, WRITE, READ_ACP, WRITE_ACP, and FULL_CONTROL. | |||
| Supports maintenance operations such as modifying bucket quotas and adding object users. | |||
| Supports maintenance operations such as adding or removing object users, and modifying access permissions. | |||
| Storage Resource | Storage Pool | Supports basic life-cycle management of storage pools, including creation and deletion. | |
| Supports three types of storage pools: block storage, object storage, and file storage. | |||
| Supports four pool roles: data pool, index pool, compound pool, and metadata pool. | |||
| Supports two data redundancy types: Replicas and EC. | |||
| Supports three data redundancy levels: server, rack, and room. | |||
| Supports maintenance operations such as increasing or reducing pool capacity, setting recovery QoS, and modifying the number of replicas for storage pools. | |||
| Supports displaying the object storage system resources pool after initializing the object storage. | |||
| Supports viewing the forecast capacity usage of storage pools in the next 30 days. | |||
| Data Disk | Supports basic life-cycle management of data disks, including creation and deletion. | ||
| Supports maintenance operations such as setting maintenance mode. | |||
| Hardware | Hard Disk | Supports maintenance operations such as initializing hard disk, setting cache partition (only for free disks), and lighting up disks. | |
| Topology | Supports managing the deployment of physical resources in the cluster in a visual manner. | ||
| Supports adding topology objects you need to generate topology structures. | |||
| Supports canvas operations such as fitting to window, zooming in, and zooming out. | |||
| Server | Supports two server types: storage servers and storage gateway servers. | ||
| A storage server provides storage pools with hard disks that can be used as data disks. | |||
| A storage gateway hosts various interfaces and clients. The system only manages the server gateways and does not manage hard disks on the server. | |||
| Supports five types of roles: admin role, monitor role, block storage gateway, object storage gateway, and file storage gateway. | |||
| The admin role is responsible for collecting the runtime status of the distributed storage cluster and managing the cluster as a management node in multiple ways, such as GUI and API. | |||
| The monitor role is responsible for monitoring the cluster storage data and maintaining overall status of the cluster, including metadata such as data mapping and cluster authentication. | |||
| The block storage gateway role is responsible for the access between the server and the cluster through Block interface. | |||
| The object storage gateway role is responsible for the access between the server and the cluster through Object interface. | |||
| On an object storage gateway server, you can turn on the object gateway to get the S3 protocol and gateway services. | |||
| On a file storage gateway server, you can create a file gateway to get file storage access protocols such as SMB and NFS. | |||
| Storage servers can be configured with any of the five roles mentioned above. | |||
| Storage gateway servers can only be configured with the block storage gateway role. | |||
| Supports adding or deleting roles for a storage server. | |||
| Supports basic life-cycle management of servers, including addition and deletion. | |||
| Cluster | Supports displaying general storage cluster information, including cluster name, network configuration, NTP server address, and number of servers. | ||
| Supports initializing high-performance cluster and setting RDMA transmission. | |||
| Monitoring Management | Operation Log | Allows you to view the record of completed operations, specifically, description, task state, operator, creation time, completion time, and task result, enabling finer-grained management. | |
| Alarm Center | Supports visually checking and managing alarm messages of the whole platform in list form, improving operational efficiency. | ||
| Supports filtering alarm messages by time range to view the details of messages triggered within this period. | |||
| Supports marking alarm messages as read. | |||
| Supports viewing alarm message details. | |||
| Supports sorting alarm messages by emergency level (emergent, major, and info) or alarm time. | |||
| Supports visually checking predefined alarm rules in list form. | |||
| Supports adding and removing endpoints. | |||
| Provides system endpoints by default. If an alarm uses a system endpoint, you will receive subscription messages sent by the system. | |||
| Supports basic life-cycle management of the endpoint, including creation and deletion. | |||
| System Setting | Email Server | Supports basic life-cycle management of email servers, including addition and deletion. | |
| Supports only one email server type: smtp. | |||
| Supports testing the connectivity of email servers. | |||
| Supports configuring encrypted connections for email server ports, including two encryption types, that is, STARTTLS/NONE and SSL/TLS. | |||
| Global Setting | Provides platform-level feature settings, which take effect globally across the platform once configured. | ||
| License Management | / | The distributed storage platform offers multiple licensing options. Purchase as needed. | |
| Licenses can be categorized into two types: Base License and Module License. | |||
| Using the base license together with module licenses helps you leverage all functionality of the distributed storage platform, thus meeting the needs in mainstream business scenarios. | |||
| The base license consists of Enterprise Trial and Enterprise Prepaid. | |||
| Using module licenses together with base licenses helps you get the storage function in special scenarios, thus meeting the special needs in particular business scenarios. | |||
| There are five types of module licenses: block storage, object storage, high-performance block storage, file storage, and high-speed network. | |||
| Supports two authorization methods: USB Key authorization and request code authorization. | |||
| Supports checking the current licenses and historical authorization records. | |||
| Supports sending license anomaly warnings (for example, license expires after xx days, license expired, insufficient license authorization quota). | |||