Generic Installation and Configuration Guide - INDIGO-2
Last updated
Last updated
This chapter provides information on how to enable and use the INDIGO DataCloud software repositories hosting the second major release INDIGO-2 (ElectricIndigo).
Summary
For more information on CentOS please check:
All the information to install this operating system can be found at
You will find there information on CentOS and .
The EPEL repository
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.
Please follow the official OpenStack Newton Installation Guides:
Please enable the use of Newton RDO repository by using:</br>
$ sudo yum install -y https://repos.fedorapeople.org/openstack/openstack-newton/rdo-release-newton-4.noarch.rpm</br>
Please enable the use of Newton CloudArchive by using:
$ sudo add-apt-repository cloud-archive:newton
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
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 -
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 to use, how to get and install it.
INDIGO-2 production repositories are available at:
YUM & APT configuration files are available at:
Install INDIGO - DataCloud repositories :
CentOS7:
wget http://repo.indigo-datacloud.eu/repository/indigo/2/centos7/x86_64/base/indigodc-release-2.0.0-1.el7.centos.noarch.rpm
yum localinstall -y indigodc-release-2.0.0-1.el7.centos.noarch.rpm
Ubuntu 16.04:
wget http://repo.indigo-datacloud.eu/repository/indigo/2/ubuntu/dists/xenial/main/binary-amd64/indigodc-release_2.0.0-1_amd64.deb
dpkg -i indigodc-release_2.0.0-1_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.
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
Content trust is associated with the TAG portion of an image. For INDIGO-2 (ElectricIndigo) release the signed tag is indigo_2. See example bellow if you want to ensure the correct use of INDIGO - DataCloud images:
for Core Services
for Applications:
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!
If not present by default on your nodes, you should enable the EPEL repository ()
For more information on Ubuntu please check:
Information to install this operating system can be found at and or at and regarding Docker Containers at .
for
for
Please follow the official or
All packages are signed with the INDIGO - DataCloud gpg key. The public key can be downloaded from , and the fingerprint from . Please import the key BEFORE starting!
CentOS7 -
Ubuntu 16.04 -
On the , INDIGO - DataCloud has organized the repositories under two Organizations:
, for Core Services
, for Applications
Containers present in those repositories and released in INDIGO-2 are tagged with "indigo_2" tag and signed, leveraging the so that users can pull trusted images.
For more details regarding the "Content Trust in Docker" please read