[
https://issues.apache.org/jira/browse/HDDS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830481#comment-16830481
]
Eric Yang commented on HDDS-1458:
---------------------------------
{quote}I don't think it's a strong limitation to make the docker run to
privileged.\{quote}
Cool, I will keep --privileged option in the patch.
{quote}But it may be useful to move out blockade tests from dist to a separated
project if you prefer it.\{quote}
I look at integration-test project and found that it was used to build
miniozone cluster. I agree that blockade code belongs to a separate project
from dist and integration-test, and have done the refactoring for next patch.
{quote}I would use a dedicated profile. The standard mvn verify (or mvn
install) is expected to be used by new contributors. I would keep that one as
simple as possible.\{quote}
I will keep -Pit for triggering the fault injection tests.
{quote}One additional question about disk failure testing (If I understood well
that will be implemented as a next step). How they are connected with blockade
tests? Do you need any functionality from blockade? Can we use the robot test
based smoketests for the same?\{quote}
Disk tests are written using docker-compose with mountable data disks. They
are separate projects from network tests. I basically created a submodule
called fault-injection-test and having disk-tests and network-tests as
submodule. In disk-tests, there are read-write-test, read-only-test, and
corruption-test. Blockcade tests are stored in network-tests. Jenkinsfile
will be updated to include -Pit profile to trigger the tests.
> Create a maven profile to run fault injection tests
> ---------------------------------------------------
>
> Key: HDDS-1458
> URL: https://issues.apache.org/jira/browse/HDDS-1458
> Project: Hadoop Distributed Data Store
> Issue Type: Test
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Major
> Attachments: HDDS-1458.001.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.
> 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}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
