Jesse Pretorius 321fb7e69a Implement pypi-based install and package pinning for non u-c packages
Rally does not adhere to the global requirements process, so its
requirements extend beyond those managed by upper-constraints, and
sometimes are incompatible with upper constraints.

We have no need to track their development from git commit to git
commit, and can rather rely on stable releases which we verify are
working with the upper constraints whenever we do a pinning bump.

This keeps things simpler for us, and also allows the repo build
process in the integrated build to do a constrained venv build
instead of doing it unconstrained and breaking stable branch builds
down the line.

Depends-On: https://review.openstack.org/570906
Change-Id: If3d0120cf6f6f78463cf7805bc046382c3b6d44e
2018-05-29 16:16:20 +00:00

77 lines
2.9 KiB
YAML

---
# Copyright 2016, Comcast Corporation
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Set the package install state for distribution and pip packages
# Options are 'present' and 'latest'
rally_package_state: "latest"
rally_pip_package_state: "latest"
rally_system_group_name: rally
rally_system_user_name: rally
rally_system_user_comment: Rally System User
rally_system_user_shell: /bin/false
rally_system_user_home: "/var/lib/{{ rally_system_user_name }}"
rally_etc_directory: /etc/rally
# We comment `rally_git_repo` so that the repo_build role does not attempt to
# build the wheel from this repo/branch. Instead, we want rally to get built
# from the stable release defined in rally_pip_packages further down in this
# file.
#rally_git_repo: https://git.openstack.org/openstack/rally
rally_git_install_branch: master
rally_developer_mode: false
rally_developer_constraints:
- "git+{{ rally_git_repo }}@{{ rally_git_install_branch }}#egg=rally"
# Name of the virtual env to deploy into
rally_venv_tag: untagged
rally_bin: "/openstack/venvs/rally-{{ rally_venv_tag }}/bin"
# venv_download, even when true, will use the fallback method of building the
# venv from scratch if the venv download fails.
rally_venv_download: "{{ not rally_developer_mode | bool }}"
rally_venv_download_url: http://127.0.0.1/venvs/untagged/ubuntu/rally.tgz
# Database vars
rally_galera_database: rally
rally_galera_user: rally
rally_database_connection_string: mysql+pymysql://{{ rally_galera_user }}:{{ rally_galera_password }}@{{ rally_galera_address }}/{{ rally_galera_database }}?charset=utf8
# Packages that must be installed before anything else
rally_requires_pip_packages:
- virtualenv
# These pins are sourced from the rally git repository's
# upper-constraints file. These should be updated whenever
# the rally pin is updated. The package pins here are only
# those not already covered by upper constraints.
rally_pip_packages:
- ansible==2.4.3.0
- morph==0.1.2
- os-faults==0.1.17
- positional===1.2.1
- pymysql # not pinned as it is in u-c
- rally==0.12.1 # current release at 29 May 2018
# The inventory group where Rally will be installed.
# This variable is used by the repo_build process to determine
# which host group to check for members of before building the
# pip packages required by this role. The value is picked up
# by the py_pkgs lookup.
rally_role_project_group: utility_all
rally_config_overrides: {}