Configuring by Wizard

Procedure

1. Select Deploy by Wizard.
2. Install the management nodes.
   1. Add a management node.
      1. Click Add Management Node.

         The Add Management Node page is displayed on the right.

      2. Set information about the management node. Table 1 describes related parameters.

         Table 1 Management node parameters

         Parameter	Description
         IP	Management network IP address (or internal management network IP address) of the management node. Both IPv4 and IPv6 addresses are supported. The management network IP addresses of all nodes must be of the same type. NOTE: When the management network is not isolated, the management network IP address cannot use the same subnet as the storage, control, service, or replication network. When the management network is isolated, the management network IP address (that is, the internal management network IP address) cannot use the same subnet as the storage, control, service, replication, or external management network.
         SN	Serial number of the management node.
         Cabinet	Cabinet where the management node resides. [Value range] The value contains 1 to 256 characters. The value can contain only letters, digits, underscores (_), and hyphens (-). The value cannot start or end with a space.
         Username	If you use a pre-installed operating system, enter fsadmin for authentication. If you use a third-party operating system: User root is preferentially used for authentication. If you use a non-root user for authentication, the user must have the SUDO, remote SFTP, and SSH permissions. For the SUDO permission, when running the sudo su - root command, you must use the password of user root instead of the password of the current user.
         Password	Password of the login user.
         Password of root	When the user is a non-root user, enter the password of user root.

         

         You can click More on the right of the node to modify or delete the management node. If the management node fails to be added, click Retry to add it again.

      3. Click OK.
   2. Configure the management nodes.
      1. Click Configure Management Node.

         The Configure Management Node page is displayed on the right.

      2. Set information about the management network. Table 1 describes related parameters.

         Table 2 Management network parameters

         Parameter	Description
         DeviceManager Mgmt IP	Floating management IP address of a management node. NOTE: After logging in to DeviceManager using this IP address, you can access the active and standby FSM nodes at the same time. The type of the floating management IP address (IPv4 or IPv6) must be the same as that configured on a node. This parameter is not displayed when a single management node is deployed.
         Installation Mode	Installation mode of the management nodes. Possible options are Pre-installation and Regular installation. Pre-installation: The basic software package has been pre-installed on management nodes and storage nodes. Regular installation: The basic software package is not installed on management nodes and storage nodes. You need to import the basic software package and install it on the nodes.
         Service Component Type	Supported service type to be selected. Possible options are Converged and Block. Converged: Supports the file service, HDFS service, and object service. Block: Supports only the block service.
         Service Type	Service type to be selected based on the actual service scenario to achieve optimal system performance. The options are General, Intelligent video and image, Backup and archiving, and Media. General: provides file, object, and HDFS storage services for upper-layer applications and applies to high-performance computing (HPC) scenarios (such as meteorology, genetics, and oil industries) and big data analysis scenarios (such as 5G log retention and analysis). Intelligent video and image: applies to video and image storage industries, including video stream and checkpoint image storage scenarios. Backup and archiving: stores data that is less frequently accessed for a long time in scenarios with low performance requirements, such as long-term retention of bills, audio/video recordings, and media resources due to compliance requirements. Media: applies to video editing and media asset archiving in broadcasting, television, and film industries with sequential read and write of large files. NOTE: This parameter is displayed when the Service Component Type is set to Converged. Intelligent video and image, Backup and archiving, and Media can be used only for networking in the standard protocol scenario.
         Port	Network port used by the management network.
         Subnet Mask	Subnet mask of the management network. The value is automatically generated after you select a port and cannot be changed. NOTE: If the management IP address is an IPv4 address, enter the corresponding subnet mask.
         Prefix	Prefix of the management network. The value is automatically generated after you select a port and cannot be changed. NOTE: If the management IP address is an IPv6 address, enter the corresponding prefix.
         Gateway	Gateway of the management network. The value is automatically generated after you select a port and cannot be changed. NOTE: When the management network is not isolated, a gateway must be configured for the management network. When the management network is isolated, a gateway must be configured for the external management network. If there are multiple subnets in the internal management network, a gateway must be configured. If there is one subnet in the internal management network, you are advised to configure a gateway.
         Management IP	External IP address of a management node. The value is automatically generated after you select a port and cannot be changed. NOTE: When a single management node is deployed, this IP address is used to access DeviceManager.
         Node Name	Name of a management node. [Value range] The name contains 1 to 64 characters. The name can contain only letters, digits, hyphens (-), underscores (_), and periods (.), and must start and end with a letter or digit. A period (.) cannot be adjacent to a period (.), hyphen (-), or underscore (_).

      3. (Optional) Enable Secondary DeviceManager Mgmt IP.

         Set information about the management network. Table 3 describes related parameters.

         Table 3 Management network parameters

         Parameter	Description
         Secondary DeviceManager Mgmt IP	Another floating management IP address of a management node. You can also use this IP address to log in to DeviceManager. NOTE: If two management nodes are configured, the type (IPv4 or IPv6) of the floating management IP address entered here must be different from that of DeviceManager Mgmt IP. If only one management node is configured, the type (IPv4 or IPv6) of the floating management IP address entered here must be different from that of Management IP. For example, if DeviceManager Mgmt IP is an IPv4 address, enter an IPv6 address. If DeviceManager Mgmt IP is an IPv6 address, enter an IPv4 address. If only one management node is deployed, the value is automatically generated after you select a port and cannot be changed.
         Port	Network port used by the management network.
         Subnet Mask	Subnet mask of the management network. NOTE: If Secondary DeviceManager Mgmt IP is an IPv4 address, enter the corresponding subnet mask. If only one management node is deployed, the value is automatically generated after you select a port and cannot be changed.
         Prefix	Prefix of the management network. NOTE: If Secondary DeviceManager Mgmt IP is an IPv6 address, enter the corresponding prefix. If only one management node is deployed, the value is automatically generated after you select a port and cannot be changed.
         Gateway	Gateway of the management network. NOTE: If only one management node is deployed, the value will be automatically filled in after you select a port and cannot be changed. When the management network is not isolated, a gateway must be configured for the management network. When the management network is isolated, a gateway must be configured for the external management network. If there are multiple subnets in the internal management network, a gateway must be configured. If there is one subnet in the internal management network, you are advised to configure a gateway.

      4. Set a password for the super administrator and enter the password again for confirmation.
      5. (Optional) Enable the Management Network Isolation function.
         Set information about the internal management network. Table 4 describes related parameters.

         Table 4 Internal management network parameters

         Parameter	Description
         Internal Management Floating IP	Internal management floating IP address of a management node. NOTE: This parameter is not displayed when a single management node is deployed.
         Port	Port used by the internal management network.
         Subnet Mask	Subnet mask of the internal management network. The value is automatically generated after you select a port and cannot be changed. NOTE: When Internal Management Floating IP is set to an IPv4 address, the system automatically generates the corresponding subnet mask.
         Arbitration IP Address	Gateway of the internal management network.
         Internal Management IP	Internal IP address of a management node. The value is automatically generated after you select a port and cannot be changed. NOTE: The IP addresses of the external management network and internal management network must be on different network segments.

      6. Click OK.
   3. Install the management nodes.
      • When Installation Mode is set to Pre-installation, click Install to install the nodes.
      • When Installation Mode is set to Regular installation, import the basic service package and then perform the installation.
        1. Click , select the basic service package to be uploaded, and click Upload.
        2. (Optional) Click , select the data pilot service package to be uploaded, and click Upload.
           

           If you do not want to import the package now, you can choose Resources > Resources > Services > Value-Added Service to import it after the initialization is complete.

        3. After the upload is complete, click Install.
   4. Wait until the installation is successful, click Next.

3. Add storage nodes.
   • Batch importing nodes
     1. Click Batch Import Node.
     2. Click , select the node information file to be imported, and click Upload.
        

        You can click Download the template, fill node parameters in the template, and upload the template file.

     3. Authenticate all nodes. Click Authenticate, enter the user name and password, and click OK.
     4. After all nodes are authenticated successfully, click OK.
     5. Click Submit.
     6. After the nodes are successfully configured, click Next.
   • Manually adding a node
     1. Click Manually Add Node.

        The Add Node page is displayed on the right.

     2. Configure basic information and authentication information of the node. Table 5 describes related parameters.

        Table 5 Basic node and authentication information

        Parameter	Description
        Node Type	The value can be New node or Management node. New node: suitable for scenarios where all types of nodes are added as storage nodes. In this mode, you need to enter the management IP address and authentication information of the nodes. Management node: suitable for scenarios where management nodes are added as storage nodes. This mode is recommended for management nodes. In this mode, you can directly select the management IP address of a management node without entering authentication information.
        Management IP Address	Management network IP address of the storage node. NOTE: The management network IP address cannot use the same subnet as the storage, control, service, or replication network. When the management network is isolated, the management IP address must be able to communicate with the internal management network.
        Cabinet	Cabinet where the storage node resides. [Value range] The value contains 1 to 256 characters. The value can contain only letters, digits, underscores (_), and hyphens (-). The value cannot start or end with a space.
        Node Name	Name of the storage node. [Value range] The name contains 1 to 64 characters. The name can contain only letters, digits, hyphens (-), underscores (_), and periods (.), and must start and end with a letter or digit. A period (.) cannot be adjacent to a period (.), hyphen (-), or underscore (_).
        Chassis	Chassis where the storage node resides.
        Slot	Number of the slot where the storage node resides.
        Node Role	Role automatically matched based on the management IP address.
        Installation Mode	Installation mode of the storage node. Possible options are Pre-installation and Regular installation.
        iBMC Password	After this function is enabled, you need to configure a user name and password for authenticating the iBMC server. NOTE: This parameter needs to be set only for nodes that contain storage roles.
        Username	If you use a pre-installed operating system, enter fsadmin for authentication. If you use a third-party operating system: User root is preferentially used for authentication. If you use a non-root user for authentication, the user must have the SUDO, remote SFTP, and SSH permissions. For the SUDO permission, when running the sudo su - root command, you must use the password of user root instead of the password of the current user.
        Password	Password of the login user.
        Password of root	When the user is a non-root user, enter the password of user root.

     3. Click OK.
     4. Add other storage nodes one by one and click Submit.
     5. After the nodes are successfully configured, click Next.

