Ansible Modules Collection for using OpenStack
Go to file
Jakob Meng f89e9f031e Fixed branch matching for parent jobs when on stable/1.0.0 branch
When a patch is submitted against a branch, Zuul CI will collect job
variants for each ci job and all its parent jobs. If both job.\
override-checkout and job.required-projects.override-checkout
attributes are not defined, then Zuul will for each (parent) job match
the current branch of the patch against all branches of the project in
which the job is defined. If no such branch exist in a project, then no
job variant matches and this job will be ignored [1].
For example, if a patch is submitted for our stable/1.0.0 branch, then
Zuul CI will try to match 'stable/1.0.0' against all branches in the
projects where job ansible-collections-openstack-functional-devstack
and its parent job openstacksdk-functional-devstack are defined. The
first is defined in openstack/ansible-collections-openstack/.zuul.yaml,
so a match for stable/1.0.0 will be found. But openstacksdk-functional-\
devstack is defined in openstack/openstacksdk/.zuul.yaml which has no
branch stable/1.0.0 defined. So Zuul will not schedule job ansible-\
collections-openstack-functional-devstack at all.

The solution is twofold. First, the base jobs such as ansible-\
collections-openstack-functional-devstack have to be changed to always
checkout existing branches in projects which define (parent) jobs.
Using job.override-checkout might have unintended sideeffects because
it will checkout the specified branch for all required projects which
also includes the project which the patch was submitted for. Instead
we set job.required-projects.override-checkout for all projects which
define parent jobs. For example, in ansible-collections-openstack-\
functional-devstack we set job.required-projects.override-checkout to
master for opendev.org/openstack/devstack which defines parent job
openstack-functional-devstack.

In child jobs which (re)define job.override-checkout, we have to change
job.required-projects.override-checkout for all projects which define
parent jobs to the value of job.override-checkout. If we fail to update
job.required-projects.override-checkout then Zuul will checkout the
branch which was defined in the base jobs because job.\
required-projects.override-checkout has higher precedence than job.\
override-checkout.

Setting attribute project.<pipeline>.debug to true helps with debugging
these job scheduling issues. "If this is set to true, Zuul will include
debugging information in reports it makes about items in the pipeline.
This should not normally be set, but in situations were it is difficult
to determine why Zuul did or did not run a certain job, the additional
information this provides may help" [2].

Note, once job scheduling has been completed, Zuul will use a different
algorithm to checkout projects which are listed in job.\
required-projects [3][4]. It will fallback to a default branch if no
matching branch can be found in projects [5].

Ref.:
[1] https://opendev.org/zuul/zuul/src/branch/master/zuul/model.py#L6996
[2] https://zuul-ci.org/docs/zuul/latest/config/project.html#attr-project.%3Cpipeline%3E.debug
[3] https://zuul-ci.org/docs/zuul/latest/job-content.html#git-repositories
[4] https://opendev.org/zuul/zuul/src/branch/master/zuul/executor/server.py#L1648
[5] https://zuul-ci.org/docs/zuul/latest/config/project.html#attr-project.default-branch

