Design
This document describes the current options in use for setting up repos, modules and versions and the proposal to use tripleo-repos as the single source for these settings upstream and rhos-release downstream.
- type: file
filename: delorean.repo
down_url: "https://trunk.rdoproject.org/{{ distro_ver }}-{{ release }}/${DLRN_PATH_TAG}/delorean.repo"
- type: generic
reponame: quickstart-centos-base
filename: quickstart-centos-base.repo
baseurl: ${NODEPOOL_CENTOS_MIRROR}/8/BaseOS/x86_64/os/
to a url w/ a pinned hash
(dlrn new) args: centos8, master, current-tripleo
(dlrn component) args: centos8, master, compute, current-tripleo
(classic dlrn)args: centos7, stein, current-tripleo
Reviewing the code base, there are multiple places where repos are set up and versions are set. Some of these include:
Since having various locations for setting is confusing and error prone, there should be one source of truth for how and which repos are installed for a tripleo deployment and that source of truth should be tripleo-repos. Having a single source of truth for repo config, modules, etc will make things more consistent, reliable and easier to debug.
Finding and setting the dlrn hash (from a dlrn link) is another area where the functionality is duplicated in various forms and in numerous places including:
Tripleo repos doesn't do what we require. Suggestion is to start something new?
container_tools_version:
container_tools_pin: master: victoria: train: - disable: rhel8 enable: 2.0
(parallel to rhos-relase)
new tripleo-repos will embed upstream urls into the code base