Skip to content

Latest commit

 

History

History
176 lines (123 loc) · 2.99 KB

EN_README.md

File metadata and controls

176 lines (123 loc) · 2.99 KB
Raw

cframe

cframe is a vpc peering product which is used connect different cloud provider(eg: aws, aliyun, tencent cloud).

How it works

cframe is a CUPS like project. it contains controller and edge.

edge is our data plane, it gets other edges from controller, routes, and finally forwards packet to peer via UDP.

controller is our control plane, she export http api to users to configure edge and dispatch configuration to edge via tcp longlive connection.

doc/images/cframe1.0.0

Get start

In this case, will will use cframe to connect aliyun and tencent cloud, we make 3 vpc connects via internal ip

VPCs and cloud server

  • VPC1, aliyun ShenZhen.

vpc cidr: 172.18.0.0/16

internal ip role
172.18.171.245 edge + controller
172.18.171.247 -
  1. VPC2, aliyun HongKong

vpc cidr: 172.31.0.0/16

internal ip role
172.31.185.158 edge
172.31.185.159 -
  1. VPC3 tengcent cloud GuangZhou

vpc cidr: 172.20.0.0/16

internal ip role
172.20.0.9 edge
172.20.0.13 -

our goal is to connect other two vpc via internal ip address.

step1: build controller and edge

./build.sh

it will created dist folder, build, copy configuration file.

dist
├── controller
├── controller.toml
├── edge
└── edge.toml

step2: deploy controller in cloud server

controller.toml:

listen_addr=":58422"
api_addr=":12345"

etcd = [
    "127.0.0.1:2379"
]


[[edges]]
name="sz-1"
# VPC1 public ip
host_addr = "$PIP1:58423"
cidr = "172.18.0.0/16"

[[edges]]
name="hk-1"
# VPC2 public ip
host_addr = "$PIP2:58423"
cidr = "172.31.0.0/16"

[[edges]]
name="gz-3"
host_addr = "$PIP3:58423"
cidr = "172.20.0.0/16"

replace $PIP1, $PIP3, $PIP3 to your vpc public ip.

step3: deploy edge

VPC1 edge.toml

controller="$CONTROLLER_PIP:58422"
name = "sz-1"
listen_addr=":58423"

VPC2 edge.toml

controller="$CONTROLLER_PIP:58422"
name = "hk-1"
listen_addr=":58423"

VPC3 edge.toml

ubuntu@VM-0-9-ubuntu:~$ cat edge/config.toml 
controller="$CONTROLLER_PIP:58422"
name = "gz-3"
listen_addr=":58423"

replace $CONTROLLER_PIP with your controller public ip.

step4: add vpc route entry

we need to add peers cidr to VPC route to make sure the traffic transfer to our edge node

  • in VPC1, add VPC2, VPC3 cidr to VPC route, nexthop to VPC1.edge instance
  • in VPC2, add VPC1, VPC3 cidr to VPC route, nexthop to VPC2.edge instance
  • in VPC3, add VPC1, VPC2 cidr to VPC route, nexthop to VPC3.edge instance

step5: test network connection

Here are some testcases.

  • in VPC1, ping VPC2
ping 172.31.185.158
ping 172.31.185.159
  • in VPC1, ping VPC3
ping 172.20.0.9
ping 172.20.0.13
  • in VPC2, ping VPC1
ping 172.18.171.245
ping 172.18.171.247
  • in VPC2, ping VPC3
ping 172.20.0.9
ping 172.20.0.13
  • in VPC3, ping VPC1
ping 172.18.171.245
ping 172.18.171.247
  • in VPC3, ping VPC2
ping 172.31.185.158
ping 172.31.185.159