Open Stack

So to make sure we are on the same page you are initially maintaining both guide - the current one (active/ passive) and the new one, which uses the new service. But wan't we us - doc'ers maintaining it as any other doc on the website?
For instance my production architecture uses a similar setup and Florian's guide has been of a great help, I really think both implementation can and should exist , since in the end this is not so much an update rather one another way to consider you HA deployment

Razique

Le 27 avr. 2013 à 01:38, Emilien Macchi <emilien.macchi at enovance.com> a écrit :

> Actually, the current guide is not complete since it miss a lot of
> services documented because I did not spend too much time on it.
> I would prefer keep my time for writing Active / Active setup.
> 
> 
> Emilien Macchi
> ----------------------------------------------------
> # OpenStack Engineer
> // eNovance Inc.              http://enovance.com
> // ✉ emilien at enovance.com     ☎ +33 (0)1 49 70 99 80
> // 10 rue de la Victoire 75009 Paris
> 
> On 04/27/2013 12:48 AM, Razique Mahroua wrote:
>> Oh the guide as is works perfectly - you mean an update with the latest OpenStack services were considered?
>> 
>> 
>> Le 27 avr. 2013 à 00:46, Emilien Macchi <emilien.macchi at enovance.com> a écrit :
>> 
>>> My opinion would be to keep only Active / Active mode for at least
>>> OpenStack services, since current active / passive mode is not
>>> completely documented and I have no time to manage it.
>>> 
>>> I think the discussion is now open !
>>> 
>>> Emilien Macchi
>>> ----------------------------------------------------
>>> # OpenStack Engineer
>>> // eNovance Inc.              http://enovance.com
>>> // ✉ emilien at enovance.com     ☎ +33 (0)1 49 70 99 80
>>> // 10 rue de la Victoire 75009 Paris
>>> 
>>> On 04/27/2013 12:17 AM, Razique Mahroua wrote:
>>>> Hey Emilien-man, not a time for us to work now hehe
>>>> Well I think definitely think keeping that one in place is something important - so I propose a separate section definitely
>>>> Active/active explaining as well used packages as well since the current guide doesn't make use of the services you use
>>>> 
>>>> Razique
>>>> 
>>>> Le 26 avr. 2013 à 23:56, Emilien Macchi <emilien.macchi at enovance.com> a écrit :
>>>> 
>>>>> Hi,
>>>>> 
>>>>> 
>>>>> Today the OpenStack HA guide written by Florian Haas and my self needs
>>>>> to be updated from active / passive to active / active mode.
>>>>> Since some services have been updated in Grizzly, I would like to submit
>>>>> a new documentation explaining how to configure this setup :
>>>>> 
>>>>> - API nodes (all OpenStack APIs) -> load balanced by HAproxy (I'll share
>>>>> my running configuration)
>>>>> - Scheduler nodes (*-scheduler + nova-conductor) -> Multiple running :
>>>>> horizontal scale
>>>>> - Compute nodes (nova-compute + Quantum L3 Agent + Quantum DHCP Agent +
>>>>> Quantum L2 Agent + Quantum Metadata Agent) : no HA, but scaling of
>>>>> Quantum L3 & DHCP agents
>>>>> - Storage node (cinder-volume) -> can't be run in full HA as far I know.
>>>>> - RabbitMQ cluster
>>>>> - MySQL Cluster (Galera)
>>>>> 
>>>>> Then, I'll like to know what is the best choice :
>>>>> - Split the guide in two parts : Active / Active & Active / Passive ?
>>>>> - Drop Active / Passive part and updating it for Active / Active setup ?
>>>>> 
>>>>> Before submitting my patches, let me know your thoughts.
>>>>> 
>>>>> Note : Please don't hesitate to share your feedback if you also run
>>>>> OpenStack in production with HA.
>>>>> 
>>>>> 
>>>>> Cheers,
>>>>> 
>>>>> -- 
>>>>> Emilien Macchi
>>>>> ----------------------------------------------------
>>>>> # OpenStack Engineer
>>>>> // eNovance Inc.              http://enovance.com
>>>>> // ✉ emilien at enovance.com     ☎ +33 (0)1 49 70 99 80
>>>>> // 10 rue de la Victoire 75009 Paris
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Openstack-docs mailing list
>>>>> Openstack-docs at lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>> 
> 
>