[
https://issues.apache.org/jira/browse/HDDS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837775#comment-16837775
]
Elek, Marton commented on HDDS-1458:
------------------------------------
bq. Let us drop the share and make it tests/blockade, and tests/smoketests etc.
That way, all tests that we ship can be found easily. Otherwise I am +1 on this
change.
I agree with Anu. I think It's time to revisit the current structure of ozone
distribution tar files. The original structure is inherited from HADOOP-6255
which is defined for a project which includes multiple subproject (hadoop,
yarn,...) and should support the creation of different RPM package from the
same tar. I think for ozone we can improve the usability with reorganizing the
dirs to a better structure.
But I am fine to do it in a separated jira and keep it in the share/test until
that to make progress.
> 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]
