The following pull request was submitted through Github. It can be accessed and reviewed at: https://github.com/lxc/linuxcontainers.org/pull/319
This e-mail was sent by the LXC bot, direct replies will not reach the author unless they happen to be subscribed to this list. === Description (from pull-request) === Reported-by: Yuta Kurosaki <[email protected]> Signed-off-by: KATOH Yasufumi <[email protected]>
From 6155802f9c9b73afa2830863844cf438a814d429 Mon Sep 17 00:00:00 2001 From: KATOH Yasufumi <[email protected]> Date: Sat, 18 Aug 2018 01:03:40 +0900 Subject: [PATCH] Fix typo in Japanese LXD 3.4 announcement Reported-by: Yuta Kurosaki <[email protected]> Signed-off-by: KATOH Yasufumi <[email protected]> --- content/lxd/news.ja/lxd-3.4.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/lxd/news.ja/lxd-3.4.yaml b/content/lxd/news.ja/lxd-3.4.yaml index 1293b1f..6838da5 100644 --- a/content/lxd/news.ja/lxd-3.4.yaml +++ b/content/lxd/news.ja/lxd-3.4.yaml @@ -88,7 +88,7 @@ content: |- <!-- One problem several users ran into when running a LXD cluster using the Ubuntu Fan as an overlay network was that even though all traffic was properly routed between the various nodes, attempting to resolve the name of a container would only work if it happened to be running on the same cluster node. --> - オーバーレイ・ネットワークとして、Ubuntu の Fan を使っている LXD クラスターを実行しているユーザの問題のひとつに、様々なノード間ですべてのオラフィックが適切にルーティングされていても、同じクラスタノード上で実行中の場合のみ、コンテナの名前解決が働くというものがありました。 + オーバーレイ・ネットワークとして、Ubuntu の Fan を使っている LXD クラスターを実行しているユーザの問題のひとつに、様々なノード間ですべてのトラフィックが適切にルーティングされていても、同じクラスタノード上で実行中の場合のみ、コンテナの名前解決が働くというものがありました。 <!-- LXD 3.4 changes that by now attempting to resolve DNS queries for the network's defined domain (`lxd` by default) against all of the nodes until one returns a value, making it feel like it's all handled by a single unified DNS server.
_______________________________________________ lxc-devel mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-devel
