ansible-role-python_venv_build/vars/main.yml

79 lines
2.9 KiB
YAML

---
# Copyright 2018, 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.
_venv_build_base_distro_package_list:
debian:
- cmake
- gcc
- "{{ (venv_python_executable == 'python2') | ternary('pkg-config', 'python3-pkgconfig') }}"
- "{{ (venv_python_executable == 'python2') | ternary('python-dev', 'python3-dev') }}"
gentoo:
- dev-util/cmake
redhat:
- autoconf
- cmake
- gcc
- gcc-c++
- "{{ (venv_python_executable == 'python2') | ternary('python2-devel', 'python3-devel') }}"
suse:
- autoconf
- cmake
- gcc
- gcc-c++
- "{{ (venv_python_executable == 'python2') | ternary('python-devel', 'python3-devel') }}"
# Set the available build targets for all nodes within an environment.
# build targets are grouped based on operating system and CPU
# architecture.
#
# This is the data structure used to determine the build host.
# venv_build_targets:
# {
# ansible_distribution_version: {
# ansible_architecture: inventory_hostname
# }
# }
#
# Auto generation process:
# * The automatic build targets will iterate over the group name
# "repo_all" and if any target is found it will catagorize it
# using the distro and cpu architecture criteria.
# * If no group named "repo_all" is found the current inventory
# hostname will be used as the only available build target.
# * If no build target is found for matching the distro and cpu
# criteria of the active inventory item, the generator will fall
# back to using the active inventory host as the build target.
#
# NOTE: (cloudnull): While there may be multiple inventory items
# that match a single distro and CPU architecture
# type, only one build target will ever be used.
# To make more than one build target effective,
# deployers should be using a shared file system
# for the repo servers.
venv_build_targets: |-
{% set targets = {
(ansible_distribution_version | string): {
(ansible_architecture | string): (inventory_hostname | string)
}
}
%}
{% for item in (groups['repo_all'] | default([inventory_hostname])) %}
{% set distro = hostvars[item]['ansible_distribution_version'] %}
{% set arch = hostvars[item]['ansible_architecture'] %}
{% set target_item = {(arch | string): (item | string)} %}
{% set _ = targets.__setitem__(distro, target_item) %}
{% endfor %}
{{ targets }}