TeamingUplink was renamed to ActiveUplink, FallbackUplink was
renamed to StandbyUplink due to VMware terminology.
Rename affected tests (plans, test groups, automation) and
UI (description string).
Change-Id: Ie251ae6f6bba7a70c79ccbcbf56aa325eb937c80
The network and uplink mapping now should be set in the new format:
a) Multiple strings each for one cluster in a textarea item;
b) Uplinks-mapping is optional
c) possible data is:
1. Cluster:VDS
2. Cluster:VDS:TU1;TU2;TU3
3. Cluster:VDS:TU1;TU2:FU3;FU4
where TU -- teaming uplink,
FU -- fallback uplink,
there is no limitation for amount of uplinks,
uplinks shoud be splitted by ';'
Change-Id: Ibf40675bb048a15a70157598931fae211da04edb
There is direct 1 cluster to 1 dvSwitch mapping in 2.1 version of
plugin. The label and the descripton were changed according to it.
Change-Id: Ic0d316af1d391cd023fe2a1d80cdcc83c7885aa4
Name of dvSwitch (or physnet to switchname mapping) mandatory should be
setted.
Change-Id: I29c18896f19b914d0423eac6e0450f63eedb4858
Closes-bug: #1481010
There is mapping scheme between physical network and DVS on vCenter.
Users have to set it manually like:
physnet1:dvSwitch1,physnet2:dvSwitch2,...
Change-Id: I6d75789e427197d5e861d2f03d5730fa80af6b65
Andreas Jaeger