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:
The SAN is auto-mounted.
For an auto-mounted SAN, follow the setup steps noted in Deploying a VM to the NAS Repository in setting the facts for identifying the paths.
For more information on facts, see
Defining Values for Grid Objects in the Novell ZENworks Orchestrator 1.3 Developer Guide and Reference.
The Orchestrator Server managing the connection requires additional information to have the SAN as an available repository for VM images.
For example, the physical disks are on the SAN, but the configuration file is on local storage. The additional information is necessary for ZENworks Orchestrator to know how to bind or connect the SAN disk on the VM host.
Perform the tasks in the following sections, as applicable:
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:
On the ZENworks Orchestrator Server, open YaST2.
Clickin the section.
Select theoption in the section. Select the tab and set up global authentication if needed. If you are not using authentication, select . Select the tab.
There should be a default iSCSI target in thelist. Delete this example target.
Specify the path to the created partition, file, or VM Image.
Specify any authentication information for incoming or outgoing stored VMs, or select.
Select. A dialog box appears, asking you to restart the service.
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.
To create a Xen configuration file and start the VM:
Enter $virt-manager at a command line prompt.
Either create a new VM or select.
Enter the new device file location as found in the hwinfo -disk command output.
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:
Ensure that the new VM appears on the tree.
Name the new repository.
Add the xen30 provisioning adapter.
For information on provisioning adapters, see Section 4.0, Provisioning Virtual Machines.
Select the new repository from the list.
In the large window on the right, fill in the following information:
Type = SAN
In thesection, fill in the following information:
SAN Type = iSCSI
SAN Vendor = "iqn"
Selectfrom the toolbar icon or the file menu.
Click the Resources selection in the tree.
Select the new VM.
On the right selectand select the Browse button . find the Virtual Disks Layout
Click the drop-down menu to change the information.
iqn: iqn.2007-05.lab.cimlocation: phy:/dev/sdbmoveable: left uncheckedrepository: iscsisize: 0 (untouched)
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.
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
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.