Changes between Version 3 and Version 4 of Xen Zfs Handler Customization

Show
Ignore:
Timestamp:
12/04/08 21:55:32 (10 years ago)
Author:
aydan (IP: 69.134.122.47)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Xen Zfs Handler Customization

    v3 v4  
    1 The Xen Zfs handler must know the kernel which disk and kernel images to use when instantiating a virtual machine. The current version supports multiple disk images but requires that all of them share the same kernel image.  
     1Before you can use the Xen Zfs handler, it must be customized for your own installation. In particular, the handler must know which disk and kernel images to use when instantiating a virtual machine. The current version supports multiple disk images but requires that all of them share the same kernel image.  
    22 
    3 The kernel and disk images are controlled by a property file inside the xen zfs handler. You will need to checkout the handler from the repository and make the following changes. 
     3The kernel and disk images are controlled by a property file inside the xen zfs handler. You will need to check out the handler from the repository and make the following changes. 
    44 
    55{{{ 
    6 svn co https://geni-orca.renci.org/svn/orca/handlers/standard[trunk or the tag/branch you need] 
     6svn co https://geni-orca.renci.org/svn/orca/handlers/standard[trunk or the tag/branch you need] handler 
     7 
     8cd handler/resources/handlers/standard/xen/zfs 
     9 
     10touch user.properties 
     11 
    712}}} 
     13 
     14The last line creates an empty file called user.properties. This file overrides properties contained in build.properties (in the same directory). In particular, the properties that you need to override are: 
     15 
     16 * unit.os.kernel - path to the kernel image to use.  The path is relative to the '''software'' sub-directory within the installation directory of the Xen driver on each Xen VMM. You can also add an absolute path, but it should refer to a valid location on each Xen VMM. See this page for instructions how to deploy your kernel image to each Xen VMM. 
     17 
     18 * image.guid - guid of the default vm image. See this page for information about preparing an image to be used with the system 
     19 
     20 * vm.ssh.key - ssh private key to be used by the Xen driver to detect that a VM has completed booting. The location of the file is relative to the '''keys''' sub-directory within the installation directory of the Xen driver on each Xen VMM. See this page for instructions how to add your probe key to the xen driver's installation package.  
     21 
     22 
     23For our setup at RENCI/Duke, this file should look something like this: 
     24 
     25{{{ 
     26################################### 
     27# Kernel-related properties 
     28################################### 
     29 
     30# Name of the kernel file 
     31unit.os.kernel=vmlinuz-2.6.18-nfsroot 
     32 
     33################################### 
     34# Default Values 
     35################################### 
     36 
     37# Default image guid 
     38image.guid=b24aa725-f142-4c19-8e22-998bbf483f6a 
     39 
     40# ssh key to use to determine when the vm has finished booting 
     41vm.ssh.key=orca_rsa 
     42}}}