[
https://issues.apache.org/jira/browse/HDFS-12469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16175561#comment-16175561
]
Anu Engineer commented on HDFS-12469:
-------------------------------------
Thank you for bringing this to my attention. Here is my interpretation of the
rules and how it applies to us.
{noformat}
Unreleased materials, in original or derived form...
MUST NOT be distributed through www.apache.org/dist.
MUST NOT be distributed through channels which encourage use by anyone outside
the project development community.
MUST NOT be advertised to anyone outside of the project development community.
MAY be distributed to consenting members of a development community.
{noformat}
bq. MUST NOT be distributed through www.apache.org/dist.
AFAIK, we will not be doing this.
bq. MUST NOT be distributed through channels which encourage use by anyone
outside the project development community.
This is little wider in its ambit, but if we have a docker compose file in
ozone root directory it can only be invoked if you have ozone right? So I am
hoping that qualifies as someone inside the project development community.
bq. MUST NOT be advertised to anyone outside of the project development
community.
We are fully in compliance with this. Maybe we should *not* have a Hadoop file
in Docker Cloud too. But the community already gave you a go-ahead in the
mailing thread.
If you want, I can create a \[VOTE\] thread for the discussion you had.
bq. MAY be distributed to consenting members of a development community.
This is what we are doing, and it is like building the tarball as and when
needed. Can we require that users must always build the tarball locally and
point the docker file to that tarball? Probably some more magic scripts from
you, but then we will be fully compliant from the Ozone perspective.
> Ozone: Create docker-compose definition to easily test real clusters
> --------------------------------------------------------------------
>
> Key: HDFS-12469
> URL: https://issues.apache.org/jira/browse/HDFS-12469
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Fix For: HDFS-7240
>
> Attachments: HDFS-12469-HDFS-7240.WIP1.patch,
> HDFS-12469-HDFS-7240.WIP2.patch
>
>
> The goal here is to create a docker-compose definition for ozone
> pseudo-cluster with docker (one component per container).
> Ideally after a full build the ozone cluster could be started easily with
> after a simple docker-compose up command.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
