openstack/openstack-ansible
Code Issues Proposed changes
9dd290a6ff
openstack-ansible/playbooks/defaults/repo_packages
History
Jean-Philippe Evrard c760537913 Make sure the branch to track is in YAML 
There is no reason to rely on comments in the files
used to bump the SHAs of upstream repositories.

Without this, a contributor can easily add a comment
and break the tooling, which relies on regexps and
well formated files to behave.

Instead, as this is a YAML file, we should rely on
a YAML parser in the release tooling, for more
robustness.

This fixes the issues by adding an extra key
(_git_track_branch) per repository, showing what to track.
This could be used in release tooling, and is not hurting
the existing code, as the extra keys are not loaded:
Those files are only consumed by the py_pkgs lookup, which
won't read this extra key.

Change-Id: I8fe08f389160e7be17dd56afde22173778540855
(manual cherry picked from commit 2a288e1b1e)
2018-09-04 15:40:17 +02:00
..
gnocchi.yml Make sure the branch to track is in YAML 2018-09-04 15:40:17 +02:00
nova_consoles.yml Make sure the branch to track is in YAML 2018-09-04 15:40:17 +02:00
openstack_services.yml Make sure the branch to track is in YAML 2018-09-04 15:40:17 +02:00
openstack_testing.yml Make sure the branch to track is in YAML 2018-09-04 15:40:17 +02:00
readme.rst Updated the py_pkgs lookup plugin for multi source 2015-12-02 18:11:56 -06:00

readme.rst

Packages built by python from git

date

2014-09-01 09:57

tags

python, pip, wheel, lxc, openstack, cloud, ansible

category

*nix

Packages Downloads and Installable

Any and all packages that need to be installed for this repository to work should be specified here in the, repo_packages directory. The files in this directory are given to the python wheel builder for construction.

Inside these files all download-able objects such as tar-balls and random files should also be specified. While the packaging roles may not be used to process these links the stated purpose of this directory is to have anything that is "installable" in a single location with the goal to allow for easily manipulation of requirements as they change.

NOTICE on items in this file:
  • If you use anything in the "*._git_install_branch" field that is not a TAG make sure to leave an in-line comment as to "why".
For the sake of anyone else editing this file:
  • If you add clients to this file please do so in alphabetical order.
  • Every entry should be name spaced with the name of the client followed by an "_"
Repository data can be set in any of the following locations by default.
  • <MAIN REPO LOCATION>
  • /etc/ansible/roles
  • /etc/openstack_deploy
The basic structure of all of these files:
  • git_repo: string URI to the git repository to clone from.
  • git_fallback_repo: string URI to an alternative git repository to clone from when git_repo fails.
  • git_dest: string full path to place a cloned git repository. This will normally incorporate the repo_path variable for consistency purposes.
  • git_install_branch: string branch, tag or SHA of a git repository to clone into.
  • git_repo_plugins: list of hashes with keys: path, package | This is used to install additional packages which may be installable from the same base repository.
  • git_package_name: string that will override the "egg" name given for the repo.