4. Configure the storage network.
   1. Select Front- and Back-End Shared Network or Front- and Back-End Separated Networks. The GUI operations vary according to the selected transmission protocol.
   2. Configure the storage network as prompted. Table 6 describes related parameters.

      Table 6 Storage network parameters

      Parameter	Description
      Use Configured Storage IP Address Only	Yes: Only storage IP addresses configured in advance are used. To select this option, storage IP addresses must be configured for all storage nodes in advance. No: If no storage network IP address is configured in advance, the system will assign new storage network IP addresses to the nodes based on the settings.
      Transmission Protocol	Transmission protocol used by the storage network. Possible options are TCP, IB, and RoCE. If Front- and Back-End Separated Networks is selected, the following transmission protocol combinations can be applied: Front-end network: TCP; back-end network: TCP. Front-end network: IB; back-end network: IB or RoCE. Front-end network: RoCE; back-end network: RoCE.
      Network Flow Classification	This parameter is available only when Transmission Protocol is set to RoCE. Set this parameter based on the data traffic type.
      Multiple IP Addresses	This parameter is available only when Transmission Protocol is set to RoCE. Set this parameter based on the node type.
      Bond Mode	This parameter is available when you select No in Use Configured Storage IP Address Only. Bond mode of the storage network. bond1: active/standby mode. bond4: dynamic link aggregation mode. NOTE: When Transmission Protocol is set to TCP, bond1 and bond4 are supported. You are advised to select bond4. When Transmission Protocol is set to IB, only bond1 is supported. bond1 supports the load balancing function.

   3. Click Add Storage IP Address Range and set the IP address range, subnet mask/prefix, and port number of the storage network.
      

      • The start and end IP addresses of each storage IP address range must use the same subnet.
      • In the multi-IP scenario, the storage network can use the same subnet as the control network, but cannot use the same subnet as the internal management, external management, service, and replication networks. The IP address range of the storage network cannot use the same subnet as the IP addresses of other ports on the nodes.
      • In non-multi-IP scenarios, the storage network cannot use the same subnet as the internal management, external management, service, and replication networks. The IP address range of the storage network cannot use the same subnet as the IP addresses of other ports on the nodes.
      • If the storage IP addresses are IPv4 addresses, enter the corresponding subnet mask. If the storage IP addresses are IPv6 addresses, enter the corresponding prefix.
      • If Use Configured IP Addresses Only is set to No, you need to configure the port of the storage network. Click to go to the Manage Bond Port page. You can configure a port as required.
      • You can click Add Storage IP Address Range to configure multiple storage IP address ranges across network segments. A maximum of 300 storage IP address ranges can be configured. If storage IP addresses are on different network segments, you need to configure static routes or policy-based routes. If multiple IP addresses are used as storage IP addresses, you need to configure policy-based routes. Click Configure Port and Route to go to the route configuration page. For details, see Managing Port and Route Configurations.
      • To remove an IP address range, select it and click Remove. You can also click More to modify or remove an added IP address range.
   4. If Transmission Protocol of the back-end shared network or front-end storage network is set to RoCE and Multiple IP Addresses is set to Yes, you need to configure control IP addresses. Click Add Control IP Address Range and set the IP address range, subnet mask/prefix, and gateway of the control network.
      

      • The control and the front-end storage networks have same VLAN ID, and can use the same (recommended) or different subnets. When using the same subnet, they must use different IP address ranges.
      • A control network gateway needs to be configured in either of the following scenarios:
        • The control network crosses subnets.
        • The control network does not cross subnets currently but needs to cross subnets due to subsequent capacity expansion.
      • If the control IP addresses are IPv4 addresses, enter the corresponding subnet mask. If the control IP addresses are IPv6 addresses, enter the corresponding prefix.
      • You can click Add Control IP Address Range to configure multiple control IP address ranges. In addition, cross-network segment configuration is supported. In cross-network segment scenarios, enter the gateway of the actually used control IP addresses.
      • To remove an IP address range, select it and click Remove. You can also click More to modify or remove an added IP address range.
   5. Click Preview. The system automatically reads the IP addresses configured on the nodes.
      • If the storage or control IP addresses have been configured, the system displays the storage or control IP address of each node.
      • If the storage or control IP addresses are not configured, the system displays the storage or control IP addresses to be allocated to storage nodes.
   6. Click Submit.
   7. After the storage network is configured successfully, click Next.

