Hello,
With help of Meimei, Tianwei, ZhiYuan, the multisite environment with Tricircle
is ready now:
https://docs.google.com/presentation/d/16Qfm3D1yhrW31ZEVRYea8mcyKI06fQ3a6Okk4VhFGkQ/
Please note that the blade2(i.e RegionTwo) is not on-site now, the blade 2 will
be returned by the end of this week. So there are only RegionOne and
RegionThree in the environment:
* Tricircle is installed in one VM running in RegionOne.
* KeyStone is installed in RegionOne, all regions including Tricricle VM
will share this KeyStone.
* Tricircle's VM has registered a region called CentralRegion in KeyStone,
there is central Neutron with Tricricle too.
* RegionOne and RegionThree have their own external network respectively.
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
Please note that "Multiple North-South gateways with East-West Networking
enabled" is the topology vIMS expected, so you can refer to the guide for vIMS
on-boarding.
Please use current project to test the VMs and networking, there is small issue
in non-configured project, and patch to fix it will be available soon.
Best Regards
Chaoyi Huang (joehuang)
_______________________________________________
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
