Am 06.02.2013 17:29, schrieb Dean Troyer:
On Wed, Feb 6, 2013 at 9:49 AM, Chuck Short chuck.sh...@canonical.com wrote:
So during our regular package builds we been noticing a lot of failures due
to requests being hardcoded to 1.0. An example of this is the following
(for glance) can be found
I'm just wondering if anyone can comment on the following two topics:
a) volatile images - e.g. development servers where new packages are
installed every few days and where the entire system state must be
preserved on every reboot. Can the whole cookie-cutter static image concept be
Hi Emilien,
I had edited keystone-data.sh and changed the password to secret. But
your pointers helped me. I had also changed the value SERVICE_TENANT_NAME
to MY_TENANT as you can see in the mysql table. Apparently that was not a
good idea. I dropped the tables, changed it back to service, run
Hello guys,
My VMs are not attaching IP address, I've been look the VM's log but I
can't realize what is going on. I'm sending my VM's log. Can anybody help
me, please?
Regards.
Guilherme.
LogVM
Description: Binary data
___
Mailing list:
Hi Guilherme,
I reported the same issue just a moment ago here :
https://answers.launchpad.net/quantum/+question/221283
I think we are facing the same issue here- atleast VM logs shows.
Anil
On Thu, Feb 7, 2013 at 5:14 PM, Guilherme Russi
luisguilherme...@gmail.comwrote:
Hello guys,
My
Hi Anil,
I'm trying to find something to fix it, are you using quantum or
nova-network? I'm working with quantum, I have one physical computer with 2
NICs that is the controller and another 4 physical computers with 2 NICs
each that are the node compute, I left the Network node with the
By the way, I'm look your post and I saw some things that I don't have at
the ifconfig, like this part:
br-eth1 Link encap:Ethernet HWaddr 00:11:25:8e:a8:2d
inet addr:10.10.3.1 Bcast:10.10.255.255 Mask:255.255.0.0
inet6 addr: fe80::211:
br-ex Link encap:Ethernet HWaddr
Hi,
I am getting an error when performing nova boot ...: on an image that I have
confirmed is in my glance repository. However, the corresponding logs do not
indicate why or what the error is.
Is there a way and how to query the database for the nova instance error as
alluded to here:
Hi,
1) connect to mysql database:
mysql -uroot -p
2) use nova database once in mysql prompt
mysql use nova;
3) find the error values
mysql select * from instance_faults;
Regards,
Gabriel
From: Malek Mushleh mmus...@isi.edu
To:
Hi,
An OpenStack meetup will be arranged in Stockholm, Sweden, on April, 3rd
2013.
You're welcome to email me if you're interested in holding a presentation
at this meetup,
More details about the meetup:
http://www.meetup.com/OpenStack-User-Group-Nordics/events/95258382/
cheers,
/Nicolae.
Again, is there a better place to ask these types of questions?
I am trying to get a provider network working where I have full control of
the ip allocations. What I need is to be able to have 2 (or more public ip
addresses, or really to our private network). I know this can't be done
with
Hey Antonio,
Unfortunately this is a known design flaw and has been reported previously as a
bug as well - [https://bugs.launchpad.net/glance/+bug/1100220]
https://bugs.launchpad.net/glance/+bug/1100220 . We will hopefully be looking
at rectifying it sometime soon.
Thanks,
Iccha
Hi all,
I have spent several days installing Grizzly-2 Keystone with SSL and PKI and
think I have been successful. I can see some of the new API resources such as
v3/domains, v3/groups, and v3/services, but I don't see these listed as
commands in the keystoneclient. Are they simply not
So I'm getting this when I try to boot a Cirros image in scheduler.log. I
have a controller node, network node, and one compute node setup with
Folsom on RHEL 6. Any ideas? Thanks!
2013-02-07 19:21:45 WARNING nova.scheduler.manager
[req-358f5c96-e236-4167-b6a9-ccc02c853d41
Hi Everyone,
I know that it's late in the cycle, but I am very excited to notify
everyone that we have been working on the MidoNet Quantum plugin for
Grizzly, which would enable MidoNet (Midokura's virtual networking
solution) in Quantum, and we are hoping to have it included in for the
Grizzly-3
Hi, all,
I am following OpenStack Basic Install guide (
http://docs.openstack.org/folsom/basic-install/content/index.html), but
when executing the keystone-endpoint.sh script on the controller-node, I
always get this error message:
Expecting authentication method via
either a service token,
Greg,
IMO, this qualifies as a bug.
To debug what's causing this scenario is your case, I would suggest
checking the database connection setting in nova.conf on your Compute
Controller host. AFAIK, it either means Compute's status is not being
updated (Compute service down) or its being updated
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/633/Project:raring_grizzly_nova_trunkDate of build:Thu, 07 Feb 2013 03:36:01 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/634/Project:raring_grizzly_nova_trunkDate of build:Thu, 07 Feb 2013 04:01:15 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt
at 20130207
Title: precise_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_deploy/111/Project:precise_grizzly_deployDate of build:Thu, 07 Feb 2013 09:40:31 -0500Build duration:13 minBuild cause:Started by command line by jenkinsStarted by command line
at 20130207
Title: precise_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/629/Project:precise_grizzly_nova_trunkDate of build:Thu, 07 Feb 2013 11:40:33 -0500Build duration:11 minBuild cause:Started by user Chuck ShortBuilt
Title: precise_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_deploy/112/Project:precise_grizzly_deployDate of build:Thu, 07 Feb 2013 11:52:16 -0500Build duration:13 minBuild cause:Started by command line by jenkinsBuilt on:masterHealth
at 20130207
at 20130207
Title: raring_grizzly_cinder_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_cinder_trunk/141/Project:raring_grizzly_cinder_trunkDate of build:Thu, 07 Feb 2013 14:26:32 -0500Build duration:4 min 40 secBuild cause:Started by user Chuck ShortBuilt
at 20130207-1932Build needed 00:00:00, 0k disc spaceE: apt-get update failedERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise
28 matches
Mail list logo