Change-Id: I31f9607ab7e2e2ae8534429da7f5e5f235560c56
2022-03-24 12:00:32 +01:00
changelogs Release 1.7.2 version 2022-03-10 11:43:44 +01:00
ci Fix assertion after stack deletion 2022-03-14 10:03:17 +00:00
contrib Update author lines 2020-06-23 21:50:43 +03:00
docs Fix docs for openstack fragment 2022-03-09 20:33:32 +00:00
meta Add openstack.cloud.baremetal_port module 2022-02-09 23:41:19 +01:00
plugins Remove old, unsupported parameters from documentation in image_info module 2022-03-18 10:57:44 +00:00
scripts/inventory Moved openstack inventory script from community.general 2020-04-13 15:22:18 +05:30
tests Move CI to use Ansible 2.12 version as main 2021-10-04 15:05:51 +03:00
tools Remove tests directory from ansible-tests 2021-08-16 16:06:10 +03:00
.gitignore Add galaxy.yml to support install from git 2020-10-21 09:12:05 +00:00
.gitreview Added .gitreview 2019-09-25 15:21:42 +00:00
.zuul.yaml Fixed branch matching for parent jobs when on stable/1.0.0 branch 2022-03-24 12:00:32 +01:00
CHANGELOG.rst Release 1.7.2 version 2022-03-10 11:43:44 +01:00
CONTRIBUTING.rst Add contributing file 2020-05-13 08:07:01 -05:00
COPYING Fix license metadata 2020-03-05 15:08:38 +00:00
README.md Bumped minimum required OpenStack SDK release to SDK 0.36.0 (Train) 2022-03-10 13:17:08 +00:00
bindep.txt Add bindep.txt for ansible-builder 2021-05-19 14:04:33 -04:00
galaxy.yml Release 1.7.2 version 2022-03-10 11:43:44 +01:00
galaxy.yml.in Add galaxy.yml to support install from git 2020-10-21 09:12:05 +00:00
requirements.txt Bumped minimum required OpenStack SDK release to SDK 0.36.0 (Train) 2022-03-10 13:17:08 +00:00
setup.cfg setup.cfg: Replace dashes with underscores 2021-04-29 17:38:54 +08:00
setup.py Add setup.py for install with pip 2020-06-04 14:23:23 +00:00
test-requirements-2.9.txt Fix linters for new ansible release 2020-09-24 23:59:26 +03:00
test-requirements-2.11.txt Fix Ansible devel jobs 2020-11-24 22:40:09 +02:00
test-requirements-2.12.txt Move CI to use Ansible 2.12 version as main 2021-10-04 15:05:51 +03:00
test-requirements.txt Fixed job hierarchy in Zuul CI configuration 2022-03-24 10:43:02 +01:00
tox.ini Move CI to use Ansible 2.12 version as main 2021-10-04 15:05:51 +03:00

README.md

OpenDev Zuul Builds - Ansible Collection OpenStack

Ansible Collection: openstack.cloud

This repo hosts the openstack.cloud Ansible Collection.

The collection includes the Openstack modules and plugins supported by Openstack community to help the management of Openstack infrastructure.

Installation and Usage

Installing dependencies

For using the Openstack Cloud collection firstly you need to install ansible and openstacksdk Python modules on your Ansible controller. For example with pip:

pip install "ansible>=2.9" "openstacksdk>=0.36"

OpenStackSDK has to be available to Ansible and to the Python interpreter on the host, where Ansible executes the module (target host). Please note, that under some circumstances Ansible might invoke a non-standard Python interpreter on the target host. Using Python version 3 is highly recommended for OpenstackSDK and strongly required from OpenstackSDK version 0.39.0.


NOTE

OpenstackSDK is better to be the last stable version. It should NOT be installed on Openstack nodes, but rather on operators host (aka "Ansible controller"). OpenstackSDK from last version supports operations on all Openstack cloud versions. Therefore OpenstackSDK module version doesn't have to match Openstack cloud version usually.


Installing the Collection from Ansible Galaxy

Before using the Openstack Cloud collection, you need to install the collection with the ansible-galaxy CLI:

ansible-galaxy collection install openstack.cloud

You can also include it in a requirements.yml file and install it through ansible-galaxy collection install -r requirements.yml using the format:

collections:
- name: openstack.cloud

Playbooks

To use a module from the Openstack Cloud collection, please reference the full namespace, collection name, and module name that you want to use:

---
- name: Using Openstack Cloud collection
  hosts: localhost
  tasks:
    - openstack.cloud.server:
        name: vm
        state: present
        cloud: openstack
        region_name: ams01
        image: Ubuntu Server 14.04
        flavor_ram: 4096
        boot_from_volume: True
        volume_size: 75

Or you can add the full namespace and collection name in the collections element:

---
- name: Using Openstack Cloud collection
  hosts: localhost
  collections:
    - openstack.cloud
  tasks:
    - server_volume:
        state: present
        cloud: openstack
        server: Mysql-server
        volume: mysql-data
        device: /dev/vdb

Usage

See the collection docs at Ansible site:

Contributing

For information on contributing, please see CONTRIBUTING

There are many ways in which you can participate in the project, for example:

We work with OpenDev Gerrit, pull requests submitted through GitHub will be ignored.

Testing and Development

If you want to develop new content for this collection or improve what is already here, the easiest way to work on the collection is to clone it into one of the configured COLLECTIONS_PATHS, and work on it there.

Testing with ansible-test

We use ansible-test for sanity:

tox -e linters

More Information

TBD

Communication

We have a dedicated Interest Group for Openstack Ansible modules. You can find other people interested in this in #openstack-ansible-sig on OFTC IRC.

License

GNU General Public License v3.0 or later

See LICENCE to see the full text.