Generic Installation and Configuration Guide

This chapter provides information on how to enable and use the INDIGO DataCloud software repositories hosting the first major release INDIGO-1 (MidnightBlue).

Summary

Installing the Operating Systems and Cloud Management Frameworks

Operating Systems

CentOS 7

For more information on CentOS please check: https://www.centos.org/

All the information to install this operating system can be found at https://wwwhttps://www.centos.org/download/[](https://www.centos.org/download/)

You will find there information on CentOS packages and Docker Containers.

The EPEL repository

If not present by default on your nodes, you should enable the EPEL repository (https://fedoraproject.org/wiki/EPEL)

EPEL has an 'epel-release' package that includes gpg keys for package signing and repository information. Installing the latest version of epel-release package available on EPEL7 repositories like:

allows you to use normal tools, such as yum, to install packages and their dependencies. By default the stable EPEL repo should be enabled.

Ubuntu 14.04

For more information on Ubuntu please check: http://www.ubuntu.com/

Information to install this operating system can be found at http://releases.ubuntu.com/trusty/ and or at Ubuntu Community Installation Guide and regarding Docker Containers at Ubuntu Official Docker repository.

Cloud Management Frameworks

OpenStack Liberty

Please follow the official OpenStack Liberty Installation Guides:

  • for RedHat & CentOS
    • Please enable the use of Liberty RDO repository by using:
      $ sudo yum install -y https://repos.fedorapeople.org/openstack/openstack-liberty/rdo-release-liberty-5.noarch.rpm
  • for Ubuntu 14.04
    • Please enable the use of Liberty CloudArchive by using:
      $ sudo add-apt-repository cloud-archive:liberty

OpenNebula 4.14

Please follow the official OpenNebula 14.4 Installation Guide for CentOS & Ubuntu

Enable the INDIGO - DataCloud packages repositories

INDIGO - DataCloud products are distributed from standard OS repositories and DockerHub registry.

The packages repositories have the following structure:

  • INDIGO-DC production (stable): indigo/{1,2}/<platform>/<basearch>/{base|updates}
    • stable and signed, well tested software components, recommended to be installed on production-sites
  • Third-party: indigo/{1,2}/<platform>/<basearch>/third-party
    • packages that are not part of INDIGO, or not part of the base OS or EPEL, but used as dependencies by other INDIGO components
  • INDIGO-DC testing: indigo-testing/{1,2}/<platform>/<basearch>
    • packages that will become part of the next stable distribution; in the certification and validation phase.
  • INDIGO-DC preview: indigo-preview/{1,2}/<platform>/<basearch>
    • signed packages that will become part of the next stable update, available for technical-previews

where

  • <basearch> is currently: x86_64, SRPMS, tgz
  • <platform> is currently: centos7, ubuntu

All packages are signed with the INDIGO - DataCloud gpg key. The public key can be downloaded from here, and the fingerprint from here. Please import the key BEFORE starting!

  • for CentOS7 save the key under /etc/pki/rpm-gpg/
    # rpm --import http://repo.indigo-datacloud.eu/repository/RPM-GPG-KEY-indigodc

  • for Ubuntu:
    # wget -q -O - http://repo.indigo-datacloud.eu/repository/RPM-GPG-KEY-indigodc | sudo apt-key add -

Giving INDIGO - DataCloud repositories precedence over EPEL

It is strongly recommended that INDIGO repositories take precedence over EPEL when installing and upgrading packages. For manual configuration:

  • you must install the yum-priorities** plugin and ensure that its configuration file, /etc/yum/pluginconf.d/priorities.conf is as follows:
    [ main ]
    enabled = 1
    check_obsoletes = 1

For automatic configuration:

  • we strongly recommend the use of indigodc-release package. Please follow the instructions given bellow on what version of the package, how to get and install it.

Configuring the use of INDIGO - DataCloud repositories

INDIGO-1 production repositories are available at:

YUM and APT configuration files are available at:

Install INDIGO - DataCloud repositories :

  • CentOS7:
    wget http://repo.indigo-datacloud.eu/repository/indigo/1/centos7/x86_64/base/indigodc-release-1.0.0-1.el7.centos.noarch.rpm
    yum localinstall -y indigodc-release-1.0.0-1.el7.centos.noarch.rpm

  • Ubuntu 14.04:
    wget http://repo.indigo-datacloud.eu/repository/indigo/1/ubuntu/dists/trusty-updates/main/binary-amd64/indigodc-release_1.0.0-2_amd64.deb
    dpkg -i indigodc-release_1.0.0-2_amd64.deb

These packages will install required dependencies, the INDIGO - DataCloud public key and ensures the precedence of INDIGO - DataCloud repositories over EPEL and Ubuntu.

It is strongly recommended the use of the latest version of the indigodc-release package containing the public key and the YUM and APT repository files.

Enable the INDIGO - DataCloud Containers repositories

On the DockerHub Registry, INDIGO - DataCloud has organized the repositories under two Organizations:

Currently, content trust is disabled by default. You must enable it by setting the DOCKER_CONTENT_TRUST environment variable, like bellow:

export DOCKER_CONTENT_TRUST=1

For more details regarding the "Content Trust in Docker" please read Docker's Documentation

Content trust is associated with the TAG portion of an image. For INDIGO-1 (Midnight) release the signed tag is indigo_1. See example bellow if you want to ensure the correct use of INDIGO - DataCloud images:

  • for Core Services
$ export DOCKER_CONTENT_TRUST=1
$ docker pull indigodatacloud/orchestrator:1.0.0-RC3
No trust data for 1.0.0-RC3
$ docker pull indigodatacloud/orchestrator:indigo_1
Pull (1 of 1): indigodatacloud/orchestrator:indigo_1@sha256:f1b692cdfe45096e7c778157a35a38a94a71b9daf5e7ba7c213a0107fd51f4a7
sha256:f1b692cdfe45096e7c778157a35a38a94a71b9daf5e7ba7c213a0107fd51f4a7: Pulling from indigodatacloud/orchestrator
3d8673bd162a: Pull complete
[...]
88c118280e3d: Pull complete
Digest: sha256:f1b692cdfe45096e7c778157a35a38a94a71b9daf5e7ba7c213a0107fd51f4a7
Status: Downloaded newer image for indigodatacloud/orchestrator@sha256:f1b692cdfe45096e7c778157a35a38a94a71b9daf5e7ba7c213a0107fd51f4a7
Tagging indigodatacloud/orchestrator@sha256:f1b692cdfe45096e7c778157a35a38a94a71b9daf5e7ba7c213a0107fd51f4a7 as indigodatacloud/orchestrator:indigo_1
$ docker images |grep orchestrator
indigodatacloud/orchestrator               indigo_1            2153bb4c33d1        4 days ago          837.1 MB
  • for Applications:
$ export DOCKER_CONTENT_TRUST=1
$ docker pull indigodatacloudapps/ambertools:latest
No trust data for latest
$ docker pull indigodatacloudapps/ambertools:indigo_1
Pull (1 of 1): indigodatacloudapps/ambertools:indigo_1@sha256:82c202e06e94b9fec85ec4672a0c8b0b4efcc10652275d15ff32eadf2e1cbefd
sha256:82c202e06e94b9fec85ec4672a0c8b0b4efcc10652275d15ff32eadf2e1cbefd: Pulling from indigodatacloudapps/ambertools
6c953ac5d795: Pull complete
[...]
fb42bfb32649: Pull complete
Digest: sha256:82c202e06e94b9fec85ec4672a0c8b0b4efcc10652275d15ff32eadf2e1cbefd
Status: Downloaded newer image for indigodatacloudapps/ambertools@sha256:82c202e06e94b9fec85ec4672a0c8b0b4efcc10652275d15ff32eadf2e1cbefd
Tagging indigodatacloudapps/ambertools@sha256:82c202e06e94b9fec85ec4672a0c8b0b4efcc10652275d15ff32eadf2e1cbefd as indigodatacloudapps/ambertools:indigo_1
$ docker images |grep amber
indigodatacloudapps/ambertools             indigo_1            6c47a81b761d        11 days ago         1.826 GB

Important note on automatic updates

The CentOS and Ubuntu Operating Systems both offer auto-updates mechanisms. Sometimes middleware updates require non-trivial configuration changes or a reconfiguration of the service. This could involve service restarts, new configuration files, etc, which makes it difficult to ensure that automatic updates will not break a service. Thus

WE STRONGLY RECOMMEND NOT TO USE AUTOMATIC UPDATE PROCEDURE OF ANY KIND

on the INDIGO - DataCloud repositories (you can keep it turned on for the OS). You should read the update information provides by each service and do the upgrade manually when an update has been released!

results matching ""

    No results matching ""