1. Subscriber Data Server Cloud Installation Guide
  2. Application Installation
  3. Configure Virtual Machines

2.5 Configure Virtual Machines

The section provides procedure to create virtual machines.

Note:

Repeat this procedure for each of the SDS VM guests (NOAMs, DR Servers, SOAMs, Query servers, and DPs) that need to be created.
Pre-requisites:
Provide values for the following variables:
  • <OVA VM name_vm_vm>
  • <ServerPool name>
  • <VM name>
  • <OVM network ID for XMI>
  • <OVM network ID for IMI>
  • <URL for OVM GUI>
  • <VM IP in XMI> from the NAPD
  • <Gateway for XMI> from the NAPD
  • <NetMask for XMI> from the NAPD
  • <VM ID>
  • <vCPUs Production>
  • <VNIC 1 ID>
  • <interface name> defined in DSR Cloud Benchmarking Guide
  1. To create a VM for each guest from the VM in the OVA virtual appliance, using OVM-M CLI perform the following steps:
    1. Retrieve the site-specific text for these variables.
      <OVA VM name_vm_vm> = 11145510c0_vm_vm
    2. Add the respective values for <OVA VM name> in the command.
      OVM> createVmFromVirtualApplianceVm VirtualApplianceVm name=<OVA VM name>
      For example:
      OVM> createVmFromVirtualApplianceVm VirtualApplianceVm name=11145510c0_vm_vm
    3. Run the command and validate success.
      createVmFromVirtualApplianceVm VirtualApplianceVm name=11145510c0_vm_vm
Status: Success
Time: 2017-04-18 16:02:09,141 EDT
JobId: 1492545641976
Data: id: 0004fb00000600004a0e02bdf9fc1bcd name:DSR-8.6.0.0.0_95.14.0.ova_vm
    4. Examine the screen results to find site-specific text for variables in the required locations.
    5. Add the respective values for these variables.
      <VM ID> = 0004fb00000600004a0e02bdf9fc1bcd
  2. Add the VM to the server pool, using OVM-M CLI.
    1. Retrieve the site-specific text for these variables.
      <VM ID> = 0004fb00000600004a0e02bdf9fc1bcd
<ServerPool name> = XLab Pool 01
    2. Add the respective values for <VM ID> and <ServerPool name> into the command.
      OVM> add Vm id=<VM id> to ServerPool name=”<ServerPool name>”
      For example:
      OVM> add Vm id=0004fb00000600004a0e02bdf9fc1bcd to ServerPool name="XLab Pool 01"
    3. Run the command and validate success.
      add Vm id=0004fb0000060000beb93da703830d3c to ServerPool name="XLab Pool 01"
Status: Success
Time: 2017-04-19 21:05:10,950 EDT
JobId: 1492650310802

      Note:

      Refer to the Server Pool section for more information.
  3. To apply required profile or resources, edit VM using OVM-M CLI.
    1. Get the site-specific text for these variables.
      <VM ID> = 0004fb00000600004a0e02bdf9fc1bcd
<VM name > = na-sdsnoam-na-2a
<vCPUs Production> = 4

      Note:

      Refer to DSR Cloud Benchmarking Guide for recommended resource.
      VM Name vCPUs Lab RAM (GB) Lab vCPUs Production RAM (GB) Production Storage (GB) Lab and Production
      Type of guest host # # # # #
    2. Add the respective values for <VM ID>, <VM name>, and <vCPUs Production> into the command.
      OVM> edit Vm id=<VM id> name=<VM name> memory=6144 memoryLimit=6144 cpuCountLimit=<vCPUs Production> cpuCount=<vCPUs Production> domainType=XEN_HVM description="<VM name>"
      For example:
      OVM> edit Vm id=0004fb00000600004a0e02bdf9fc1bcd name=na-sdsnoam-na-2a memory=6144 memoryLimit=6144 cpuCountLimit=4 cpuCount=4 domainType=XEN_HVM description="na-sdsnoam-na-2a"
    3. Run the command and validate success.
      edit Vm id=0004fb00000600004a0e02bdf9fc1bcd name=na-sdsnoam-na-2a memory=6144 memoryLimit=6144 cpuCountLimit=4 cpuCount=4 domainType=XEN_HVM description="na-sdsnoam-na-2a"
Status: Success
Time: 2017-04-18 17:55:25,645 EDT
JobId: 1492552525477

      Now, the VM has a name and resources.

  4. Determine VNIC ID, using OVM-M CLI.
    1. Retrive the site-specific text for this variable.
      <VM name> = na-sdsnoam-na-2a
    2. Add the respective value for <VM name> in the command.
      OVM> show Vm name=<VM name>
      For example:
      OVM> show Vm name=na-nsdsoam-na-2a
    3. Run the command and validate success.
      Status = Stopped
