925273f524
Trying to reverse proxy upstream pypi has not turned out to be very stable, or very useful. We've had many, many reports of stability issues and the additional complexity for offline and proxy usage is just not worth it. Given we already have a mechanism in place to handle using upstream pypi if the repo server is not there yet, disabling this should just result in that mechanism kicking in and all will be well again. Once the repo is built, the reverse proxy to pypiserver will then be exclusively used and the upstream pypi proxy is not necessary anyway. Change-Id: Ic6e4a2d24040655fdd575477ea7438fd6e4d58d9 Needed-By: https://review.openstack.org/584385
76 lines
3.0 KiB
YAML
76 lines
3.0 KiB
YAML
---
|
|
# Copyright 2016, Rackspace US, Inc.
|
|
#
|
|
# 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.
|
|
|
|
# Ensure that the package state matches the global setting
|
|
repo_server_package_state: "{{ package_state }}"
|
|
repo_build_package_state: "{{ package_state }}"
|
|
|
|
# Optionally set this variable to the location on the deployment
|
|
# host where a set of git clones may be sourced to stage the repo
|
|
# server.
|
|
#repo_build_git_cache: /opt/git/openstack/
|
|
|
|
# The folder in the repo container where the git clones should
|
|
# be synchronised to.
|
|
repo_build_git_dir: /var/www/repo/openstackgit
|
|
|
|
# The folder in the repo container which is bind-mounted to
|
|
# the host.
|
|
repo_service_home_folder: /var/www
|
|
|
|
# The folder on the repo container's host which will hold
|
|
# the git clones via the container-host bind-mount
|
|
repo_build_git_bind_mount: "/openstack/{{ inventory_hostname }}{{ repo_build_git_dir | replace(repo_service_home_folder, '') }}"
|
|
|
|
# The appropriate user:group names for the repo_build_git_dir
|
|
# folder/file attributes.
|
|
repo_service_user_name: nginx
|
|
repo_service_group_name: www-data
|
|
|
|
# Ensure that the repo service and the repo build use the same user:group
|
|
repo_build_service_user_name: "{{ repo_service_user_name }}"
|
|
repo_build_service_group_name: "{{ repo_service_group_name }}"
|
|
|
|
# The following package must always build from source.
|
|
#
|
|
# libvirt-python:
|
|
# A pre-built wheel can be missing libvirt capabilities from the installed
|
|
# version of libvirt-bin, leading to nova-compute failing to start.
|
|
#
|
|
# NOTE(hwoarang) cryptography may bundle openssl in the wheel and that
|
|
# causes symbol conflicts if a different openssl is provided by the
|
|
# distribution. As such, it's probably safer to re-build cryptography
|
|
# ourselves just to be sure that the correct distro libraries are used
|
|
# see https://github.com/pyca/cryptography/issues/3804
|
|
# This keeps popping up every now and then so it might worth keeping this
|
|
# around even if the upstream issue is resolved
|
|
# The upstream issue should be resolved now, and we are testing
|
|
# cryptography with the usage of wheels by removing it from no_binary.
|
|
repo_build_pip_no_binary:
|
|
- libvirt-python
|
|
|
|
# Set the build tag and the repo version
|
|
repo_build_release_tag: "{{ openstack_release }}"
|
|
repo_build_os_distro_version: "{{ os_distro_version }}"
|
|
|
|
# This is required because the nova package list has a conditional package
|
|
# based on this var.
|
|
nova_barbican_enabled: "{{ hostvars['localhost']['nova_barbican_enabled'] }}"
|
|
|
|
pkg_locations:
|
|
- "{{ playbook_dir }}/../"
|
|
- /etc/ansible/roles
|
|
- /etc/openstack_deploy
|