-
Notifications
You must be signed in to change notification settings - Fork 194
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1103 from Martchus/multinet
qemu: Don't use deprecated/removed vlan option for multinet
- Loading branch information
Showing
3 changed files
with
20 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,24 +1,31 @@ | ||
# Networking in OpenQA | ||
There are three possible network configurations for OpenQA virtual machines (VM). | ||
The configuration is controlled by NICTYPE and MULTINET variables passed from OpenQA. | ||
# Networking in openQA | ||
There are three possible network configurations for openQA virtual machines when using the | ||
qemu backend. | ||
|
||
## default situation | ||
By default NICTYPE is set to "user" and MULTINET is not set. In this case, each VM is created | ||
The configuration is controlled by NICTYPE, NICMAC and NICVLAN variables passed from openQA. | ||
|
||
## Default situation | ||
By default NICTYPE is set to "user". In this case, each VM is created | ||
with one network device, QEMU provided DHCP configuration. "User" network mode does have a | ||
limitation - only TCP and UDP are supported. However no additional configuration is needed. | ||
|
||
## options for "user" mode | ||
## Options for "user" mode | ||
If options for "user" mode are required, they can be set in NICTYPE_USER_OPTIONS variable. | ||
|
||
## multiple network devices | ||
When MULTINET variable is set, only NICTYPE set to "user" is supported. In this case, each VM | ||
is created with two network devices using "user" network mode. | ||
|
||
## TAP device support | ||
When advanced configurations, routing or better performance is required, NICTYPE can be set to | ||
"tap". In this case, preconfigured TAP device on host system is used as VM network device. | ||
Which TAP device is used depends on TAPDEV variable which is automatically set to "tap" + worker id - 1, | ||
i.e. worker1 uses tap0, worker 6 uses tap5. This mode requires system administrator to create | ||
TAP device for each running worker and to manually prepare any routing or bridging before "tap" | ||
i.e. worker1 uses tap0, worker 6 uses tap5. This mode requires the system administrator to create | ||
a TAP device for each running worker and to manually prepare any routing or bridging before "tap" | ||
networking can be used. TAP devices need to be created with proper permissions so VMs can access | ||
them, e.g. "tunctl -u _openqa-worker -p -t tap0" | ||
them, e.g. "tunctl -u _openqa-worker -p -t tap0". | ||
|
||
## Multiple network devices | ||
To create multiple network devices, one can set multiple, comma-separated MAC addresses | ||
via NICMAC. The TAPDEV variable supports multiple, comma-separated values, too. | ||
|
||
--- | ||
|
||
Also have a look at [Multi Machine Tests Setup](http://open.qa/docs/#_multi_machine_tests_setup) | ||
documentation. |