[ 
https://issues.apache.org/jira/browse/HDDS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837709#comment-16837709
 ] 

Eric Yang commented on HDDS-1458:
---------------------------------

[~anu] [~jnp] [~elek] and myself were in a meeting and discovered the 
documentation did not reflect the current code base correctly with HDDS-1513, 
HDDS-1518, HDDS-1519, HDDS-1520 opened.  we agreed on the current layout of 
ozone tarball needs to be more compatible with Hadoop directory layout to 
prevent developers from writing inflexible code.  The proposal is to generate 
test artifacts in ozone-[version]/share/ozone/tests for fault injection test 
framework in release binary tarball.  

User will be able to run:
{code}
cd $DIRECTORY_OF_OZONE
python -m pytest -s  share/ozone/tests/blockade/
{code}

In source tarball, user can run from top level of ozone source code or inside 
fault-injection-test directory:

{code}
mvn clean verify -Pit
{code}

This issue is not going to handle limitation of hard coded uid/gid in 
hadoop-runner image.  Hence some developers may not be able to run blockade 
tests until that issues is addressed in HDDS-1513.  Please comment if I didn't 
capture this correctly.  Thanks

> 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
>              Labels: pull-request-available
>         Attachments: HDDS-1458.001.patch, HDDS-1458.002.patch, 
> HDDS-1458.003.patch, HDDS-1458.004.patch
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to