[
https://issues.apache.org/jira/browse/HDDS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846131#comment-16846131
]
Eric Yang commented on HDDS-1458:
---------------------------------
[~elek] {quote}Can you please delete the original one from the
compose/ozoneblockade dir of the dirst tar.{quote}
Sorry, I am confused about this ask. compose/ozoneblockade dir is already
removed from dist project. Do you want me to remove compose/ozoneblockade from
tarball too? If yes, this implies that python script will default to use
$OZONE_HOME/compose/ozone as source for yaml files for testing purpose. If no,
please clarify.
For clarity on locating docker-compose file:
{code}
if "MAVEN_TEST" in os.environ:
compose_dir = environ.get("MAVEN_TEST")
FILE = os.path.join(compose_dir, "docker-compose.yaml")
elif "OZONE_HOME" in os.environ:
compose_dir = environ.get("OZONE_HOME")
FILE = os.path.join(compose_dir, "compose", "ozone", \
"docker-compose.yaml")
else:
compose_dir = os.getcwd()
FILE = os.path.join(compose_dir, "compose", "ozone", \
"docker-compose.yaml")
{code}
# MAVEN_TEST is self explaintory, to located docker compose in maven build
directory.
# OZONE_HOME is used, if binary executable is symlink to a location such as
/usr/bin. Where PATH variable can find the script via symlink location, but
OZONE_HOME variable is required to assist locating compose file.
# If system environment is not configured, there is no OZONE_HOME variable
defined, then look for compose file from the current location. This style is
used for expanding tarball, and run directly.
Hope this explains the three type of differences that the script is improved to
support.
> 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
> Fix For: 0.4.1
>
> Attachments: HDDS-1458.001.patch, HDDS-1458.002.patch,
> HDDS-1458.003.patch, HDDS-1458.004.patch, HDDS-1458.005.patch,
> HDDS-1458.006.patch, HDDS-1458.007.patch, HDDS-1458.008.patch,
> HDDS-1458.009.patch, HDDS-1458.010.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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