Memory (MB) = 6144
Max. Memory (MB) = 6144
Processors = 4
Max. Processors = 4
Priority = 50
Processor Cap = 100
High Availability = No
Operating System = Oracle Linux 6
Mouse Type = PS2 Mouse
Domain Type = Xen HVM
Keymap = en-us
Start Policy = Use Pool Policy
Origin = http://10.240.155.70/iso/SDS/8.6/ova/SDS-8.6.0.0.0_95.14.0.ova
Disk Limit = 4
Huge Pages Enabled = No
Config File Absolute Path = 192.168.5.5:/storage/ovm01/repository/VirtualMachines/0004fb00000600004a0e02bdf9fc1bcd/vm.cfg
Config File Mounted Path = /OVS/Repositories/0004fb0000030000da5738315337bfc7/VirtualMachines/0004fb00000600004a0e02bdf9fc1bcd/vm.cfg
Server Pool = 0004fb00000200009148c8926d307f05 [XLab Pool 01]
Repository = 0004fb0000030000da5738315337bfc7 [XLab Utility Repo01] Vnic 1 = 0004fb0000070000091e1ab5ae291d8a [Template Vnic]
VmDiskMapping 1 = 0004fb0000130000a1996c6074d40563 [Mapping for disk Id (79def426328a4127b5bf9f7ae53d3f48.img)]
VmDiskMapping 2 = 0004fb00001300002db3d4b67a143ab5 [Mapping for disk Id (EMPTY_CDROM)]
Restart Action On Crash = Restart
Id = 0004fb00000600004a0e02bdf9fc1bcd [na-sdsnoam-na-2a]
Name = na-sdsnoam-na-2a
Description = na-sdsnoam-na-2a
Locked = false
DeprecatedAttrs = [Huge Pages Enabled (Deprecated for PV guest)]
    4. Examine the screen results to find site-specific text for variables in the required locations.
    5. Add the respective values for these variables.
      <VNIC 1 ID> = 0004fb0000070000091e1ab5ae291d8a
  5. Determine network interfaces for the type of guest host.

    Note:

    Refer to the DSR Cloud Benchmarking Guide, for further information on which network interfaces need to be configured for each guest type.
    The referring table sample:
      OAM (XMI) Local (IMI)
    Type of guest host eth# eth#

    Note:

    The VNICs must be created in the correct order so that the interfaces are associated with the correct network.
  6. Attach XMI VNIC, if required by guest host type, using the OVM-M CLI.
    1. Retreive the site-specific text for these variables:
      <VNIC 1 ID> = 0004fb0000070000091e1ab5ae291d8a
<OVM network ID for XMI> = 10345112c9
    2. Add the respective values for <VNIC 1 ID> and <OVM network ID for XMI> in the command:
      OVM> add Vnic ID=<Vnic 1 ID> to Network name=<OVM network ID for XMI>
      For example:
      OVM> add Vnic ID=0004fb0000070000091e1ab5ae291d8a to Network name=10345112c9
    3. Run the command and validate success.
      add Vnic id=0004fb0000070000091e1ab5ae291d8a to Network name=10345112c9
Status: Success
Time: 2017-04-19 19:08:59,496 EDT
JobId: 1492643339327
  7. To create and attach IMI VNIC, if required by guest host type, using OVM-M CLI, perform the following steps:
    1. Retrive the site-specific text for these variables:
      <VM name> = na-sdsnoam-na-2a
<OVM network ID for IMI> = 102e89a481
    2. Add the respective values for <OVM network ID for IMI> and <VM name> into the command:
      OVM> create Vnic network=<OVM network ID for IMI> name=<VM name>-IMI on VM name=<VM name>
      For example:
      OVM> create Vnic network=102e89a481 name=na-sdsnoam-na-2a-IMI on Vm name=na-sdsnoam-na-2a
    3. Run the command and validate success.
      create Vnic network=102e89a481 name=na-sdsnoam-na-2a-IMI on Vm name=na-sdsnoam-na-2a
Status: Success
Time: 2017-04-19 21:21:57,363 EDT
JobId: 1492651317194
Data:
id:0004fb00000700004f16dc3bfe0750a7 name:na-sdsnoam-na-2a-IMI
  8. To start VM, using OVM-M CLI, perform the following steps:
    1. Retrieve the site-specific text for this variable:
      <VM name> = na-sdsnoam-na-2a
    2. Add the respective values for <VM name> in the command.
      OVM> start Vm name=<VM name>
      For example:
      OVM> start Vm name=na-sdsnoam-na-2a
    3. Run the command and validate success.
      start Vm name=na-sdsnoam-na-2a
Status: Success
Time: 2017-04-19 19:29:35,376 EDT
JobId: 1492644568558
  9. To configure the XMI network interface for this VM, using OVM-M GUI, perform the following steps:
    1. Retreive the site-specific text for these variables:
      <URL for OVM GUI> = https://100.64.62.221:7002/ovm/console/faces/resource/resourceView.jspx
<interface name> = from the table in DSR Cloud Benchmarking Guide
<VM IP in XMI> = from the NAPD
<Gateway for XMI> = from the NAPD
<NetMask for XMI> = from the NAPD
    2. Access the CLI of the console for the VM, by logging into the OVM-M GUI by entering the <URL for OVM GUI> in a browser.
    3. Navigate to the Servers and VMs tab.
      1. Expand and select the <ServerPool name>.
      2. From the Perspective list, select Virtual Machines.
      3. Select the <VM name> from the rows listed and click the Launch Console icon.
      4. In the Console window, log into the VM as the admusr.
    4. Add the respective values for <interface name>, <VM IP in XMI>, <Gateway for XMI>, and <NetMask for XMI> into the commands.
      Command for Netmask XMI:
      $ sudo netAdm set --onboot=yes --device=<interface name> --address=<VM IP in XMI> --netmask=<NetMask for XMI>
      For example:
      $ sudo netAdm set --onboot=yes --device=eth0 --address=10.75.158.189 --netmask=255.255.255.128
      Command for Gateway XMI:
      $ sudo netAdm add --route=default --device=<interface name> –gateway=<Gateway for XMI>
      For example:
      $ sudo netAdm add --route=default --device=eth0 --gateway=10.75.158.129

      Note:

      Run the above command, to validate success.
    5. Verify network connectivity, by pinging Gateway of network.
      $ ping –c3 <Gateway for XMI>
    6. Reboot the VM.
      $ sudo init 6
      It takeS approximately 5 minutes for the VM to complete rebooting.
    The new VM should now be accessible using both network and console.