FusionCompute VMs

Production End and DR End

• In the FusionCompute VM environment, FusionCompute must be able to create datastores using the storage resources provided by FC SAN, IP SAN, Advanced SAN storage, Huawei Distributed Block Storage or NAS devices, create VMs, and provide clusters or hosts, ports group resources, and northbound interfaces available to users.
• In the FusionManager VM environment, FusionManager must be able to create VMs together with the FusionCompute environment and provide network and security group resources through VPC users.
• The FusionManager and FusionCompute environment configurations include the cascade configuration of FusionManager and FusionCompute, configuration of FusionManager providing network resources and security group resources, configuration of FusionCompute and storage arrays, and configuration of FusionCompute providing clusters or host resources and port group resources. For details, see the FusionSphere Virtualization Suite Product Documentation and FusionManager V100R006Cxx Product Documentation.

1. Check and configure the FusionCompute environments at the production end and the DR end.

   After FusionCompute is installed, you need to configure the FusionCompute environment, for example, configure clusters/hosts in FusionCompute, FusionCompute and storage arrays, and network resources in FusionCompute.

   

   All the following configurations are basic configurations of FusionCompute. For details, see the FusionSphere Virtualization Suite Product Documentation.

   1. Check the clusters and hosts in FusionCompute.
      1. Log in to FusionCompute as an administrator.
      2. Check whether any cluster or host resource is available. If no such a resource exists, create a resource.
      

      If you want to use a cluster to manage resources, ensure that the cluster contains available hosts.

   2. Check FusionCompute and storage arrays.
      1. Log in to FusionCompute as an administrator.
      2. Check whether any IP SAN, FC SAN, Advanced SAN, NAS or Huawei Distributed Block Storage storage is available. If no such storage system exists, add a storage system.
      3. In the host resources of FusionCompute, select ports to which you want to connect so that the service ports are added for service communication between the storage and FusionCompute.
   3. Optional: Check the storage plane configuration of the virtualized SAN.
      

      If there is no storage plane, you need to disable the function.

      1. Log in to FusionCompute as an administrator.
      2. On the menu, choose Resource Pools > Storage.
      3. Click VIMS Heartbeat Configuration, go to the VIMS Heartbeat Configuration page and check that the storage plane configuration of the virtualized SAN has been disabled.
   4. Check network resources in FusionCompute.
      1. Log in to FusionCompute as an administrator.
      2. Check whether any port group is available in the network pool and ensure that the network pool is associated with the host. If no such a port group exists, create a port group.
   5. Check interconnection users of FusionCompute.
      1. Log in to FusionCompute as an administrator.
      2. Check whether Interface interconnection user exists. If no such user exists, create one and ensure that roles of administrator are selected.

2. Check and configure the FusionManager environments at the production end and the DR end.

   Create a FusionCompute VM and install FusionManager on the VM. After installing FusionManager, install Tools and configure the FusionManager primary node.

   

   All the following configurations are basic configurations of FusionManager. For details, see the FusionManager V100R006Cxx Product Documentation.

   1. Configure virtual data center (VDC) and virtual private cloud (VPC) users.
      1. Log in to FusionManager as an administrator.
      2. Create a VDC and add users to it.
      3. Login as the newly created VDC user and add a VPC.
      4. Optional: In the VPC list, add routers to the desired VPC User for establishing a routed network.
      5. Add direct, internal, and routed networks to the desired VPC user.
      6. Create a security group for the desired VPC user.
   2. Open the northbound simple object access protocol (SOAP) interface.

      The northbound SOAP interface of the FusionManager VM is closed in default, you need to open the northbound SOAP interface to make the RD service normal.

      1. Use the PuTTY to log in to the FusionManager VM as galaxmanager user.
      2. Run TMOUT=0 to prevent the automatic exit of PuTTY due to timeout.
         

         After you run this command, the system continues to run when no operation is performed, resulting a risk. For security, run exit to exit the system.

      3. Run north soap open command to open the northbound SOAP interface.
      4. Run uportal restart command to restart the interface.

Production End

1. Check whether datastores have been created on FusionCompute at the production end.
   

   When creating a datastore, use a virtualized method and ensure that formatting has been performed.

   1. Log in to FusionCompute as an administrator.
   2. Check whether datastores have been created. If no datastore has been created, perform the following steps to create one:
   3. Click Add Data Store to go to the datastore addition page.
   4. Select IP SAN to create datastores.

2. Check whether VMs have been created on FusionCompute at the production end.
   • Check whether VMs have been created on FusionCompute.
     1. Log in to FusionCompute as an administrator.
     2. Choose Resource Pools > ManagementCluster > Host and check whether VMs that require DR protection have been created. If no VMs are created, follow the wizard to select an appropriate customized datastore to create VMs.
   • Check whether VMs have been created on FusionManager.
     1. Log in to FusionManager as the VPC user.
     2. Follow the wizard to create FusionManager VMs.
     3. Log in to FusionCompute as an administrator and migrate the newly created VMs to desired customized datastores.
   

   Ensure that virtualized datastores are configured for disaster recovery VMs.

Storage End

Table 1 describes the storage requirements of disaster recovery solutions.