[vdsm] [RFC] GlusterFS domain specific changes
We are developing a GlusterFS server translator to export block devices as regular files to the client. Using block devices to serve VM images gives performance improvements, since it avoids some file system bottlenecks in the host kernel. Goal is to use one block device(ie file at the client side) per VM image and feed this file to QEMU to get the performance improvements. QEMU will talk to glusterfs server directly using libgfapi. Currently we support only exporting Volume groups and Logical Volumes. Logical volumes are exported as regular files to the client. In GlusterFS terminology a volume capable of exporting block devices is created by specifying the 'Volume Group' (ie VG in Logical Volume management). Block Device translator(BD xlator) exports this volume group as a directory and LVs under it as regular files. In the gluster mount point creating a file results in creating a logical volume, removing a file results in removing logical volume etc. When a GlusterFS volume enabled with BD xlator is used, directory creation in that gluster mount path is not supported because directory maps to Volume groups in BD xlator. But it could be an issue in VDSM environment when a new VDSM volume is created for GlusterFS domain, VDSM mounts the storage domain and creates directories under that and create files for vm image and other uses (like meta data). Is it possible to modify this behavior in VDSM to use flat structure instead of creating directories and VM images and other files underneath it? ie for GlusterFS domain with BD xlator VDSM will not create any directory and only creates all required files under the mount point directory itself. Note: Patches to enable exporting block devices as regular files are available in Gluster Gerrit system http://review.gluster.com/3551 ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] minutes: today's call
On 07/25/2012 04:36 PM, Ryan Harper wrote: * Eyal Edri ee...@redhat.com [2012-07-18 11:59]: I'm in favor on doing it next monday. (not too healthy to do upgrades before the weekend...). We'll need to send email to rhev-devel + qe for an estimated downtime of 1 hour for gerrit.eng.lab.tlv.redhat.com. Any update? I've sent an update earlier today to infra that i'm planning to upgrade gerrit to 2.4.2 coming sunday. after a few days of a clean upgrade, I'll do the patched version of it. Eyal. - Original Message - From: Itamar Heim ih...@redhat.com To: Ryan Harper ry...@us.ibm.com Cc: Dan Kenigsberg dan...@redhat.com, Adam Litke a...@us.ibm.com, Anthony Liguori aligu...@us.ibm.com, VDSM Project Development vdsm-devel@lists.fedorahosted.org, Eyal Edri ee...@redhat.com, Attila Darazs adar...@redhat.com, Moran Goldboim mgold...@redhat.com Sent: Wednesday, July 18, 2012 7:48:01 PM Subject: Re: [vdsm] minutes: today's call On 07/18/2012 06:24 PM, Ryan Harper wrote: * Itamar Heim ih...@redhat.com [2012-05-16 10:26]: On 05/16/2012 06:11 PM, Dan Kenigsberg wrote: On Wed, May 16, 2012 at 09:43:57AM -0500, Ryan Harper wrote: * Dan Kenigsbergdan...@redhat.com [2012-05-07 05:42]: On Mon, Apr 23, 2012 at 05:52:13PM +0300, Dan Kenigsberg wrote: On Mon, Apr 23, 2012 at 07:34:14AM -0500, Adam Litke wrote: On Mon, Apr 23, 2012 at 04:17:18AM -0400, Ayal Baron wrote: Hi all, I would like to discuss the following on today's call: 1. Gerrit vs. mailing list Gerrit is an inhibiter for some contributors. One approach to solve this improve gerrit: - Gerrit should send the patch when it notified of a change. This may attract more reviewers. I'm happy to inform that Gal has sent a patch for this to upstream gerrit: https://gerrit-review.googlesource.com/#/c/34861/ Add unified diff to newchange mail template. Any eta on getting the gerrit notifications of changes to include the full patch in the email? You can +1 them in googlesource, maybe it helps ;-) indeed, please help push them upstream... https://gerrit-review.googlesource.com/#/c/34861/ https://gerrit-review.googlesource.com/#/c/34862/ I'm definitely happy to see notification on new posts and changes; helps me see what new activity is happening, but I'd really enjoy seeing the the patch series attached (via threading) as well. Itamar, I know Red Hat hates to do it, but can we take these patches to ovirt's gerrit before they are accepted upstream? yes we can. after i'll upgrade it to 2.3, which i prefer to do after i return from PTO in case there are some issues with the upgrade. so ETA end of the month for clean upgrade to 2.3, then after we see all is ok, let's say another week to upgrade to the version with these patches. It's about 6 weeks later. Dan's been asking for more review in vdsm; I know that I'd be able to review quite a bit more if I can get patches via email instead of the webui. Can we get this enabled? eyal/attila - any ETA on testing gerrit 2.4 (.2 by now) so we can upgrade to it? ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] minutes: today's call
* Eyal Edri ee...@redhat.com [2012-07-18 11:59]: I'm in favor on doing it next monday. (not too healthy to do upgrades before the weekend...). We'll need to send email to rhev-devel + qe for an estimated downtime of 1 hour for gerrit.eng.lab.tlv.redhat.com. Any update? Eyal. - Original Message - From: Itamar Heim ih...@redhat.com To: Ryan Harper ry...@us.ibm.com Cc: Dan Kenigsberg dan...@redhat.com, Adam Litke a...@us.ibm.com, Anthony Liguori aligu...@us.ibm.com, VDSM Project Development vdsm-devel@lists.fedorahosted.org, Eyal Edri ee...@redhat.com, Attila Darazs adar...@redhat.com, Moran Goldboim mgold...@redhat.com Sent: Wednesday, July 18, 2012 7:48:01 PM Subject: Re: [vdsm] minutes: today's call On 07/18/2012 06:24 PM, Ryan Harper wrote: * Itamar Heim ih...@redhat.com [2012-05-16 10:26]: On 05/16/2012 06:11 PM, Dan Kenigsberg wrote: On Wed, May 16, 2012 at 09:43:57AM -0500, Ryan Harper wrote: * Dan Kenigsbergdan...@redhat.com [2012-05-07 05:42]: On Mon, Apr 23, 2012 at 05:52:13PM +0300, Dan Kenigsberg wrote: On Mon, Apr 23, 2012 at 07:34:14AM -0500, Adam Litke wrote: On Mon, Apr 23, 2012 at 04:17:18AM -0400, Ayal Baron wrote: Hi all, I would like to discuss the following on today's call: 1. Gerrit vs. mailing list Gerrit is an inhibiter for some contributors. One approach to solve this improve gerrit: - Gerrit should send the patch when it notified of a change. This may attract more reviewers. I'm happy to inform that Gal has sent a patch for this to upstream gerrit: https://gerrit-review.googlesource.com/#/c/34861/ Add unified diff to newchange mail template. Any eta on getting the gerrit notifications of changes to include the full patch in the email? You can +1 them in googlesource, maybe it helps ;-) indeed, please help push them upstream... https://gerrit-review.googlesource.com/#/c/34861/ https://gerrit-review.googlesource.com/#/c/34862/ I'm definitely happy to see notification on new posts and changes; helps me see what new activity is happening, but I'd really enjoy seeing the the patch series attached (via threading) as well. Itamar, I know Red Hat hates to do it, but can we take these patches to ovirt's gerrit before they are accepted upstream? yes we can. after i'll upgrade it to 2.3, which i prefer to do after i return from PTO in case there are some issues with the upgrade. so ETA end of the month for clean upgrade to 2.3, then after we see all is ok, let's say another week to upgrade to the version with these patches. It's about 6 weeks later. Dan's been asking for more review in vdsm; I know that I'd be able to review quite a bit more if I can get patches via email instead of the webui. Can we get this enabled? eyal/attila - any ETA on testing gerrit 2.4 (.2 by now) so we can upgrade to it? -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx ry...@us.ibm.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] Fatal error when migrate the VM with disk on iscsi data center
Hi, I am testing the VM migration in oVirt engine 3.1 bteta release and successfully did the migration test on NFS date center. However, the test of VM migration on iSCSI data center failed. I dumped the error and warning segments from the vdsm logs on both the source and destination host. Please ignore the time stamp out of sync between the two hosts. _ _*The vdsm log segment from the source host:* 66-4da5-8310-6dcc970e5367`::migration downtime thread exiting Thread-115166::ERROR::2012-07-25 23:18:55,953::vm::176::vm.Vm::(_recover) vmId=`11e06222-2d66-4da5-8310-6dcc970e5367`::operation failed: Failed to connect to remote libvirt URI qemu+tcp://9.181.129.110/system Dummy-115148::DEBUG::2012-07-25 23:18:55,981::__init__::1249::Storage.Misc.excCmd::(_log) 'dd if=/rhev/data-center/0b9a4ea4-d487-11e1-b614-5254001498c4/mastersd/dom_md/inbox iflag=direct,fullblock count=1 bs=1024000' (cwd None) Thread-115166::ERROR::2012-07-25 23:18:56,028::vm::240::vm.Vm::(run) vmId=`11e06222-2d66-4da5-8310-6dcc970e5367`::Failed to migrate Traceback (most recent call last): File /usr/share/vdsm/vm.py, line 223, in run self._startUnderlyingMigration() File /usr/share/vdsm/libvirtvm.py, line 451, in _startUnderlyingMigration None, maxBandwidth) File /usr/share/vdsm/libvirtvm.py, line 491, in f ret = attr(*args, **kwargs) File /usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py, line 82, in wrapper ret = f(*args, **kwargs) File /usr/lib64/python2.7/site-packages/libvirt.py, line 1034, in migrateToURI2 if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed', dom=self) libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+tcp://9.181.129.110/system *The vdsm log segment from the destination host:* Thread-1577::INFO::2012-07-25 23:19:50,407::API::601::vds::(_getNetworkIp) network None: using 0 Thread-1577::INFO::2012-07-25 23:19:50,407::API::228::vds::(create) vmContainerLock acquired by vm 11e06222-2d66-4da5-8310-6dcc970e5367 Thread-1578::DEBUG::2012-07-25 23:19:50,411::vm::564::vm.Vm::(_startUnderlyingVm) vmId=`11e06222-2d66-4da5-8310-6dcc970e5367`::Start Thread-1577::DEBUG::2012-07-25 23:19:50,411::API::244::vds::(create) Total desktops after creation of 11e06222-2d66-4da5-8310-6dcc970e5367 is 1 Thread-1578::DEBUG::2012-07-25 23:19:50,411::vm::568::vm.Vm::(_startUnderlyingVm) vmId=`11e06222-2d66-4da5-8310-6dcc970e5367`::_ongoingCreations acquired Thread-1577::DEBUG::2012-07-25 23:19:50,412::libvirtvm::2438::vm.Vm::(waitForMigrationDestinationPrepare) vmId=`11e06222-2d66-4da5-8310-6dcc970e5367`::migration destination: waiting 36s for path preparation Thread-1578::INFO::2012-07-25 23:19:50,412::libvirtvm::1285::vm.Vm::(_run) vmId=`11e06222-2d66-4da5-8310-6dcc970e5367`::VM wrapper has started Thread-1578::WARNING::2012-07-25 23:19:50,413::vm::398::vm.Vm::(getConfDevices) vmId=`11e06222-2d66-4da5-8310-6dcc970e5367`::Unknown type found, device: '{'device': 'unix', 'alias': 'channel0', 'type': 'channel', 'address': {'bus': '0', 'controller': '0', 'type': 'virtio-serial', 'port': '1'}}' found Thread-1578::ERROR::2012-07-25 23:24:50,484::vm::604::vm.Vm::(_startUnderlyingVm) vmId=`11e06222-2d66-4da5-8310-6dcc970e5367`::The vm start process failed Traceback (most recent call last): File /usr/share/vdsm/vm.py, line 584, in _startUnderlyingVm self._waitForIncomingMigrationFinish() File /usr/share/vdsm/libvirtvm.py, line 1572, in _waitForIncomingMigrationFinish self._connection.lookupByUUIDString(self.id), File /usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py, line 82, in wrapper ret = f(*args, **kwargs) File /usr/lib64/python2.7/site-packages/libvirt.py, line 2608, in lookupByUUIDString if ret is None:raise libvirtError('virDomainLookupByUUIDString() failed', conn=self) libvirtError: Domain not found: no domain with matching uuid '11e06222-2d66-4da5-8310-6dcc970e5367' - Timed out (did not receive success event) Thread-1578::DEBUG::2012-07-25 23:24:50,485::vm::920::vm.Vm::(setDownStatus) vmId=`11e06222-2d66-4da5-8310-6dcc970e5367`::Changed state to Down: Domain not found: no domain with matching uuid '11e0622 Any idea? -- Shu Ming shum...@linux.vnet.ibm.com IBM China Systems and Technology Laboratory ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel