Open Stack

Keep in mind there are a couple memcached bugs that were recently resolved in 2013.1.1:

https://bugs.launchpad.net/nova/+bug/1158958
https://bugs.launchpad.net/nova/+bug/1160900

Regards,
Daneyon Hansen
Software Engineer
Email: danehans at cisco.com
Phone: 303-718-0400
http://about.me/daneyon_hansen

From: Emilien Macchi <emilien.macchi at enovance.com<mailto:emilien.macchi at enovance.com>>
Date: Monday, May 13, 2013 1:38 AM
To: Juan José Pavlik Salles <jjpavlik at gmail.com<mailto:jjpavlik at gmail.com>>
Cc: "openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>" <openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>>
Subject: Re: [Openstack-operators] Problem with multiple nova-consoleauth

Hi,


We are running :

  *   2 memcached servers on dedicated nodes
  *   2 nova-consoleauth with memcached_servers flag in nova.conf (don't forget to install python-memcache on nova-consoleauth nodes)
  *   2 nova-html5proxy in load balancing with HAproxy in front-end.

It works fine.


Cheers !


Emilien


________________________________
From: "Juan José Pavlik Salles" <jjpavlik at gmail.com<mailto:jjpavlik at gmail.com>>
To: "Sam Morrison" <sorrison at gmail.com<mailto:sorrison at gmail.com>>
Cc: openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>
Sent: Monday, May 13, 2013 2:37:56 AM
Subject: Re: [Openstack-operators] Problem with multiple nova-consoleauth

Great, thank guys!!, Should i run one memcache server??? instead of running many of them, one in every compute node, using the configuration John Dewey says.


2013/5/12 Sam Morrison <sorrison at gmail.com<mailto:sorrison at gmail.com>>
If you run multiple consoleauths they need to talk to the same memcached server.

Sam


On 12/05/2013, at 11:46 AM, Juan José Pavlik Salles <jjpavlik at gmail.com<mailto:jjpavlik at gmail.com>> wrote:


Hi guys, on friday i was trying to reach my vms through novnc proxy and i ran into some kind of odd behaviour. One every two attempts were successfull so we started watching logs. after a couple of hours stopping and starting services we realized that this strange behaviour was due to we had two nova-consoleauth instances running, one per compute node. We stopped one of the instances a everything started to work just fine, even both novncproxies.
I found this https://bugs.launchpad.net/nova/+bug/989337 but it's suppossed to be fixed in folsom, and i'm running grizzly.

Should i run just one instance of nova-consoleauth?

_______________________________________________

OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators




--
Pavlik Salles Juan José

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130513/4eb5fcfc/attachment.html>