OpenNebula

Hello,

We have a two VDC OpenNebula running and we have an issue regarding to datastores.

Here is the global setup:

• we use qcow2 TM for VM images and SYSTEM datastores
• we use shared TM for ISO images
• we use SAN storage on the physical machines and expose it to the frontend through NFS
• ONE frontend is a VM running on the nebula physical hosts (corosync/pacemaker)

The SAN storage is allocated like this:

• a SAN storage is common to all clusters, mounted under /var/lib/one/datastores (GFS2), to store VM images and ISOs common to all VDCs
• a VDC has a dedicated SAN storage for its stored VM images (DS ID 104) and running VMs (DS ID 103), mounted under /var/lib/one/datastores/<VDC-NAME> only for the hosts of the cluster used by this VDC, it's NFS exported to the frontend which mount it under the same path

The dedicated VDC datastores have their BASE_PATH set to /var/lib/one/datastores/<VDC-NAME>.

Unfortunately, this parameter seems not honored by the qcow2 TM, neither with the libvirt XML generator.

• Log from qcow2 TM: the path on nebula5 should be /var/lib/one//datastores/<VDC>/103/30901/disk.0
  

  oneadmin@one-frontend:~$ cat vms/30901/transfer.0.prolog 
  CLONE qcow2 one-frontend:/var/lib/one/datastores/envole/104/f4735e653caf14377c016db8ecf16a29 nebula5:/var/lib/one//datastores/103/30901/disk.0 30901 104
  CONTEXT qcow2 /var/lib/one/vms/30901/context.sh nebula5:/var/lib/one//datastores/103/30901/disk.1 30901 103
  

• Log for the VM: the deployement file path should be /var/lib/one//datastores/<VDC>/103/30901/deployment.0
  

  Wed Feb  3 10:50:11 2016 [Z0][VM][I]: New state is ACTIVE
  Wed Feb  3 10:50:11 2016 [Z0][VM][I]: New LCM state is PROLOG
  Wed Feb  3 10:50:13 2016 [Z0][VM][I]: New LCM state is BOOT
  Wed Feb  3 10:50:13 2016 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/30901/deployment.0
  Wed Feb  3 10:50:13 2016 [Z0][VMM][I]: ExitCode: 0
  Wed Feb  3 10:50:13 2016 [Z0][VMM][I]: Successfully execute network driver operation: pre.
  Wed Feb  3 10:50:13 2016 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/deploy '/var/lib/one//datastores/103/30901/deployment.0' 'nebula5' 30901 nebula5
  Wed Feb  3 10:50:13 2016 [Z0][VMM][I]: error: Failed to create domain from /var/lib/one//datastores/103/30901/deployment.0
  Wed Feb  3 10:50:13 2016 [Z0][VMM][I]: error: Failed to open file '/var/lib/one//datastores/103/30901/disk.0': No such file or directory
  Wed Feb  3 10:50:13 2016 [Z0][VMM][E]: Could not create domain from /var/lib/one//datastores/103/30901/deployment.0
  Wed Feb  3 10:50:13 2016 [Z0][VMM][I]: ExitCode: 255
  Wed Feb  3 10:50:13 2016 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
  Wed Feb  3 10:50:13 2016 [Z0][VMM][E]: Error deploying virtual machine: Could not create domain from /var/lib/one//datastores/103/30901/deployment.0
  Wed Feb  3 10:50:13 2016 [Z0][VM][I]: New LCM state is BOOT_FAILURE
  

• libvirt XML definition of the VM: the <source file= should use /var/lib/one//datastores/<VDC>/103/30901/
  

  <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
      <name>one-30901</name>
      <vcpu>2</vcpu>
      <cputune>
          <shares>205</shares>
      </cputune>
      <memory>2097152</memory>
      <os>
          <type arch='x86_64'>hvm</type>
          <boot dev='hd'/>
      </os>
      <devices>
          <emulator>/usr/bin/qemu-system-x86_64</emulator>
          <disk type='file' device='disk'>
              <source file='/var/lib/one//datastores/103/30901/disk.0'/>
              <target dev='vda'/>
              <driver name='qemu' type='qcow2' cache='writeback' io='native'/>
          </disk>
          <disk type='file' device='cdrom'>
              <source file='/var/lib/one//datastores/103/30901/disk.1'/>
              <target dev='hda'/>
              <readonly/>
              <driver name='qemu' type='raw'/>
          </disk>
          <interface type='bridge'>
              <virtualport type='openvswitch'/>
              <source bridge='rectorat'/>
              <mac address='02:00:ac:1b:07:23'/>
              <model type='virtio'/>
          </interface>
          <graphics type='vnc' listen='0.0.0.0' port='36801' keymap='fr'/>
          <input type='tablet' bus='usb'/>
      </devices>
      <features>
          <acpi/>
          <apic/>
      </features>
      <metadata>
          <system_datastore>/var/lib/one//datastores/103/30901</system_datastore>
      </metadata>
  </domain>
  
  

To work around this, we created two simlinks:

• /var/lib/one/datastores/103 pointing to /var/lib/one//datastores/<VDC>/103/
• /var/lib/one/datastores/104 pointing to /var/lib/one//datastores/<VDC>/104/

Regards.