Rename tools/atc/email-stats.py to tools/atc/email_stats.py in
preparation for making it an importable module. This is being
separated from the subsequent change to make it more reviewable.
Change-Id: I1907de0715c96f54edb44910746fbb24a5ab8665
The zuul node label selection functions missed a few corner cases where
precise, centos6, or trusty needed to be selected. Specifically if the
job name includes precise that job should run on precise. If the job
name says centos6 that job should run on centos6 and so on.
Change-Id: If9a99c0347412c8bb54dd663dbdca4908cb3eb03
This reverts commit 72c32e161e126a7dfdda82f801ba4c18b2f76a9e.
Jenkins masters have all had their gearman plugin updating which makes
them register jobs properly.
Change-Id: I6894e590a2ee033ad46149c2859b8f8c33055c5a
This reverts commit 607b2f2ab4962dec4f4400ecc4687db2b206003a.
Jenkins masters have all had their gearman plugin updating which makes
them register jobs properly.
Conflicts:
modules/openstack_project/files/zuul/layout.yaml
Change-Id: I3edeb26c9a1d3878b80266ea32d333bd8fc2f67e
Temporary make gate-rally-install-bare-centos6 non voting.
For some reason this job is failing with "NOT_REGISTERED" flag.
So make it temporary non voting, until things are fixed
Change-Id: Ic9e71ffd17a7949d25a46a3cc6e4e552869b5936
The OpenStack Identity (Keystone) team has decided to split the
packaging of the middleware used by external services (both from
Keystone and python-keystoneclient) into it's own separate packaging.
This is to enable the reduction in dependencies required by the
keystoneclient library (some dependencies are specific to servers
such as memcache) and allow for releasing fixes to the various
middleware code without needing to also release either a fix to
Keystone or a fix to the keystoneclient library.
The new keystonemiddleware project will be released independent
of the OpenStack named-cycle (similar to the client libraries).
Further details on this change can be seen in the approved
Keystone specification: https://review.openstack.org/#/c/95987/
The upstream repository is an extraction of the middleware from the
respective repositories maintaining the commit history.
Change-Id: I44a0d59999c720fe9eee99e322138818080b41e0
We need to check django_openstack_auth on stable releases as well,
otherwise we'll run into an issue where it breaks stable.
Change-Id: Iad769129da5bcfeffd07cd0a22a60e55fcb95ea5
Related-Bug: #1331406
This patch will build and upload the files required to boot the
Ironic Python Agent ramdisk using CoreOS and a Docker container.
The Ironic Python Agent is one of the methods to provision servers
in Ironic. This will make testing the agent much easier.
Change-Id: I34ea9a196c5ac1954a4ebd6d27850f6b6e56afa7
Co-Authored-By: Jay Faulkner <jay@jvf.cc>
This reverts commit 46b8b8857dad86431652217b0edd616dbf5c7b0b.
This is necessary as there is a bug in the Jenkins gearman-plugin that
prevents node selection from working properly. Adding this will cause
jobs to run on trusty even if we don't want them to run there. Revert to
avoid this problem.
Change-Id: Ie8541cdb4fafe0db87e1785374a26539811e80f5
This reverts commit c76f930c09b57ac134d8610ed5fde6d3b802806b.
This is necessary as there is a Jenkings gearman-plugin bug that causes
a node to register all available labels for a job even if it is capable
of serving only one label. This bug prevents zuul from properly
selectiong nodes as desired by this change.
Change-Id: I035d31a91c4ca1a8366316b7ff422f4a2b03622c
We have trusty slaves, we have trusty workers registered in gearman,
make zuul use them for everything newer than icehouse when running dsvm
jobs.
Change-Id: Iae037e6c1853aee5044c8e8549d8b6dc93db2b02
Now that zuul is selecting the node label for all jobs we can make
trusty an option for all dsvm jobs. A subsequent change will update zuul
to select trusty nodes. We are staggering the changes to avoid races
between zuul and jenkins config updates.
Change-Id: If3abb111f9378c192e647ceaced5bc9b16fe6bb4
In order to facilitate the transition from precise to trusty for Juno
testing we need to make zuul the decider of node labels for every job.
Do this by refactoring how we apply parameter functions to zuul jobs.
Since we can have only one parameter function per job it is easier to do
decision logic in a single global parameter function. Add this single
function and have it maintain backward compatbility with old parameter
function selections. But also make it select the ZUUL_NODE for every
job.
Change-Id: I42fa26fc42c7dc4e94d3a7382cc8de0a5e6d1f36
The destination prefix is given by the calcuated LOG_PATH env
variable now that zuul sets a deterministic path for patchsets.
Also fix joining the final path variables
Change-Id: I6d98b0df8bb87d8ad136a8df0d5bf04d2e27a628
Once we have trusty nodes we can run tempest and grenade on them in the
experimental queue as the first step in migrating juno from precise to
trusty. Start the process with this change.
Change-Id: Ib96bd2439e09c21b7fc69da910e3d4073995b8a5
Start booting devstack and bare trusty images with nodepool. This will
allow us to start the migration to trusty while we work on adding dib
support to nodepool.
Change-Id: I07b90af0dc4a5cfb5c547c28d05d8d51c59b9c8e
devstack-vagrant is a set of vagrant tooling around devstack to
make it super easy to bring up devstack locally on any machine
that supports vagrant. It includes a few top level config options
to bring up some custom configs of devstack, and will be evolved
to make it easy to replicate very closely the configuration of
devstack-gate.
Change-Id: I24390f5fbd582b8d7d268c6460ac24479c63719f
Adding the project definition for the Octavia project - an LBaaS
reference implementation.
Includes:
- Adds project to Stackforge
- Gerritbot for Freenode in #openstack-lbaas
- Adds basic Python Jenkins and Zuul jobs
- Adds Gerrit ACLs for the repo
Change-Id: I1fcdefd295dc7f23be6fa66e523d269f6ca32b42
Logaas is Logging as a Service for OpenStack
Goal of this project is to unify process of how we are dealing with
logs in OpenStack based on logstash/syslog and other backends, and
as well present OpenStack API for querying logs.
Change-Id: I4d115794d50e58f9277506425ba8600c67583afe
Put the variables defined in manifests/site.pp at the top of the file so
that they are in a known location after running csplit in test.sh and we
can prepend them to the puppet-apply top files.
A better solution would be to move this data into hiera, but this is not
sensitive data, so a move to hiera should wait until we a have solution
for a public hiera data repo separate from the private hiera data.
Change-Id: I509a8266462dfdf53e1727938e4fb043241166b6
