Hello everyone,
This is crunch time (again):
Diablo-4 is our last feature milestone, and its release branch will be
cut early morning Tuesday, Aug 23. That means all your features must be
*merged* by end of day, Monday, Aug 22 !
Please propose early and review often !
We should be very careful
On 08/19/2011 01:31 PM, Isaku Yamahata wrote:
> It looks you specified "root=/dev/xvda", but the disk that is
> instantiated is /dev/sda.
> But I didn't see why it happened. Did you customized the template
> for libvirt, libvirt.xml.template?
This seems wrong then, because under Xen, you should us
The nova-tarmac jobs gets hung quite often lately. I know a lot of fingers have
been pointing at Launchpad issues but I'm not sure that is the case here. When
its hung the console output of the job is almost always at:
Running test command: /home/jenkins/openstack-ci/test_nova.sh
This is ess
Yep, if you were just running two nova-api processes, you'd have two entry
points. Hence the need for something like HAProxy (or Pound) to act as your
single EC2 entry point but passing requests to your nova-api processes.
Everything being stateless you wouldn't get into a state where the DB &
mess
HI,
I am installing Diablo using ppa:nova-core/milestone in Lucid. I am following
the installation steps of OpenStack Compute
Administration Manual for cactus.
While I run euca-authorize -P icmp -t -1:-1 default I get err [Errno 111]
Connection refused.
Nova.conf is
# cat /etc/nova/nova.conf
Hey Everyone,
Yesterday, I merge prop'd a branch that adds the tenant id to all request uris,
as is to spec. It also removes the ability to use the 'X-Auth-Project-Id'
header in requests other than authentication requests. This may have
implications since some custom v1.1 bindings and test su
Try restarting the nova-api process.
From: openstack-bounces+jtran=attinteractive@lists.launchpad.net
[openstack-bounces+jtran=attinteractive@lists.launchpad.net] On Behalf Of
haynes.da...@accenture.com [haynes.da...@accenture.com]
Sent: Friday, Au
Greetings, Haynes!
Are you wanting to run the ec2 API specifically? I will defer to the list,
but I believe sometime recently the OSAPI became the default API in Nova,
and that might explain why 8773 isn't returning anything. Do you see
anything on 8774?
I would guess that none of the euca comm
Good morning,
I've installed Diablo from packages (from trunk) yesterday on Ubuntu 11.04 -
and have a single instance setup working just fine for firing up instances,
shutting them down, etc.
I then attempted to add a computing node to that setup, but have been unable to
get instances to fire
There was an issue on one version of ubuntu (I think it was natty?), where xen
was using /dev/sd* instead of /dev/xd*. I remember discussion on the mailing
list or a bug about having to have a specific workaround.
On Aug 19, 2011, at 1:42 AM, Thomas Goirand wrote:
> On 08/19/2011 01:31 PM, Isa
hi,
Looking at nova/utils.py I *think* that utcnow() is right but
utcnow_ts() is incorrect. The former does give UTC, the latter
unfortunately changes it to localtime. I haven't written a test in
nova, but I extracted the code and wrote a little demo that I *think*
shows the right way to do it, us
It looks like it was maverick, you can find a lot of good info here on xen,if
you're not using this already:
http://wiki.openstack.org/XenServerDevelopment
I believe the work around Vish is referring to is made in nova.conf:
--xenapi_remap_vbd_dev=true
Give that a go, hopefully gets you on your
Ya, that is what I was thinking also.
I haven't customized anything though. This is just the normal
euca-run-instances + basic openstack diablo-3.
$ euca-run-instances ami-001f -k mykey -t m1.tiny
Where ami is:
IMAGEami-001fubb/maverick-server-uec-amd64.img.manifest.xml
Ok but I am going through libvirt instead of xenapi since I am just using a
debian + xen-hypervisor package.
Also going through libvirt seems to be better, since it doesn't make your setup
as "strongly" connected to xen.
For those using the following in debian/ubunbu would the usage of the xena
For my nova/virt/libvirt.xml.template on my compute node.
The following is being done.
#if $type == 'xen'
#set $disk_prefix = 'sd'
#set $disk_bus = 'scsi'
linux
/dev/xvda
Should that be /dev/sda for the /root node here?
On 8/19/11 10:24 AM, "Joshua Harl
So what I've figured out is the following seems to work with xen4.
$ diff nova-2011.3/nova/virt/libvirt.xml.template libvirt.xml.template
21c21
< /dev/xvda
---
> /dev/sda
46a47,49
> #if $type == 'xen'
> /usr/lib/xen-4.0/bin/pygrub
> #end if
62c65,69
<
Hello,
This question is not directly related to the OpenStack Object Store, but
it would be interesting to hear your opinions on that.
Imagine multi-cloud environment with multiple heterogeneous object
stores (e.g. OpenStack, AWS S3, Azure blob store, etc.). And the
question is: How to ident
17 matches
Mail list logo