5. Install the storage nodes.
   1. (Optional) If the installation fails, you can click Restore Factory Settings to reconfigure the nodes.
   2. Click Install.
   3. Wait until the installation is successful, click Next.
   

   After a storage node is added to the cluster, the security sandbox function will be automatically enabled for the storage node. To check whether the security sandbox function is automatically enabled, after the initial configuration is complete, choose Cluster > Cluster > Hardware and click the Nodes tab to view the security sandbox status. If the security sandbox is disabled, enable it.

6. Create a control cluster.
   1. Set the control cluster name.
      

      • The name contains 1 to 64 characters.
      • A control cluster name can contain only letters, digits, underscores (_), and hyphens (-).
   2. In Metadata Storage Location, select the location to store the metadata.
      • Physical disk: If you select this option, specify Disk Type and Disk Selection Mode.
        

        Disk selection modes include:

        • Specify Slot: Enter a slot number. A slot number ranges from 0 to 60.
        • Manually Select: You need to manually select disks for each node.

        If you need to select different disk types for different nodes, set the disk type to Custom. In this case, the disk selection mode can only be Manually Select.

      • System disk partition: If you select this option, the system uses the /opt/zk_disk, /opt/ccdb_disk, and /opt/ccdb_disk2 partitions of the system disk to store metadata.
      • Custom: Physical disk and System disk partition can be mixed. This mode is used when you need to select different metadata storage locations for different nodes.
   3. Select the nodes where the control cluster is to be created.
      • If Metadata Storage Location is set to Physical disk, select the nodes and disks for creating the control cluster from Available Nodes.
      • If Metadata Storage Location is set to System disk partition, select the nodes for creating the control cluster from Available Nodes.
   4. Click Create.
   5. After the creation is complete, click Finish.

Follow-up Procedure

After the initialization is complete, the page for importing license files is displayed. You need to import a license file before using the system. For details, see Importing a License File.