Commit Graph

37 Commits

Author SHA1 Message Date
Ghanshyam Mann c2ff9b8f49 Retire Tripleo: remove repo content
TripleO project is retiring
- https://review.opendev.org/c/openstack/governance/+/905145

this commit remove the content of this project repo

Change-Id: I7f1dc7801a025d9bb28110f74340846b99870b79
2024-02-24 11:43:13 -08:00
Jiri Podivin 8d17681d3d Capping ansible-lint version
Closes-Bug: #2004633

Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: I0b1a4a8d534ca985f7430255c8add86211e5ddab
2023-02-06 13:41:21 +01:00
rabi 90cf6a6dbe Switch to stestr
stestr is maintained project to which all Openstack projects
should use.

Change-Id: I18a83ef1909e758e82f7e9d888d65363a4528249
2022-04-08 19:43:56 +05:30
Sorin Sbarnea a013f42e36 Enable ansible-lint
- enable run of ansible-lint, with a temporary set of excludes
- fixes two problems reported by ansible-linter

Change-Id: Ibbe23db8fd5ac1008109f50f514df96686b0fa19
Bug: #1921409
2021-03-30 09:18:15 +01:00
Hervé Beraud fea7fa2d9c Add doc/requirements
We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].
Removed specific doc requirements from test-requirements.txt.

The problem here is that this repos haven't doc/requirements.txt file
and by default in this case zuul will use the test-requirements.txt file
to
pull requirements [4].

This requirements file contains extra requirements like flake8 that
collided with those allowed in our job environment and so the new pip
resolver fails to install these requirements and the job exits in error.

This project meet the conditions leading to the bug.

/!\/!\/!\
Notice that I voluntarily added the doc directory even if no docs
are generated here because zuul will try to pull this requirements from
there first and the contained requirements are needed for reno but AFAIK
the releasenotes dir is ignored by zuul. c.f [4] for further details.
/!\/!\/!\

