[
https://issues.apache.org/jira/browse/HDDS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831740#comment-16831740
]
Elek, Marton commented on HDDS-1458:
------------------------------------
Thank you very much to give me more details.
I have slightly different view of this problem. If I understood well there is
no technical limitations as of now it's more like a semantic question what is
the good usage of docker or what is well designed. To be honest it's hard to
judge for me. I think there is more than one way to do it well.
For example I can see are two different use cases:
1. starting docker based pseudo cluster from a (released or dev)
distribution. In this case the mount is not a problem. I think here we should
use mounting to ensure we have exactly the same bits inside and outside. I
can't see any problem here.
2. The second use case is to provide independent, portable docker-compose
files. We have this one even now:
{code}
docker run apache/ozone cat docker-compose.yaml > docker-compose.yaml
docker run apache/ozone cat docker-config > docker-config
docker-compose up -d
{code}
3. I have slightly different experience with docker image creation. I now how
the layering works but the current structure of the project (especially the
creation of two 100Mb shaded jar files) can be handled very well. We need new
layers anyway even if we changed only one class file in the project.
4. I didn't check the source of the maven docker plugin but based on the output
it has some additional copy. I need to check.
5. The release tar file also contains the compose directory. I think it's a
very important part. With mounting the distribution package from the
docker-compose files we can provide the easiest UX to start a pseudo cluster
without any additional image creation.
6. FYI: the docker image creation as part of the maven build is added with the
latest k8s patches. I agree with you that it can help at same cases. But I
don't think that we need to replace the volume mounts in the compose files.
> 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, HDDS-1458.002.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: [email protected]
For additional commands, e-mail: [email protected]
