HyraxDockerReleaseGuide: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
(Created page with "== Overview == This document describes how to make a release of the official Hyrax Docker image The Docker image is based on official releases of the Hyrax server. The images...")
 
Line 3: Line 3:


The Docker image is based on official releases of the Hyrax server. The images are built using the official release tar/war files whose authenticity is verified during the build.
The Docker image is based on official releases of the Hyrax server. The images are built using the official release tar/war files whose authenticity is verified during the build.
In our Docker project, each release of Hyrax has its own directory. Making a new release begins with copying the most recent release files to a new release directory and editing their contents, and of course, testing that it works.
; 1. Create a new Docker release directory and copy the most files from the previous release into the new directory
: <tt>mkdir hyrax-xx.yy.zz</tt>
: <tt>cp -R hyrax-1.13.4/*  hyrax-xx.yy.zz</tt>
; 2. In each of these files:
: <tt>hyrax-xx.yy.zz/besd/Dockerfile </tt>
: <tt>hyrax-xx.yy.zz/olfs/Dockerfile </tt>
: <tt>hyrax-xx.yy.zz/hyrax/Dockerfile </tt>
: <tt>hyrax-xx.yy.zz/ncWMS/Dockerfile </tt>
;  You will need to edit 3 specific sections:
LABEL vendor="OPeNDAP Incorporated"
LABEL org.opendap.hyrax.version="1.13.4"
LABEL org.opendap.hyrax.release-date="2017-06-05"
LABEL org.opendap.hyrax.version.is-production="true"
# HYRAX VERSION INFO
ENV HYRAX_VERSION=1.13.4
ENV LIBDAP_VERSION=3.19.0-1
ENV BES_VERSION=3.18.0-1
ENV OLFS_VERSION=1.16.3
# RELEASE URLs
ENV LIBDAP_RPM="https://www.opendap.org/pub/binary/hyrax-${HYRAX_VERSION}/centos-7.x/libdap-${LIBDAP_VERSION}.el7.centos.x86_64.rpm"
ENV BES_RPM="https://www.opendap.org/pub/binary/hyrax-${HYRAX_VERSION}/centos-7.x/bes-${BES_VERSION}.static.el7.centos.x86_64.rpm"
ENV OLFS_WAR_URL="https://www.opendap.org/pub/olfs/olfs-${OLFS_VERSION}-webapp.tgz"
And update the version and download URL information. Once updated, build the docker images and test them. If it all works tag the built image and push it to docker hub.
;Note: ''This page is pretty thin as we have not yet made a second release of our Docker images. Doing so will help us fill in the blanksy.

Revision as of 18:38, 17 July 2017

Overview

This document describes how to make a release of the official Hyrax Docker image

The Docker image is based on official releases of the Hyrax server. The images are built using the official release tar/war files whose authenticity is verified during the build.

In our Docker project, each release of Hyrax has its own directory. Making a new release begins with copying the most recent release files to a new release directory and editing their contents, and of course, testing that it works.

1. Create a new Docker release directory and copy the most files from the previous release into the new directory
mkdir hyrax-xx.yy.zz
cp -R hyrax-1.13.4/* hyrax-xx.yy.zz
2. In each of these files
hyrax-xx.yy.zz/besd/Dockerfile
hyrax-xx.yy.zz/olfs/Dockerfile
hyrax-xx.yy.zz/hyrax/Dockerfile
hyrax-xx.yy.zz/ncWMS/Dockerfile
You will need to edit 3 specific sections
LABEL vendor="OPeNDAP Incorporated" 
LABEL org.opendap.hyrax.version="1.13.4"
LABEL org.opendap.hyrax.release-date="2017-06-05"
LABEL org.opendap.hyrax.version.is-production="true"
# HYRAX VERSION INFO 
ENV HYRAX_VERSION=1.13.4 
ENV LIBDAP_VERSION=3.19.0-1
ENV BES_VERSION=3.18.0-1
ENV OLFS_VERSION=1.16.3
# RELEASE URLs
ENV LIBDAP_RPM="https://www.opendap.org/pub/binary/hyrax-${HYRAX_VERSION}/centos-7.x/libdap-${LIBDAP_VERSION}.el7.centos.x86_64.rpm"
ENV BES_RPM="https://www.opendap.org/pub/binary/hyrax-${HYRAX_VERSION}/centos-7.x/bes-${BES_VERSION}.static.el7.centos.x86_64.rpm"
ENV OLFS_WAR_URL="https://www.opendap.org/pub/olfs/olfs-${OLFS_VERSION}-webapp.tgz"

And update the version and download URL information. Once updated, build the docker images and test them. If it all works tag the built image and push it to docker hub.

Note
This page is pretty thin as we have not yet made a second release of our Docker images. Doing so will help us fill in the blanksy.