Jump to: navigation, search

Difference between revisions of "Tricircle"

(Current active participants)
(Current active participants)
Line 118: Line 118:
 
Pengfei Shi, OMNI Lab
 
Pengfei Shi, OMNI Lab
  
Yipei Niu
+
Yipei Niu, Huazhong University of Science and Technology
  
 
Howard Huang, Huawei
 
Howard Huang, Huawei

Revision as of 08:19, 10 March 2016

Overview

Tricircle is an OpenStack project that aims to deal with OpenStack deployment across multiple sites, and provides a Extension as a Service. Tricircle would enable user to have a single management view by having only one Tricircle instance on behalf of all the involved OpenStack instances. Tricircle essentially serves as the central OpenStack API calls gateway to other OpenStack instances that are called upon.

Tricircle is the formal open source project for OpenStack cascading solution ( https://wiki.openstack.org/wiki/OpenStack_cascading_solution ).

Currently there have been various good sub-projects within different OpenStack projects that try to solve the same problem as Tricircle does, however when OpenStack is deployed in the real world, a suite of OpenStack projects need to be deployed together rather than individual one. That puts additional difficulties on the cross site multi-openstack-instances deployment. Builds upon that, the management of such deployment would make it sounds even impossible to deal with.

Here in Tricircle, we try to solve this problem by defining a unified approach that would apply to any OpenStack projects, as well as providing a plugable structure that is extensible and has minimal impact on the main in-tree code.

Tricircle could be extended to support more powerful capabilities such as support the central Tricircle instance being virtually splitted into multiple micro instances which could enable user to have a more fine granularity on the tenancy and service. And the Tricircle also enables OpenStack based hybrid cloud.

Architecture

The cascading solution based on PoC design with enhancement is running in several production clouds like Huawei Public Cloud in China, which brings the confidence of the value of cascading, here the focus is on how to design and develop a perfect cascading solution in open source.

The initial architectural in the PoC is stateful, which could be found in https://wiki.openstack.org/wiki/OpenStack_cascading_solution, and the major notorious part identified in the PoC are status synchronization for VM,Volume, etc, UUID mapping and coupling with OpenSatck existing services like Nova, Cinder.

Now Tricircle will be developed with stateless design to remove the challenges, and fully decouple with OpenStack services. An improved design is discussed and developed in https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g/edit?usp=sharing,

Stateless Architecture

Tricircle improved architecture design - stateless


Admin API

  • expose api for administrator to manage the cascading
  • manage sites and availability zone mapping
  • retrieve resource routing
  • expose api for maintenance

Nova API-GW

  • an standalone web service to receive all nova api request, and routing the request to regarding bottom OpenStack according to Availability Zone ( during creation ) or resource id ( during operation and query ).
  • work as stateless service, and could run with processes distributed in mutlti-hosts.

Cinder API-GW

  • an standalone web service to receive all cinder api request, and routing the request to regarding bottom OpenStack according to Availability Zone ( during creation ) or resource id ( during operation and query ).
  • work as stateless service, and could run with processes distributed in mutlti-hosts.

XJob

  • receive and process cross OpenStack functionalities and other aync. jobs from message bus
  • for example, when booting a VM for the first time for the project, router, security group rule, FIP and other resources may have not already been created in the bottom site, but it’s required. Not like network,security group, ssh key etc resources they must be created before a VM booting, these resources could be created in async.way to accelerate response for the first VM booting request
  • cross OpenStack networking also will be done in async. jobs
  • Any of Admin API, Nova API-GW, Cinder API-GW, Neutron Tricircle plugin could send an async. job to XJob through message bus with RPC API provided by XJob

Neutron Tricircle plugin

  • Just like OVN Neutron plugin, the tricircle plugin serve for multi-site networking purpose, including interaction with DCI SDN controller, will use ML2 mechnism driver interface to call DCI SDN controller, especially for cross OpenStack provider multi-segment L2 networking.

DB

  • Tricircle can have its own database to store sites, availability zone mapping, jobs, resource routing tables

FAQ

Q: What is the different between Tricircle and OpenStack Cascading?

OpenStack Cascading was mainly an implementation method used in a PoC done in late 2014 and early 2015, which aims to test out the idea that multiple OpenStack instances COULD be deployed across multiple geo-diverse sites. After the PoC was carried out successfully, the team then planned to contribute the core idea to the community.

Tricircle Project was born out of that idea, however got a different shape and focus. Unlike what is usually part of in a PoC, which has plenty twists and plumbers of feature enhancements, Tricircle in its earliest stage tries to build a clean architecture that is extendable, pluggable and reusable in nature.

In short, OpenStack Cascading is a specific deployment solution used for production purpose, while Tricircle represents an idea of one type of services, like Neutron or Murano, that in the future could be applied to OpenStack Ecosystem.

Q: What are the use cases for Tricircle ?

Use Cases for Tricircle could be found in Telco WG documents, Large Deployment Team Use Cases, and OPNFV Multisite Use Cases


Q: What is the goal of Tricircle?

In short term, Tricircle would focus on developing a robust architecture and related features, in a long run, we hope we could successfully establish a paradigm that could be applied to the whole OpenStack community

Q: How can I set up Tricircle hand by hand ?

Yes, some volunteers sucessfully set up the Tricircle in 3 VMs with virtualbox in Ubuntu 14.04 LTS. The blog can be found in this

To do list

To do list is in the etherpad: https://etherpad.openstack.org/p/TricircleToDo

How to contribute

  1. Clone https://github.com/openstack/tricircle
  2. Make the changes to your entry, be sure to include what’s changed and why
  3. Commit the change for review
  4. The changes will be reviewed, merged within a day or so.

Tricircle is designed to use the same tools for submission and review as other OpenStack projects. As such we follow the OpenStack development workflow. New contributors should follow the getting started steps before proceeding, as a Launchpad ID and signed contributor license are required to add new entries.

The Tricircle Launchpad page can be found at https://launchpad.net/tricircle. Register BP or report bug in https://launchpad.net/tricircle

Community

We have regular weekly meetings at #openstack-meeting on every Wednesday starting from UTC 13:00.

You are also welcomed to discuss issues you cared about using openstack-dev mailing list with [Tricircle] in the mail title. I believe our team member would be quite responsible :)

Meeting minutes and logs

all meeting logs and minutes could be found in
2016: http://eavesdrop.openstack.org/meetings/tricircle/2016/
2015: http://eavesdrop.openstack.org/meetings/tricircle/2015/

Team Member

Contact team members in IRC channel: #openstack-tricircle

Current active participants

Joe Huang, Huawei

Khayam Gondal, Dell

Shinobu Kinjo, RedHat

Vega Cai, Huawei

Pengfei Shi, OMNI Lab

Yipei Niu, Huazhong University of Science and Technology

Howard Huang, Huawei