[
https://issues.apache.org/jira/browse/HDDS-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-1526:
---------------------------------
Labels: pull-request-available (was: )
> Publish ozone 0.4.0 to the dockerhub
> ------------------------------------
>
> Key: HDDS-1526
> URL: https://issues.apache.org/jira/browse/HDDS-1526
> Project: Hadoop Distributed Data Store
> Issue Type: Task
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Labels: pull-request-available
>
> As 0.4.0-alpha is released we can publish the latest stable version on
> dockerhub.
> Required steps:
> * Update ozone-latest branch in apache/hadoop-docker-ozone repository.
> * Create a new branch ozone-0.4.0 from the ozone-latest
> Dockerhub is configured to create new tags from any branch which starts with
> ozone-:
> branchname: ozone-XXXX --> docker image: apache/ozone:XXXX
> Note: this releasing is in sync with ASF policies (See LEGAL-270)
> bq. The main Docker Hub at hub.docker.com is a public-facing downstream
> distribution channel – similar to Maven Central, PyPI, Debian package
> management, etc.
> bq. It is appropriate to distribute official releases through downstream
> channels, but inappropriate to distribute unreleased materials through them.
> (That's
> why having `latest` on hub.docker.com point to git `master` is problematic.)
> See Apache's formal Release Policy and Release Distribution Policy documents
> This is a downstream distribution of the already voted and release ozone
> package. Please note that the Dockerfile points to the official download
> page.
> The ozone version command can show that we have exactly the same, voted and
> released bits inside:
> {code}
> docker run apache/ozone:latest ozone version
> //////////////
> ////////////////////
> //////// ////////////////
> ////// ////////////////
> ///// //////////////// /
> ///// //////// ///
> //// //////// /////
> ///// ////////////////
> ///// //////////////// //
> //// /////////////// /////
> ///// /////////////// ////
> ///// ////// /////
> ////// ////// /////
> /////////// ////////
> ////// ////////////
> /// //////////
> / 0.4.0-alpha(Badlands)
> Source code repository https://github.com/apache/hadoop.git -r
> 4ea602c1ee7b5e1a5560c6cbd096de4b140f776b
> Compiled by ajay.kumar on 2019-04-30T03:25Z
> Compiled with protoc 2.5.0
> From source with checksum 45e58ba9203a1b4470e183bf90281b20
> Using HDDS 0.4.0-alpha
> Source code repository https://github.com/apache/hadoop.git -r
> 4ea602c1ee7b5e1a5560c6cbd096de4b140f776b
> Compiled by ajay.kumar on 2019-04-30T03:24Z
> Compiled with protoc 2.5.0
> From source with checksum 57412e0def0317aed91721fb7ef5
> {code}
> How to test:
> 1. Single image version
> {code}
> ./build.sh
> docker run -p 9878:9878 -p 9876:9876 apache/ozone:latest
> ls > /tmp/testfile
> aws s3api --endpoint http://localhost:9878/ create-bucket --bucket=bucket1
> aws s3 --endpoint http://localhost:9878 cp --storage-class REDUCED_REDUNDANCY
> /tmp/testfile s3://bucket1/testfile
> {code}
> Yes, it's an ozone cluster in one line.
> 2. pseudo-cluster version
> {code}
> ./build.sh
> docker tag apache/ozone:latest apache/ozone:0.4.0
> mkdir /tmp/ozonetest
> cd /tmp/ozonetest
> #The required config files are inlined!!!
> docker run apache/ozone:latest cat docker-config > docker-config
> docker run apache/ozone:latest cat docker-config.yaml > docker-config.yaml
> docker-compose up -d
> docker-compose scale datanode=3
> ls > /tmp/testfile
> aws s3api --endpoint http://localhost:9878/ create-bucket --bucket=bucket1
> aws s3 --endpoint http://localhost:9878 cp /tmp/testfile
> s3://bucket1/testfile
> {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]
