e6ad4cf7cf
This patch updates all the roles to the latest available SHA's, updates all the OpenStack Service SHA's and also updates the appropriate python requirements pins. This patch also includes the following changes to unblock the gate. * os_.* services need RabbitMQ connection config The *_rabbitmq_host_group vars. * Recent changes in the os_nova role require us to bump all of the SHAs to support a more updated newton release. * changes to "get-pypi-pkg-version.py" were required because pypi no longer allows http requests. * The "repo_build_pip_no_binary" capability has been added to the AIO to support a fully capable "libvirt-python" library which is required by nova. This ensures that the OpenStack-Infra provided wheels are not used as they are compiled without the right C libraries on the host. * Ansible is configured to use ssh instead of 'smart' connections and to use a shorter timeout. This change is made to improve the reliability and speed of connections and to prevent flip-flopping between ssh and paramiko connectivity. * "ansible_ssh_extra_args" are set in group_vars/all to improve performance. Change-Id: I4509b11684efda20defe3ebe0a651a8db9a61f70 Implements: blueprint multi-rabbitmq-clusters Signed-off-by: Kevin Carter <kevin.carter@rackspace.com> |
||
---|---|---|
.. | ||
openstack_other.yml | ||
openstack_services.yml | ||
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
ofhashes
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.
- git_repo: