Jakob Meng 4db7a6238b Changed TripleO jobs to use correct release files
Commit bc27851617 [1] in opendev.org/openstack/tripleo-ci changed the
release filename for periodic jobs to promotion-testing-hash-*.yml [2]
instead of using e.g. train.yml for OpenStack Train based releases [3].
Due to this change, container images were not pulled from the local
image registry but from trunk.registry.rdoproject.org instead [2]. This
caused our periodic jobs to fail during container image build because
when using a local registry a different namespace prefix "openstack"
(instead of *-binary such as centos-binary) is used which is not valid
on trunk.registry.rdoproject.org.

As a workaround, we force TripleO jobs to run as check jobs, no matter
what pipeline they run in [4].

Thanks to Sandeep Yadav <sandyada@redhat.com> for discovering the root
cause of this issue and providing a workaround!

Ref.:
[1] bc27851617
[2] https://github.com/openstack/tripleo-quickstart/blob/master/config/release/tripleo-ci/CentOS-8/promotion-testing-hash-train.yml#L7
[3] https://github.com/openstack/tripleo-quickstart/blob/master/config/release/tripleo-ci/CentOS-8/train.yml
[4] https://opendev.org/openstack/tripleo-ci/src/branch/master/roles/ci-common-vars/vars/main.yaml#L24

Change-Id: Ib7d8fc9e6781e43e04f0a9feee261b9f3f29e1fe
2022-05-11 11:47:31 +02:00
2022-03-09 20:17:52 +01:00
2022-05-11 06:50:33 +00:00
2020-06-23 21:50:43 +03:00
2022-03-09 22:20:40 +02:00
2022-03-31 20:05:06 +00:00
2019-09-25 15:21:42 +00:00
2021-05-19 14:04:33 -04:00
2022-03-09 20:17:52 +01:00
2020-05-13 08:07:01 -05:00
2020-03-05 15:08:38 +00:00
2020-06-04 14:23:23 +00:00

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.

⚠️ WARNING: This collection is currently being ported to the upcoming OpenStack SDK 1.* release. SDK version 1.* introduces numerous API changes which break backward compatibility with previous 0.* releases. Since keeping a single collection release compatible with both SDK series is not sustainable, our collection codebase has been split: Branch stable/1.0.0 and 1.*.* releases of the collection are compatible with previous OpenStack SDK 0.* releases only. The master branch and upcoming 2.*.* releases of this collection will be compatible with SDK 1.* only. Both branches will continue to be maintained for now. Patches from master will be backported to stable/1.0.0 on a best effort basis but expect new features to be introduced in the master branch only. Contributions are welcome for both branches! ⚠️

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.

Description
Ansible Modules Collection for using OpenStack
Readme 17 MiB
Languages
Python 99.3%
Shell 0.7%