History

Jean-Philippe Evrard abe0b22c76 Update all SHAs for milestone 3

This patch updates all the roles to the latest available stable
SHA's, copies the release notes from the updated roles into the
integrated repo, updates all the OpenStack Service SHA's, and
updates the appropriate python requirements pins.

We also had to make master branch install HEAD of tempest
master: without it, all the sha bumps of keystone would fail in
tempest, as there are discrepencies between latest keystone
and 18.0.0 tempest (the pip installed version).

In order to install tempest from master branch, the workaround in
the gates is:
- Keeping the same behavior as currently when not on master branch
  (installing tempest from pip packages)
- Installing master of tempest without using enabling the
  repo build for everyone, until a new version of tempest
  is released with the patch [1] included.

[1]: 7d2b636a30

Depends-On: https://review.openstack.org/#/c/573398/
Depends-On: https://review.openstack.org/#/c/583955/
Change-Id: I1edfc43ac571198fcb592ae8e97dcc85d20940af

2018-07-19 22:37:48 +02:00

gnocchi.yml

Update all SHAs for milestone 3

2018-07-19 22:37:48 +02:00

nova_consoles.yml

Update all SHAs for milestone 3

2018-07-19 22:37:48 +02:00

openstack_services.yml

Update all SHAs for milestone 3

2018-07-19 22:37:48 +02: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.