Open Stack

Hi Huang,

Thanks for looking in to my proposal.

Yes, Alliance is will be utilizing/retain all Northbound service APIs, in addition it will expose APIs for inter Alliance (inter cloud) communication. Alliance will be running at topmost layer on each individual OpenStack Cloud of multi-site distributed cloud setup. Additionally Alliance will provide loosely coupled integration among multiple clouds or cloudyfied data center.

In case of multi regions setup “regional Alliance” (RA) will orchestrate the resource (project, VMs, volumes, network ….) provisioning and state synchronization through its peers RA. In case cross enterprise integration (Enterprise/VPC/bursting like scenario) <-----> multi site public cloud) “global Alliance” (GA) will be interface for external integration point and communicating with individual RAs.  I will update the wiki to make it more clear.

I will love to coordinate with your team and solve this issue together,  I will be reaching there in Paris on 1 Nov and we can site f2f before session. Let’s plan a time to meet, Monday will be easy for me.


Thanks,
Arvind



From: joehuang [mailto:joehuang at huawei.com]
Sent: Wednesday, October 01, 2014 5:01 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading


Hi, Tiwari,



Great to know you are also trying to address similar issues. For sure we are happy to work out a common solution for these issues.



I just go through the wiki page, the question for me is "will the Alliance provide/retain current north bound OpenStack API ?". It's very important for the cloud still expose OpenStack API so that the OpenStack API ecosystem will not be lost.



And currently OpenStack cascading has not covered the hybrid cloud (private cloud and public cloud federation), so your project will be a good supplement.



May we have a f2f workshop before the formal Paris design summit, so that we can exchange ideas completely. 40 minutes design summit session is not enough for deep diving. PoC team will stay at Paris from Oct.29 to Nov.8.



Best Regards



Chaoyi Huang ( joehuang )



________________________________
From: Tiwari, Arvind [arvind.tiwari at hp.com]
Sent: 02 October 2014 0:42
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading
Hi Chaoyi,

Thanks for sharing these information.

Sometime back I have stared a project called “Alliance” which trying to address the same concerns (see the link below). Alliance service is designed to provide "Inter-Cloud Resource Federation" which will enable resource sharing across cloud in distributed multi-site OpenStack clouds deployments. This service will run on top of OpenStack Cloud and fabricate different cloud (or data centers) instances in distributed cloud setup. This service will work closely with OpenStack components (Keystone, Nova, Cinder....) to manage and provision different resources (token, VM, images, network .....). Alliance service will provide abstraction to hide interoperability and integration complexities from underpinning cloud instance and enable following business use cases.

- Multi Region Capability
- Virtual Private Cloud
- Cloud Bursting

This service will provide true plug & play model for region expansion, VPC like use case, conceptual design can be found at  https://wiki.openstack.org/wiki/Inter_Cloud_Resource_Federation. We are working on POC using this concept which is in WIP.

I will be happy to coordinate with you on this and try to come up with common solution, seems we both are trying to address same issues.

Thoughts?

Thanks,
Arvind

From: joehuang [mailto:joehuang at huawei.com]
Sent: Wednesday, October 01, 2014 6:56 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading

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#<http://junodesignsummit.sched.org/event/a0d38e1278182eb09f06e22457d94c0c>
[2] https://etherpad.openstack.org/p/juno-nova-clustered-hypervisor-support




From:        joehuang <joehuang at huawei.com<mailto:joehuang at huawei.com>>
To:        "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto: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<mailto: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/20141002/f66b0bfc/attachment.html>