please let me
know how it goes.
Regards,
Neil
On Aug 29, 2011, at 7:24 AM, Emanuele Verga wrote:
Hi, I downloaded and installe hsflowd trunk revision 226 but using hsflowd
I keep seeing virStorageLookupByPath errors, and VM disk statistics
aren't displayed. Do I need to tell hsflowd
Hi, I downloaded and installe hsflowd trunk revision 226 but using hsflowd
I keep seeing virStorageLookupByPath errors, and VM disk statistics aren't
displayed. Do I need to tell hsflowd explicitly to use target=vda call? If
yes, how?
Thanks in advance,
Emanuele
2011/8/25 Emanuele Verga
Hi Neil,
Yes that's possible, the problem is Nova places each image in a separate
folder (/var/lib/nova/instance/INSTANCENAME/), so we would have to create a
new pool with the corresponding path each time a new instance is created,
and if we start to add more servers it quicly becomes
Ok, I tried linking one of the disk files to the default storage pool
folder and it actually detected the linked volume in libvirt:
After issuing a *virsh pool-refresh default *the disk was correctly detected
and reported as a volume by *virsh vol-list default, *but there is a
problem:
The
of -DHSF_VRT), and you may get
better results. Please let me know what happens.
Neil
On Aug 16, 2011, at 2:14 AM, Emanuele Verga wrote:
Hi,
we have a problem with the following installation:
we have a system that’s a compute node in an Openstack test installation.
Now on this machine we
Hi,
we have a problem with the following installation:
we have a system that’s a compute node in an Openstack test installation.
Now on this machine we decided to install Ganglia, to check it’s monitoring
capabilities regarding virtual machines hosted on that node by Openstack.
We then
6 matches
Mail list logo