Placement is now ran by default for all latest supported releases
of openstack. This change removes the supported_releases field
to make sure each release of openstack we build now correctly
supports it.
Change-Id: I373f3f1e745d4af19f4266c48949c48d55e715eb
Also fixes related issue with distutils installation for Debian Stretch
and Ubuntu Xenial with py3: unlike in Bionic, distutils is installed with
python3 and python3-distutils package is not available in these distributions.
Run Debian build with py3 against stable/train, as master requires at
least python3.6, not available for distribution out of box.
Also increases job timeout to 5400 due to increased amount of builds.
Change-Id: I04c9253af80d941afb45231bee20f7bb1c4a96d4
This patch set makes the placement service voting and publish the
placement image for OpenStack releases: stein, train and master.
Change-Id: If180168fb2f60ecc4c7da3074409ea2ae3d354d8
Signed-off-by: Tin Lam <tin@irrational.io>
There's a need to keep building images from eol releases. This commit
introduces ability to specify eol release for project and clone to
{release}-eol instead of stable/{release}
Octavia moved to eol, using ocata-eol instead.
Also fixes gates providing ensure-pip role to executor.
Also pins openSUSE image to 15.1
Change-Id: I041033bb6c9cfe193c4bae9a0b6b4028f4602c5f
Signed-off-by: Andrii Ostapenko <andrii.ostapenko@att.com>
Introduces image build for bionic with py3 and nautilus.
Switches centos to py3 and fixes related issues.
Xenial is now run with stable/ocata.
Adds ability to skip specific build for particular component specifying
"supported_releases" in zuul component configuration. Sets
supported_releases for placement not available for releases prior to
Stein.
Removes redundant parameters for project reference using defaults
instead, as they relate to loci project, not to project we build
with loci. Also hard-codes parameters in playbooks/vars.yaml, making
it a definitive build configuration.
Change-Id: I7290203d80461f46ed70d5e3bea55c9765f9e746
This includes the building of OpenSUSE Leap 15 in checks/gates.
As the build of each project requires the building of the
requirements first, added to the fact that a new distro is added
into the jobs, this extends the timeout for the base job beyond
the maximum time for requirements, so that all the projects
(excluding requirements) have more time to complete.
Change-Id: I73b055b3942a6d80b8474544a9d65df0b3005e15
Without this patch, the loci builder automatically consumes a
previously published requirements image when the project is not
"requirements". This also means the first step in checks/gates
for non requirement images would be to pull a requirement.
Currently there is neither a "pipeline" nor consumption of
artifacts between jobs. Which means the "requirements" build
and the other image build have to be considered as independant.
However, by default, the "non-requirements" image built is
consuming previously published "requirements" image, but not
immediately previous built requirements image.
This is a problem, as it leaves us open to a race condition
where a new build of "requirements" and "non-requirements"
can succeed in a commit, but would cause all the next
"non-requirements" builds to fail, as it is possible the
newly published "requirements" to be incompatible with
the next "non-requirements", as they are not tested together.
This should fix the problem by ensuring that "requirements"
are always built and consumed in the "non-requirement"
building process, instead of re-using the previously built
requirements. For this, project needs to be overriden to
build the requirement image, and therefore a new profile
'requirements' was added to the buildargs of the distros.
Requirements repo also needs to be cloned in the gating
environment, and therefore was added to all the required
projects.
This will also allow new branches to be created, as there
would be no need of a previous build and publish
of requirements in the gating.
Change-Id: I093e4dfc0eef03c47d2d029011fdb5429242ae79
OpenStack test changes of main repos like nova, keystone, neutron
in the same pipeline. These are meant to be delivered together,
and therefore I think the images that are built by loci should
be built together. It is currently in-line with current loci
code, as there is already many loci jobs like loci-keystone,
loci-nova, loci-neutron, in the main repository.
However, while all the loci-* jobs are passing, only the
loci-requirements is voting.
This is a problem, as code could (theoretically) merge while
breaking a test.
This should fix it.
Change-Id: I6173b57b2b2f79341a9c57acc1aa74f1a9d9facf
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I9d7fad04e0158a18baeb89441264b9202c358234
The secret needed to be updated to make this work. Now we are pushing to
quay.io as well, both under the same loci namespace
Change-Id: I086aec21c2ebe69bcdf0aa25749280d8878f946d
We will be switching to a slightly different job structure to prevent
this from happening in the future
Change-Id: I49457eae5055c519287c079e3942e9ebc4d4bcd4
Zuul now supports including the file extension on the playbook path
and omitting the extension is now deprecrated. Update references
to include the extension.
Change-Id: I6f1d939c9b44811fbbad3e67bebed56308d2e892
Vladimir Kozhukalov