JIRA INFRA-2156 #action In Progress

JIRA INFRA-2148

JIRA INFRA-1563

JIRA INFRA-1563 #action In Progress

By default, we have:
default_channels:
  - https://repo.anaconda.com/pkgs/main
  - https://repo.anaconda.com/pkgs/r

Set it to an empty list to make sure repo.anaconda.com
is not accessed (there shouldn't be any connection to it from the TN).

JIRA INFRA-1560 #action In Progress

Using the conda_env module is more robust.
- If the handler failed for any reason, the env file had to be deleted
  for it to run again
- conda_env ensures the environment is up to date without having to recreate it

Using the conda module to update conda prevents to update from version
older than 4.6 (the module requires 4.6).
Using the command module should allow to update from older versions.

foo that isn't supposed to exist, does in conda-e3 for test

Avoid hard-coding /opt/conda

conda and conda_env share the same Conda class.
This class should be imported from another file but modules can only
use imports from ansible.module_utils due to the way the module is
copied to the host.
See https://docs.ansible.com/ansible/latest/dev_guide/developing_program_flow_modules.html#ansiballz

JIRA INFRA-1307 #action In Progress

Avoid timeout on gitlab-runners

Need conda 4.6 already installed, so update the installer.

JIRA INFRA-1201 #action In Progress

use_only_tar_bz2 is required for compatibility with Artifactory remote
conda repositories. Only .tar.bz2 are currently cached.
See https://www.jfrog.com/jira/browse/RTFACT-19267

Debian

See merge request ics-ansible-galaxy/ics-ans-role-conda!2

with Debian based operating systems.

JIRA INFRA-1028

conda_default_env.sh is executed before conda.sh file and thus the conda
function is not known.
File renamed condaz_default_env.sh to be run after.

conda-e3 is now used to install pyepics and pvapy

Variable conda_default_env can be set to an environment name.
This environment will be automatically activated for all users (using
/etc/profile.d/conda_default_env.sh).

On the TN, we can't access repo.anaconda.com.
The channel_alias has to be set before trying to update conda.

Updated conda to 4.6.12

See merge request ics-ansible-galaxy/ics-ans-role-conda!1

Allow to specify the channels to use using the conda_channels variable.

The create and destroy playbooks are not required anymore.
They are part of molecule (for docker).

When installing conda with the installer, conda can be updated by using
conda. But when using the RPM, conda should only be updated with yum.

The RPMs provided by conda are currently updated very seldomly (conda
4.6.11 is available, but the only rpm available is still 4.5.12).
Using the installer gives better control of the version we want to
install.

1. It's easier to use a mirror (no need to manually copy new RPMs to
artifactory)
2. The mirror is configured in this role because it's the only repo needed to
install conda (no EPEL). No need to put it in the ics-ans-role-repository and
add a dependency.

- only specify the python version to install (without exact dependencies
to avoid deprecated packages)
- use file from the repository to test http url (python27_env.yml) to
not rely on an external repository

RPM released by anaconda.
Installation is done from the RPM to avoid adding the repository as
dependency.