Deploying IBM StoredIQ on Microsoft Hyper-V

As an alternative to installing on an ESX server, the IBM® StoredIQ® gateway, data server, and application stack can be installed on Microsoft Hyper-V. This option is not supported for the Elasticsearch virtual appliance.

Complete these steps for the gateway, the data server, and the AppStack. The following procedure describes the steps for the AppStack but is similar for the gateway and the data server. Differences for these components are explicitly called out in a step.

1. Extract the vmdk file from the OVA.
   1. Download the OVA.
   2. Extract the contents of the OVA by using 7-zip for Windows or tar for the Linux operating system.
      Each IBM StoredIQ OVA contains multiple vmdk files that are consecutively numbered. For the AppStack, for example, the file names look like this:

      • xxxxxxx0.vmdk
      • xxxxxxx1.vmdk
      • xxxxxxx2.vmdk
   3. Delete everything except the vmdk files when the OVA extraction is complete.
2. Convert all vmdk files to Microsoft Hyper-V vhd files.
   Use this naming convention for the converted files: component-diskn.vhd

   component is as for the AppStack, gw for the gateway, and ds for the data server. n equals the number of the vmdk file you're converting.

   For instructions about converting vmdk files to vhd files, see the following links:

   • Use Microsoft Virtual Machine Converter
   • Using qemu-img
3. Build a virtual machine by using the first vhd file.
   For the AppStack, for example, the file to use is as-disk0.vhd.
   1. Select New Virtual Machine > Next from Hyper-V Manager.
   2. Enter the name of the virtual machine in the Specify Name and Location window and click Next.
   3. Select Generation of the machine in the Specify Generation window.
   4. Enter the startup memory in the Assign Memory window.
   5. Select the correct network in the Configure Network window and click Next.
   6. Select Use an existing virtual hard disk in the Connect Virtual Hard Disk window. Search the disk location, select one of the primary disks, and then click Next.
   7. Click Finish.
   8. Do not start the virtual machine yet, but add the remaining vhd files to the virtual machine by updating the VM settings.
      For example, add the as-disk1.vhd and as-disk-2.vhd files for the AppStack. You must add the files in the sequence indicated by the number assigned to the vmdk file.
4. For the gateway or a data server, start the virtual machine.
   Gateway and data servers should then be in the initial boot process. Complete their respective configuration as described in Configuring the gateway and Configuring the data server. For gateway and data server, you can skip the rest of the procedure.

   For the AppStack, continue with step 5.

5. Start the virtual machine in rescue mode.
   Errors might occur during the boot process. In this case, keep entering exit until you enter the initial boot process for the AppStack.
6. Complete the AppStack configuration as described in Configuring the application stack.
   After the configuration is complete, the virtual machine is automatically restarted. During this boot process, make sure the machine is started in rescue mode.
7. Log in to the AppStack.
8. Check the status of the AppStack services by entering the following command:

   systemctl list-dependencies appstack.target

   All service should be green. However, if you didn't enable secure gateway communication, appstack-stunnel.service will be red.

9. Check the /var/siq/log/nucleus.log file.
   Wait until you see the message All services are ready before you continue.
10. Rebuild the initial RAM disk images for preloading modules by using this command:

    dracut -f

11. Restart the virtual machine in regular mode.