openstack/openstack-ansible
Code Issues Proposed changes
ad2f2e00e8
openstack-ansible/playbooks/defaults/repo_packages
History
Andrew Smith 899bc74a67 Replace rabbitmq references with oslo messaging 
This removes, everywhere applicable, the reference
_rabbitmq_, replacing it with the new oslo
counterpart. Shims for compatibility are explicitly
referenced, so that we can remove them later, when
the roles have been adapted appropriately.

It explicitly puts all the oslo messaging details
in one place, as this is easier to track. It is
applied on the all group, as most of the time, the
details are used by 2 or more roles.

This also updated spice-html5 git repository URL
as their code moved out of github. This also adds
some details in job log collection in order to be
able to gather more information about failures.

Depends-On: https://review.openstack.org/#/c/572413/
Depends-On: https://review.openstack.org/#/c/572565/
Depends-On: https://review.openstack.org/#/c/560574/
Change-Id: I1bab622e22d7d820fa2f774b4df60323b1eb7d1e
2018-06-06 12:29:02 -04:00
..
gnocchi.yml Update all SHAs for master 2018-04-13 07:57:21 +00:00
nova_consoles.yml Replace rabbitmq references with oslo messaging 2018-06-06 12:29:02 -04:00
openstack_services.yml Freeze the networking-odl repo from SHA bumps 2018-04-20 14:58:24 +01:00
readme.rst Remove git_dest variables 2017-03-13 16:44:39 -07: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_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.