Open Stack

On 9 May 2013 16:16, Dan Smith <dms at danplanet.com> wrote:
>> We now have two different types of drivers: those that manage
>> individual hypervisor nodes, and those that proxy to much more
>> complex systems.
>
> I really suspect that consuming a complex system like vCenter at the
> virt layer is the wrong approach and likely to quickly become a mess of
> trying to push features of these less-cloudy systems up several layers
> in the stack so they are exposed to the user. I think we learned that
> lesson with the baremetal stuff.

I think the issues are extremely similar to baremetal vs single hypervisor.

> Another approach I've thought about is to consume these large systems
> at the cells layer. Right now, I think a vCenter or oVirt deployment
> looks a lot like a child cell in Nova, in that it implements a
> scheduler, provides compute nodes, and (presumably) consumes services
> from Glance, Quantum, etc. If (yes, it's a big "if") the cells interface
> was codified in such a way that other things could implement it, then we
> could presumably have aggregation of Nova compute resources with
> vCenter resources as children under a single parent API cell.

+1

In a previous existence I looked into having CloudStack clouds as a
child cell (at the time a zone), for very similar reasons. Mostly it
was to get support for XenAPI pool features, but same difference.