[openstack-dev] [Nova] Cells conversation starter
loy wolfe
loywolfe at gmail.com
Thu Oct 23 01:45:28 UTC 2014
I suspect whether cell itself could ease large scale deployment across
multiple DC. Although openstack is modularized as separated projects,
but top level total solution across projects is needed when
considering issues such as scaling, especially coordination between
nova and network / metering.
Personally +1 to Steve, that in terms of future plans decision for
scaling, we should explore all similar proposals such as Cascading and
Federation. In fact networking and metering face the same challenge as
nova, or even more with l2pop and dvr. Those two proposals both bring
total solution across projects besides nova, with each has its own
emphasis by the view of intra vs. inter admin domain.
On Thu, Oct 23, 2014 at 8:11 AM, Sam Morrison <sorrison at gmail.com> wrote:
>
>> On 23 Oct 2014, at 5:55 am, Andrew Laski <andrew.laski at rackspace.com> wrote:
>>
>>> While I agree that N is a bit interesting, I have seen N=3 in production
>>>
>>> [central API]-->[state/region1]-->[state/region DC1]
>>> \->[state/region DC2]
>>> -->[state/region2 DC]
>>> -->[state/region3 DC]
>>> -->[state/region4 DC]
>>
>> I would be curious to hear any information about how this is working out. Does everything that works for N=2 work when N=3? Are there fixes that needed to be added to make this work? Why do it this way rather than bring [state/region DC1] and [state/region DC2] up a level?
>
> We (NeCTAR) have 3 tiers, our current setup has one parent, 6 children then 3 of the children have 2 grandchildren each. All compute nodes are at the lowest level.
>
> Everything works fine and we haven’t needed to do any modifications.
>
> We run in a 3 tier system because it matches how our infrastructure is logically laid out, but I don’t see a problem in just having a 2 tier system and getting rid of the middle man.
>
> Sam
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
More information about the OpenStack-dev
mailing list