openstack/openstack-ansible
Code Issues Proposed changes
e148635e78
openstack-ansible/playbooks/defaults/repo_packages
History
kevin 2086f6edb1 Updated tempest isolation options 
This change updates the way that the packages are installed in an
isolated deployment. This ensures that our build packages are used
within the deployment while also allowing temptest to go online and
consume upstream packages from pypi. Additionally this updates
tempest-lib which is needed to make keystone w/ fernet tokens go as
there is an upstream issues with date timestamps with all versions
of tempest-lib that will prohibit the use of fernet tokens.

Change-Id: Ia479610b9ab69d64d1de756099d840b2ab331378
Related-Bug: #1466010
2015-06-24 23:29:42 +00:00
..
openstack_clients.yml Updated master to the latest SHAs - 22.06.2015 2015-06-24 15:50:42 +00:00
openstack_other.yml Updated tempest isolation options 2015-06-24 23:29:42 +00:00
openstack_services.yml Updated master to the latest SHAs - 22.06.2015 2015-06-24 15:50:42 +00:00
python2_lxc.yml Moved the playbook vars to defaults 2015-05-14 12:32:36 -05:00
readme.rst Moved the playbook vars to defaults 2015-05-14 12:32:36 -05: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 "_"
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.