No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionInsight HD 6.5.0 Software Installation 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Generating the Configuration Files (Video Cloud Surveillance)

Generating the Configuration Files (Video Cloud Surveillance)

Scenario

Huawei video cloud surveillance solution, based on the "One Cloud, One Pool, One Platform" concept, provides unified standard service interfaces and is compatible with mainstream vendors' food management software, video analysis algorithms, and service application software. It aims to provide high-quality video management and analysis applications. In the video cloud scenario, the configuration planning tool recommends required components and configuration solutions based on the data volume.

Use the FusionInsight Configuration Planning Tool to generate installation configuration files, and upload these files to related nodes for them to be used during the automatic cluster installation.

Prerequisites

  • The FusionInsight Configuration Planning Tool of the matched version has been obtained based on Preparing Tools and Software, and required data has been planned in Preparing Data.
  • When the FusionInsight Configuration Planning Tool is used, other Excel files with the macro function enabled have been closed to avoid compilation errors.
  • The software package has been decompressed and configured by following the instructions provided in Configuring the Software Package.

Procedure

  1. Open the FusionInsight Configuration Planning Tool, click Options in the Security Warning bar. In the displayed dialog box, select Enable this content and click OK, as shown in Figure 7-1.

    Figure 7-1 Enabling the macro

  2. Click the Tool Description tab, and read the description of the FusionInsight Configuration Planning Tool.

    Select English in Language Select.

  3. Set Use Solution Design to Yes.

    The Solution Configurations sheet is displayed.

  4. Select Video Cloud Big Data (Preferred) for Solution.
  5. On the generated Solution Configurations sheet and Video Cloud Big Data (Preferred) sheet, check the planning suggestions and click Generate Plan.

    Complete the configurations based on the generated plan.

  6. Set the parameters in Basic Configuration based on the description. After filling the form, click Next to go to the Select Services tab.

    • Parameters marked with red asterisks (*) are mandatory in Basic Configuration.
    • Set Install Mode to Cluster Installation. Cluster Expansion is used for cluster capacity expansion. For details, see FusionInsight HD Capacity Expansion Guide.
    • If you set Authentication Mode to Normal Mode, user data can be accessed without security authentication, which brings security risks to enterprise services. Therefore, you are advised to use Security Mode.
    • If you install the cluster as user omm, perform the User name as omm.
    • Configuration option takes effect only when Customize the option or not is set to No.
    • Number of cluster nodes indicates the number of nodes the current cluster contains.
      NOTE:

      When a cluster containing more than 1000 nodes is to be installed, you are advised to generate configuration files by using the Configuration Planning Tool based on the scale of 1000 nodes and then install the cluster. After the cluster is successfully installed, new nodes are added through cluster capacity expansion. You are advised to add not more than 1000 nodes each time. For details about cluster capacity expansion, see the FusionInsight HD Capacity Expansion Guide.

    • The target path of configuration indicates the software decompression path of the active and standby management node. The format is:
      Active management node IP address:software decompression path
      Standby management node IP address:software decompression path

      Example:

      192.168.10.10:/opt/FusionInsight_Manager/software,/opt/FusionInsight_SetupTool
      192.168.10.11:/opt/FusionInsight_Manager/software,/opt/FusionInsight_SetupTool
      NOTE:
      • The "," separator can be used between multiple paths on the same node.
      • If this parameter is empty, the configuration planning tool does not automatically upload the generated configuration file.
    • Chip type specifies the server chip type. Set it to x86_64 for x86 servers and aarch64 for ARM servers.

  7. Select a service based on the planning.

    NOTE:
    • When a service is selected, services depended by it will be selected automatically. Do not manually delete other services that this service depends on.
    • When selecting the services, selecty DBService on two nodes that have the same service plane NIC name.

    After selecting the service, click Next to go to the IP Planning&Process Deployment tab.

  8. Based on the planning and prompts, set Rack Name, Management IP, and Service IP.

    NOTE:
    • When setting Rack Name, you are advised to deploy the active and standby management nodes on different racks, control nodes on different racks, and data nodes on different racks to ensure reliability.
    • Service roles are allocated to different nodes by default. To change the role allocation, go to the Basic Configuration tab, and set Customize the option or not to Yes. Then, go back to the IP Planning&Process Deployment tab to change the role allocation as required.

    After filling the form, click Next to go to the Node Information tab.

  9. Set the parameters in Node Information based on the description.

    NOTE:
    • Number of Logical Disks on Node indicates the number of the disks identified by the OS after RAID configuration is performed.
    • Minimum Data Disk Capacity indicates the capacity of the disk with the minimum capacity on the node except the OS disk.
    • If the value of Host Name is inconsistent with the actual host name of the node, the host name of the node will be changed to the value of Host Name on the Configuration Planning Tool after Configuring and Checking the Installation Environment is performed.

    After filling the form, click Next to go to the Floating IP tab.

  10. Based on the planning and description, set Floating IP, Interface, Subnet Mask, and Gateway of each configuration item.

    If bonds are configured for the node when configuring Interface, enter the correct bond ID, for example, bond0:oms or bond0:web. Otherwise, enter the correct NIC port, for example, eth0:oms or eth0:web.

    After filling the form, click Next to go to the Disk Configuration tab.

    NOTE:

    On the ARM platform, the NIC port is named enahisicXXX by default and cannot be modified. If it is modified, the NIC port name will be reset to the default one after the system is restarted. In this case, FusionInsight services will be unavailable.

  11. Enter the size of each disk partition and the number of disks.

    • Enter the size of each OS disk partition on each node by seeing Preparing OS and the actual planning.
    • Set Data Disk Count of Kafka based on the actual plan. The default parameter value is 1.
    • Determine that Solr index data is stored on a local disk or in the HDFS based on the actual plan. If the data is to be stored on a local disk, select Stored_On_LocalDisk; if the data is to be stored in the HDFS, select Stored_On_HDFS
      NOTE:

      If you select to store Solr index data on HDFS, deploy only one SolrServer instance (including SolrServerAdmin) on each node.

      Click Basic Configuration and set Customize the option or not to Yes. Then delete unnecessary SolrServer instances from IP Planning&Process Deployment.

    • Based on the number of partitions on each node in Management Metadata Disk, set Metadata Disk Count of each node. (For example, if there are four partitions in Management Metadata Disk of node 1, set this parameter to 4.)
    • Data Disk Count of HDFS will be automatically generated.

    After filling the form, click Next to go to the Cluster Configuration tab.

  12. Set parameters that need to be configured according to parameter description. You can skip this step if no parameter needs to be set manually.

    After filling the form, click Next to go to the Instance Configuration tab.

    NOTE:
    • If you want to encrypt disk partitions, specify specify the encryption algorithm of disk partitions and the key length. If you do not specify the item, the configuration file of the partition to be encrypted cannot be generated.
    • The aes-xts-plain64 encryption algorithm is recommended. The minimum key length is recommended to be 256. The complete parameter value example is aes-xts-plain64:256.
    • Before using a third-party encryption algorithm, you must ensure that the OS kernel has been correctly integrated this encryption algorithm.

  13. Set parameters that need to be configured according to parameter description. You can skip this step if no parameter needs to be set manually.

    After filling the form, click Next to go to the Create Config Files tab.

  14. Click Create Config Files. The configuration files required for installing the FusionInsight HD system are automatically generated by the tool and a prompt of file export path is displayed, for example, The installation configuration files are generated in the following path: D:\Test.. Then click OK.

    NOTE:

    If the generated configuration files exist in The target path of configuration, The path D:\Test\software is not empty, do you want to generate configuration files in this path? will be displayed. Back up the files that need to be reserved, and click OK.

  15. In the displayed dialog box, determine whether to upload all the files in Basic Configuration > Output path of configuration files to the specified path on the active and standby management node.

    • If yes, click Yes, enter the username (such as root or omm) of the active management node, click OK, enter the user password, and click OK to start uploading the files. After the files are uploaded, press any key to close the dialog box. Enter the username (such as root or omm) of the standby management node, click OK, enter the user password, and click OK to start uploading the files. After the files are uploaded, press any key to close the dialog box.
    • If no, click No and go to Step 16.

  16. View the configuration files that are generated (listed in Table 7-1), and use WinSCP to upload the files to the corresponding positions.

    NOTE:
    • If you install the cluster as user omm, please upload the files as user omm; otherwise, upload the files as user root.
    • Copy the generated precheck and preinstall folders to overwrite the same folders generated after the software package is decompressed on the active management node. Handle other files according to the description in the table.
    Table 7-1 Configuration files

    Configuration File Type

    Configuration File

    Usage

    Directory Generated (Example Value)

    Server Installation Directory

    OS configuration file

    preinstall.ini

    Configures the OS.

    D:\Test\preinstall

    Generally, preinstall.ini is located on the management node (it is located on the active management node if there are active and standby management nodes). For example, the installation directory is:

    /opt/FusionInsight_SetupTool/preinstall

    Partition configuration file

    hostN.ini (N=0, 1, 2, ...)

    Configures the partition for each node.

    D:\Test\preinstall\partition\ini

    • FusionInsight Configuration Planning Tool generates multiple configuration files naming hostN.ini (N=0, 1, 2, ...), such as host0.ini, host1.ini, and host2.ini.
    • If the partition information is the same on some nodes, the partition configuration file can be shared on these nodes. For example, node 192.168.10.10 and node 192.168.10.11 share host1.ini.
    • The partition configuration file is referenced by preinstall.ini.

    Generally, hostN.ini is located on the management node (it is located on the active management node if there are active and standby management nodes). For example, the installation directory is:

    /opt/FusionInsight_SetupTool/preinstall/partition/ini

    *.conf

    The *.conf is referenced by the hostN.ini file and records the configuration information of each partition.

    D:\Test\preinstall\partition\ini-plugin\conf

    Generally, the *.conf file is located on the management node (it is located on the active management node if there are active and standby management nodes). For example, the installation directory is:

    /opt/FusionInsight_SetupTool/preinstall/partition/ini-plugin/conf

    Installation environment check file

    checkNodes.Config

    Checks the installation environment.

    D:\Test\precheck

    Generally, checkNodes.Config is located on the management node (it is located on the active management node if there are active and standby management nodes). For example, the installation directory is:

    /opt/FusionInsight_SetupTool/precheck

    Manager installation configuration file

    HostIP.ini

    (Corresponds to the install.ini file in the /opt/FusionInsight_Manager/software directory generated by the installation software package)

    Installs Manager.

    D:\Test\install_oms

    • FusionInsight Configuration Planning Tool generates two configuration files naming the IP addresses of the active and standby management nodes, such as 192.168.10.10.ini and 192.168.10.11.ini.
    • To install a single-node Manager, you need to modify this file manually.

    Generally, HostIP.ini is located on the active and standby management nodes. For example, 192.168.10.10.ini is located on the active management node and 192.168.10.11.ini is located on the standby management node. For example, the installation directory is:

    /opt/FusionInsight_Manager/software/install_oms

    Cluster installation configuration file

    InstallTemplate.xml

    Installs the cluster.

    D:\Test\install_cluster

    Cluster installation template file, which does not need to be uploaded.

  17. After the upload is complete, follow the instructions in section Configuring and Checking the Installation Environment to complete the installation and configuration.
Download
Updated: 2019-05-17

Document ID: EDOC1100074555

Views: 6121

Downloads: 6

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next