File README-AFTER-SETUP of Package opennebula-driver-hyperv3

File README-AFTER-SETUP of Package opennebula-driver-hyperv3 (Revision 6d3a2f4d1865c24099e89921cfff347e)

Currently displaying revision 6d3a2f4d1865c24099e89921cfff347e, show latest

# After the installation, please add the following to your oned.conf file
# and restart OpenNebula to activate the Hyper-V Drivers Addon

IM_MAD = [
      name       = "im_hyperv",
      executable = "one_im_sh",
      arguments  = "-r 0 -t 15 hyperv" ]
 
VM_MAD = [
    name       = "vmm_hyperv",
    executable = "one_vmm_sh",
    arguments  = "-t 15 -r 0 hyperv",
    default    = "vmm_exec/vmm_exec_kvm.conf",
    type       = "xml" ]
 
TM_MAD = [
    name       = "tm_hyperv",
    executable = "one_tm",
    arguments  = "tm_hyperv/tm_hyperv.conf" ]

We will also need to configure the TM so it knows where the share storage is mounted in /etc/one/tm_hyperv/tm_hypervrc:

SMB_MOUNT=<MOUNT POINT>

Change <MOUNT POINT> to the path previously used to mount the Windows shared directory.

We will also need to add a couple of parameters to /etc/one/defaultrc:

ONE_HYPERV_PROXY=<PROXY>
	ONE_HYPERV_VMDIR=<WINDOWS SHARE>

PROXY: this is the name of the Windows frontend sever that has the sshd running.
    WINDOWS SHARE: the windows path to access the shared storage

For example, if our server is called FRONTEND and the share is called vms the configuration will be:

ONE_HYPERV_PROXY=FRONTEND
	ONE_HYPERV_VMDIR=\\\\FRONTEND\\vms

See http://wiki.opennebula.org/hyperv:documentation for detailed configuration steps.