Skip to content

CODE-RADE Foundation Release 3 - Build Containers

Latest
Latest
Compare
Choose a tag to compare
@brucellino brucellino released this 06 May 05:48
· 23 commits to master since this release
v0.0.2-fr3
be88e60

DOI License Build Status

CODE-RADE build containers

Roles used

This repository contains the Ansible-Container code for building the CODE-RADE build slave containers. It uses the AAROC.CODE-RADE-container role from Ansible Galaxy

Containers

The containers are built with Ansible Container and stored on quay.io. We build the following base images :

Image Status
CentOS 6 Docker Repository on Quay
Ubuntu 14.04 Docker Repository on Quay
CentOS 7 Docker Repository on Quay
Ubuntu 16.10 Docker Repository on Quay

The containers can be used by pulling them from quay.io e.g. :

docker pull quay.io/aaroc/code-rade-ubuntu1610

The container adds a user, jdk and ssh daemon for jenkins, as well as some CODE-RADE secret sauce :

  • The ci modulefile which sets a few variables:
    • $SOFT_DIR: The software installation path for the CI environment
      setenv SOFT_DIR /data/ci-build/$::env(SITE)/$::env(OS)/$::env(ARCH)/$::env(NAME)/$::env(VERSION)
    • $REPO_DIR : The built artefacts (in tarball) in the CI environment
      setenv REPO_DIR /data/artefacts/$::env(SITE)/$::env(OS)/$::env(ARCH)/$::env(NAME)/$::env(VERSION)
    • $SRC_DIR : The local cache for the source tarballs
      setenv SRC_DIR /data/src/$::env(NAME)/$::env(VERSION)
    • $MODULES : The path to the modulefiles for the CI environment
      set MODULES /data/modules
  • The deploy modulefile which sets the same variables except the root of $SOFT_DIR is under /cvmfs
  • A data container (CODE-RADE-data) is used to persist the data from build to build, and to make the builds portable.

The Data Containers

We use the data container pattern to provide persistence to the build artefacts, across jobs. These are expressed in the container.yml for Docker only.

To build

In order to build the containers, you can simply do :

ansible-container --project-name code-rade build --roles-path /home/becker/Ops/AAROC/DevOps/Ansible/roles/ --use-local-python

Pushing to the image registry

container.yml contains the specification of which registries are used. We use quay by default. In order to push the built image to a registry, so as to make it usable by another build site, do

ansible-container --project-name code-rade push --roles-path /home/becker/Ops/AAROC
/DevOps/Ansible/roles/ --push-to quay --tag latest

Running

These containers are designed to be provisioned automatically by a CI system. The default entrypoint is ssh on port 5200.

You can use them to check builds locally. In order to run them, do

ansible-container ansible-container --project-name code-rade run --roles-path /home/becker/Ops/AAROC/DevOps/Ansible/roles/

Then ssh into the running container :

ssh [email protected] -p 5200

Deploy

As mentioned before, these containers are for provisioning from CI environments. If you really want to run a static build cluster, you can use the --deploy command of Ansible Container. See https://docs.ansible.com/ansible-container/reference/deploy.html for deployment options

Citing

If you produce research or other output and these containers are a part of that workflow, please cite as
Bruce Becker. (2017). AAROC/CODE-RADE-build-containers: CODE-RADE Foundation Release 3 - Build Containers [Data set]. Zenodo. http://doi.org/10.5281/zenodo.572275

Assets 2
Loading