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

OceanStor BCManager 6.5.0 eReplication User Guide 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).
Installing the eReplication Server Using a KVM (Only Applicable to FusionSphere OpenStack)

Installing the eReplication Server Using a KVM (Only Applicable to FusionSphere OpenStack)

This section describes how to use FusionSphere OpenStack OM management software to install the eReplication Server based on a Kernel-based Virtual Machine (KVM) template. This installation method is only applicable to FusionSphere OpenStack.

Prerequisites

  • To deploy the eReplication Server on FusionSphere OpenStack using a KVM template, the system environment must meet the following requirements:
    • vCPUs: 4
    • Memory: 8 GB or larger DDR
    • Free disk space: 40 GB or larger
  • FusionSphere OpenStack OM management software V100R006C00RC3 or later has been prepared, and its management IP address or floating IP address, login account, and password have been obtained.
  • The image file of the FusionSphere OpenStack KVM and the tool have been obtained.
  • The signature file and digital signature public key have been obtained and the software integrity has been verified.
    1. On the page for downloading the eReplication software package, you can download the .asc digital signature file whose name is the same as that of the software package.
    2. You have used the digital signature public key and verification tool provided by the website to verify the digital signature of the software package. You can obtain the digital signature public key, verification tool, and their usage methods from:

Context

  • Ensure the time of the VM with the eReplication Server installed and the OpenStack Server system time are same.
  • In CAHA scenarios, after the eReplication Server is installed using a KVM template, you need to configure mappings between service domain names of OpenStack and corresponding IP addresses using the DNS or host file to enable eReplication to access the OpenStack services using the domain names.
  • In the virtualization template, the SFTP service is disabled, by default. For this reason, files cannot be directly uploaded to a template environment. If you want to use a tool, for example, XFTP, to upload files to a template environment, see the rollback solution in Disabling the SFTP Service in the OceanStor BCManager V200R001C10 eReplication Security Configuration Hardening Manual to enable the SFTP service.
  • You can log in to SFTP only as user DRManager, an account with low-level permissions. Files can only be uploaded to directory /home/DRManager by default. If files are uploaded to another directory, ensure that the directory has related permissions.
  • Xshell and PuTTY, manually enable the SSHD, rpcbind, or NTP service as follows (the SSHD service is used as an example):
    1. Log in to the virtualization template environment in VNC mode.
    2. Run the service sshd start to start the SSHD service.
    3. Optional: If you want to start the SSHD service along with the system startup, run the systemctl enable sshd command.

