Can you explain what some of the errors mean? For instance, for this
merge proposal:
https://review.openstack.org/#change,1950
the unit tests passed, but the libvirt tests were Hit by Torpedo and
XenServer tests had a Chef client timeout. Am I right to assume that
at least the chef client
hi ,everybody
nova compute node error :
2011-12-01 17:35:52,871 WARNING nova.compute.manager [-] Error during
power_state sync: QueuePool limit of size 10 overflow 10 reached,
connection timed out, timeout 30
2011-12-01 17:37:27,531 WARNING nova.compute.manager [-] Error during
power_state sync:
Hi
Thats an sqlalchemy error, what database backend are you using ? That error
is that actually youre not closing connections and they are not returning
to the pool
Regards
On Thu, Dec 1, 2011 at 7:04 AM, darkfower atk...@gmail.com wrote:
hi ,everybody
nova compute node error :
2011-12-01
Sure! Sorry about that :)
Torpedo is just the set of ruby tests that we have been using for a while
to smoketest the API, separated into a project outside of VPC - the
project that was running for a while on the jenkins server. Source is
here: https://github.com/dprince/torpedo When one is hit
It finally works. The problem was the flag checks while looking for the
ISO SR.
inside the find_iso_sr method (in nova/virt/xenapi/vm_utils.py), I found
that the ISO SR must have these settings:
content type: iso
other-config:i18n-key=local-storage-iso
As far as I know, this wasn't
Hi Michaël,that would be great if you can provide us an how-to for that that we will integrate into the documentation !Regards,Razique
Nuage Co - Razique Mahrouarazique.mahr...@gmail.com
Le 1 déc. 2011 à 16:14, Michaël Van de Borne a écrit :
It finally works. The problem was
Thanks for the info! I've logged bug 898682 [1] to ensure it gets
added to the documentation. Based on this note, is this a solution for
Xen only?
Is this the same as using a config drive? I had heard a config drive
works on KVM but not Xen.
If someone who's familiar with this area could work
Hey all,
OK, so I'm almost done with Draft 3 of the OpenStack Images API 2.0
Proposal. While doing this, however, I have come to the conclusion
that the container_format we added in the Cactus timeframe just makes
things more confusing and should probably be removed.
We have two fields in the
That's right, it's a Xen*Server* only feature. I insist on XenServer
because it's been implemented only inside the xenapi.
If you wish to manage VMs using KVM or Xen hypervisor (the community
hypervisor packaged in Linux distributions), this will utilize the
libvirt API, and not XenAPI.
So,
On 30 Nov 2011 - 11:07, Duncan McGreggor wrote:
On Tue, Nov 29, 2011 at 12:21 PM, Soren Hansen so...@linux2go.dk wrote:
It's been a bit over a week since I started this thread. So far we've
agreed that running the test suite is too slow, mostly because there
are too many things in there
Hi Nova-cores
Is the Console function in OS API 1.1 specs?
(See https://bugs.launchpad.net/nova/+bug/898266)
The implementation is not in contrib directory, so it didn't looks an extension.
But as 898266 mentioned, it is not described in API docs.
And also, I checked API spces from code. (I
hi all
i write a document about openstack swift distributed log system slogging
http://wiki.openstack.org/development/swift/slogging
if some one can put it into the development document i will very appreciate.
thanks.
___
Mailing list:
On Dec 1, 2011, at 10:52 AM, Jay Pipes wrote:
What do people think of this proposal to combine the two into a single
format field?
I think it's a good idea. When I was trying to figure out how to migrate the
glance-upload examples to glance add, I found it confusing that there were
two
This might be a bug
.launchpad.net/horizon/+bug/876663
The fix that was backported into Diablo/stable was to retry connections a
few times. Here's info about the fix: https://
review.openstack.org/#change,1661
On Dec 1, 2011 11:16 PM, darkfower atk...@gmail.com wrote:
hi,nova.conf as follow:
o,thanks
2011/12/2 Leandro Reox leandro.r...@gmail.com:
This might be a bug
.launchpad.net/horizon/+bug/876663
The fix that was backported into Diablo/stable was to retry connections a
few times. Here's info about the fix: https://
review.openstack.org/#change,1661
On Dec 1, 2011 11:16
15 matches
Mail list logo
