>
> Dear All,
>
I am facing issue while running instances under ubuntu 11.04 server
edition.
*Steps followed:*
1. Installed openstack nova, bexar edition to my cluster.
2. check all the running processes
3. Able to publish the image.
4. Able to describe the images, which change the s
Hello everyone,
The team meeting will take place at 21:00 UTC this Tuesday in
#openstack-meeting on IRC. PTLs, if you can't make it, please name a
substitute on [2].
This is the last meeting before the milestone branch point for
Glance/Nova diablo-4, which is the last feature milestone for Diablo
On 08/16/2011 05:41 AM, Joshua Harlow wrote:
> Hi all,
>
> I am using debian 6 (wheezy) + nova-diablo-3 + glance (from git) and
> have installed the needed python pkgs and have the correct servers and
> such running.
>
> I am seeing the following error when running the following:
>
> #uec-publi
Check first that the network process is running and not producing
errors. Then check for errors in
/var/log/libvert/qemu/instance-0001.log. I suspect the issue lies
with, either, the network configuration or with a missing file for
qemu (kvm-pxe).
-Mandell
On Mon, Aug 15, 2011 at 9:48 PM, p
On Mon, Aug 15, 2011, Vishvananda Ishaya wrote:
> I pushed a new version of that branch with the suggested change. The
> recent change to our db library to make it use eventlet is stealing the
> stack trace, so we can't reraise the same exception. The branch now
> logs the exception and returns
Thierry Carrez wrote:
> This is the last meeting before the milestone branch point for
> Glance/Nova diablo-4, which is the last feature milestone for Diablo:
> all Diablo features should be merged by end of day, Monday Sept 22 ! We
> will therefore review progress towards the D4 objectives.
Oops,
Keystone has been assigned TCP port 35357 by IANA.
We'll make that the default port.
Thanks,
Z
On 6/24/11 12:46 AM, "Mark Nottingham" wrote:
>On 24/06/2011, at 3:31 PM,
> wrote:
>
>> Couple of quick points:
>>
>> a) Once the ports are fixed, we should register them with IANA as well
>>know
This looks like a bug. It appears that you are using xen through libvirt which
hasn't had a whole lot of testing.
Vish
On Aug 15, 2011, at 7:18 PM, Joshua Harlow wrote:
> Hi all,
>
> Another error that others may have seen:
> Is it supposed to continue even if this fails?
> This is for runnin
ctoteam@buildingbuild:~$ sudo modprobe nbd
ctoteam@buildingbuild:~$
Is there supposed to be devices there??
On 8/15/11 10:23 PM, "Yuriy Taraday" wrote:
You probably should try to do "modprobe nbd" before running nova. This will
create list of nbd devices that nova uses to inject keys and get i
Hi folks,
At the last OpenStack meeting, Vish asked me to send out an update on the
Quantum project. Here's some info:
Quantum is a virtual network service, targeted at Openstack. If you're not
familiar with Quantum, please see:
- http://wiki.openstack.org/Quantum
- http://launchpad.net/quantum
NBD shouldn't be needed for xen. You probably need to set
--nouse_cow_images
which will stop nova from trying to use qcow2 as the image format.
Vish
On Aug 16, 2011, at 11:06 AM, Joshua Harlow wrote:
> ctoteam@buildingbuild:~$ sudo modprobe nbd
> ctoteam@buildingbuild:~$
>
> Is there supposed
Great update, Dan. Thank you!
-jay
On Tue, Aug 16, 2011 at 2:54 PM, Dan Wendlandt wrote:
> Hi folks,
> At the last OpenStack meeting, Vish asked me to send out an update on the
> Quantum project. Here's some info:
> Quantum is a virtual network service, targeted at Openstack. If you're not
> f
If you don't want legacy token auth as a middleware you should still be
able to edit keystone.conf and remove legacy-auth from the pipeline and
have the application running.
Regards
On 08/15/2011 06:44 PM, Nguyen, Liem Manh wrote:
Hello Stackers,
Currently, we have the legacy_token_auth to "
On Mon, Aug 15, 2011 at 6:44 PM, Nguyen, Liem Manh wrote:
> Currently, we have the legacy_token_auth to “help” with integration with
> services (like Swift) that still talks auth v1.0. Will this filter go away
> and other services will be speaking pure Keystone when Diablo releases?
It would ki
Hello,
It was decided in our weekly OpenStack meeting that from this point forward,
us developers should make a quick announcement on this ML whenever adding
new dependencies to any OS project -- preferably *before* your branch merges
in trunk. This should make all our jobs a little easier. :)
Th
Thanks,
I'll give it a try and see if the libvirt stuff works, or I'll just switch to
the native xen usage in openstack.
-Josh
On 8/16/11 11:44 AM, "Vishvananda Ishaya" wrote:
NBD shouldn't be needed for xen. You probably need to set
--nouse_cow_images
which will stop nova from trying to use
Are there any good documentations on making openstack fault tolerant or exactly
how it will handle failures?
Like say the mq server dies, can another mq server take over. Similar with the
database (mysql replication?)
Seems like having that kind of information for corporate users would be n
Just notifying everyone of a small change introduced by a recent merge
of mine into Glance. A single line was added to
etc/glance-registry.conf--the line is inserted into the [filter:context]
section, so the section should now read:
[filter:context]
context_class = glance.registry
Ok, seems like it go past this error.
2011-08-16 16:12:24,218 DEBUG nova.utils [-] Running cmd (subprocess): sudo
losetup --detach /dev/loop0 from (pid=5538) execute
/home/ctoteam/nova/nova/utils.py:143
2011-08-16 16:12:24,262 WARNING nova.virt.libvirt_conn [-] instance
instance-0001: ignor
Looks like there is something wrong with the xml. You might try navigating to
the instances dir/instance-0001/libvirt.xml and see if there is anything
that looks wrong.
if you try: virsh create dir/instance-0001/libvirt.xml you might get some
more useful error message about what is wron
Ok, seems like getting further.
I made sure that I added
--libvirt_type=xen
Along with
--libvirt_uri=xen:///
Now I get:
. from (pid=6198) inner /home/ctoteam/nova/nova/utils.py:600
2011-08-16 16:36:09,911 ERROR nova.exception [-] Uncaught exception
(nova.exception): TRACE: Traceback (most rec
You've extended beyond my experience. Never tried open source xen. Perhaps
soren has some insight here.
Vish
On Aug 16, 2011, at 5:06 PM, Joshua Harlow wrote:
> Ah, ok.
>
> So updated that.
>
> Now I get the following:
>
> 2011-08-16 16:58:33,973 DEBUG nova.utils [-] Running cmd (subproces
Dear Mandell,
The nova-network process is running.
But I am not able to see any log file under /var/log/libvert/qemu/
directory.
When I run describe instance command , I am able to see this output.
root@openstack2:~# euca-describe-instances
RESERVATIONr-l4zr8lygbexardefault
INSTANCE
23 matches
Mail list logo
