Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
L
lxc
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Chen Yisong
lxc
Commits
0332ef2c
Unverified
Commit
0332ef2c
authored
Jun 19, 2020
by
Christian Brauner
Committed by
Stéphane Graber
Jun 19, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: update terminology
Signed-off-by:
Christian Brauner
<
christian.brauner@ubuntu.com
>
parent
b15eb500
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
19 additions
and
19 deletions
+19
-19
lxc.container.conf.sgml.in
doc/ja/lxc.container.conf.sgml.in
+10
-10
lxc.container.conf.sgml.in
doc/lxc.container.conf.sgml.in
+9
-9
No files found.
doc/ja/lxc.container.conf.sgml.in
View file @
0332ef2c
...
...
@@ -713,25 +713,25 @@ by KATOH Yasufumi <karma at jazz.email.ne.jp>
modes are <option>l3</option>, <option>l3s</option> and
<option>l2</option>. It defaults to <option>l3</option> mode.
In <option>l3</option> mode TX processing up to L3 happens on the stack instance
attached to the
slave
device and packets are switched to the stack instance of the
master
device for the L2 processing and routing from that instance will be
used before packets are queued on the outbound device. In this mode the
slav
es
attached to the
dependent
device and packets are switched to the stack instance of the
parent
device for the L2 processing and routing from that instance will be
used before packets are queued on the outbound device. In this mode the
dependent devic
es
will not receive nor can send multicast / broadcast traffic.
In <option>l3s</option> mode TX processing is very similar to the L3 mode except that
iptables (conn-tracking) works in this mode and hence it is L3-symmetric (L3s).
This will have slightly less performance but that shouldn't matter since you are
choosing this mode over plain-L3 mode to make conn-tracking work.
In <option>l2</option> mode TX processing happens on the stack instance attached to
the
slave device and packets are switched and queued to the master
device to send
out. In this mode the
slav
es will RX/TX multicast and broadcast (if applicable) as well.
the
dependent device and packets are switched and queued to the parent
device to send
out. In this mode the
dependent devic
es will RX/TX multicast and broadcast (if applicable) as well.
<option>lxc.net.[i].ipvlan.isolation</option> specifies the isolation mode.
The accepted isolation values are <option>bridge</option>,
<option>private</option> and <option>vepa</option>.
It defaults to <option>bridge</option>.
In <option>bridge</option> isolation mode
slav
es can cross-talk among themselves
apart from talking through the
master
device.
In <option>bridge</option> isolation mode
dependent devic
es can cross-talk among themselves
apart from talking through the
parent
device.
In <option>private</option> isolation mode the port is set in private mode.
i.e. port won't allow cross communication between
slav
es.
i.e. port won't allow cross communication between
dependent devic
es.
In <option>vepa</option> isolation mode the port is set in VEPA mode.
i.e. port will offload switching functionality to the external entity as
described in 802.1Qbg.
...
...
@@ -1548,7 +1548,7 @@ by KATOH Yasufumi <karma at jazz.email.ne.jp>
fstab フォーマットの一行と同じフォーマットのマウントポイントの指定をします。
<!--
Moreover lxc supports mount propagation, such as rs
lave
or
Moreover lxc supports mount propagation, such as rs
hared
or
rprivate, and adds three additional mount options.
<option>optional</option> don't fail if mount does not work.
<option>create=dir</option> or <option>create=file</option>
...
...
@@ -1556,7 +1556,7 @@ by KATOH Yasufumi <karma at jazz.email.ne.jp>
<option>relative</option> source path is taken to be relative to
the mounted container root. For instance,
-->
加えて、LXC では rs
lave
や rprivate といったマウント・プロパゲーションオプションと、独自の 3 つのマウントオプションが使えます。
加えて、LXC では rs
hared
や rprivate といったマウント・プロパゲーションオプションと、独自の 3 つのマウントオプションが使えます。
<option>optional</option> は、マウントが失敗しても失敗を返さずに無視します。
<option>create=dir</option> と <option>create=file</option> は、マウントポイントをマウントする際にディレクトリもしくはファイルを作成します。
<option>relative</option> を指定すると、マウントされたコンテナルートからの相対パスとして取得されます。
...
...
doc/lxc.container.conf.sgml.in
View file @
0332ef2c
...
...
@@ -530,25 +530,25 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
modes are <option>l3</option>, <option>l3s</option> and
<option>l2</option>. It defaults to <option>l3</option> mode.
In <option>l3</option> mode TX processing up to L3 happens on the stack instance
attached to the
slave
device and packets are switched to the stack instance of the
master
device for the L2 processing and routing from that instance will be
used before packets are queued on the outbound device. In this mode the
slav
es
attached to the
dependent
device and packets are switched to the stack instance of the
parent
device for the L2 processing and routing from that instance will be
used before packets are queued on the outbound device. In this mode the
dependent devic
es
will not receive nor can send multicast / broadcast traffic.
In <option>l3s</option> mode TX processing is very similar to the L3 mode except that
iptables (conn-tracking) works in this mode and hence it is L3-symmetric (L3s).
This will have slightly less performance but that shouldn't matter since you are
choosing this mode over plain-L3 mode to make conn-tracking work.
In <option>l2</option> mode TX processing happens on the stack instance attached to
the
slave device and packets are switched and queued to the master device to send
out. In this mode the
slav
es will RX/TX multicast and broadcast (if applicable) as well.
the
dependent device and packets are switched and queued to the parent device to send devices
out. In this mode the
dependent devic
es will RX/TX multicast and broadcast (if applicable) as well.
<option>lxc.net.[i].ipvlan.isolation</option> specifies the isolation mode.
The accepted isolation values are <option>bridge</option>,
<option>private</option> and <option>vepa</option>.
It defaults to <option>bridge</option>.
In <option>bridge</option> isolation mode
slav
es can cross-talk among themselves
apart from talking through the
master
device.
In <option>bridge</option> isolation mode
dependent devic
es can cross-talk among themselves
apart from talking through the
parent
device.
In <option>private</option> isolation mode the port is set in private mode.
i.e. port won't allow cross communication between
slav
es.
i.e. port won't allow cross communication between
dependent devic
es.
In <option>vepa</option> isolation mode the port is set in VEPA mode.
i.e. port will offload switching functionality to the external entity as
described in 802.1Qbg.
...
...
@@ -1164,7 +1164,7 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Specify a mount point corresponding to a line in the
fstab format.
Moreover lxc supports mount propagation, such as rs
lave
or
Moreover lxc supports mount propagation, such as rs
hared
or
rprivate, and adds three additional mount options.
<option>optional</option> don't fail if mount does not work.
<option>create=dir</option> or <option>create=file</option>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment