...
/* work in progress */
1.1 High Level Overview
In the top level, the CVP framework requires the tester's lab consist of the System Under Test (SUT), the jumphost that has access both public Internet and the private Management Network (a.k.a. Operation and Management Network, or O&M), necessary networking configuration and security gateways. The tester may realize this by a firewall, as shown below, and putting the jumphost in the DMZ. However, this configuration is just one possibility and a suggestion; it is not an explicit CVP requirement. Other methods of achieving the same goal of allowing the jumphost to have secure access to both the public Internet and private Management Network are equally valid.
The OPNFV CVP server, shown on the right side of the diagram above, is included for reference only. It is not the responsibility of the tester for the purpose of CVP certification.
In a data center environment, a remote management infrastructure (a.k.a. Light Out Management) is a important part of the running a large scale system efficiently and reliably. Such remote management infrastructure however is not an explicit requirement of CVP at this time. The test suite does not make direct reference to the existence of a remote management system, although it is a recommended component.
1.2 Hardware
The following bare metal hardware is required:
- 1 jumphost
- 5 controller and compute hosts
We require all 5 controller and compute hosts to be bare metal hosts because of high availability and scalability tests require bare metal environment. Other test cases may also be developed with bare metal environment only.
The jumphost does not have to be bare metal for CVP. However, this guide assumes it is a stand alone bare metal machine for simplicity. It is the tester's responsibility to make necessary configurations such that a virtual machine or a container can perform the same duties as a bare metal jumphost.
1.2.1 Jumphost
The jumphost should meet the following minimum hardware requirements.
The 5 controller and compute hosts should meet the following minimum hardware requirements.
1.3 Networking
1.4 Management
...
6.1 Check dovetail commands
% dovetail -h
Dovetail has three commands: list, run and show.
6.2 List
6.2.1 List help
% dovetail list -h
6.2.2 List a test suite
List command will list all test cases belong to the given test suite.
% dovetail list compliance_set
% dovetail list debug
The ipv6, example and nfvi are test areas. If no <TESTSUITE> is given, it will list all testsuites.
6.3 Show
Show command will give the detailed info of one certain test case.
6.3.1 Show help
% dovetail show -h
6.3.2 Show test case
6.4 Run
Dovetail supports running a named test suite, or one named test area of a test suite.
6.4.1 Run help
% dovetail run -h
There are some options:
func_tag: set FuncTest’s Docker tag, for example stable,latest and danube.1.0
openrc: give the path of OpenStack credential file
yard_tag: set Yardstick’s Docker tag
testarea: set a certain testarea within a certain testsuite
offline: run without pull the docker images, and it requires the jumphost to have these images locally. This will ensure DoveTail run in an offline environment.
report: push results to DB or store with files
testsuite: set the testsuite to be tested
debug: flag to show the debug log messages
...