Open Stack

Hi Hossein,

This is a pretty open-ended question that can be answered several different
ways.

Have you read through both the Operators Guide
<http://docs.openstack.org/openstack-ops/content/> and Architecture Design
Guide <http://docs.openstack.org/arch-design/content/>? Both of those docs
might contain some useful advise. There's also a High Availability Guide
<http://docs.openstack.org/high-availability-guide/content/index.html>,
though I believe it's going through a rewrite at the moment.

My personal opinion for three nodes is to allocate one node for the
controller services (keystone, glance, nova-api, etc) and the other two for
compute. When you're able to add more nodes to the cloud, dedicate one as
the second controller to make things HA.

You should be able to add more controller services with minimum service
interruption. I'm not too familiar with Neutron, but from personal
experience, all other OpenStack components scale horizontally very well
behind a load balancer.

If you want to prep your single controller for expansion, begin by
installing a load balancer such as HAProxy on the single controller to pass
all requests to the services running on that same controller. Then when you
get a second controller, you can simply append the new services to the
HAProxy config. You can then introduce something like VRRP or uCARP to
balance a shared IP between the two controllers.

Hope that helps,
Joe




On Thu, Oct 23, 2014 at 4:24 AM, Hossein Zabolzadeh <zabolzadeh at gmail.com>
wrote:

> Appreciated if someone help to find my answer.
> Thanks in advance.
>
> On 10/22/14, Hossein Zabolzadeh <zabolzadeh at gmail.com> wrote:
> > Any idea?
> >
> > On 10/21/14, 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?
> >> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20141023/0e52d209/attachment.html>