Open Stack

Hello,  Alex,

Thank you very much for your mail about remote cluster hypervisor.

One of the inspiration for OpenStack cascading is from the remote clustered hypervisor like vCenter. The difference between the remote clustered hypervisor and OpenStack cascading is that not only Nova involved in the cascading, but also Cinder, Neutron, Ceilometer, and even Glance(optional).

Please refer to https://wiki.openstack.org/wiki/OpenStack_cascading_solution#Inspiration,
https://wiki.openstack.org/wiki/OpenStack_cascading_solution#Architecture for more detail information.

Best Regards

Chaoyi Huang ( joehuang )

________________________________
From: Alex Glikson [GLIKSON at il.ibm.com]
Sent: 01 October 2014 12:51
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading

This sounds related to the discussion on the 'Nova clustered hypervisor driver' which started at Juno design summit [1]. Talking to another OpenStack should be similar to talking to vCenter. The idea was that the Cells support could be refactored around this notion as well.
Not sure whether there have been any active progress with this in Juno, though.

Regards,
Alex


[1] http://junodesignsummit.sched.org/event/a0d38e1278182eb09f06e22457d94c0c#
[2] https://etherpad.openstack.org/p/juno-nova-clustered-hypervisor-support




From:        joehuang <joehuang at huawei.com>
To:        "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date:        30/09/2014 04:08 PM
Subject:        [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading
________________________________



Hello, Dear TC and all,

Large cloud operators prefer to deploy multiple OpenStack instances(as different zones), rather than a single monolithic OpenStack instance because of these reasons:

1) Multiple data centers distributed geographically;
2) Multi-vendor business policy;
3) Server nodes scale up modularized from 00's up to million;
4) Fault and maintenance isolation between zones (only REST interface);

At the same time, they also want to integrate these OpenStack instances into one cloud. Instead of proprietary orchestration layer, they want to use standard OpenStack framework for Northbound API compatibility with HEAT/Horizon or other 3rd ecosystem apps.

We call this pattern as "OpenStack Cascading", with proposal described by [1][2]. PoC live demo video can be found[3][4].

Nova, Cinder, Neutron, Ceilometer and Glance (optional) are involved in the OpenStack cascading.

Kindly ask for cross program design summit session to discuss OpenStack cascading and the contribution to Kilo.

Kindly invite those who are interested in the OpenStack cascading to work together and contribute it to OpenStack.

(I applied for “other projects” track [5], but it would be better to have a discussion as a formal cross program session, because many core programs are involved )


[1] wiki: https://wiki.openstack.org/wiki/OpenStack_cascading_solution
[2] PoC source code: https://github.com/stackforge/tricircle
[3] Live demo video at YouTube: https://www.youtube.com/watch?v=OSU6PYRz5qY
[4] Live demo video at Youku (low quality, for those who can't access YouTube)：http://v.youku.com/v_show/id_XNzkzNDQ3MDg4.html
[5] http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg36395.html

Best Regards
Chaoyi Huang ( Joe Huang )
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141001/9a4dd6aa/attachment.html>