Logan V 86a697cf4b Fix bashate xargs run
Bashate does not fail for "E004 File did not end with a newline"
properly unless the file is the last in the list when multiple
check files are provided (as we do with xargs). Since the file order
is random, if only 1 or 2 files are failing, this can cause very
random linter failures.

The solution is to use 'xargs -n1' to pass only 1 file to each
bashate process.

See also https://review.openstack.org/#/c/614542/

Change-Id: I2186795510c2327571e7631b45de8a112f4d4445
2019-03-13 12:09:39 -05:00
2018-07-12 16:44:20 +02:00
2018-09-12 16:40:51 -06:00
2018-03-15 07:42:10 +00:00
2018-08-10 16:49:52 +00:00
2018-08-17 14:16:36 -04:00
2018-10-01 11:16:21 -05:00
2019-02-22 13:49:51 -06:00
2018-04-11 13:49:00 +02:00
2016-05-26 11:33:41 +01:00
2018-06-19 17:08:11 +08:00
2019-02-22 13:49:51 -06:00
2017-03-02 11:52:36 +00:00
2019-03-13 12:09:39 -05:00
2018-07-06 10:18:02 +07:00
2018-09-24 11:51:53 +01:00

Team and repository tags

image

OpenStack-Ansible testing

This is the openstack-ansible-tests repository, providing a framework and consolidation of testing configuration and playbooks. This can be used to integrate new projects, and ensure that code duplication is minimized whilst allowing the addition of new testing scenarios with greater ease.

Role Integration

To enable the openstack-ansible-tests repository, ensure that the tox.ini configuration in the role repository matches the galera_client repository tox.ini with the exception of the value for ROLE_NAME. A more advanced configuration which implements multiple functional test scenarios is available in the neutron role tox.ini.

To override variables you can create a ${rolename}-overrides.yml file inside the role's tests folder. This variable file can be includes in the functional tox target configuration in tox.ini as demonstrated in the following extract:

ansible-playbook -i {toxinidir}/tests/inventory \
                 -e @{toxinidir}/tests/${rolename}-overrides.yml \
                 {toxinidir}/tests/test.yml -vvvv

In your repositories tests/test.yml file, you can call any of the included playbooks, for example:

- include: common/test-prepare-keys.yml

Network Settings

The networking can be configured and setup using the bridges variable.

The base option, when only 1 interface is required is to specify just a single base - this is only for backwards compatibility with existing test setup and will default to br-mgmt with an IP of 10.1.0.1.

bridges:
  - "br-mgmt"

To allow a more complicated network setup we can specify ip_addr: The IP address on the interface. netmask: Netmask of the interface (defaults to 255.255.255.0) name: Name of the interface veth_peer: Set up a veth peer for the interface alias: Add an alias IP address

For example, a Nova setup may look like this:

bridges:
  - name: "br-mgmt"
    ip_addr: "10.1.0.1"
  - name: "br-vxlan"
    ip_addr: "10.1.1.1"
  - name: "br-vlan"
    ip_addr: "10.1.2.200"
    veth_peer: "eth12"
    alias: "10.1.2.1"
Documentation for the project can be found at:

https://docs.openstack.org/openstack-ansible-tests/latest/

Release notes for the project can be found at:

https://docs.openstack.org/releasenotes/openstack-ansible-tests/

The project home is at:

https://launchpad.net/openstack-ansible

Description
DEPRECATED, Common testing content for OpenStack-Ansible
Readme 11 MiB