Hello,
Tricircle is a project to provide tenant level L2/L3 overlay networking
automation across Neutron in multi-region OpenStack deployments.
The cross OpenStack networking topology can be composed mainly from four
concepts:
Local Network
- Local Network is a network which can only reside in one OpenStack cloud.
- Network type could be VLAN, VxLAN, Flat.
Local Router
- Local Router is a logical router which can only reside in one OpenStack
cloud.
Cross OpenStack L2 Network
- Cross OpenStack L2 Network is a network which can be streched into more
than one OpenStack cloud.
- Also called cross Neutron L2 network, or cross pod L2 network.
- Network type could be VLAN, VxLAN, Flat.
Non-Local Router
- Non-Local Router will be able to reside in more than one OpenStack cloud,
and internally inter-connected with bridge network.
- Bridge network used internally for non-local router is a special cross
OpenStack L2 network.
- Local networks or cross OpenStack L2 networks can be attached to local
router or non-local routers if the network can be presented to the region
where the router can reside.
With these four concepts, various typologies could be composed:
- Instances in different OpenStack clouds can be attached to a cross
OpenStack L2 network directly, so that they can communicate with
each other no matter in which OpenStack cloud.
- Local router can be set gateway with external networks to support
north-south traffic handled locally.
- Non-local router can work only for cross OpenStack east-west networking
purpose if no external network is set to the router.
- Non-local router can serve as the centralized north-south traffic gateway
if external network is attached to the router, and support east-west
traffic at the same time.
Several typical cross OpenStack networking topology have been supported in
Tricircle Pike1.5, just released on May.2:
1. Multiple North-South gateways with East-West Networking enabled
-
https://docs.openstack.org/developer/tricircle/networking-guide-multiple-ns-with-ew-enabled.html
2. North South Networking via Single External Network
-
https://docs.openstack.org/developer/tricircle/networking-guide-single-external-network.html
3. North South Networking via Multiple External Networks
-
https://docs.openstack.org/developer/tricircle/networking-guide-multiple-external-networks.html
4. North South Networking via Direct Provider Networks
-
https://docs.openstack.org/developer/tricircle/networking-guide-direct-provider-networks.html
Now you can experience these networking automation capabilities through
devstack, the installation guide is also available:
-
https://docs.openstack.org/developer/tricircle/installation-guide.html#multi-pod-installation-with-devstack
If you want to learn more about the networking automation provided by
Tricircle, the wiki page of Tricircle is an entrance to the project:
- https://wiki.openstack.org/wiki/Tricircle
Two sessions in OpenStack Boston Summit are also good start point.
1. When One Cloud is Not Enough: An Overview of Sites, Regions...
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18076/
2. Tricircle - Project Onboarding.
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18701
And in OPNFV Beijing Summit in June, one PoC demo will be done to show how
Tricircle networking capability can help VNF(telecom application) to achieve
high availability across OpenStack clouds(or multi-sites):
https://docs.google.com/presentation/d/16Qfm3D1yhrW31ZEVRYea8mcyKI06fQ3a6Okk4VhFGkQ/
.
Feel free to ping us in mail-list or IRC if you have any topic to be discussed.
Very keen to get your feedback on the networking requirements and expectation,
and discuss in more detail f2f if needed.
Best Regards
Chaoyi Huang (joehuang)
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
