network_environment¶
Role Documentation¶
Welcome to the “network_environment” role documentation.
Role Defaults¶
This section highlights all of the defaults and variables set within the “network_environment” role.
network_environment_path: environments/network-environment.yaml
plan_env_path: plan-environment.yaml
ip_pools_path: environments/ips-from-pool-all.yaml
Role Variables: main.yml¶
metadata:
name: Validate the Heat environment file for network configuration
description: >
This validates the network environment and nic-config files
that specify the overcloud network configuration and are stored
in the current plan's Swift container.
The deployers are expected to write these files themselves as
described in the Network Isolation guide:
http://tripleo.org/advanced_deployment/network_isolation.html
groups:
- pre-deployment
Molecule Scenarios¶
Molecule is being used to test the “network_environment” role. The following section highlights the drivers in service and provides an example playbook showing how the role is leveraged.
- Driver: podman
Scenario: default¶
Molecule Platform(s)¶
- name: centos
hostname: centos
image: centos/centos:stream8
registry:
url: quay.io
dockerfile: ../../../../.config/molecule/Dockerfile
pkg_extras: python*-setuptools python*-pyyaml
volumes:
- /etc/ci/mirror_info.sh:/etc/ci/mirror_info.sh:ro
privileged: true
environment:
http_proxy: "{{ lookup('env', 'http_proxy') }}"
https_proxy: "{{ lookup('env', 'https_proxy') }}"
ulimits:
- host
Molecule Inventory¶
hosts:
all:
hosts:
centos:
ansible_python_interpreter: /usr/bin/python3
Example default playbook¶
- name: Converge
hosts: all
gather_facts: false
tasks:
- name: Warn developers about the lack of molecule testing
fail:
msg: >-
This role needs molecule tests!