Hi,
192.168.3.0/24 is the fixed_range in my localrc for both nodes. My
second node doesn't have direct access to the public network. It has only
one interface (eth1) connected to the private network. It has an ip of
192.168.2.2. Is there a way set this node up as a compute node without
Hi Anne,
Thanks for your reply. I've just set the 'use_deprecated_auth=true' and it
won't work. Actually I've seen the page you sent me and did this before
last entire OS re-installation, and it didn't work either. I guess it's a
bug then.
Thanks.
Regards,
Chang
On Thu, Dec 29, 2011 at 1:08
Hey guys. I have two nodes each one running two VM's. One of the nodes have all
the nova components and the other just have the nova-compute and nova-network.
I can successfully access outside the openstack network via ssh the VM's that
are running in the node that have all the nova
Thanks, Ask!
amqplib versions after and including 1.0 enables SO_KEEPALIVE by default,
and Kombu versions after and including 1.2.1 depends on amqplib = 1.0,
so maybe you should update your package dependencies?
devstack requied amqplib 0.6.1.
I will research the best solution more detailed.
Yes. But interesting to use heartbeats like in Pika. Is kamqp supports
heartbeats now?
2011/12/29 Ask Solem a...@rabbitmq.com
On 28 Dec 2011, at 17:26, Chris Behrens wrote:
On Dec 28, 2011, at 5:36 AM, Ask Solem wrote:
[...]
amqplib does not support heartbeats so there may be cases
Hi all :)here are some topics my mind crossed..# nova doesn't have any prunning mecanisms. Here are some things I'm thinking about :- database cleaning deleted instances non consistent fixed_ips deleted groups deleted projectsFor instance my "instances" table has more than 85% of deleted
Hi,
I'm trying to learn how the testing framework is set up and write my own
unit tests for the driver I've been working on. Unfortunately I'm not
making much progress, on my Ubuntu 11.10 system I keep running into
problems with M2Crypto.
I picked up the change to use apt-get instead of pip, but
Well, we're running tests in Jenkins on 11.10, so there is certainly
something that we're doing that you're not... let's see if we can track
that down so that we can document it properly.
Ensure that you have the following packages installed via apt:
build-essential python-all-dev libssl-dev
Hi Monty,
Thanks for the response, performed the steps you recommended and pastes the
output from run_tests.sh on pastebin:
http://paste.openstack.org/show/4018/
Let me know if this is useful. Also, I'm going to try running on a fresh
11.10 install, I suspect there's some config on my existing
Hi,
A few weeks ago, I wrote about turning on an integration test gating job
for the stable/diablo branch. That's been running for a while now, and
during that time with help from Anthony Young and Jesse Andrews, we've
been able to address the issues we saw and make the job fairly reliable.
At
Hey Sagar,
It does sound like you need to use eth1 for FLAT_INTERFACE - but note this
parameter is used when your network is first created with nova-manage, so
if you change this you will need to re-run stack.sh (it isn't enough to
update your nova.conf), which is probably best to do after a
This is brilliant news. Thanks to everyone involved in making this work --
it's a great milestone.
You're right that this might uncover non-determinisms in Nova -- if it does
then that would be great news, because shaking those out is important for the
quality of the software overall. And
I'm getting 4 failures with the current Glance functional tests, all of this
form:
FAIL: test_glance_cli
(glance.tests.functional.test_private_images.TestPrivateImagesCli)
--
Traceback (most recent call last):
File
On 12/30/2011 03:02 AM, Ewan Mellor wrote:
It's a JSON dictionary. It looks like it's only purpose is for the
administrator to set arbitrary key-value pairs, and then get them again
later. It looks completely useless and overdone to me. Both xapi and Nova
already have databases -- I've
14 matches
Mail list logo