Procedure

  1. Log in to FusionSphere OpenStack OM.
    1. Open an Internet Explorer browser. This section uses Windows Internet Explorer 9.0 as an example.
    2. In the address box, type https://management IP address (deployed in standalone mode) or floating IP address (deployed in active-standby mode) and press Enter.

      For example, in the address box of the browser, enter https://192.168.10.10.

    3. Select a language, and set Username and Password.

      Username defaults to cloud_admin, and Password defaults to FusionSphere123. If the default password of an account has been changed, contact the FusionSphere OpenStack administrator to obtain the latest password.

    4. Click Login or Enter.
  2. Create an image.
    1. On the menu bar, choose Resources > Images.
    2. Click Register.
    3. In the Register Image dialog box that is displayed, set the image parameters. Table 2-20 lists related parameters.



      Table 2-20  Parameters for registering an image

      Parameter

      Description

      Setting

      Provided As Service

      Whether an image can be provided as a service.

      Not supported

      Type

      The template currently used is a KVM template.

      [Value range]

      KVM

      Name

      Name of an image to be registered.

      [Value range]

      Contains 0 to 255 characters.

      Applicable OS

      Set based on template operating system types. The template operating system is Linux.

      [Value range]

      Linux

      OS Version

      Set based on operating system versions. The template operating system version is EulerLinux V100R001C00 64bit.
      NOTE:
      If there is no EulerLinux V100R001C00 64bit in the drop-down list box of OS Version, you can select Euler2.2 or other Euler OS versions.

      [Value range]

      EulerLinux V100R001C00 64bit

      Min Disk (GB)

      Set based on site requirements.

      [Value range]

      40

      Min Memory (MB)

      Set based on site requirements.

      [Value range]

      8192

      Disk Device Type

      Because the template system does not equipped with vmtools, select ide.

      [Value range]

      ide

      Upload Mode

      HTTPS is supported for local uploading.

      [Value range]

      HTTPS

      Image File

      Select a locally uploaded image file.

      -

      Disk Format

      Set based on the image type. The value of the current template is qcow2.

      [Value range]

      qcow2

      Description

      Remarks of an image to be registered.

      [Value range]

      Contains 0 to 1024 characters.

      NOTE:
      For parameters not described in Table 2-20, use their default values.

    4. Click Register.
    5. In the Confirm dialog box that is displayed, click OK.



      After the image is successfully registered, its Status is Registration Succeeded.

  3. Create specifications.
    1. On the menu bar, choose Resources > Flavors.
    2. Click Create Flavor.
    3. In the Create Flavor dialog box that is displayed, set the specifications parameters. Table 2-21 lists related parameters.

      In the following figure, Boot Device is set to Cloud Disk.



      Table 2-21  Specifications parameters

      Parameter

      Description

      Setting

      Type

      Choose VM.

      [Value range]

      VM

      Boot Device

      select Local Disk or Cloud Disk.

      [Value range]

      If control nodes are interconnected with storage devices, select Cloud Disk.

      If control nodes are not interconnected with storage devices, select Local Disk.

      Name

      Specification name

      [Value range]

      • Contains 0 to 255 characters.
      • Contains only letters, digits, hyphens (-), underscores (_), and periods (.).

      vCPUs

      Set based on site requirements.

      [Value range]

      4

      Memory (MB)

      Equal to or larger than Min Memory (MB) in Table 2-20.

      [Value range]

      8192

      System Volume(GB)

      This parameter is displayed when Boot Device is set to Cloud Disk.

      Equal to or larger than Min Disk (GB) in Table 2-20.

      [Value range]

      40

      Root Disk(GB)

      This parameter is displayed when Boot Device is set to Local Disk.

      Equal to or larger than Min Disk (GB) in Table 2-20.

      [Value range]

      40

      NOTE:
      For parameters not described in Table 2-21, use their default values.

    4. Click OK.
  4. Create a VM.
    1. On the menu bar, choose Resources > Compute Instances.
    2. Click Create.
    3. Select manage-az in the Availability Zones, and click Next.
    4. Select the image created in 2, select Cloud Disk, and click Next.

      NOTE:

      Setting Boot Device to Cloud Disk is used as an example only. You can set Boot Device based on site requirements.

    5. Select specifications created in 3 and click Next.
    6. In Network, select a project that can communicate externally.
    7. In Network, select the external_api network that can communicate externally.
    8. In IP, select Specified.
    9. In Available IP Address Segments, enter an IP address. This IP address cannot be set for other devices. Click Next.

      NOTE:

      Floating IP address configuration: If the template VM is used in eReplication HA mode scenarios, and floating IP addresses are planned in advanced, set the floating IP address to be the one configured for HA mode. Otherwise, the floating IP address cannot be used to access the eReplication service after the eReplication active-standby network is configured. If you want to modify the floating IP address after the virtualization template is deployed, see the Change the floating IP address in Postrequisite.



    10. Set VM Name, select the host where the template is to be imported, and click Import.
    11. In the Import dialog box that is displayed, copy the following additional information.

      {
         "localIP":{"type":"ip","value":""},
         "netmask":{"type":"ip","value":"255.255.0.0"},
         "gateway":{"type":"ip","value":""}
      }
      NOTE:
      • If you need to add additional information, click Add. If you want to delete additional information, click Delete in the Operation area.
      • localIP is the IP address set in 4.i.

    12. Click OK. The information is imported to Additional Info.



      NOTE:
      • localIP is the IP address set in 4.i.
      • If you need to add additional information, click Add. If you want to delete additional information, click Delete in the Operation area.

    13. Click Next.
    14. Click Finish.

      If the VM is successfully created, its Status is Running.

      NOTE:

      eReplication may not be started after the VM is successfully created. You can log in to the VM, go to directory /opt/BCManager/Runtime/bin, and run the sh showSystemStatus.sh command to check whether eReplication is started. If the service status displayed is Normal or Active_normal, eReplication is started and you can log in to eReplication.

  5. Install UVP VMTools.

    After template deployment, you need to install UVP VMTools on the eReplication Server VM to enhance the I/O processing capability as well as implement VM hardware monitoring.

    NOTE:
    • Install UVP VMTools right after the active and standby nodes are installed, because installing UVP VMTools during the follow-up procedures will restart the eReplication Server and thereby interrupting services.
    • For details about the installation instructions of UVP VMTools, please refer to Installing UVP VMTools.

  6. (Optional)Configure firewalls.

    For security purposes, you are advised to Refer to configure the firewall rule by referring to 2 to 7 described in Euler Linux (the Server server) in Configuring the Firewall.
    • After the firewall rules have been configured, if maintenance terminals do not need to access port 22 of the eReplication server by using IP addresses, run the iptables -D INPUT num command to delete the corresponding rule. (Run the iptables -L -n -v --line-numbers command to check the detailed definition and obtain num of the current firewall rule.) After deletion, you can log in to the operating system only using VNC.
    • Run the iptables -P INPUT ACCEPT command and use num to delete the corresponding firewall rule. If you delete port 22 through remote logins, you are advised to run the iptables -P INPUT ACCEPT for deletion. Otherwise, you can only log in to the operating system of the eReplication Server using VNC and the IP address of an allowable maintenance terminal, instead of the current maintenance terminal after deletion.

    After the firewall is enabled, perform Log In To eReplication. If the login succeeds, the eReplication Server is successfully installed.

