Distributed Storage Service Deployment and Takeover
The distributed storage service is used to deploy or take over distributed storage systems in ZStack Cube Virtualization Edition. You can initialize a distributed storage cluster through the quick deployment workflow, or take over an external distributed storage system that has already been deployed or is already running.
After deployment or takeover, the platform can centrally manage and use distributed storage resources, and provide information such as storage overview, node details, performance metrics, and disk health status. You can add distributed storage as data storage for virtual machines based on business requirements.
Step 1: Upload the Installation Package
Before you begin
- You have prepared the installation package of the distributed storage software.
- The platform management node has been added to the platform as a host.
- At least two distributed storage nodes have been added to the platform as hosts, and the storage network has been configured for the nodes by using Kernel adapters from hosts or distributed port groups. For more information about configuring the storage network, see Create a Kernel Adapter.
- To ensure that distributed storage can enable management node HA together with the platform, configure management node HA in MN Ops before installing distributed storage. For more information about configuring management node HA, see Set Up with the UI.
Procedure
- In the navigation pane, choose .
- On the Storage Overview page, click Upload.
-
In the Upload Installation Package dialog, configure the following options:
Option Description Server IP Displays the IP address of the current management node. In a dual management node environment, this field displays the IP address of the node that hosts the VIP.
Storage Path Specify a directory path on the server to store uploaded installation packages and their extracted files.
Note:
- Make sure this directory has sufficient available space. Otherwise, installation might fail.
- Do not use system directories such as /, /dev, /proc, /sys, /usr/bin, /bin, or /opt. Using system directories might cause server exceptions.
Upload By Select how to upload the installation package. Options include URL and Local File. Interrupted local uploads can be resumed.
Note:
- The system automatically retries recoverable upload errors. If an upload is paused due to a network interruption and the page remains open, the upload resumes automatically after the network recovers.
- If the browser retains permission to access the original local file after the page is refreshed or you sign in again, the system automatically resumes an upload that was paused due to an error. If the browser prompts you to allow access to previously selected files or folders, grant access as needed.
- If the browser does not have permission to access the file or the permission has expired, the upload cannot resume automatically. Click Pending Uploads at the top of the page. In the Pending Upload Tasks panel, locate the task, click Select to Continue, and reselect the same local file.
- A manually paused task does not resume automatically. In the task details, click Continue.
- If the local file has been modified, moved, or deleted, the original upload task cannot resume. Start a new upload.
- If an upload error occurs, the platform automatically retries the upload up to five times. If all five retry attempts fail, the upload task enters the Failed state and cannot be resumed. Start a new upload.
- Click View Upload History to view local file upload tasks.
- Click OK.
Step 2: Deploy the Management Service
Procedure
- On the Storage Overview page, click Install.
-
In the Deploy Management Service dialog, configure the following options:
Option Description VIP Displays the management node IP address in a single management node environment, or the VIP address in a dual management node environment. MN IP Displays the IP address of the single management node or dual management nodes. Enter the SSH port and password of the management node. Database Password If left empty, the initial database password is used by default. If the database password has been changed, enter the new password. - Review the configuration and click OK.
Step 3: Initialize Distributed Storage
Before you begin
Before initialization, configure the storage network for distributed storage nodes by using Kernel adapters from hosts or distributed port groups. For more information about configuring the storage network, see Create a Kernel Adapter.Procedure
- On the Storage Overview page, click Initialize.
- In the Initialize Distributed Storage dialog, complete initialization and storage configuration.
-
For Initialization, configure the following options:
Option Description Storage MN IP Select the management node IP address of the distributed storage. Cluster Displays the cluster location. Admin Network Enter the admin network CIDR to manage and configure the storage cluster. Cluster Network Enter the cluster network CIDR to monitor data disks and synchronize replicas among nodes in the storage cluster. Public Network Enter the public network CIDR for the storage cluster to provide external services. Time Sync Server IP This parameter is displayed based on the storage service type detected by the system. Enter the time synchronization server IP address to ensure time synchronization between nodes in the storage cluster. Gateway Network This parameter is displayed based on the storage service type detected by the system. Enter the gateway network so that user services can access storage resources through this network. - Review the configuration and click Next.
- For Storage Configuration, click Add to add distributed storage nodes.
-
Configure manager and monitor roles.
For data security, we recommend assigning manager (Mgr) and monitor roles (Mon) to three nodes.
-
Specify hostnames for the nodes.
Note:
- Length: 2 to 60 characters.
- Allowed characters: uppercase and lowercase letters, numbers, and hyphens (-).
- The hostname cannot contain consecutive hyphens or start or end with a hyphen.
- When nodes are added, suffixes such as
-1/-2/-3are automatically appended to node hostnames to ensure uniqueness.
- Review the configuration and click OK.
What to do next
Starting from ZStack Cube Virtualization Edition 2.4.10.20, for ZCE-X distributed storage, if you need to access the distributed storage management interface separately, the default login credentials are admin/Admin@123.
Take Over Distributed Storage
After storage package installation, network configuration, and system initialization are complete on the server, or when distributed storage is already running and in use, you can use this method to take over distributed storage.
Procedure
- In the navigation pane, choose .
- On the Storage Overview page, click Take Over Existing Storage.
-
In the Take Over Distributed Storage dialog, configure the following options:
Option Description Storage MN IP Enter the management node IP address of the distributed storage to be taken over. Storage Service Check Click Check to check whether storage services exist and whether the connection can be established successfully. Username Enter the username for logging in to the distributed storage platform. Password Enter the login password. Access Token Enter this parameter as needed based on the detected storage service type. - Review the configuration and click OK.
What to do next
Starting from ZStack Cube Virtualization Edition 2.4.10.20, for ZCE-X distributed storage, if you need to access the distributed storage management interface separately, the default login credentials are admin/Admin@123.
Cancel Distributed Storage Takeover
Canceling distributed storage takeover does not affect stored data, but the platform can no longer manage the distributed storage system.
Procedure
- In the navigation pane, choose .
- On the Storage Overview page, click Cancel Takeover.
- In the confirmation dialog, read the risk warning and click OK after you acknowledge the risk.
