[ovirt-devel] Interacting with VDSM storage without oVirt Engine

[Hayley Swimelar]

Hello all,

Like the title says, I need to work with VDSM's storage layer without 
involving the engine.

Presently, I'm testing this with NFS domains and have been able to use 
vdsClient to create, attach, and activate a new storage domain, but I 
have not been able to create a new image or volume.

Here are the commands I ran to get to this step, starting with a nfs 
volume already mounted on the machine I ran the commands on.

----
vdsClient -s host_name createStorageDomain 1 
97338d5c-9b6f-1859-b827-e977ed082e53 cli_domain storage_server:/data

vdsClient -s host_name attachStorageDomain 
97338d5c-9b6f-1859-b827-e977ed082e53 00000001-0001-0001-0001-00000000033c

vdsClient -s host_name activateStorageDomain 
97338d5c-9b6f-1859-b827-e977ed082e53 00000001-0001-0001-0001-00000000033c

vdsClient -s frodo createVolume 97338d5c-9b6f-1859-b827-e977ed082e53 
00000001-0001-0001-0001-00000000033c 
0288f410-71f1-4b7d-bdb7-e815a93e34ef 53690000000 5 1 2 
96d7726c-6969-40a5-84bd-0925496b6051 cli_volume
----

The last command outputs a new UUID, but there is nothing under
/rhev/data-center/00000001-0001-0001-0001-00000000033c/97338d5c-9b6f-1859-b827-e977ed082e53/images/ 
directory.

If I pass createVolume an existing image/storage domain UUID, the 
command still outputs a new UUID, but nothing changes under the images 
directory.

Is there a step that I am missing somewhere in this process?

-- 
Hayley Swimelar
LINBIT | Keeping the Digital World Running
DRBD — Corosync — Pacemaker
+1-503-573-1262 x212