2f35e36e54
The py_pkgs lookup plugin will now handle multiple sources. This change was needed to enable the system to allow for overrides of repo_package resources and general python packaging as found throughout the stack. The module has precedence as it loads / searches for packages and he item loaded last is the one that has the most precedence. The repo-build play has been updated to now search for compatible packages in the main playbook directory, the root ansible role directory and the user_variables file. Documentation has been added regarding this capability and how to override and set items to meet the needs of the deployment. Closes-Bug: #1510575 Implements: blueprint independent-role-repositories Change-Id: Ib7cda14db18c0ca58bb5ac495d1c201812cf0f48 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
34 lines
2.0 KiB
ReStructuredText
34 lines
2.0 KiB
ReStructuredText
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.
|