HDDS-1458. Create a maven profile to run fault injection tests

[elek]

Some fault injection tests have been written using blockade. It would be nice to have ability to start docker compose and exercise the blockade test cases against Ozone docker containers, and generate reports. This is optional integration tests to catch race conditions and fault tolerance defects.

We can introduce a profile with id: it (short for integration tests). This will launch docker compose via maven-exec-plugin and run blockade to simulate container failures and timeout.

Usage command:
{code}
mvn clean verify -Pit
{code}

See: https://issues.apache.org/jira/browse/HDDS-1458

[hadoop-yetus]

💔 -1 overall

Vote	Subsystem	Runtime	Comment
0	reexec	31	Docker mode activated.
		_ Prechecks _
+1	dupname	0	No case conflicting files found.
+1	@author	1	The patch does not contain any @author tags.
-1	test4tests	0	The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.
		_ trunk Compile Tests _
+1	mvninstall	403	trunk passed
+1	compile	202	trunk passed
+1	mvnsite	0	trunk passed
+1	shadedclient	1362	branch has no errors when building and testing our client artifacts.
+1	javadoc	121	trunk passed
		_ Patch Compile Tests _
+1	mvninstall	393	the patch passed
+1	compile	204	the patch passed
+1	javac	204	the patch passed
+1	mvnsite	0	the patch passed
+1	whitespace	0	The patch has no whitespace issues.
+1	xml	1	The patch has no ill-formed XML file.
+1	shadedclient	641	patch has no errors when building and testing our client artifacts.
+1	javadoc	127	the patch passed
		_ Other Tests _
-1	unit	133	hadoop-hdds in the patch failed.
-1	unit	1424	hadoop-ozone in the patch failed.
+1	asflicense	38	The patch does not generate ASF License warnings.
		4633

Subsystem	Report/Notes
Docker	Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-800/1/artifact/out/Dockerfile
GITHUB PR	#800
Optional Tests	dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml
uname	Linux 0b542b01a181 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Build tool	maven
Personality	personality/hadoop.sh
git revision	trunk / 3172f6c
Default Java	1.8.0_191
unit	https://builds.apache.org/job/hadoop-multibranch/job/PR-800/1/artifact/out/patch-unit-hadoop-hdds.txt
unit	https://builds.apache.org/job/hadoop-multibranch/job/PR-800/1/artifact/out/patch-unit-hadoop-ozone.txt
Test Results	https://builds.apache.org/job/hadoop-multibranch/job/PR-800/1/testReport/
Max. process+thread count	4759 (vs. ulimit of 5500)
modules	C: hadoop-ozone/dist U: hadoop-ozone/dist
Console output	https://builds.apache.org/job/hadoop-multibranch/job/PR-800/1/console
versions	git=2.7.4 maven=3.3.9
Powered by	Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

[eyanghwx]

Fault injection tests includes disk tests and network tests. Blockade is only network test. There are other scenarios missing and needs to be included.

[elek]

Sure, this patch demonstrates how the existing tests can be executed as part of the maven build process. I think we can agree that the same pattern can be used to executed any other type of tests.

[elek]

This is the description of the jira. I think this problem is solved by this patch:

Some fault injection tests have been written using blockade. It would be nice to have ability to start docker compose and exercise the blockade test cases against Ozone docker containers, and generate reports. This is optional integration tests to catch race conditions and fault tolerance defects.