[openstack-dev] [ironic] [QA] some notes on ironic functional testing
nobodycam at gmail.com
Fri Jan 17 22:47:50 UTC 2014
Reading your post got me to thinking. What if we modified the ssh driver so
it used the libvirt api. Just off the top of my head some thing along the
lines of changing the ssh driver to issue python-libvirt commands would
work. As an example:
> shh user at host "python -c \"import libvirt;conn =
> libvirt.openReadOnly(None);dom0 = conn.lookupByName('seed');print 'Seed: id
> %d running %s' % (dom0.ID(), dom0.OSType())\""
> Seed: id 2 running hvm
This seems like a straight forward improvement to the driver, and should
improve overall performance.
On Wed, Jan 15, 2014 at 2:22 AM, Alexander Gordeev <agordeev at mirantis.com>wrote:
> Hi, Devananda
> On Wed, Jan 15, 2014 at 8:19 AM, Devananda van der Veen <
> devananda.vdv at gmail.com> wrote:
>> On Tue, Jan 14, 2014 at 6:28 AM, Alexander Gordeev <agordeev at mirantis.com
>> > wrote:
>>> - Secondly, virsh has some performance issues if you deal with >30
>>> VMs (it is not our case for now but who knows).
>>> This is a reason why you want to use python libvirt api instead of virsh
>> CLI, correct? I don't see a problem, but I will defer to the tempest devs
>> on whether that's OK.
> Yes, that's correct. In short, using of python API binding makes possible
> to execute all operations inside just one opened libvirt connection. Virsh
> CLI opens new connection every time when you call it. Every new connection
> produces a fork of libvirt daemon. When you're going to spawn/create/modify
> few dozens of VMs in short period of time this performance issue becomes
> very noticeable.
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev