5.5 Deploying a VM to the SAN Repository

The Storage Area Network (SAN) Repository is a single storage server that can be accessed by multiple machines.

NOTE:This section refers to an iSCSI SAN, not a Fibre Channel SAN.

There are two ways to access VMs on a SAN:

Perform the tasks in the following sections, as applicable:

5.5.1 Setting Up the SAN

For information on setting up an iSCSI target, see Setting Up an iSCSI Target in the SUSE Linux Enterprise Server 10 Installation and Administration Guide.

For information on setting up an iSCSI Initiator, see Configuring iSCSI Initiator in the SUSE Linux Enterprise Server 10 Installation and Administration Guide.

You need to have one of the following for the setup:

  • On the server, create a file or partition that has sufficient size for a VM image.

  • Have or select a VM disk image.

You can set up the iSCSI target according to the linked directions above, or you can use a VM image as your target. With the addition of the optional instructions on installing on a VM Image are included here.

NOTE:If the iSCSI Target is not installed, you are prompted to install the iscsitarget package.

To install the target (iSCSI Server) and complete setting up the SAN:

  1. On the ZENworks Orchestrator Server, open YaST2.

  2. Click iSCSI Target in the Miscellaneous section.

  3. Select the When Booting option in the Service Start section. Select the Global tab and set up global authentication if needed. If you are not using authentication, select No Authentication. Select the Targets tab.

  4. There should be a default iSCSI target in the Targets list. Delete this example target.

  5. Click Add.

  6. Click Add again.

  7. Select Type=fileio.

  8. Specify the path to the created partition, file, or VM Image.

  9. Click OK.

  10. Click Next.

  11. Specify any authentication information for incoming or outgoing stored VMs, or select No Authentication.

  12. Select Finish. A dialog box appears, asking you to restart the service.

  13. Click Yes.

  14. After you have installed and configured your iSCSI Target and Initiator, run $hwinfo -disk to see something similar to the following:

    Model: "IET VIRTUAL-DISK"  Vendor: "IET"  Device: "VIRTUAL-DISK"  Revision: "0"  Driver: "sd"  Device File: /dev/sdb (/dev/sg2)
    

    NOTE:Notice the virtual disk and the new device file that appear. This shows that the iSCSI initiator has established a connection and is able to attach to the file, partition, or VM image. If this information does not appear, troubleshoot the iSCSI connection and setup.

  15. To create a Xen configuration file and start the VM:

    1. Enter $virt-manager at a command line prompt.

    2. Either create a new VM or select I have a disk or disk image.

    3. Select Disks.

    4. Enter the new device file location as found in the hwinfo -disk command output.

5.5.2 Configuring the iSCSI SAN in ZENworks Orchestrator

After you have set the SAN up outside of ZENworks Orchestrator, launch the ZENworks Orchestrator Console.

Perform the following steps if your iSCSI SAN is a VM Image:

  1. Click Provision > Discover VM Images.

  2. Ensure that the new VM appears on the tree.

  3. Right-click Repositories and select New Repository.

  4. Name the new repository.

  5. Add the xen30 provisioning adapter.

    For information on provisioning adapters, see Section 4.0, Provisioning Virtual Machines.

  6. Click Create.

  7. Select the new repository from the list.

  8. In the large window on the right, fill in the following information:

    • Type = SAN

    In the SAN Specific Configuration section, fill in the following information:

    • SAN Type = iSCSI

    • SAN Vendor = "iqn"

  9. Select Save from the toolbar icon or the file menu.

  10. Click the Resources selection in the tree.

  11. Select the new VM.

  12. On the right select Info/Groups and select the Browse button (…). find the Virtual Disks Layout

  13. Click the drop-down menu to change the information.

    For example:

    iqn: iqn.2007-05.lab.cimlocation: phy:/dev/sdbmoveable: left uncheckedrepository: iscsisize: 0 (untouched)
    
  14. Test the new setup by provisioning a VM.

    For information, see Provisioning Virtual Machines in the Novell ZENworks Orchestrator 1.3 Developer Guide and Reference.

  15. Check the Job Log for bind/unbind operations similar to this:

    iscsi unbind(iqn=iqn.2007-05.lab.cim,u=None,pw=None,auth=None) Running 'iscsiadm -m node' rslt= 0 Found record for iqn: e375f3 Run cmd: iscsiadm -m node -r e375f3 -urslt= 0unbind was successful
    

5.5.3 Virtual Repository

A Virtual Repository is where ZENworks Orchestrator assumes the VM store is handled by the underlying VM technology. For example, the Virtual Repository is used by the Virtual Center adapter because Virtual Center is managing the VM storage.