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

FusionStorage V100R006C20 Block Storage Service Software Installation Guide 07

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).
Connecting FusionStorage Block to the Native OpenStack System

Connecting FusionStorage Block to the Native OpenStack System

Scenarios

If FusionStorage Block is used in the native OpenStack system, connect FusionStorage Block to the native OpenStack system after installing and configuring FusionStorage Block. This operation is used to guide software commissioning engineers to connect FusionStorage Block to the native OpenStack system (Mitaka release).

Prerequisites

Conditions

  • You have installed the native OpenStack system and FusionStorage Block.
  • You have installed FusionStorage Agent (FSA) on the nodes in the native OpenStack system and have created the block storage clients.

Procedure

    Connect FusionStorage Block to the native OpenStack system.

    1. Use PuTTY to log in to a cinder-volume deployed node as user root.
    2. Run the following command to open the cinder.conf file using the vi editor:

      vi /etc/cinder/cinder.conf

    3. Press i to enter the editing mode.
    4. Add information about the FusionStorage Block backend storage to the cinder.conf file.

      Change the enabled_backends value and add storage information to the end of the configuration file.

      An example of parameter enabled_backends is provided as follows:
      [DEFAULT]
      enabled_backends=lvm,fusionstorage_ssd3copy
      dsware_manager = 192.168.211.99
      fusionstorageagent = 192.168.211.82,192.168.211.85,192.168.211.86
      
      An example of the added storage configuration information is as follows:
      [fusionstorage_ssd3copy]
      volume_backend_name = fusionstorage_ssd3copy
      volume_driver = cinder.volume.drivers.dsware.DSWARELocalDriver
      pool_id_list = 0,1
      over_ratio = 3.0
      Table 9-4 describes the parameters in the configuration file.
      Table 9-4  Parameter description

      Parameter

      Description

      enabled_backends

      Name of the backend storage to be enabled in the OpenStack system

      The parameter value must be the same as the fusionstorage_ssd3copy value. Multiple backend storage systems are isolated using commas (,).

      dsware_manager

      Floating IP address of FSM nodes

      fusionstorageagent

      IP addresses of the nodes in the OpenStack system which are specified for the communication with FusionStorage Block

      The specified nodes are used to deliver management commands to FusionStorage Block. You are advised to specify three nodes.

      fusionstorage_ssd3copy

      Backend storage name which can be defined by users

      volume_backend_name

      Backend storage name

      The parameter value must be the same as the fusionstorage_ssd3copy value.

      volume_driver

      Directory containing the FusionStorage Block storage driver

      The parameter value is cinder.volume.drivers.dsware.DSWARELocalDriver, and you do not need to change the value.

      pool_id_list

      Storage pool list

      Specifies the storage pool within which to create volumes. If multiple storage pools are available in the system, you can use this parameter to create volumes in the specified storage pool.

      pool_type

      Storage pool type

      Possible values are sas2copy, sas3copy, sata2copy, sata3copy, ssd2copy, and ssd3copy.

    5. Optional: To back up the volumes whose status is in-use, you need to modify the following configuration items in the cinder.conf file:

      backup_use_same_host=true
      backup_use_temp_snapshot=true

    6. Press Esc and enter :wq.

      The system saves the modification and exits the vi editor.

    7. Run the following command to restart the cinder-volume service:

      service openstack-cinder-volume restart

    8. If multiple cinder-volume deployed nodes need to be configured, repeat 1 to 7 to complete the configuration.

    Check iptables.

    1. Use PuTTY to log in to each FSA node where OpenStack has been installed as user root.
    2. Run the iptables -s | grep REJECT command to check whether INPUT and FORWARD of icmp-host-prohibited contain REJECT, as shown in Figure 9-3.

      Figure 9-3  Checking iptables
      • If REJECT is not contained, no further action is required.
      • If REJECT is contained, perform the following operations:

    3. Run the vim /etc/sysconfig/iptables command, comment out the content related to icmp-host-prohibited, run the :wq command, and press Enter to save the configuration.

      #-A INPUT -j REJECT --reject-with icmp-host-prohibited
      #-A FORWARD -j REJECT --reject-with icmp-host-prohibited

    4. Run the systemctl restart iptables command to restart the iptables service.
Translation
Download
Updated: 2019-06-29

Document ID: EDOC1100016637

Views: 23904

Downloads: 14

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