[Openstack-operators] Openstack Manual install with nova-network

Hi guys, I have a 2 node(1 controller + 1 compute nodes) architecture that I installed manually, all of my compute services, including nova network, are on the compute node. I tried logging to the dashboard but I received this message: ConnectionFailed at /admin/ Connection to neutron failed: M

[Openstack-operators] neutron debug messages

Hi guys, I've disabled all debugging and verbose configs, but I still get/see this in my logs: 2014-09-02 11:45:08.247 50862 DEBUG neutron.agent.metadata.namespace_proxy [-] Request: GET /2008-02-01/meta-data/security-groups HTTP/1.0 Accept: */* Any idea how to disable these from being logged or

Re: [Openstack-operators] Openstack Manual install with nova-network

Looking at the "exception location" seems like you have python-neutronclient installed. Would you please check below: 1) Use rpm -qa (REL based) or dpkg -l (debian based) to look for the package python-neutronclient. If so please remove python client for neutron. 2) What is value of parameter netwo

Re: [Openstack-operators] neutron debug messages

Make sure you have set *debug = False* both in *neutron.conf* and agent configuration (*metadata_agent.ini* in this case from example message). Thanks, Vishal On Tue, Sep 2, 2014 at 6:57 AM, Alex Leonhardt wrote: > Hi guys, > > I've disabled all debugging and verbose configs, but I still get/s

Re: [Openstack-operators] Openstack Manual install with nova-network

Hi Vishal, Thank for the quick response, the python-neutronclient is a dependency for the dashboard installation, when I try to remove it, it says it will remove the dashboard installation as well. Do you know of a way to force the openstack not to use the neutron client, but to use the nova-ne

Re: [Openstack-operators] High Availability Guide team

As would I... On 26/08/2014 21:48, Adam Lawson wrote: > > I'd be happy to participate as needed Anne. > > On Aug 26, 2014 11:10 AM, "Anne Gentle" > wrote: > > Hi all, > Cross-posting to -docs and -operators. > > At the Ops mid-cycle meetup this week, Matt

Re: [Openstack-operators] Openstack Manual install with nova-network

It will help if you include your nova.conf file. Thanks, Edgar From: , Ohad mailto:[email protected]>> Date: Tuesday, September 2, 2014 at 1:07 AM To: "[email protected]" mailto:[email protected]>> S

Re: [Openstack-operators] Openstack Manual install with nova-network

Have you checked the Horizon configuration setting for OPENSTACK_NEUTRON_NETWORK? Set all enable_* options to False. Possibly this is the way you can configure Horizon not to use Neutron. Would you please try. Thanks, Vishal On Tue, Sep 2, 2014 at 9:59 AM, Baruch, Ohad wrote: > Hi Vishal, > >

Re: [Openstack-operators] RabbitMQ issues since upgrading to Icehouse

Hi Sam, We upgraded to Icehouse over the weekend and had some issues with Rabbit. The number of RabbitMQ connections went from ~70 to ~380 post-upgrade and we had reports of users being unable to use the metadata service and that instances took longer to boot as they waited for metadata. I notic

[Openstack-operators] Ceilometer - cinder meters missing

Hello. I'm setting up metering for the first time. I'm using Icehouse, and - after following the instructions - I'm now seeing samples from most of the services (nova, neutron, swift, and glance).

Re: [Openstack-operators] Ceilometer - cinder meters missing

Hi, You may need to add the cinder-volume-usage-audit script to your crontab: https://github.com/openstack/cinder/blob/master/bin/cinder-volume-usage-audit HTH, Arne On Sep 2, 2014, at 9:26 PM, Mustafa Jamil wrote: > Hello. I'm setting up metering for the first time. I'm using Icehouse, and

Re: [Openstack-operators] Ceilometer - cinder meters missing

Thank you Arne. That was it. On Tue, Sep 2, 2014 at 12:39 PM, Arne Wiebalck wrote: > Hi, > > You may need to add the cinder-volume-usage-audit script to your crontab: > > https://github.com/openstack/cinder/blob/master/bin/cinder-volume-usage-audit > > HTH, > Arne > > On Sep 2, 2014, at 9:26 P

[Openstack-operators] Monitoring RabbitMQ

Hi all, The topic of RabbitMQ related issues came up at last week's operator meetup in San Antonio. I meant to give some more detail to a couple of the attendees on Tuesday but was unable to attend. Here's a blog post that goes over a few of the ways to help with issues that could be RabbitMQ rel

Re: [Openstack-operators] RabbitMQ issues since upgrading to Icehouse

What release were you running before Icehouse? I’m curious if you purged/deleted queues during the upgrade. Might be useful to start fresh with your rabbit, like completely trash your mensia during a maintenance window (obviously with your services stopped) so they recreate the queues at startup.

Re: [Openstack-operators] memcached redundancy

On Thu, 14 Aug 2014 10:09:59 -0600 Joe Topjian wrote: > But if I take a server down for maintenance, I notice a 2-3 second delay in > all requests. I've confirmed it's memcached by editing the list of > memcached servers in the config files and the delay goes away. This is odd. When memcached is

Re: [Openstack-operators] RabbitMQ issues since upgrading to Icehouse

Hi Abel, We were running Havana on Precise before. We moved to Icehouse on Trusty. So new kombu etc. too. We also moved to new rabbit servers so all the queues were fresh etc. Joe: Yeah we have metadata_workers set to 2 also, a little gotcha for the icehouse upgrade. Cheers, Sam On 3 Sep 20

Re: [Openstack-operators] Monitoring RabbitMQ

On Tue, Sep 2, 2014 at 2:25 PM, Andy Hill wrote: > > http://virtualandy.wordpress.com/2014/09/02/operating-openstack-monitoring-rabbitmq/ Nice writeup Andy, thanks for sharing! ___ OpenStack-operators mailing list [email protected].

Re: [Openstack-operators] RabbitMQ issues since upgrading to Icehouse

What was the problem with metadata workers set to 2 ? Tim > -Original Message- > From: Sam Morrison [mailto:[email protected]] > Sent: 03 September 2014 00:55 > To: Abel Lopez > Cc: [email protected]; [email protected] > Subject: Re: [Openstack-operators

Re: [Openstack-operators] RabbitMQ issues since upgrading to Icehouse

No problem setting it to 2, the problem arises when you upgrade to icehouse the default for metadata workers has changed from 1 -> number of processes. So if you don’t change your config you’ll all of a sudden get a lot more nova-api-metadata servers running. (If you’re using multi host and have

Re: [Openstack-operators] neutron debug messages

Hi, Yeah that's already the case but I keep seeing them though :/ Thanks Alex On 2 Sep 2014 14:21, "vishal yadav" wrote: > Make sure you have set *debug = False* both in *neutron.conf* and agent > configuration (*metadata_agent.ini* in this case from example message). > > Thanks, > Vishal > >