questions)
openstack-dev@lists.openstack.org
Sent: Thursday, August 21, 2014 11:05:18 AM
Subject: Re: [openstack-dev] [nova][libvirt] Non-readonly connection to
libvirt in unit tests
On Thu, Aug 21, 2014 at 10:52:42AM -0400, Solly Ross wrote:
FYI, the context of this is that I would
Sent: Thursday, August 21, 2014 11:23:17 AM
Subject: Re: [openstack-dev] [nova][libvirt] Non-readonly connection to
libvirt in unit tests
On Thu, Aug 21, 2014 at 11:14:33AM -0400, Solly Ross wrote:
(reply inline)
- Original Message -
From: Daniel P. Berrange berra
spots where we'll want to use fakelibvirt.
Best Regards,
Solly
- Original Message -
From: Matt Riedemann mrie...@linux.vnet.ibm.com
To: openstack-dev@lists.openstack.org
Sent: Wednesday, August 20, 2014 8:37:39 PM
Subject: Re: [openstack-dev] [nova][libvirt] Non-readonly connection
On Thu, Aug 21, 2014 at 10:52:42AM -0400, Solly Ross wrote:
FYI, the context of this is that I would like to be able to test some
of the libvirt storage pool code against a live file system, as we
currently test the storage pool code. To do this, we need at least to
be able to get a proper
@lists.openstack.org
Sent: Thursday, August 21, 2014 11:05:18 AM
Subject: Re: [openstack-dev] [nova][libvirt] Non-readonly connection to libvirt
in unit tests
On Thu, Aug 21, 2014 at 10:52:42AM -0400, Solly Ross wrote:
FYI, the context of this is that I would like to be able to test some
of the libvirt storage
Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday, August 21, 2014 11:05:18 AM
Subject: Re: [openstack-dev] [nova][libvirt] Non-readonly connection to
libvirt in unit tests
On Thu, Aug 21, 2014 at 10:52:42AM -0400, Solly Ross wrote:
FYI
...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday, August 21, 2014 11:05:18 AM
Subject: Re: [openstack-dev] [nova][libvirt] Non-readonly connection to libvirt
in unit tests
On Thu, Aug 21, 2014 at 10:52:42AM -0400, Solly
-dev] [nova][libvirt] Non-readonly connection to libvirt
in unit tests
On Thu, Aug 21, 2014 at 10:52:42AM -0400, Solly Ross wrote:
FYI, the context of this is that I would like to be able to test some
of the libvirt storage pool code against a live file system, as we
currently test the storage pool
On 8/11/2014 4:42 AM, Daniel P. Berrange wrote:
On Mon, Aug 04, 2014 at 06:46:13PM -0400, Solly Ross wrote:
Hi,
I was wondering if there was a way to get a non-readonly connection
to libvirt when running the unit tests
on the CI. If I call `LibvirtDriver._connect(LibvirtDriver.uri())`,
it
On 8/11/2014 4:42 AM, Daniel P. Berrange wrote:
On Mon, Aug 04, 2014 at 06:46:13PM -0400, Solly Ross wrote:
Hi,
I was wondering if there was a way to get a non-readonly connection
to libvirt when running the unit tests
on the CI. If I call `LibvirtDriver._connect(LibvirtDriver.uri())`,
it
On Mon, Aug 04, 2014 at 06:46:13PM -0400, Solly Ross wrote:
Hi,
I was wondering if there was a way to get a non-readonly connection
to libvirt when running the unit tests
on the CI. If I call `LibvirtDriver._connect(LibvirtDriver.uri())`,
it works fine locally, but the upstream
CI barfs
Hi,
I was wondering if there was a way to get a non-readonly connection to libvirt
when running the unit tests
on the CI. If I call `LibvirtDriver._connect(LibvirtDriver.uri())`, it works
fine locally, but the upstream
CI barfs with libvirtError: internal error Unable to locate libvirtd daemon
12 matches
Mail list logo
