[Openstack-operators] Three Node Deployment Model

Hossein Zabolzadeh zabolzadeh at gmail.com
Sun Oct 26 14:55:42 UTC 2014


Really thanks for your opinion.

On 10/26/14, Juan José Pavlik Salles <jjpavlik at gmail.com> wrote:
> Hi Hossein, I wouldn't use a VM from the cloud as a controller failover, it
> would complicate things unnecessarily. What I would do is: use one of the
> compute nodes a controller failover.  You can install the APIs easily on
> the compute node and the rest of the software too.
>
> 2014-10-26 10:38 GMT-03:00 Hossein Zabolzadeh <zabolzadeh at gmail.com>:
>
>> With three node deployment in mind(one controller and 2 compute
>> nodes), in order to acheive minimum HA with threse three physical
>> nodes, is it possible to setup second controller as a virtual machine
>> on one of my compute node?
>> Does this approach improve HA in my deployment(atleast until my other
>> physical nodes become available)?
>> Thanks in advance.
>>
>> On 10/25/14, Hossein Zabolzadeh <zabolzadeh at gmail.com> wrote:
>> > Thanks for your useful answers.
>> > Very helpful resource and guides.
>> >
>> > On 10/23/14, Adam Lawson <alawson at aqorn.com> wrote:
>> >> Your dilemna looks like this as I see it:
>> >>
>> >> Highly-Available, Highly-Scalable, Limited Hardware. Pick any 2.
>> >>
>> >> In an ideal world we'd all like the benefits of everything with
>> >> limited
>> >> resources. True HA requires some meaningful separation (logical
>> >> fencing
>> >> if
>> >> you will). You can't do that with only 3 nodes so you need to make
>> >> some
>> >> concessions. Starting with motivation that begins your efforts within
>> >> Openstack Docs per Anne. ; )
>> >>
>> >> Mahalo,
>> >> Adam
>> >>
>> >>
>> >> *Adam Lawson*
>> >>
>> >> AQORN, Inc.
>> >> 427 North Tatnall Street
>> >> Ste. 58461
>> >> Wilmington, Delaware 19801-2230
>> >> Toll-free: (844) 4-AQORN-NOW ext. 101
>> >> International: +1 302-387-4660
>> >> Direct: +1 916-246-2072
>> >>
>> >>
>> >> On Thu, Oct 23, 2014 at 10:58 AM, Anne Gentle <anne at openstack.org>
>> wrote:
>> >>
>> >>>
>> >>>
>> >>> On Tue, Oct 21, 2014 at 2:43 PM, Hossein Zabolzadeh
>> >>> <zabolzadeh at gmail.com>
>> >>> wrote:
>> >>>
>> >>>> Hi there,
>> >>>> I have an openstack deployment question. I have three physical
>> >>>> server(Configurations are listed in the following). What is the best
>> >>>> optimized production-ready deployment model to achieve the following
>> >>>> goals in mind(Users will not exceeds more than 10)?
>> >>>> - Ability to add more services(compute, controller, storage node)
>> >>>> later, without service interruption
>> >>>> - Ability to provide HA for all services, after more nodes added
>> >>>> without service interruption
>> >>>> - No need to change the deployment architecture later when more
>> >>>> physical nodes and resources available(My physical infrastructure
>> >>>> will
>> >>>> be scaled later, and not limitted to these three physical machines).
>> >>>> For example I don't know is it better to have 1 neutron node, or
>> >>>> have
>> >>>> two neutron service on my two compute nodes?
>> >>>>
>> >>>
>> >>> Hi - Have you read:
>> >>> http://docs.openstack.org/openstack-ops/content/scaling.html
>> >>>
>> >>> and
>> >>>
>> >>>
>> >>>
>> http://docs.openstack.org/openstack-ops/content/example_architecture.html#example_architecture-neutron
>> >>>
>> >>> Horizontal scaling is covered in these as well as your neutron
>> question.
>> >>>
>> >>> Anne
>> >>>
>> >>>
>> >>>
>> >>>> A really appreciate any helps.
>> >>>> Thanks in advance.
>> >>>> ------
>> >>>> Server 1:
>> >>>> RAM: 128GB
>> >>>> HDD: 300GB
>> >>>> ------
>> >>>> Server 2:
>> >>>> RAM: 128GB
>> >>>> HDD: 300GB
>> >>>> ------
>> >>>> Server 3:
>> >>>> RAM: 256GB
>> >>>> HDD: 512GB
>> >>>>
>> >>>> _______________________________________________
>> >>>> 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
>> >>>
>> >>>
>> >>
>> >
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
>
> --
> Pavlik Salles Juan José
> Blog - http://viviendolared.blogspot.com
>



More information about the OpenStack-operators mailing list