As jenkins docs job use venv envrionment to work, we
need add such section to make it work.
Partially-Implements: blueprint kolla-tox-doc
Change-Id: I716219515f2bf1375fd094b3aeca866cbcf5c7c6
There is no longer a docker build system in the tree. Remove
the cruft that was missed in the original removal patches.
Partially-Implements: blueprint gate-source-builds
Change-Id: I4e6132502e8c0f812a0b3a767dd9c7f5c7b92fe3
The template option is deprecated and --template is now default.
Also rename the tox jobs test calls since we won't have Docker
build operations.
Change-Id: I99df9c337680003e042e7e56a19d6cae2a59ed74
Partially-Implements: blueprint gate-source-builds
Updated build.py to reflect this change.
Deprecate --template option and make it a noop.
Change-Id: I7cd98d1ee684a4c64984a49597159868152683b2
Partially-Implements: blueprint remove-docker-dir
Remove the docker directory (yay) and old build tools.
This will result in an f21 failing gate - however, I have a patch
submission to remove that gate from our project configuration.
Change-Id: I3c461cedb6906422c8076f60c470e773d6cdcf33
Partially-Implements: blueprint remove-docker-dir
Start off the removal of the docker directory by making the gate
only run against docker templates. The idea is we are going to
from this patch set forward completely abandon the functioning of
the docker directory and focus on making templates work properly.
In order to facilitate that, this patch set makes sure each change
gates properly for the changed service in the Templates build.
Note because git review and gerrit can't keep history on removal
followed by a git move operation, we first git rm the files affected
then git mv them to get the gate working again.
Every other patch in this patch set will fail the gate. That is
expected behavior.
Change-Id: I1be2e2638aef4ada038bfe5f3dd563f040542df2
Many tiers have been shed over this issue and frankly enough is enough
on this tiering thing, it's tiering us apart! Now we use threading a
bit better as well.
No more tiers! Puns very much intended.
Additionally, this refactors the function names to make inc0 happier
and be consistent.
We also modify the test_build.py to catch the new statuses introduced
by the regex patch. Then we remove the Ubuntu Source from the Docker
folder test as that will never ever be functional.
Also fixed regex to properly match true regex expressions.
Co-Authored-By: Michal Jastrzebski (inc0) <michal.jastrzebski@intel.com>
Change-Id: I650fd6af76eddb809756762222e66aefd6fc1dca
Partially-Implements: blueprint build-script
We will gate on all combos of:
/docker
/docker_templates
Centos
Ubuntu
Binary
Source
Except for Ubuntu + Binary because there is no delorean
style repository for Ubuntu.
Change-Id: Ic1ed8c22c2f86ff339299939da9ac492a7c7c5f5
Partially-Impelements: blueprint gate-source-builds
The tox targets were previously src and rdo when they should
have been source and binary.
The gate review has been changed to these as well.
Change-Id: Ib09980c77e5859fa28a54953fc1f3f123c1886d7
This adds a new test script for the new python based build script. A new
tox target has been created to execute it for usage in the gate.
Eventually, the other build script stuff can be deleted, but that won't
be done until full functionality exists in the new build.py.
Change-Id: Id9dd19926b1b9d875dcb069fd13d6450318374c8
Paritally-Implements: blueprint build-script
The fedora version of docker is hacked by Red Hat to have specific
features which we don't want in the gating. Use the pristine
upstream version from Docker Inc.
Change-Id: Ied219bc3868176f541083e9d42cde7d6cdeeb71d
Partially-Implements: blueprint gate-source-builds
We don't use config-internal anymore, so remove validate-min-env-vars
from being gated upon. This is becuse there is no minimum
environment variables required. While we are at it we remove
min-env.
Partially-Implements: blueprint remove-config-internal
Change-Id: Ibe2947b35e4dc1549e82acc66c01153495a91882
Currently we require a slew of deps on each destination node, this
includes a gcc compiler and installing things via pip. We can remove
these dependencies by containerizing them and running and Ansible
inside the container itself. The container would then report back
facts about idempotency.
DocImpact
Closes-Bug: #1481495
Implements: blueprint containerize-dependencies
Change-Id: I3dfccbf9fafc06ffc36e78f3006fe5d3367891df
Renamed kolla script to kolla-compose
Update change in the dev guide also
Change-Id: I6cae3d13752ecb4bb3deeb91c5e0f827fde80c2a
Implements: blueprint kolla-compose-script
Added additional tox test for json / yaml / link /
dockerfile validation. This currently mimics the
existing pep8 test which will be updated to run flake8
Change-Id: Id4657e6d4f4921ab419dc84e8d62468a827aaeb1
Implements: blueprint rename-pep8-validate
1. Move setup_docker.sh to tools directory
2. Make a setup_gate.sh that installs necessary packages including
docker and starts docker.
3. Add logging output.
4. Add default test timeout of 2 hours.
5. Add user to the docker group before running test cases.
6. Run image build as dockerroot group.
This patch has to be one commit to fix the gate in one go.
Co-Authored-By: Steven Dake <stdake@cisco.com>
Change-Id: I83f3cdb1dabf0dfface589c581cb22c155467acc
This adds functional tests to tox, along with a number of prerequisite
steps. Since this is primarily a bash project, pbr usage has been avoided.
Tests are to be written in python and put in the tests directory.
Running tox -e setupenv will execute a setup script
(tests/setup_docker.sh) to ensure the running instance of docker meets
the minimum version requirement.
Running tox -e images will execute the image building script
(tools/build-all-docker-images) and will parse the resulting output to report
failures.
Running tox -e startenv will generate the environment file, run
"tools/kolla start", and run first time initialization (eventually).
Running tox -e functional is for actually testing the deployed OpenStack
environment via a series of tests utilizing the client APIs.
Change-Id: Iff6dfdca43f0c44d471e7540a7836e56a0de4507
When discussing with the infra guys they have mentioned it would be
easier to call our linting job pep8, it's indeed badly named but that
target has been used all over openstack for linting projects. As a bonus
point it would make things easier to add the job to the gate. To make
that patch much more interesting than a three characters change I have
improved the validate-samples script to detect if jsonlint was present
and if not fallback to the standard python -mjson.tool which give you
less details but nonetheless works if jsonlint is present.
Change-Id: I8d71a229917004dfd7223a16e4f270101cf2f0a8
This is a simple JSON validation script based on demjson python library,
we do some shell script trickeries to exit properly if there is a
failure for tox (should probably patch demjson to properly exit
instead).
Change-Id: I930908336deef7daeaab5b55ba2031c64698d880
Implements: blueprint json-validation-gate