Open Stack

It's totally okay to use regions as AZs if that's what you need,
unless you are planning to deploy in another city. Then you will be
already exhausting the term region and you will have been left with
much more to deal with. Ultimately it comes down to needs and future
plans.

Secondly, I think you should be fine with a single cell anyway as we
have much more in one cell. However experience may vary depending on
the volume and characteristics of the daily workload and the design of
the control plane, so maybe you should take someone else's word with
more in-depth knowledge for the guidance.

Cheers.

On Wed, 5 Apr 2023 at 18:47, Satish Patel <satish.txt at gmail.com> wrote:
>
> Folks,
>
> This is a very broad question and could have many answers but still wanted to ask to see what people are thinking and doing.
>
> We have DC with multiple racks and around 600 nodes so we are planning to create 3 private openstack and each with 200 nodes. In other data centers we have multiple 200 nodes openstack clusters and life is good. In the new datacenter I am thinking of deploying the same way openstack but shared keystone between multiple openstack environments to have a single place for identification and I am going to call it 3 regions even it's in a single DC. Hope shared keystone is helpful/easier for doing terrafrom work and selecting region easily.
>
> Other option I was thinking about to deploy cellv2 technology and put all 600 nodes in single cloud but always worried for operation point of view. Now sure how many people running cellv2 successfully without pain. (Except CERN)
>
> If people running multi-region openstack cloud then please share some thought and idea to make life easier. Not looking for best solution but just clue to get idea to deploy and manage multiple openstack.
>
> Thanks in advance.
> S
>
>