Changes

Qemu native GlusterFS integration

449 bytes added, 13:33, 20 December 2013
/* GlusterFS */
= GlusterFS =
 
'''NOTE: this got implemented in stoney cloud 1.2.10.4 and you should not have to perform the following steps.'''
Since we run Qemu as unprivileged user we have to permit access to GlusterFS from an unprivileged port as well as an unprivileged user.
<syntaxhighlight lang='xml'>
<disk type='network' device='disk'>
<driver name='qemu' type='qcow2' cache='none'/>
<source protocol='gluster' name='virtualization/vm-templates/5b77d2f6-061f-410c-8ee7-9e61da6f1927/f3d87cf9-f7d8-4224-b908-cc9fc6c8fcd4.qcow2'>
<host name='10.1.120.11'/>
= LDAP =
'''current'''<pre> <disk type='file' device='disk'> <driver nameCurrent ='qemu' type='qcow2' cache='none'/> <source file='/var/virtualization/vm-templates/5b77d2f6-061f-410c-8ee7-9e61da6f1927/f3d87cf9-f7d8-4224-b908-cc9fc6c8fcd4.qcow2'/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk></pre>
<syntaxhighlight lang='ldif'>
dn: sstDisk=vda,ou=devices,sstVirtualMachine=ece1eab1-4a9e-4729-bfc1-59d9f01550a5,ou=virtual machines,ou=virtualization,ou=services,dc=foss-cloud,dc=org
</syntaxhighlight>
'''new'''<syntaxhighlight lang='xml'> <disk type='network' deviceNew ='disk'> <driver name='qemu' type='qcow2'/> <source protocol='gluster' name='virtualization/vm-templates/5b77d2f6-061f-410c-8ee7-9e61da6f1927/f3d87cf9-f7d8-4224-b908-cc9fc6c8fcd4.qcow2'> <host name='10.1.120.11'/> </source> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk></syntaxhighlight> 
<syntaxhighlight lang='ldif'>
dn: sstDisk=vda,ou=devices,sstVirtualMachine=ece1eab1-4a9e-4729-bfc1-59d9f01550a5,ou=virtual machines,ou=virtualization,ou=services,dc=foss-cloud,dc=org
objectclass: top
objectclass: sstVirtualizationVirtualMachineDisk
'''sstType: network'''-> instead of file
sstDevice: disk
sstDriverName: qemu
sstDriverCache: none
sstVolumeName: 3aa376a5-6d09-442b-8662-425de888385b
sstSourceFilesstSourceProtocol: gluster -> newsstSourceName: /var/virtualization/vm-persistent/0f83f084-8080-413e-b558-b678e504836e/3aa376a5-6d09-442b-8662-425de888385b.qcow2-> new attributesstSourceHostName: 10.1.120.11 -> new and multi-valued attribute (for later use, currently, only one entry is supported)
sstDisk: vda
sstTargetBus: virtio
sstVolumeCapacity: 32212254720
</syntaxhighlight>
 
== Notes for Configuration in LDAP ==
=== Persistent Storage Pool ===
<syntaxhighlight lang='ldif'>
sstStoragePool=0f83f084-8080-413e-b558-b678e504836e,ou=storage pools,ou=virtualization,ou=services,o=stepping-stone,c=ch
</syntaxhighlight>
 
==== file ====
<syntaxhighlight lang='ldif'>
sstStoragePoolURI: file:///var/virtualization/vm-persistent/0f83f084-8080-413e-b558-b678e504836e
</syntaxhighlight>
 
==== gluster ====
<syntaxhighlight lang='ldif'>
sstStoragePoolURI: gluster:///tier1-storage-node-01/gv-tier1-vm-01/vm-persistent/0f83f084-8080-413e-b558-b678e504836e
</syntaxhighlight>
 
=== Questions / Open Issues ===
* Where do we store the following configuration values?
** Possible storage pool types: file, gluster (others could follow)
** Host names or ip addresses (in case of gluster): tier1-storage-node-01
** Mount point: /var/virtualization/vm-persistent/ or /gv-tier1-vm-01/vm-persistent/
** Storage Pool Names: 0f83f084-8080-413e-b558-b678e504836e
** Where and how to we store the information, that we have slow and fast storage?
= Test =
Bureaucrat, administrator
425
edits