[1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html
[4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36

Change-Id: I519ef389448acb3dde328a0e61c074e48d7e0466
2021-01-05 09:49:46 +01:00
Michele Baldessari 87b365afd3 Fix Flakes and lower-constraints errors
With the switch to Ubuntu Focal for tox jobs via https://review.opendev.org/#/c/738322/
our 1.1.0 version of hacking pulls in old modules that are not compatible
with python3.8:
https://github.com/openstack/hacking/blob/1.1.0/requirements.txt#L6

Let's upgrade hacking to >= 3.0.1 and < 3.1.0 so that it supports python3.8
correctly. The newer hacking also triggered new errors which are
fixed in this review as well:
./tools/render-ansible-tasks.py:113:25: F841 local variable 'e' is assigned to but never used
./tools/yaml-validate.py:541:19: F999 '...'.format(...) has unused arguments at position(s): 2
./tools/render-ansible-tasks.py:126:1: E305 expected 2 blank lines after class or function definition, found 1
./tools/yaml-validate.py:33:1: E305 expected 2 blank lines after class or function definition, found 1
./container_config_scripts/tests/test_nova_statedir_ownership.py:35:1: E305 expected 2 blank lines after class or function definition, found 0

Also make sure we exclude .tox and __pycache__ from flake8 as well

We also need to change the lower-constraint requirements to make them
py3.8 compatible. See https://bugs.launchpad.net/nova/+bug/1886298
cffi==1.14.0
greenlet==0.4.15
MarkupSafe==1.1.0
paramiko==2.7.1

Suggested-By: Yatin Karel <ykarel@redhat.com>

Change-Id: Ic280ce9a51f26d165d4e93ba0dc0c47cdf8d7961
Closes-Bug: #1895093
2020-09-10 11:10:54 +02:00
Hervé Beraud 11f84b6302 Use unittest.mock instead of mock
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.

Change-Id: Iabd3e90a46fd087c8e780796e04fcc050c5277ab
2020-06-09 18:41:21 +02:00
Emilien Macchi 910d54b608 test-requirements: remove python 2.7 dependency for sphinx
We no more have python27 support, we need to remove that dependency from
the test requirements.
Also update the syntax of sphinx dep to match with the requirements.

Change-Id: Ia2ff347b095dd4829425b9c4acbc71e31f240dc2
2020-05-29 09:07:18 -04:00
Zuul 5504f947ea Merge "tox: Keeping going with docs" 2019-11-07 20:02:09 +00:00
gujin bfa44f0bbe tox: Keeping going with docs
Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.

[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045

Change-Id: I806842ce6d2522deab060f5e9ef6607a1e919dbf
2019-11-03 02:44:38 +08:00
Carlos Camacho 0de387ee3c Ansible lint check in THT
Until now if there is a nit inside any
Ansible task part of tripleo-heat-templates we will
need to wait until the end-to-end test imports
the actual tasks to fail.

This submission adds the hability to run a syntax
check for any Ansible task part of any role
defined by default in the resource registry.

Also it will allow to reduce the CI CO2 footprint
by not executing unneeded jobs meant to fail.
Let's save the planet and some CI cycles.

Change-Id: I6eb7c873cc9a4b7d765e745dc260475bff7b268a
2019-10-30 04:56:05 -04:00
jacky06 2f69815a18 Sync Sphinx requirement
Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.

Change-Id: Id28b0bc4b76fa42113f2aff6def198a39b1f8717
Closes-Bug: #1830827
2019-05-29 11:23:29 +08:00
confi-surya 13d0057c99 Update hacking version
Use latest release 1.1.0 and compatible changes w.r.t pep8

Change-Id: I23612ab78f858ad4fcd84268ada47160057a097d
2018-12-31 17:42:10 +00:00
Oliver Walsh 58624abf5f Improve nova statedir ownership logic
The nova_compute container kolla config is currently set to recursively change
the ownership of /var/lib/nova to nova:nova on startup.

This is necessary when upgrading from an non-container deployment to a
containerized deployment as the nova uids are not consistent across the host
and container image.

If the nova instancedir is an NFS mount then open filehandles are
broken and every VM using that NFS export fails with I/O errors.

This change re-implements the nova statedir ownership logic to target only the
files/directories controlled by nova.

Requires dist-git change: https://review.rdoproject.org/r/14734

Change-Id: I57d421feb6356d28002e77fb9bfa50a397758cbf
Closes-bug: 1778465
2018-07-09 17:07:30 +01:00
OpenStack Proposal Bot c2d1a7c9bb Updated from global requirements
Change-Id: I958e335d8f4d87fe118bff9b437c36962ed3fef0
2018-03-15 09:38:11 +00:00
OpenStack Proposal Bot c7d0e5a4d2 Updated from global requirements
Change-Id: I2ddf6426d660321c957600eb8b56ed0b9888b0b8
2018-03-13 07:36:30 +00:00
OpenStack Proposal Bot 3a635efaa9 Updated from global requirements
Change-Id: I777f74854ce5325636f6282c6a5de03d7bb4c941
2018-03-10 13:58:37 +00:00
Zuul 47018f5bd9 Merge "Introduce tests for yaql structures" 2018-01-31 09:24:26 +00:00
OpenStack Proposal Bot 01ae6094fd Updated from global requirements
Change-Id: I64b78e7ebb71699a92c4005577706635f2e5e4a2
2018-01-24 01:39:53 +00:00
OpenStack Proposal Bot bee24f0c13 Updated from global requirements
Change-Id: Ifd3529ae312c593dab801855d683b4ba08450dd2
2018-01-18 03:38:12 +00:00
Thomas Herve e10d529b46 Introduce tests for yaql structures
We use yaql in many hot templates, but they are usually faily obscure
and not documented, which makes it hard to change them over time (to
make them perform better for example).

This introduces some basic infrastructure for testing them, as well as a
first modification to show how things would be easier to change.

Change-Id: I1a8d3a514d8fa0de4b024d3ae320723d791f3e7d
2018-01-17 14:36:06 +01:00
OpenStack Proposal Bot 3d13febbc7 Updated from global requirements
Change-Id: Ib5402fdd0b0d2eb882f464c21bcac238defe6be1
I5d7257f6e9200b6def18cbb40e43eb2be4be7fe6
I451c6524b575a72eb45d6f6ab6d34be8fba0a090
2018-01-16 13:05:09 +00:00
OpenStack Proposal Bot 719a211f90 Updated from global requirements
Change-Id: I2f2ad0259ccf8d5be196cf060b1d4e35b2eca9e8
2017-11-16 11:30:33 +00:00
OpenStack Proposal Bot 0b60f60504 Updated from global requirements
Change-Id: I64eb6589063163445770bb350713765d5a4153c9
2017-09-26 03:38:07 +00:00
OpenStack Proposal Bot 5b84f8f1ff Updated from global requirements
Change-Id: I097c141e4bf9d681d1f3484fea0bce1fac7646c9
2017-07-19 22:32:37 +00:00
Emilien Macchi aa3b3e2203 Switch from oslosphinx to openstackdocstheme
As part of the docs migration work[0] for Pike we need to switch to use the
openstackdocstheme.

[0] https://review.openstack.org/#/c/472275/

Change-Id: Ib2b6afb7075c68fecf1fbeaf650a31a7494af49f
2017-07-06 10:33:29 -07:00
OpenStack Proposal Bot bbb3e60b16 Updated from global requirements
Change-Id: I714ecad87a406bc237e3d4fdf88bc7e10555693c
2017-07-04 17:59:34 +00:00
OpenStack Proposal Bot 9786bf57d2 Updated from global requirements
Change-Id: I9496de0e5cc670e0a370588a9471594b20fdadf3
2017-06-19 05:49:19 +00:00
Ben Nemec 4e24c8cb6a Sample environment generator
This is a tool to automate the generation of our sample environment
files.  It takes a yaml file as input, and based on the environments
defined in that file generates a number of sample environment files
from the parameters in the Heat templates.  A tox genconfig target
is added that mirrors how the other OpenStack services generate
their sample config files.

A description of the available options for the input file is
provided in a README file in the sample-env-generator directory.

In this commit only a single sample config is provided as a basic
example of how the tool works, but subsequent commits will add
more generated sample configs.

Change-Id: I855f33a61bba5337d844555a7c41b633b3327f7a
bp: environment-generator
2017-06-12 15:02:50 -05:00
OpenStack Proposal Bot 86ca8711d6 Updated from global requirements
Change-Id: I124d7f5bb0e662585a034668cd82ef1fa6db2fa1
2017-06-06 23:29:28 +00:00
OpenStack Proposal Bot b29441b187 Updated from global requirements
Change-Id: I468f654fa75b22aef398e2cba9c3625eb8f0767c
2017-05-22 15:58:04 +00:00
OpenStack Proposal Bot 093949dc5d Updated from global requirements
Change-Id: Ic4cfdedfc0a60ebfd2391d03112f68e7a11629ce
2017-02-14 06:02:06 +00:00
OpenStack Proposal Bot fa45e05f50 Updated from global requirements
Change-Id: Icadcb1b27852d729608195f4890f914c8350ac8c
2017-01-14 10:47:01 +00:00
Emilien Macchi 5efee26c97 Add ReNo support
Add ReNo support to manage release notes.
http://docs.openstack.org/developer/reno/

Change-Id: Ie5154d909e616e4e7e813052f9c121d6ac5b0875
2017-01-13 14:35:27 -05:00
Steven Hardy 3af65ff574 Fix error path for tools/process-templates.py
The error path for this fails because we don't import six
or install it in the templates tox venv

Change-Id: Ie9f46332f2b03d48a1b0a4a432e9721757833569
2017-01-11 11:47:11 +00:00
OpenStack Proposal Bot 216aa0d4db Updated from global requirements
Change-Id: I9ae60dfb2ef5e8fb5aae482ddb08206fc1980ca5
2017-01-10 09:44:01 +00:00
Chris Jones 80da8e3968 Add release configuration.
We can now release through openstack.org infrastructure.

Change-Id: I6dff6ae4a97db15bdc4ce419e46e9a125bec277c
2013-10-22 17:49:35 +01:00