tungstenfabric/website

Tungsten-Fabric-Architecture-CN chinese translation incorrect

Closed this issue · 7 comments

In file https://github.com/tungstenfabric/website/blob/master/L10N/Tungsten-Fabric-Architecture-CN.md charter Kubernetes Containers with Tungsten Fabric {#tf-kubernetes} .
1.The English original text is
"Each pod in a service is allocated a unique IP addresses within a virtual network, and also a floating IP address which is the same for all the pods in a service."

The Chinese translation text is
"服务中的每个容器在虚拟网络中分配唯一的IP地址,并且还为服务中的所有容器分配浮动IP地址"

For Chinese it should be
"服务中的每个POD在虚拟网络中分配唯一的IP地址,并且还为服务中的所有POD分配一个浮动IP地址"

2. The English original text is
“When traffic is sent from a pod to a service IP, the vRouter attached to that pod performs ECMP load-balancing using the routes to the service IP address that resolve to the interfaces of the individual pods that form the destination service.”

The Chinese translation text is
"当流量从容器发送到服务IP时,连接到该容器的vRouter将使用到服务IP地址的路由执行ECMP负载平衡,该服务IP地址将解析为构成目标服务的各个容器的接口。"

For Chinese it should be
"当流量从POD发送到服务IP时,连接到该POD的vRouter将使用到服务IP地址的路由执行ECMP负载平衡,该服务IP地址将解析为构成目标服务的各个POD的接口。"

The "容器" must be "POD".
When I read out the Chinese text, I was confused that allocating a unique IP address for each containers.

@ocean1598 Could you have a look?

/cc @randybias

I'd like the comments. @ccccbjcn , thanks.

I'd like the comments. @ccccbjcn , thanks.

My pleasure. Thanks.

Hey @ocean1598 can you make a pull request with this change pretty please?

Hi @ocean1598, TF uses XMPP protocol to connect controller and vRouter, is controller as XMPP Server role and vRouter is the Client role? Why we use protocol as the connection protocol?
Thanks.