Follow-up Procedure

  • After the template is deployed, you need to configure the DNS server or modify file Hosts. Otherwise, OpenStack cannot be detected.

    If no DNS server is configured on the system, you need to change the IP address and domain name in file /etc/hosts under the root directory.

    cloud server HA scenario: the following operation uses 192.168.31.10 as the IP address of the External API reverse agents in the production and DR centers on FusionSphere OpenStack, and the Keystone is az1.dc1.domainname.com:443 as an example.
    192.168.31.10 identity.az1.dc1.domainname.com
    
    192.168.31.10 compute.az1.dc1.domainname.com
    192.168.31.10 volume.az1.dc1.domainname.com
    192.168.31.10 network.az1.dc1.domainname.com
    192.168.31.10 drextend.az1.dc1.domainname.com
    192.168.31.10 nova-novncproxy.az1.dc1.domainname.com
    192.168.31.10 compute-ext.az1.dc1.domainname.com
    192.168.31.10 metering.az1.dc1.domainname.com
    192.168.31.10 image.az1.dc1.domainname.com
    
    cloud server DR scenario: the following operation uses 192.168.31.10 and 192.168.32.11 as the IP address of the External API reverse agents in the production and DR centers on FusionSphere OpenStack, and the Keystone is az1.dc1.domainname.com:443 as an example.
    192.168.31.10 identity.az1.dc1.domainname.com
    
    192.168.31.10 compute.az1.dc1.domainname.com
    192.168.31.10 volume.az1.dc1.domainname.com
    192.168.31.10 network.az1.dc1.domainname.com
    192.168.31.10 drextend.az1.dc1.domainname.com
    192.168.31.10 nova-novncproxy.az1.dc1.domainname.com
    192.168.31.10 compute-ext.az1.dc1.domainname.com
    192.168.31.10 metering.az1.dc1.domainname.com
    192.168.31.10 image.az1.dc1.domainname.com
    
    192.168.32.11 compute.az1.dc2.domainname.com
    192.168.32.11 volume.az1.dc2.domainname.com
    192.168.32.11 network.az1.dc2.domainname.com
    192.168.32.11 drextend.az1.dc2.domainname.com
    192.168.32.11 nova-novncproxy.az1.dc2.domainname.com
    192.168.32.11 compute-ext.az1.dc2.domainname.com
    192.168.32.11 metering.az1.dc2.domainname.com
    192.168.32.11 image.az1.dc2.domainname.com
    
    NOTE:

    where az1 is the Availability Zone (AZ) name, dc1 and dc2 are the name of the data center.

    To check Keystone, perform the following steps:
    1. Log in to the page for deploying FusionSphere OpenStack.
    2. In the navigation tree, choose Configure > System.
    3. In the operation area, click Change Domain Name.
    4. In the Change Domain Name dialog box that is displayed, check Keystone.

      The following figure is used as an example, Keystone is az1.dc1.domainname.com:443.



  • Change the floating IP address.
    If the floating IP address of the eReplication HA mode changes, you need to synchronize the change to FusionSphere Openstack OM. Otherwise, external networks cannot access the floating IP address.
    1. After the template-based deployment is complete, use the floating IP addresses to log in to FusionSphere OpenStack OM to configure them.
    2. In the navigation tree, choose Resources > Compute Instances.
    3. Click the VM name.
    4. Choose Hardware > NIC.
    5. Click Configure Floating IP Address and enter the floating IP addresses used when configuring HA mode.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 17974

Downloads: 76

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