This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I720104960ed2c611dc40534feddc02fac7ee8ca8
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Id7cee8138dd60acaf4ebc055fce05985529c2421
Story: #2002586
Task: #24319
We reinitialize the venv to ensure that the right version of
python is in the venv, but we do not want virtualenv to also
replace pip, setuptools and wheel so we tell it not to. If we
don't do this then virtualenv will install the latest available
version, which is not what we want.
Change-Id: I39e64f29e794075ef303d3e1a2c0c1a6a18937b6
Partial-Bug: #1764470
(cherry picked from commit a9561bbce9)
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I31e6655743d3f69a84046978fe40f76021823cf3
In the previous patch removing the virtualenv-tools, we've updated
paths to the proper binaries, but we don't reset the virtualenv
like what we used to do.
Change-Id: I799bec0d7422406b5364407d7bf740612413959b
Partial-Bug: #1741634
virtualenv-tools has a bug which gets triggered in gates: it can't
change the shebang of a virtualenv python bin/ files if they
were generated with a virtualenv script whose shebang ends with
python2 instead of python.
Because we can't modify virtualenv-tools, we use shell scripts
instead.
Change-Id: Ia154238ef95767576283c3230d93748f65b56606
Partial-Bug: #1741634
This causes linters to break: since ansible 2.4 the systemd
module can have only the daemon_reload directive.
Change-Id: I808068128afa92f800d01636bef3a431cff1054b
With addition of pip_install on every node, we don't
need to have pip_install as a meta dependency.
Depends-On: If3412bb888ebb854874bbc43eb76bfcb3e4a7868
Depends-On: I79ff70c438b44753be2a93f004ebbc46de0a963d
Change-Id: Id0c03817663b7a05f9db0f7a53439f29fd83fb08
Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.
Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
.
Change-Id: Iaca6b8618133f07d12d1f8b01530020bfa46bd58
Initially the intent for adding this was to better test
any patches for roles together before they merge, but it
has had the unintended side-effect of causing patches to
take much longer to merge (because they all get lined up
in a single queue, rather than independent queues) and
a lot more infra resources are used (because a patch
that fails at the top of the queue will result in all
subsequent patches restarting all their tests).
As discussed in the channel, we'd prefer to revert back
to the previous independent queue method of testing. It
has served us well.
Change-Id: I8658108ad13cdc2fb2ff27e3079577f638cdbb11
This patch implements an initial set of jobs intended to match
the current job execution method. It does not intend to improve
how the jobs are executed - only to replicate what is currently
in openstack-infra/openstack-zuul-jobs and provide the platform
to iterate on.
Depends-On: I0391ec310c4eede436011a48490e3c524c8ddf4d
Change-Id: I3cb805ca067970033ba49f9ec5ef6c2db1fb8719
We need to add openstack ansible information in the role
metadata to be able to track role maturity. With it,
we can create a role maturity table and take decisions about
role deprecations.
Change-Id: I518fe35a49f4088f03ee2c0f4f1ba5e22db9ea64
Update searchlight.conf's service_credentials options to use Keystone
v3 and reorder the install tasks so that the service is setup before
attempting an index sync.
Change-Id: I13b4fa07fae269a681c2075fb6be40aa5bffa40e
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: I3c5aa514b815f2d7bd50ee274c6ec49522e56ea6
The keystonemiddleware library recently switched to using the
cryptography library over pycrypto, which was unmaintained. See
Iced7f5115e49ccf4f7f5bf6813cb5988b95c248b
Change-Id: I53abb72a2ec8774069cfe0784ebab089b854f6a1
Co-Authored-By: Nolan Brubaker <nolan.brubaker@rackspace.com>
Import the initial verison of the os_searchlight role.
This role currently does the following:
- Installs a jdk, elasticsearch and searchlight
- Starts the searchlight services (api and listener)
- Does an initial DB sync
- Listens for messages from other openstack services
- installs the openstack CLI plugin
Current issues / TODO list:
- linting of Stouts.elasticsearch role
- Setup Apache site properly.
Change-Id: I3ff72c9fbfc96a1f80f5cdd51a91f4d7ef638682