refactor: re-org networkchaos sections
Signed-off-by: Yue Yang <g1enyy0ung@gmail.com>
This commit is contained in:
Yue Yang
parent
8e3ac10e45
commit
a4b0a662f5
|
|
@ -182,14 +182,14 @@ Before creating NetworkChaos experiments, ensure the following:
|
|||
| externalTargets | []string | Indicates the network targets except for Kubernetes, which can be IPv4 addresses or domains. This parameter only works with `direction: to`. | None | No | 1.1.1.1, google.com |
|
||||
| device | string | Specifies the affected network interface | None | No | "eth0" |
|
||||
|
||||
### Description for `action`-related fields
|
||||
## Description for `action`-related fields
|
||||
|
||||
For the Net Emulation and Bandwidth fault types, you can further configure the `action` related parameters according to the following description.
|
||||
|
||||
- Net Emulation type: `delay`, `loss`, `duplicated`, `corrupt`, `rate`
|
||||
- Bandwidth type: `bandwidth`
|
||||
|
||||
#### delay
|
||||
### delay
|
||||
|
||||
Setting `action` to `delay` means simulating network delay fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -218,7 +218,7 @@ The computational model for `correlation` is as follows:
|
|||
|
||||
In the above command, `sigma` is `jitter` and `mu` is `latency`.
|
||||
|
||||
#### reorder
|
||||
### reorder
|
||||
|
||||
Setting `action` to `reorder` means simulating network packet reordering fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -228,7 +228,7 @@ Setting `action` to `reorder` means simulating network packet reordering fault.
|
|||
| correlation | string | Indicates the correlation between this time's length of delay time and the previous time's length of delay time. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| gap | int | Indicates the gap before and after packet reordering | 0 | No | 5 |
|
||||
|
||||
#### loss
|
||||
### loss
|
||||
|
||||
Setting `action` to `loss` means simulating packet loss fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -237,7 +237,7 @@ Setting `action` to `loss` means simulating packet loss fault. You can also conf
|
|||
| loss | string | Indicates the probability of packet loss. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| correlation | string | Indicates the correlation between the probability of current packet loss and the previous time's packet loss. Range of value: [0, 100] | 0 | No | 50 |
|
||||
|
||||
#### duplicate
|
||||
### duplicate
|
||||
|
||||
Set `action` to `duplicate`, meaning simulating package duplication. At this point, you can also set the following parameters.
|
||||
|
||||
|
|
@ -246,7 +246,7 @@ Set `action` to `duplicate`, meaning simulating package duplication. At this poi
|
|||
| duplicate | string | Indicates the probability of packet duplicating. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| correlation | string | Indicates the correlation between the probability of current packet duplicating and the previous time's packet duplicating. Range of value: [0, 100] | 0 | No | 50 |
|
||||
|
||||
#### corrupt
|
||||
### corrupt
|
||||
|
||||
Setting `action` to `corrupt` means simulating package corruption fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -257,7 +257,7 @@ Setting `action` to `corrupt` means simulating package corruption fault. You can
|
|||
|
||||
For occasional events such as `reorder`, `loss`, `duplicate`, and `corrupt`, the `correlation` is more complicated. For specific model description, refer to [NetemCLG](http://web.archive.org/web/20200120162102/http://netgroup.uniroma2.it/twiki/bin/view.cgi/Main/NetemCLG).
|
||||
|
||||
#### rate
|
||||
### rate
|
||||
|
||||
Setting `action` to `rate` means simulating bandwidth rate fault. This action is similar to [bandwidth/rate](#bandwidth) below, however, **the key distinction is that this action can combine with other `netem` actions listed above**. However, if you require more control over the bandwidth simulation such as limiting the buffer size, check the [bandwidth](#bandwidth) action.
|
||||
|
||||
|
|
@ -265,7 +265,7 @@ Setting `action` to `rate` means simulating bandwidth rate fault. This action is
|
|||
| --- | --- | --- | --- | --- | --- |
|
||||
| rate | string | Indicates the rate of bandwidth limit. Allows bit, kbit, mbit, gbit, tbit, bps, kbps, mbps, gbps, tbps unit. bps means bytes per second | | Yes | 1mbps |
|
||||
|
||||
#### bandwidth
|
||||
### bandwidth
|
||||
|
||||
Setting `action` to `bandwidth` means simulating bandwidth limit fault. You also need to configure the following parameters.
|
||||
|
||||
|
|
|
|||
|
|
@ -134,7 +134,7 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
kubectl apply -f ./network-bandwidth.yaml
|
||||
```
|
||||
|
||||
### 字段说明
|
||||
## 字段说明
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
|
|
@ -147,18 +147,18 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
| externalTargets | []string | 表示 Kubernetes 之外的网络目标, 可以是 IPv4 地址或者域名。只能与 `direction: to` 一起工作。 | 无 | 否 | 1.1.1.1, google.com |
|
||||
| device | string | 指定影响的网络设备 | 无 | 否 | "eth0" |
|
||||
|
||||
针对不同的 `action`，还有不同的配置项可以填写。
|
||||
## 不同 `action` 的配置项
|
||||
|
||||
#### Net Emulation
|
||||
### Net Emulation
|
||||
|
||||
| 参数 | 类型 | 说明 | 是否必填 |
|
||||
| --------- | ----------------------- | ------------------------ | -------- |
|
||||
| delay | [Delay](#Delay) | 描述网络的延迟状态 | 否 |
|
||||
| loss | [Loss](#Loss) | 描述网络的丢包状态 | 否 |
|
||||
| duplicate | [Duplicate](#Duplicate) | 描述网络重复包的状态 | 否 |
|
||||
| corrupt | [Corrupt](#Corrupt) | 描述网络包出现错误的状态 | 否 |
|
||||
| delay | [Delay](#delay) | 描述网络的延迟状态 | 否 |
|
||||
| loss | [Loss](#loss) | 描述网络的丢包状态 | 否 |
|
||||
| duplicate | [Duplicate](#duplicate) | 描述网络重复包的状态 | 否 |
|
||||
| corrupt | [Corrupt](#corrupt) | 描述网络包出现错误的状态 | 否 |
|
||||
|
||||
##### Delay
|
||||
### Delay
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
|
|
@ -185,7 +185,7 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
|
||||
其中 `sigma` 为 `jitter`，`mu` 为 `latency`。
|
||||
|
||||
##### Reorder
|
||||
### Reorder
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------- | ------ | -------- | ---- |
|
||||
|
|
@ -193,21 +193,21 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
| correlation | string | 表示发生重新排序的概率与前一次的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| gap | int | 表示乱序将包推后的距离 | 0 | 否 | 5 |
|
||||
|
||||
##### Loss
|
||||
### Loss
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | -------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
| loss | string | 表示丢包发生的概率。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| correlation | string | 表示丢包发生的概率与前一次是否发生的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
|
||||
##### Duplicate
|
||||
### Duplicate
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
| duplicate | string | 表示包重复发生的概率。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| correlation | string | 表示包重复发生的概率与前一次是否发生的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
|
||||
##### Corrupt
|
||||
### Corrupt
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
|
|
@ -216,7 +216,7 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
|
||||
对于 `reorder`，`loss`，`duplicate`，`corrupt` 这些偶发事件，`correlation` 则更为复杂。具体模型描述参考 [NetemCLG](http://web.archive.org/web/20200120162102/http://netgroup.uniroma2.it/twiki/bin/view.cgi/Main/NetemCLG) 。
|
||||
|
||||
#### Bandwidth
|
||||
### Bandwidth
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| -------- | ------ | ------------------------ | ------ | -------- | ----- |
|
||||
|
|
|
|||
|
|
@ -134,7 +134,7 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
kubectl apply -f ./network-bandwidth.yaml
|
||||
```
|
||||
|
||||
### 字段说明
|
||||
## 字段说明
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
|
|
@ -147,18 +147,18 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
| externalTargets | []string | 表示 Kubernetes 之外的网络目标, 可以是 IPv4 地址或者域名。只能与 `direction: to` 一起工作。 | 无 | 否 | 1.1.1.1, google.com |
|
||||
| device | string | 指定影响的网络设备 | 无 | 否 | "eth0" |
|
||||
|
||||
针对不同的 `action`，还有不同的配置项可以填写。
|
||||
## 不同 `action` 的配置项
|
||||
|
||||
#### Net Emulation
|
||||
### Net Emulation
|
||||
|
||||
| 参数 | 类型 | 说明 | 是否必填 |
|
||||
| --------- | ----------------------- | ------------------------ | -------- |
|
||||
| delay | [Delay](#Delay) | 描述网络的延迟状态 | 否 |
|
||||
| loss | [Loss](#Loss) | 描述网络的丢包状态 | 否 |
|
||||
| duplicate | [Duplicate](#Duplicate) | 描述网络重复包的状态 | 否 |
|
||||
| corrupt | [Corrupt](#Corrupt) | 描述网络包出现错误的状态 | 否 |
|
||||
| delay | [Delay](#delay) | 描述网络的延迟状态 | 否 |
|
||||
| loss | [Loss](#loss) | 描述网络的丢包状态 | 否 |
|
||||
| duplicate | [Duplicate](#duplicate) | 描述网络重复包的状态 | 否 |
|
||||
| corrupt | [Corrupt](#corrupt) | 描述网络包出现错误的状态 | 否 |
|
||||
|
||||
##### Delay
|
||||
### Delay
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
|
|
@ -185,7 +185,7 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
|
||||
其中 `sigma` 为 `jitter`，`mu` 为 `latency`。
|
||||
|
||||
##### Reorder
|
||||
### Reorder
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------- | ------ | -------- | ---- |
|
||||
|
|
@ -193,21 +193,21 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
| correlation | string | 表示发生重新排序的概率与前一次的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| gap | int | 表示乱序将包推后的距离 | 0 | 否 | 5 |
|
||||
|
||||
##### Loss
|
||||
### Loss
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | -------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
| loss | string | 表示丢包发生的概率。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| correlation | string | 表示丢包发生的概率与前一次是否发生的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
|
||||
##### Duplicate
|
||||
### Duplicate
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
| duplicate | string | 表示包重复发生的概率。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| correlation | string | 表示包重复发生的概率与前一次是否发生的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
|
||||
##### Corrupt
|
||||
### Corrupt
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
|
|
@ -216,7 +216,7 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
|
||||
对于 `reorder`，`loss`，`duplicate`，`corrupt` 这些偶发事件，`correlation` 则更为复杂。具体模型描述参考 [NetemCLG](http://web.archive.org/web/20200120162102/http://netgroup.uniroma2.it/twiki/bin/view.cgi/Main/NetemCLG) 。
|
||||
|
||||
#### Bandwidth
|
||||
### Bandwidth
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| -------- | ------ | ------------------------ | ------ | -------- | ----- |
|
||||
|
|
|
|||
|
|
@ -134,7 +134,7 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
kubectl apply -f ./network-bandwidth.yaml
|
||||
```
|
||||
|
||||
### 字段说明
|
||||
## 字段说明
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
|
|
@ -147,18 +147,18 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
| externalTargets | []string | 表示 Kubernetes 之外的网络目标, 可以是 IPv4 地址或者域名。只能与 `direction: to` 一起工作。 | 无 | 否 | 1.1.1.1, google.com |
|
||||
| device | string | 指定影响的网络设备 | 无 | 否 | "eth0" |
|
||||
|
||||
针对不同的 `action`，还有不同的配置项可以填写。
|
||||
## 不同 `action` 的配置项
|
||||
|
||||
#### Net Emulation
|
||||
### Net Emulation
|
||||
|
||||
| 参数 | 类型 | 说明 | 是否必填 |
|
||||
| --------- | ----------------------- | ------------------------ | -------- |
|
||||
| delay | [Delay](#Delay) | 描述网络的延迟状态 | 否 |
|
||||
| loss | [Loss](#Loss) | 描述网络的丢包状态 | 否 |
|
||||
| duplicate | [Duplicate](#Duplicate) | 描述网络重复包的状态 | 否 |
|
||||
| corrupt | [Corrupt](#Corrupt) | 描述网络包出现错误的状态 | 否 |
|
||||
| delay | [Delay](#delay) | 描述网络的延迟状态 | 否 |
|
||||
| loss | [Loss](#loss) | 描述网络的丢包状态 | 否 |
|
||||
| duplicate | [Duplicate](#duplicate) | 描述网络重复包的状态 | 否 |
|
||||
| corrupt | [Corrupt](#corrupt) | 描述网络包出现错误的状态 | 否 |
|
||||
|
||||
##### Delay
|
||||
### Delay
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
|
|
@ -185,7 +185,7 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
|
||||
其中 `sigma` 为 `jitter`，`mu` 为 `latency`。
|
||||
|
||||
##### Reorder
|
||||
### Reorder
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------- | ------ | -------- | ---- |
|
||||
|
|
@ -193,21 +193,21 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
| correlation | string | 表示发生重新排序的概率与前一次的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| gap | int | 表示乱序将包推后的距离 | 0 | 否 | 5 |
|
||||
|
||||
##### Loss
|
||||
### Loss
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | -------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
| loss | string | 表示丢包发生的概率。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| correlation | string | 表示丢包发生的概率与前一次是否发生的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
|
||||
##### Duplicate
|
||||
### Duplicate
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
| duplicate | string | 表示包重复发生的概率。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| correlation | string | 表示包重复发生的概率与前一次是否发生的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
|
||||
##### Corrupt
|
||||
### Corrupt
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
|
|
@ -216,7 +216,7 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
|
||||
对于 `reorder`，`loss`，`duplicate`，`corrupt` 这些偶发事件，`correlation` 则更为复杂。具体模型描述参考 [NetemCLG](http://web.archive.org/web/20200120162102/http://netgroup.uniroma2.it/twiki/bin/view.cgi/Main/NetemCLG) 。
|
||||
|
||||
#### Bandwidth
|
||||
### Bandwidth
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| -------- | ------ | ------------------------ | ------ | -------- | ----- |
|
||||
|
|
|
|||
|
|
@ -147,18 +147,18 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
| externalTargets | []string | 表示 Kubernetes 之外的网络目标, 可以是 IPv4 地址或者域名。只能与 `direction: to` 一起工作。 | 无 | 否 | 1.1.1.1, google.com |
|
||||
| device | string | 指定影响的网络设备 | 无 | 否 | "eth0" |
|
||||
|
||||
针对不同的 `action`，还有不同的配置项可以填写。
|
||||
## 不同 `action` 的配置项
|
||||
|
||||
#### Net Emulation
|
||||
### Net Emulation
|
||||
|
||||
| 参数 | 类型 | 说明 | 是否必填 |
|
||||
| --------- | ----------------------- | ------------------------ | -------- |
|
||||
| delay | [Delay](#Delay) | 描述网络的延迟状态 | 否 |
|
||||
| loss | [Loss](#Loss) | 描述网络的丢包状态 | 否 |
|
||||
| duplicate | [Duplicate](#Duplicate) | 描述网络重复包的状态 | 否 |
|
||||
| corrupt | [Corrupt](#Corrupt) | 描述网络包出现错误的状态 | 否 |
|
||||
| delay | [Delay](#delay) | 描述网络的延迟状态 | 否 |
|
||||
| loss | [Loss](#loss) | 描述网络的丢包状态 | 否 |
|
||||
| duplicate | [Duplicate](#duplicate) | 描述网络重复包的状态 | 否 |
|
||||
| corrupt | [Corrupt](#corrupt) | 描述网络包出现错误的状态 | 否 |
|
||||
|
||||
##### Delay
|
||||
### Delay
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
|
|
@ -185,7 +185,7 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
|
||||
其中 `sigma` 为 `jitter`，`mu` 为 `latency`。
|
||||
|
||||
##### Reorder
|
||||
### Reorder
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------- | ------ | -------- | ---- |
|
||||
|
|
@ -193,21 +193,21 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
| correlation | string | 表示发生重新排序的概率与前一次的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| gap | int | 表示乱序将包推后的距离 | 0 | 否 | 5 |
|
||||
|
||||
##### Loss
|
||||
### Loss
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | -------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
| loss | string | 表示丢包发生的概率。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| correlation | string | 表示丢包发生的概率与前一次是否发生的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
|
||||
##### Duplicate
|
||||
### Duplicate
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
| duplicate | string | 表示包重复发生的概率。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
| correlation | string | 表示包重复发生的概率与前一次是否发生的相关性。取值范围：[0, 100] | 0 | 否 | 50 |
|
||||
|
||||
##### Corrupt
|
||||
### Corrupt
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| ----------- | ------ | ---------------------------------------------------------------- | ------ | -------- | ---- |
|
||||
|
|
@ -216,7 +216,7 @@ NetworkChaos 用于模拟集群中网络故障的场景，目前支持以下几
|
|||
|
||||
对于 `reorder`，`loss`，`duplicate`，`corrupt` 这些偶发事件，`correlation` 则更为复杂。具体模型描述参考 [NetemCLG](http://web.archive.org/web/20200120162102/http://netgroup.uniroma2.it/twiki/bin/view.cgi/Main/NetemCLG) 。
|
||||
|
||||
#### Bandwidth
|
||||
### Bandwidth
|
||||
|
||||
| 参数 | 类型 | 说明 | 默认值 | 是否必填 | 示例 |
|
||||
| -------- | ------ | ------------------------ | ------ | -------- | ----- |
|
||||
|
|
|
|||
|
|
@ -149,14 +149,14 @@ Before creating NetworkChaos experiments, ensure the following:
|
|||
| externalTargets | []string | Indicates the network targets except for Kubernetes, which can be IPv4 addresses or domains. This parameter only works with `direction: to`. | None | No | 1.1.1.1, google.com |
|
||||
| device | string | Specifies the affected network interface | None | No | "eth0" |
|
||||
|
||||
### Description for `action`-related fields
|
||||
## Description for `action`-related fields
|
||||
|
||||
For the Net Emulation and Bandwidth fault types, you can further configure the `action` related parameters according to the following description.
|
||||
|
||||
- Net Emulation type: `delay`, `loss`, `duplicated`, `corrupt`
|
||||
- Bandwidth type: `bandwidth`
|
||||
|
||||
#### delay
|
||||
### delay
|
||||
|
||||
Setting `action` to `delay` means simulating network delay fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -185,7 +185,7 @@ The computational model for `correlation` is as follows:
|
|||
|
||||
In the above command, `sigma` is `jitter` and `mu` is `latency`.
|
||||
|
||||
#### reorder
|
||||
### reorder
|
||||
|
||||
Setting `action` to `reorder` means simulating network packet reordering fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -195,7 +195,7 @@ Setting `action` to `reorder` means simulating network packet reordering fault.
|
|||
| correlation | string | Indicates the correlation between this time's length of delay time and the previous time's length of delay time. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| gap | int | Indicates the gap before and after packet reordering | 0 | No | 5 |
|
||||
|
||||
#### loss
|
||||
### loss
|
||||
|
||||
Setting `action` to `loss` means simulating packet loss fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -204,7 +204,7 @@ Setting `action` to `loss` means simulating packet loss fault. You can also conf
|
|||
| loss | string | Indicates the probability of packet loss. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| correlation | string | Indicates the correlation between the probability of current packet loss and the previous time's packet loss. Range of value: [0, 100] | 0 | No | 50 |
|
||||
|
||||
#### duplicate
|
||||
### duplicate
|
||||
|
||||
Set `action` to `duplicate`, meaning simulating package duplication. At this point, you can also set the following parameters.
|
||||
|
||||
|
|
@ -213,7 +213,7 @@ Set `action` to `duplicate`, meaning simulating package duplication. At this poi
|
|||
| duplicate | string | Indicates the probability of packet duplicating. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| correlation | string | Indicates the correlation between the probability of current packet duplicating and the previous time's packet duplicating. Range of value: [0, 100] | 0 | No | 50 |
|
||||
|
||||
#### corrupt
|
||||
### corrupt
|
||||
|
||||
Setting `action` to `corrupt` means simulating package corruption fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -224,7 +224,7 @@ Setting `action` to `corrupt` means simulating package corruption fault. You can
|
|||
|
||||
For occasional events such as `reorder`, `loss`, `duplicate`, and `corrupt`, the `correlation` is more complicated. For specific model description, refer to [NetemCLG](http://web.archive.org/web/20200120162102/http://netgroup.uniroma2.it/twiki/bin/view.cgi/Main/NetemCLG).
|
||||
|
||||
#### bandwidth
|
||||
### bandwidth
|
||||
|
||||
Setting `action` to `bandwidth` means simulating bandwidth limit fault. You also need to configure the following parameters.
|
||||
|
||||
|
|
|
|||
|
|
@ -149,14 +149,14 @@ Before creating NetworkChaos experiments, ensure the following:
|
|||
| externalTargets | []string | Indicates the network targets except for Kubernetes, which can be IPv4 addresses or domains. This parameter only works with `direction: to`. | None | No | 1.1.1.1, google.com |
|
||||
| device | string | Specifies the affected network interface | None | No | "eth0" |
|
||||
|
||||
### Description for `action`-related fields
|
||||
## Description for `action`-related fields
|
||||
|
||||
For the Net Emulation and Bandwidth fault types, you can further configure the `action` related parameters according to the following description.
|
||||
|
||||
- Net Emulation type: `delay`, `loss`, `duplicated`, `corrupt`
|
||||
- Bandwidth type: `bandwidth`
|
||||
|
||||
#### delay
|
||||
### delay
|
||||
|
||||
Setting `action` to `delay` means simulating network delay fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -185,7 +185,7 @@ The computational model for `correlation` is as follows:
|
|||
|
||||
In the above command, `sigma` is `jitter` and `mu` is `latency`.
|
||||
|
||||
#### reorder
|
||||
### reorder
|
||||
|
||||
Setting `action` to `reorder` means simulating network packet reordering fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -195,7 +195,7 @@ Setting `action` to `reorder` means simulating network packet reordering fault.
|
|||
| correlation | string | Indicates the correlation between this time's length of delay time and the previous time's length of delay time. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| gap | int | Indicates the gap before and after packet reordering | 0 | No | 5 |
|
||||
|
||||
#### loss
|
||||
### loss
|
||||
|
||||
Setting `action` to `loss` means simulating packet loss fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -204,7 +204,7 @@ Setting `action` to `loss` means simulating packet loss fault. You can also conf
|
|||
| loss | string | Indicates the probability of packet loss. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| correlation | string | Indicates the correlation between the probability of current packet loss and the previous time's packet loss. Range of value: [0, 100] | 0 | No | 50 |
|
||||
|
||||
#### duplicate
|
||||
### duplicate
|
||||
|
||||
Set `action` to `duplicate`, meaning simulating package duplication. At this point, you can also set the following parameters.
|
||||
|
||||
|
|
@ -213,7 +213,7 @@ Set `action` to `duplicate`, meaning simulating package duplication. At this poi
|
|||
| duplicate | string | Indicates the probability of packet duplicating. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| correlation | string | Indicates the correlation between the probability of current packet duplicating and the previous time's packet duplicating. Range of value: [0, 100] | 0 | No | 50 |
|
||||
|
||||
#### corrupt
|
||||
### corrupt
|
||||
|
||||
Setting `action` to `corrupt` means simulating package corruption fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -224,7 +224,7 @@ Setting `action` to `corrupt` means simulating package corruption fault. You can
|
|||
|
||||
For occasional events such as `reorder`, `loss`, `duplicate`, and `corrupt`, the `correlation` is more complicated. For specific model description, refer to [NetemCLG](http://web.archive.org/web/20200120162102/http://netgroup.uniroma2.it/twiki/bin/view.cgi/Main/NetemCLG).
|
||||
|
||||
#### bandwidth
|
||||
### bandwidth
|
||||
|
||||
Setting `action` to `bandwidth` means simulating bandwidth limit fault. You also need to configure the following parameters.
|
||||
|
||||
|
|
|
|||
|
|
@ -149,14 +149,14 @@ Before creating NetworkChaos experiments, ensure the following:
|
|||
| externalTargets | []string | Indicates the network targets except for Kubernetes, which can be IPv4 addresses or domains. This parameter only works with `direction: to`. | None | No | 1.1.1.1, google.com |
|
||||
| device | string | Specifies the affected network interface | None | No | "eth0" |
|
||||
|
||||
### Description for `action`-related fields
|
||||
## Description for `action`-related fields
|
||||
|
||||
For the Net Emulation and Bandwidth fault types, you can further configure the `action` related parameters according to the following description.
|
||||
|
||||
- Net Emulation type: `delay`, `loss`, `duplicated`, `corrupt`
|
||||
- Bandwidth type: `bandwidth`
|
||||
|
||||
#### delay
|
||||
### delay
|
||||
|
||||
Setting `action` to `delay` means simulating network delay fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -185,7 +185,7 @@ The computational model for `correlation` is as follows:
|
|||
|
||||
In the above command, `sigma` is `jitter` and `mu` is `latency`.
|
||||
|
||||
#### reorder
|
||||
### reorder
|
||||
|
||||
Setting `action` to `reorder` means simulating network packet reordering fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -195,7 +195,7 @@ Setting `action` to `reorder` means simulating network packet reordering fault.
|
|||
| correlation | string | Indicates the correlation between this time's length of delay time and the previous time's length of delay time. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| gap | int | Indicates the gap before and after packet reordering | 0 | No | 5 |
|
||||
|
||||
#### loss
|
||||
### loss
|
||||
|
||||
Setting `action` to `loss` means simulating packet loss fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -204,7 +204,7 @@ Setting `action` to `loss` means simulating packet loss fault. You can also conf
|
|||
| loss | string | Indicates the probability of packet loss. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| correlation | string | Indicates the correlation between the probability of current packet loss and the previous time's packet loss. Range of value: [0, 100] | 0 | No | 50 |
|
||||
|
||||
#### duplicate
|
||||
### duplicate
|
||||
|
||||
Set `action` to `duplicate`, meaning simulating package duplication. At this point, you can also set the following parameters.
|
||||
|
||||
|
|
@ -213,7 +213,7 @@ Set `action` to `duplicate`, meaning simulating package duplication. At this poi
|
|||
| duplicate | string | Indicates the probability of packet duplicating. Range of value: [0, 100] | 0 | No | 50 |
|
||||
| correlation | string | Indicates the correlation between the probability of current packet duplicating and the previous time's packet duplicating. Range of value: [0, 100] | 0 | No | 50 |
|
||||
|
||||
#### corrupt
|
||||
### corrupt
|
||||
|
||||
Setting `action` to `corrupt` means simulating package corruption fault. You can also configure the following parameters.
|
||||
|
||||
|
|
@ -224,7 +224,7 @@ Setting `action` to `corrupt` means simulating package corruption fault. You can
|
|||
|
||||
For occasional events such as `reorder`, `loss`, `duplicate`, and `corrupt`, the `correlation` is more complicated. For specific model description, refer to [NetemCLG](http://web.archive.org/web/20200120162102/http://netgroup.uniroma2.it/twiki/bin/view.cgi/Main/NetemCLG).
|
||||
|
||||
#### bandwidth
|
||||
### bandwidth
|
||||
|
||||
Setting `action` to `bandwidth` means simulating bandwidth limit fault. You also need to configure the following parameters.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue