> I am interested in Openstack development,
> i started installation setup, i am getting some errors like
> when i am doing "uec-publish-tarball ubuntu-10.10-server-uec-
> amd64.tar.gz mybucket " step ,
> i am getting unknown error "Unable to run euca-describe-images. Is
> euca200ls environment
Dear Leo van den Bulck ,
When i am doing ./nova.sh install
i am getting following error
" Downloading/unpacking glance from bzr+https://launchpad.net/glance (from
-r /root/dash/openstack-dashboard/tools/pip-requires (line 19))
Checking out https://launchpad.net/glance to
./.dashboard-venv/build/g
On Fri, 2011-08-26 at 23:10 +, Monsyne Dragon wrote:
> First off, I think it would be better if whatever had the failure
> responded by sending a request somewhere (a cast) to say "Hey, this
> bombed. Retry it. "
What if the failure was due to the process crashing, so that it can't
possibly se
I would think we have enough tracking information to support the goal of
identifying failures. In any scenario, some of the failures will simply be
unrecoverable.
Regarding the process crashing, who's to say the retry process also
wouldn't crash? We could endlessly argue the arbiter/watchdog proc
Is it possible to have world writable containers? After reading
http://swift.openstack.org/misc.html#module-swift.common.middleware.acl I
was able to create world readable containers using .r:*, but that syntax
is not allowed for writable containers and * doesn't seem to work either.
Any syntax he
On Aug 26, 2011, at 6:10 PM, Monsyne Dragon wrote:
> First off, I think it would be better if whatever had the failure responded
> by sending a request somewhere (a cast) to say "Hey, this bombed. Retry it. "
> I wouldn't try doing calls instead of casts, as some have suggested, for
> performa
>I also considered making it part of the existing scheduler service,
> but wasn't sure how to add a "time-delayed" message to the scheduler queue
> for the follow-up. If that's possible, then there would not need to be a
> separate service; the scheduler can simply follow up itself.
Unl
Hi everyone,
I released a new version of the Burrow message queue service today,
tagged in the diablo-4 milestone. You can find it here:
https://launchpad.net/burrow
The work during diablo has focused on finishing the conversion of
prototype to a real project and increasing test coverage, docs,
We are fast approaching the next swift release, version 1.4.3. This is the
version of swift that will be in the diablo release of openstack. Since swift
1.4.3 is scheduled for next week, all patches that will be included need to be
proposed now. We will be doing final dev and QA work this week t
Hi all,
What is the ip table rule that needs to be created to allow cloud utils to
connect?
I get these when starting up.
wget: can't connect to remote host (169.254.169.254): Connection timed out
cloud-setup: failed 2/30: up 26.44. request failed
>From what I was told there needs to be a rule
It should be created for you automatically on the network host.
you might need to set ip_forward to 1 in sysctl, but it should be working.
Request failed seems like an odd error, it may be that you are connecting from
the wrong ip somehow so the metadata server can't figure out which metadata t
Ok, so should nova-network be adding a iptables rule?
It seems like mine are all empty on where that application is running (or if I
restart it).
I've changed the ip_forward though. On a compute node (not the same as the
network node), when its being ran does that node also get an iptables rule
Dear All,
I was able to run the instances but the problem I am facing is that the
instances are in shutdown state.
1.
#euca-run-instances ami-0003 -k test -t m1.tiny
# euca-describe-instances
RESERVATION r-6t4mze5l admin default
INSTANCEi-0002 ami-000310.0.0
what is the output of "euca-get-console-output $instancename" and the
nova-compute.log on the running node
On Tue, Aug 30, 2011 at 1:55 AM, bhaskar kotha wrote:
> Dear All,
>
> I was able to run the instances but the problem I am facing is that the
> instances are in shutdown state.
> 1.
> #euca-
hi,
The output for euca-get-console-output i-0008 is:
*i-0008
2011-08-30T06:17:52Z*
Thanks,
Bhaskar
On Tue, Aug 30, 2011 at 11:45 AM, Leandro Reox wrote:
> what is the output of "euca-get-console-output $instancename" and the
> nova-compute.log on the running node
>
>
> On Tue, Aug 30,
15 matches
Mail list logo
