Open Stack

On my setup, they run as active / active by the way, since I'm using memcached for storing tokens. 



----- Original Message -----

From: "Razique Mahroua" <razique.mahroua at gmail.com> 
To: "Emilien Macchi" <emilien.macchi at enovance.com> 
Cc: "Juan José Pavlik Salles" <jjpavlik at gmail.com>, openstack-operators at lists.openstack.org 
Sent: Monday, May 13, 2013 10:15:11 AM 
Subject: Re: [Openstack-operators] Problem with multiple nova-consoleauth 

Hi, 
I myself use two instances of console-auth, but they act as active/ passive via Pacemaker/ Corosync 

regards, 

Razique Mahroua - Nuage & Co 
razique.mahroua at gmail.com 
Tel : +33 9 72 37 94 15 


Le 13 mai 2013 à 09:38, Emilien Macchi < emilien.macchi at enovance.com > a écrit : 




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 


----- Original Message -----

From: "Juan José Pavlik Salles" < jjpavlik at gmail.com > 
To: "Sam Morrison" < sorrison at gmail.com > 
Cc: 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 > 

<blockquote>

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 > wrote: 


<blockquote>



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 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators 





</blockquote>




-- 
Pavlik Salles Juan José 

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

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

</blockquote>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130513/a8872e19/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NUAGECO-LOGO-Fblan_petit.jpg
Type: image/jpeg
Size: 10122 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130513/a8872e19/attachment.jpg>