Hi,
I'm trying to get all logging into syslog.
I have modified the nova.conf:
use_syslog= True
syslog_log_facility= LOG_LOCAL0
However it appears for most components logging is still going to
/var/log/nova/service
So the api.log and compute.log are still going there.
There are some messages
Hi,
Stupid question, did you restart compute and api service?
I don't have any problems with those flags.
--
Regards,
Sébastien Han.
On Mon, Jan 7, 2013 at 9:58 AM, Robert van Leeuwen
robert.vanleeu...@spilgames.com wrote:
Hi,
I'm trying to get all logging into syslog.
I have modified
John Griffith wrote:
On Fri, Jan 4, 2013 at 11:39 AM, Akira Yoshiyama wrote:
I think Cinder should have its own client service 'cinder-agent'.
There are many benefits:
This is something I've thought about a little bit but to be honest it's
been very low on my priority list. I've be
HI,
I am pretty sure, Its a bug in OpenStack, did everthing. but no result.
Best Regards,
Umar
On Mon, Jan 7, 2013 at 2:59 AM, Nathanael Burton
nathanael.i.bur...@gmail.com wrote:
Ah! It looks like you've changed the default availability zone for your
two nodes. Host compute1 is in AZ
I have the same problem, I can't create more than around 15 instances at
once or I get a timeout error.
BTW, the default was decreased in essex from 3600 to 60:
https://bugs.launchpad.net/nova/+bug/938287
If you can find a reasonable default value would be very appreciated :)
thanx
.a.
On
Just a note on this. I recently added functionality in Grizzly that will allow
specified non-admin users to use this functionality.
https://bugs.launchpad.net/nova/+bug/1070880
Not useful for non-admins in Folsom I'm afraid but, the functionality should
work for the admin context.
From:
I can lead this task. Please join me on IRC #openstack-community (I'm
reed) to coordinate efforts.
Cheers,
stef
On 11/18/2012 05:30 AM, Ryan Lane wrote:
On Sat, Nov 17, 2012 at 3:05 AM, Laurence Miao laurence.m...@gmail.com
mailto:laurence.m...@gmail.com wrote:
Hi Michael,
I'd love
The other issue seems to be that the log-facility is not honoured properly:
My messages mostly end up in /var/log/messages instead of the file that is
specified using the log_facility.
Some messages do get in there so it does not seem to be related to the
syslog(-ng) config.
Also, if I filter
Hi All,
I have a growing problem in which compute nodes are puzzlingly over
reporting their resource utilization and thus appearing to be over utilized
when they are in fact empty. System is Ubuntu 12.04 using cloud archive
Folsom (2012.2-0ubuntu5~cloud0) problem appeared on a single node after
Hallo All,
I am using OpenStack ESSEX and I have made all the necessary changes in order
to perform live-migration (mounting the nova instances directory and
libvirt-bin configurations). The issue that I am facing is when I perform live
migration using the nova commands, there is neither error
If you want to setup DHCP flat networking, maybe this page (and the chapter
that contains it) could help:
http://docs.openstack.org/essex/openstack-compute/admin/content/libvirt-flat-dhcp-networking.html
Regards,
Stefano
On Mon, Jan 7, 2013 at 7:03 PM, Umar Draz unix...@gmail.com wrote:
Hello all,
I'm having an issue when using the Python API for swift [1]. I am unable to
do two sequential operations. The first operation works and the second
ceases to work. Is this expected, or is this a bug?
I'm using Ubuntu 12.04 with the Folsom Packages.
Example output (Python Interpreter):
I think My network configuration is ok,
I can ping compute's own ip address 192.168.1.133 from virtual machine. But
I can't access other local machines.
I think its security firewall issue or need some routing table?
Here is the out put of ping.
root@ubuntu-cloud# ping 192.168.1.133
PING
Can you please post the output of ip addr list, route -n and brctl
show on compute node and virtual machine? More than a firewall issue, it
seems a routing issue to me.
Thanks,
Stefano
On Mon, Jan 7, 2013 at 7:38 PM, Umar Draz unix...@gmail.com wrote:
I think My network configuration is
Hi
Here is the result
Compute node
*brctl show*
bridge name bridge id STP enabled interfaces
br100 8000.002590976edb no eth1
vnet0
*ip addr list*
1: lo: LOOPBACK,UP,LOWER_UP
Can you try to set rp_filter to 0? I needed to disable it today, otherwise
I was facing problem similar to yours.
Try to ping with rp_filter disabled, let's see if we can resolve the
problem that way.
Regards,
Stefano
On Mon, Jan 7, 2013 at 8:57 PM, Umar Draz unix...@gmail.com wrote:
Hi
I think there's a mismatching here between configuration and intended
behavior, I'm sorry not to have detected it before.
With your configuration, you're bridging (Layer 2) two different networks
(Layer3). They cannot communicate if not properly routed or masqueraded.
Do you need to NAT VMs
Hey all,
We just started work on a new plugin for Quantum that we're calling
Quark. The blueprint lives here:
https://blueprints.launchpad.net/quantum/+spec/quark
In short, we want to provide an alternative to the existing NVP plugin
that's a bit more cognizant of how much it
There is a typo in the docs...If you look closely, it says Hybird instead of
Hybrid.
LibvirtHybirdOVSBridgeDriver
LibvirtHybridOVSBridgeDriver
Byron
On Nov 15, 2012, at 4:38 PM, Nikola Pajtic salge...@gmail.com wrote:
Yeah, that worked!!! Thanks a lot, Doug, for pointing me in right
See if this bug might be related to your problem...
https://bugs.launchpad.net/nova/+bug/1060363
Byron
Begin forwarded message [Openstack] Base images removed in upgrade essex -
folsom and other stories:
We also came across an issue where some compute nodes were reporting bogus
resource
when using live migration, the process automate rollback when the
transection failed, check both the src and dst host nova-compute.log for
the reason why it failed .
2013/1/8 Narayanan, Krishnaprasad naray...@uni-mainz.de
Hallo All,
** **
I am using OpenStack ESSEX and I have made
Hey guy,
Please try as below:
1) If there is no log, maybe config/log file's privilege issue. You can
edit their owner: $ chown nova:nova /etc/nova chown nova:nova /var/log/nova
2) After method 1) , there must be logs in log file. You can run command $
nova-manage logs error, it
Hey,
I have met the situation when injecting keypair into VM with nbd module failed.
Nova only print nbd failed but still create VM successfully. That makes
keypair(private key) is not successfully inject into VM. So the VM is not match
my prefer.
So I think it is necessary to make the VM to
I don't think so.
2013/1/8 hzyangtk hzyan...@corp.netease.com:
Hey,
I have met the situation when injecting keypair into VM with nbd module
failed. Nova only print nbd failed but still create VM successfully. That
makes keypair(private key) is not successfully inject into VM. So the VM is
at 20130107
Title: precise_grizzly_python-swiftclient_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-swiftclient_trunk/17/Project:precise_grizzly_python-swiftclient_trunkDate of build:Mon, 07 Jan 2013 07:18:46 -0500Build duration:2 min 17 secBuild
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/400/Project:precise_grizzly_nova_trunkDate of build:Mon, 07 Jan 2013 09:01:03 -0500Build duration:4 min 38 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/403/Project:raring_grizzly_nova_trunkDate of build:Mon, 07 Jan 2013 09:01:05 -0500Build duration:12 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/401/Project:precise_grizzly_nova_trunkDate of build:Mon, 07 Jan 2013 11:01:11 -0500Build duration:2 min 28 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/404/Project:raring_grizzly_nova_trunkDate of build:Mon, 07 Jan 2013 11:01:05 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/402/Project:precise_grizzly_nova_trunkDate of build:Mon, 07 Jan 2013 11:30:59 -0500Build duration:6 min 8 secBuild 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/405/Project:raring_grizzly_nova_trunkDate of build:Mon, 07 Jan 2013 13:06:17 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/404/Project:precise_grizzly_nova_trunkDate of build:Mon, 07 Jan 2013 14:01:02 -0500Build duration:5 min 47 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/405/Project:precise_grizzly_nova_trunkDate of build:Mon, 07 Jan 2013 14:17:44 -0500Build duration:9 min 46 secBuild cause:Started by user adamBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/406/Project:precise_grizzly_nova_trunkDate of build:Mon, 07 Jan 2013 14:39:31 -0500Build duration:10 minBuild cause:Started by user adamBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/407/Project:precise_grizzly_nova_trunkDate of build:Mon, 07 Jan 2013 14:58:03 -0500Build duration:13 minBuild cause:Started by user adamBuilt
Title: precise_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_deploy/49/Project:precise_grizzly_deployDate of build:Mon, 07 Jan 2013 15:11:12 -0500Build duration:25 minBuild cause:Started by command lineBuilt on:masterHealth
at 20130107
at 20130107
Title: precise_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/409/Project:precise_grizzly_nova_trunkDate of build:Tue, 08 Jan 2013 00:01:03 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_deploy
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_deploy/50/Project:precise_grizzly_deployDate of build:Tue, 08 Jan 2013 00:14:31 -0500Build duration:22 minBuild cause:Started by command lineBuilt on:masterHealth
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/412/Project:raring_grizzly_nova_trunkDate of build:Tue, 08 Jan 2013 02:31:03 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt
42 matches
Mail list logo
